JP2019061307A - Vehicle allocation system and vehicle allocation method - Google Patents

Abstract

To provide a vehicle allocation system capable of rapidly eliminating a double vehicle allocation state.SOLUTION: A vehicle allocation system includes: a vehicle allocation server; and a base station communicable with on-vehicle terminals mounted on each one of multiple vehicles. The vehicle allocation server allows vehicle allocation requests to include at least slip numbers and loaner car numbers to be given by a consecutive number for each vehicle allocation request, so as to transmit the requests to the on-vehicle terminals. When the vehicle allocation request is received, each one of the on-vehicle terminals allows moving state information to include the slip number and the loaner car number, so as to transmit the information to the vehicle allocation server. The vehicle allocation server acquires slip numbers of the respective on-vehicle terminals from moving state information, determines double vehicle allocation when the same slip numbers exist, and transmits a vehicle allocation cancel signal to the on-vehicle terminal other than the on-vehicle terminal with the greatest loaner car number between the on-vehicle terminals determined to be double vehicle allocation.SELECTED DRAWING: Figure 6

Description

  The present invention relates to a dispatch system, and is particularly applicable to a 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. Further, 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. The fusion of the wireless mobile communication system and the positioning system makes the data transmission system and the position management system of the mobile unit practical, and is used for the purpose of improving the efficiency of allocation of taxis and transportation vehicles through business radio and public radio.

  The AVM (Automatic Vehicle Monitoring) system for taxi dispatch using business wireless includes GPS satellites, a mobile station (taxi), a base station performing wireless communication with the mobile station, and a management center connected to the base station via a dedicated line. It consists of In such an AVM system for taxi allocation, a customer contacts the allocation center to convey his current position and necessary vehicle information, and requests allocation. In the dispatch center, the operator operates the dispatch terminal to transmit customer information and necessary vehicle information to the management center. The management center searches for the optimum vehicle from the collected mobile station position information in order to distribute the optimum vehicle according to the current position information of the customer, and the vehicle selected by the operator from among the searched vehicles Operate to allocate vehicles.

  A taxi dispatch system capable of efficiently dispatching 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 dispatch in the taxi dispatch system. FIG. 4 is a sequence diagram for explaining a case where the vehicle allocation fails because a signal does not reach the vehicle allocation server (AVM server) in the management center from the mobile station (in-vehicle terminal). In FIG.3 and FIG.4, the sequence diagram which shows the timing of transmission and reception between a dispatch terminal, an AVM server, a GW server, and a vehicle-mounted terminal is shown.

(Succession sequence)
First, the dispatch terminal first issues a dispatch request to the AVM server of the management center (S1). The AVM server searches for an optimal vehicle and makes a dispatch request to the on-vehicle terminal of the vehicle (S2). The GW server notifies the on-vehicle terminal of a vehicle allocation instruction based on the distribution request from the AVM server (S3).

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

  When the vehicle-mounted terminal receives the vehicle allocation information, it notifies the crew that a vehicle allocation request has been received. When the crew can go to the customer's location, he presses the "OK" button. When the crew presses the "OK" button, the on-vehicle terminal transmits a vehicle allocation completion signal to the AVM server via the GW server (S8, S9). When the AVM server receives the allocation approval signal, the AVM server transmits an acceptance approval signal (acknowledgement ACK) to the on-vehicle terminal via the GW server, and allocation is completed (S10, S11).

(Car dispatch failure sequence)
The case where the allocation failure in FIG. 4 occurs will be described. Steps S <b> 1 to S <b> 7 are the same as those in FIG. 3, and the description thereof will be omitted. When receiving the allocation information, the on-vehicle terminal performs a predetermined acceptance operation, and transmits an allocation completion signal to the AVM server via the GW server (S8). However, when the mobile station moves into the wireless blind area (for example, outside the communication area of the wireless base station), the AVM server can not receive the allocation confirmation information from the in-vehicle terminal. Therefore, since the AVM server can not receive the acknowledgment signal (S8), it can not determine whether the vehicle allocation information has reached the in-vehicle terminal, and thus determines that the vehicle allocation has failed. On the other hand, since the in-vehicle terminal can not receive the acknowledgment signal (acknowledgement ACK) from the AVM server, it can not determine whether the AVM server has received the acknowledgment signal, but in order to prevent the vehicle heading to the customer's location from being lost. It is determined that the vehicle allocation is completed.

