Vehicle allocation support system

Abstract

The present application provides a vehicle assignment support system that appropriately deals with even in the case of a delayed arrival of a registered vehicle. In the present application, the controller determines whether there is another vehicle assignment plan affected by the delay, i.e., an affected object plan, in the case where the communication device receives a delay notification from the registered vehicle executing the vehicle assignment plan, cancels the affected object plan in the case where it is determined that there is the affected object plan, and performs a recalculation process on a reservation request corresponding to the affected object plan as a new reservation request, i.e., a re-reservation request. In the recalculation process, as a simulation for allocating the re-reservation request, a process of changing a scheduled time of arrival within a range of a permissible arrival time width for one or more transit points in another vehicle assignment plan is included.

Description

Technical Field

[0001] This invention relates to a vehicle support system. Background Technology

[0002] In recent years, computer systems have been developed that can create vehicle allocation plans for registered vehicles based on requests such as human movement or goods delivery. For example, Japanese Patent No. 7511080 discloses a system that takes into account vehicle leeway and can create a vehicle allocation plan that can effectively fulfill requests.

[0003] Patent Document 1: Japanese Patent No. 7511080 Summary of the Invention

[0004] However, there is room for improvement in the above system regarding how to handle situations where the arrival of actually registered vehicles is delayed in accordance with the plan, or where delays are possible. The object of the present invention is to provide a vehicle allocation support system that can cope even in the event of a delayed arrival of a registered vehicle.

[0005] The vehicle allocation support system of the present invention includes: a communication device for receiving reservation requests containing information relating to a plurality of transit points for which a job is to be performed and a desired arrival time for at least one of the transit points; and a controller for managing a plurality of registered vehicles and setting a vehicle allocation plan for the registered vehicles based on the reservation requests received by the communication device. One vehicle allocation plan is set for each reservation request. For each transit point in the vehicle allocation plan, a predetermined arrival time for the transit point and an allowable arrival time width, ranging from the earliest allowed time to the latest allowed time, are set for the allowed arrival time at the transit point. When the communication device receives a delay notification from a registered vehicle executing the vehicle allocation plan, indicating that the estimated arrival time or actual arrival time of the transit point is later than the latest allowed time of the transit point and containing information about the estimated arrival time or the arrival time, the controller determines whether there are other vehicle allocation plans, i.e., affected plans, that are affected by the delay of the vehicle allocation plan corresponding to the delay notification. If the controller determines that the affected plan exists, it cancels the affected plan and recalculates the reservation request corresponding to the affected plan as a new reservation request. In the recalculation process, as a simulation for allocating the re-reservation request, it includes processing the change of the arrival time of one or more of the other vehicle allocation plans' transit points within the allowed arrival time width.

[0006] Invention Effects

[0007] According to the present invention, in cases where a delay is presumed to have occurred in the vehicle allocation plan or where a delay has actually occurred, the affected vehicle allocation plan, i.e., the affected plan, is cancelled and recalculated as a new reservation request (re-reservation request). In the recalculation process, since the arrival time is adjusted within the allowable arrival time width, the possibility of allocating the re-reservation request within the allowable range increases. According to the present invention, even in cases of delayed arrival of registered vehicles, this can be addressed. Attached Figure Description

[0008] Figure 1 This is a structural diagram of the vehicle support system in this embodiment.

[0009] Figure 2 This is a flowchart illustrating the recalculation process of this embodiment.

[0010] Figure 3 This is a conceptual diagram used to illustrate the vehicle allocation plan of this embodiment.

[0011] Figure 4 This is a conceptual diagram used to illustrate the recalculation process of this embodiment. Detailed Implementation

[0012] Hereinafter, a vehicle matching support system 1, as an embodiment of the present invention, will be described in detail with reference to the accompanying drawings, as a way to carry out the present invention. Furthermore, in addition to the embodiments described below, the present invention can be implemented in various ways with different modifications and improvements based on the knowledge of those skilled in the art.

[0013] like Figure 1 As shown, the vehicle matching support system 1 includes a communication device 2, a controller 3, a user terminal 4, and a vehicle terminal 5. The communication device 2 is, for example, a wireless or wired communication device capable of connecting to a network such as the Internet. The communication device 2 performs the communication functions of the controller 3, sending received information to the controller 3 and transmitting information according to transmission instructions from the controller 3. The communication device 2 is configured to receive reservation requests from the user terminal 4.

