JP6941014B2 - Vehicle dispatch system and vehicle allocation method - Google Patents

Description

The present invention relates to a vehicle dispatch system, and is particularly applicable to a vehicle dispatch system such as a taxi.

In recent years, with the development of wireless mobile communication systems, it has become possible to easily perform mobile data communication targeting a wide area. In addition, with the development of positioning technology using radio waves, it has become possible to obtain position information by a GPS (Global Positioning System) positioning system using artificial satellites. By fusing these wireless mobile communication systems and positioning systems, mobile data transmission systems and position management systems have been put into practical use, and are used for the purpose of improving the efficiency of dispatching taxis and transportation vehicles through commercial radios and public radios.

The AVM (Automatic Vehicle Monitoring) system for taxi dispatch by commercial radio is a GPS satellite, a mobile station (taxi), a base station that wirelessly communicates with the mobile station, and a management center connected to the base station by a dedicated line. It is composed of. In such an AVM system for taxi dispatch, a customer contacts a dispatch center, informs him / her current position and necessary vehicle information, and requests vehicle dispatch. At the vehicle dispatch center, the operator operates the vehicle dispatch terminal to transmit customer information and necessary vehicle information to the management center. The management center searches for the most suitable vehicle from the collected location information of the mobile station in order to dispatch the most suitable vehicle according to the customer's current position information, and the vehicle selected by the operator from the searched vehicles. Operate to dispatch vehicles.

A taxi dispatch system capable of efficiently dispatching a vehicle by using such an AVM system for taxi dispatch has been proposed (see Japanese Patent No. 5302832).

FIG. 3 is a sequence diagram for explaining the flow of vehicle allocation in the taxi dispatch system. FIG. 4 is a sequence diagram illustrating a case where vehicle allocation fails because a signal does not reach the vehicle allocation server (AVM server) in the management center from the mobile station (vehicle-mounted terminal). 3 and 4 show a sequence diagram showing transmission and reception timings between the vehicle dispatch terminal, the AVM server, the GW server, and the in-vehicle terminal.

(Successful vehicle allocation sequence)
First, the vehicle dispatch terminal makes a vehicle dispatch request to the AVM server of the management center (S1). The AVM server searches for the most suitable vehicle and makes a vehicle allocation request to the vehicle-mounted terminal of the vehicle (S2). The GW server notifies the in-vehicle terminal of the vehicle allocation instruction based on the distribution request from the AVM server (S3).

The in-vehicle terminal that has received the vehicle allocation instruction transmits a vehicle allocation information acquisition request to the AVM server via the GW server (S4, S5). The AVM server transmits the vehicle allocation information to the in-vehicle terminal via the GW server based on the vehicle allocation information acquisition request (S6, S7).

When the in-vehicle terminal receives the vehicle allocation information, it notifies the crew of the vehicle allocation request. When the crew can go to the customer's position, they press the "OK" button. When the crew presses the "OK" button, the in-vehicle terminal transmits a vehicle allocation consent signal to the AVM server via the GW server (S8, S9). When the AVM server receives the vehicle allocation approval signal, it transmits an approval approval signal (acknowledgement ACK) to the in-vehicle terminal via the GW server, and the vehicle allocation is completed (S10, S11).

(Vehicle dispatch failure sequence)
The case where the vehicle allocation fails in FIG. 4 will be described. S1-S7 are the same as those in FIG. 3, and the description thereof will be omitted. Upon receiving the vehicle allocation information, the in-vehicle terminal performs a predetermined approval operation and transmits the vehicle allocation approval signal to the AVM server via the GW server (S8). However, when the mobile station moves within the radio dead area (for example, outside the communication area of the radio base station), the AVM server cannot receive the vehicle allocation consent information from the in-vehicle terminal. Therefore, since the AVM server cannot receive the consent signal (S8), it cannot determine whether the vehicle allocation information has arrived at the in-vehicle terminal, and thus determines that the vehicle allocation has failed. On the other hand, since the in-vehicle terminal cannot receive the approval signal (acknowledgement ACK) from the AVM server, it cannot be determined whether the AVM server has received the approval signal, but in order to avoid leaving the vehicle heading to the customer's position, " It is judged that the vehicle allocation is completed.

Japanese Patent No. 5302832

In the taxi dispatch AVM system, when the management center cannot receive the vehicle dispatch approval signal from the mobile station as described above, the management center gives an instruction to dispatch the vehicle to another mobile station (taxi). Therefore, there is a problem of double or multiple vehicle allocation in which a plurality of mobile stations (taxi) head to the same customer's location.

