JP7637583B2 - Vehicle allocation management device and vehicle allocation management method - Google Patents

Description

The present invention relates to a vehicle dispatch management device and a vehicle dispatch management method for managing the dispatch of taxis.

Conventionally, systems for managing taxi dispatch are known. For example, Patent Document 1 proposes a system that manages the taxi status, which indicates whether the taxi is available or not, and the taxi's location information, and when it receives the current location from a taxi user, searches for taxis in the vicinity of the current location and notifies the user of the search results.

JP 2011-248848 A

When multiple dispatch requests are accepted from one user, the user may unintentionally make multiple dispatch requests with dispatch dates and times close to each other, resulting in a situation in which the user does not show up at the dispatch location for any of the dispatch requests (a so-called no-show). In such cases, the effort of the taxi driver to travel to the dispatch location is wasted, to the driver's detriment.

The present invention was made in consideration of these points, and aims to prevent a situation in which a taxi driver's efforts are wasted when multiple dispatch requests are received from a single user.

The vehicle dispatch management device of the first aspect of the present invention has a reception unit that receives a plurality of vehicle dispatch requests from a user for dispatching a vehicle at a specified date and time and a specified location, and a request transmission unit that transmits a vehicle dispatch request to a vehicle for dispatching a vehicle to the specified location of each of the vehicle dispatch requests at the specified date and time of the plurality of vehicle dispatch requests, and the reception unit does not accept the second vehicle dispatch request when a second vehicle dispatch request is accepted from the user after accepting a first vehicle dispatch request from the user, when the specified date and time of the second vehicle dispatch request is included in a predetermined period based on the specified date and time of the first vehicle dispatch request, and accepts the second vehicle dispatch request when the specified date and time of the second vehicle dispatch request is not included in the period.

The reception unit may receive the setting of the period from an administrator who manages the vehicle dispatch management device.

The vehicle dispatch management device may further include a notification unit that notifies the user terminal of information indicating whether the specified date and time is included in the period while the specified date and time is being accepted at the user terminal used by the user.

The reception unit may receive the second vehicle dispatch request even when the period includes the specified date and time of the second vehicle dispatch request if the specified date and time and the specified location of the first vehicle dispatch request are the same as the specified date and time and the specified location of the second vehicle dispatch request.

When the reception unit receives a first vehicle dispatch request from a first user to dispatch a vehicle to the first user, and then receives a second vehicle dispatch request from the first user to dispatch a vehicle to a second user different from the first user, the reception unit may accept the second vehicle dispatch request even when the specified date and time of the second vehicle dispatch request is included in the period.

The request transmission unit may not need to transmit the dispatch request for the dispatch request if a vehicle has been dispatched to the user or the user is in the vehicle before the specified date and time of the dispatch request.

The request transmission unit may not transmit the dispatch request for the dispatch request if the user is in the vehicle before the specified date and time of the dispatch request, and the relationship between the specified location and at least one of the location or destination of the vehicle in which the user is in the vehicle satisfies a predetermined condition.

The reception unit may cancel the remaining vehicle dispatch requests among the multiple vehicle dispatch requests received from the user if the user does not board a vehicle dispatched based on a predetermined number or percentage or more of the multiple vehicle dispatch requests received from the user.

The vehicle dispatch management device may further have a selection unit that selects a candidate vehicle from among a plurality of dispatchable vehicles that are within a predetermined range based on the specified position of each of the plurality of dispatch requests at a time prior to the specified date and time of each of the plurality of dispatch requests, and the request transmission unit may transmit the dispatch request to the candidate vehicle selected by the selection unit.

The selection unit may predict a predicted arrival time at which each of the plurality of dispatchable vehicles will arrive at the specified location, and select the candidate vehicle from among the plurality of dispatchable vehicles based on a relationship between the predicted arrival time and the specified date and time.

The vehicle dispatch management method of the second aspect of the present invention includes the steps of: accepting a first vehicle dispatch request from a user for dispatching a vehicle to a first designated date and time and a first designated location, and accepting a second vehicle dispatch request from the user for dispatching a vehicle to a second designated date and time and a second designated location after accepting the first vehicle dispatch request from the user, where the second vehicle dispatch request is not accepted when the second designated date and time is included in a predetermined period based on the first designated date and time, and the second vehicle dispatch request is accepted when the second designated date and time is not included in the period; transmitting a first vehicle dispatch request to a vehicle for dispatching a vehicle to the first designated location at the first designated date and time; and transmitting a second vehicle dispatch request to a vehicle for dispatching a vehicle to the second designated location at the second designated date and time.

The present invention has the effect of preventing a taxi driver's efforts from being wasted when multiple dispatch requests are received from a single user.

FIG. 1 is a diagram for explaining an overview of a vehicle dispatch management system according to an embodiment. FIG. 1 is a block diagram of a vehicle dispatch management system according to an embodiment. FIG. 13 is a schematic diagram of a user terminal displaying a vehicle dispatch request screen. FIG. 13 is a schematic diagram of a user terminal displaying a vehicle dispatch request confirmation screen. 4 is a schematic diagram for explaining a method in which a selection unit selects a candidate vehicle. FIG. FIG. 13 is a schematic diagram of a driver terminal displaying a vehicle dispatch request screen. FIG. 13 is a schematic diagram of a user terminal displaying a notification screen. FIG. 2 is a flowchart illustrating an exemplary vehicle dispatch management method executed by the vehicle dispatch management device according to the embodiment. FIG. 13 is a schematic diagram of a user terminal displaying a vehicle dispatch request list screen. FIG. 13 is a schematic diagram of a user terminal displaying a vehicle dispatch request screen. FIG. 11 is a flowchart showing a process of receiving a vehicle dispatch request in an exemplary vehicle dispatch management method executed by a vehicle dispatch management device according to a modified example. FIG. 11 is a flowchart showing a process of transmitting a vehicle dispatch request in an exemplary vehicle dispatch management method executed by a vehicle dispatch management device according to a modified example.

First Embodiment
[Overview of the vehicle allocation management system]
1 is a diagram for explaining an overview of a vehicle dispatch management system according to this embodiment. The vehicle dispatch management system is a system for managing the dispatch of taxis, and includes a vehicle dispatch management device 1, a user terminal 2, and a driver terminal 3. The vehicle dispatch management system may also include other devices such as a server and a terminal.

The dispatch management device 1 is a computer such as a server that manages the dispatch of taxis. The dispatch management device 1 accepts a dispatch request from a user to dispatch a taxi to a specified date and time and to a specified location, and selects a vehicle that can be dispatched in response to the dispatch request and issues a dispatch request. The dispatch request may include any type of information that can convey to a taxi dispatching company that a user (also called a customer or passenger) who uses a taxi desires to be dispatched. The dispatch management device 1 is connected to multiple user terminals 2 and multiple driver terminals 3 via a communication network such as the Internet.

The user terminal 2 is an information terminal such as a smartphone or tablet terminal used by a user. The user terminal 2 has a display unit such as a liquid crystal display capable of displaying information, and an operation unit such as a touch panel capable of receiving operations by a human. The user terminal 2 has installed therein a vehicle dispatch application program (hereinafter referred to as the "vehicle dispatch application") that receives input of taxi dispatch conditions from a user.

The crew terminal 3 is an information terminal such as a smartphone or tablet terminal used by the taxi crew (also called the driver) and is provided in the taxi. The crew terminal 3 may be a device integrated with the vehicle, such as a car navigation system. The crew terminal 3 has a display unit such as a liquid crystal display capable of displaying information, and an operation unit such as a touch panel capable of receiving operations by a human. A crew application program (hereinafter referred to as a "crew application") is installed on the crew terminal 3, which displays a request for dispatch to the crew and receives approval for dispatch from the crew.

An overview of the processing executed by the vehicle dispatch management system according to this embodiment is provided below. The user terminal 2 executes a vehicle dispatch application and transmits a dispatch request to the vehicle dispatch management device 1 for dispatching a taxi to a specified date and time and a specified location in the future in response to a user operation.