[0014] Reservation requests can be of two types, for example, passenger transport reservations and delivery reservations for goods. Passenger transport reservations, for example, include information about the passenger's boarding and alighting locations and their desired (or feasible) times. Delivery reservations, for example, include information about the goods' receiving and delivery locations and their desired (or feasible) times. Thus, a reservation request contains information about the location and time of execution for a pair of operations (boarding and alighting, receiving and delivery). The execution time information included in the reservation request may only be for one time. In this case, the controller 3 sets another time.

[0015] Users can send their desired reservation requests (ride reservations or delivery reservations) from their user terminal 4 to the communication device 2. User terminal 4 is a communication terminal capable of communicating with and displaying information on the communication device 2, such as a smartphone or tablet. User terminal 4 can, for example, obtain its location information via GPS and send it to the communication device 2. Users can, for example, select their desired time from the time range displayed on user terminal 4.

[0016] Controller 3 consists of a computer with one or more processors and one or more memory units. Communication device 2 can be configured inside controller 3. Controller 3 determines the vehicle allocation plan based on the reservation requests received by communication device 2. Controller 3 can also be considered a server. Controller 3 periodically exchanges information with user terminal 4 and vehicle terminal 5.

[0017] As described above, a ride reservation request includes information on the pick-up location, drop-off location, desired pick-up time, and desired drop-off time. The pick-up location can be the location information of user terminal 4. A delivery reservation request includes information on the location for receiving goods (e.g., a store), the delivery destination, the specified available pick-up time, and the desired delivery time. For example, based on rules set in controller 3 or information obtained from stores, the available pick-up time information displayed on user terminal 4 is updated. Multiple vehicles are registered in controller 3.

[0018] Vehicle terminal 5 is a communication terminal capable of communicating with controller 3 and displaying information, such as a smartphone, tablet, or device mounted on the vehicle. Vehicle terminal 5 receives the vehicle allocation plan for the corresponding registered vehicle from controller 3 and displays the plan on the screen. The driver of the registered vehicle obtains the vehicle allocation plan information from vehicle terminal 5. Controller 3 stores the locations where operations occur (vehicle boarding / alighting, cargo handover, etc.) as "via locations (or operation locations)".

[0019] The vehicle terminal 5 displays, for example, the transit points, the desired arrival time at each transit point (and / or the allowed arrival time width described later), the operational details for each transit point (number of passengers, number of passengers alighting, user information, type and quantity of goods received, type and quantity of goods delivered, etc.), and recommended routes. The vehicle terminal 5 can, for example, obtain its current location information through its own GPS function or by sharing information with the registered vehicle, and send it to the communication device 2. The vehicle terminal 5 also sends its current location information (corresponding to the location information of the registered vehicle), the remaining driving range, and the charging status (if the registered vehicle is an electric vehicle) shared with the registered vehicle to the communication device 2.

[0020] (Recalculation)

[0021] In the vehicle allocation support system 1, one vehicle allocation plan is created for each reservation request. The vehicle allocation plan for each reservation request includes at least the scheduled arrival time at the pick-up location and the scheduled arrival time at the drop-off location (described later, the scheduled times have an allowed time width). The controller 3 sets multiple vehicle allocation plans for multiple reservation requests, so that each reservation request corresponds to one vehicle allocation plan.

[0022] In the vehicle allocation plan, an "allowed arrival time width" is set for each transit point. For example, if the desired departure time in the reservation request is 3 PM, the vehicle allocation plan sets the scheduled arrival time at the departure location to 3 PM, and the allowed arrival time width is set to, for example, 2:50 PM to 3:30 PM based on the desired departure time and the vehicle's actual availability (feasibility). In this case, for example, the user terminal 4 and vehicle terminal 5 display the scheduled arrival time as 3 PM and the allowed arrival time width as 2:50 PM to 3:30 PM. Thus, a scheduled arrival time and an allowed arrival time width are set for each transit point in the vehicle allocation plan. The scheduled arrival time is set within the allowed arrival time width. Hereinafter, the earliest time within the allowed arrival time width will be referred to as the "earliest allowed time," and the latest time will be referred to as the "latest allowed time."

[0023] When communication device 2 receives a delay notification indicating that the estimated arrival time or actual arrival time of a currently traveling registered vehicle's transit point is later than the latest allowed time, controller 3 performs recalculation processing. The delay notification may be sent, for example, from vehicle terminal 5. Vehicle terminal 5 periodically estimates the time of arrival of the registered vehicle at the next transit point, or obtains estimated arrival time information through information sharing with the registered vehicle.