An object of the present disclosure is to provide a vehicle allocation system that can eliminate the state of double vehicle allocation at an early stage.

Other challenges and novel features will become apparent from the description and accompanying drawings herein.

The following is a brief overview of the representative ones of the present disclosure.

That is, the vehicle allocation system includes a vehicle allocation server and a base station capable of communicating with an in-vehicle terminal mounted on each of a plurality of vehicles. The vehicle allocation server transmits to the in-vehicle terminal including at least a slip number and a substitute vehicle number assigned in sequence for each vehicle allocation request in the vehicle allocation request. Upon receiving the vehicle allocation request, the in-vehicle terminal transmits the slip number and the substitute vehicle number to the vehicle allocation server in the dynamic information. The vehicle allocation server acquires the slip number of each in-vehicle terminal from the dynamic information, determines that if there is the same slip number, it is a double vehicle allocation, and among the in-vehicle terminals determined to be double vehicle allocation, the substitute vehicle number is the most. A vehicle allocation cancellation signal is sent to an in-vehicle terminal other than a large in-vehicle terminal.

According to the above-mentioned vehicle allocation system, the state of double vehicle allocation can be resolved at an early stage.

It is a figure which shows the schematic structure of the vehicle dispatch system which concerns on Example 1. FIG. It is a figure which shows the schematic structure of the management center which concerns on Example 1. FIG. It is a sequence diagram explaining the completion of vehicle allocation. It is a sequence diagram explaining the vehicle allocation failure. It is a vehicle allocation sequence diagram which concerns on Example 1. FIG. It is a vehicle allocation sequence diagram which concerns on Example 2. FIG. It is a vehicle allocation cancellation processing flow chart which concerns on modification 2. FIG.

Hereinafter, examples will be described with reference to the drawings. However, in the following description, the same components may be designated by the same reference numerals and repeated description may be omitted. The drawings may be represented schematically as compared with actual embodiments in order to clarify the description, but they are merely examples and do not limit the interpretation of the present invention.

An example of a configuration diagram of the vehicle allocation system according to the first embodiment of the present invention will be described with reference to the drawings. FIG. 1 shows a schematic configuration diagram of a vehicle allocation system according to the first embodiment.

(Configuration of vehicle allocation system)
The vehicle dispatch system 1 is an AVM (Automatic Vehicle Monitoring) system for taxi dispatch using a wireless mobile communication system and a positioning system. The vehicle dispatch system 1 includes a management center 101, a plurality of radio base stations 102 (102-1, 102-2, ..., 102-L), and a plurality of mobile stations (vehicles such as taxis) 104 (104-1). , 104-2, ..., 104-N), a GPS satellite 105, and a vehicle allocation center 107 having a plurality of vehicle allocation terminals 106 (106-1, 106-2, ..., 106-M). It is configured using.

Each radio base station 102 has a communication area in which its own station can communicate. For example, the communication area 103-1 of the radio base station 102-1 is a mobile station 104 and a radio base station 102- existing in the area. It shows that it can communicate with 1.

Each mobile station 104 can obtain the position information (latitude, longitude) of its own vehicle by receiving the position information from the GPS satellite 105. The position information obtained by the mobile station 104 is periodically sent to the management center 101 through the radio base station 102 having the communication area 103 in which the vehicle exists, together with the dynamic information of the mobile station 104 (vehicle).

The management center 101 collects the position information and the dynamic information of the mobile station 104 existing in the communication area 103 through each of the plurality of radio base stations 102, and manages each mobile station 104.

