JP7728846B2 - Vehicle allocation processing device, vehicle allocation processing method, and vehicle allocation processing system - Google Patents

Description

Related to a vehicle dispatch processing device, vehicle dispatch processing method, or vehicle dispatch processing system that transmits information regarding vehicle dispatch.

It is common practice to dispatch a taxi according to a user's request. For example, Patent Document 1 describes a system in which, if a taxi reservation is not made, the user is notified that the taxi reservation could not be made.

Japanese Patent Application Laid-Open No. 2020-135281

Even if a user is notified that a shared car or taxi reservation cannot be made, if the user is unable to find an alternative, the user may be unable to use a taxi and may not be able to arrive at their destination by the desired time.

The present invention was made in consideration of the above circumstances, and aims to increase the probability that users will be able to board a vehicle at their desired time.

A vehicle dispatch processing device according to an aspect of the present invention includes a reception unit that receives a vehicle dispatch request along with a desired boarding location; a vehicle dispatch management unit that, when the reception unit receives the vehicle dispatch request, transmits a vehicle dispatch request to one or more pre-registered vehicles; and a transmission control unit that, when the vehicle dispatch management unit does not receive a vehicle dispatch approval for the vehicle dispatch request a predetermined time before a predetermined desired boarding time, transmits vehicle dispatch incomplete information indicating that the vehicle dispatch has not been completed to at least one of an administrator of the organization that manages the one or more vehicles and an administrator of the organization to which the user who sent the vehicle dispatch request belongs.

This invention has the effect of increasing the probability that a user will be able to board a vehicle at their desired boarding time.

1 is a diagram illustrating a configuration of a vehicle dispatch processing system according to an embodiment. FIG. 2 is a diagram illustrating the configuration of a user terminal. FIG. 2 is a diagram illustrating a configuration of a vehicle dispatch processing device. FIG. 3 is a diagram illustrating an example of user data stored in a storage unit. FIG. 4 is a diagram illustrating an example of organization-specific data stored in a storage unit. FIG. 4 is a diagram illustrating an example of area-specific data stored in a storage unit. FIG. 4 is a diagram illustrating an example of time-slot-specific data stored in a storage unit. FIG. 4 is a diagram illustrating an example of purpose-specific data stored in a storage unit. FIG. 10 is a diagram for explaining the timing of transmission of a vehicle dispatch request by the vehicle dispatch management unit. FIG. 10 is a diagram for explaining the timing of transmission of a vehicle dispatch request by the vehicle dispatch management unit. FIG. 10 is a diagram for explaining the timing of transmission of dispatch incomplete information by the communication control unit. 10 shows an example of dispatch request transmission history information. FIG. 2 is a diagram illustrating a configuration of a crew terminal. 10 is a flowchart showing the processing procedure for arranging a vehicle V by a vehicle dispatch processing device.

First Embodiment
[Outline of vehicle dispatch processing system S]
1 is a diagram showing the configuration of a vehicle dispatch processing system S according to this embodiment. The vehicle dispatch processing system S is a system for dispatching a vehicle V selected from a plurality of vehicles V in response to a request from a user U. The vehicle V is, for example, a shared vehicle that multiple users U can ride in together, but it may also be a vehicle that only one user U rides in. The vehicle dispatch processing system S includes a plurality of user terminals 1, a vehicle dispatch processing device 2, a crew terminal 3, an operator device 4, and a management device 5.

The user terminal 1 is, for example, a smartphone. The user terminal 1 communicates with the vehicle dispatch processing device 2 via a network. The user terminal 1, for example, accepts an operation from a user U requesting the dispatch of a vehicle V. Based on the accepted operation from the user U, the user terminal 1 transmits a dispatch request to the vehicle dispatch processing device 2 to request the dispatch of a vehicle V. The dispatch request includes a user ID (equivalent to user identification information) for identifying the user U, or an organization ID (equivalent to organization identification information) for identifying the organization to which the user U belongs.

The user terminal 1 transmits, along with the dispatch request, information indicating, for example, the desired boarding location where user U wishes to board vehicle V to the dispatch processing device 2. When the dispatch of vehicle V is reserved, the user terminal 1 receives a dispatch notification from the dispatch processing device 2 indicating that the dispatch of vehicle V has been reserved.

The vehicle dispatch processing device 2 is, for example, a server managed by a taxi company that manages the operation of the vehicle V, or a business that provides vehicle dispatch services. The vehicle dispatch processing device 2 communicates with the user terminal 1, the driver terminal 3, the business device 4, and the management device 5 via a network.

The vehicle dispatch processing device 2 accepts a vehicle dispatch request from the user terminal 1. Along with this vehicle dispatch request, the vehicle dispatch processing device 2 also accepts the desired boarding location where the user U wishes to board the vehicle V.

The vehicle dispatch processing device 2 transmits a vehicle dispatch request to the crew terminal 3 mounted on the vehicle V, requesting that the vehicle V head to the accepted desired boarding location by a specified desired boarding time. After transmitting the vehicle dispatch request to the crew terminal 3, if the vehicle dispatch processing device 2 receives a vehicle dispatch approval from the crew terminal 3 approving the vehicle dispatch request, it transmits a vehicle dispatch notification to the user terminal 1 indicating that the vehicle dispatch reservation has been completed. If the vehicle dispatch processing device 2 has not received a vehicle dispatch approval for the vehicle dispatch request a specified time before the desired boarding time, it transmits incomplete vehicle dispatch information indicating that the vehicle dispatch has not been completed to the management device 5 owned by the administrator of the organization that manages one or more vehicles V.

The crew terminal 3 is installed in the vehicle V and is an information terminal used by the driver of the vehicle V. The crew terminal 3 can send and receive data with the dispatch processing device 2 via wireless communication lines and a network.

The business operator device 4 is, for example, a computer used by an administrator belonging to an organization (e.g., a corporation). The business operator device 4 communicates with the vehicle dispatch processing device 2 via a network. For example, the business operator device 4 accepts operations from the administrator to set conditions when a user U belonging to this corporation reserves a vehicle V. For example, the business operator device 4 accepts operations to set the timing at which the vehicle dispatch processing device 2 sends incomplete vehicle dispatch information indicating that the vehicle dispatch has not been completed to an external device (e.g., a management device 5 used by the administrator of vehicle V). This timing is set, for example, as a predetermined time equivalent to the time difference between the timing at which the incomplete vehicle dispatch information is sent and the desired boarding time. The business operator device 4 transmits setting data indicating the accepted conditions, such as the predetermined time, to the vehicle dispatch processing device 2. The business operator device 4 receives notification data from the vehicle dispatch processing device 2 indicating that the vehicle dispatch reservation for user U belonging to this corporation has been completed.

The management device 5 is, for example, a computer owned by an administrator of an organization (e.g., a taxi company) that manages multiple vehicles V. The management device 5 communicates with the vehicle dispatch processing device 2 via a network. For example, the management device 5 receives incomplete vehicle dispatch information from the vehicle dispatch processing device 2, indicating that vehicle dispatch has not been completed. When the management device 5 receives the incomplete vehicle dispatch information, the administrator of the management device 5 can contact the driver and attempt to dispatch the vehicle.

If the vehicle dispatch processing device 2 has not received a vehicle dispatch approval for the vehicle dispatch request a predetermined time before the desired boarding time, it sends vehicle dispatch incomplete information to the management device 5 owned by the administrator of the organization that manages the vehicle V. Therefore, if there is no response from vehicle V to the vehicle dispatch request or if vehicle V refuses to be dispatched in response to the vehicle dispatch request, the vehicle dispatch processing device 2 can make it possible for the administrator to request one of the vehicles V to head to the desired boarding point. Therefore, the vehicle dispatch processing device 2 can increase the probability that user U will be able to board vehicle V at the desired boarding time.

