JP6295088B2 - Dispatch system - Google Patents

Description

  The present invention relates to a vehicle allocation system, and more particularly to a vehicle allocation system capable of confirming a movement status of a vehicle to be picked up after the user makes a reservation for vehicle allocation until the vehicle to be picked up arrives at the user's boarding position.

In recent years, a system capable of requesting taxi dispatch using a user-owned mobile terminal has been used.
For example, an empty taxi that uses GPS (Global Positioning System) to recognize the current location of a taxi that can be dispatched and the user who requested the dispatch, determines the taxi to be dispatched, and then combines the information on the taxi to be dispatched with map information A system for transmitting guidance to a terminal device of a user is used (for example, Patent Document 1).

  In addition, a system that calculates the expected arrival time of a taxi to be dispatched and displays it on the user's mobile terminal in consideration of the convenience of the user who requested the dispatch (Patent Document 2), the estimated arrival time of the taxi to be dispatched And a system that notifies the user of the current location of the taxi, map information including the location of the taxi determined to be dispatched and the expected location of the taxi is distributed to the mobile terminal owned by the user and the crew terminal of the taxi to be dispatched. When the taxi and the taxi approach a certain distance, data communication and calls between the two parties are permitted, and the entire display screen of the user's mobile terminal is illuminated with a specific color so that the crew can easily find passengers A system (Patent Document 3) is proposed.

JP 2009-64072 A JP 2004-157698 A JP 2012-88925 A

Using the conventional system as described above, there is an advantage that the user can request a taxi dispatch anywhere and anytime by using his / her portable terminal, but there are also the following problems .
When only the estimated arrival time of a taxi to be dispatched is notified to the user, the user may be unsure as to how far the taxi is currently coming or whether it will arrive by the estimated arrival time.
Even if the current taxi location is displayed, if there is an error in the GPS location information, the current taxi location is not clearly displayed on the map. In the case of a large road with lanes, it may not be clear which direction of travel should wait at the position facing the lane.

Furthermore, when the current position of the user and the taxi is acquired by GPS and displayed in the map display, the current position where the user is present is always acquired by the system, so the user's action (until the taxi arrives at the boarding position ( (Movement history) can be monitored by a third party, which is not preferable from the viewpoint of personal information protection.
Therefore, the present invention has been made in view of the above circumstances, and after the user makes a taxi dispatch reservation, the traveling situation of the incoming taxi until the arrival taxi arrives at the boarding position is determined. It is an object of the present invention to provide a dispatch system that can be easily confirmed by a terminal.

The present invention is a vehicle allocation system in which a user terminal owned by a user, an in-vehicle terminal mounted on a vehicle, and a vehicle allocation management server are connected to be communicable with each other via a network, the user terminal being a vehicle A reservation request unit that transmits a vehicle allocation reservation request that requests the vehicle to be allocated at the user's desired boarding position and boarding time to the vehicle allocation management server, and the in-vehicle terminal acquires the current position of the vehicle A current position acquisition unit, a current position of the acquired vehicle, and a vehicle pickup start unit that transmits to the vehicle allocation management server the vehicle pickup start information indicating that the vehicle pick-up position starts in response to the vehicle reservation request And the vehicle allocation management server inquires of the reservation reception unit that receives the vehicle allocation reservation request and an in-vehicle terminal mounted on a predetermined vehicle whether or not the vehicle can be picked up. A Geisha arrangements unit reservation is judged to be satisfied when the Geisha friendly information is transmitted to indicate that the vehicle-mounted terminal is capable of Geisha, when receiving a Geisha start information from the vehicle terminal, from the vehicle terminal Using the current position of the vehicle that has been sent and the boarding position included in the dispatch reservation request, predicting the route from the current position of the vehicle to the boarding position, on which the receiving vehicle that has made the reservation travels, predicts the incoming car An incoming vehicle status confirmation unit that generates a route, and an incoming vehicle information generation unit that transmits incoming vehicle information including the current position of the incoming vehicle and the generated predicted incoming vehicle route to the user terminal. A vehicle allocation system is provided.

  According to the present invention, since the vehicle reception information including the current position of the vehicle being picked up and the predicted arrival route from the current position to the boarding position is transmitted to the user terminal, the user who owns the user terminal receives the received vehicle pickup information. By confirming, it is possible to easily confirm the current traveling state of the vehicle being picked up, and to wait in peace until the vehicle being picked up arrives at the boarding position.

It is explanatory drawing of schematic structure of the vehicle allocation system of this invention. It is a block diagram of a configuration of an embodiment of a user terminal UTE according to the present invention. It is a block diagram of an embodiment of the in-vehicle terminal CTE of the present invention. It is a structure block diagram of one Example of the vehicle allocation management server SV of this invention. It is a flowchart of one Example of the reservation process etc. in the user terminal UTE of this invention. It is a flowchart of one Example of the pick-up process etc. in the taxi vehicle-mounted terminal CTE of this invention. It is a flowchart of one Example, such as a reservation in the dispatch management server SV of this invention, and an incoming vehicle management process. It is explanatory drawing of one Example of the communication sequence in the user terminal UTE of this invention, the vehicle allocation management server SV, and the vehicle-mounted terminal CTE.

The best mode for carrying out the present invention will be described below with reference to the drawings. However, this does not limit the present invention.
<Schematic configuration of the dispatch system>
FIG. 1 is an explanatory diagram of an overall configuration showing an outline of a vehicle allocation system according to the present invention.
The vehicle allocation system according to the present invention includes a mobile terminal 100 owned by a user (hereinafter referred to as a user terminal or UTE), a terminal 200 mounted on the vehicle (hereinafter referred to as an in-vehicle terminal or CTE), a management center, and the like. The vehicle allocation management server 300 (hereinafter referred to as a server or SV) installed in the network is connected via a network 4 such as the Internet.

The connection with the network 4 may be performed by wired communication using a wired cable, but since the user terminal UTE and the in-vehicle terminal CTE are both used by moving, they are connected to the network 4 by wireless communication. It is preferable.
The connection protocol for wireless communication and the data communication protocol are not particularly limited, and any currently used protocol may be used.

The user terminal UTE is a portable information communication terminal such as a mobile phone, a smart phone, and a tablet terminal, and includes a program for realizing a vehicle allocation reservation function described later.
The in-vehicle terminal CTE is an information communication terminal mounted on a vehicle, for example, a taxi, and includes a program that realizes a reception function for guiding the vehicle to a boarding position requested in response to a reservation for dispatch.

The vehicle allocation management server SV stores reservation information and vehicle pickup management information, accepts vehicle allocation reservations from the user terminal UTE, selects a vehicle to be picked up, and travels the vehicle until the vehicle arrives at the requested boarding position. It is an information management device that grasps the situation and controls various information transmitted to and received from each terminal (UTE, CTE).
In particular, in the server SV of the present invention, in order to always grasp the information of the current position where the vehicle is traveling, the in-vehicle terminal CTE is equipped with a GPS receiver, and the vehicle current position information calculated from the received GPS signal is obtained. , It shall be transmitted periodically from the CTE to the SV.