The customer makes a vehicle allocation request by contacting the vehicle allocation center 107 and transmitting information on the position of the vehicle allocation destination (for example, the customer's current position) and the desired vehicle.

At the vehicle allocation center 107, the operator operates the vehicle allocation terminal 106 to transmit a vehicle allocation request (information on the position of the vehicle allocation destination and the desired vehicle) to the management center 101.

The management center 101 searches (searches for) a vehicle suitable for vehicle allocation from the collected position information of each mobile station 104 in accordance with the vehicle allocation request received from the vehicle allocation center 107, and sets the vehicle to the position instructed by the vehicle allocation destination. Operate to dispatch vehicles.

In addition, the customer can access the management center 101 through the Internet line by using the homepage of the taxi company or the application for requesting vehicle allocation installed on various commercially available mobile terminals (mobile phone terminals and tablet terminals). , It is also possible to make a vehicle allocation request to the management center 101 without going through the vehicle allocation center 107.

Next, the mobile station 104 deployed in each vehicle will be described. The mobile station 104 can exchange various information with the management center 101 through wireless communication with the radio base station 102 having the communication area 103 in which the own vehicle exists.

In addition, the mobile station 104 periodically obtains the position information (latitude, longitude) of its own vehicle based on the information received from the GPS satellite 105, and the information indicating the dynamics of the vehicle in which the mobile station 104 is deployed and the information indicating the dynamics of the vehicle to which the mobile station 104 is deployed. Notify the management center 101 together with the vehicle identification information.

The dynamics of the vehicle include "actual vehicle", "empty vehicle", "empty vehicle schedule", "payment", "break", etc., and are set by the crew operating the mobile station 104 deployed in each vehicle. Vehicles searched for as vehicle allocation candidates are basically "empty vehicles", but vehicles with other dynamics ("empty vehicle schedule", "payment", "break") that can be substantially allocated are also vehicle allocation candidates. The search may be performed as a vehicle of the taxi company, and which dynamics to be searched for as a vehicle to be dispatched may be set in advance according to the policy of the taxi company or the like.

Further, the mobile station 104 includes information indicating that when the own vehicle starts waiting at the standby place, the mobile station 104 starts waiting at the standby place in response to the operation of the mobile station 104 by the crew, and the standby. Information for identifying the location is transmitted to the management center 101 together with the identification information of the vehicle.

Further, the mobile station 104 includes information indicating that when the own vehicle ends the standby at the standby place, the standby at the standby place is terminated in response to the operation of the mobile station 104 by the crew, and the standby. Information for identifying the location is transmitted to the management center 101 together with the identification information of the vehicle.

Here, as the mobile station 104, a dedicated wireless communication terminal may be used, but various mobile terminals such as a commercially available mobile phone terminal (for example, a smartphone) and a tablet terminal having a wireless communication function may be used. You may use the one which installed the application for the vehicle dispatch system which realizes each function of.

(Configuration of management center)
Next, the configuration of the management center 101 will be described with reference to the configuration example shown in FIG.

The management center 101 includes a database server 200, a map server 220, a vehicle allocation server (AVM server) 240, and a gateway server 250.

The database server 200 is a server that manages various data related to the operation of the vehicle allocation system. In this example, the area information management unit 201 that stores and manages the area information related to each vehicle allocation area, and the vehicle information related to each vehicle. It has a vehicle information management unit 202 that stores and manages the information.

The area information of each vehicle allocation area managed by the area information management unit 201 includes identification information of the vehicle allocation area, information indicating the range of the vehicle allocation area, and information indicating the priority order applied in the search for vehicles to be allocated to the vehicle allocation area. Information indicating the priority order of the range for searching for vehicles in the vehicle allocation area, information indicating a time zone in which the area information is applied (hereinafter, applicable time zone), and the like are stored.

The vehicle information of each vehicle managed by the vehicle information management unit 202 includes vehicle identification information, current position information of the vehicle, information indicating the waiting place when the vehicle is waiting at the waiting place, and waiting order. Information to be shown, information to show the dynamics of the vehicle, information to show the front-end conditions for the vehicle, information to show the crew / vehicle shift of the vehicle, and the like are stored.

The map server 220 is a server that manages map information including the business area of a taxi company. In this example, a search for a route connecting these points and a distance index (straight line distance) are performed according to input of a departure point and an arrival point. , Route distance, estimated travel time), it has a route search unit 221.

The vehicle dispatch server 240 is a server that searches for vehicles to be dispatched by using the database server 200 and the map server 220. In this example, a vehicle suitable for vehicle allocation is searched for in response to a vehicle dispatch request from a customer (vehicle search). ), And a vehicle allocation instruction unit 242 that gives a vehicle allocation instruction to the vehicle (mobile station 104) searched by the candidate vehicle search unit 241.

When the candidate vehicle search unit 241 receives a vehicle allocation request from a customer, the candidate vehicle search unit 241 accesses the area information management unit 201 and the vehicle information management unit 202 using the vehicle allocation request as a search condition, and accesses the vehicle allocation destination specified in the vehicle allocation request. It is the area information of the vehicle allocation area including the position of, and the area information of the applicable time zone including the current time (at the time of search) is specified. The candidate vehicle search unit 241 also searches for an empty vehicle or a standby vehicle having the highest priority order and does not exist in the exclusion area according to the priority order and exclusion area set in the area information, and searches for the vehicle. Is determined as the vehicle to be dispatched (the most suitable vehicle for dispatching to the designated vehicle). Here, when a plurality of vehicles are specified in the vehicle allocation request, the specified number of vehicles is searched and the vehicle to be allocated is determined.