[Configuration of user terminal 1]
2 is a diagram showing the configuration of the user terminal 1. The user terminal 1 is owned, for example, by a user who wishes to ride in a vehicle V. The user terminal 1 includes an operation unit 11, a communication unit 12, a display unit 13, a storage unit 14, and a control unit 15. The control unit 15 includes an operation reception unit 151, a communication control unit 152, and a display control unit 153.

The operation unit 11 is, for example, a touch panel. The operation unit 11 accepts operations from the user U. The operation unit 11 inputs information indicating the content of the accepted operation from the user U to the control unit 15. The communication unit 12 is a wireless communication module for communicating with the vehicle dispatch processing device 2. The display unit 13 is a display that displays various information. The display unit 13 is, for example, superimposed on the touch panel.

The memory unit 14 includes a storage medium such as ROM (Read Only Memory) or RAM (Random Access Memory). The memory unit 14 stores programs executed by the control unit 15.

The control unit 15 is, for example, a CPU (Central Processing Unit). The control unit 15 executes programs stored in the storage unit 14, thereby functioning as an operation reception unit 151, a communication control unit 152, and a display control unit 153.

The operation acceptance unit 151 accepts operations by the user U. For example, the operation acceptance unit 151 accepts input of a desired boarding point from which the user U wishes to dispatch vehicle V, from the user U who owns the user terminal 1. The operation acceptance unit 151 accepts input of a dispatch request to request dispatch of vehicle V. The dispatch request includes a user ID or a business operator ID. The operation acceptance unit 151 may also accept input of a desired boarding time at which vehicle V is desired to be dispatched. The operation acceptance unit 151 outputs the accepted desired boarding point and dispatch request to the communication control unit 152.

The communication control unit 152 communicates with the vehicle dispatch processing device 2 via the communication unit 12. For example, the communication control unit 152 transmits information indicating the desired boarding point to the vehicle dispatch processing device 2 along with the vehicle dispatch request accepted by the operation acceptance unit 151. The communication control unit 152 receives a vehicle dispatch notification from the vehicle dispatch processing device 2 indicating that the dispatch of vehicle V has been reserved.

[Configuration of vehicle dispatch processing device 2]
3 is a diagram showing the configuration of the vehicle dispatch processing device 2. The vehicle dispatch processing device 2 has a reception unit 231, a vehicle dispatch management unit 232, and a communication control unit 233.

The communication unit 21 is a communication interface for transmitting and receiving various data between the user terminal 1, the crew terminal 3, and the business operator device 4. The communication unit 21 receives, for example, a vehicle dispatch request from the user terminal 1 and transmits a vehicle dispatch notification to the user terminal 1. The communication unit 21 also transmits a vehicle dispatch request to the crew terminal 3 and receives a vehicle dispatch approval from the crew terminal 3. Furthermore, the communication unit 21 receives setting data from the business operator device 4 and transmits notification data to the business operator device 4.

The memory unit 22 has a storage medium such as ROM, RAM, or SSD (Solid State Drive). The memory unit 22 stores programs executed by the control unit 23. The memory unit 22 also stores data used by the control unit 23 to execute various processes related to vehicle dispatch. For example, the memory unit 22 stores the desired boarding time for user U to board vehicle V.

Figure 4 shows an example of user data stored in the memory unit 22. The user data shown in Figure 4 associates a user ID, organization ID, desired boarding date, desired boarding point, destination, and dispatched vehicle ID.

The user ID is information for identifying each of multiple users U who use the services provided by the vehicle dispatch processing device 2, and is, for example, the name of the user U or the membership number of the user U. The organization ID is information for identifying each of multiple organizations that use the services provided by the vehicle dispatch processing device 2, and includes, for example, a character string assigned by the administrator of the vehicle dispatch processing device 2.

The desired boarding date is the date and time entered by the user U when making a vehicle dispatch request on the user terminal 1. The desired boarding point is the desired boarding location entered by the user U when making a vehicle dispatch request on the user terminal 1. The destination is the desired destination entered by the user U when making a vehicle dispatch request on the user terminal 1. The dispatched vehicle ID is information for identifying the crew terminal 3 that sent a vehicle dispatch approval in response to the dispatch request sent by the vehicle dispatch processing device 2. The user data stored in the memory unit 22 is not limited to that shown in Figure 4, and may be any data that associates a user ID that identifies the user U with an organization ID that identifies the organization to which the user U belongs.

Figure 5 is a diagram showing an example of organization-specific data stored in the memory unit 22. In the organization-specific data shown in Figure 5, an organization ID is associated with a predetermined time. In the example in the top row of Figure 5, organization ID "G0001" is associated with a predetermined time of "30" minutes. The organization-specific data is referenced by the communication control unit 233, for example, to determine the timing for sending dispatch incomplete information.

Figure 6 is a diagram showing an example of area-specific data stored in the memory unit 22. In the area-specific data shown in Figure 6, areas are associated with predetermined times. In the example in the top row of Figure 6, the area "residential area" is associated with a predetermined time of "20" minutes. The area-specific data is referenced by the communication control unit 233, for example, to determine the timing for transmitting dispatch incomplete information.

Figure 7 is a diagram showing an example of time-slot-specific data stored in the memory unit 22. In the time-slot-specific data shown in Figure 7, time slots are associated with predetermined times. In the time-slot-specific data, the lower the probability of dispatching a vehicle, the longer the predetermined time is set. In the example in the top row of Figure 7, the time slot "12:00 - 5:00" is associated with a predetermined time of "40" minutes. The time-slot-specific data is referenced by the communication control unit 233, for example, to determine the timing of sending dispatch incomplete information.

Figure 8 is a diagram showing an example of purpose-specific data stored in the memory unit 22. In the purpose-specific data shown in Figure 8, the purpose of riding is associated with a predetermined time. In the purpose-specific data, the predetermined time corresponding to a riding purpose related to commuting to work or school, where there is a high probability that many users U will wish to ride in vehicle V during the same time period, is set longer than the predetermined time corresponding to a riding purpose not related to business. In the example in the top row of Figure 8, the predetermined time of "30" minutes is associated with the riding purpose of "commuting." The purpose-specific data is referenced by the communication control unit 233, for example, to determine the timing of sending incomplete vehicle dispatch information.

The control unit 23 in FIG. 3 is, for example, a CPU. The control unit 23 executes programs stored in the storage unit 22, thereby functioning as a reception unit 231, a vehicle dispatch management unit 232, and a communication control unit 233.

The reception unit 231 communicates with the user terminal 1 via the communication unit 21. The reception unit 231 receives a vehicle dispatch request along with a desired boarding point. The vehicle dispatch request includes a user ID for identifying the user U or an organization ID for identifying the organization to which the user U belongs. The reception unit 231 may further receive the purpose of the user U boarding the vehicle V. The reception unit 231 may receive a desired boarding time along with the vehicle dispatch request. The reception unit 231 may receive a desired arrival time zone along with the vehicle dispatch request. The desired arrival time zone is the range of time during which the user U wishes to arrive at the destination. The reception unit 231 outputs the received vehicle dispatch request, desired boarding point, and purpose of the ride to the vehicle dispatch management unit 232.