The vehicle allocation system of the present invention guides the vehicle to be picked up to the boarding position requested by the user in the following general steps, for example.
Step 1: When a user inputs a vehicle allocation reservation in the UTE, a vehicle allocation reservation request including reservation information is transmitted from the UTE to the SV. The transmitted reservation information includes, for example, information such as a reservation ID, a boarding time, and a boarding position.
Step 2: The SV searches for a vehicle that can be picked up (hereinafter also referred to as a taxi) based on the received reservation information, and inquires whether or not the pick-up is possible from the CTE mounted on the selected picking-up vehicle. Send information (incoming vehicle inquiry information).
Step 3: In a vehicle equipped with a CTE that has received the incoming vehicle inquiry information from the SV, it is determined whether or not the driver of the vehicle can pick up the vehicle. Repayable information) to the SV.
Step 4: The SV considers that the reservation has been established by receiving the information on whether to accept the vehicle, and transmits information (reservation establishment information) indicating that the reservation has been established to the UTE and the CTE.

Step 5: In the CTE that has received the reservation establishment information, if the vehicle is an empty vehicle, or after the vehicle can actually be picked up, the incoming vehicle start information indicating that the vehicle will start to the reserved boarding position from now on. Send to SV.
Step 6: In the SV, after receiving the pickup start information, using the information on the current position of the vehicle to be picked up and the information on the reserved boarding position, the route to the pickup and the arrival time are predicted, and the pickup information To the UTE. The incoming vehicle information includes, for example, the current position of the vehicle, an incoming vehicle predicted route, and an estimated arrival time.
Step 7: In the UTE that has received the pick-up information, based on the pick-up information, the current position of the pick-up vehicle, the predicted arrival time, the predicted pick-up route on which the vehicle travels, etc. are displayed together with a map on the display screen provided in the UTE. . Until the incoming vehicle arrives at the boarding position, the current position of the vehicle, the predicted arrival route, and the predicted arrival time are updated and displayed in substantially real time.

Step 8: When the vehicle being picked up arrives in the vicinity of the boarding position, information (arrival information) indicating the arrival is transmitted from the CTE to the SV.
Step 9: The SV transmits information indicating that the vehicle has arrived at the boarding position (vehicle arrival completion information) to the UTE based on the received arrival information.
Step 10: In the UTE that has received the vehicle arrival completion information, information (vehicle arrival notification) indicating that the vehicle has arrived at the boarding position is notified to the user possessing the UTE.
Step 11: After that, when the user finds an incoming vehicle at the boarding position and actually gets on the vehicle, information indicating that the user's boarding is completed (boarding completion notification) is transmitted from the CTE to the SV. .
Step 12: After receiving the boarding completion notification, the SV transmits information indicating that the reserved vehicle allocation has been completed (vehicle allocation completion notification) to the UTE. In the UTE, when the vehicle allocation completion notification is received, a display indicating that the reserved vehicle allocation is completed is displayed, and a series of vehicle allocation reservations is completed.

  The above is the outline steps of the vehicle allocation system of the present invention, but this series of steps is only one embodiment. Such a dispatch system is realized by a system configuration as described below and transmission / reception of various information.

<Configuration of user terminal UTE>
FIG. 2 shows a configuration block diagram of an embodiment of the user terminal UTE100 in the present invention.
The user terminal UTE mainly includes a control unit 101, a display unit 102, an input unit 103, a communication unit 104, a reservation request unit 105, an incoming vehicle information processing unit 106, a current position acquisition unit 107, a GPS receiver 108, and a storage unit 110. .

As the user terminal UTE, a mobile terminal such as a mobile phone or a smart phone currently used can be used. In this case, for the display unit, the input unit, the communication unit, the current position acquisition unit, and the storage unit, You may use what is already provided in.
Here, the reservation request unit 105, the incoming vehicle information processing unit 106, and various types of information stored in the storage unit 110 are functional blocks unique to the present invention.

The control unit 101 is a part that controls the operation of each functional block of the UTE, and is mainly realized by a microcomputer including a CPU, a ROM, a RAM, an I / O controller, a timer, and the like.
The CPU realizes functions such as vehicle allocation reservation of the present invention by organically operating various hardware based on a program stored in a ROM or the like.

The display unit 102 is a part that displays a map, the status of a taxi to be picked up, a function selection screen, a setting screen for reservation input, and an LCD or an organic EL display is used.
For example, as will be described later, on the display unit 102, the current position of the incoming taxi and the predicted incoming route are included in the map information, together with the map information, using the incoming vehicle information transmitted from the SV. The
The input unit 103 is a part where the user inputs various setting information, inputs for selecting functions, and the like, and a keyboard, a mouse, a touch panel, or the like is used.
For example, the user inputs the boarding position and boarding time desired by the user through the input unit 103.
In the case where the user terminal is a portable terminal, it is preferable to use an LCD that is a display unit and a touch panel that are overlapped with each other, or an LCD and a touch panel that are integrally formed.

The communication unit 104 is a part that performs data communication with the SV via the network 4 and corresponds to the first communication unit described above. As a communication method, either wired communication or wireless communication currently used may be used. However, when the user terminal UTE is a mobile terminal, it is preferable to use wireless communication.
The reservation request unit 105 is a part that requests the SV to make a reservation for dispatch. Specifically, a dispatch reservation request for requesting that a taxi be dispatched at the boarding position and boarding time desired by the user who is the owner of the UTE is transmitted to the SV.
As will be described later, for example, when a user who is the owner of the UTE inputs information including a boarding position, a boarding time, and the like using the input unit 103 and inputs an instruction meaning a reservation request, dispatch reservation information Is transmitted from the UTE to the SV.

The incoming vehicle information processing unit 106 is a part for confirming the current state of the incoming vehicle from when the vehicle allocation reservation is accepted until the taxi actually arrives at the boarding position.
For example, various kinds of information sent from the SV are checked, and the display unit 102 is made to display a reservation establishment, a map display showing the current position of the incoming taxi, and a map display of the predicted incoming route for the incoming taxi.
The current position acquisition unit 107 is a part that acquires information (geographic information) on the position where the user who owns the UTE is currently located.
The GPS receiver 108 is a part that receives a GPS signal and outputs position information (latitude, longitude) on the earth from the received signal.
The current position acquisition unit 107 specifies the current position 141 of the user by using the position information output from the GPS receiver 108 and the map information 142 stored in the storage unit 110.
The user's current position 141 may be shown in a map displayed on the display unit 102.

The storage unit 110 stores information and programs used when executing the functions of the UTE of the present invention, and includes a semiconductor storage element such as ROM and RAM, a storage device such as HDD and SSD, and other storage media. Used.
The storage unit 110 stores, for example, reservation information 120, incoming vehicle information 130, a user current position 141, display map information 142, and the like.
The reservation information 120 is information generated when the user inputs a vehicle allocation reservation, and includes, for example, a reservation ID 121, a boarding time 122, a boarding position 123, and the like.
The reservation ID 121 is a reservation identification number, and for example, data including a plurality of numeric strings and characters such as a user name is given.
The boarding time 122 is information input by the user, and means a time when the user wishes to board a taxi reserved by the user. Therefore, a time later than the current time is input.
The boarding position 123 is information input by the user, and means a place where the user wants to board a taxi reserved by the user.

As the boarding position 123, a geographical address may be input as characters. However, when a touch panel is used, a map is displayed on the display unit 102, and the user selects and inputs a desired position (touch input). The boarding position may be input.
The incoming vehicle information 130 is information indicating the status of a taxi (referred to as an incoming taxi) coming to the user, and includes, for example, a taxi current position 131, an incoming arrival prediction route 132, an expected arrival time 133, and the like.
The incoming vehicle information 130 is information that is periodically transmitted from the SV, or is transmitted from the SV when the route of the incoming taxi is changed or based on a request from the UTE.