When a distance index for the position of the vehicle allocation destination and the position of each vehicle is required, these position information is provided to the map server 220 and calculated by the route search unit 221, and the result is acquired. Used for vehicle search.

In addition, if there is a request for front-end conditions such as vehicle characteristics (vehicle type, body color, etc.) and crew characteristics (gender, age, etc.) in the vehicle allocation request, priority is given to vehicles that meet those requests. , Search for vehicles.

The vehicle allocation instruction unit 242 notifies the mobile station 104 deployed in the vehicle searched by the candidate vehicle search unit 241 of the position of the vehicle allocation destination specified in the vehicle allocation request, and dispatches the vehicle to that position. Give instructions for dispatching vehicles.

The gateway server (GW server) 250 transmits a vehicle allocation instruction from the vehicle allocation instruction unit 242 to the vehicle mobile station 104 via the radio base station 102 of the communication area 103 in which the vehicle mobile station 104 exists.

(Vehicle dispatch sequence 1)
FIG. 5 is a vehicle allocation sequence diagram according to the embodiment. In FIG. 5, as described in FIG. 4, after the AVM server 240 determines that the vehicle-mounted terminal 104-1 has “failed to dispatch a vehicle”, for example, the vehicle is dispatched when a distribution request is made to the vehicle-mounted terminal 104-2. Shows the sequence. Since the explanations up to steps S1-S8 are the same as those in FIG. 4, the description is omitted.

An order is received from the customer and a vehicle dispatch request is issued from the vehicle dispatch terminal 106 to the AVM server 240 (S1). After that, the AVM server 240 creates reception information, stores it in the database server 200, and uses the AVM system to store the reception information. Give a unique slip number. The AVM server 240 creates vehicle allocation information and manages the vehicle allocation status. The vehicle allocation information shall include the slip number, the number of orders (vehicle allocation serial number), the number of vehicles allocated (substitute vehicle number), the status (vehicle allocation status), the vehicle allocation list (vehicle number), and the like.

After step S8, the AVM server 240 times out the reception of the consent signal from the vehicle-mounted terminal 104-1 after the non-reception state of the consent signal from the vehicle-mounted terminal 104-1 has elapsed for a predetermined time (acknowledgement signal timeout). (S22), the vehicle dispatch request is made to the next candidate in-vehicle terminal 104-2. That is, in the management center 101, in order to search for the optimum vehicle again according to the customer's current position information, from the position information of the mobile station 104 (104-2, 104-3, ..., 104-N) collected. , The optimum vehicle is re-searched, and the re-searched optimum vehicle is dispatched to the customer's current position. For example, it is assumed that the vehicle of the mobile station (vehicle-mounted terminal) 104-2 is newly selected as the optimum vehicle. When searching for vehicles, it is possible to search for vehicles in excess of the ordered number. It is also possible to select from a plurality of searched vehicles based on priority or to be selected at the discretion of the operator. As a result, the next candidate vehicle can also be selected based on the priority or at the discretion of the operator, so that the time for re-searching can be saved.

The AVM server 240 makes a vehicle allocation request to the in-vehicle terminal 104-2 (S22). Based on the distribution request from the AVM server 240, the GW server 250 notifies the vehicle-mounted terminal 104-2 of the vehicle of the vehicle allocation instruction via the radio base station 102 of the communication area 103 in which the vehicle-mounted terminal 104-2 is located. (S3). Upon receiving the vehicle allocation instruction, the in-vehicle terminal 104-2 transmits a vehicle allocation information acquisition request to the AVM server 240 via the GW server 250 (S24, S25). The AVM server 240 transmits the vehicle allocation information to the in-vehicle terminal 104-2 via the GW server 250 and the radio base station 102 based on the vehicle allocation information acquisition request (S26, S27).

Upon receiving the vehicle allocation information, the in-vehicle terminal 104-2 notifies the crew that a vehicle allocation request has been received. If the crew can go, press "OK". (If you cannot go, press "No"). When the crew member presses "OK" when he / she can go, he / she sends a vehicle allocation consent signal to the AVM server 240 via the GW server 250 (S28, S29). When the AVM server 240 receives the vehicle allocation consent signal, it completes the vehicle allocation status (vehicle allocation status), transmits the approval approval signal (acknowledgement ACK (OK)) to the vehicle-mounted terminal 104-2 via the GW server 250, and transmits the vehicle-mounted terminal 104-2. The dispatch to 104-2 is completed (S30, S31). As a result, the vehicle is dispatched to the in-vehicle terminal 104-2.

