A vehicle allocation system

Abstract: The invention executes vehicle relocation by considering the seriousness of vehicle shortage. In relocating vehicles to a port running short of vehicles from another port, the seriousness of shortage is considered. A computing section 102 computes the number of expected demands. A computing section 104 computes the number of expected vehicles. An excess/shortage count computing section 106 computes excess or shortage from the difference between the number of demands and the number of vehicles. An evaluation value computing section 105 computes an evaluation value indicative of the degree of seriousness of vehicle shortage. A vehicle relocation setting section 107 sets relocation by considering the evaluation value, namely the degree of seriousness of vehicle shortage.

Description: The present invention relates generally to a vehicle allocation system and, more particularly, to a vehicle allocation system capable of supplying (or allocating) vehicles with stability within a desired wait time set in the system according to a ride demand in each port inside a certain area including a plurality of ports. In a vehicle allocation system for allocating the predetermined number of vehicles deployed in a certain area according to ride demands occurring in a plurality of ports, there may occur a shortage of currently available vehicles in any of the ports relative to the ride demand occurring in that port. If the shortage occurs, excess vehicles in other ports may be allocated to the shortage port (this is hereafter referred to as "vehicle relocation"). However, the above-mentioned vehicle allocation system is a reactive system in which measures are taken only after the occurrence of vehicle shortage, thus taking time for relocation from other ports to the port concerned. In addition, ride demands that newly occur during vehicle relocation and the arrival of vehicles that departed from other ports before vehicle relocation may cause a new vehicle shortage or excess in each port, thereby failing to meet with stability ride demands within a desired wait time. To solve the above-mentioned problems inherent to the conventional vehicle allocation system, vehicle relocation may be performed on the basis of the forecast data about ride demands. For example, vehicle allocation may be made according to the number of currently owned vehicles in each port and the ride demand forecast on the basis of the current ride demand occurring in that port and the past ride demand statistical data. For one example of vehicle allocation based on forecast ride demand, a vehicle demand forecasting system is disclosed in Japanese Patent Laid-open No. Hei 9-153098. In the above-mentioned conventional vehicle demand forecasting system, the number of currently available vehicles in each area is compared in absolute value with the demand to determine excess or shortage of vehicles. Actually, however, even if the number of vehicles in shortage is equal between ports, the degree of urgency in the number of vehicles to be allocated may differ from one port to another depending on the number of currently owned vehicles in each port. For example, assume that one port have 90 currently owned vehicles and 100 ride demands, resulting in a shortage of 10 vehicles, and another port have 10 currently owned vehicles and 20 ride demands, resulting in a shortage of 10 vehicles. The latter is obviously higher in the urgency than the former. Conventionally, the relocation based on the number of vehicles in shortage relative to the currently owned vehicles is not executed, so that the proper vehicle allocation based on the degree of urgency in the number of vehicles cannot be provided satisfactorily. It is therefore an object of the present invention to provide a vehicle allocation system that is based on the degree of urgency in the number of vehicles in each port, thereby meeting actual ride demands more properly than the conventional system. In carrying out the invention and according to one aspect thereof, there is provided a vehicle allocation system comprising: a vehicle excess/shortage count detecting means for detecting the number of vehicle excess/shortage that is estimated within a scheduled time for each of a plurality of ports set in an area; an evaluation value computing means for computing an evaluation value of a degree of vehicle shortage considering a ride demand expected within said scheduled time relative to the number of vehicle excess/shortage for each of said plurality of ports; and a relocation setting means for relocating an excess vehicle to the port having a lowest evaluation value from another port. According to the present invention, the number of vehicle excess/shortages is detected in each of an area. Based on the detection, excess vehicles are relocated from a port having excess vehicles to a port having vehicles fewer than the expected number of vehicles. As mentioned above and according to the invention claimed in claims 1 through 5 appended hereto, when relocating vehicles to ports running short of vehicles, relocation is executed first for a port running short of vehicles most seriously. Consequently, if a vehicle shortage occurs in an area, relocation can be executed evenly for all the ports in the area without involving concentration. Especially, according to claim 3 appended hereto, the evaluation value indicative of the degree of urgency in the number of vehicles is updated every time relocation is executed. Consequently, if there are two or more ports running short of vehicles, vehicle movement can be executed evenly. According to the invention claimed in claim 4 appended hereto, relocation is executed starting from a port in excess of vehicles more than other ports, thereby deploying vehicles evenly in the area. According to the invention claimed in claim 5 appended hereto, a port running in short of vehicles is relocated with vehicles from the port nearest to that port. Consequently, the vehicle wait time is shorted further. This invention will be described in further detail by way of example with reference to the accompanying drawings. FIG. 1 is a schematic diagram illustrating a vehicle allocation system practiced as one preferred embodiment of the invention. FIG. 2 is a block diagram illustrating main capabilities of a host computer and a terminal which are set at a port. FIG. 3 is a diagram illustrating a ride demand and the number of vehicles of each port before relocation instruction. FIG. 4 is a diagram illustrating a ride demand and the number of vehicles in each port after relocation instruction. FIG. 5 is a flowchart indicative of relocation setting processing. FIG. 6 is a diagram illustrating one example of vehicle travel times between ports. FIG. 7 is a diagram illustrating a relationship between the number of deployed vehicles and the number of relocated vehicles. FIG. 8 is a diagram illustrating a relationship between the number of deployed vehicles and an average wait time. FIGS. 9(a) to 9(c) are diagrams illustrating a result of simulations of vehicle travel time between ports. FIG. 10 is a diagram illustrating a transition of a daily ride demand. FIG. 11 is another diagram illustrating a deviation in the wait time for each number of deployed vehicles. FIG. 12 is a diagram illustrating a deviation in the wait time for each number of deployed vehicles. FIG. 1 is a schematic diagram illustrating a vehicle allocation system practiced as one preferred embodiment of the invention. As shown, there provided five ports in one area. Ports P1, P2, P3, P4, and P5 (hereafter generically referred to as port P unless specific ports are referenced) are predetermined parking spaces arranged in such as a golf course, an airport, or a hotel for example. In this area, a plurality of vehicles 4 are deployed. The optimum number of vehicles to be deployed in the area will be described later. Port P has a terminal 2 which is connected to a sensor 3 for detecting vehicles coming and going. The sensor 3 has a capability of identifying vehicle numbers to identify the vehicle 4. The vehicle number herein may be a vehicle number written on the number plates of each vehicle at its front and rear or one that is written on a special portion of a vehicle such as its side or top. The vehicle numbers are not limited to numeric characters. They may be identification information such as bar-codes and other codes. The sensor 3 may be an optical sensor for optically reading the vehicle number on each vehicle. The terminal 2 has an identification device (not shown) for identifying a user of that vehicle. This identification device checks the ID number or the like of the user whether the user is a registered contract user or not. Preferably, the ID number or the like is written on an IC card. The identification device reads the IC card presented by the user at the beginning of use and at the end of use to identify the end of vehicle usage. The terminal 2 has an input device (not shown) for the user to input a destination. This input device may be constituted by the switches corresponding to the ports P1 through P5. The vehicle 4 is a self-propelled electric car for example, which is constituted such that the door lock is cleared for starting when the user is permitted to use the car. It should be noted that the door lock may be cleared by the above-mentioned IC card of the user. In any case, it is.preferable that the identification information (ID number or the like) for identifying the user having the IC card is identified by the terminal 2 of the port P in which the user rides the vehicle. The terminal 2 is connected to a host computer 1 (hereafter referred to as a "host") through a communication line. Data transfer is executed between the terminal 2 and the host 1. The terminal 2 in the port P in which the user rides the vehicle sends the currently owned vehicle numbers in port P, the number of such vehicles in port P, the contract user ID numbers in port P, the ride demands, and so on to the host 1. A ride demand occurs when the user inputs the ID number. The ride demand includes the information about destination. The host 1 references the personal information of the contract user based on the ID number to determine whether the use of the vehicle is permitted or not, then instructing the terminal 2 for the permission of vehicle lending and the vehicle to be lent. This instruction actually allows the ride in the vehicle. When this instruction is made, "occurrence trip" occurs. On the other hand, the terminal 2 of port P in which the vehicle carrying the user arrives sends the currently owned vehicle numbers in the port P, the number of such vehicles in port P, the contract user ID number, the arrival recognition information, the contract user travel data, and so on to the host 1. The arrival recognition information is outputted, on the basis of the detection result of the sensor 3, when the vehicle 4 corresponding to the occurrence trip has entered port P. The host 1 has a computing means (CPU) 10 for performing the computation for instructing, on the basis of the information supplied from the terminal 2, the terminal 2 for lending permission and a vehicle to be lent, a storage device (memory) 11, and a communication device 12 for giving instructions to each vehicle 4. The memory 11 stores forecast ride demand data (hereafter referred to as "forecast occurrence trip") of each port P as one of the ride demand statistical data of all ports. The memory also stores data such as contract user information and contract user travel data. The forecast occurrence trip denotes a prospective demand per day set on the basis of past demand results. The contract user information is personal information such as the name of contract user corresponding to the ID number. The contract user travel data includes travel distance and travel time for use in billing the contract user. FIG. 2 is a block diagram illustrating main capabilities of the host 1 and the terminal 2 for setting vehicle allocation and relocation. The terminal 2 has a currently owned demand count detector 20, a currently owned vehicle count detector 21, an arrival trip count detector 22, and a display section 23. On the basis of a demand detection signal caused when the ID number inputted by the user is recognized, the currently owned demand count detector 20, detects the number of demands actually occurring in that port P. On the basis of the vehicle number detected by the sensor 3 and the detection result of vehicle comings and goings, the currently owned vehicle count detector 21 detects the number of currently available vehicles in that port P. The arrival trip count detector 22 detects the occurrence trip that actually occurred in another port P and the number of vehicles (arrival trips) that surely arrive by relocation. The arrival trip includes both a vehicle within an SD time to be described later and a vehicle deployed by relocation out of the SD time. The display section 23 is for instructing or guiding the user for the vehicle to ride in. On the basis of the lending permission or the like inputted from the host 1, guidance is executed in image or voice. If the vehicle 4 is available in port P and a ride vehicle instruction can be issued immediately after inputting of the ID number of the user, the display section 23 may execute guidance of the vehicle number and the like and, if the vehicle 4 is unavailable, the display section 23 may execute guidance of the forecast wait time. The currently owned demand count detector 20, the currently owned vehicle count detector 21, the arrival trip count detector 22, and the display section 23 may be provided as capabilities of the terminal 2. Except for the display section 23, these detectors may be capabilities to be executed by the host 1 side on the basis of the information supplied from the terminal 2. On the other hand, the memory 11 of the host 1 is provided with a forecast occurrence trip storage device section 110. The forecast occurrence trip storage section 110 stores a ride demand result of one day in the form of time-series data as a forecast occurrence trip (forecast ride demand) for each port P. The forecast occurrence trip is a accumulation of the past ride demand results classified by weather, time and date, and day of the week for example. Preferably, the forecast occurrence trip according to time and date, weather, day of the week for example may be supplied to the CPU 10 in advance. The forecast occurrence trip is read by a forecast occurrence trip count detector 101 to be supplied to a forecast occurrence demand count computing section 102. The forecast occurrence demand computing section 102 adds the above-mentioned the currently owned demand count to the forecast occurrence trip count to compute a forecast occurrence demand count. The forecast arrival trip count detector 103 detects a forecast arrival trip count on the basis of the above-mentioned forecast occurrence trip and inputs the detection into a forecast occurrence vehicle count computing section 104. The forecast occurrence vehicle count computing section 104 adds the forecast arrival trip count and the arrival trip count to the number of currently owned vehicles to compute a forecast occurrence vehicle count. It should be noted that the forecast arrival trip count depends on the ratio of the number of currently owned vehicles (including the arrival trips within the SD time in this case) in that port P to the forecast occurrence demand count in port P in which an occurrence trip corresponding to the arrival trip has occurred. Namely, when this ratio is large, it indicates that there are excess vehicles, so that it is highly possible for the forecast arrival trip to become an actual arrival trip. When this ratio is low, it means there is no excess vehicles, so that the possibility of the forecast arrival trip becoming an actual arrival trip is low. Therefore, a value obtained by multiplying a forecast arrival trip count by the above-mentioned ratio (referred to as a reduction coefficient) is used as a forecast arrival trip count, which is used for the calculation of a forecast occurrence vehicle count. Namely, the forecast occurrence vehicle count and the reduction coefficient are calculated by relations (f1) and (f2) as follows: Forecast occurrence vehicle count = currently owned vehicle count + (reduction coefficient × forecast arrival trip count) + arrival trip count Reduction coefficient = (currently owned vehicle count + arrival trip count) ÷ forecast occurrence demand count An evaluation value computing section 105 computes an evaluation value for determining the urgency of the number of vehicles in each port P by use of relation (f3) on the basis of a forecast occurrence demand count and a forecast occurrence vehicle count: Evaluation value = (forecast occurrence vehicle count - forecast occurrence demand) ÷ forecast occurrence demand count ½ It should be noted that the root of the forecast occurrence demand count is the denominator. This is because relocation setting processing to be described later can be executed as initially intended by largely varying the evaluation value according to the variation in the forecast occurrence demand count, namely by making the sensitivity high. Therefore, although a square root is used in relation (f3), a cubic root or other roots may be used as required. Obviously, as the multiplier increases, the sensitivity of the evaluation value goes higher. An excess/shortage count computing section 106 computes the difference between a forecast occurrence demand count and a forecast occurrence vehicle count, namely the excess or shortage of vehicles. A vehicle relocation setting section 107, on the basis of the vehicle excess/shortage count of each port P and in consideration of the above-mentioned evaluation value, gives an instruction of relocation for moving the excess vehicle 4 to another port P. This vehicle relocation instruction is given to the vehicle 4 through the above-mentioned communication device 12. In order to meet the relocation requirement, the vehicle 4 is equipped with a communication device and an automatic travel device. For the automatic travel system, a known system may be used such as a position sensing system using map data and GPS and a traffic light and obstacle monitor system. If an available vehicle is found, a vehicle allocation setting section 108, immediately informs the terminal 2 of the lending permission and the vehicle to lend. If there is no available vehicle, the vehicle allocation setting section calculates a wait time on the basis of the arrival trip, the relocated vehicle arrival scheduled time, and so on, and informs the terminal 2 of the result. This allows the user to recognize the wait time. It should be noted that an SD setting section 109 determines, on the basis of the data stored in a forecast occurrence trip storage device 110, whether the demand estimated to occur per scheduled time is in excess of the number of scheduled reference vehicles. According to the result of the determination, the SD setting section 109 determines whether to search the forecast occurrence trips how many hours (or minutes) from the current time, thereby determining a search range (SD time). The forecast occurrence demand count computing section 102 and the forecast occurrence vehicle count computing section 104 compute the number of demands and the number of vehicles in this SD time. An SD time determination algorithm will be described later. The following describes an actual example of vehicle allocation and vehicle relocation. If vehicle relocation is executed only on the basis of the currently owned vehicle count and currently owned demand count in each port P, no efficient vehicle allocation can be executed because of a new vehicle excess or shortage caused by demand fluctuation and vehicle movement. Therefore, in the present embodiment, in order to execute vehicle relocation, the vehicle excess or shortage is calculated by considering the forecast occurrence demand the forecast occurrence vehicle count within a preset SD time. In this case, vehicle relocation is executed by using a reduction coefficient for increasing the accuracy of the forecast arrival trip count as mentioned above and considering an evaluation value representing the degree of urgency of the number of vehicles in each port P. FIG. 3 is a diagram illustrating variations in the number of vehicles caused by the occurrences of occurrence trips and arrival trips in each port P. In this diagram, the occurrence of trips predicted in the current SD time is estimated but the trips for vehicle relocation are not considered. In the figure, the currently owned demand count is "3" and the currently owned vehicle count is "0" in port P1, indicating a shortage of three vehicles at this point of time. In port P1, there are arrival trip Ta1 due to the occurrence trip caused in another port before the current point of time and arrival trip Ta11 due to the initial occurrence trip Td3 in the current SD time caused in port P3. On the other hand, because the occurrence of forecast occurrence trip Tf1 is predicted, the total number of demands, namely the number of forecast demands is "4". Therefore, the number of demands is "4" relative to the number of available vehicles of "2" within the current SD time, resulting in a shortage of two vehicles. In port P2, the currently owned demand count is "0" and the currently owned vehicle count is "5", so that five vehicles are in excess at the current point of time. In port P2, forecast occurrence trips Tf2 and Tf21 are predicted to occur, so that the total number of demands is 2. Therefore, the number of demands is "2" relative to the number of available vehicle of "5" in the current SD time, so that three vehicles are expected to be in excess. In port P3, the currently owned demand count is "5" and the current owned vehicle count is "2", so that three vehicles are in shortage at the current point of time. In port 3, there are two currently owned vehicles, so that occurrence trips Td3 and Td31 immediately occur in response to the two demands. Also, there are arrival trips Ta3 and Ta31 due to occurrence trips that occurred in another port in a previous SD time. There is no forecast occurrence trip, so that the total number of demands remains "5". As a result, the number of demands is "5" relative to the number of available vehicles of "4" within the current SD time, indicating a shortage of one vehicle. In port P4, the currently owned demand count is "1" and the currently owned vehicle count is "1", so that there is no excess or shortage of vehicles. In port P4, because there is one currently owned vehicle, occurrence trip Td4 occurs immediately in response to a demand. In port P4, forecast occurrence trip Tf4 is predicted, so that the total number of demands is "2". Also, arrival trip Ta4 due to the occurrence trip that occurred in port P3 is predicted. Therefore, the number of demands is "2" relative to the number of available vehicles of "2" within the current SD time, so that there is no excess or shortage of vehicles. In port P5, the currently owned demand count is "0" and the currently owned vehicle count is "1", so that one vehicle is in excess at the current point of time. In port P5, there is arrival trip Ta5 due to occurrence trip Td4 in port P4 and there is arrival trip Ta51 due to the occurrence trip that occurred in another port in a previous SD time. Also, forecast occurrence trip Tf5 is predicted, so that the total number of demands is "1". As a result, the number of demands is "1" relative to the number of available vehicles in the current SD time of "3", so that there will be two excess vehicles. Relocation is set on the basis of the fluctuation in the number of vehicles and demands within the above-mentioned SD time. The following describes a vehicle relocation algorithm step by step. First, as a first stage, a vehicle relocatable port and the number of relocatable vehicles within a SD time are detected. In the above-mentioned example, port P2 and port P5 have excess vehicles, so that relocation can be made from these ports. As a second stage, in the vehicle relocatable ports, the number of vehicles remaining at these ports after relocation is calculated. As a third stage, it is determined whether these remaining vehicles can meet a demand that occurs next. Namely, if a demand occurs after all vehicles have been relocated and before the number of vehicles in that port P recovers due to arrival trip and so on, that demand cannot be satisfied immediately. Therefore, if the number of remaining vehicles is possibly available for the demand that occurs next, these vehicles are actually made relocatable. It should be noted that the vehicles to be relocated are sequentially set for ports P in increasing order of the calculated evaluation values. Here, it is determined whether relocation is to begin in increasing order of distances from the ports P having excess vehicles to the port P in shortage or in decreasing order of the evaluation values of the ports P having excess vehicles. In the above-mentioned example, if three excess vehicles are relocated from port P2, there remain two vehicles, so that there still remains one vehicle when forecast occurrence trip Tf2 that occurs next is satisfied. Therefore, port P2 can relocate three vehicles. On the other hand, in port P5, when two excess vehicles are relocated, only one vehicle remains. Therefore, when forecast occurrence trip Tf5 that occurs next is satisfied with this one vehicle, there remains no vehicle, making relocation impossible. If vehicle relocation is practicable in port P5, relocation becomes practicable from both port P2 and port P5. Therefore, relocation can be executed from ports 2 or port 5 whichever is nearer to port P1 and port P3 running short of vehicles. FIG. 4 is a diagram illustrating the variations in the number of vehicles in each port P within SD time when relocation has been executed on the basis of the result of the above-mentioned examination. In the figure, in port P1, one of the users of the current demands can ride on the vehicle of arrival trip Ta1 and second and third users can ride on two vehicles (Dv1 and Dv2) relocated from port P2. The user of forecast occurrence trip Tf 1 can ride on the vehicle of arrival demand Ta11. In port P2, two vehicles (d1 and d2) are relocated to port P1 and one vehicle (d3) relocated to port P3. The user of forecast occurrence trip Tf2 can ride on the currently owned vehicle (V1) and the user of forecast occurrence trip Tf21 can ride on the currently owned vehicle (V2). In port P3, there are two currently owned vehicles, so that two of the five demands can be met immediately, thereby allowing two users to ride on the vehicles of occurrence trips Td3 and Td31. The third and fourth users can ride on the vehicles of arrival trips Ta3 and Ta31. The fifth user can ride on the vehicle (Dv3) relocated from port P2. In port P4, there is one currently owned vehicle, so that one demand can be met immediately, thereby allowing the user to ride on the vehicle of occurrence trip Td4. Further, a user corresponding to forecast occurrence trip can ride the vehicle of arrival trip Ta4. In addition, in port P4, there is arrival trip Ta41, which is based on forecast occurrence trip Tf5 in port P5 and therefore unpredictable and not considered at the examination of relocation. In port P5, there is one currently owned vehicle but no demand, so that no occurrence trip occurs immediately. The user of forecast occurrence trip Tf5 can ride currently owned vehicle V5. The vehicles of arrival trips Ta5 and Ta51 that will occur thereafter remain unrelocated. In port P5, there is arrival trip Ta52 based on forecast occurrence trip Tf4 that occurred in port P4. This arrival trip is unpredictable and therefore not considered at the examination of relocation. However, based on statistical data, this arrival trip Ta52 may be considered into the calculation of relocation. Thus, as a result, ports P1 through P3 can meet the demands within SD time without involving vehicle excess or shortage. In port P4, there remains one vehicle, while in port P5 there remain three vehicles. In the above-mentioned example, the demands can be met within the current SD time. However, if some demands cannot be met within this SD time, the vehicle in shortage are remained till the examination of relocation in the next SD time. In the case where a maximum wait time is preset and this preset maximum wait time is exceeded within this current SD time, the relocatable vehicles including ones in the ports P previously determined for no vehicle relocation are relocated to meet the demands. The following describes the processing of the above-mentioned vehicle relocation with reference to a flowchart. FIG. 5 is the flowchart indicative of the processing of vehicle relocation setting. In step S1, the number of forecast occurrence demands is calculated. In step S2, the number of forecast occurrence vehicles is calculated. In step S3, an evaluation value is calculated from the number of forecast occurrence demands and the number of forecast occurrence vehicles by use of the above-mentioned relation (f1). When processing operations of steps S1 through S3 have been performed on all ports P, then the processing goes to step S4. In step S4, the ports P are arranged in the increasing order of evaluation values. In step S5, the ports P are checked for vehicle excess or shortage in the increasing order of evaluation values. In step S6, it is determined whether all ports P have been checked. If the decision is "no", then the processing goes to step S7. In step S7, the number of forecast occurrence demands is subtracted from the number of forecast occurrence vehicles of that port P and the result is set to variable B. In step S8, it is determined whether variable B is negative or positive, thereby determining whether port P concerned is running short of vehicles. If any port P running short of vehicles is found, then the step goes to step S9 in which the vehicle relocatable ports P are checked in the increasing order of distances from the port P running short of vehicles. In step S10, it is determined whether all ports P have been checked. If the decision is "no", the processing goes to step S11. In step S11, it is determined whether port P concerned is currently in excess of vehicles. The excess of vehicles here denotes that there is currently an excess vehicle and the number of currently owned vehicles is greater than the number of forecast occurrence demands. This condition is provided to meet a situation in which, when excess vehicles have been relocated and there still remain vehicles, thereby satisfying a demand that occurs next. If the decision in step S11 is "yes", then the processing goes to step S12, in which relocation is executed. In step S13, an evaluation value is calculated from both the number of forecast occurrence demands and the number of forecast occurrence vehicles after the relocation made in step S12. When the evaluation value is obtained, the processing goes back to step S4 to repeat the above-mentioned processing operations. If no port P is found not running short of vehicles, namely, if the decision of step S6 is "yes", no relocation is required, upon which this processing comes to the end. If, for all ports P, there are not enough vehicles for relocation, namely if the decision of step S10 is "yes", no relocation can be performed, upon which this processing comes to the end. As described, in the present embodiment, relocation is executed from the ports P in the order of more serious vehicle shortage determined on the basis of the obtained evaluation value. And the evaluation value is updated every time one session of relocation has been executed, thereby dynamically meeting the vehicle excess or shortage that may fluctuate from one session of relation to another. In the above-mentioned flowchart, for the detection of vehicle relocatable ports, the ports are checked in the increasing order of their locations from port P running short of vehicles. This check may also be performed in the decreasing order of the evaluation values of the ports P. This can prevent a situation in which a specific port is outstandingly in excess of vehicles, thereby maintaining a situation in which vehicles are deployed equally all over ports P. The following describes an algorithm for setting SD time. FIG. 6 is a diagram illustrating times required for vehicle relocations among ports. As shown, the required time between farthest ports is 30 minutes while the required time between nearest ports is 5 minutes. As seen from the figure, if the number of vehicles relocatable within an SD time of less than 5 minutes is determined, the vehicles relocated in that SD time will not arrive at a schedule port. Within an SD time of 5 minutes to less than 7 minutes, relocation can be made only between port P1 and port P2. Within an SD time of 7 minutes to less than 9 minutes, relocation can be made only between port P1 and port P2 and between port P2 and port P3. Likewise, further examination indicates that relocation can be made all between ports within an SD time of 30 minutes or longer. Thus, to make relocation practicable, an SD time over the minimum required time for each travelling port P-to-port P must be set. In the example shown in FIG. 6, this SD time is 5 minutes or longer. In terms of a maximum wait time, an SD time which is shorter than a maximum wait time must be set. For example, if a maximum wait time is 15 minutes, an SD time must be set to less than 15 minutes. In this case, vehicle relocation can be made between port P1 and port P2, between port P2 and port P3, between port P3 and port P4, and between port P4 and port P5. If the vehicle 4 is to be relocated by automatically traveling the same, the required times between the ports are obviously determined on the basis of the travel speed of automatic traveling. The following describes an algorithm for determining an SD time with respect to the number of vehicles to be deployed. Obviously, if the number of vehicles equal to the total number of demands in port P is deployed in advance, there is no need for vehicle relocation to that port P. As the number of vehicles to be deployed to port P decreases, the number of vehicles to be relocated increases. Therefore, if the number of deployed vehicles is large and the necessity for relocation is small, the SD time can be set to a small value, tending to shorten the wait time in port P. However, it is not economical to increase the number of deployed vehicles without limitation. Preferably, the number of deployed vehicles is decreased by positively using relocated vehicles. On the other hand, if the number of deployed vehicles is decreased and the SD time is extremely made long, the wait time tends to become long. In addition, if the SD time gets long, the wait time also gets long but many arrival trips from other ports can be expected, thereby comparatively decreasing the number of relocated vehicles. Consequently, preferably, the number of deployed vehicles, the number of relocated vehicles, and wait time are totally examined to determine the SD time. FIG. 7 is a diagram illustrating a relationship between the number of deployed vehicles and the number of relocated vehicles with SD time used as a parameter. FIG. 8 is a diagram illustrating a relationship between the number of deployed vehicles and wait time with SD time used as a parameter. As shown in FIG. 7, if the number of deployed vehicles is less than "a" and the number of relocated vehicles is less than "A", decreasing the number of deployed vehicles decreases the number of relocated vehicles within the same SD time (the SD time being SD1 > SD2 > SD3 > SD4). On the other hand, as shown in FIG. 8, decreasing the number of deployed vehicles increases average wait time. Namely, because the number of deployed vehicles is decreased, the number of relocated vehicles decreases, the wait time increases consequently. Thus, to prevent the average wait time from exceeding the upper limit time B (B minutes) when the number of deployed vehicles has been decreased, the number of relocated vehicles must be increased. To do so, the SD time must be shortened. In other words, if the number of relocated vehicles is to be decreased, the SD time must be made longer and if the average wait time is to be shortened, the SD time must be shortened. For example, if points L, M, and H are set, each of these points satisfies both the settings of upper limit B minutes of average wait time and the number of relocated vehicles A. Therefore, which of the number of deployed vehicles, the number of relocated vehicles, and average wait time is to be prioritized can be determined by the necessities of each occasion (for example, business decision). The following describes a result of an examination performed on the ideal number of deployed vehicles. In order to make a wait time "0" (zero) if there is a difference between the number of demands that actually occur in each port and the number of demands forecast by the forecast occurrence trips of ride demand statistical data, each port, theoretically, may only have one vehicle always every time one demand occurs. On the other hand, if a demand occurs in a port and the number of deployed vehicles that can be relocated from the destination of that demand to the demanding port is deployed in advance, these two ports always have vehicles after the movement of relocated vehicles between the ports. Consequently, the number of deployed vehicles in each port becomes as initially set. Given the time for moving all port-to-port be constant and when a demand occurred in one of the ports, if relocation is executed from any other port, all ports can have vehicles after the movement time by replenishing by relocation vehicles between the ports in which vehicles come and go as described above. And if the demand occurrence frequency is only once in the above-mentioned movement time between ports, deploying one vehicle in each port in advance can make the wait time "0" (zero) theoretically. Therefore, actually, the number of deployed vehicles may be determined on the basis of how many times the forecast occurrence trips predicted take place in the entire area as calculated from the total number of forecast occurrence trips per day. The following describes an example obtained by a simulation executed on the basis of particular values. FIG. 9 is a diagram illustrating travel times between port P1 through port P5 for identifying the size of an area. In the figure, (a) indicates a travel time (48 km/hour) at which a human driver drives a vehicle, while (b) indicates a travel time (16 km/hour) at which a vehicle travels in an unattended manner. FIG. 10 is a diagram illustrating one example of actually measure values of ride demands in one day. As shown, ride demands are not constant throughout a day, namely they fairly fluctuate. In this example, the total number of forecast occurrence trips a day is about 1800. on the basis of the above-mentioned simulation conditions, the optimum number of deployed vehicles is calculated. The travel time between the ports is based on the travel time in the unattended, automatic travel state. At relocation, the travel speed of unattended travel is lower than that of attended travel, so that the travel time of unattended travel is longer than that of attended travel. Simply averaging the vehicle travel times shown in FIG. 9 (b) provides 14.46 minutes (about 15 minutes). If the total forecast occurrence trips in one day is 1,800, then the number of trips in every 15 minutes becomes about 18. This denotes that about 18 trips occur while attended vehicles and unattended vehicles travel for mutual supplement between ports. Therefore, the number of vehicles for the forecast occurrence trips per average travel time of vehicles between ports may only be deployed. To be more specific, deployment of 18 vehicles for each of 5 ports, namely a total of 90 vehicles (in other words, 5% of the total number, which is 1800, of forecast occurrence trips per day) in an area allows relocation from any port in response to occurrence trips. Theoretically, one vehicle always exists in each port when a demand occurs. Actually, however, there are variations in travel times between ports, the total number of occurrence trips per day varies, and demands may concentratedly occur in a particular time zone. These uncertain elements do not always make the wait time zero. However, as described above, in a system in which vehicle relocation is executed by forecasting occurrence trips and arrival trips from statistical data, the variation in wait time can be decreased if actual demands get out of forecast values. FIG. 11 and FIG. 12 are diagrams illustrating the deviations of wait times for each deployed vehicle in an area including a case in which actually demands (occurrence trips) are deviated from the forecast occurrence trips of ride demand statistical data. In each figure, the horizontal axis represents the ratio between the number of trips and the number of ports. It should be noted that FIG. 12 enlarges the wait time deviation shown in FIG. 11. As shown in these figures, if the number of deployed vehicles is 90, the deviation of actual demands from statistical data, whether it is small or large, results in only a small and stable deviation in wait time. On the other hand, if the number of deployed vehicles is 72 and 54, the deviation of actual demands from statistical data results in a very large deviation in wait time, indicating drastic variations. If the ratio between the number of trips and the number of ports decreases, namely if the number of trips is extremely low as compared with the number of ports, the deviation increases. If the number of ports is less than "about 10" relative to the number of trips of "1800", the deviation in the wait time in the number of trips and the number ports is small. Namely, the wait time becomes hardly affected by the number of trips and the number of ports. As described above, determining the number of deployed vehicles on the basis of the number of forecast occurrence trips per average travel time between ports provides a vehicle relocation system which is stable to the variations in actual demands. Further, as shown in FIG. 10, demands do not occur evenly throughout a day (24 hours). There is a time zone (4 hours) in which no demand occurred at all. Therefore, the total number of ride demands of 1800 trips of the total number of forecast occurrence trips per day may be considered as the number of trips for 20 hours. On the basis thereof, the number of forecast occurrence trips per average travel time between ports may be calculated. In that case, it is preferable to consider that the frequency of occurrence of trips between ports is not even but unbalanced. For example, the number of vehicles traveling between port P1 and port P2 may be larger than the number of vehicles traveling between port P1 and port P5. The above-mentioned case shown in FIG. 9 (c). FIG. 9 (c) shows a ratio to the frequency of occurrence of trips between ports, namely the above-mentioned trips. In this case, it is desired that the average travel time between ports be weighted-averaged instead of the above-mentioned simple averaging. From FIGS. 9 (b) and (c), the average travel time becomes 11.91 minutes (about 12 minutes). Therefore, 1800 trips per 20 hours are equivalent to 18 trips in about every 12 minutes, denoting that 90 vehicles may be deployed for 5 ports. The above-mentioned frequency of occurrence of trips between ports is specific to areas, so that, when an area is set, an occurrence frequency can be forecast and data can be gathered on the basis of the characteristics of the area. Consequently, it is preferable to consider the travel time between ports and the number of forecast occurrence trips in this travel time on the basis of the above-mentioned frequency of occurrence of trips between ports and a daily demand distribution. Namely, the travel time between ports may be handled not as a simple average value but as a weighted average value with the frequency of occurrence trips considered. In this case, one day may not always be handled as 24 hours. In the above-mentioned embodiment, a system in which the vehicle 4 is automatically traveled for relocation is assumed. It will be apparent to those skilled in the art that a relocated vehicle may be driven by a human driver and the vehicle 4 may be pulled by a trailer or another vehicle. It will be also apparent to those skilled in the art that the present invention is applicable to not only a vehicle relocation system in which vehicles are driven by users but also a vehicle relocation system in which taxis and limousine taxis are used. The invention executes vehicle relocation by considering the seriousness of vehicle shortage. In relocating vehicles to a port running short of vehicles from another port, the seriousness of shortage is considered. A computing section 102 computes the number of expected demands. A computing section 104 computes the number of expected vehicles. An excess/shortage count computing section 106 computes excess or shortage from the difference between the number of demands and the number of vehicles. An evaluation value computing section 105 computes an evaluation value indicative of the degree of seriousness of vehicle shortage. A vehicle relocation setting section 107 sets relocation by considering the evaluation value, namely the degree of seriousness of vehicle shortage.