The taxi current position 131 indicates information on the position where the incoming taxi is currently located, and the current position of the incoming taxi is displayed on the map using this information.
As will be described later, the predicted arrival route 132 is that the taxi will travel based on the predicted traveling route of the incoming taxi generated by the SV, that is, the current position of the taxi and the information on the boarding position specified by the user. It is information indicating the route.
In addition to the current position 131 of the taxi, this incoming train prediction route 132 is also displayed on the map.
By displaying the predicted arrival route 132 in the map displayed on the display unit of the UTE, the user can know which route the incoming taxi travels, and in which direction with respect to the specified boarding position. It ’s easy to see where you ’re coming from before you arrive. Therefore, since it was discovered that the taxi had arrived in the opposite lane, it was possible to wait in peace without having to rush across the lane and move to the opposite lane.

The estimated arrival time 133 is the time at which the incoming taxi will arrive at the boarding position designated, and is the time predicted in the SV.
This time 133 is also displayed somewhere on the display screen of the display unit 102.
Since at least these three pieces of information (131, 132, 133) are displayed on the display unit 102 of the UTE, the reserved user can wait for a taxi without annoyance as compared with the case where nothing is displayed. Can do.
Also, you can know the approximate arrival time, so if you have enough time to arrive, you do not have to stay at the boarding position and wait for a while, leaving the boarding position and doing other things. It is also possible to return to the boarding position by the estimated arrival time.

As described above, the user current position 141 is information acquired by the current position acquisition unit 107, and the user may move. Therefore, the user current position 141 is preferably acquired periodically or in real time.
Moreover, in this invention, it is not necessary to transmit this user present position 141 to SV or CTE. Therefore, the current position and behavior of the user are not known to the SV operator or taxi driver, and personal information can be protected.
Further, as for the reservation ID 121 transmitted to the server, personal information can be further protected by using a simple numeric string that does not include information for identifying an individual.
The display map information 142 is map information stored in the storage unit 110 in advance, and includes information that can be navigated in addition to information such as roads, place names, buildings, and intersections.
This information 142 is displayed on the display unit 102, and the acquired arrival information 130 is also displayed at a corresponding position on the map.

<Configuration of in-vehicle terminal CTE>
FIG. 3 shows a configuration block diagram of an embodiment of the in-vehicle terminal CTE 200 according to the present invention.
In FIG. 3, CTE mainly includes a control unit 201, a display unit 202, an input unit 203, a communication unit 204, a current position acquisition unit 205, an incoming / outgoing vehicle determination unit 206, an incoming vehicle start unit 207, an arrival processing unit 208, and a boarding processing unit. 209 and a storage unit 220.
The control unit 201 is a microcomputer that executes each function. The display unit 202 is an LCD or an organic EL display that displays map information and the like. The communication unit 204 corresponds to the second communication unit described above, and is a part that performs data communication with the SV wirelessly. The current position acquisition unit 205 is a part that uses the GPS signal received by the GPS receiver 210 to acquire information on the current position 241 of the taxi on which the CTE is mounted and store it in the storage unit 220.

The vehicle acceptability determination unit 206 is a part that receives the vehicle inquiry information sent from the SV and determines whether or not it is possible to go to the boarding position reserved for dispatch by the reserved boarding time. .
Whether or not the vehicle can be picked up is determined by the driver of the taxi equipped with the CTE. As a determination material for making the determination, the reservation information 230 included in the incoming vehicle inquiry information is displayed on the display unit 202, and an inquiry screen for requesting whether or not to accept is displayed on the display unit 202. The driver looks at the screen display and sees the current driving situation (for example, the current position of the taxi, the degree of congestion on the road, the direction of travel, the current destination of the passenger if there is a passenger on board) In consideration of the scheduled arrival time at the destination), it is determined whether or not the reserved position can be picked up, and whether or not the pick-up can be picked up is input using the input unit 203.
In addition, the vehicle acceptability determination unit 206 transmits the input information indicating whether the vehicle is accepted (acceptance information or inaccessibility information) to the SV. For example, when the driver inputs that means that the vehicle can be picked up, it is determined that the vehicle can be picked up, and the information on whether the vehicle can be picked up is transmitted to the SV.

In addition, in CTE, when it can be determined that the vehicle cannot be picked up clearly using the received reservation information 230 and the information indicating the current driving situation, the information indicating that the vehicle cannot be picked up automatically is inquired without inquiring the driver. You may transmit to SV.
In addition, if the taxi is currently in an empty state and you are traveling in a position that is very close to the boarding position so that you can go to the boarding position immediately, you can check the driver and send the information that you can receive to the SV. Good.

In response to the vehicle allocation reservation request, the incoming vehicle start unit 207 is a part that transmits to the SV information (incoming vehicle start information) indicating that the incoming vehicle travel to the reserved boarding position is started.
In order to start traveling for an incoming vehicle, in order to make it clear that the vehicle is going to the incoming vehicle, it is preferable that the driver himself / herself uses the input unit 203 to input that means starting an incoming vehicle. Therefore, after confirming that there has been a driver's incoming start input, the incoming start unit 207 transmits incoming start information to the SV.
If the taxi is an empty car, the information on the arrival of the vehicle will be sent to the SV immediately in response to the inquiry from the SV, and the reservation will be established. Sent.
However, if the passenger is still in the boarding state, the vehicle will travel for a while, and after the passenger gets off at the destination, the driver will receive the start information to the SV by making an input indicating that the driver will start the pickup. Will be.

The arrival processing unit 208 is a part that transmits information indicating arrival (arrival information) to the SV when the taxi arrives at the reserved boarding position.
Whether or not the arrival position is determined by, for example, comparing information on the current position acquired by the current position acquisition unit 205 with information on the boarding position 233 included in the reservation information 230 received and stored in the storage unit 220. If the position information error is less than or equal to a predetermined value (for example, several meters), it may be determined that it has arrived.

The boarding processing unit 209 is a part that transmits to the SV information (boarding completion notification) indicating that the reserved user has actually boarded the taxi.
The boarding processing unit 209 also checks whether there is an input indicating that the user has boarded. When the user gets in, for example, when the driver inputs using the input unit 203 to indicate that the user has boarded, a ride completion notification is transmitted to the SV.

The storage unit 220 is a part that stores information and programs necessary for executing the CTE function. For example, the received reservation information 230, the taxi current position 241, and the display map information 242 are stored.
The reservation information 230 includes a reservation ID 231, a boarding time 232, and a boarding position 233, and may be the same information stored in the UTE or SV.
The display map information 242 is so-called navigable map information, and when displayed on the display unit 202, information such as the current position of a taxi and a reserved boarding position is also displayed in the map.

<Vehicle allocation management server SV>
FIG. 4 shows a configuration block diagram of an embodiment of the vehicle allocation management server SV300 in the present invention.
In FIG. 4, the vehicle allocation management server SV mainly includes a control unit 301, a display unit 302, an input unit 303, a communication unit 304, a reservation reception unit 305, an incoming vehicle arrangement unit 306, an incoming vehicle state confirmation unit 307, an incoming vehicle information generation unit 308, A storage unit 310 is provided.
The control unit 301, the display unit 302, the input unit 303, and the communication unit 304 are functional blocks similar to the above-described UTE and CTE. The communication unit 304 corresponds to the third communication unit described above, and is a part that communicates with the UTE and the CTE.

  The reservation receiving unit 305 is a part that receives a vehicle allocation reservation request transmitted from the UTE, and is a part that acquires the reservation information 320 included in the request and stores it in the storage unit 310.