Next, for example, it is assumed that the vehicle-mounted terminal 104-1 moves into the communication area 103 of the wireless base station 102 and the communication between the vehicle-mounted terminal 104-1 and the wireless base station 102 is restored. In this case, the in-vehicle terminal 104-1 determines that the approval approval signal (acknowledgement ACK (OK)) from the AVM server 240 has timed out ((acknowledgement ACK timeout)), and transmits the vehicle allocation consent signal to the AVM server via the GW server 250. Retransmitting to 240 (S40, S41). The AVM server 240 executes a determination process for determining double vehicle allocation. In this case, since vehicle allocation to the in-vehicle terminal 104-2 is completed, double vehicle allocation is performed. It is determined that there is, and an acceptance approval signal (acknowledgement ACK (NG)) is transmitted to the in-vehicle terminal 104-1 via the GW server 250. That is, the AVM server 240 transmits the acceptance approval signal (acknowledgement ACK (NG)). By transmitting NG)), the vehicle allocation cancellation process is executed for the in-vehicle terminal 104-1. The in-vehicle terminal 104-1 is determined to have failed in vehicle allocation by receiving the approval approval signal (acknowledgement ACK (NG)). Then, notify the crew of the cancellation of the dispatch.

As described above, the management center 101 sends the first approval approval signal “OK ACK (OK)” and the second acknowledgment approval signal “OK ACK (NG)” to the in-vehicle terminal 104. Has the function of The first approval approval signal "OK ACK (OK)" is a signal for notifying the in-vehicle terminal (104-2) instructed to dispatch the vehicle that the vehicle has been dispatched. The second approval approval signal "OK ACK (NG)" is a signal for notifying the in-vehicle terminal (104-1) that has been instructed once to cancel the vehicle allocation.

As a result, the state of the management center 101 and the vehicle-mounted terminal 104 (104-1) is confirmed by confirming from the vehicle-mounted terminal 104 (104-1) to the AVM server 240 of the management center 101 whether or not the vehicle is double-distributed. It is possible to reduce the probability that the inconsistency will occur. In addition, the state of double or multiple vehicle allocation can be resolved at an early stage.

(Vehicle dispatch sequence 2)
FIG. 6 is a vehicle allocation sequence diagram according to the second embodiment. In FIG. 6, the part different from FIG. 5 is that steps S40 and S41) are deleted and step S50-step S53 is added instead. As described in the first embodiment, simply confirming from the in-vehicle terminal 104 (104-1) to the AVM server 240 of the management center 101 whether or not the vehicle is double-distributed is a communication failure, and how many times "OK". Even if the "signal" is retransmitted, it may not reach the AVM server 240, and the possibility of double vehicle allocation remains. Therefore, as in the second embodiment, it is preferable to add a mechanism for monitoring the double vehicle allocation on the management center 101 side and canceling the vehicle allocation from the management center 101 side to the in-vehicle terminal 104 when the double vehicle allocation occurs. Is.

The vehicle allocation sequence shown in FIG. 6 identifies a vehicle for which the vehicle allocation cancellation process has not been completed when there is a vehicle allocation number (vehicle allocation instruction) equal to or greater than the number ordered by the customer after the vehicle allocation is completed. This makes it possible to reliably perform the vehicle allocation cancellation process. It is preferable that this vehicle allocation sequence is automatically executed by the AVM server 240 of the management center 101 after the vehicle allocation is completed after receiving the order from the customer (step S31).

In the case of FIG. 6, a substitute vehicle number is added to the vehicle allocation information (slip data) managed by the AVM server 240, and the vehicle allocation request is created every time the vehicle allocation request is transmitted to the vehicle-mounted terminal (104). The dynamic information transmitted by the terminal to the AVM server 240 includes the slip number recognized by the in-vehicle terminal, the vehicle allocation serial number, and the substitute vehicle number. The slip number, vehicle allocation serial number, and substitute vehicle number are referred to as vehicle allocation key information.

Here, the slip number is a control number given for each customer's order.

The vehicle allocation serial number is a number assigned to each vehicle allocated to the customer's order. If the number of units ordered is two, the data of the vehicle allocation serial numbers 1 and 2 is generated.