[Send a ride request]
The vehicle allocation management unit 232 communicates with the crew terminal 3 via the communication unit 21. When the reception unit 231 receives a vehicle allocation request, the vehicle allocation management unit 232 transmits a vehicle allocation request to one or more vehicles V registered in advance to the crew terminal 3.

First, the vehicle allocation management unit 232 receives vehicle position information indicating the position of each vehicle V from multiple pre-registered vehicles V. Based on the vehicle position indicated by the received vehicle position information, the vehicle allocation management unit 232 identifies, from the multiple pre-registered vehicles V, a vehicle V that can reach the desired boarding point accepted by the acceptance unit 231 by the desired boarding time stored in the memory unit 22.

Figures 9 and 10 are diagrams for explaining the timing of sending a vehicle dispatch request by the vehicle dispatch management unit 232. Figures 9(a), 9(b), 10(a), and 10(b) chronologically show vehicles V that can reach the desired boarding point (the position of the house in Figure 9(a)) accepted by the acceptance unit 231 by the desired boarding time stored in the memory unit 22. As shown in Figures 9(a), 9(b), 10(a), and 10(b), as the current time approaches the desired boarding time, the number of vehicles V that can reach the desired boarding point by the desired boarding time decreases.

If the vehicle dispatch management unit 232 sends a vehicle dispatch request to vehicle V at a relatively early timing, there is a high probability that vehicle V that approves this dispatch request will be able to reach the desired boarding point by the desired boarding time. However, the time vehicle V must wait until the desired boarding time after arriving at the desired boarding point will be longer, which will be a greater disadvantage to vehicle V. If the vehicle dispatch management unit 232 sends a vehicle dispatch request to vehicle V at a relatively late timing, the time vehicle V must wait until the desired boarding time after arriving at the desired boarding point will be shorter, but the risk that vehicle V will not be able to reach the desired boarding point by the desired boarding time will increase. For this reason, the vehicle dispatch management unit 232 starts sending vehicle dispatch requests to pre-registered vehicles V at a timing a predetermined reserve time before the desired boarding time (hereinafter also referred to as the vehicle dispatch request start time). The reserve time is, for example, several times the predetermined time.

The vehicle dispatch management unit 232 may specify the reserve time based on the area to which the desired boarding point accepted by the reception unit 231 belongs. For example, if the area to which the desired boarding point accepted by the reception unit 231 belongs is an urban area where vehicles V travel at a relatively high density, the vehicle dispatch management unit 232 specifies a longer reserve time than if the area to which the desired boarding point accepted by the reception unit 231 belongs is a residential area where vehicles V travel at a relatively low density.

In this way, the vehicle dispatch management unit 232 sends a vehicle dispatch request earlier in residential areas where vehicles V are traveling at a relatively low density, thereby increasing the probability that vehicles V will arrive at the desired boarding point by the desired boarding time. On the other hand, the vehicle dispatch management unit 232 sends a vehicle dispatch request later in urban areas where vehicles V are traveling at a relatively high density, thereby preventing vehicles V from having to wait long periods of time until the desired boarding time.

The vehicle dispatch management unit 232 sends a dispatch request to the crew terminal 3 of any one of multiple vehicles V that can reach the desired boarding point by the desired boarding time. As an example, the vehicle dispatch management unit 232 assigns priorities to multiple vehicles V that can reach the desired boarding point by the desired boarding time, in order of proximity to the desired boarding point. In this case, the closer a vehicle V is to the desired boarding point, the higher the priority assigned to that vehicle V. The vehicle dispatch management unit 232 sends dispatch requests to the crew terminals 3 of vehicles V in order of highest assigned priority. Each time the vehicle dispatch management unit 232 sends a dispatch request to the crew terminal 3 of a vehicle V, it may select the next vehicle V to send a dispatch request to.

After transmitting a dispatch request to the crew terminal 3 of vehicle V, the dispatch management unit 232 receives a dispatch approval from the crew terminal 3 of vehicle V, which approves the dispatch of vehicle V, or a dispatch refusal from the crew terminal 3 of vehicle V. The dispatch management unit 232 outputs the received dispatch approval or dispatch refusal to the communication control unit 233.

When the vehicle dispatch management unit 232 receives a dispatch refusal from the driver terminal 3 of a vehicle V, or when a predetermined response time has elapsed without receiving a dispatch approval from the vehicle V that sent the dispatch request, the vehicle dispatch management unit 232 sends a dispatch request to one of the remaining vehicles V that can reach the desired boarding point by the desired boarding time. The response time is set in advance by, for example, the driver of the vehicle V. The vehicle dispatch management unit 232 repeats the same process until it receives a dispatch approval from the driver terminal 3 of one of the vehicles V that sent the dispatch request.

When the vehicle dispatch management unit 232 receives a vehicle dispatch approval from the crew terminal 3 of any vehicle V that has sent a vehicle dispatch request, it accepts a vehicle dispatch request to have another user U ride in the confirmed vehicle V within the range in which the first user U can arrive at the destination within the desired arrival time slot. The desired arrival time slot is the range of time within which the first user U wishes to arrive at the destination.

The vehicle allocation management unit 232 determines whether the first user U would be able to arrive at the destination in the desired arrival time slot if the other user U who accepted the vehicle allocation request were to be allowed to ride with the first user U, and whether the other user U would be able to arrive at the destination in the desired arrival time slot. The vehicle allocation management unit 232 allows the other user U to ride with the vehicle V if the first user U would be able to arrive at the destination in the desired arrival time slot if the other user U who accepted the vehicle allocation request were to be allowed to ride with the first user U, and the other user U would be able to arrive at the destination in the desired arrival time slot. The vehicle allocation management unit 232 does not allow the other user U to ride with the vehicle V if the first user U would not be able to arrive at the destination in the desired arrival time slot if the other user U who accepted the vehicle allocation request were to be allowed to ride with the first user U, or if the other user U would not be able to arrive at the destination in the desired arrival time slot.

[Send incomplete vehicle dispatch information]
The communication control unit 233 communicates with the user terminal 1 via the communication unit 21. If the vehicle dispatch management unit 232 has not received a vehicle dispatch approval for a vehicle dispatch request at a predetermined time before a predetermined desired boarding time, the communication control unit 233 transmits vehicle dispatch incompletion information indicating that the vehicle dispatch has not been completed to the management device 5 of the administrator of the organization that manages one or more vehicles V.

The management device 5 to which the incomplete dispatch information is sent may be, for example, the management device 5 of the administrator of all taxi companies that are permitted to operate in the area where the desired boarding point received by the reception unit 231 is located, or the management device 5 of the administrator of taxi companies excluding private taxis that are permitted to operate in the area where the desired boarding point received by the reception unit 231 is located. The management device 5 to which the incomplete dispatch information is sent may be the management device 5 of the administrators of multiple taxi companies that meet predetermined conditions, such as having a number of vehicles V equal to or greater than a threshold.

The specified desired boarding time is, for example, a time stored in the memory unit 22. The specified desired boarding time may also be a time received by the reception unit 231 from the user terminal 1. The communication control unit 233 may send the incomplete vehicle dispatch information to the user terminal 1 of the user U who sent the dispatch request, or to a management device (not shown) of the administrator of the organization to which the user U who sent the dispatch request belongs, instead of the management device 5 of the administrator of the organization that manages the vehicle V. This management device may also be treated as the business operator device 4 (Figure 1).