When the reservation information 320 is received, the pick-up arrangement section 306 searches and selects a taxi that can be picked up, and requests whether or not the pick-up is possible to the CTE mounted on the selected taxi (incoming car inquiry request). Is the part to send.
The incoming vehicle inquiry request includes incoming vehicle inquiry information. For example, the received reservation information 320 is transmitted to the CTE as it is.
In addition, it is confirmed whether a response is returned from the CTE in response to a request for an incoming call, and it is determined whether or not the selected taxi can receive an incoming call.
When the CTE that has made the inquiry transmits a response information indicating that the vehicle can be picked up as a response, the selected taxi can be picked up and it is determined that the reservation has been made. That is, a taxi to be picked up is determined and a reservation is established. When the reservation is established, reservation establishment information indicating that the reservation has been established is transmitted to the user terminal UTE of the user who has transmitted the dispatch reservation request and the CTE of the receiving taxi that has transmitted the acceptance information.

On the other hand, if the CTE has received information indicating that the vehicle cannot be picked up, the selected taxi is determined not to be picked up, and another taxi that can be picked up is searched again.
Here, at the time of searching, in order to determine whether or not the vehicle can be picked up, for example, the current taxi position sent from the CTE of each taxi and the boarding position of the received reservation information can be used.
In this case, if the current taxi position is within a predetermined distance from the boarding position, it may be determined that the taxi can be picked up.
Further, whether or not each taxi is currently in an empty state may be inquired of the CTE of each taxi, and if it is an empty vehicle, it may be selected as a candidate that can be picked up.
Furthermore, the time difference between the boarding time of the received reservation information and the current time may be used to determine the predetermined distance. If the time difference is long, the predetermined distance may be set long. If the time difference is short, the predetermined distance may be set short.

The reception status confirmation unit 307 receives the reception information from the CTE, that is, based on information sent from the taxi heading to the reception until the boarding is completed after the reservation is established and the reception starts. The part that checks the status of the taxi.
For example, it checks whether or not a reception start information, taxi arrival information, and boarding completion notification transmitted from the CTE of the reception taxi are received.
In addition, using the current location of the incoming taxi sent from the CTE and the boarding location information included in the dispatch reservation request, the taxi arrival time can be predicted and the incoming taxi can be found from the current location to the location of the taxi. A process for predicting a travel route (passing vehicle predicted route) that is considered to travel is performed. That is, the calculation of the estimated arrival time 334 and the generation of the predicted arrival route 333 are performed almost in real time and are updated periodically.
After the generation of the predicted arrival route, if the current position of the latest taxi transmitted from the CTE of the incoming taxi is out of the predicted arrival route stored in the storage unit 310, the current taxi current Using a position and the boarding position memorize | stored in the memory | storage part 310, regeneration of a new prediction route and recalculation of estimated arrival time are performed.

When the SV receives the taxi arrival information, the SV transmits taxi arrival completion information indicating that the taxi has arrived at the boarding position designated by the user to the UTE.
Further, when the boarding completion notification is received, the dispatching completion notification indicating that the dispatching is completed and a series of the dispatching reservation processing is completed is transmitted to the UTE.

The incoming vehicle information generation unit 308 is a part that generates information (incoming vehicle information) indicating the current situation of the incoming taxi and transmits it to the UTE.
The incoming vehicle information transmitted to the UTE includes, for example, an incoming vehicle predicted route generated by the incoming vehicle status confirmation unit 307, an estimated arrival time, a current taxi position, and the like.
As described above, after the arrival status confirmation unit 307 receives the arrival start information from the CTE, it uses the latest acquired taxi position information to search for the expected arrival route and calculates the estimated arrival time. The incoming car information is generated by the incoming car information generating unit 308 and transmitted to the UTE.

The storage unit 310 stores information and programs necessary for executing the SV function.
In the storage unit 310, for example, reservation information 320, incoming vehicle management information 330, and usage status information 340 are stored.
These pieces of information are preferably stored for each taxi.
For example, when the server SV is installed in one taxi company, each piece of information is stored for each taxi owned by the taxi company.
The reservation information 320 is reservation information included in a vehicle allocation reservation request transmitted from the UTE, and includes a reservation ID 321, a boarding time 322, and a boarding position 323, similar to the UTE.

The incoming vehicle management information 330 stores information indicating the incoming state of a taxi that has been reserved and will be picked up.
The incoming vehicle management information 330 includes, for example, a taxi identification ID 331, a taxi current position 332, an incoming vehicle predicted route 333, an estimated arrival time 334, an incoming vehicle start flag 335, an arrival completion flag 336, and a boarding completion flag 337.
The taxi current position 332 is always updated to the latest one according to information sent from the CTE.
The predicted arrival route 333 is a route generated by the reception state confirmation unit 307, and is a route searched using the received boarding position 323 as the destination and the taxi current position 332 as the search start position. However, if the latest taxi current position 332 deviates from the predicted route that was searched immediately before, the search start position is changed to the latest taxi current position, the route is searched again, and a new predicted arrival taxi route Is generated.

  Estimated arrival time 334 is obtained by setting an appropriate vehicle speed for the generated predicted arrival route 332, calculating the time required to travel the route, and adding the time to the current time. It is. This estimated arrival time 334 may change when the predicted arrival route is changed, and also changes depending on the acquired road congestion information.

The incoming vehicle start flag 335 is information indicating whether or not incoming vehicle start information has been received from the CTE.
For example, it is set to an initial value (for example, zero) at the time of reservation establishment, and remains zero even when no arrival start information is received. 1).
The incoming vehicle information generation unit 308 transmits the incoming vehicle information to the UTE after confirming that the value of the incoming vehicle start flag 335 is 1.

The arrival completion flag 336 is information indicating whether taxi arrival information has been received from the CTE. For example, it is set to an initial value (for example, zero) at the time of reservation establishment, and is set to a numerical value (for example, 1) indicating arrival when taxi arrival information is received.
After the arrival status confirmation unit 307 confirms that the arrival completion flag 336 is set to 1, the arrival state confirmation unit 307 transmits a taxi arrival completion to the UTE.

The boarding completion flag 337 is information indicating whether or not a boarding completion notification is received from the CTE.
For example, it is set to an initial value (for example, zero) at the time of reservation establishment, and is set to a numerical value (for example, 1) indicating that the boarding is completed when a boarding completion notification is received.
After confirming that the boarding situation confirmation unit 307 has this boarding completion flag 337 set to 1, a vehicle dispatching completion notification is transmitted to the UTE.

The usage status information 340 is information indicating the current usage status of each taxi, and stores, for example, information for distinguishing between “empty vehicle”, “ride”, and “arrival”.
“Empty” indicates that there are currently no passengers, “Ride” indicates that the passenger is currently on board and is traveling toward the destination, It shows that the user is currently traveling toward the boarding position designated by the user who made the reservation.

(First embodiment)
<Vehicle allocation reservation process and arrival check process>
The following shows the operation of each device until the reservation is made after the user makes a taxi dispatch reservation by the UTE, the incoming taxi travels to the boarding position designated by the user, and the user gets into the incoming taxi. A flowchart and a communication sequence will be described.
FIG. 5 shows a flowchart of an embodiment of the user terminal UTE.
FIG. 6 shows a flowchart of an embodiment of the in-vehicle terminal CTE.
FIG. 7 shows a flowchart of an embodiment of the server SV.
FIG. 8 shows an example of a communication sequence of UTE, CTE, and SV.