The substitute vehicle number is a number assigned to each transmitted vehicle allocation request. The highest number is given to the last vehicle dispatched.

The dynamic information indicates the state of the taxi, such as "actual vehicle", "empty vehicle", and "break". Basically, the vehicle dispatched by the AVM server 240 is a candidate for a vehicle that is "empty" (the "actual vehicle" that is scheduled to become "empty" soon may also be a candidate).

The in-vehicle terminal 104 (104-1, 104-2) transmits the dynamic information to the AVM server 240 at the timing when a certain time elapses, a certain distance travels, or the dynamic information is changed (S50-S53). It is assumed that the dynamic information of the vehicle-mounted terminal 104-1 is transmitted to the AVM server 240 in steps S50 and S51, and the dynamic information of the vehicle-mounted terminal 104-2 is transmitted to the AVM server 240 in steps S52 and S53.

When double vehicle allocation occurs, dynamic information of the same slip number and vehicle allocation serial number is transmitted from in-vehicle terminals (140) of a plurality of vehicles (S50-S53). Therefore, the AVM server 240 of the management center 101 periodically (for example, every minute) monitors the dynamic information, and determines whether or not the same slip number and the dynamic data of the vehicle allocation serial number exist in a plurality of vehicles. .. That is, the AVM server 240 executes a determination process for determining double vehicle allocation based on the reception of dynamic information. As a result of the determination process, if the same slip number and the dynamic data of the vehicle allocation serial number exist in multiple vehicles, the vehicle allocation cancellation instruction is issued to the in-vehicle terminal (104-1), leaving the one with the largest substitute vehicle number. ) (S42, S43) to cancel the vehicle allocation. When the number of ordered vehicles is limited to one, or when a different slip number is assigned to each vehicle even when ordered from the same customer, it is possible to determine double vehicle allocation without assigning a vehicle allocation serial number. That is, when there is dynamic information of the same slip number, it is determined that double vehicle allocation has occurred, and a vehicle allocation cancellation instruction is transmitted to an in-vehicle terminal other than the in-vehicle terminal having the largest substitute vehicle number.

According to the above configuration, if it is recognized that the in-vehicle terminal 104-1 is dispatched, the dynamic information includes the slip number, the vehicle dispatch serial number, and the substitute vehicle number, so that the AVM server 240 is transmitted. But it becomes recognizable.

According to the second embodiment, since the in-vehicle terminal 104 is configured to periodically send dynamic information, when the communication environment is improved, the state of the in-vehicle terminal 104 is transmitted to the AVM server 240 of the management center 101. Can be done. By using this dynamic information, even after the vehicle allocation sequence is completed, the AVM server 240 can monitor double vehicle allocation or multiple vehicle allocation, and perform a determination process for determining double vehicle allocation. By automatically executing the vehicle allocation cancellation process from the AVM server 240 to the in-vehicle terminal 104, it is possible to save the trouble of the operator. By managing by the substitute vehicle number, it is possible to determine the vehicle to be canceled by a simple judgment flow.

It is also possible to combine the vehicle allocation sequence of FIG. 5 and the vehicle allocation sequence of FIG.

(Modification example 1)
FIG. 7 is a vehicle allocation cancellation processing flow diagram according to the first modification.

In this case, the AVM server 240 creates and holds a list (vehicle allocation information) in which the slip number, the vehicle that sent the vehicle allocation request, and the situation (acknowledgement, failure, timeout, etc.) are linked. Send a vehicle allocation cancellation signal to vehicles whose status is not "OK".

First, an order is received from a customer, and a vehicle dispatch request is issued from the vehicle dispatch terminal 106 to the AVM server 240. The AVM server 240 creates reception information, stores it in the database server 200, and assigns a slip number unique to the AVM system. The AVM server 240 creates vehicle allocation information and manages the vehicle allocation status. The vehicle allocation information shall include the slip number, the number of orders (vehicle allocation serial number), the number of vehicles allocated (substitute vehicle number), the status (vehicle allocation status), the vehicle allocation list (vehicle number), and the like.

For example, this flow may be automatically executed by the AVM server 240 of the management center 101 after receiving an order from the customer and completing the vehicle allocation (step S31). Alternatively, after receiving step S50-step S53 of FIG. 6, it may be automatically executed by the AVM server 240 of the management center 101. After step S31 or step S53, this flow starts (step S60).