Figure 11 is a diagram illustrating the timing of transmission of incomplete vehicle dispatch information by the communication control unit 233. The horizontal axis in Figure 11 represents time. After the vehicle dispatch management unit 232 begins identifying a vehicle V that can reach the desired boarding point by the desired boarding time, the vehicle dispatch management unit 232 begins transmitting a vehicle dispatch request at the vehicle dispatch request start time, which is a reserve time before the desired boarding time. The communication control unit 233 transmits incomplete vehicle dispatch information to the management device 5 at a time a predetermined time before the desired boarding time.

First, the communication control unit 233 identifies the predetermined time. More specifically, the communication control unit 233 reads from the storage unit 22 organization-specific data (Figure 5) that associates organization identification information for identifying the organization to which user U belongs with the predetermined time. The communication control unit 233 references the read organization-specific data to identify the predetermined time associated with the organization ID included in the vehicle dispatch request. If the vehicle dispatch request includes a user ID, the communication control unit 233 may reference the user data shown in Figure 4 to identify the organization ID associated with the user ID and identify the predetermined time corresponding to this organization ID.

The communication control unit 233 may specify the predetermined time based on the area to which the desired boarding point accepted by the acceptance unit 231 belongs. More specifically, the communication control unit 233 reads area-specific data (Figure 6) that associates areas with predetermined times from the storage unit 22. The communication control unit 233 may refer to the read area-specific data to specify the predetermined time associated with the area to which the desired boarding point accepted by the acceptance unit 231 belongs. As an example, if the area to which the desired boarding point accepted by the acceptance unit 231 belongs is a "residential area," the communication control unit 233 specifies "20" minutes, associated with this "residential area," as the predetermined time.

The communication control unit 233 may identify the density of vehicles V traveling in the area to which the desired boarding point accepted by the acceptance unit 231 belongs, and may identify the predetermined time based on the identified density. For example, the communication control unit 233 may identify a relatively short predetermined time if the identified density is higher than a threshold. On the other hand, the communication control unit 233 may identify a relatively long predetermined time if the identified density is equal to or lower than the threshold. The threshold is set, for example, by a management device 5 owned by an administrator of the organization that manages the vehicles V.

In this way, the communication control unit 233 can transmit incomplete vehicle dispatch data to the administrator of the organization that manages vehicle V at a relatively early timing in areas where the density of vehicle V traveling is relatively low, and can transmit incomplete vehicle dispatch data to the administrator of the organization that manages vehicle V at a relatively late timing in areas where the density of vehicle V traveling is relatively high. As a result, the communication control unit 233 can reduce the risk that vehicle V will not be able to be dispatched to the desired boarding point by the desired boarding time, while preventing the transmission of incomplete vehicle dispatch data to the administrator until vehicle V can be dispatched to the desired boarding point by the desired boarding time.

When the communication control unit 233 accepts a desired boarding time accepted by the acceptance unit 231, it may specify the predetermined time based on this desired boarding time. More specifically, the communication control unit 233 reads time-zone data (Figure 7) that associates time zones with predetermined times from the storage unit 22. The communication control unit 233 may refer to the read time-zone data to specify the predetermined time associated with the time zone to which the desired boarding time accepted by the acceptance unit 231 belongs. As an example, when the acceptance unit 231 accepts a desired boarding time of "4 o'clock," the communication control unit 233 specifies "40" minutes, which is associated with the time zone of "12:00 to 5:00" to which this desired boarding time of "4 o'clock" belongs, as the predetermined time.

In this way, the communication control unit 233 transmits the incomplete vehicle dispatch data to the administrator at a relatively early timing during time periods when the number of vehicles V traveling is relatively low, and transmits the incomplete vehicle dispatch data to the administrator at a relatively late timing during time periods when the number of vehicles V traveling is relatively high. As a result, the communication control unit 233 can reduce the risk that vehicle V will not be able to be dispatched to the desired boarding point by the desired boarding time, while preventing the transmission of incomplete vehicle dispatch data to the administrator until vehicle V can be dispatched to the desired boarding point by the desired boarding time.

When the reception unit 231 receives a purpose of riding along with a ride dispatch request, the communication control unit 233 may specify the predetermined time based on this purpose of riding. First, the communication control unit 233 reads purpose-specific data (Figure 8) that associates the purpose of riding with a predetermined time from the storage unit 22. The communication control unit 233 may refer to the read purpose-specific data to specify the predetermined time associated with the purpose of riding accepted by the acceptance unit 231. As an example, when the acceptance unit 231 receives the purpose of riding "commute," the communication control unit 233 specifies "30" minutes associated with this purpose of riding "commute" as the predetermined time.

In this way, when the communication control unit 233 receives a ride purpose such as "commuting to work" or "commuting to school," which is relatively likely to cause many users U to want to ride in vehicle V during the same time period as user U, it transmits the purpose relatively early to the administrator of the organization that manages vehicle V. On the other hand, when the communication control unit 233 receives a ride purpose such as "travel" or "shopping," which is relatively unlikely to cause many users U to want to ride in vehicle V during the same time period as user U, it transmits the purpose relatively late to the administrator of the organization that manages vehicle V. In this way, the communication control unit 233 can reduce the risk that vehicle V will not be able to be dispatched to the desired boarding point by the desired boarding time, while preventing the communication control unit 233 from sending incomplete vehicle dispatch data to the administrator until vehicle V can be dispatched to the desired boarding point by the desired boarding time.

[Transmission of information indicating the result of sending a vehicle dispatch request]
The communication control unit 233 may transmit, together with the incomplete vehicle dispatch information, transmission history information indicating the results of transmitting the vehicle dispatch request to the management device 5 of the administrator of the organization that manages one or more vehicles V or the management device of the administrator of the organization to which the user U belongs. For example, the communication control unit 233 transmits, to the management device 5, etc., transmission history information including information indicating whether a vehicle V that did not approve the transmitted vehicle dispatch request rejected the vehicle dispatch request or did not respond to the vehicle dispatch request. The communication control unit 233 may transmit, to the management device 5, etc., transmission history information including information for identifying a vehicle V that did not approve the vehicle dispatch request transmitted by the vehicle dispatch management unit 232.

Figure 12 shows an example of transmission history information for a vehicle dispatch request. The transmission history information shown in Figure 12 associates the vehicle ID, the time of the last transmission of the vehicle dispatch request, and the response content. The vehicle ID is information for identifying the crew terminal 3 installed in vehicle V. The time of the last transmission of the vehicle dispatch request indicates the time when the vehicle dispatch management unit 232 last transmitted a vehicle dispatch request. For example, in the example in the first row from the top of Figure 12, the vehicle dispatch management unit 232 last transmitted a vehicle dispatch request to vehicle V with vehicle ID "V001" at 4:00 PM, indicating that the vehicle dispatch management unit 232 received a vehicle dispatch refusal from vehicle V in response to the vehicle dispatch request. In the example in the second row from the top of Figure 12, the vehicle dispatch management unit 232 last transmitted a vehicle dispatch request to vehicle V with vehicle ID "V002" at 4:01 PM, indicating that the vehicle dispatch management unit 232 has not received a response to the vehicle dispatch request.

The transmission history information shown in Figure 12 includes vehicle IDs, so by referencing this transmission history information, the administrator can identify vehicles V that did not approve the dispatch request sent by the dispatch management unit 232. Therefore, if necessary, the administrator can again request these vehicles V to head to the desired boarding point by the desired boarding time.