<Reservation processing in UTE>
In FIG. 5, first, in step S <b> 1, the UTE control unit 101 checks whether or not there is an input from the user requesting start of reservation for dispatch. If not, step S1 is looped. If there is a reservation start input, the process proceeds to step S2.
When the user wants to reserve a vehicle allocation, the user performs a predetermined input operation corresponding to the vehicle allocation reservation request using the input unit 103.
In step S2, a reservation screen for inputting information for vehicle allocation reservation is displayed on the display unit 102.
In step S3, the reservation information 120 input by the user is stored in the storage unit 110.
Here, for example, the user inputs a desired boarding position and boarding time. The input boarding position 123 and boarding time 122 are stored as one piece of reservation information 120 with a reservation ID 121 made up of an appropriate numeric string.

In step S4, the reservation request unit 105 transmits a reservation request including the stored reservation information 120 to the SV. This corresponds to step U01 of the communication sequence in FIG.
In step S5, the control unit 101 checks whether or not the reservation establishment information transmitted from the SV is received. If the reservation establishment information is received, the process proceeds to step S6, and if not, the process proceeds to step S13.
In step S6, a screen indicating that the reservation has been established is displayed on the display unit 102. This corresponds to step U02 in the sequence of FIG.

In step S13, if information indicating that the reservation has not been established (reservation failure information) is received, the process proceeds to step S14, and if not, the process proceeds to step S15.
In step S14, the display unit 102 displays a screen indicating that the reservation has not been established, and the process returns to step S1.
In step S15, after the reservation information 120 is transmitted to the server SV, it is checked whether or not a predetermined time has elapsed. If the time has elapsed and timed out, the process returns to step S1. If the predetermined time has not elapsed, the process returns to step S5.

In step S7, the incoming vehicle information processing unit 106 checks whether or not incoming vehicle information is received from the SV. If it is received, the process proceeds to step S8, and if not, step S7 is looped.
In step S <b> 8, the incoming vehicle information processing unit 106 acquires the current taxi current position 131, the predicted incoming vehicle route 132, and the estimated arrival time 133 from the received incoming vehicle information, and includes the current taxi current location 131 and the incoming vehicle in the display map information 142. The predicted route 132 is combined with the corresponding position, and a map is displayed on the display unit 102. This corresponds to step U03 in the sequence of FIG.
Further, the current position of the UTE acquired by the current position acquisition unit 107 of the UTE may be displayed in the displayed map.
By viewing this map, the user can grasp the current position of the incoming taxi and the predicted route that the incoming taxi will come from the current position to the boarding position designated by the user.

In step S9, the vehicle information processing unit 106 checks whether or not the taxi arrival completion sent from the server is received. If the taxi arrival completion is received, the process proceeds to step S10, and if not, the process returns to step S7.
After returning to step S7, when receiving information including only taxi current position information is received, a map indicating the current position of the new taxi is displayed. This corresponds to step U04 in the sequence of FIG.
In addition, when the incoming taxi has deviated from the predicted route and new incoming information including the predicted incoming route and the estimated arrival time is received, the changed predicted incoming route and estimated arrival time are displayed on the map. . This corresponds to step U05 in the sequence of FIG.
By the loop of steps S7, S8 and S9, the current position of the taxi that changes every moment, the predicted travel route, and the estimated arrival time are periodically updated until the incoming taxi arrives at the designated boarding position. Or updated display on the map in near real time.

In step S10, the user is notified that the taxi has arrived at the boarding position designated by the user. For example, in the map displayed on the display unit 102, the current position where the taxi has arrived is displayed blinking.
Alternatively, the arrival may be notified by outputting a sound indicating arrival, blinking light, or vibrating the UTE main body. This corresponds to step U06 in the sequence of FIG.
In step S11, the vehicle information processing unit 106 checks whether or not a boarding completion notification is received from the server. If received, the process proceeds to step S12, and if not, the process returns to step S10.
In step S12, a notification indicating that reservation dispatch has been completed is performed. For example, the display unit 102 displays information indicating the completion of the reservation dispatch. Or you may notify that reservation dispatch was completed by other methods, such as an audio | voice, light, and a vibration. This corresponds to step U07 in the sequence of FIG.
Then, it returns to step S1.
The above is one example of the processing of the user terminal UTE.

According to this, since the current position of the taxi, the predicted route to travel, and the estimated arrival time are displayed on the display unit until the taxi arrives at the terminal UTE possessed by the user, the user can receive the taxi. You can know the route and direction that will arrive, so you can wait for the arrival of a taxi with peace of mind, and if you have enough time to arrive, you can move the user's current position to the lane side where the taxi comes .
In addition, after making a reservation, identification information for identifying the user is not transmitted to the SV until the taxi arrives and gets on, so that the personal information of the user is protected.

<Treatment at CTE>
In step S <b> 31 of FIG. 6, the taxi current position 241 is acquired by the current position acquisition unit 205 in the taxi-mounted terminal CTE.
In step S32, the acquired taxi current position 241 is transmitted to the SV. This corresponds to step C01 in the sequence of FIG.
In addition, the acquisition of the taxi current position 241 may be performed regularly or almost in real time regardless of the pick-up process.
In step S <b> 33, the incoming / outgoing vehicle availability determination unit 206 checks whether or not incoming vehicle inquiry information is received from the SV. If received, the process proceeds to step S34, and if not, the process returns to step S31.
Since the reception information includes reservation information 230, the reservation information 230 is temporarily stored in the storage unit 220.

In step S34, the received vehicle inquiry information is displayed on the CTE display unit 202. For example, it is requested to input the reservation of the pick-up service, the boarding position and boarding time specified as the contents of the reservation, and whether or not it is possible to go to the boarding position by the boarding time. Is displayed.
The taxi driver confirms this display content, determines whether or not the vehicle can be picked up, and inputs whether or not the vehicle can be picked up by performing a predetermined input operation using the input unit 203.
Alternatively, if possible, a microphone and a voice recognition function may be provided so that the driver generates a voice that can or cannot be picked up, and the voice is recognized to determine whether or not the car can be picked up. Thereby, it is possible to omit the driver's manual input operation.

In step S <b> 35, the vehicle acceptability determination unit 206 checks whether or not the user has input whether the vehicle is acceptable. This corresponds to step C02 in the sequence of FIG.
If it is determined in step S36 that there is an input indicating that the vehicle can be picked up, the process proceeds to step S38. Proceed to
In step S <b> 37, the incoming / outgoing vehicle acceptability determining unit 206 transmits the incoming vehicle impossibility information to the SV. Then, it returns to step S31.
In step S <b> 38, the vehicle admittance determination unit 206 transmits the vehicle arriving information to the SV.
Thereafter, although not shown in the figure, it waits for information on whether the reservation is established or not established, from the SV.
In step S39, it is checked whether or not reservation establishment information is received from the SV. If "reservation establishment" is received, the process proceeds to step S41, and if "reservation establishment not established" is received, the process proceeds to step S40.

In step S40, the display unit 202 displays that the reservation has not been established (reservation is not established), and returns to step S31.
In step S41, the display unit 202 displays that the reservation has been established (reservation has been established). Or you may output the sound which shows that the reservation was materialized from the speaker. This corresponds to step C03 in the sequence of FIG.
The taxi driver looks at the indication that the reservation has been made or has not been made, and confirms whether or not he / she needs to go to the car.
In addition, when the reservation is made, the boarding position and the boarding time to go to the pick-up vehicle may be displayed again in order to call attention together with the display of the reservation making.
Thereafter, when it becomes possible to actually go to the pick-up vehicle, the driver makes an input meaning that the pick-up is started.
In step S42, the incoming car start unit 207 checks whether or not an input indicating the incoming car start has been made.