[0024] For example, if it is determined that the estimated arrival time of a transit point is later than the latest allowed time due to traffic congestion or an accident, vehicle terminal 5 will send a delay notification including the estimated arrival time to communication device 2. Vehicle terminal 5 can periodically send the estimated arrival time of the transit point to the current destination. Vehicle terminal 5 obtains the estimated arrival time information from the vehicle's navigation system or from a map application within vehicle terminal 5. For example, vehicle terminal 5 monitors the estimated arrival time, and if the estimated arrival time is later than the latest allowed time by a specified time (specified time ≥ 0), it sends a delay notification. When the estimated arrival time is updated, vehicle terminal 5 sends this information to communication device 2. Furthermore, when controller 3 determines whether there is a delay based on the estimated arrival time, the estimated arrival time notification can be considered equivalent to a delay notification.

[0025] The time at which the delay notification based on vehicle terminal 5 is sent can be, for example, (1) a time when the estimated arrival time of the first transit point in the next transit point or the next vehicle allocation plan is delayed by a specified time (specified time ≥ 0) or more; (2) a time when the latest allowed time has been exceeded while the vehicle has not yet arrived at the next transit point in the ongoing vehicle allocation plan; and / or (3) a time when the vehicle has actually arrived at the transit point. In the sending at times (1) and (2), the delay notification includes information on the estimated arrival time; in the sending at time (3), the delay notification includes information on the actual arrival time. The time at which the delay notification is sent can be all of (1) to (3), or only some of them. In this example, the delay notification is sent at least at time (1).

[0026] refer to Figure 2 The recalculation process is explained below. If the controller 3 receives a delay notification from the vehicle terminal 5, it investigates the vehicle allocation plans affected by the delay (hereinafter also referred to as "affected plans") from the pre-set vehicle allocation plans (S101). The controller 3 obtains various information about each registered vehicle through communication with the vehicle terminal 5 of each registered vehicle, such as the completion status of the vehicle allocation plan, the possible travel distance, and the charging status (in the case of electric vehicles). The controller 3 considers the estimated arrival time of the delayed vehicle, other vehicle allocation plans, and the status of other registered vehicles to determine which vehicle allocation plan is affected by the delay.

[0027] For example, such as Figure 3 As shown, when a vehicle allocation plan a1 is set for registered vehicle A, and a predetermined vehicle allocation plan a2 is set to be executed after vehicle allocation plan a1, the controller 3 calculates whether vehicle allocation plan a2 can be executed as scheduled (within the allowed time range) due to the delay of the executing vehicle allocation plan a1. For example, if the estimated arrival time of the transit point 72 for vehicle allocation plan a2 is later than the latest allowed time of transit point 72 due to the delay of vehicle allocation plan a1, the controller 3 determines that vehicle allocation plan a2 is the affected plan. On the other hand, vehicle allocation plan b1 set for registered vehicle B, which is a different vehicle from registered vehicle A, is determined to be unaffected by the delay of registered vehicle A. Although the delay of vehicle allocation plan a1 cannot be addressed, the affected plan a2 is recalculated. In addition, the determination of whether or not there is a delay notification based on the vehicle terminal 5 or the effect of the delay based on the controller 3 can be performed, for example, when the estimated arrival time of the route 71 of the vehicle allocation plan a1 is slower than the latest allowed time of the route 71, or when the estimated arrival time of the route 72 of the vehicle allocation plan a2 is slower than the latest allowed time of the route 72.

[0028] If there are no affected plans (S102: No), controller 3 ends the recalculation process. If there are more than one affected plan (S102: Yes), controller 3 temporarily cancels (releases) the affected plan and returns to the reservation request stage (S103). The affected plan is canceled and returns to the reservation request stage, becoming the same calculation object as the new reservation request. The reservation request corresponding to the canceled vehicle allocation plan is called a "re-reservation request".

[0029] As a constraint in recalculation, one example is that, in principle, the vehicle allocation plan can only be executed on the registered vehicle that performed the operation after the completion of the initial transit point (boarding, receiving) in the allocation plan. For instance, if the first allocation plan involves the first registered vehicle receiving the first and second goods at the first transit point and delivering the first goods at the second transit point, and the second allocation plan involves delivering the second goods at the third transit point, then even if the first allocation plan is delayed, the second allocation plan must still be executed on the first registered vehicle. Thus, the constraint that identifies the registered vehicle as the object of the allocation plan is called a "vehicle-specific constraint."