The transmission history information shown in Figure 12 includes the response content, so by referring to the transmission history information, the administrator can determine whether a vehicle V that did not approve the dispatch request that was sent rejected the dispatch request or did not respond to the dispatch request. Therefore, the administrator can try measures such as requesting again, via a different means of communication, that a vehicle V that did not respond to the dispatch request head to the desired boarding point by the desired boarding time.

As described above, the communication control unit 233 transmits to the administrator information for identifying the vehicle V that did not approve the dispatch request sent by the dispatch management unit 232, or information indicating whether the vehicle V that did not approve the dispatch request rejected the dispatch request or did not respond to the dispatch request. Therefore, the administrator can refer to the received information and take over from the dispatch processing device 2 the process of requesting the vehicle V to head to the desired boarding point by the desired boarding time.

When a reservation is made for the dispatch of vehicle V, the communication control unit 233 transmits a dispatch notification to the user terminal 1 indicating that the dispatch of vehicle V has been reserved. When a reservation is made for the dispatch of vehicle V, the communication control unit 233 transmits notification data to the business operator device 4 indicating that the dispatch of vehicle V has been reserved.

[Exceptions to the timing of sending incomplete vehicle dispatch information]
When the vehicle dispatch management unit 232 identifies a vehicle V that can reach the desired boarding point accepted by the acceptance unit 231 by the desired boarding time, there may be no vehicle V that can reach the desired boarding point by the desired boarding time. In this case, a vehicle V that can reach the desired boarding point by the desired boarding time may appear again, but it is often difficult to predict whether such a vehicle V will appear again.

For this reason, the communication control unit 233 may transmit incomplete vehicle dispatch information at a time earlier than the time a predetermined time before the desired boarding time when there is no vehicle V that can reach the desired boarding point by the desired boarding time. In this way, the communication control unit 233 can request the administrator of the organization that manages the vehicle V to arrange for a vehicle V for user U to board at an earlier time when there is no vehicle V that can reach the desired boarding point by the desired boarding time.

If there are a relatively large number of vehicles V that can reach the desired boarding point by the desired boarding time at a point a predetermined time before the desired boarding time, there is a relatively high possibility that a vehicle dispatch approval will be received immediately, even if the vehicle dispatch management unit 232 has not received a vehicle dispatch approval at that time. Therefore, if the number of vehicles V that can reach the desired boarding point by the desired boarding time is equal to or greater than a predetermined number, the communication control unit 233 does not need to send vehicle dispatch incomplete information at a point a predetermined time before the desired boarding time, even if the vehicle dispatch management unit 232 has not received a vehicle dispatch approval.

The predetermined number of vehicles is determined, for example, according to the ratio of the number of dispatch approvals received from vehicles V to the number of dispatch requests sent to vehicles V. The smaller this ratio, the larger the value set as the predetermined number of vehicles. In this way, the communication control unit 233 delays the timing of sending dispatch incomplete information to the manager of vehicle V's operation when there are a relatively large number of vehicles V that can reach the desired boarding point by the desired boarding time at a point a predetermined time before the desired boarding time. Therefore, the communication control unit 233 can prevent sending dispatch incomplete data to the manager until vehicle V can be dispatched to the desired boarding point by the desired boarding time.

[Configuration of crew terminal 3]
13 is a diagram showing the configuration of the crew terminal 3. The crew terminal 3 includes an operation unit 31, a communication unit 32, a display unit 33, a storage unit 34, and a control unit 35.

The operation unit 31 is, for example, a touch panel superimposed on the display unit 33. The operation unit 31 accepts operations from the driver of the vehicle V. The operation unit 31 inputs information indicating the content of the accepted driver operation to the control unit 35.

The communication unit 32 is a wireless communication module for communicating with the vehicle dispatch processing device 2. The display unit 33 is a display that displays various information.

The memory unit 34 includes a storage medium such as ROM, RAM, or SSD. The memory unit 34 stores the programs executed by the control unit 35.

The control unit 35 is, for example, a CPU. The control unit 35 performs various functions by executing programs stored in the memory unit 34. The control unit 35 communicates with the vehicle dispatch processing device 2 via the communication unit 21. For example, the control unit 35 receives a vehicle dispatch request from the vehicle dispatch processing device 2 requesting that the vehicle V head to the boarding location by the desired boarding time.

After receiving a dispatch request, the control unit 35 accepts the driver's operation via the operation unit 31 to input whether or not to approve the received dispatch request. When the control unit 35 accepts a driver's operation approving the received dispatch request, it transmits a dispatch approval approving the dispatch request to the dispatch processing device 2. When the control unit 35 accepts a driver's operation indicating that the received dispatch request is not approved, it transmits a dispatch refusal indicating that the dispatch request is not approved to the dispatch processing device 2.

[Procedure for arranging vehicle V]
14 is a flowchart showing the processing procedure for arranging a vehicle V by the vehicle dispatch processing device 2. This processing procedure starts, for example, while the vehicle dispatch processing device 2 is communicating with the user terminal 1. First, the reception unit 231 receives a vehicle dispatch request along with a desired boarding point and a desired arrival time zone from the user terminal 1 (S101). The desired arrival time zone is the range of time during which the first user U wishes to arrive at the destination.

The vehicle dispatch management unit 232 identifies a vehicle V from among multiple pre-registered vehicles V that can reach the desired boarding point accepted by the reception unit 231 by the desired boarding time stored in the memory unit 22 (S102). The vehicle dispatch management unit 232 determines whether it is the vehicle dispatch request start time (S103). If it is the vehicle dispatch request start time (YES in S103), the vehicle dispatch management unit 232 transmits a vehicle dispatch request to one of the crew terminals 3 of vehicles V that can reach the desired boarding point accepted by the reception unit 231 by the desired boarding time (S104).

The vehicle dispatch management unit 232 determines whether or not a vehicle dispatch approval for the transmitted vehicle dispatch request has been received from the driver terminal 3 of vehicle V (S105). If a vehicle dispatch approval has not been received from the driver terminal 3 of vehicle V (NO in S105), the vehicle dispatch management unit 232 determines whether or not there is a next vehicle V that has not transmitted a vehicle dispatch request among the vehicles V that can reach the desired boarding point received by the reception unit 231 by the desired boarding time (S106).

If there is no next vehicle V for which a dispatch request has not been sent (NO in S106), the communication control unit 233 determines whether it is a predetermined time before the desired boarding time (S107). If it is a predetermined time before the desired boarding time (YES in S107), the communication control unit 233 transmits dispatch incomplete information indicating that dispatch has not been completed to the administrator of the organization that manages the vehicle V (S108), and ends the processing.

If the vehicle dispatch management unit 232 determines in S103 that it is not the dispatch request start time (NO in S103), it returns to the processing of S102. If the vehicle dispatch management unit 232 determines in S105 that a dispatch approval has been received from the driver terminal 3 of vehicle V (YES in S105), it selects another user U to ride with user U in this vehicle V (S109). The vehicle dispatch management unit 232 is in a state where a vehicle has been confirmed for user U (hereinafter also referred to as the first user) of the user terminal 1 that accepted the dispatch request immediately before executing the processing of S109. At this time, the vehicle dispatch management unit 232 accepts a dispatch request to have another user U ride in the confirmed vehicle V for dispatch, within a range in which the first user U can arrive at the destination within the desired arrival time slot, and within which users U who will ride in the same vehicle V as the first user U can arrive at the destination within the desired arrival time slot. The desired arrival time slot is the range of time in which the first user U wishes to arrive at the destination.