Claims: A vehicle allocation system comprising: a vehicle excess/shortage count detecting means (106) for detecting the number of vehicle excess/shortage that is estimated within a scheduled time for each of a plurality of ports set in an area; an evaluation value computing means (105) for computing an evaluation value of a degree of vehicle shortage considering a ride demand expected within said scheduled time relative to the number of vehicle excess/shortage for each of said plurality of ports; and a relocation setting means (107) for relocating an excess vehicle to the port having a lowest evaluation value from another port. A vehicle allocation system comprising: a ride demand count detecting means (20) for detecting a forecast occurrence ride demand count for each port by adding a forecast ride demand count expected to occur within a scheduled time to a currently owned ride demand count; a vehicle count detecting means (21) for detecting a forecast occurrence vehicle count for each port by adding an arrival vehicle count expected to arrive within said scheduled time to a currently owned vehicle count; an excess/shortage count computing means (106) for computing a vehicle excess or shortage count for each port on the basis of said forecast occurrence ride demand count and said forecast occurrence vehicle count; and an evaluation value computing means (105) for computing an evaluation value of the degree of urgency of the number of vehicles on the basis of said forecast occurrence ride demand count relative to said vehicle excess or shortage count; wherein an excess vehicle is relocated to the port having a lowest evaluation value from another port. The vehicle allocation system as claimed in claim 1 or 2, wherein said evaluation value computing means (105) is adapted to compute an evaluation value every time vehicle relocation is executed. The vehicle allocation system as claimed in one of claims 1 through 3, wherein said vehicle relocation is executed sequentially on vehicles of ports in the decreasing order of the evaluation values thereof. The vehicle allocation system as claimed in one of claims 1 through 3, wherein said vehicle relocation is executed sequentially on vehicles of ports in the increasing order of distances therefrom to the port having a smallest evaluation value.

Inventors: MURAKAMI HIROSHI, NAKAMURA KAZUHIRO, UEHARA YUJI, YANO SHUNJI, MURAKAMI, HIROSHI, NAKAMURA, KAZUHIRO, UEHARA, YUJI, YANO, SHUNJI
Applicants: HONDA MOTOR CO LTD, HONDA GIKEN KOGYO KABUSHIKI KAISHA
Application year: 1999
Main classification: G08G1
IPC codes: B65G61, G08G1