[0030] Examples of vehicle-specific constraints include delivery reservation requests for operations on registered vehicles equipped with insulated / cooled boxes (e.g., food receiving), and ride reservation requests for operations on registered vehicles with boarding / alighting assistance or wheelchair-accessible registered vehicles (e.g., elderly passengers). In other words, vehicle-specific constraints refer to "vehicle allocation plans that must be performed on specific registered vehicles," such as allocation plans that have already been implemented at a certain transit point or allocation plans requiring vehicles with specific functions. The presence or absence of vehicle-specific constraints is considered in the relationship between allocation plans and re-reservation requests during recalculation. When the content of a re-reservation request is an object of a vehicle-specific constraint, controller 3 performs recalculation (reassignment, rescheduling) to implement the allocation plan on the specific registered vehicle.

[0031] In the presence of multiple rebooking requests (S104: Yes), controller 3 determines the recalculation order (S105). The recalculation of rebooking requests is based on the property that earlier rebooking requests are relatively easier to allocate. That is, it can be said that earlier requests have relatively more available space (registered vehicles or times) and higher degrees of freedom than later ones. Therefore, controller 3 is configured to recalculate rebooking requests that are more difficult to allocate, prioritizing those that are harder to allocate.

[0032] The difficulty of allocation can be determined, for example, based on the difference between the current time and the latest allowed time of the next transit point in the rebooking request (i.e., the grace period). The smaller the grace period, the higher the difficulty (constraint) of recalculation, and the earlier the recalculation order. That is, controller 3 sets the recalculation order so that rebooking requests are arranged in order of increasing difficulty (rebooking requests with higher difficulty are placed first).

[0033] Furthermore, when the rebooking request involves a vehicle-specific constraint, controller 3 determines it to be of high difficulty. That is, controller 3 first recalculates rebooking requests with vehicle-specific constraints. In this example, the order of rebooking requests with vehicle-specific constraints is independent of the grace period; they are prioritized. For instance, the recalculation order, starting with the fastest, is: "rebooking requests with vehicle-specific constraints and small grace periods," "rebooking requests with vehicle-specific constraints and large grace periods," "rebooking requests without vehicle-specific constraints and small grace periods," and "rebooking requests without vehicle-specific constraints and large grace periods." Controller 3 determines the recalculation order based on the grace period and the presence or absence of vehicle-specific constraints. Additionally, if there is only one rebooking request (S104: No), controller 3 proceeds to the next step (S106).

[0034] According to the determined recalculation order, the controller 3 allocates the rebooking requests one by one using a successive optimal method (S106). Regarding successive optimality, firstly, the controller 3 calculates whether the rebooking request can be allocated by changing more than one arrival time within the allowable arrival time width of each transit point in each vehicle allocation plan.

[0035] For example, such as Figure 4 As shown, a vehicle allocation plan a1 is set for registered vehicle A, which includes receiving goods Z1 at store 81 (via location) and delivering goods Z1 to user residence 82 (via location). Controller 3 causes the unexecuted vehicle allocation plan a1 to move towards the faster side of the scheduled arrival time at store 81 within the allowed arrival time width (receivable period), and towards the slower side of the scheduled arrival time at user residence 82 within the allowed arrival time width (deliverable period). This creates a margin of time during the movement from store 81 to user residence 82. Controller 3 calculates whether to allocate a rebooking request during this margin of time. The movement (correction) to the scheduled arrival time is carried out within the allowed arrival time width and within the range achievable by the registered vehicle (especially the movement towards the faster side).

[0036] exist Figure 4In the example, the rebooking request involves receiving goods Z2 at store 91 and delivering goods Z2 to customer residence 92. Controller 3 considers the allowable arrival time width (receivable period) of store 91, the allowable arrival time width (deliverable period) of customer residence 92, and the travel time of registered vehicle A to determine whether the rebooking request can be executed on registered vehicle A within the leeway of vehicle allocation plan a1. Controller 3 performs the same simulation based on adjustments for the scheduled arrival time for other registered vehicles. Figure 4 The example shown is of a rebooking request being allocated during the leeway of vehicle allocation plan a1 to become vehicle allocation plan a2.