The vehicle allocation management unit 232 allows the other user U, who has accepted the vehicle allocation request, to ride in the vehicle V on the condition that the first user U can arrive at the destination within the desired arrival time if the other user U rides in the vehicle V, and that the other user U who rides in the same vehicle V as the first user U can arrive at the destination within the desired arrival time. The communication control unit 233 notifies the first user U and the other user U that a reservation has been made for the allocation of vehicle V (S110), and ends the processing.

If there is a next vehicle V for which a dispatch request has not been sent (YES in S106), the dispatch management unit 232 sends a dispatch request to the crew terminal 3 of the next vehicle V (S104) and proceeds to the determination in S105. If it is not a predetermined time before the desired boarding time (NO in S107), the communication control unit 233 returns to the processing in S102.

The dispatch request that the reception unit 231 receives from the user terminal 1 of the first user U may include information selecting whether the first user U desires individual transportation in vehicle V without other users U sharing in vehicle V, or whether the first user U is also able to share vehicle V with other users U. The dispatch management unit 232 may also always send individual transportation with the first user U in vehicle V, and not accept dispatch requests in which other users U wish to share vehicle V. If the dispatch management unit 232 does not receive a dispatch request in which other users U wish to share vehicle V, step S109 is not executed and the process proceeds to step S110.

Second Embodiment
In the first embodiment, an example has been described in which the vehicle dispatch management unit 232 accepts a vehicle dispatch request for another user U to share a confirmed vehicle V within a range in which the first user U can arrive at the destination within the desired arrival time slot. However, the present invention is not limited to this. For example, the vehicle dispatch management unit 232 may start transmitting a vehicle dispatch request to the crew terminal 3 after the user U selects which other user to share a ride with.

After accepting a vehicle dispatch request, desired boarding time, desired boarding point, desired arrival time zone, and destination from a first user U, the reception unit 231 similarly accepts vehicle dispatch requests, desired boarding time, desired boarding point, desired arrival time zone, and destination from multiple other users U.

First, the vehicle allocation management unit 232 selects the first user U as the user who will ride in the vehicle V. Next, the vehicle allocation management unit 232 selects other users U who will ride in the same vehicle V as the first user U from multiple other users U who have accepted vehicle allocation requests. At this time, the vehicle allocation management unit 232 selects other users U to ride with user U so that the first user U can arrive at their destination within their desired arrival time slot, and so that other users who wish to ride together can arrive at their destination within their desired arrival time slots.

For example, the vehicle dispatch management unit 232 provisionally determines another user U whose total distance from the desired boarding point received from the first user U to the desired boarding point received from the other user U and the distance from the destination received from the first user U to the destination received from the other user U is the smallest as the user who will ride in the same vehicle V as the first user. The vehicle dispatch management unit 232 identifies the travel route of the vehicle V and the timing at which the vehicle V will pass through each of the desired boarding point of the user provisionally determined as the user who will ride in the same vehicle V as the first user U (hereinafter referred to as the provisional ride-sharing user), the desired boarding point of the first user U, the destination of the first user, and the destination of the provisional ride-sharing user, when the vehicle V passes through each of these points.

In this case, the vehicle dispatch management unit 232 determines whether the first user U can arrive at the destination within their desired arrival time slot, and whether the provisional ridership user can arrive at the destination within their desired arrival time slot. If the vehicle dispatch management unit 232 determines that the first user U can arrive at the destination within their desired arrival time slot, and that the provisional ridership user can arrive at the destination within their desired arrival time slot, the vehicle dispatch management unit 232 ultimately selects the provisional ridership user as the user who will ride in the same vehicle V as the first user U. The vehicle dispatch management unit 232 similarly selects the second and subsequent users U who will ride in the same vehicle V as the first user U.

If the vehicle dispatch management unit 232 determines that the first user U cannot arrive at the destination within the desired arrival time slot, or that the provisional rideshare user cannot arrive at the destination within the desired arrival time slot, the vehicle dispatch management unit 232 does not select the provisional rideshare user as a user to ride in the same vehicle V as the first user U. At this time, the vehicle dispatch management unit 232 provisionally selects another provisional rideshare user from multiple other users U who have accepted vehicle dispatch requests, and repeats the same determination.

The vehicle allocation management unit 232 selects all other users U who will be riding in the same vehicle V as the first user U by the start time of the vehicle allocation request, and reserves the vehicle V for the first user U in the same manner as in the first embodiment. The communication control unit 233 notifies the first user U and all other users U who will be riding in the same vehicle V as the first user U that they have been selected as users to ride in vehicle V and that vehicle V has been reserved for allocation.

[Effects of the vehicle dispatch processing system S of the first and second embodiments]
According to the vehicle dispatch processing system S of this embodiment, if the communication control unit 233 has not received a vehicle dispatch approval for the vehicle dispatch request at a predetermined time before the desired boarding time, it transmits vehicle dispatch incomplete information to the administrator. In this way, the communication control unit 233 can make it possible for the administrator to request one of the vehicles V to head to the desired boarding point when there is no response from the vehicle V to the vehicle dispatch request or when the vehicle V refuses to dispatch the vehicle to the vehicle dispatch request. Therefore, the communication control unit 233 can increase the probability that the user U can board the vehicle V at the desired boarding time.

<Summary>
[General-purpose project]
One of the objects of the present invention is to increase the probability that a user can board a vehicle at the desired boarding time.

[Issues corresponding to Appendix 1]
One of the purposes of the present invention is to enable an administrator of an organization that manages one or more vehicles, or an administrator of an organization to which the user who sent the vehicle dispatch request belongs, to know that the vehicle dispatch has not been completed.

[Appendix 1]
The vehicle dispatch processing device of this embodiment comprises a reception unit that receives a vehicle dispatch request along with a desired boarding point, a vehicle dispatch management unit that, when the reception unit receives the vehicle dispatch request, sends a vehicle dispatch request to one or more pre-registered vehicles, and a transmission control unit that, when the vehicle dispatch management unit has not received a vehicle dispatch approval for the vehicle dispatch request at a predetermined time before a predetermined desired boarding time, sends vehicle dispatch incomplete information indicating that the vehicle dispatch has not been completed to at least one of an administrator of an organization that manages the one or more vehicles and an administrator of an organization to which the user who sent the vehicle dispatch request belongs.
According to the above-mentioned vehicle dispatch processing device, if a vehicle dispatch approval for a vehicle dispatch request is not received a predetermined time before the desired boarding time, information about incomplete vehicle dispatch is sent to at least one of the administrator of the organization that manages vehicle V and the administrator of the organization to which user U who sent the vehicle dispatch request belongs.Therefore, if there is no response from vehicle V to the vehicle dispatch request or if vehicle V refuses to be dispatched in response to the vehicle dispatch request, it becomes possible for the administrator to request the vehicle to head to the desired boarding point by the desired boarding time.

[Issues corresponding to Appendix 2]
One of the objects of the present invention is to set the timing for sending dispatch incomplete information to the administrator of the organization that manages the vehicle V for each organization to which the user belongs.
[Appendix 2]
The vehicle dispatch management device described in Appendix 1 further includes a memory unit that stores organization identification information for identifying the organization to which the user belongs in association with the specified time, and the transmission control unit identifies the specified time associated with the organization identification information included in the vehicle dispatch request by referring to the memory unit.
This allows the dispatch incomplete information to be sent to the administrator of the organization that manages the vehicle V at a timing that corresponds to the organization to which the user belongs.