The vehicle dispatch management device 1 accepts a dispatch request from the user terminal 2 to dispatch a vehicle to a specified date and time and a specified location. The vehicle dispatch management device 1 selects candidate vehicles from among multiple dispatchable vehicles that are within a specified range based on the specified location at a time before the specified date and time. The specified range based on the specified location is, for example, a range within a specified distance from the specified location, or a range that is preset as an area where a vehicle can be dispatched to the specified location. The specified range based on the specified location may be a range that is preset as an area in which the user can travel to the specified location within a time that is set as the minimum value of the difference between the date and time when the user made the dispatch request and the specified date and time. The specified range based on the specified location may also be a range that is set based on another location that corresponds to the specified location. In this case, the specified range based on the specified location is, for example, a range associated with a reference position within a specified area that includes the specified location.

The vehicle dispatch management device 1 selects a candidate vehicle, for example, at a time before the pick-up arrangement time on the specified date and time. The pick-up arrangement time is the time assumed to be required for a dispatchable vehicle to go to the location of the user using the user terminal 2 to pick up the user. The pick-up arrangement time is, for example, the longest time assumed for a dispatchable vehicle in the vicinity of the specified location to reach the specified location after a dispatch request is made to the dispatchable vehicle. As an example, the pick-up arrangement time is the longest time assumed to be required for a vehicle located farthest from the specified location within the above-mentioned specified range to move to the specified location, for example, 10 to 20 minutes.

The vehicle dispatch management device 1 transmits a dispatch request to the selected candidate vehicle to dispatch the vehicle to the specified location. The driver terminal 3 installed in the candidate vehicle executes a driver application and transmits a dispatch acceptance to the vehicle dispatch management device 1 in response to the driver's operation.

When the vehicle dispatch management device 1 receives a dispatch acceptance from the driver terminal 3 of the candidate vehicle, it determines the candidate vehicle as the dispatch vehicle to be dispatched to the user and transmits a dispatch instruction to the driver terminal 3 of the dispatch vehicle.

In this way, the vehicle dispatch management device 1 selects a candidate vehicle to be dispatched to the user from among the vehicles available for dispatch that are in the vicinity of the specified location at a time prior to the specified date and time, and transmits a dispatch request. This allows the taxi driver to appropriately accept dispatch to the user as the specified date and time approaches, eliminating the need to adjust taxi operations or wait for long periods of time in the vicinity of the specified location. Therefore, the vehicle dispatch management device 1 can dispatch a taxi to the specified date and time and location specified by the user, while reducing the burden on the taxi driver.

[Configuration of the vehicle allocation management system]
FIG. 2 is a block diagram of the vehicle dispatch management system according to this embodiment. In FIG. 2, the arrows indicate the main data flows, and there may be data flows other than those shown in FIG. 2. In FIG. 2, each block indicates a functional configuration, not a hardware (device) configuration. Therefore, the blocks shown in FIG. 2 may be implemented in a single device, or may be implemented separately in multiple devices. Data may be exchanged between blocks via any means, such as a data bus, a network, or a portable storage medium.

The vehicle dispatch management device 1 has a communication unit 11, a storage unit 12, and a control unit 13. The vehicle dispatch management device 1 may be configured by connecting two or more physically separate devices by wire or wirelessly. The vehicle dispatch management device 1 may also be configured by a cloud, which is a collection of computer resources.

The communication unit 11 is a communication interface for communicating with the user terminal 2 and the crew terminal 3 via a communication network such as the Internet. The storage unit 12 is a storage medium including a ROM (Read Only Memory), a RAM (Random Access Memory), a hard disk drive, etc. The storage unit 12 pre-stores programs to be executed by the control unit 13. The storage unit 12 may be provided outside the vehicle dispatch management device 1, in which case data may be exchanged between the storage unit 12 and the control unit 13 via the network.

The control unit 13 has a reception unit 131, a calculation unit 132, a selection unit 133, a request transmission unit 134, a vehicle dispatch instruction unit 135, and a notification unit 136. The control unit 13 is a processor such as a CPU (Central Processing Unit), and functions as the reception unit 131, the calculation unit 132, the selection unit 133, the request transmission unit 134, the vehicle dispatch instruction unit 135, and the notification unit 136 by executing a program stored in the storage unit 12. At least some of the functions of the control unit 13 may be performed by an electric circuit. In addition, at least some of the functions of the control unit 13 may be realized by the control unit 13 executing a program executed via a network.

The reception unit 131 receives a request for dispatching a vehicle to a specified date and time and a specified location. The user terminal 2 displays a dispatch request screen on the display unit for the user to input a dispatch request for dispatching a vehicle to a specified date and time and a specified location. Figure 3 is a schematic diagram of the user terminal 2 displaying the dispatch request screen A.

The dispatch request screen A includes a designated location field A1 for inputting a designated location that is the departure point when the user receives a taxi dispatch, and a designated date and time field A2 for inputting a designated date and time that is the date and time when the user receives the taxi dispatch. The designated location field A1 may accept as the designated location a location that is designated by the user on a map included in the dispatch request screen A, or may accept as the designated location an address that is input by the user.

In the example of FIG. 3, the user terminal 2 accepts input of the specified date and time after accepting input of the specified location, but the order in which each piece of information is accepted and the input method are not limited. Furthermore, the dispatch request screen A may accept input of other information related to the dispatch request, such as the destination of the user after receiving the taxi dispatch and the payment method that the user will use to pay the taxi fare.

The user terminal 2 transmits the information input by the user on the dispatch request screen A to the dispatch management device 1 as a dispatch request. The dispatch request is information including, for example, a specified date and time and a specified location. As an example, in the dispatch management device 1, the reception unit 131 receives a dispatch request including a specified date and time and a specified location from the user terminal 2. At this point, the reception unit 131 does not confirm the received dispatch request.

The reception unit 131 may also receive information indicating a specified date and time and a specified location from a terminal other than the user terminal 2, and then receive a vehicle dispatch request from the user terminal 2 that does not include a specified date and time and a specified location. In this case, the reception unit 131 may, for example, associate a vehicle dispatch request received from a user terminal 2 in which user identification information (hereinafter, user ID) for identifying a user who uses the user terminal 2 is set with a specified date and time and a specified location received from another terminal in which the user ID is set.

The calculation unit 132 calculates the dispatch success probability, which is the probability that a vehicle can be dispatched at the time specified by the user, and is used by the vehicle dispatch management device 1 to decide whether to accept a dispatch request at the specified date and time. The calculation unit 132 calculates the dispatch success probability based on information on past dispatch performance by vehicles within a specified range based on the specified position, for example. In order to calculate the dispatch success probability, the calculation unit 132 acquires statistical information corresponding to the number of vehicles that have been dispatched in the past in the surrounding area including the specified position, as an example. The surrounding area is, for example, a specified area such as a business district including the specified position where taxis can operate as a business, or an area within a specified range (for example, a circle with a radius of 2 km) centered on the specified position.

The statistical information includes, for example, the average supply of taxis in the surrounding area and the actual dispatch time required for past dispatches. The average supply is the average number of dispatchable taxis, tabulated by time period, day of the week, date, etc. The actual dispatch time is, for example, the time it takes to dispatch a taxi with a given probability (for example, the 95th percentile), tabulated by time period, day of the week, date, etc. for each mesh area (mesh) on the map.

The calculation unit 132 calculates an estimated required time, which is the time estimated to be required for a taxi to reach a specified position, based on the average supply number and actual dispatch time included in the statistical information. The calculation unit 132 calculates the dispatch success probability that a taxi can be dispatched to a specified position at a specified date and time, based on, for example, the average supply number included in the statistical information and the calculated estimated required time. The dispatch success probability is the probability that a dispatchable taxi can be secured within a specified pick-up arrangement time, and that the taxi can arrive at the specified position.

The calculation unit 132 calculates the probability of successful dispatch as the probability that a greater number of taxis can be secured within the time obtained by subtracting the estimated required time from the pick-up arrangement time, using, for example, the average supply number for the same category as the time slot, day of the week, or date of the specified date and time.