[0037] Thus, controller 3 performs the following calculations for each registered vehicle: as a simulation, the scheduled arrival times at each transit point are moved within the allowable arrival time width to generate leeway. Controller 3 scores the registered vehicles that can allocate rebooking requests to leeway using a prescribed evaluation function. The evaluation function can be appropriately set; for example, it can be set so that the shorter the overall travel distance or travel time of the registered vehicles after allocation, the higher the score. Furthermore, for example, the evaluation function related to the delivery of food such as bento boxes that require still-warm food upon delivery can be set so that the earlier the scheduled arrival time at the transit point, the higher the score. In this example's evaluation function, a higher score equates to a higher evaluation.

[0038] For example, if the calculation result of the allocation calculation and evaluation function is "Registered vehicle A scores 80 points", "Registered vehicle B scores 70 points", and "Registered vehicle C cannot be allocated and is not included in the calculation", then registered vehicle A is determined as the vehicle to be allocated for the rebooking request. Controller 3, for example, sets a vehicle allocation plan corresponding to the rebooking request that utilizes the slack time of registered vehicle A. Thus, successive optimization (successive optimal processing) means allocating the rebooking request to the registered vehicle with the highest score in the evaluation function. Controller 3 performs optimization sequentially for each rebooking request in a set order. The rebooking request is allocated as a new reservation and becomes a vehicle allocation plan again. Additionally, the evaluation function can also be used for the vehicle allocation plan (the initial vehicle allocation plan) for the reservation request. Furthermore, in Figure 3 In the case where registered vehicle B can execute the affected object plan a2, the rebooking request can be assigned to registered vehicle B. Alternatively, the rebooking request can be assigned to other registered vehicles without changing the arrival time. In this case, the registered vehicle can also be assigned based on the score of the evaluation function.

[0039] As a successive optimal outcome, if there are no unallocated rebooking requests (S107: Yes), the controller 3 sends the revised plan details to the corresponding vehicle terminal 5 via the communication device 2 (S108). The driver of the registered vehicle can confirm the revised plan details via the vehicle terminal 5. If there are unallocated rebooking requests (S107: No), the controller 3 sends status information to the operator terminal 6 and requests assistance from the operator (person) (S109). The operator can, for example, deploy a new registered vehicle, making that deployed vehicle correspond to the rebooking request.

[0040] The recalculation point can be the moment when it is determined that the vehicle allocation plan is affected by the delay after the delay notification (i.e., the moment when it is determined that recalculation is required). Alternatively, the recalculation point can be from the moment it is determined that recalculation is required, and the allocation can be reserved until a specified time before the time when the allocation can be realized, depending on the degree of delay (the degree of deviation between the scheduled and actual time). Therefore, in the case of a new reservation request with a small grace period, the reservation request can be allocated with priority over a re-reservation request. That is, by reserving the allocation of re-reservation requests to a certain extent, the allocation flexibility of subsequent reservation requests can be increased. During the recalculation reservation, in the case of a new reservation request, the controller 3 can set the recalculation order of the new reservation request and the re-reservation request at that moment (the moment the new reservation request is received), and perform the recalculation according to the set order. Furthermore, the registered vehicle can be an autonomous vehicle. In this case, based on the vehicle allocation plan information sent to the vehicle terminal 5, the registered vehicle is autonomously operated.

[0041] (Summary of this implementation method)

[0042] The vehicle allocation support system 1 of this embodiment includes: a communication device 2, which receives reservation requests including information related to multiple transit points where the operation will take place and the expected arrival time of at least one transit point; and a controller 3, which manages multiple registered vehicles and sets up a vehicle allocation plan for the registered vehicles based on the reservation requests received by the communication device 2. In the vehicle allocation support system 1, one vehicle allocation plan is set for each reservation request. At each transit point in the vehicle allocation plan, an allowable arrival time width is set between the earliest allowed time and the latest allowed time, which serves as the predetermined arrival time of the transit point and the allowed period for arrival at the transit point.

[0043] When communication device 2 receives a delay notification from a registered vehicle (vehicle terminal 5) executing a vehicle allocation plan, controller 3 determines whether there are other vehicle allocation plans, i.e., affected plans, that are affected by the delay in the vehicle allocation plan corresponding to the delay notification. A delay notification is a notification indicating that the estimated or actual arrival time at a transit point is later than the latest allowed time for that transit point, and it includes information about the estimated or actual arrival time. If controller 3 determines that there are affected plans, it cancels the affected plan and performs recalculation processing on the booking request corresponding to the affected plan as a new booking request. In the recalculation processing, as a simulation for allocating rebooking requests, it includes processing for changing the scheduled arrival time for one or more transit points in other vehicle allocation plans within the allowed arrival time width.