Patent No. 5302832

  In the AVM system for taxi allocation, when the management center fails to receive the allocation confirmation signal from the mobile station as described above, the management center instructs the other mobile stations (taxi) to allocate the vehicle. Therefore, there has been a problem of double or multiple vehicle allocation in which a plurality of mobile stations (taxi) go to the same customer location.

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

  Other problems and novel features will be apparent from the description of the present specification and the accompanying drawings.

  The outline of typical ones of the present disclosure will be briefly described as follows.

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

  According to the above allocation system, the state of double allocation can be eliminated at an early stage.

FIG. 1 is a diagram showing a schematic configuration of a vehicle allocation system according to a first embodiment. FIG. 2 is a diagram showing a schematic configuration of a management center according to the first embodiment. It is a sequence diagram explaining the completion of dispatch. It is a sequence diagram explaining dispatch failure. FIG. 5 is a sequence diagram of vehicle allocation according to the first embodiment. FIG. 7 is a sequence diagram of vehicle allocation according to a second embodiment. FIG. 16 is a flowchart of an allocation cancellation process according to a second modification.

  Hereinafter, examples will be described using the drawings. However, in the following description, the same components may be assigned the same reference numerals and repeated descriptions may be omitted. In addition, although drawing may be represented typically compared with an actual aspect, in order to clarify description, it is an example to the last, and does not limit interpretation of this invention.

  An example of a configuration diagram of a vehicle allocation system according to a 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 a first embodiment.