In addition, the calculation unit 132 may use past dispatch records within a specified range based on the specified location instead of statistical information to calculate the dispatch success probability of dispatching a vehicle to the specified location at the specified date and time. The calculation unit 132 is not limited to the specific method shown here for calculating the estimated required time and the dispatch success probability, and may use other methods based on information on past dispatch records.

The calculation unit 132 also calculates the dispatch fee for the dispatch request according to the predicted conditions of a predetermined range based on the specified location at the specified date and time. The calculation unit 132 acquires, for example, weather forecast information indicating the weather conditions of a predetermined range based on the specified location at the specified date and time, and traffic forecast information indicating the traffic conditions of a predetermined range based on the specified location at the specified date and time, from an external server. The calculation unit 132 calculates the dispatch fee based on the number of dispatch requests already accepted at the specified date and time, the weather forecast information, and the traffic forecast information.

For example, the calculation unit 132 may set the arrangement fee higher when the weather forecast information indicates bad weather than when the weather forecast information does not indicate bad weather. For example, the calculation unit 132 may set the arrangement fee higher when the traffic forecast information indicates the occurrence of congestion than when the traffic forecast information does not indicate bad weather.

The calculation unit 132 may set a higher dispatch fee the more dispatch requests that have already been accepted at the specified date and time. The calculation unit 132 may set a higher dispatch fee the more dispatch requests that have been accepted within a specified period before the specified date and time. The period corresponds to the average length of one ride, for example, 15 minutes. The calculation unit 132 determines the dispatch fee based on the number of dispatch requests in this way, which leads to an equalization of the frequency at which dispatch requests are made.

The calculation unit 132 also calculates the dispatch success probability and dispatch fee in a similar manner for one or more candidate dates and times (e.g., 10 minutes before and 10 minutes after the specified date and time) that are different from the specified date and time within a predetermined period based on the specified date and time, in addition to the specified date and time. The calculation unit 132 notifies the reception unit 131 of the calculated dispatch success probability and dispatch fee.

The reception unit 131 transmits to the user terminal 2 information necessary for the user terminal 2 to display a dispatch request confirmation screen that allows the user to set the specified date and time for dispatch. The reception unit 131 transmits to the user terminal 2 information including, for example, whether the specified date and time and candidate date and time can be selected based on the dispatch success probability calculated by the calculation unit 132, and the dispatch fee required to dispatch a taxi at the specified date and time and candidate date and time. Based on the information received from the dispatch management device 1, the user terminal 2 displays on the display unit a dispatch request confirmation screen that allows the user to confirm the dispatch request. Figures 4(a) and 4(b) are schematic diagrams of the user terminal 2 displaying the dispatch request confirmation screen B.

Figure 4(a) shows a dispatch request confirmation screen B that is displayed when the dispatch success probability is equal to or greater than a predetermined threshold (e.g., a predetermined value such as 0.95, 0.99, etc.). On the other hand, Figure 4(b) shows a dispatch request confirmation screen B that is displayed when the dispatch success probability is less than the threshold.

The dispatch request confirmation screen B includes a specified date and time selection field B1 for the user to select a specified date and time, and a candidate date and time selection field B2 for the user to select a candidate date and time. The specified date and time selection field B1 represents the specified date and time specified by the user on the dispatch request screen A, and the arrangement fee for the specified date and time. The candidate date and time selection field B2 represents one or more candidate dates and times different from the specified date and time (for example, 10 minutes before and 10 minutes after the specified date and time), and the arrangement fee for each of the one or more candidate dates and times. The candidate date and time selection field B2 does not represent candidate dates and times for which the probability of dispatch success is less than a threshold value, but only represents candidate dates and times for which the probability of dispatch success is equal to or greater than a threshold value.

In this way, the vehicle dispatch management device 1 presents to the user the designated date and time, candidate date and time, and the dispatch fee for each of the designated date and time and candidate date and time in association with each other. Since the dispatch fee is set to vary depending on the congestion level of dispatch requests, weather forecasts, traffic predictions, etc., the vehicle dispatch management device 1 can prevent dispatch requests from concentrating on specific dates and times.

The reception unit 131 receives a selection of either the specified date and time or the candidate date and time on the dispatch request confirmation screen B displayed on the user terminal 2. The reception unit 131 receives a dispatch request for dispatching a vehicle to a specified location specified on the dispatch request screen A at the specified date and time or the candidate date and time selected on the dispatch request confirmation screen B as a confirmed dispatch request, and stores the request in the memory unit 12 in association with the user ID.

In the dispatch request confirmation screen B, if the dispatch success probability is equal to or greater than a threshold, the specified date and time selection field B1 is selectable as shown in FIG. 4(a), and if the dispatch success probability is less than the threshold, the specified date and time selection field B1 is not selectable as shown in FIG. 4(b). That is, the reception unit 131 accepts a dispatch request for dispatching a vehicle to a specified date and time and a specified location, on the condition that the dispatch success probability is equal to or greater than a threshold. In this way, the dispatch management device 1 accepts a dispatch request for a specified date and time, on the condition that the dispatch success probability for the specified date and time calculated based on statistical information is high, thereby reducing the probability that a taxi cannot be arranged just before the specified date and time, and preventing disadvantages to the user.

On the other hand, if the probability of successful dispatch is less than the threshold, the reception unit 131 does not accept a dispatch request for the specified date and time, but accepts a dispatch request for dispatching a vehicle to the selected candidate date and time and the specified location. In this way, if the probability of successful dispatch for the specified date and time calculated based on statistical information is low, the dispatch management device 1 suggests to the user a candidate date and time that is different from the specified date and time and has a high probability of successful dispatch, thereby improving user convenience.

In addition, instead of or in addition to the probability of successful dispatch, the reception unit 131 may determine whether to accept a dispatch request for the specified date and time based on the number of dispatch requests already accepted for the specified date and time. In this case, the reception unit 131 acquires information that indicates the maximum number of dispatch requests that can be accepted for each date and time, which is pre-stored in the memory unit 12.

The maximum number may be a fixed value for each date and time, or may be a value determined according to at least one of weather conditions or traffic conditions in a predetermined range based on the specified location at the specified date and time. The reception unit 131 receives the setting of the maximum number value, for example, on a terminal of a business operator that provides a vehicle dispatch management system. The reception unit 131 may also determine, as the maximum number value, a number associated with at least one of weather conditions or traffic conditions in a predetermined range based on the specified location at the specified date and time, for example, using a table that previously associates weather information or traffic conditions with the number of vehicle dispatch requests that can be accepted.

The reception unit 131 may also determine the maximum number based on the number of past dispatch requests within a predetermined range based on the specified position. In this case, the reception unit 131 may, for example, increase the maximum number as the number of past dispatch requests decreases, and decrease the maximum number as the number of past dispatch requests increases.

If the number of dispatch requests already accepted at the specified date and time is equal to or greater than the maximum number, the reception unit 131 does not accept a dispatch request for dispatching a vehicle at the specified date and time, and otherwise accepts a dispatch request. This allows the dispatch management device 1 to reduce the probability that a taxi cannot be arranged just before the specified date and time.

On the dispatch request confirmation screen B, if the number of dispatch requests already accepted at the specified date and time is less than the maximum value, the specified date and time selection field B1 can be selected as shown in FIG. 4(a), and if the number of dispatch requests already accepted at the specified date and time is equal to or greater than the maximum value, the specified date and time selection field B1 cannot be selected as shown in FIG. 4(b).

In other words, the reception unit 131 accepts a dispatch request for dispatching a vehicle to the specified date and time and the specified location, on the condition that the number of dispatch requests already accepted for the specified date and time is less than the maximum value. On the other hand, if the number of dispatch requests already accepted for the specified date and time is equal to or greater than the maximum value, the reception unit 131 does not accept a dispatch request for the specified date and time, and instead accepts a dispatch request for dispatching a vehicle to the selected candidate date and time and the specified location.