If it is determined in step S43 that an incoming car start has been input, the process proceeds to step S44, and if not, the process returns to step S42.
In step S44, incoming vehicle start information indicating that an incoming vehicle is to be started is transmitted to the SV. This corresponds to step C04 in the sequence of FIG.
In step S45, a map up to the boarding position is displayed on the display unit 202 of the CTE.
Here, the current position of the own taxi is acquired, and the predicted arrival route is searched using information on the current position of the taxi and the boarding position. Then, the current position of the taxi, the searched predicted route, and the boarding position are added to the map and displayed.
As a result, the driver can check the travel route to the boarding position.

In step S46, the current position acquisition unit 205 periodically acquires the current taxi position 241 while traveling for an incoming vehicle.
In step S47, the acquired taxi current position 241 is transmitted to the SV. This corresponds to steps C05 and C06 in the sequence of FIG.
In step S48, it is checked whether or not it has arrived at the boarding position. That is, it is checked whether or not the acquired taxi current position 241 and the stored boarding position 233 are within a predetermined distance and substantially coincide with each other.

If it is determined in step S49 that the vehicle has arrived, the process proceeds to step S50, and if not, the process returns to step S46.
In step S50, the arrival processing unit 208 transmits information (taxi arrival information) indicating arrival at the boarding position to the SV. This corresponds to step C07 in the sequence of FIG.
When the taxi arrives at the boarding position, the driver waits for the user to come to the boarding position. When the user comes, after confirming that the user is a reservation person, the driver opens the door and asks the user to get on.

In step S51, the boarding processing unit 209 checks whether or not the user has completed the boarding of the incoming taxi. The driver confirms that the user has boarded, closes the door, and then performs a predetermined input operation using the input unit 203 to input that the user has completed boarding.
In step S52, if there is an input signifying completion of boarding, the process proceeds to step S53, and if not, the process returns to step S51.
In step S53, the boarding processing unit 209 transmits the user's boarding completion notification to the SV. This corresponds to step C08 in the sequence of FIG.
Then, it returns to step S31.
Thereby, in the CTE, the pick-up process is completed, and the driver carries the reserved user and runs the taxi to the user's destination.

<Reservation and incoming vehicle management processing in server SV>
In step S61 in FIG. 7, the SV checks the reception of the current taxi position sent from the CTE of each taxi.
In step S62, if the current taxi position is received, the process proceeds to step S63, and if not, the process proceeds to step S64.
In step S63, the received taxi current position 332 is stored in the storage unit 310. This corresponds to step V01 in the sequence of FIG.
Thereafter, the process proceeds to step S64.
The taxi current position 332 is preferably received periodically or almost in real time for all taxis managed by the SV.
In step S64, the reservation receiving unit 305 checks whether or not a vehicle allocation reservation request including reservation information is received from the UTE.
If a valid vehicle allocation reservation request is received, the process proceeds to step S65, and if not, the process returns to step S61.

In step S65, the received reservation information 320 is acquired and stored in the storage unit 310.
In step S66, a taxi that can be dispatched is searched.
Here, for example, the distance between the boarding position 323 of the received reservation information and the current position 332 of each taxi is calculated. If this distance is shorter than a predetermined distance, the taxi can be dispatched. to decide.
Further, by using the usage status information 340, taxis that are “empty” and “ride” may be candidates, and taxis that are “passing” may be excluded from candidates.
A taxi that is determined to be able to be dispatched is temporarily stored as a dispatch candidate.

For all taxis managed, it is determined whether or not dispatch is possible, and then a temporarily stored list of dispatch candidates is displayed.
The person in charge of the SV looks at this list and selects a taxi to be picked up. When a plurality of taxis are displayed in the list, for example, a taxi that is likely to arrive at the boarding position earliest is selected.
In addition, when the person in charge is not requested, such as when the person in charge is absent, the taxi current position may be preferentially selected from the taxi closest to the boarding position.
In step S67, the taxi selected and input by the person in charge is set as an incoming car candidate.

In step S68, the incoming vehicle arrangement unit 306 generates incoming vehicle inquiry information and transmits an incoming vehicle inquiry request to the CTE of the selected incoming taxi. The incoming vehicle inquiry information includes reservation information 320. This corresponds to step V02 in the sequence of FIG.
In step S69, the pick-up arrangement unit 306 checks whether or not the pick-up information is received from the CTE of the pick-up taxi that transmitted the pick-up inquiry request.
In step S70, if the vehicle-acceptable information is received from the CTE, the process proceeds to step S71. If the vehicle-inaccessible information is received or no reply is received even after a predetermined time has elapsed, the process returns to step S66.
After returning to step S66, an incoming vehicle inquiry request is made in the same manner for the other taxis listed in the dispatch candidates. This corresponds to step V03 in the sequence of FIG.
In step S71, the reservation establishment information is transmitted to the UTE that has made the reservation request and the CTE that has transmitted the arrival information. As a result, the reservation for dispatch is accepted and the taxi heading for the pick-up is confirmed.
Thereafter, it waits for reception of incoming vehicle start information indicating that the vehicle has actually started traveling for an incoming vehicle from the confirmed incoming taxi.

In step S <b> 72, the incoming vehicle status confirmation unit 307 performs reception check of incoming vehicle start information sent from the CTE of the incoming taxi.
In step S73, if the incoming vehicle start information is received, the process proceeds to step S74. If not, step S72 is looped.
In step S <b> 74, the incoming vehicle status confirmation unit 307 performs a monitoring process for the incoming taxi that has started the incoming vehicle. In addition, the incoming vehicle start flag 335 is set to a numerical value “1” indicating start, and the usage status information 340 of the incoming taxi is set to “incoming vehicle”.
Here, a predicted arrival route 333 until the arrival taxi arrives at the boarding position is searched, and an estimated arrival time 334 is calculated.
The predicted arrival route 333 and the estimated arrival time 334 are stored in the incoming taxi management information 330 of the incoming taxi. This corresponds to step V04 in the sequence of FIG.
In step S75, the incoming vehicle information generation unit 308 generates incoming vehicle information and transmits it to the UTE.
The incoming vehicle information includes a taxi identification ID 331 for identifying an incoming taxi, a current location 332 of the incoming taxi, an incoming vehicle predicted route 333, and an estimated arrival time 334 stored in the incoming vehicle management information 330.

In step S <b> 76, the incoming vehicle status confirmation unit 307 checks whether arrival information is received from the CTE of the incoming taxi.
In step S77, if arrival information is received, the process proceeds to step S83, and if not, the process proceeds to step S78.
In step S78, a new taxi current position 332 is acquired from the CTE of the incoming taxi.
In step S <b> 79, the incoming vehicle status confirmation unit 307 checks whether or not the acquired new taxi current position has deviated from the incoming vehicle predicted route. For example, whether the taxi is off may be checked by checking whether the current taxi position is on a road different from the road on the predicted route. If it is off, the process proceeds to step S80, and if it is not off, the process proceeds to step S82.

In step S82, since the incoming taxi is traveling on the predicted route, the new taxi current position is transmitted to the UTE. Thereafter, the process returns to step S76. This corresponds to step V05 in the sequence of FIG.
In step S80, since the incoming taxi has deviated from the predicted route, the incoming vehicle status confirmation unit 307 searches again for the predicted incoming vehicle route 333 that the taxi is expected to travel from the new current taxi position.
The estimated arrival time is also recalculated.
In step S81, the new taxi current position 332, the re-searched arrival vehicle predicted route 333, and the recalculated estimated arrival time 334 are transmitted to the UTE. Thereafter, the process returns to step S76. This corresponds to step V06 in the sequence of FIG.