(Configuration of dispatch system)
The dispatch system 1 is an AVM (Automatic Vehicle Monitoring) system for taxi dispatch using a wireless mobile communication system and a positioning system. The dispatch system 1 includes a management center 101, a plurality of wireless 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 dispatch center 107 having a plurality of dispatch terminals 106 (106-1, 106-2, ..., 106-M) It is configured using.

  Each wireless base station 102 has a communication area in which the local station can communicate. For example, the communication area 103-1 of the wireless base station 102-1 includes the mobile station 104 and the wireless base station 102 in the area. 1 indicates that communication can be performed.

  Each mobile station 104 can receive the position information from the GPS satellite 105 and obtain the position information (latitude, longitude) of the vehicle. 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 movement information of the mobile station 104 (vehicle).

  The management center 101 manages the mobile stations 104 by collecting location information and movement information of the mobile stations 104 present in the communication area 103 through each of a plurality of wireless base stations 102.

  The customer contacts the dispatch center 107 to make a dispatch request by communicating the location of the dispatch destination (for example, the current location of the customer) and the information of the desired vehicle.

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

  The management center 101 searches for (searches for) a suitable vehicle for dispatch from the collected location information of the mobile stations 104 according to the dispatch request received from the dispatch center 107, and moves the vehicle to the position instructed by the dispatch destination. Carry out the operation of dispatching.

  The customer accesses the management center 101 through the Internet using the taxi company's website or an application for dispatch request installed on various mobile terminals (mobile phone terminals and tablet terminals) that are generally marketed. A dispatch request can also be issued to the management center 101 without passing through the dispatch 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 wireless base station 102 having the communication area 103 in which the host vehicle is located.

  Also, the mobile station 104 periodically obtains the position information (latitude, longitude) of the own vehicle based on the information received from the GPS satellite 105, and information indicating the movement of the vehicle in which the mobile station 104 is deployed and The control center 101 is notified along with the identification information of the vehicle.

  The behavior of the vehicle includes "real vehicle", "empty vehicle", "vacant vehicle schedule", "payment", "rest", etc., and is set by a crew member operating the mobile station 104 deployed in each vehicle. The vehicles searched as allocation candidates are basically "empty vehicles" vehicles, but allocation candidates are also possible for vehicles with other statuses ("empty vehicles scheduled", "payment", "rest") that can be allocated substantially The vehicle may be searched as a vehicle of the above, and it may be set in advance according to the policy of the taxi company etc. which dynamic is to be searched as a vehicle of the vehicle allocation candidate.

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

  In addition, when the mobile station 104 ends the standby at the standby location, the mobile station 104 displays information indicating that the standby at the standby location is ended in response to the operation of the mobile station 104 by the crew. Information identifying the place 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 mobile phone terminal (for example, a smart phone) generally marketed and a tablet terminal having a wireless communication function can be used. You may use what installed the application for the dispatch system which implement | achieves 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, and in this example, an area information management unit 201 that stores and manages area information related to each vehicle allocation area, and vehicle information related to each vehicle And a vehicle information management unit 202 that stores and manages the information.

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

  The vehicle information of each vehicle managed by the vehicle information management unit 202 includes identification information of the vehicle, current position information of the vehicle, information indicating the waiting place when the vehicle is waiting at the waiting place, and the waiting order Information indicating the movement of the vehicle, information indicating a front end condition of the vehicle, information indicating a shift of a passenger / vehicle 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, and in this example, according to the input of the departure point and the arrival point, searching for a route connecting between these points and a distance indicator , A route distance, and an estimated travel time).

  The dispatch server 240 is a server that searches for a vehicle to be dispatched using the database server 200 and the map server 220. In this example, a vehicle suitable for dispatch is retrieved according to a dispatch request from a customer And a dispatch instruction unit 242 that issues a dispatch instruction to the vehicle (mobile station 104) retrieved by the candidate vehicle retrieval unit 241.

  When the candidate vehicle search unit 241 receives the allocation request from the customer, the candidate vehicle search unit 241 uses the allocation request as a search condition to access the area information management unit 201 and the vehicle information management unit 202, and distributes the destination specified by the allocation request. It is the area information of the dispatch area which includes the position of, and the area information of the application time zone including the current time (point of time of search). The candidate vehicle search unit 241 also searches for an empty vehicle vehicle or a standby vehicle with the highest priority and that is not in the exclusion area according to the priority order and exclusion area set in the area information, and the vehicles To be the target vehicle for dispatch (the most suitable vehicle for dispatch to the designated dispatch destination). Here, when a plurality of vehicles are designated by the dispatch request, the specified number of vehicles are searched and determined as vehicles to be dispatched.

  In addition, when the distance index about the position of the allocation destination and the position of each vehicle is required, the position information is provided to the map server 220, and the route search unit 221 calculates it, and the result is obtained. Used for vehicle search.

  In addition, when there is a request for pre-setting conditions such as vehicle characteristics (vehicle type, car body color, etc.) and crew characteristics (sex, age, etc.) in the allocation request, priority is given to the vehicle that satisfies the request. Do a vehicle search.

  The dispatch instruction unit 242 notifies the mobile station 104 deployed in the vehicle searched by the candidate vehicle search unit 241 of the location of the dispatch destination designated by the dispatch request, and dispatches the vehicle to that position. Carry out dispatch instructions.

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