In this way, the vehicle dispatch management device 1 switches whether to accept a vehicle dispatch request for the specified date and time depending on the number of vehicle dispatch requests that can be accepted for each date and time, and proposes other candidate dates and times, thereby reducing the probability that a taxi cannot be arranged just before the specified date and time, and preventing disadvantages to the user.

In response to the reception unit 131 receiving a vehicle dispatch request from a user, the selection unit 133 selects a vehicle to be instructed to dispatch at a time before the specified date and time. For example, the selection unit 133 selects a candidate vehicle to which a dispatch request is to be sent from among multiple dispatchable vehicles within a predetermined range based on the specified location, based on the specified date and time and specified location included in the dispatch request received by the reception unit 131 at a time before the pick-up arrangement time for the specified date and time. As described above, the pick-up arrangement time is the longest expected time for a dispatchable vehicle in the vicinity of the specified location to reach the specified location after a dispatch request is made to the dispatchable vehicle, and is a predetermined time of, for example, 10 to 20 minutes.

The predetermined range used to select candidate vehicles is, for example, a surrounding area including the specified location. The surrounding area is, for example, a business district including the specified location where taxis can travel as part of their business, or a predetermined area (for example, a circle with a radius of 2 km) centered on the specified location. The predetermined range used to select candidate vehicles may also be an area that does not include the specified location, but is defined based on the specified location, and does not include the specified location (for example, a donut-shaped area centered on the specified location). The shape of the predetermined range is not limited to a circle, and may be another shape. The boundaries of the predetermined range may be determined by the boundaries of a city, town, or village, or the boundaries of the business area of a taxi company.

The selection unit 133, for example, preferentially selects a candidate vehicle that has a high probability of arriving at the specified position at the specified date and time, and if the selected candidate vehicle is unable to respond to the dispatch request, selects another candidate vehicle that has the potential to arrive at the specified position at the specified date and time from among vehicles excluding the previously selected candidate vehicle. The selection unit 133 then selects, for example, another candidate vehicle that has the potential to arrive at the specified position earlier than the previously selected candidate vehicle. The selection unit 133 notifies the request transmission unit 134 of the selected candidate vehicle and causes the request transmission unit 134 to transmit a dispatch request to the candidate vehicle.

The request sending unit 134 sends a dispatch request to dispatch a vehicle to the specified location to the driver terminal 3 installed in the candidate vehicle selected by the selection unit 133. The dispatch request is, for example, information including the specified location. The dispatch request may include a specified date and time in addition to the specified location.

Figure 5 is a schematic diagram for explaining how the selection unit 133 selects a candidate vehicle. Figure 5 shows a surrounding area R that includes the specified location. The surrounding area R is a specified area, such as a business district that includes the specified location where a taxi can travel for business purposes, or an area within a specified range (e.g., a circle with a radius of 2 km) centered on the specified location.

The example in Figure 5 shows a situation in which the selection unit 133 starts selecting candidate vehicles at the current time, 16:48, because the specified date and time is 17:00 and the pick-up arrangement time is set to 12 minutes.

The selection unit 133 acquires the specified date and time and the specified location included in the dispatch request accepted by the acceptance unit 131. The selection unit 133 also acquires location information indicating the location of the taxi identified using a Global Positioning System (GPS) from the driver terminal 3 installed in each of the multiple taxis.

The selection unit 133 identifies a plurality of dispatchable vehicles that are in a surrounding area R including the designated position based on the position information of each of the plurality of taxis. The dispatchable vehicles are taxis that are located in the surrounding area R and are vacant. The selection unit 133 predicts the predicted arrival time at which each of the identified plurality of dispatchable vehicles will arrive at the designated position. The selection unit 133, for example, uses a known route search method to search for a route from the position of the dispatchable vehicle to the designated position, and calculates the predicted arrival time at which the dispatchable vehicle at a predetermined speed will travel the searched route and arrive at the designated position. The method used by the selection unit 133 to predict the predicted arrival time is not limited to the specific method shown here, and other methods may be used.

The selection unit 133 selects one of the candidate vehicles from among the multiple dispatchable vehicles based on the relationship between the predicted arrival time and the specified date and time, and causes the request sending unit 134 to send a dispatch request to the candidate vehicle. For example, the selection unit 133 selects, from among the multiple dispatchable vehicles, a vehicle whose predicted arrival time is closest to a time a predetermined time before the specified date and time (for example, two minutes before), as a candidate vehicle. In this way, the dispatch management device 1 can adjust the arrival of the taxi at the specified position slightly before the specified date and time specified by the user, and prevent the taxi from waiting for a long time and being delayed to the specified date and time.

When a candidate vehicle does not accept the dispatch request as described below, the selection unit 133 reselects, as a candidate vehicle, a vehicle having a predicted arrival time closest to a predetermined time (e.g., two minutes) before the specified date and time from among multiple dispatchable vehicles other than the candidate vehicle that did not accept the dispatch request, and causes the request transmission unit 134 to transmit a dispatch request to the candidate vehicle. The selection unit 133 may also select, as a candidate vehicle, a vehicle that can arrive earlier than the candidate vehicle that did not accept the dispatch request. The selection unit 133 repeats the selection of candidate vehicles until one of the candidate vehicles accepts the dispatch request. In this way, the dispatch management device 1 can search for a taxi that can be dispatched to the user at the specified date and time while respecting the wishes of the taxi driver.

The example in FIG. 5 shows a situation in which the selection unit 133 has identified vehicles V1, V2, and V3 as dispatchable vehicles and predicted the predicted arrival times of each of the vehicles V1, V2, and V3 at the designated position P. The selection unit 133 selects vehicle V1, which has a predicted arrival time closest to two minutes before the designated date and time of 17:00, as a candidate vehicle, and causes the request transmission unit 134 to transmit a dispatch request to vehicle V1. If vehicle V1 does not accept the dispatch request, the selection unit 133 selects vehicle V2, which has the next closest predicted arrival time after vehicle V1, which is two minutes before the designated date and time of 12:00, as a candidate vehicle, and causes the request transmission unit 134 to transmit a dispatch request to vehicle V2.

The selection unit 133 may determine the pick-up arrangement time according to the number of dispatchable vehicles in the surrounding area R. In this case, the selection unit 133, for example, shortens the pick-up arrangement time the more dispatchable vehicles there are, and lengthens the pick-up arrangement time the fewer dispatchable vehicles there are. In this way, when there are few vacant taxis around the specified location and it is expected that it will take some time to determine a taxi, the dispatch management device 1 lengthens the pick-up arrangement time, thereby increasing the probability of dispatching a taxi to the user at the specified date and time.

The selection unit 133 may also determine the pick-up arrangement time depending on the weather conditions or traffic conditions at the specified location. In this case, the selection unit 133 acquires weather forecast information and traffic prediction information from an external server. For example, when the weather forecast information indicates bad weather, the calculation unit 132 sets the pick-up arrangement time longer than when the weather forecast information does not indicate bad weather. For example, when the traffic prediction information indicates the occurrence of congestion, the calculation unit 132 sets the pick-up arrangement time longer than when the traffic prediction information does not indicate the occurrence of congestion. In this way, the vehicle dispatch management device 1 can increase the probability of dispatching a vehicle to the user at the specified date and time by lengthening the pick-up arrangement time when demand for taxis increases due to bad weather or when congestion causes a taxi to take a long time to arrive at the specified location.

Based on the dispatch request received from the dispatch management device 1, the crew terminal 3 displays a dispatch request screen on the display unit for the crew to accept the dispatch request. FIG. 6 is a schematic diagram of the crew terminal 3 displaying the dispatch request screen C. The dispatch request screen C shows on a map the specified location included in the dispatch request and the location of the taxi where the crew terminal 3 is deployed. The dispatch request screen C also accepts an operation from the crew to accept the dispatch request.