In step S83, the reception status confirmation unit 307 receives the arrival taxi arrival information, and transmits information indicating that the arrival taxi has arrived at the boarding position (taxi arrival completion) to the UTE. The arrival completion flag 336 is set to “1”. This corresponds to step V07 in the sequence of FIG.
In step S <b> 84, the arrival status confirmation unit 307 checks whether or not information indicating that the user has actually boarded (boarding completion notification) is received from the CTE.
In step S85, if the boarding completion notification is received from the CTE, the process proceeds to step S86, and if not, step S84 is looped.
In step S86, a dispatch completion notification indicating that the reserved dispatch has been completed is transmitted to the UTE. The boarding completion flag 337 is set to “1”. This corresponds to step V08 in the sequence of FIG.

In step S87, a vehicle allocation end process is performed. Here, the use taxi usage status information 340 is set to “ride”. In addition, the incoming vehicle management information 330 stored for the incoming taxi may be deleted.
Thereafter, the process returns to step S61.

As described above, the server SV accepts the reservation for dispatching from the user, determines the taxi to be picked up, and then, until the taxi arrives at the boarding position specified in the reservation and the user gets on, the server SV runs. Monitor the situation.
In addition, the user can check the traveling status of the taxi arriving by the current position of the taxi and the predicted route that is considered to travel to the boarding position.
As a result, the reserved user can clearly grasp the direction and road where the incoming taxi arrives, and can wait with peace of mind.

(Second embodiment)
You may learn the route that the taxi picked up actually traveled and use it for the prediction of the subsequent pick-up.
Each time the incoming taxi deviates from the predicted route, the incoming arrival predicted route is re-searched and the estimated arrival time is recalculated, so that the accuracy of the estimated arrival time of the incoming taxi can be improved.
In addition, taxi drivers are often familiar with back roads and road congestion at different times based on their own experience, so they choose the best route rather than a general car navigation system. There is a case.
Therefore, in the server SV, every time the predicted route is departed, the incoming route predicted route is searched again, and then the route that the incoming taxi actually traveled is memorized and learned by the incoming route prediction algorithm. When traveling on a route and picking up a vehicle, it is possible to set an optimum route that the taxi driver will select as a predicted vehicle-receiving route.
As described above, by learning the route on which the taxi is actually traveling, the accuracy of the estimated arrival time can be further improved when the vehicle is traveling on the same route thereafter.

(Third embodiment)
In some cases, such as when the arrival route is changed, the updated estimated arrival time may change significantly compared to the previous estimated arrival time. For example, if unexpected congestion occurs due to an accident or the like, the estimated arrival time may be considerably delayed. Further, since the vehicle has traveled on the back road, the estimated arrival time may be much earlier than the previous estimated arrival time.
In this way, when the estimated arrival time changes greatly from the time notified to the user last time, a large time loss may occur in the user, so that the user can easily be notified that the estimated arrival time deviates greatly. It is preferable.
For example, when the estimated arrival time before and after the update changes by about 30 minutes or more, the display color of the estimated arrival time displayed in the user's UTE is changed. Alternatively, it may be notified by voice that the estimated arrival time has changed significantly, or the UTE main body may be vibrated.
According to this, the user can surely know that the estimated arrival time has changed significantly. In addition, when the user is away from the scheduled boarding position, the timing for moving to the scheduled boarding position can be adjusted earlier, and the time until the user gets on the taxi can be used effectively.

<Appendix>
The present invention is a vehicle allocation system and a vehicle allocation management server having the following configurations.
(Appendix 1)
A user dispatching system in which a user terminal owned by a user, an in-vehicle terminal mounted on a vehicle, and a dispatch management server are connected via a network, wherein the user terminal communicates with the dispatch management server. A communication requesting unit that transmits a vehicle reservation request for requesting the vehicle to be dispatched at the boarding position and boarding time desired by the user to the vehicle allocation management server; A current position acquisition unit that acquires a current position, a second communication unit that communicates with the vehicle allocation management server, a current position of the acquired vehicle, and an arrival at the boarding position in response to the vehicle allocation reservation request An incoming vehicle start unit that transmits the incoming vehicle start information to the vehicle allocation management server, and the vehicle allocation management server communicates with the user terminal and the in-vehicle terminal, A reservation reception unit that receives a vehicle allocation reservation request and an in-vehicle terminal mounted on a predetermined vehicle inquire whether or not the vehicle can be picked up, and information indicating that the vehicle can be picked up is transmitted from the in-vehicle terminal inquired. A reservation arrangement unit that determines that a reservation has been established when the vehicle has been received, and the vehicle current position and the vehicle allocation reservation request transmitted from the in-vehicle terminal when receiving the incoming vehicle start information from the in-vehicle terminal. Using the boarding position, and predicting the route on which the reservation vehicle that has been reserved travels from the current position to the boarding position, and generating a predicted incoming route, and the current position of the incoming vehicle and the A vehicle allocation system comprising: an incoming vehicle information generation unit that transmits incoming vehicle information including a generated predicted incoming vehicle route to the user terminal.

(Appendix 2)
The user terminal further includes an input unit and a display unit, and the boarding position and boarding time desired by the user are input by the input unit, and the incoming vehicle transmitted from the vehicle allocation management server to the display unit. The vehicle allocation system according to appendix 1, wherein the information is used to display the map information together with the current position of the vehicle to be picked up and the predicted route to be picked up in the map information.
According to this, since the map information, the current position of the incoming vehicle included in the map information, and the predicted incoming route are displayed on the display unit of the user terminal, the user who owns the user terminal receives the incoming vehicle It is possible to easily check the current driving situation of the vehicle, know from which direction the incoming vehicle will come to the boarding position, and wait in peace.

(Appendix 3)
The vehicle allocation management server further includes a storage unit that stores a boarding position included in the received vehicle allocation reservation request and the generated predicted incoming vehicle route, and the latest information transmitted from the in-vehicle terminal of the incoming vehicle. When the current position of the vehicle is out of the predicted arrival route stored in the storage unit, the reception state confirmation unit uses the current position of the latest vehicle and the boarding position stored in the storage unit. Regenerating the predicted arrival route, and the reception information generating unit transmits the reception information including the current position of the latest vehicle and the regenerated estimated prediction route to the user terminal. The vehicle allocation system according to appendix 1 or 2.
According to this, even when the incoming vehicle deviates from the incoming predicted route, the predicted incoming route is regenerated using the current position of the latest vehicle, so the accuracy of the predicted arrival time of the incoming vehicle can be improved, The user can always wait for the incoming vehicle to come in peace by confirming the latest traveling state of the incoming vehicle.

(Appendix 4)
The in-vehicle terminal determines whether or not it is possible to go to the boarding position reserved for dispatch by the reserved boarding time in response to the inquiry about whether or not the car can be picked up from the dispatch management server. In such a case, the vehicle allocation system according to any one of appendices 1 to 3, further comprising: a vehicle arrival / absence determination unit that transmits vehicle arrival information to the vehicle allocation management server.
According to this, since it is determined whether or not the vehicle can be picked up by the in-vehicle terminal, the driver of the vehicle equipped with the in-vehicle terminal can determine whether or not to pick up the vehicle based on the current driving situation of the vehicle.