(Delivery sequence 1)
FIG. 5 is a dispatch sequence diagram according to the embodiment. In FIG. 5, as described in FIG. 4, for example, when the AVM server 240 determines that “vehicle allocation failure” is made to the in-vehicle terminal 104-1, the vehicle allocation when transmitting a distribution request to the in-vehicle terminal 104-2, for example The sequence is shown. In addition, since the description to step S1-S8 is the same as FIG. 4, the description is abbreviate | omitted.

  In addition, when receiving an order from a customer and issuing a dispatch request from the dispatch terminal 106 to the AVM server 240 (S1), the AVM server 240 then creates reception information, stores it in the database server 200, and receives the reception information by the AVM system. Assign a unique document number. The AVM server 240 creates vehicle allocation information and manages the vehicle allocation state. The vehicle allocation information includes a slip number, an ordered number (allocation serial number), an allocated number (replacement vehicle number), a status (allocation status), an allocation list (vehicle number) and the like.

  After step S8, the AVM server 240 times out the reception of the acceptance signal from the on-board terminal 104-1 after a predetermined time has passed since the state in which the acceptance signal from the on-board terminal 104-1 has not been received (approval signal timeout) Then, the vehicle allocation request is issued to the next candidate, the on-vehicle terminal 104-2 (S22). That is, in order to re-search for an optimal vehicle in accordance with the current position information of the customer in the management center 101, the position information of the mobile stations 104 (104-2, 104-3, ..., 104-N) being collected is used. , Re-search for the optimum vehicle, and distribute the optimum vehicle re-searched to the current position of the customer. For example, it is assumed that the vehicle of the mobile station (vehicle-mounted terminal) 104-2 is newly selected as the optimal vehicle. In addition, when searching for a vehicle, you may make it search the vehicle more than the ordered number. It may be configured to select from among the plurality of searched vehicles based on the 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 selected by the determination of the operator, so that re-search time can be omitted.

  The AVM server 240 makes a dispatch 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 on-vehicle terminal 104-2 of the vehicle of the allocation instruction via the wireless base station 102 of the communication area 103 where the on-board terminal 104-2 exists. (S3). The in-vehicle terminal 104-2 having received the allocation instruction transmits an 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 on-board terminal 104-2 via the GW server 250 and the wireless base station 102 based on the vehicle allocation information acquisition request (S26, S27).

  When the vehicle-mounted terminal 104-2 receives the vehicle allocation information, it notifies the crew that a vehicle allocation request has been received. When the crew can go, press "OK". (If you can not go, press "impossible"). When the crew can go, pressing “OK” sends a dispatch completion signal to the AVM server 240 via the GW server 250 (S 28, S 29). When the AVM server 240 receives the allocation approval signal, the AVM server 240 sets the status (allocation status) to allocation completion, and transmits an approval acknowledgment signal (Ock ACK (OK)) to the on-board terminal 104-2 via the GW server 250, Dispatch to 104-2 is completed (S30, S31). By this, the vehicle allocation to the on-vehicle terminal 104-2 is established.

  Next, for example, it is assumed that the on-vehicle terminal 104-1 moves into the communication area 103 of the wireless base station 102, and the communication between the on-vehicle terminal 104-1 and the wireless base station 102 is recovered. In this case, the on-vehicle terminal 104-1 determines that the acceptance acknowledgment signal (acknowledgement ACK (OK)) from the AVM server 240 is timed out ((approval ACK timeout), and transmits the dispatch acceptance signal to the AVM server via the GW server 250. Retransmit to 240 (S40, S41) The AVM server 240 carries out the determination processing to determine double allocation In this case, since allocation to the on-vehicle terminal 104-2 is completed, double allocation is performed. It is determined that there is an acknowledgment signal (acknowledgement ACK (NG)) to the on-vehicle terminal 104-1 via the GW server 250. That is, the AVM server 240 transmits the acknowledge signal (acknowledgement ACK (acknowledgement ACK (NG)). By transmitting the NG)), the vehicle allocation cancellation process is executed to the on-board terminal 104-1. By the reception of), it is determined that the dispatch is not satisfied, and notifies the dispatch cancellation to the crew.

  As described above, the management center 101 sends, to the on-vehicle terminal 104, the first acknowledgment signal "Acknowledgement ACK (OK)" and the second acknowledgment signal "Acknowledgement ACK (NG)". Have a function to The first acceptance approval signal “acknowledgement ACK (OK)” is a signal for notifying the on-vehicle terminal (104-2) that has instructed the allocation of the allocation completion. The second acceptance approval signal “acknowledgement ACK (NG)” is a signal for notifying the vehicle-mounted terminal (104-1) instructed at one end of the vehicle allocation cancellation.

  Thus, the status of the management center 101 and the in-vehicle terminal 104 (104-1) can be confirmed by confirming from the in-vehicle terminal 104 (104-1) whether the AVM server 240 of the management center 101 is in double allocation. Can reduce the probability of the occurrence of a mismatch. In addition, the state of double or multiple dispatch can be eliminated early.