If the candidate vehicles do not accept the dispatch request, i.e., if the driver does not perform an operation to accept the dispatch request on the driver terminal 3 for a specified period of time, the selection unit 133 in the dispatch management device 1 excludes the candidate vehicles that did not accept the dispatch request and reselects candidate vehicles using the method shown in FIG. 5.

When the candidate vehicle accepts the dispatch request, the dispatch instruction unit 135 confirms the candidate vehicle that accepted the dispatch request as the dispatch vehicle and transmits a dispatch instruction to the dispatch vehicle indicating that the vehicle will be dispatched to the specified location at the specified date and time. The driver of the dispatch vehicle dispatches the vehicle according to the specified date and time and specified location indicated in the dispatch instruction received from the dispatch management device 1, and has the user board the vehicle.

The selection unit 133 may also select multiple candidate vehicles from among multiple dispatchable vehicles based on the relationship between the predicted arrival time and the specified date and time, and cause the request transmission unit 134 to transmit a dispatch request to each of the multiple candidate vehicles. The selection unit 133 may, for example, simultaneously transmit the dispatch request to taxis within a specified range based on the specified position. In this case, the dispatch instruction unit 135 determines, as the dispatch vehicle, one of the multiple candidate vehicles that has accepted the dispatch request.

Furthermore, before selecting a candidate vehicle, the selection unit 133 may determine whether or not a vehicle can be dispatched to the specified location at the specified date and time, and the notification unit 136 may notify the user of specified information when the selection unit 133 determines that a vehicle cannot be dispatched. To determine whether a vehicle can be dispatched to the specified location at the specified date and time, the selection unit 133 acquires weather forecast information and traffic prediction information from an external server, for example, at a time before the pick-up arrangement time at the specified date and time. For example, when the weather forecast information indicates bad weather or when the traffic prediction information indicates the occurrence of traffic congestion, the selection unit 133 determines that a vehicle cannot be dispatched to the specified location at the specified date and time.

The selection unit 133 may also receive information indicating the number of vacant taxis within a predetermined range based on the designated position from an external server at a time before the pick-up arrangement time on the specified date and time, and determine that a taxi cannot be dispatched to the specified location on the specified date and time if the number of vacant taxis is less than the number of dispatch requests. The selection unit 133 may also determine whether or not a taxi can be dispatched to the specified location on the specified date and time using the number of actual taxis scheduled to arrive within a predetermined range based on the designated position in addition to the number of vacant taxis within a predetermined range based on the designated position. In this case, the selection unit 133 may receive information indicating, for example, a taxi whose destination inputted into the car navigation system is within a predetermined range based on the designated position, or a taxi whose arrival point predicted from the departure point is within a predetermined range based on the designated position from an external server, and determine the taxi as a taxi scheduled to arrive within the predetermined range based on the designated position.

When the selection unit 133 determines that a vehicle cannot be dispatched, the notification unit 136 generates notification information notifying the user that a vehicle cannot be dispatched to the specified location at the specified date and time, and transmits the notification information to the user terminal 2. The user terminal 2 displays a notification screen including the notification information received from the vehicle dispatch management device 1 on the display unit.

Figure 7 is a schematic diagram of a user terminal 2 displaying a notification screen D. The notification screen D includes notification information that notifies the user that a vehicle cannot be dispatched to the specified location at the specified date and time. The notification screen D also accepts an operation from the user to select whether to continue the vehicle dispatch request or to cancel the vehicle dispatch request. The selection unit 133 selects a candidate vehicle when the user selects to continue the vehicle dispatch request, and does not select a candidate vehicle when the user selects to cancel the vehicle dispatch request. In this way, the vehicle dispatch management device 1 notifies the user that a vehicle may not be dispatched on time, and can switch between selecting a candidate vehicle or not according to the user's wishes, thereby reducing user dissatisfaction.

[Flowchart of vehicle allocation management method]
8 is a diagram showing a flowchart of an exemplary vehicle dispatch management method executed by the vehicle dispatch management device 1 according to the present embodiment. In the vehicle dispatch management device 1, the reception unit 131 receives a vehicle dispatch request for dispatching a vehicle to a specified date and time and a specified location from the user terminal 2 (S11). The calculation unit 132 calculates a vehicle dispatch success probability that a vehicle can be dispatched to the specified location at the specified date and time based on statistical information (S12). The calculation unit 132 also calculates an arrangement fee for the vehicle dispatch request according to a predicted situation in a predetermined range based on the specified location at the specified date and time. The calculation unit 132 also calculates a vehicle dispatch success probability and an arrangement fee for candidate dates and times before and after the specified date and time.

The reception unit 131 transmits information including the dispatch success probability and dispatch fee calculated by the calculation unit 132 to the user terminal 2. The reception unit 131 receives a selection of either a specified date and time or a candidate date and time in the user terminal 2 (S13). The reception unit 131 receives a dispatch request for dispatching a vehicle to a specified location at the selected specified date and time or candidate date and time as a confirmed dispatch request.

If it is not the time before the pickup arrangement time for the specified date and time (NO in S14), the selection unit 133 waits. If it is the time before the pickup arrangement time for the specified date and time (YES in S14), the selection unit 133 selects a candidate vehicle to which the dispatch request is to be sent based on the specified date and time and the specified location included in the dispatch request accepted by the acceptance unit 131 (S15).

The request sending unit 134 sends a dispatch request to dispatch the vehicle to the specified location to the driver terminal 3 installed in the candidate vehicle selected by the selection unit 133 (S16). If the candidate vehicle does not accept the dispatch request (NO in S17), the selection unit 133 excludes the candidate vehicle that did not accept the dispatch request and returns to step S15 to select a new candidate vehicle.

If the candidate vehicle accepts the dispatch request (YES in S17), the dispatch instruction unit 135 confirms the candidate vehicle that accepted the dispatch request as the dispatch vehicle, and transmits a dispatch instruction to the dispatch vehicle indicating that the vehicle will be dispatched to the specified location at the specified date and time (S18).

[Effects of the embodiment]
According to the vehicle dispatch management system of this embodiment, the vehicle dispatch management device 1 selects a candidate vehicle to be dispatched to the user from among vehicles available for dispatch around the specified location at a time before the specified date and time, and transmits a dispatch request. This allows the taxi driver to appropriately undertake dispatch to the user as the specified date and time approaches, eliminating the need to adjust taxi operation around the specified location or wait for a long time. Therefore, the vehicle dispatch management device 1 can dispatch a taxi to the specified date and time and location specified by the user while reducing the burden on the taxi driver.

Second Embodiment
In this embodiment, the vehicle dispatch management system accepts multiple vehicle dispatch requests from one user. The vehicle dispatch management system according to this embodiment has, for example, the configuration shown in Figures 1 and 2. Below, the differences from the first embodiment will be mainly described.

In order to receive multiple vehicle dispatch requests from a user, the user terminal 2 displays a vehicle dispatch request list screen on the display unit before displaying the vehicle dispatch request screen A illustrated in FIG. 3. FIGS. 9(a) and 9(b) are schematic diagrams of the user terminal 2 displaying the vehicle dispatch request list screen E. If the user has not yet made a vehicle dispatch request, the vehicle dispatch request list screen E includes a button E1 for making a new vehicle dispatch request.

When a user has already made one or more dispatch requests, the dispatch request list screen E includes a button E1 for making a new dispatch request, and dispatch request information E2. The dispatch request information E2 is information about each of the one or more dispatch requests accepted from the user by the acceptance unit 131 of the dispatch management device 1. The dispatch request information E2 includes, for example, the specified date and time, the dispatch fee, the specified location (starting point), and the destination.

When a user selects button E1 on the vehicle dispatch request list screen E, the user terminal 2 displays the vehicle dispatch request screen A illustrated in FIG. 3 on the display unit. The user terminal 2 transmits the information entered by the user on the vehicle dispatch request screen A to the vehicle dispatch management device 1 as a vehicle dispatch request. In the vehicle dispatch management device 1, the reception unit 131 receives a vehicle dispatch request including, for example, a specified date and time and a specified location from the user terminal 2. In this way, the reception unit 131 can receive multiple vehicle dispatch requests for dispatching a vehicle to a specified date and time and a specified location from the user by sequentially receiving the vehicle dispatch requests on the vehicle dispatch request list screen E and the vehicle dispatch request screen A displayed on the user terminal 2.