[Issues corresponding to Appendix 3]
One of the purposes of the present invention is to identify the organization to which a user belongs.
[Appendix 3]
The vehicle dispatch management device described in Appendix 1 further includes a memory unit that stores user data that associates user identification information that identifies a user with organization identification information that identifies the organization to which the user belongs, and organization-specific data that associates the organization identification information with the specified time, and the transmission control unit identifies the organization identification information associated with the user identification information included in the vehicle dispatch request by referring to the user data stored in the memory unit, and identifies the specified time associated with the identified organization identification information by referring to the organization-specific data stored in the memory unit.
This allows the dispatch incomplete information to be sent to the administrator or the like at a timing corresponding to the organization to which the user belongs, without the user having to register information about the organization to which the user belongs.

[Issues corresponding to Supplementary Note 4]
One of the objects of the present invention is to enable a user to specify a desired boarding time.
[Appendix 4]
The vehicle dispatch management device described in any one of appendixes 1 to 3, wherein the reception unit receives the desired boarding time along with the vehicle dispatch request, and the transmission control unit identifies the specified time based on the desired boarding time received by the reception unit.
This allows the incomplete vehicle dispatch information to be sent to the administrator or the like at a timing corresponding to the desired boarding time specified by the user.

[Issues corresponding to Supplementary Note 5]
One of the objects of the present invention is to enable an administrator of an organization that manages vehicles to identify vehicles whose dispatch requests have not been approved.
[Appendix 5]
The vehicle dispatch management device described in any one of Appendices 1 to 3, wherein the transmission control unit transmits information for identifying vehicles that did not approve the dispatch request sent to at least one of an administrator of an organization that manages the one or more vehicles and an administrator of an organization to which the user belongs.
This allows the transmission control unit to identify vehicles whose dispatch requests have not been approved by an administrator or the like of the organization that manages the vehicles. Therefore, the transmission control unit allows the administrator or the like to take over the process of requesting the vehicle to head to the desired boarding point by the desired boarding time.

[Problem corresponding to Supplementary Note 6]
One of the purposes of the present invention is to enable an administrator of an organization that manages a vehicle V to understand whether the vehicle V has rejected a dispatch request or has not responded to a dispatch request.
[Appendix 6]
The vehicle dispatch management device described in any one of Appendices 1 to 3, wherein the transmission control unit transmits information indicating whether a vehicle that did not approve the dispatch request that was sent rejected the dispatch request or did not respond to the dispatch request to at least one of an administrator of an organization that manages the one or more vehicles and an administrator of an organization to which the user belongs.
This allows the transmission control unit to enable an administrator or the like of the organization that manages the vehicle V to know whether the vehicle V has rejected the dispatch request or has not responded to the dispatch request. Therefore, the transmission control unit allows the administrator or the like to take over the process of requesting the vehicle to head to the desired boarding point by the desired boarding time.

[Problem corresponding to Supplementary Note 7]
One of the objects of the present invention is to set the timing for transmitting incomplete vehicle dispatch information for each area.
[Appendix 7]
The vehicle dispatch management device according to any one of claims 1 to 3, wherein the transmission control unit identifies the specified time based on the area to which the desired boarding point accepted by the acceptance unit belongs.
This allows the transmission control unit to transmit the dispatch incomplete information at a timing according to the area to which the desired boarding point belongs.

[Problem corresponding to Supplementary Note 8]
One of the objects of the present invention is to set the timing for transmitting a dispatch request to a vehicle for each area.
[Appendix 8]
The vehicle dispatch management device described in any one of appendix 1 to 3, wherein the vehicle dispatch management unit identifies a reserve time based on the area to which the desired boarding point accepted by the acceptance unit belongs, and starts sending the vehicle dispatch request to a pre-registered vehicle at a timing that is the reserve time before the desired boarding time.
This allows the vehicle dispatch management unit to transmit the vehicle dispatch incomplete information at a timing according to the area to which the desired boarding point belongs.

[Problem corresponding to Supplementary Note 9]
One of the objects of the present invention is to accelerate the timing of transmitting incomplete vehicle dispatch information when there is no vehicle that can reach the desired boarding point by the desired boarding time.
[Appendix 9]
A vehicle dispatch management device described in any one of Appendices 1 to 3, wherein the transmission control unit transmits the vehicle dispatch incomplete information at a time earlier than the time that is the specified time before the desired boarding time if there is no vehicle that can reach the desired boarding point by the desired boarding time.
This allows the transmission control unit to transmit the incomplete vehicle dispatch information at an earlier timing when there is no vehicle that can reach the desired boarding point by the desired boarding time.

[Problem corresponding to Supplementary Note 10]
One of the objects of the present invention is to delay the timing of transmitting incomplete vehicle dispatch information when there are a relatively large number of vehicles that can reach the desired boarding point by the desired boarding time.
[Supplementary Note 10]
A vehicle dispatch management device as described in any one of Appendices 1 to 3, wherein the transmission control unit does not transmit the vehicle dispatch incomplete information at a point before the desired boarding time by the specified time even if the vehicle dispatch management unit has not received the vehicle dispatch approval if the number of vehicles among the multiple vehicles that can reach the desired boarding point by the desired boarding time is equal to or greater than a specified number.
This allows the transmission control unit to transmit the incomplete vehicle dispatch information at a later timing when there are relatively many vehicles that can reach the desired boarding point by the desired boarding time.

[Problem corresponding to Supplementary Note 11]
One of the objects of the present invention is to set the timing for transmitting incomplete vehicle dispatch information depending on the purpose of the ride.
[Appendix 11]
the reception unit receives the purpose of the ride along with the vehicle dispatch request,
The vehicle dispatch management device according to any one of claims 1 to 3, wherein the transmission control unit specifies the predetermined time based on the purpose of the ride received together with the vehicle dispatch request.
This allows the transmission control unit to transmit the dispatch incomplete information at a timing appropriate to the purpose of the ride.

[Problem corresponding to Supplementary Note 12]
One of the purposes of the present invention is to enable an administrator of an organization that manages one or more vehicles, or an administrator of an organization to which a user who sent a vehicle dispatch request belongs, to know that the vehicle dispatch has not been completed.
[Appendix 12]
A vehicle dispatch management method comprising the steps of: receiving a vehicle dispatch request together with a desired boarding point, executed by a computer; when the vehicle dispatch request is received, sending a vehicle dispatch request to one or more pre-registered vehicles; and when vehicle dispatch approval for the vehicle dispatch request is not received a predetermined time before a predetermined desired boarding time, sending information indicating that the vehicle dispatch has not been completed to at least one of an administrator of an organization that manages the one or more vehicles and an administrator of an organization to which the user belongs.
According to the above-mentioned vehicle dispatch processing method, if a vehicle dispatch approval for a vehicle dispatch request is not received a predetermined time before the desired boarding time, information about incomplete vehicle dispatch is sent to at least one of the administrator of the organization that manages vehicle V and the administrator of the organization to which user U who sent the vehicle dispatch request belongs.Therefore, if there is no response from vehicle V to the vehicle dispatch request or if vehicle V refuses to be dispatched in response to the vehicle dispatch request, it becomes possible for the administrator to request the vehicle to head to the desired boarding point by the desired boarding time.