First, the database server 200 is accessed, a slip number is acquired from the vehicle allocation information for which vehicle allocation has been completed, and the number of orders, the number of vehicles allocated, the vehicle allocation status, and the vehicle allocation list (vehicle number) for the slip number are acquired. Then, it is determined whether or not the ordered number of vehicles and the number of vehicles dispatched match, using the number of vehicles whose vehicle allocation status is other than the accepted number as the number of vehicles allocated (step S61). Step S61 can be regarded as a determination process for determining double vehicle allocation. As a result of the judgment, if the number of ordered vehicles and the number of vehicles dispatched match, it is judged as normal and this flow ends. Here, "normal" means that the situation of double or multiple vehicle allocation has not occurred.

As a result of the determination, if the number of ordered vehicles and the number of vehicles dispatched do not match, the process proceeds to step S62.

In step S62, it is determined whether or not the value obtained by subtracting the ordered number from the dispatched number (distributed number-ordered number) is 0 (zero). That is, the number of vehicles for which the vehicle allocation cancellation has not been processed is determined.

When (number of vehicles dispatched-number of ordered vehicles) is 0, it is determined that the vehicle allocation cancellation process is completed and the state of double vehicle allocation or multiple vehicle allocation has been resolved, and this flow ends.

If (number of vehicles dispatched-number of ordered vehicles) is not 0 (≠ 0), it is recognized that the vehicle allocation cancellation process is incomplete and the vehicle is in the state of double vehicle allocation or multiple vehicle allocation, and the process proceeds to step S63.

In step S63, it is determined whether the status for the vehicle number (No. xx) in the vehicle allocation list is OK or non-acceptable (failure, timeout). If it is accepted, the process proceeds to step S62. In the case of other than the consent (failure, timeout, etc.), the AVM server 240 sends the consent approval signal "OK ACK (NG)" to the vehicle number (No.xx) and executes the vehicle allocation cancellation process (FIG. 7). See S42 and S43). Further, the status of the vehicle number (No. xx) is changed to, for example, "OK ACK (NG)" to the state in which the vehicle allocation cancellation process is completed, and the dynamic information is set to, for example, "empty vehicle".

After that, the process proceeds to step S62, and steps S63 and S64 are executed until (number of vehicles allocated-number of orders) becomes 0.

By automatically executing the above flow by the AVM server 240 of the management center 101, it is determined and specified that the vehicle has not completed the vehicle allocation cancellation process, and the vehicle allocation cancellation signal "OK ACK (NG)" is transmitted. .. As a result, it is possible to reliably perform the vehicle allocation cancellation process while saving the trouble of the operator, so that it is possible to eliminate the state of double vehicle allocation or multiple vehicle allocation at an early stage.

It is also possible to combine the vehicle allocation sequence of FIG. 5 and the vehicle allocation cancellation processing flow of FIG. 7.

(Modification 2)
It is also possible to monitor double or multiple vehicle allocation at the management center 101, notify the operator, and manually cancel the vehicle allocation.

Monitoring of double or multiple vehicle allocation can be performed by the same mechanism as in the second embodiment. The detected result is notified to the vehicle dispatch terminal 106. As a notification method, the detection result is written in the database server 200, and the number of slips is transmitted to the vehicle dispatch terminal 106. On the operator side, when a double vehicle allocation slip is generated, the operator performs a process of opening the slip (determination process for determining double vehicle allocation) at the vehicle allocation terminal 106. Exclusive processing is performed on the database server 200 side so that a plurality of operators do not open the slip, and the slip is assigned on a first-come, first-served basis.

Open the slip and display on the map the vehicle that has been dispatched and the vehicle that has failed to dispatch but is sending the key data of the slip number of the slip in the dynamic data. Of these, those with double dispatch will be identified by turning the icon red. In addition, the route is searched from each vehicle to the pick-up destination, and the distance to the pick-up destination and the estimated arrival time are displayed.

The operator leaves the vehicle that is likely to arrive earliest from the estimated arrival time and the position on the map, performs the vehicle allocation cancellation process for other vehicles, and issues an instruction to cancel the vehicle allocation (“OK ACK (NG)” signal. Send). For vehicles that have been canceled, record the completion of the vehicle allocation cancellation in the vehicle allocation data, and explicitly leave that the vehicle allocation cancellation process has been executed. In addition, when leaving a vehicle that has failed to be dispatched, the vehicle allocation status of the vehicle allocation data is changed from the vehicle allocation failure to the vehicle allocation completion. By doing so, you will be able to know which vehicle was finally dispatched.