When accepting a second or subsequent dispatch request from a user, the reception unit 131 determines whether to accept a new dispatch request based on the relationship between the specified date and time of the already accepted dispatch request and the specified date and time of the new dispatch request. A second or subsequent dispatch request is a dispatch request made by a user when there are other dispatch requests remaining whose specified date and time have not yet arrived. A first dispatch request is a dispatch request made by a user when there are no other dispatch requests remaining whose specified date and time have not yet arrived.

For example, when the reception unit 131 receives a second dispatch request from a user after receiving a first dispatch request from the user, the reception unit 131 does not accept the second dispatch request when the specified date and time of the second dispatch request is included in an exclusion period based on the specified date and time of the first dispatch request, and accepts the second dispatch request when the specified date and time of the second dispatch request is not included in the exclusion period. The first dispatch request is, for example, one or more dispatch requests that have already been received from the user and for which dispatch has not yet been performed (i.e., the specified date and time has not yet arrived). In this way, the reception unit 131 does not accept a dispatch request when the specified dates and times of the multiple dispatch requests are close to each other, thereby preventing the user from unintentionally making multiple dispatch requests with specified dates and times that are close to each other, and suppressing a situation in which the labor of the taxi driver is wasted.

The exclusion period is a period during which the specified dates and times of multiple dispatch requests are not permitted to be included. The exclusion period is expressed as a predetermined time, for example, 30 minutes, 1 hour, or 1 day. The exclusion period may also be set by an administrator who manages the dispatch management device 1. In this case, the reception unit 131 accepts as the exclusion period a period specified on an information terminal such as a smartphone or tablet terminal used by the administrator. This allows the dispatch management device 1 to easily adjust the interval between the specified dates and times that can be accepted for multiple dispatch requests.

The notification unit 136 may notify the user terminal 2 of information indicating whether or not the specified date and time is included in the exclusion period while accepting the specification of the specified date and time at the user terminal 2. The acceptance unit 131, for example, acquires the specified date and time specified at the user terminal 2, and determines whether or not the specified date and time of the second vehicle dispatch request is included in the exclusion period based on the specified date and time of the first vehicle dispatch request, using the acquired specified date and time as the specified date and time of the second vehicle dispatch request.

When the specified date and time is included in the excluded period, the notification unit 136 transmits notification information indicating that the specified date and time is included in the excluded period to the user terminal 2. The user terminal 2 displays the notification information received from the vehicle dispatch management device 1 on the vehicle dispatch request screen A.

Figure 10 is a schematic diagram of a user terminal 2 displaying a vehicle dispatch request screen A. The vehicle dispatch request screen A includes notification information A3 in addition to the specified date and time field A2 illustrated in Figure 3. The notification information A3 includes, for example, a message indicating that the specified date and time is included in an excluded period. This allows the vehicle dispatch management device 1 to notify the user whether the specified date and time specified by the user is within the excluded period or not, and to prompt the user to specify another specified date and time.

The calculation unit 132 calculates the probability of successful dispatch and the dispatch fee in a manner similar to that of the first embodiment. The reception unit 131 transmits to the user terminal 2 information necessary for the user terminal 2 to display a dispatch request confirmation screen based on the probability of successful dispatch and the dispatch fee. Based on the information received from the dispatch management device 1, the user terminal 2 displays on the display unit a dispatch request confirmation screen for the user to confirm the dispatch request.

The reception unit 131 accepts, as a confirmed dispatch request, a dispatch request for dispatching a vehicle to a specified location specified on the dispatch request screen at the specified date and time or candidate date and time selected on the dispatch request confirmation screen. The confirmed dispatch request is displayed as dispatch request information E2 on the dispatch request list screen E illustrated in FIG. 9(b).

The selection unit 133 selects a vehicle to be instructed to be dispatched at a time before the specified date and time of each of the one or more dispatch requests. The method in which the selection unit 133 selects a vehicle based on one dispatch request is the same as in the first embodiment. For example, the selection unit 133 selects a candidate vehicle from among multiple dispatchable vehicles that are within a predetermined range based on the specified position of the dispatch request at a time before the pick-up arrangement time for the specified date and time of each of the one or more dispatch requests.

The request sending unit 134 sends a dispatch request to the candidate vehicle selected by the selection unit 133 to dispatch a vehicle to the specified location of one or more dispatch requests at the specified date and time of each of the dispatch requests. The method in which the request sending unit 134 sends a dispatch request based on one dispatch request is the same as in the first embodiment.

When the candidate vehicle accepts the dispatch request, the dispatch instruction unit 135 confirms the candidate vehicle that accepted the dispatch request as the dispatch vehicle and transmits a dispatch instruction to the dispatch vehicle indicating that the vehicle will be dispatched to the specified location at the specified date and time. The driver of the dispatch vehicle dispatches the vehicle according to the specified date and time and specified location indicated in the dispatch instruction received from the dispatch management device 1, and has the user board the vehicle.

After the dispatch instruction unit 135 transmits a dispatch instruction, the reception unit 131 receives from the driver terminal 3 dispatch record information indicating that a vehicle has been dispatched to the user, that the user is in the dispatched vehicle, the destination of the vehicle the user is in, and that the user has disembarked from the dispatched vehicle, and stores the information in the memory unit 12 in association with the user ID.

If a user does not board a vehicle that has been dispatched based on a predetermined number or percentage or more of the vehicle dispatch requests received from the user based on the vehicle dispatch record information stored in the memory unit 12, the reception unit 131 cancels the remaining vehicle dispatch requests among the multiple vehicle dispatch requests received from the user. The reception unit 131 cancels the vehicle dispatch request, for example, by deleting the vehicle dispatch request in the memory unit 12 or by associating information (such as a flag) indicating that the vehicle dispatch request has been canceled. In this way, the vehicle dispatch management device 1 can automatically cancel the vehicle dispatch request of a user who often does not board the vehicle despite making a vehicle dispatch request, thereby reducing the probability of disadvantage to the driver.

[Flowchart of vehicle allocation management method]
11 is a diagram showing a flowchart of a process of accepting a vehicle dispatch request in an exemplary vehicle dispatch management method executed by the vehicle dispatch management device 1 according to this modification. In the vehicle dispatch management device 1, the reception unit 131 receives a vehicle dispatch request for dispatching a vehicle to a specified date and time and to a specified location from the user terminal 2 (S21).

The reception unit 131 determines whether the dispatch request received from the user terminal 2 is a second or subsequent dispatch request (i.e., whether a dispatch request has already been received from the same user) (S22). If the reception unit 131 determines that the received dispatch request is the first dispatch request from the user (NO in S22), the dispatch management device 1 proceeds to step S25.

When the reception unit 131 determines that the received dispatch request is the second or subsequent dispatch request from the user (YES in S22), the reception unit 131 sets the dispatch request to be accepted as a second dispatch request, and determines whether the specified date and time of the second dispatch request is included in an exclusion period based on the specified date and time of the first dispatch request that has already been accepted. The first dispatch request is, for example, one or more dispatch requests that have already been accepted from the user and for which dispatch has not yet been performed (i.e., the specified date and time has not yet arrived).

If the reception unit 131 determines that the specified date and time of the second vehicle dispatch request is included in the excluded period (YES in step S23), the reception unit 131 does not accept the second vehicle dispatch request, and the notification unit 136 sends notification information indicating that the specified date and time is included in the excluded period to the user terminal 2 (step S24). The vehicle dispatch management device 1 returns to step S21. If the reception unit 131 determines that the specified date and time of the second vehicle dispatch request is not included in the excluded period (NO in step S23), the reception unit 131 accepts the second vehicle dispatch request, and the vehicle dispatch management device 1 proceeds to step S25.