(Appendix 5)
A user terminal owned by a user, a vehicle-mounted terminal mounted on a vehicle, and a vehicle allocation management server are vehicle allocation management servers of a vehicle allocation system connected via a network, and communicate with the user terminal and the vehicle-mounted terminal. A reservation acceptance unit that receives a vehicle allocation reservation request that is transmitted from the user terminal and includes a user's desired boarding position and boarding time, and when the vehicle allocation reservation request is received, A reservation was made when an inbound vehicle inquiry request that inquires whether the vehicle can be picked up at the location and boarding time is received, and the in-car terminal information indicating that the vehicle can be picked up is sent from the in-vehicle terminal that made the inquiry. Judgment, reservation establishment information is transmitted to the user terminal that has transmitted the dispatch reservation request, to the in-vehicle terminal of the receiving vehicle that has transmitted the acceptance information, When receiving the vehicle start information and the current position of the vehicle being picked up from the loading terminal, the route on which the vehicle is traveling from the current position to the boarding position is predicted using the current position and the boarding position of the vehicle being picked up An incoming vehicle situation confirmation unit for generating an incoming vehicle predicted route, and an incoming vehicle information generation unit for transmitting incoming vehicle information including the current position of the incoming vehicle and the incoming vehicle predicted route to the user terminal. A vehicle allocation management server for a vehicle allocation system.

1 user 2 taxi 4 network 100 user terminal UTE
101 Control Unit 102 Display Unit 103 Input Unit 104 Communication Unit 105 Reservation Request Unit 106 Pick-up Information Processing Unit 107 Current Position Acquisition Unit 108 GPS Receiver 110 Storage Unit 120 Reservation Information 121 Reservation ID
122 Boarding time 123 Boarding position 130 Pick-up information 131 Taxi present position 132 Pick-up predicted route 133 Arrival estimated time 141 User current position 142 Display map information 200 In-vehicle terminal CTE
201 Control Unit 202 Display Unit 203 Input Unit 204 Communication Unit 205 Current Position Acquisition Unit 206 Pick-up Acceptability Determination Unit 207 Pick-up Start Unit 208 Arrival Processing Unit 209 Boarding Processing Unit 220 Storage Unit 230 Reservation Information 231 Reservation ID
232 Boarding time 233 Boarding position 241 Taxi current position 242 Display map information 300 Allocation management server SV
301 Control Unit 302 Display Unit 303 Input Unit 304 Communication Unit 305 Reservation Accepting Unit 306 Pick-up Arrangement Unit 307 Pick-up State Confirmation Unit 308 Pick-up Information Generation Unit 310 Storage Unit 320 Reservation Information 321 Reservation ID
322 Boarding time 323 Boarding position 330 Pick-up management information 331 Taxi identification ID
332 Taxi current position 333 Expected arrival route 334 Expected arrival time 335 Arrival start 336 Arrival completion 337 Ride completion 340 Usage information

Claims (6)

A user terminal owned by a user, an in-vehicle terminal mounted on a vehicle, and a vehicle allocation management server are connected to each other via a network so that they can communicate with each other ,
The user terminal is
A reservation request unit that transmits a vehicle allocation request for requesting that the vehicle is allocated at the boarding position and boarding time desired by the user to the vehicle allocation management server;
The in-vehicle terminal is
A current position acquisition unit for acquiring a current position of the vehicle;
An incoming vehicle start unit for transmitting to the vehicle allocation management server the current location of the acquired vehicle, and incoming vehicle start information indicating that an incoming vehicle to the boarding location starts in response to the vehicle allocation reservation request;
The vehicle allocation management server is
The reservation accepting unit that receives the vehicle allocation reservation request and the in-vehicle terminal mounted on the predetermined vehicle inquires whether or not the vehicle can be picked up. A reception arrangement section that determines that a reservation has been made when sent,
When receiving the vehicle arrival information from the in-vehicle terminal, using the current position of the vehicle transmitted from the in-vehicle terminal and the boarding position included in the dispatch reservation request, from the current position of the vehicle to the boarding position, An incoming vehicle situation confirmation unit that predicts a route traveled by the incoming vehicle for which the reservation is established and generates an incoming vehicle predicted route;
A vehicle allocation system comprising: an incoming vehicle information generation unit configured to transmit incoming vehicle information including a current position of the incoming vehicle and the generated predicted incoming vehicle route to the user terminal. The user terminal further includes an input unit and a display unit,
A boarding position and boarding time desired by the user are input by the input unit, and the display unit uses the incoming vehicle information transmitted from the dispatch management server, and the current location of the incoming vehicle and the map information. The vehicle allocation system according to claim 1, wherein the vehicle arrival prediction route is included in map information and displayed. The vehicle allocation management server further includes a storage unit that stores a boarding position included in the received vehicle allocation reservation request and the generated incoming vehicle predicted route,
When the current position of the latest vehicle transmitted from the in-vehicle terminal of the receiving vehicle is out of the predicted incoming vehicle route stored in the storage unit, the incoming vehicle status confirmation unit is configured as the current position of the latest vehicle. Then, using the boarding position stored in the storage unit, regenerates a predicted incoming route, and the incoming information generation unit includes the current position of the latest vehicle and the regenerated predicted predicted route. 3. The vehicle allocation system according to claim 1, wherein information is transmitted to the user terminal.   The in-vehicle terminal determines whether or not it is possible to go to the boarding position reserved for dispatch by the reserved boarding time in response to the inquiry about whether or not the car can be picked up from the dispatch management server. 4. The vehicle allocation system according to claim 1, further comprising: a vehicle arrival / absence determination unit that transmits vehicle arrival information to the vehicle allocation management server. A user terminal owned by a user, an in-vehicle terminal mounted on a vehicle, and a vehicle allocation management server are vehicle allocation management servers of a vehicle allocation system connected via a network,
A communication unit that communicates with the user terminal and the in-vehicle terminal;
A reservation reception unit that is transmitted from the user terminal and receives a vehicle allocation reservation request including a boarding position and a boarding time desired by the user;
When the vehicle allocation reservation request is received, the vehicle-mounted terminal transmits a vehicle-inquiry inquiry request asking whether the vehicle can be picked up at the boarding position and boarding time, and the vehicle-mounted terminal inquired can receive the vehicle. Is received, information indicating that the reservation has been established is transmitted, and the reservation establishment information is transmitted to the user terminal that transmitted the allocation request and the in-vehicle terminal of the vehicle that has received the arrival information. A vehicle arrangement department,
When receiving the incoming vehicle start information and the current position of the incoming vehicle from the in-vehicle terminal of the incoming vehicle, the incoming vehicle travels from the current position to the boarding position using the current position of the incoming vehicle and the boarding position. An incoming vehicle situation confirmation unit that predicts a route to be generated and generates an incoming vehicle prediction route;
A vehicle allocation management server for a vehicle allocation system, comprising: an incoming vehicle information generation unit that transmits incoming vehicle information including the current position of the incoming vehicle and the predicted incoming vehicle route to the user terminal.   A user terminal owned by a user, an in-vehicle terminal mounted on a vehicle, and a vehicle allocation management server are user terminals of a vehicle allocation system that are communicably connected to each other via a network,
  The user terminal is
  A reservation requesting unit for transmitting a vehicle reservation request for requesting the vehicle to be dispatched at the boarding position and boarding time desired by the user to the vehicle allocation management server, an input unit, and a display unit;
  When the boarding position and boarding time desired by the user are input by the input unit, the reservation requesting unit transmits the vehicle allocation reservation request to the vehicle allocation management server,
The current location of the incoming vehicle and the incoming vehicle generated by the allocation management server travel from the allocation management server that has received the incoming vehicle start information and the current location of the incoming vehicle from the in-vehicle terminal of the incoming vehicle that has been reserved. When receiving the incoming vehicle information including the incoming vehicle predicted route predicting the route, using the incoming vehicle information transmitted from the dispatch management server to the display unit, together with the map information, the current position of the incoming vehicle, and A user terminal of a vehicle allocation system, wherein a predicted arrival route is included in map information and displayed.