(Delivery sequence 2)
FIG. 6 is a dispatch sequence diagram according to the second embodiment. 6 differs from FIG. 5 in that steps S40 and S41) are deleted, and instead, steps S50 to S53 are added. As described in the first embodiment, only by confirming from the on-vehicle terminal 104 (104-1) whether or not double allocation has been made to the AVM server 240 of the management center 101 is a communication failure. Even if the signal is retransmitted, it may be considered that the signal does not reach the AVM server 240, and the possibility of dual vehicle allocation remains. Therefore, as in the second embodiment, it is preferable to monitor the double allocation at the management center 101 and add a mechanism for canceling the allocation to the on-vehicle terminal 104 from the management center 101 when the double allocation occurs. It is.

  The allocation sequence shown in FIG. 6 is for identifying a vehicle for which the allocation cancellation process has not been completed when there is a distribution number (arrangement instruction) equal to or more than the number ordered by the customer after allocation is completed. As a result, it is possible to reliably perform the vehicle allocation cancellation process. The vehicle allocation sequence may be automatically executed by the AVM server 240 of the management center 101 after the vehicle allocation is completed after receiving an order from the customer (step S31).

  In the case of FIG. 6, a substitute car number is added to the allocation information (slip data) managed by the AVM server 240, and slip data is created each time the allocation request is transmitted to the on-vehicle terminal (104) of the vehicle. The movement information transmitted by the terminal to the AVM server 240 is transmitted including the slip number recognized as received by the in-vehicle terminal, the vehicle allocation serial number, and the substitute car number. The slip number, the dispatch serial number, and the dispatch car number are referred to as dispatch key information.

  Here, the slip number is a control number assigned to each customer's order.

  The allocation serial number is a number given to each vehicle allocated for the customer's order. If the number of orders is two, data of the dispatch serial numbers 1 and 2 are generated.

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

  The movement information indicates the state of the taxi, such as "vehicle", "empty car", "rest", and the like. Basically, the vehicle allocated by the AVM server 240 is a candidate for an “empty” vehicle (a “vehicle” which is scheduled to be “empty” soon may be a candidate).

  The on-board terminal 104 (104-1, 104-2) transmits the movement information to the AVM server 240 at a predetermined time, traveling a certain distance, or at a timing when the movement information is changed (S50 to S53). The movement information of the in-vehicle terminal 104-1 is transmitted by the AVM server 240 at steps S50 and S51, and the movement information of the in-vehicle terminal 104-2 is transmitted by the AVM server 240 at steps S52 and S53.

  When double allocation occurs, movement information of the same slip number and allocation serial number is transmitted from the on-vehicle terminals (140) of a plurality of vehicles (S50-S53). Therefore, the AVM server 240 of the management center 101 monitors the movement information periodically (for example, every one minute), and determines whether or not movement data of the same slip number and allocation serial number exist in a plurality of vehicles. . That is, the AVM server 240 carries out a determination process of determining double vehicle allocation based on the reception of the movement information. As a result of the execution of the determination process, when the same slip number and dynamic data of the allocation serial number exist in a plurality of vehicles, leaving the one with the largest substitute car number, the allocation cancellation instruction to the on-vehicle terminal (104-1 The transmission cancellation process is carried out by transmitting (S42, S43). In the case where the number of ordered units is limited to one, or when an order from the same customer is assigned a different slip number for each unit, double allocation can be determined without assigning an allocation serial number. That is, when there is movement information of the same slip number, it is determined that double allocation has occurred, and an allocation cancellation instruction is transmitted to an on-board terminal other than the on-board terminal having the largest substitute car number.

  With the above configuration, if it is recognized that the on-vehicle terminal 104-1 is allocated, the AVM server 240 transmits the movement information including the slip number, the allocation number, and the substitute car number. But it will be recognizable.

  According to the second embodiment, since the in-vehicle terminal 104 is configured to periodically send the movement 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 do. By using this movement information, even after the end of the vehicle allocation sequence, the AVM server 240 can monitor double or multiple vehicle allocation, and can execute determination processing for determining double vehicle allocation. By automatically executing the allocation cancellation process from the AVM server 240 to the on-vehicle terminal 104, it is possible to save the operator's time and effort. By managing with the substitute car number, it is possible to decide the vehicle to be canceled by a simple determination flow.

  In addition, it is also possible to combine the dispatch sequence of FIG. 5 and the dispatch sequence of FIG.

(Modification 1)
FIG. 7 is a flowchart of an allocation cancellation process according to the first modification.

  In this case, the AVM server 240 creates and holds a list (allocation information) in which the slip number, the vehicle that has transmitted the allocation request, and the situation (acknowledgement, failure, time-out, etc.) are linked. A dispatch cancellation signal is transmitted to vehicles whose status is other than "OK".

  First, upon receiving an order from a customer, a dispatch request is issued from the 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 that is unique in the AVM system. The AVM server 240 creates vehicle allocation information and manages the vehicle allocation state. The vehicle allocation information includes a slip number, an ordered number (allocation serial number), an allocated number (replacement vehicle number), a status (allocation status), an allocation list (vehicle number) and the like.

  This flow may be automatically executed by the AVM server 240 of the management center 101, for example, after receiving an order from a customer and completing allocation (step S31). Alternatively, it may be automatically executed by the AVM server 240 of the management center 101 after receiving step S50 to step S53 of FIG. This flow starts after step S31 or step S53 (step S60).

  First, the database server 200 is accessed, the slip number is acquired from the allocation information for which allocation has been completed, and the ordered number, allocation number, allocation status, allocation list (vehicle number) are acquired for the slip number. Then, with the number of vehicles for which the dispatch status is other than "OK" as the number of dispatched vehicles, it is determined whether the ordered number matches the number of dispatched vehicles (step S61). Step S61 can be regarded as determination processing for determining double allocation. As a result of the determination, if the ordered number and the dispatched number match, it is determined that the operation is normal, and the flow ends. Here, normal means that there is no double or multiple dispatch situation.

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

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

  If (number of vehicles allocated-number of units ordered) is 0, it is determined that the vehicle allocation cancellation processing is completed, and the state of double or multiple vehicle allocation is resolved, and this flow ends.

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

  In step S63, it is determined whether the condition for the vehicle number (No. xx) in the allocation list is either OK or not (failure, timeout). If yes, the process moves to step S62. If it is other than OK (failure, time-out, etc.), the AVM server 240 sends an OK approval signal “OK ACK (NG)” to the vehicle number (No. xx), and executes the 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 a state where the allocation cancellation processing is completed, and the movement information is set to "empty car", for example.

  Thereafter, the process proceeds to step S62, and steps S63 and S64 are executed until (the number of allocated vehicles-the number of ordered units) becomes zero.

  The above flow is automatically executed by the AVM server 240 of the management center 101 to determine and identify a vehicle for which the dispatch cancellation process has not been completed, and transmits a dispatch cancellation signal “OK ACK (NG)”. . As a result, it is possible to reliably perform the allocation cancellation process while saving the time and effort of the operator, so that it is possible to quickly eliminate the state of double allocation or multiple allocation.

  In addition, it is also possible to combine the dispatch sequence of FIG. 5 and the dispatch cancellation process flow of FIG.

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

  It is possible to monitor double allocation or multiple allocation in the same manner as in the second embodiment. The detected result is notified to the dispatch terminal 106. In the notification method, the detection result is written to the database server 200, and the number of the slips is transmitted to the vehicle allocation terminal 106. On the operator side, when a slip for double allocation is generated, processing for opening the slip at the allocation terminal 106 (determination processing for determining double allocation) is performed. Exclusion processing is performed on the side of the database server 200 so that a plurality of operators do not open a slip, and the slip is assigned in a first-come-first-served manner.

  A slip is opened, and a vehicle for which delivery has been completed and a vehicle for which delivery has failed but key data of the slip number of the relevant slip has been displayed as dynamic data is displayed on a map. Among them, those that are double-dispatched can be identified by making the icon red. In addition, the route search from each vehicle to the destination is performed, and the distance to the destination and the estimated arrival time are displayed.

  The operator leaves the vehicle that is likely to arrive earliest from the estimated arrival time or the position on the map, performs cancellation processing for other vehicles, and issues a cancellation instruction ("OK ACK (NG)" signal) Sending). With regard to the vehicles for which the dispatch has been canceled, the completion of the dispatch cancellation is recorded in the dispatch data, and it is explicitly left that the dispatch cancellation processing has been executed. Also, when leaving a vehicle for which allocation has failed, the allocation state of the allocation data is changed from allocation failure to allocation completion. By doing so, it is possible to know which vehicle finally allocated.

  As mentioned above, although the invention made by the present inventor was concretely explained based on an example, the present invention is not limited to the above-mentioned embodiment and an example, and it can not be overemphasized that it can change variously .