The calculation unit 132 calculates the probability of successful dispatch of a vehicle to the specified location at the specified date and time based on the statistical information (S25). The calculation unit 132 also calculates the dispatch fee for the vehicle dispatch request according to the predicted situation in a predetermined range based on the specified location at the specified date and time. The calculation unit 132 also calculates the probability of successful dispatch and the dispatch fee for candidate dates and times before and after the specified date and time in the same way.

The reception unit 131 transmits information including the dispatch success probability and dispatch fee calculated by the calculation unit 132 to the user terminal 2. The reception unit 131 receives a selection of either the specified date and time or the candidate date and time in the user terminal 2 (S26). The reception unit 131 receives a dispatch request for dispatching a vehicle to a specified location at the selected specified date and time or the candidate date and time as a confirmed dispatch request.

If the vehicle dispatch management device 1 has not finished accepting vehicle dispatch requests from the user (NO in S27), the vehicle dispatch management device 1 repeats steps S21 to S27. If the vehicle dispatch management device 1 has finished accepting vehicle dispatch requests from the user (YES in S27), the vehicle dispatch management device 1 ends the process.

Figure 12 is a diagram showing a flowchart of a process for sending a dispatch request in an exemplary vehicle dispatch management method executed by the vehicle dispatch management device 1 according to this modified example. The process according to the flowchart in Figure 12 may be performed after the process according to the flowchart in Figure 11, or may be performed in parallel with the process according to the flowchart in Figure 11.

If the time has not yet come before the pick-up arrangement time for the specified date and time of one or more vehicle dispatch requests received from the user (NO in S31), the selection unit 133 waits. If the time has come before the pick-up arrangement time for any of the specified date and time of one or more vehicle dispatch requests received from the user (YES in S31), the selection unit 133 selects a candidate vehicle to which a vehicle dispatch request is to be sent based on the specified date and time and specified location included in the vehicle dispatch request (S32).

The request sending unit 134 sends a dispatch request to dispatch the vehicle to the specified location to the driver terminal 3 installed in the candidate vehicle selected by the selection unit 133 (S33). If the candidate vehicle does not accept the dispatch request (NO in S34), the selection unit 133 excludes the candidate vehicle that did not accept the dispatch request and returns to step S32 to select a new candidate vehicle.

If the candidate vehicle accepts the dispatch request (YES in S34), the dispatch instruction unit 135 confirms the candidate vehicle that accepted the dispatch request as the dispatch vehicle, and transmits a dispatch instruction to the dispatch vehicle indicating that the vehicle will be dispatched to the specified location at the specified date and time (S35). The driver of the dispatch vehicle dispatches the vehicle according to the specified date and time and the specified location indicated in the dispatch instruction received from the dispatch management device 1, and has the user board.

After the dispatch instruction unit 135 transmits a dispatch instruction, the reception unit 131 receives from the driver terminal 3 dispatch record information indicating that a vehicle has been dispatched to the user, that the user is in the dispatched vehicle, the destination of the vehicle the user is in, and that the user has disembarked from the dispatched vehicle, and stores the information in the memory unit 12 in association with the user ID.

If the user does not board a vehicle that was dispatched based on a predetermined number or percentage or more of the multiple dispatch requests received from the user based on the dispatch record information stored in the memory unit 12 (YES in S36), the reception unit 131 cancels the remaining dispatch requests from the multiple dispatch requests received from the user (S37); otherwise (NO in S36), the dispatch management device 1 proceeds to step S38. If dispatching of vehicles corresponding to all dispatch requests has been completed (YES in S38), the dispatch management device 1 ends the process; otherwise (NO in S38), it returns to step S31.

[Effects of the embodiment]
According to the vehicle dispatch management system of this embodiment, the vehicle dispatch management device 1 does not accept multiple vehicle dispatch requests with designated dates and times close to each other. This prevents the user from unintentionally making multiple vehicle dispatch requests with designated dates and times close to each other, making it less likely that the user will not show up at the designated location. Therefore, when accepting multiple vehicle dispatch requests from one user, the vehicle dispatch management device 1 can prevent a situation in which the taxi driver wastes effort in traveling to the designated location.

[First Modification]
If a vehicle is being dispatched to the user or the user is in a vehicle immediately before the specified date and time of the vehicle dispatch request received from the user, there is a high possibility that the user will not appear at the location specified in the vehicle dispatch request. In such a case, the vehicle dispatch management device 1 according to this modified example does not transmit a vehicle dispatch request.

The request sending unit 134 determines whether a vehicle has been dispatched to the user and whether the user is in the vehicle at a time before the specified date and time of each of one or more vehicle dispatch requests received from the user. The time at which the request sending unit 134 makes the determination is, for example, the time before the pick-up arrangement time for the specified date and time in the first embodiment. The time at which the request sending unit 134 makes the determination may also be a predetermined time before the specified date and time, such as 10 minutes or 30 minutes before. The request sending unit 134 determines whether a vehicle has been dispatched to the user and whether the user is in the vehicle, for example, based on the dispatch record information stored in the memory unit 12.

When the request sending unit 134 determines that a vehicle has been dispatched to the user or that the user is in the vehicle, it does not send a dispatch request for the dispatch request to the candidate vehicles. On the other hand, when the request sending unit 134 determines that a vehicle has not been dispatched to the user and that the user is not in the vehicle prior to the specified date and time of the dispatch request, it sends a dispatch request for the dispatch request to the candidate vehicles. This allows the dispatch management device 1 to avoid dispatching a vehicle to a user who is currently dispatched or in the vehicle, thereby preventing the taxi driver's efforts from being wasted.

In addition, when the request sending unit 134 determines, based on the dispatch record information stored in the memory unit 12, that the user is in the vehicle and that the relationship between the destination of the vehicle the user is in and the specified location of the dispatch request satisfies a predetermined condition, the request sending unit 134 may not send a dispatch request for the dispatch request. The relationship between the destination and the specified location is, for example, that the destination and the specified location are separated by a predetermined distance (10 km, 30 km, etc.) or more. If the destination of the vehicle the user is in is significantly separated from the specified location of the dispatch request, there is a high probability that the user will not appear at the specified location of the dispatch request. By not sending a dispatch request to a user whose vehicle destination is far from the specified location, the request sending unit 134 can prevent a situation in which the taxi driver's labor is wasted.

In addition, the request transmission unit 134 may determine whether to transmit a dispatch request for a dispatch request based on the relationship between the destination of the vehicle in which the user is riding and the specified location, as well as the relationship between the time when the user is scheduled to arrive at the destination and the specified date and time. As an example, the request transmission unit 134 acquires, via the communication unit 11, location information indicating the location of the vehicle identified as being in which the user is riding based on the dispatch record information stored in the storage unit 12. The request transmission unit 134 calculates the scheduled time of arrival at the destination based on the distance between the location of the vehicle in which the user is riding and the destination, and the traveling speed of the vehicle (e.g., average traveling speed). Furthermore, the request transmission unit 134 calculates the time required to travel from the destination to the specified location based on the distance between the destination and the specified location, and calculates the time when the user is estimated to be able to arrive at the specified location from the location of the vehicle via the destination in the shortest time. If the estimated time is later than the specified date and time of the dispatch request, the request transmission unit 134 does not transmit a dispatch request. By operating in this manner, the request transmission unit 134 can detect with high accuracy that the user will not arrive at the specified location by the specified date and time, thereby preventing the taxi driver's efforts from being wasted.

The request sending unit 134 may acquire, via the communication unit 11, location information indicating the location of a vehicle identified as being in the vehicle of the user based on the dispatch record information stored in the memory unit 12, and may not send a dispatch request if the distance between the location of the vehicle and the designated location satisfies a predetermined condition. As an example, the request sending unit 134 calculates the estimated time that the vehicle will be able to arrive at the designated location based on the distance between the location of the vehicle in which the user is riding and the designated location, and the vehicle's traveling speed (e.g., average traveling speed). If the estimated time is later than the date and time specified in the dispatch request, the request sending unit 134 does not send a dispatch request. By operating in this manner, the request sending unit 134 can detect with high accuracy that the user will not arrive at the designated location by the specified date and time, thereby preventing a situation in which the taxi driver's labor is wasted.