[Problem corresponding to Supplementary Note 13]
One of the objects of the present invention is to enable an administrator of an organization that manages one or more vehicles, or an administrator of an organization to which the user who sent the vehicle dispatch request belongs, to know that the vehicle dispatch has not been completed.
[Appendix 13]
A vehicle dispatch processing system including a vehicle dispatch processing device for dispatching a vehicle and a user terminal, wherein the user terminal has an operation reception unit that receives a user's operation to input a desired boarding point from which the user wishes to dispatch the vehicle, and a transmission control unit that transmits the desired boarding point together with a dispatch request for dispatching a vehicle to the vehicle dispatch processing device,
The vehicle dispatch processing device includes a reception unit that receives the vehicle dispatch request from the user terminal along with the desired boarding point, a vehicle dispatch management unit that, when the reception unit receives the vehicle dispatch request, sends a vehicle dispatch request to one or more pre-registered vehicles, and a transmission control unit that, when the vehicle dispatch management unit has not received a vehicle dispatch approval for the vehicle dispatch request at a predetermined time before a predetermined desired boarding time, sends vehicle dispatch incomplete information indicating that the vehicle dispatch has not been completed to at least one of an administrator of an organization that manages the one or more vehicles and an administrator of an organization to which the user who sent the vehicle dispatch request belongs.
According to the above-mentioned vehicle dispatch processing system, if a vehicle dispatch approval for a vehicle dispatch request is not received a predetermined time before the desired boarding time, information about incomplete vehicle dispatch is sent to at least one of the administrator of the organization that manages vehicle V and the administrator of the organization to which user U who sent the vehicle dispatch request belongs.Therefore, if there is no response from vehicle V to the vehicle dispatch request or if vehicle V refuses to be dispatched in response to the vehicle dispatch request, it becomes possible for the administrator to request the vehicle to head to the desired boarding point by the desired boarding time.

The present invention has been described above using embodiments, but the technical scope of the present invention is not limited to the scope described in the above embodiments, and various modifications and alterations are possible within the spirit of the invention. For example, all or part of the device can be configured by functionally or physically distributing or integrating any unit. Furthermore, new embodiments resulting from any combination of multiple embodiments are also included in the embodiments of the present invention. The effects of new embodiments resulting from the combination will also have the effects of the original embodiments.

1 User terminal 2 Vehicle dispatch processing device 3 Crew terminal 4 Business operator device 5 Management device 11 Operation unit 12 Communication unit 13 Display unit 14 Memory unit 15 Control unit 21 Communication unit 22 Memory unit 23 Control unit 31 Operation unit 32 Communication unit 33 Display unit 34 Memory unit 35 Control unit 151 Operation reception unit 152 Communication control unit 153 Display control unit 231 Reception unit 232 Vehicle dispatch management unit 233 Communication control unit ID Dispatched vehicle S Vehicle dispatch processing system U User V Vehicle

Claims (13)

a reception unit that receives a dispatch request along with a desired boarding location;
a vehicle allocation management unit that transmits a vehicle allocation request to one or more pre-registered vehicles when the reception unit receives the vehicle allocation request;
a transmission control unit that, when the vehicle dispatch management unit has not received a vehicle dispatch approval for the vehicle dispatch request at a time a predetermined time before a predetermined desired boarding time, transmits vehicle dispatch incompletion information indicating that the vehicle dispatch has not been completed to at least one of an administrator of an organization that manages the one or more vehicles and an administrator of an organization to which the user who transmitted the vehicle dispatch request belongs;
A vehicle dispatch processing device comprising: a storage unit that stores organization identification information for identifying an organization to which the user belongs in association with the predetermined time;
the transmission control unit refers to the storage unit to identify the predetermined time associated with the organization identification information included in the vehicle dispatch request.
The vehicle dispatch processing device according to claim 1 . The system further includes a storage unit configured to store user data in which user identification information for identifying a user is associated with organization identification information for identifying an organization to which the user belongs, and organization-specific data in which the organization identification information is associated with the predetermined time,
the transmission control unit identifies the organization identification information associated with the user identification information included in the vehicle dispatch request by referring to the user data stored in the storage unit, and identifies the predetermined time associated with the identified organization identification information by referring to the organization-specific data stored in the storage unit;
The vehicle dispatch processing device according to claim 1 . the reception unit receives the desired boarding time together with the vehicle dispatch request,
the transmission control unit specifies the predetermined time based on the desired boarding time accepted by the acceptance unit.
The vehicle dispatch processing device according to any one of claims 1 to 3. The transmission control unit transmits information for identifying vehicles that did not approve the transmitted vehicle dispatch request to at least one of an administrator of an organization that manages the one or more vehicles and an administrator of an organization to which the user belongs.
The vehicle dispatch processing device according to any one of claims 1 to 3. The transmission control unit transmits information indicating whether a vehicle that did not approve the transmitted vehicle allocation request rejected the vehicle allocation request or did not respond to the vehicle allocation request to at least one of an administrator of an organization that manages the one or more vehicles and an administrator of an organization to which the user belongs.
The vehicle dispatch processing device according to any one of claims 1 to 3. the transmission control unit specifies the predetermined time based on an area to which the desired boarding point accepted by the acceptance unit belongs.
The vehicle dispatch processing device according to any one of claims 1 to 3. the vehicle dispatch management unit specifies a reserve time based on an area to which the desired boarding point accepted by the acceptance unit belongs, and starts transmitting the vehicle dispatch request to a pre-registered vehicle at a timing that is the reserve time before the desired boarding time;
The vehicle dispatch processing device according to any one of claims 1 to 3. the transmission control unit transmits the vehicle dispatch incompletion information at a time earlier than the time that is the predetermined time before the desired boarding time when there is no vehicle that can reach the desired boarding point by the desired boarding time.
The vehicle dispatch processing device according to any one of claims 1 to 3. when the number of vehicles that can reach the desired boarding point by the desired boarding time is equal to or greater than a predetermined number among the plurality of vehicles, the transmission control unit does not transmit the vehicle dispatch incompletion information at a time before the desired boarding time, even if the vehicle dispatch management unit has not received the vehicle dispatch approval;
The vehicle dispatch processing device according to any one of claims 1 to 3. the reception unit receives the purpose of the ride along with the vehicle dispatch request,
the transmission control unit specifies the predetermined time based on the purpose of the ride received together with the vehicle dispatch request.
The vehicle dispatch processing device according to any one of claims 1 to 3. The computer executes
accepting a request for a ride along with a desired pickup location;
transmitting a vehicle allocation request to one or more pre-registered vehicles when the vehicle allocation request is received;
If a vehicle dispatch approval for the vehicle dispatch request has not been received at a time before a predetermined desired boarding time, sending information indicating that the vehicle dispatch has not been completed to at least one of an administrator of an organization that manages the one or more vehicles and an administrator of an organization to which the user belongs;
A vehicle dispatch processing method comprising: A vehicle dispatch processing system including a vehicle dispatch processing device for dispatching vehicles and a user terminal,
The user terminal
an operation receiving unit that receives an operation by a user to input a desired boarding point where the user wishes to have the vehicle dispatched;
a transmission control unit that transmits the desired boarding point to the vehicle dispatch processing device together with a vehicle dispatch request for dispatching a vehicle,
The vehicle dispatch processing device includes:
a reception unit that receives the vehicle dispatch request together with the desired boarding point from the user terminal;
a vehicle allocation management unit that transmits a vehicle allocation request to one or more pre-registered vehicles when the reception unit receives the vehicle allocation request;
a transmission control unit that, when the vehicle dispatch management unit has not received a vehicle dispatch approval for the vehicle dispatch request at a time a predetermined time before a predetermined desired boarding time, transmits vehicle dispatch incompletion information indicating that the vehicle dispatch has not been completed to at least one of an administrator of an organization that manages the one or more vehicles and an administrator of an organization to which the user who transmitted the vehicle dispatch request belongs,
Vehicle dispatch processing system.