101: management center 102 (102-1, 2, ..., L): wireless base station 103 (103-1, 2, ..., L): communication area 104 (104-1, 2, ... N): Mobile station (vehicle)
105: GPS satellite 106 (106-1, 2, ..., M): dispatch terminal 107: 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: Dispatch instruction unit 250: Gateway server (GW server)

Claims (6)

A dispatch server and a base station capable of communicating with on-vehicle terminals installed in each of a plurality of vehicles;
The allocation server transmits to the in-vehicle terminal the allocation request including at least a slip number and a substitute car number to be sequentially assigned for each allocation request.
When the vehicle-mounted terminal receives the allocation request, the on-board terminal transmits the movement information including the slip number and the substitute car number to the allocation server.
The allocation server acquires the slip number of each in-vehicle terminal from the movement information, and when there is the same slip number, determines that it is a double allocation, and among the in-vehicle terminals determined to be a double allocation, the substitute car number is the most A dispatch system that sends dispatch cancellation signals to on-board terminals other than large on-board terminals. In the dispatch system of claim 1,
The allocation server transmits, to the in-vehicle terminal, the allocation request including the allocation serial number assigned to each allocated vehicle by a serial number,
The in-vehicle terminal transmits the movement information including the allocation serial number to the allocation server.
The vehicle allocation system, wherein the vehicle allocation server determines that there is a double vehicle allocation when there are the same slip number and vehicle allocation serial number. A dispatch server and a base station capable of communicating with on-vehicle terminals installed in each of a plurality of vehicles;
The allocation server creates a list in which at least the slip number, the on-board terminal that has transmitted the allocation request, and the allocation status indicating whether allocation succeeded or failed, and allocation among the on-vehicle terminals in the list failed. A dispatch system that sends a dispatch cancellation signal to an on-vehicle terminal linked with a dispatch status indicating that. An allocation method for eliminating multiple allocation in an allocation system including an allocation server and a base station capable of communicating with in-vehicle terminals mounted in each of a plurality of vehicles.
The allocation request transmitted from the allocation server to the in-vehicle terminal includes at least a slip number and a substitute car number to be assigned by a serial number for each allocation request,
The movement information transmitted from the in-vehicle terminal to the allocation server includes the slip number and the substitute car number.
If the same slip number is included in the movement information, it is determined to be double allocation, and the allocation cancellation signal is sent to an on-vehicle terminal other than the on-vehicle terminal having the largest substitute car number among the on-vehicle terminals determined to be double allocation. How to dispatch. In the vehicle allocation method of claim 4,
The allocation request includes an allocation serial number assigned to each allocated vehicle in a serial number,
The movement information includes the vehicle allocation serial number,
A dispatch method in which it is determined that double dispatch is performed when the same slip number and dispatch serial number exist among the movement information. An allocation method for eliminating multiple allocation in an allocation system including an allocation server and a base station capable of communicating with in-vehicle terminals mounted in each of a plurality of vehicles.
Create a list linked with at least the slip number, the on-board terminal that has sent the allocation request, and the allocation status indicating whether allocation has succeeded or failed,
The vehicle allocation method of transmitting a vehicle allocation cancellation signal to the vehicle-mounted terminal associated with the vehicle allocation status indicating that the vehicle allocation has failed among the vehicle-mounted terminals in the list.

Images