[Second Modification]
The vehicle dispatch management device 1 may receive a vehicle dispatch request for dispatching multiple vehicles simultaneously to a specified date and time and a specified location from one user. In this modified example, when a user desires to dispatch multiple vehicles simultaneously, the vehicle dispatch management device 1 receives multiple vehicle dispatch requests regardless of the relationship between the specified dates and times of the multiple vehicle dispatch requests.

The reception unit 131 receives, for example, from the user terminal 2, multiple vehicle dispatch requests corresponding to multiple vehicles to be dispatched simultaneously. In addition, the reception unit 131 may receive the number of vehicles to be dispatched together with one dispatch request, and when the number is two or more, the dispatch request may be accepted as multiple dispatch requests corresponding to the number of vehicles.

For example, when the specified date and time and the specified location of a first dispatch request are the same as the specified date and time and the specified location of a second dispatch request, the reception unit 131 accepts the second dispatch request even when the specified date and time of the second dispatch request is included in the excluded period. This allows the dispatch management device 1 to dispatch multiple vehicles when a user wishes to dispatch multiple vehicles simultaneously, even if the specified dates and times of the multiple dispatch requests are close to each other, thereby improving user convenience.

[Third Modification]
The vehicle dispatch management device 1 may receive a vehicle dispatch request from one user to dispatch a vehicle to another user. In this modified example, when one user desires to dispatch a vehicle to another user, the vehicle dispatch management device 1 receives a plurality of vehicle dispatch requests regardless of the relationship between the specified dates and times of the plurality of vehicle dispatch requests.

The reception unit 131 receives, for example, from the user terminal 2, a user ID for identifying the user to whom the vehicle is to be dispatched, along with a vehicle dispatch request, and stores the vehicle dispatch request in the storage unit 12 in association with the user ID of the user to whom the vehicle is to be dispatched. For example, when the reception unit 131 receives a first vehicle dispatch request from a first user to dispatch a vehicle to the first user, and then receives a second vehicle dispatch request from the first user to dispatch a vehicle to a second user different from the first user, the reception unit 131 accepts the second vehicle dispatch request even if the specified date and time of the second vehicle dispatch request is included in the exclusion period.

In a situation where a first user makes a vehicle dispatch request for a second user, the fact that the designated dates and times of multiple vehicle dispatch requests made by the first user are close to each other is unlikely to be a factor in the first user not appearing at the designated location. Therefore, when a first user requests a vehicle to be dispatched to a second user, the vehicle dispatch management device 1 of this modified example makes it possible to dispatch a vehicle even if the designated dates and times of the vehicle dispatch request for dispatching a vehicle to the first user and the vehicle dispatch request for dispatching a vehicle to the second user are close to each other, thereby improving user convenience.

Although the present invention has been described above using embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments, and various modifications and changes are possible within the scope of the gist of the invention. For example, all or part of the device can be configured by distributing or integrating functionally or physically in any unit. In addition, new embodiments resulting from any combination of multiple embodiments are also included in the embodiments of the present invention. The effect of the new embodiment resulting from the combination also has the effect of the original embodiment.

The processor of the vehicle dispatch management device 1 is responsible for each step (process) included in the vehicle dispatch management method shown in Figures 8, 11, and 12. That is, the processor of the vehicle dispatch management device 1 reads a program for executing the vehicle dispatch management method shown in Figures 8, 11, and 12 from the storage unit 12, and executes the program to execute the vehicle dispatch management method shown in Figures 8, 11, and 12. Some of the steps included in the vehicle dispatch management method shown in Figures 8, 11, and 12 may be omitted, the order of the steps may be changed, and multiple steps may be performed in parallel.

1 Vehicle allocation management device 13 Control unit 131 Reception unit 132 Calculation unit 133 Selection unit 134 Request transmission unit 135 Vehicle allocation instruction unit 136 Notification unit

Claims (11)

A reception unit that receives a plurality of vehicle dispatch requests for dispatching a vehicle to a specified date and time and to a specified location from a user;
a request transmission unit that transmits, to a vehicle, a vehicle dispatch request for dispatching a vehicle to the designated location of each of the plurality of vehicle dispatch requests at the designated date and time;
having
the reception unit, when receiving a second vehicle dispatch request from the user after receiving the first vehicle dispatch request from the user, does not accept the second vehicle dispatch request when the designated date and time of the second vehicle dispatch request is included in a predetermined period based on the designated date and time of the first vehicle dispatch request, and accepts the second vehicle dispatch request when the designated date and time of the second vehicle dispatch request is not included in the period;
Vehicle dispatch management device. The reception unit receives a setting of the period from an administrator who manages the vehicle dispatch management device.
The vehicle dispatch management device according to claim 1. a notification unit that notifies the user terminal of information indicating whether the specified date and time is included in the period while the specified date and time is being specified in the user terminal used by the user;
The vehicle dispatch management device according to claim 1 or 2. the reception unit, when the designated date and time and the designated location of the first vehicle dispatch request are the same as the designated date and time and the designated location of the second vehicle dispatch request, receives the second vehicle dispatch request even when the designated date and time of the second vehicle dispatch request is included in the period;
The vehicle dispatch management device according to any one of claims 1 to 3. when the reception unit receives a second vehicle dispatch request from the first user for dispatching a vehicle to a second user different from the first user after receiving a first vehicle dispatch request from the first user for dispatching a vehicle to the first user, the reception unit accepts the second vehicle dispatch request even when the specified date and time of the second vehicle dispatch request is included in the period;
The vehicle dispatch management device according to any one of claims 1 to 4. the request transmission unit does not transmit the vehicle dispatch request in response to the vehicle dispatch request if a vehicle has been dispatched to the user or the user is in the vehicle before the specified date and time of the vehicle dispatch request.
The vehicle dispatch management device according to any one of claims 1 to 5. the request transmission unit does not transmit the vehicle dispatch request in a case where the user is in the vehicle before the specified date and time of the vehicle dispatch request, and a relationship between at least one of a location or a destination of the vehicle in which the user is in the vehicle and the specified location satisfies a predetermined condition.
The vehicle dispatch management device according to claim 6. when the user does not board a vehicle that has been dispatched based on a predetermined number or a predetermined percentage or more of the vehicle dispatch requests received from the user, the reception unit cancels the remaining vehicle dispatch requests among the plurality of vehicle dispatch requests received from the user;
The vehicle dispatch management device according to any one of claims 1 to 7. a selection unit that selects a candidate vehicle from among a plurality of available vehicles that are within a predetermined range based on the designated position of each of the plurality of vehicle dispatch requests at a time before the designated date and time of each of the plurality of vehicle dispatch requests;
The request transmission unit transmits the vehicle dispatch request to the candidate vehicle selected by the selection unit.
The vehicle dispatch management device according to any one of claims 1 to 8. the selection unit predicts a predicted arrival time at which each of the plurality of available vehicles will arrive at the designated location, and selects the candidate vehicle from among the plurality of available vehicles based on a relationship between the predicted arrival time and the designated date and time.
The vehicle dispatch management device according to claim 9. The processor executes
receiving a first dispatch request from a user for dispatching a vehicle to a first specified date and time and to a first specified location;
a step of accepting a second vehicle dispatch request from the user for dispatching a vehicle to a second designated date and time and a second designated location after accepting the first vehicle dispatch request from the user, not accepting the second vehicle dispatch request when the second designated date and time is included in a predetermined period based on the first designated date and time, and accepting the second vehicle dispatch request when the second designated date and time is not included in the period;
transmitting a first dispatch request to a vehicle for dispatching the vehicle to the first specified location at the first specified date and time;
transmitting a second dispatch request to a vehicle for dispatching the vehicle to the second specified location at the second specified date and time;
A vehicle dispatch management method comprising the steps of:

Images