[0044] According to this structure, in cases where a delay is presumed to have occurred in the vehicle allocation plan, or where a delay actually occurs, the affected vehicle allocation plan (i.e., the affected plan) is cancelled and recalculated as a new reservation request (re-reservation request). During the recalculation process, since the arrival time is adjusted within the allowable arrival time width, the likelihood of allocating the re-reservation request within the allowed range increases. This structure can address situations where registered vehicles arrive late. In other words, this structure can suppress the impact of delays.

[0045] In the recalculation process, controller 3 determines whether a rebooking request can be assigned to a registered vehicle by changing the arrival time of other vehicle allocation plans within the allowed arrival time width, taking into account changes to the transit points. If there is only one available registered vehicle, controller 3 assigns the rebooking request to that vehicle. If there are multiple available registered vehicles, the rebooking request is assigned to the registered vehicle with the highest evaluation in the prescribed evaluation function. If no available registered vehicle exists, controller 3 sends the rebooking request information to the operator.

[0046] In the recalculation process, when multiple rebooking requests exist, controller 3 assigns a difficulty level to each rebooking request and executes the recalculation process in descending order of difficulty. Controller 3 imposes vehicle-specific constraints on vehicle allocation plans or rebooking requests that must be made in a specific registered vehicle, mandating the use of that specific registered vehicle, and performs recalculation processing based on these vehicle-specific constraints. As described above, the vehicle allocation support system 1 of this embodiment has a more practical structure.

[0047] Symbol Explanation

[0048] 1-Vehicle support system, 2-Communication device, 3-Controller, 4-User terminal, 5-Vehicle terminal.

Claims

1. A vehicle allocation support system, comprising: A communication device that receives a reservation request including information relating to a plurality of transit points where the operation will take place and a desired arrival time for at least one of the transit points; and The controller manages multiple registered vehicles and sets up a vehicle allocation plan for the registered vehicles based on the reservation requests received by the communication device. For each reservation request, one vehicle allocation plan is set. The vehicle allocation support system is characterized by the following features: In each of the transit points in the vehicle allocation plan, a predetermined arrival time for reaching the transit point is set, and an allowable arrival time width between the earliest and latest allowed time for reaching the transit point is defined. The controller performs the following processing: In the event that the communication device receives a delay notification from the registered vehicle executing the vehicle allocation plan, indicating that the estimated or actual arrival time of the transit point is later than the latest allowed time of that transit point, and including information about the estimated or actual arrival time. Determine whether there are other vehicle allocation plans, i.e., affected plans, that are affected by the delay in the vehicle allocation plan corresponding to the delay notification. If it is determined that the affected party's plan exists, the affected party's plan is cancelled, and the reservation request corresponding to the affected party's plan is treated as a new reservation request (i.e., a re-reservation request) and recalculated. In the recalculation process, as a simulation for allocating the rebooking request, there is a process for changing the arrival time of one or more of the transit points in the other vehicle allocation plans within the allowed arrival time width.

2. The vehicle allocation support system according to claim 1, characterized in that, The controller performs the following processing in the recalculation process: By changing the scheduled arrival time of the transit point within the allowed arrival time width for other vehicle allocation plans during the recalculation process, it is determined whether the rebooking request can be assigned to the registered vehicle. If there is only one registered vehicle available for allocation, the rebooking request will be allocated to that registered vehicle. If there are multiple registered vehicles that can be allocated, the rebooking request will be allocated to the registered vehicle with the highest rating in the prescribed evaluation function.

3. The vehicle allocation support system according to claim 2, characterized in that, If no registered vehicle can be allocated, the controller sends the rebooking request information to the operator.

4. The vehicle allocation support system according to claim 1, characterized in that, In the recalculation process, if there are multiple re-reservation requests, the controller assigns a difficulty level to each re-reservation request and executes the recalculation process in descending order of difficulty.

5. The vehicle allocation support system according to any one of claims 1 to 4, characterized in that, The controller performs the following processing: For the vehicle allocation plan or the rebooking request that must be carried out by a specific registered vehicle, impose vehicle-specific constraints that require the use of a specific registered vehicle; and The recalculation process is performed based on the vehicle-specific constraints.

Images