Although the invention made by the present inventor has been specifically described above based on examples, it goes without saying that the present invention is not limited to the above-described embodiments and examples and can be variously modified. ..

101: Management center 102 (102-1, 2, ..., L): Radio base station 103 (103-1, 2, ..., L): Communication area 104 (104-1, 2, ..., L): Communication area 104 (104-1, 2, ... N): Mobile station (vehicle)
105: GPS satellite 106 (106-1, 2, ..., M): Vehicle dispatch terminal 107: Vehicle dispatch center,
200, 200a: Database server 201: Area information management unit 202: Vehicle information management unit 203: Vehicle allocation history information storage unit 220: Map server 221: Route search unit 240: Vehicle allocation server (AVM server)
241: Candidate vehicle search unit 242: Vehicle allocation instruction unit 250: Gateway server (GW server)

Claims (6)

It is equipped with a vehicle allocation server and a base station capable of communicating with in-vehicle terminals mounted on each of a plurality of vehicles.
The vehicle allocation server transmits to the in-vehicle terminal including at least a slip number and a substitute vehicle number assigned in sequence for each vehicle allocation request in the vehicle allocation request.
When the in-vehicle terminal receives the vehicle allocation request, the in-vehicle terminal includes the slip number and the substitute vehicle number in the dynamic information and transmits the vehicle allocation request to the vehicle allocation server.
The vehicle allocation server acquires the slip number of each in-vehicle terminal from the dynamic information, determines that if there is the same slip number, it is a double vehicle allocation, and among the in-vehicle terminals determined to be double vehicle allocation, the substitute vehicle number is the most. A vehicle allocation system that sends a vehicle allocation cancellation signal to in-vehicle terminals other than large in-vehicle terminals. In the vehicle allocation system of claim 1,
The vehicle allocation server transmits the vehicle allocation request to the in-vehicle terminal, including the vehicle allocation serial number assigned to each vehicle allocated.
The in-vehicle terminal transmits the dynamic information including the vehicle allocation serial number to the vehicle allocation server.
The vehicle allocation server is a vehicle allocation system that determines that if there is the same slip number and vehicle allocation serial number, it is determined to be double vehicle allocation. It is equipped with a vehicle allocation server and a base station capable of communicating with in-vehicle terminals mounted on each of a plurality of vehicles.
The vehicle allocation server creates a list in which at least the slip number, the in-vehicle terminal that sent the vehicle allocation request, and the vehicle allocation status indicating whether the vehicle allocation was successful or unsuccessful are linked, and among the in-vehicle terminals in the list, the vehicle allocation failed. A vehicle allocation system that sends a vehicle allocation cancellation signal to the in-vehicle terminal linked to the vehicle allocation status indicating that. It is a vehicle allocation method that eliminates multiple vehicle allocation in a vehicle allocation system including a vehicle allocation server and a base station capable of communicating with an in-vehicle terminal mounted on each of a plurality of vehicles.
The vehicle allocation request transmitted from the vehicle allocation server to the in-vehicle terminal includes at least a slip number and a substitute vehicle number assigned in sequence for each vehicle allocation request.
The dynamic information transmitted from the in-vehicle terminal to the vehicle allocation server includes the slip number and the substitute vehicle number.
If there is the same slip number in the dynamic information, it is determined that the vehicle is double-distributed, and a vehicle allocation cancellation signal is sent to the in-vehicle terminal other than the in-vehicle terminal having the highest substitute vehicle number among the in-vehicle terminals determined to be double-distributed. How to dispatch a car. In the vehicle allocation method of claim 4,
The vehicle allocation request includes a vehicle allocation serial number assigned to each vehicle allocated.
The dynamic information includes the vehicle allocation serial number,
A vehicle allocation method in which if the same slip number and vehicle allocation serial number are present in the dynamic information, it is determined to be double vehicle allocation. It is a vehicle allocation method that eliminates multiple vehicle allocation in a vehicle allocation system including a vehicle allocation server and a base station capable of communicating with an in-vehicle terminal mounted on each of a plurality of vehicles.
Create a list linked with at least the slip number, the in-vehicle terminal that sent the vehicle allocation request, and the vehicle allocation status indicating whether the vehicle allocation was successful or unsuccessful.
A vehicle allocation method that sends a vehicle allocation cancellation signal to the in-vehicle terminal associated with the vehicle allocation status indicating that the vehicle allocation has failed among the in-vehicle terminals in the list.

Images