JP2021152761A - Vehicle allocation management device, vehicle allocation management method, and program - Google Patents

Abstract

To enable more efficient operation when a passenger's destination is outside of a service area of a taxi thereof.SOLUTION: A vehicle allocation management part comprises a management part for transmitting a vehicle allocation request to a taxi extracted by extracting the taxi whose boarding place is outside an operation area and whose destination is outside the operation area, in a case where the boarding place of the vehicle allocation request transmitted from a terminal of a user as a taxi user, and the destination thereof, are different operation areas. The present technique is applicable to, for example, a vehicle allocation management device or the like by which taxi allocation is managed.SELECTED DRAWING: Figure 1

Description

This technology relates to vehicle allocation management devices, vehicle allocation management methods, and programs, and in particular, vehicle allocation management that enables more efficient business operations when the passenger's destination is outside the taxi's business area. Regarding equipment, vehicle allocation management methods, and programs.

Taxi has a business area for each business establishment, and passengers cannot be acquired outside the business area. Therefore, if the destination of the passenger on the taxi is outside the business area of the business office to which the taxi belongs, after the passenger gets off at the destination, the taxi runs empty until it enters the business area of the business office to which the taxi belongs. Had to do.

In response to this situation, for example, a taxi dispatch system has been proposed in which passengers are transferred to a taxi that includes the passenger's destination in the business area at the point where the taxi leaves the business area. For example, see Patent Document 1).

Japanese Unexamined Patent Publication No. 2004-302942

It is inconvenient for passengers to transfer as in Patent Document 1. A more efficient sales system is required when the passenger's destination is outside the taxi's business area.

This technology was made in view of such a situation, and enables more efficient business operations when the destination of the passenger is outside the business area of the taxi. ..

The vehicle allocation management device on one aspect of the present technology is such that the boarding place is outside the business area when the boarding place and the destination of the vehicle dispatch request sent from the terminal device of the user who is the taxi user are different from the business area. The taxi is extracted from the taxi whose destination is within the business area, and the management unit is provided to send a dispatch request to the extracted taxi.

The vehicle allocation management method of one aspect of the present technology is the above-mentioned boarding when the vehicle allocation management device is in a business area where the boarding place and the destination of the vehicle dispatch request sent from the terminal device of the user who is the taxi user are different. A taxi whose location is outside the business area and whose destination is within the business area is extracted, and a dispatch request is transmitted to the extracted taxi.

In the program of one aspect of the present technology, when the computer is in a business area where the boarding place and the destination of the vehicle allocation request sent from the terminal device of the user who is a taxi user are different from the boarding place, the boarding place is the business area. The purpose is to extract a taxi that is outside and whose destination is within the business area, and to function as a management unit that sends a dispatch request to the extracted taxi.

In one aspect of the present technology, when the boarding place and the destination of the vehicle allocation request sent from the terminal device of the user who is the taxi user are different from the business area, the boarding place is outside the business area. A taxi whose destination is within the business area is extracted, and a dispatch request is sent to the extracted taxi.

The vehicle allocation management device, which is one aspect of the present technology, can be realized by causing a computer to execute a program. The program to be executed by the computer can be provided by transmitting via a transmission medium or by recording on a recording medium.

The vehicle allocation management device may be an independent device or an internal block constituting one device.

It is a block diagram which shows the configuration example of the taxi dispatch system which is the embodiment to which this technology is applied. It is a flowchart explaining the processing flow of the whole taxi dispatch system. It is a figure which shows the example of the vehicle dispatch request screen of a user application. It is a flowchart explaining the normal vehicle allocation processing by a vehicle allocation integrated management device. It is a flowchart explaining the 1st vehicle allocation processing by a vehicle allocation integrated management apparatus. It is a figure which shows the example of the vehicle dispatch request screen of a driver application. It is a flowchart explaining the process of generating the taxi list traveling outside the business area. It is a flowchart explaining the 2nd vehicle allocation processing by the vehicle allocation integrated management apparatus. It is a figure which shows the example of the selection screen. It is a figure explaining the division of the business area in Tokyo. It is a flowchart explaining the 3rd vehicle allocation process by the vehicle allocation integrated management apparatus. It is a figure which shows other example of the vehicle dispatch request screen of a user application. It is a figure which shows other example of the vehicle dispatch request screen of a user application. It is a block diagram which shows the structural example of one Embodiment of the computer to which this technique is applied.

Hereinafter, embodiments for carrying out the present technology (hereinafter referred to as embodiments) will be described with reference to the accompanying drawings. In the present specification and the drawings, components having substantially the same functional configuration are designated by the same reference numerals, so that duplicate description will be omitted. The explanation will be given in the following order.
1. 1. Configuration example of taxi dispatch system 2. Flow of the entire taxi dispatch system 3. Normal vehicle allocation processing of the vehicle allocation integrated management device 4. 1. First vehicle allocation process of the vehicle allocation integrated management device 5. Second vehicle allocation process of the vehicle allocation integrated management device 6. Third vehicle allocation process of the vehicle allocation integrated management device 7. Other examples of the vehicle allocation request screen of the user application 8. Modification 9. Computer configuration example

<1. Configuration example of taxi dispatch system>
FIG. 1 is a block diagram showing a configuration example of a taxi dispatch system according to an embodiment to which the present technology is applied.

The taxi dispatch system 1 of FIG. 1 is a system that dispatches a taxi to a user based on a request of a user who is a taxi user, and is a vehicle dispatch management device 11A of each taxi company of company A, company B, and company C. To 11C and a vehicle allocation management device 12 which is a vehicle allocation management device for integrated management of them.

The vehicle allocation management device 11A of company A is connected to one or more taxis 21A belonging to company A via a predetermined network, and is also connected to the vehicle allocation management device 12 via a predetermined network.

Similarly, the vehicle allocation management device 11B of company B is connected to one or more taxis 21B belonging to company B via a predetermined network, and is also connected to the vehicle allocation integrated management device 12 via a predetermined network.

Similarly, the vehicle allocation management device 11C of company C is connected to one or more taxi 21Cs belonging to company C via a predetermined network, and is also connected to the vehicle allocation integrated management device 12 via a predetermined network.

Further, the individual taxi 21D that does not belong to the predetermined company is directly connected to the vehicle allocation integrated management device 12 via the vehicle allocation management device 11 without going through the vehicle allocation management device 11. When the taxis 21A to 21C of companies A, B, and C, and the individual taxi 21D are not particularly distinguished, they are simply referred to as taxi 21.

Here, the predetermined network is, for example, the Internet, a public telephone line network, a wide area communication network for wireless mobiles such as a so-called 4G line or a 5G line, WAN (Wide Area Network), LAN (Local Area Network), Bluetooth ( Wireless communication network that communicates in accordance with the registered trademark) standard, short-range wireless communication channel such as NFC (Near Field Communication), infrared communication channel, HDMI (registered trademark) (High-Definition Multimedia Interface) and USB It can be configured by a communication network or communication path of any communication standard such as a wired communication communication network conforming to a standard such as (Universal Serial Bus).

The taxi 21A of company A has an on-board unit 31 and a communication unit 32. Further, the taxi 21A of the company A is equipped with a terminal device 33.

The on-board unit 31 acquires necessary data from a toll meter, a GPS (Global Positioning System) receiver, a gyro sensor, a speedometer, etc. (all not shown), and represents a vehicle dynamics log of the vehicle (taxi 21A). The vehicle dynamic data generation unit 34 for generating data is provided.

The vehicle dynamic data generation unit 34 acquires data such as the status of "actual vehicle", "vacant vehicle", or "pick-up vehicle" and the fare (fare) from the fare meter, for example. Further, the vehicle dynamic data generation unit 34 acquires information such as the current position, moving speed, and moving direction of the vehicle from, for example, a GPS receiver, a gyro sensor, a speed meter, and the like.

Then, the vehicle dynamic data generation unit 34 generates a company ID for identifying the company to which the taxi 21A belongs, a radio ID for identifying the vehicle of the taxi 21A, a crew ID for identifying the driver who is on the taxi 21A, and a status generation time. Status time representing, taxi 21A position information latitude and longitude, taxi 21A running speed and direction of travel, "real vehicle", "empty" or "pick-up" status, and status of "real vehicle" or "actual vehicle" or " In the case of "pick-up", information such as the boarding place and destination of the taxi 21 is periodically or irregularly generated as vehicle dynamic data, and is transmitted to the vehicle allocation management device 11A of company A via the communication unit 32. ..

The communication unit 32 transmits the vehicle dynamic data generated by the vehicle dynamic data generation unit 34 of the vehicle-mounted device 31 to the vehicle allocation management device 11A of the company A. The communication unit 32 is composed of a network interface that performs network communication via a predetermined network.

The terminal device 33 is composed of, for example, an information processing device such as a smartphone or a tablet terminal. The driver application 35, which is an application program for the driver, is installed in the terminal device 33. The driver application 35 acquires the data related to the vehicle allocation request from the vehicle allocation management device 12 and displays it on the display, or transmits the response data to the vehicle allocation request to the vehicle allocation management device 12 based on the driver's operation. The driver application 35 directly communicates with the vehicle allocation integrated management device 12 via a network such as a wide area communication network for wireless mobiles. The driver application 35 may communicate with the vehicle allocation integrated management device 12 via the vehicle allocation management device 11A of the company A via the communication unit 32.

The taxi 21B of company B and the taxi 21C of company C are basically the same as the taxi 21A of company A except that the companies are different, so the description thereof will be omitted.

The vehicle allocation management device 11A of company A collects vehicle dynamic data of one or more taxi 21A of company A and transmits the vehicle dynamic data to the vehicle allocation management device 12 and is transmitted from the vehicle allocation management device 12 to the taxi 21A of company A. The data related to the vehicle dispatch request is relayed and transmitted to the designated taxi 21A of company A.

The vehicle allocation management device 11A of company A has a vehicle dynamic data management unit 41, an order information management unit 42, and a communication unit 43. The vehicle allocation management device 11A of company A is composed of, for example, a server device (information processing device) having a network connection function.

The vehicle dynamic data management unit 41 manages vehicle dynamic data supplied from each of the taxi 21A of company A. Specifically, the vehicle dynamic data management unit 41 stores the vehicle dynamic data supplied from each of the taxi 21A of the company A in the internal storage unit, and displays the vehicle dynamic data of each taxi 21A on a display (not shown). .. Further, the vehicle dynamic data management unit 41 transmits the vehicle dynamic data supplied from each taxi 21A to the vehicle allocation integrated management device 12.

When the operator who manages the operation of the taxi 21A of the company A receives a call for dispatching the taxi to the company A, the current position of each taxi 21A of the company A, which is stored in the vehicle dynamics data management unit 41, and " You can check the status of "actual vehicle" or "empty vehicle" and search for or assign a taxi 21A that can respond to a vehicle allocation request.

The order information management unit 42 manages information on prior vehicle allocation requests (vehicle allocation reservations) from customers and the like. For example, when the operator of the taxi 21A of company A receives a call for a vehicle allocation reservation from a customer, the operator inputs information on the vehicle allocation reservation, for example, information such as a pick-up location, a pick-up time, a customer name, and a destination. Is input to the order information management unit 42. The order information management unit 42 stores the information of the vehicle allocation reservation, and displays the vehicle allocation request when the predetermined time before the reservation time comes. The operator who confirms the display of the vehicle allocation request makes a vehicle allocation request to the predetermined taxi 21A based on the vehicle dynamic data stored in the vehicle dynamic data management unit 41. The order information management unit 42 may search for the optimum taxi 21A from the vehicle dynamics data of the vehicle dynamics data management unit 41 and make a vehicle allocation request before the reserved time.

The communication unit 43 performs predetermined communication with each of the vehicle allocation integrated management device 12 and the taxi 21A of the company A. For example, the communication unit 43 transmits a vehicle allocation request from the vehicle allocation integrated management device 12 to a predetermined taxi 21A, and transmits vehicle dynamic data periodically acquired from each taxi 21A to the vehicle allocation integrated management device 12.

The vehicle allocation management devices 11B and 11C of the taxi companies of companies B and C are basically the same as the vehicle allocation management devices 11A of company A except that the companies are different, so the description thereof will be omitted. When company A, company B, and company C are not particularly distinguished, they may be simply referred to as the vehicle allocation management device 11.

The vehicle allocation integrated management device 12 transmits and receives data such as vehicle dynamic data and vehicle allocation request to and from the vehicle allocation management devices 11 of companies A, B, and C. Further, the vehicle allocation integrated management device 12 is also referred to as an application program (hereinafter, referred to as a user application) 61 installed in a terminal device (hereinafter, referred to as a user terminal) 13 of a user who is a taxi user to request a vehicle allocation. , Communicate over a predetermined network. The vehicle allocation integrated management device 12 is composed of, for example, a server device (information processing device) having a network connection function.

The vehicle allocation integrated management device 12 is a vehicle allocation management device that manages the vehicle allocation of all taxis 21. The vehicle allocation integrated management device 12 includes a vehicle dynamic data management unit 51, a customer data management unit 52, an order information management unit 53, a vehicle allocation management unit 54, a taxi company communication unit 55, and an application communication unit 56.

The vehicle dynamic data management unit 51 manages the vehicle dynamic data supplied from the vehicle allocation management device 11 of each taxi company and each individual taxi 21D. Specifically, the vehicle dynamics data management unit 51 stores vehicle dynamics data supplied from the vehicle allocation management device 11 of each taxi company and each individual taxi 21D in an internal storage unit, and displays the vehicle dynamics data (not shown). To display. The vehicle dynamic data includes the company ID of the taxi 21, the radio ID of the taxi 21, the crew ID, the status time, the position information of the taxi 21, the traveling speed and the direction of travel of the taxi 21, the status, and the status of "actual vehicle" or "pick-up". This is information such as the boarding place and destination of the taxi 21 in the case of. In addition, the vehicle dynamic data management unit 51 records the company ID of the taxi 21, the radio ID of the taxi 21, the crew ID, the boarding place and the destination, the fare, etc. every time the status of one "actual vehicle" is completed. It is recorded in the internal storage as the actual vehicle data.

The customer data management unit 52 generates customer data based on the data input by the operator or transmitted from the user application 61, and stores the customer data in the internal storage unit. For example, the customer data management unit 52, as customer data, includes the customer's name, the customer's grade, the tax company that the customer likes or preferentially dispatches, the frequently used taxi stand, and the average waiting time for picking up. Information such as is stored together with the customer ID which is the identification information for identifying the customer. The customer data may be data input (designated) by the user in the user application 61, or may be data generated by the customer data management unit 52 based on the user's boarding history or the like.

The order information management unit 53 manages information on prior vehicle allocation requests (vehicle allocation reservations) from customers and the like. The order information management unit 42 of each vehicle allocation management device 11 is the information of the vehicle allocation request (vehicle allocation reservation) received by each taxi company, whereas the order information management unit 53 is the reservation of the representative who controls each taxi company. It manages the information of the vehicle allocation request (vehicle allocation reservation) received by the center or the user application 61. The order information management unit 53 makes a vehicle allocation request to the vehicle allocation management unit 54 before a predetermined time of the reservation time of the vehicle allocation reservation.

The vehicle allocation management unit 54 controls vehicle allocation based on a vehicle allocation request or a vehicle allocation reservation. For example, when the vehicle allocation request is transmitted from the user application 61, the vehicle allocation management unit 54 extracts the taxi 21 that satisfies the vehicle allocation request condition based on the vehicle dynamic data stored in the vehicle dynamic data management unit 51. Then, the dispatch request is sent to the extracted taxi 21. Further, when the vehicle allocation request is transmitted from the order information management unit 53, the vehicle allocation management unit 54 selects the taxi 21 that satisfies the vehicle allocation request condition based on the vehicle dynamic data stored in the vehicle dynamic data management unit 51. Extract and send a vehicle allocation request to the extracted taxi 21.

The taxi company communication unit 55 performs predetermined communication with each of the vehicle allocation management devices 11 of each taxi company. For example, the taxi company communication unit 55 receives vehicle dynamic data periodically transmitted from each taxi 21A and supplies the vehicle dynamic data to the vehicle dynamic data management unit 51, or receives a vehicle allocation request from the vehicle allocation management unit 54 for vehicle allocation management. It is transmitted to a predetermined taxi 21 via the device 11.

The taxi company communication unit 55 directly communicates with the taxi 21 of each taxi company without going through the vehicle allocation management device 11 of each taxi company to receive vehicle dynamic data or from the vehicle allocation management unit 54. The vehicle dispatch request may be sent to a predetermined taxi 21.

The application communication unit 56 performs predetermined communication with the user application 61. For example, the application communication unit 56 receives a vehicle allocation request from the user application 61 and supplies it to the vehicle allocation management unit 54, or sends a vehicle allocation confirmation notification to the user application 61 when the allocation of a predetermined taxi 21 is confirmed. do.

Although only the user terminal 13 and the user application 61 corresponding to one user are shown in FIG. 1 for easy understanding, the vehicle allocation integrated management device 12 is the user application 61 of a plurality of user terminals 13. And, if necessary, the required communication can be performed.

The user terminal 13 is composed of, for example, an information processing device such as a smartphone or a tablet terminal, and performs predetermined communication with the vehicle allocation integrated management device 12. The user application 61 requests the vehicle allocation integrated management device 12 to dispatch the taxi 21 based on the user's operation, and displays the vehicle allocation confirmation in response to the vehicle allocation request. In addition, the user application 61 can display the current operation status of the taxi 21 on the display by acquiring the vehicle dynamic data in the vicinity of the user's current location from the vehicle allocation integrated management device 12.

In the taxi dispatch system 1 configured as described above, when the user operates the user application 61 to request the taxi 21 to be dispatched, the vehicle dispatch integrated management device 12 uses the vehicle dynamics of the vehicle dynamics data management unit 51. With reference to the data, the optimum taxi 21 is searched for, and a dispatch request is sent to the searched taxi 21.

Each taxi company has a business area, and either the boarding point or the destination must be within the business area when carrying passengers. The business area is defined for the purpose of adjusting the supply and demand of taxis within the area, and there are 643 areas nationwide. Taxi fares within the business area are the same.

Taking a taxi company whose business area is Tokyo's 23 wards as an example, if the business section (boarding section) is between Ota Ward and Machida City, either the boarding point or the destination will be within the business area, so it is possible to operate. However, if the business section is between Machida City and Yokohama City, it is not possible to conduct business because both the boarding place and the destination are outside the business area.

If a taxi whose business area is in the 23rd ward of Tokyo carries passengers whose destination is Machida City, the next passenger to be picked up in the suburbs of Machida City must be a passenger whose destination is within the 23rd ward, which is within the business area. However, it is difficult to find passengers who want such a specific destination area, and the current operation is that if the taxi is outside the business area, it will be returned to the business area as a deadhead and then searched for passengers. It is carried out.

Therefore, the vehicle allocation integrated management device 12 reduces the chances of the taxi 21 returning to the business area as a forwarding when the taxi 21 operates from outside the business area as a destination, and the time required for returning from the outside of the business area to the inside of the business area. And it is configured to control vehicle allocation that can reduce fuel waste.

That is, according to the taxi dispatch system 1, the taxi 21 can be efficiently dispatched when moving outside the business area.

<2. Flow of the entire taxi dispatch system>
First, the flow of vehicle allocation control in the entire taxi vehicle allocation system 1 will be described with reference to the flowchart of FIG.

In addition to the processing of FIG. 2, the vehicle allocation integrated management device 12 acquires the vehicle dynamic data of the taxi 21 from each taxi 21 periodically or irregularly, and updates the vehicle dynamic data of the vehicle dynamic data management unit 51. It is assumed that the process is always executed.

First, in step S1, the user inputs the boarding place "X" and the destination "Y" into the user application 61, and operates the vehicle allocation request.

FIG. 3 shows an example of a vehicle allocation request screen of the user application 61 when the user application 61 is activated in order to make a vehicle allocation request.

On the vehicle allocation request screen of FIG. 3, an area map 81 for displaying a map of the vicinity of the current location, a vehicle allocation request operation unit 82 for performing a vehicle allocation request operation, a boarding place input unit 83 for inputting a boarding location, and a destination input unit for inputting a destination 84 and a payment setting unit 85 for designating a payment method are provided.

On the area map 81, empty taxi marks 91A and 91B representing taxis 21 having a status of "empty" are displayed at positions on the map corresponding to the current positions of those taxis 21. The display color or pattern is different between the empty taxi mark 91A and the empty taxi mark 91B, and the display color or pattern corresponds to, for example, the color of the actual body of the taxi 21.

The empty taxi marks 91 (91A and 91B) displayed on the area map 81 display only the preset N units (N> 0) when there are many taxi 21 with the status "empty" near the current location. It can be controlled to display. Further, not only the taxi 21 whose status is "empty" but also the taxi mark representing the taxi 21 whose status is "actual vehicle" may be displayed on the area map 81.

Further, the area map 81 includes a current location mark 93 indicating the user's current location acquired by the GPS receiver of the user terminal 13 and a boarding location mark 94 at a position corresponding to the boarding location input by the user to the boarding location input unit 83. Is displayed. The boarding place mark 94 can be freely moved to a desired place on the area map 81 by the user by touch operation, and the address corresponding to the place of the boarding place mark 94 is displayed on the boarding place input unit 83.

The operation bar 82A is displayed on the vehicle allocation request operation unit 82, and the vehicle allocation request can be executed by sliding the operation bar 82A to the right side.

The boarding place desired by the user is input to the boarding place input unit 83. The boarding location input unit 83 may be left blank when the application is started, or the current location acquired by the GPS receiver may be input by default. If the boarding place input unit 83 is left blank, the boarding place mark 94 is also not displayed.

The destination, which is the destination desired by the user, is input to the destination input unit 84.

The payment setting unit 85 can specify the payment method. As the payment method, for example, cash payment to pay the driver in cash, card payment to pay with the credit card registered in the user application 61, or the like can be selected. The payment setting unit 85 of FIG. 3 shows a display example when card payment is specified.

When the operation bar 82A is slid to the right by the user on the vehicle allocation request screen of FIG. 3, the user application 61 requests vehicle allocation together with the information of the boarding place “X” and the destination “Y” in step S2 of FIG. , Is transmitted to the vehicle allocation integrated management device 12.

In step S11, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 receives the vehicle allocation request from the user application 61, refers to the current vehicle dynamic data managed by the vehicle dynamic data management unit 51, and can dispatch the taxi 21. Is extracted. Here, it is assumed that the taxi 21A of the company A having the status of "empty" is searched for the taxi 21 closest to the boarding place "X".

In step S12, the vehicle allocation management unit 54 transmits a vehicle allocation request to the searched taxi 21A of company A.

In step S21, the driver application 35 of the taxi 21A of the company A acquires the data related to the vehicle allocation request from the vehicle allocation integrated management device 12 (for example, the boarding place “X” and the destination “Y”) and displays it on the display. .. Then, when the driver performs a response operation to the effect that the vehicle allocation request is accepted, in step S22, the driver application 35 transmits a request acceptance notification to the effect that the vehicle allocation request is accepted to the vehicle allocation integrated management device 12.

When the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 receives the request acceptance notification from the taxi 21A in step S13, the taxi 21A is determined to be the taxi to be allocated, and in step S14, the vehicle allocation is confirmed by the user application 61. Send a notification.

When the user application 61 receives the vehicle allocation confirmation notification in step S3, the user application 61 displays the vehicle allocation confirmation. Then, when the taxi 21A of company A assigned to the user arrives at the boarding place "X", in step S4, the user gets on the taxi 21A and starts moving to the destination "Y".

<3. Normal vehicle allocation processing of vehicle allocation integrated management device>
Next, among the flow of vehicle allocation control of the entire taxi vehicle allocation system 1 described with reference to FIG. 2, the normal vehicle allocation process by the vehicle allocation integrated management device 12 will be described with reference to the flowchart of FIG. Here, the normal vehicle allocation process represents a vehicle allocation process when the difference in business areas is not particularly considered. The process of FIG. 4 is started, for example, when a program for executing the vehicle allocation process is started in the server device as the vehicle allocation integrated management device 12.

First, in step S41, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 determines from the user application 61 whether or not the vehicle allocation request has been received, and waits until it is determined that the vehicle allocation request has been received. In the vehicle dispatch request sent from the taxi 21, as described with reference to FIG. 3, the user ID that identifies the user and the user ID that identifies the user, along with the boarding place, destination, and payment method entered on the vehicle dispatch request screen, and the payment method Contains information such as name.

If it is determined in step S41 that the vehicle allocation request has been received from the user application 61, the process proceeds to step S42.

In step S42, the vehicle allocation management unit 54 refers to the vehicle dynamics data stored in the vehicle dynamics data management unit 51, and from the taxi 21 whose status is "empty", the vehicle allocation request is made to the boarding place for a predetermined time. The taxi 21 that can be dispatched within is extracted. For example, the vehicle allocation management unit 54 calculates the travel time from the current position of the taxi 21 to the boarding place specified by the user for the taxi 21 whose status is "empty", and the calculated travel time is within a predetermined time. Extract taxi 21.

In step S43, the vehicle allocation management unit 54 determines the taxi 21 that can arrive at the boarding place earliest from the extracted one or more taxi 21 as a vehicle allocation candidate, and in step S44, determines the vehicle allocation candidate. Send a dispatch request to taxi 21.

In step S45, the vehicle allocation management unit 54 determines whether or not the request acceptance notification has been received from the taxi 21 that has transmitted the vehicle allocation request.

In step S45, if the taxi 21 that has sent the vehicle allocation request does not receive the request acceptance notification within a certain period of time (for example, 15 seconds), or if the request refusal notification is transmitted, the vehicle allocation management unit 54 It is determined that there is no request acceptance notification, and the process returns to step S43. As a result, the next taxi 21 that can respond to the vehicle allocation request is determined as a vehicle allocation candidate.

On the other hand, when the request acceptance notification is received from the taxi 21 that has sent the vehicle allocation request, the vehicle allocation management unit 54 determines in step S45 that the request acceptance notification has been received from the taxi 21 that has sent the vehicle allocation request, and processes the process in step S46. Proceed.

In step S46, the vehicle allocation management unit 54 determines the taxi 21 that has transmitted the request acceptance notification to the taxi 21 to be allocated, and transmits the vehicle allocation reservation information to the determined taxi 21. The vehicle allocation reservation information is, for example, information such as the name of the user who has requested the vehicle allocation, the boarding place, the boarding time, and the destination.

Then, in step S47, the vehicle allocation management unit 54 transmits a vehicle allocation confirmation notification to the user application 61 that has requested the vehicle allocation.

The normal vehicle allocation process is executed as described above.

<4. 1st vehicle allocation process of vehicle allocation integrated management device>
Next, with reference to the flowchart of FIG. 5, the first vehicle allocation process in consideration of the difference in the business area by the vehicle allocation integrated management device 12 will be described. This process is started, for example, when a program that executes the vehicle allocation process is started in the server device as the vehicle allocation integrated management device 12.

First, in step S61, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 determines from the user application 61 whether or not the vehicle allocation request has been received, and waits until it is determined that the vehicle allocation request has been received. If it is determined in step S61 that the vehicle allocation request has been received, the process proceeds to step S62.

In step S62, the vehicle allocation management unit 54 determines whether the boarding place of the transmitted vehicle allocation request and the business area of the destination are different.

If it is determined in step S62 that the business area of the boarding place and the destination is the same, the process proceeds to step S63, and the vehicle allocation management unit 54 executes a normal vehicle allocation process without particularly considering the difference in the business area. As the normal vehicle allocation process here, the processes of steps S42 to S47 of the normal vehicle allocation process described with reference to FIG. 4 are executed.

On the other hand, if it is determined in step S62 that the business area of the boarding place and the destination are different, the process proceeds to step S64, and the vehicle allocation management unit 54 uses the vehicle dynamic data stored in the vehicle dynamic data management unit 51. By referring to the taxi 21, the taxi 21 whose status is "empty" is extracted from the taxi 21 which can be dispatched to the boarding place where the dispatch request is made within a predetermined time. This process is the same as the process of step S42 of the normal vehicle allocation process of FIG.

Subsequently, in step S65, the vehicle allocation management unit 54 determines whether or not there is a taxi 21 whose business area is not the boarding place among the extracted taxi 21 that can be allocated. Whether or not the boarding place or the destination is a business area can be identified by checking the company ID or wireless ID of the taxi 21 included in the vehicle dynamic data, for example. In addition, the vehicle dynamic data may include business area information that identifies the business area of the taxi 21, and the determination may be made based on the information.

If it is determined in step S65 that there is no taxi 21 whose boarding location is not the business area, the process proceeds to step S63 described above, and a normal vehicle allocation process that does not particularly consider the difference in the business area is executed.

On the other hand, if it is determined in step S65 that there is a taxi 21 whose boarding place is not a business area, the process proceeds to step S66, and the vehicle allocation management unit 54 extracts the taxi 21 whose boarding place is not a business area.

Next, in step S67, the vehicle allocation management unit 54 determines whether or not there is a taxi 21 whose business area is the destination among the taxi 21 that can be allocated in step S66.

If it is determined in step S67 that the taxi 21 whose destination is the business area does not exist, the process proceeds to step S63 described above, and a normal vehicle allocation process that does not particularly consider the difference in the business area is executed.

On the other hand, if it is determined in step S67 that there is a taxi 21 whose business area is the destination, the process proceeds to step S68, and the vehicle allocation management unit 54 is among the taxi 21 that can be allocated in step S66. , Extract the taxi 21 whose business area is the destination. The taxi 21 extracted here is a taxi whose boarding place is outside the business area and whose destination is the business area.

Then, in step S69, the vehicle allocation management unit 54 determines, among the taxi 21 that can be allocated in step S68, the taxi 21 that can arrive at the boarding place earliest as a vehicle allocation candidate, and in step S70, the taxi is allocated. A dispatch request is sent to the taxi 21 determined as a candidate.

FIG. 6 shows an example of a vehicle allocation request screen of the driver application 35 displayed on the display of the terminal device 33 when a vehicle allocation request is transmitted from the vehicle allocation integrated management device 12.

On the vehicle allocation request screen of FIG. 6, an area map 121 that displays a map including the boarding place and the destination of the vehicle allocation request is displayed. Further, the area map 121 displays a boarding place mark 122 indicating the boarding place of the vehicle allocation request, a destination mark 123 indicating the destination of the vehicle allocation request, and a planned travel route 124 to the destination.

In addition, on the area map 121, for example, the message 125 "There is a vehicle dispatch request for the business area. The estimated fare is 8000 yen. Do you want to receive an order?" Is displayed.

Further, on the vehicle allocation request screen of FIG. 6, an order receiving button 131, which is operated when an order is received, and an order non-order button 132, which is operated when an order is not desired, are displayed.

When receiving an order for a vehicle allocation request, the driver presses the order button 131. On the other hand, if the driver does not want to receive an order for the vehicle allocation request, the driver presses the order-not-order button 132. In the driver application 35, if neither the order button 131 nor the non-order button 132 is operated between the time when the vehicle allocation request screen shown in FIG. 6 is displayed and the time when the predetermined time elapses, the non-order button 132 is pressed. The same processing as when pressed can be performed. As a result, if there is no driver operation within a certain period of time, the vehicle allocation integrated management device 12 can send a vehicle allocation request to the next taxi 21 candidate.

Returning to FIG. 5, in step S71, the vehicle allocation management unit 54 determines whether or not the request acceptance notification has been received from the taxi 21 that has transmitted the vehicle allocation request.

In step S71, if the taxi 21 that has sent the vehicle allocation request does not receive the request acceptance notification within a certain period of time (for example, 15 seconds), or if the request refusal notification is transmitted, the vehicle allocation management unit 54 It is determined that there is no request acceptance notification, and the process returns to step S69. As a result, the next taxi 21 that can respond to the vehicle allocation request is determined as a vehicle allocation candidate.

On the other hand, when the request acceptance notification is received from the taxi 21 that has sent the vehicle allocation request, the vehicle allocation management unit 54 determines in step S71 that the request acceptance notification has been received from the taxi 21 that has sent the vehicle allocation request, and processes the process in step S72. Proceed.

In step S72, the vehicle allocation management unit 54 determines the taxi 21 that has transmitted the request acceptance notification to the taxi 21 to be allocated, and transmits the vehicle allocation reservation information to the determined taxi 21. The vehicle allocation reservation information is, for example, information such as the name of the user who has requested the vehicle allocation, the boarding place, the boarding time, and the destination.

Then, in step S73, the vehicle allocation management unit 54 transmits a vehicle allocation confirmation notification to the user application 61 that has transmitted the vehicle allocation request.

After step S73 or step S63, the process returns to step S61, and the vehicle allocation management unit 54 waits until the next vehicle allocation request is received.

According to the first vehicle allocation process in consideration of the difference in the business area of FIG. 5, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 does not set the boarding place as the business area in the taxi 21 whose status is "empty". If there is a taxi 21 whose business area is the destination, the taxi dispatch request is preferentially transmitted to the taxi 21.

As a result, the taxi 21 that operates for the destination outside the business area can reduce the chance of returning to the business area as a deadhead as much as possible, and reduce the waste of time and fuel when returning from the outside of the business area to the inside of the business area. can.

<5. Second vehicle allocation process of the vehicle allocation integrated management device>
In the first vehicle allocation process described with reference to FIG. 5, the vehicle allocation request is transmitted from outside the business area to the taxi 21 scheduled to return to the business area, and the vehicle can be allocated to the boarding place where the vehicle allocation request was made within a predetermined time. Only when there is a taxi 21 that is scheduled to return from outside the business area to the inside of the business area among the taxi 21 extracted as.

On the other hand, for example, even if there is some waiting time for the vehicle allocation request, it is possible to control the taxi 21 scheduled to return from outside the business area to the inside of the business area as much as possible. Hereinafter, the second vehicle allocation process for performing such vehicle allocation control will be described.

A user who is a user of taxi 21 is given some incentive if he / she is asked to use taxi 21 which is scheduled to return from outside the business area to the inside of the business area with some waiting time. ..

FIG. 7 is a flowchart of a taxi list generation process outside the business area, which is executed in parallel with the second vehicle allocation process by the vehicle allocation integrated management device 12 when the second vehicle allocation process is executed. This process is started, for example, when a program that executes the vehicle allocation process is started in the server device as the vehicle allocation integrated management device 12.

First, in step S91, the vehicle dynamic data management unit 41 acquires the vehicle dynamic data supplied from each taxi 21A and updates the vehicle dynamic data stored in the internal storage unit. As a result, the position information of the taxi 21, the traveling speed and the direction of travel, the status, and the information such as the boarding place and the destination of the taxi 21 when the status is "actual vehicle" or "pick-up" are updated.

In step S92, the vehicle allocation management unit 54 determines whether or not there is a taxi 21 traveling with the destination outside the business area in the updated vehicle dynamic data.

If it is determined in step S92 that there is a taxi 21 traveling outside the business area as a destination, the process proceeds to step S93, and the vehicle allocation management unit 54 stores the taxi outside the business area in the internal memory. Add taxi 21 traveling outside the business area to the list. In the list of taxis traveling outside the business area, for each taxi 21 traveling outside the business area, the company ID, wireless ID, crew ID, status time, position information of taxi 21A, traveling speed and direction of travel, and destination Information such as the estimated time of arrival at the destination and the estimated time of arrival at the destination is registered. The registration information is updated for the already registered running taxi 21, and the registration information is added for the newly discovered running taxi 21.

After step S93, the process returns to step S91, and steps S91 to S93 described above are repeatedly executed.

Next, with reference to the flowchart of FIG. 8, the second vehicle allocation process in consideration of the difference in the business area by the vehicle allocation integrated management device 12 will be described. This process is started, for example, when a program that executes the vehicle allocation process is started in the server device as the vehicle allocation integrated management device 12.

First, in step S121, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 determines from the user application 61 whether or not the vehicle allocation request has been received, and waits until it is determined that the vehicle allocation request has been received. If it is determined in step S121 that the vehicle allocation request has been received, the process proceeds to step S122.

In step S122, the vehicle allocation management unit 54 determines whether the business area of the destination and the boarding place of the transmitted vehicle allocation request are different.

If it is determined in step S122 that the business area of the boarding place and the destination is the same, the process proceeds to step S123, and the vehicle allocation management unit 54 executes a normal vehicle allocation process without particularly considering the difference in the business area. As the normal vehicle allocation process here, the processes of steps S42 to S47 of the normal vehicle allocation process described with reference to FIG. 4 are executed.

On the other hand, if it is determined in step S122 that the business areas of the boarding place and the destination are different, the process proceeds to step S124, and the vehicle allocation management unit 54 uses the vehicle dynamic data stored in the vehicle dynamic data management unit 51. With reference to the taxi 21, the taxi 21 whose status is "empty" is extracted from the taxi 21 which can be dispatched to the boarding place where the dispatch request is made within a predetermined time.

The above processes of steps S121 to S124 are the same as the processes of steps S61 to S64 of the first vehicle allocation process. In the process of step S124, taxis 21 that can be dispatched within a predetermined time are extracted without considering the difference in business areas.

In the process of step S124, when there is a taxi 21 whose boarding place is outside the business area and whose destination is within the business area in the vicinity of the boarding place where the vehicle dispatch request is made, the taxi 21 is found in the same manner as in the first vehicle dispatch process. Taxi 21 can be preferentially selected as a candidate for dispatch, but in this process, such taxi 21 does not exist, and in the process of step S124, both the boarding place and the destination are only taxi 21 within the business area. Is extracted.

Next, in step S125, the vehicle allocation management unit 54 determines whether or not there is a taxi 21 whose business area is the destination of the vehicle allocation request in the list of taxis traveling outside the business area.

If it is determined in step S125 that there is no taxi 21 whose business area is the destination of the vehicle allocation request in the taxi list traveling outside the business area, the process proceeds to step S123, and the difference in the business area is not particularly considered. Normally, the vehicle allocation process is executed.

On the other hand, if it is determined in step S125 that there is a taxi 21 whose business area is the destination of the vehicle allocation request in the list of taxis traveling outside the business area, the process proceeds to step S126, and the vehicle allocation management unit 54 operates. From the list of taxis traveling outside the area, taxis 21 whose business area is the destination of the vehicle allocation request are extracted.

In step S127, among the taxis 21 extracted in steps S124 and S126, the taxi 21 outside the business area and the taxi 21 within the business area that can reach the boarding place earliest are determined as vehicle allocation candidates. Candidates for taxi 21 outside the business area that can reach the boarding place earliest are determined from the taxi 21 extracted in step S126, and the taxi 21 within the business area that can reach the boarding place earliest is determined. The vehicle allocation candidate is determined from the taxi 21 extracted in step S124.

In step S128, a vehicle allocation candidate request is transmitted to the two vehicle allocation candidate taxis 21.

In step S129, the vehicle allocation management unit 54 determines whether or not the request acceptance notification has been received from the taxi 21 that has transmitted the vehicle allocation candidate request.

In step S129, if the taxi 21 that has sent the vehicle allocation candidate request does not receive the request acceptance notification within a certain period of time (for example, 15 seconds), or if the request refusal notification is transmitted, the vehicle allocation management unit 54 , It is determined that there is no request acceptance notification, and the process is returned to step S127. As a result, the next taxi 21 that can respond to the vehicle allocation request is determined as a vehicle allocation candidate.

If it is determined in step S129 that the taxi 21 that has sent the vehicle allocation candidate request has received a request acceptance notification, the vehicle allocation management unit 54 transmits a selection request for two types of taxi 21 to the user application 61 in step S130. do.

FIG. 9 shows an example of a selection screen displayed when the user application 61 receives a selection request from the vehicle allocation integrated management device 12.

On the selection screen of FIG. 9, an area map 141 including the boarding place and the destination of the vehicle allocation request is displayed. Further, on the area map 141, a boarding place mark 142 indicating the boarding place of the vehicle allocation request, a destination mark 143 indicating the destination of the vehicle allocation request, and a planned travel route 144 to the destination are displayed.

In addition, on the area map 141, for example, "Which taxi do you choose? Time required to pick up / fare to destination Taxi A: 20 minutes / 12000 yen Taxi B: 05 minutes / 18000 yen" Message 151 is displayed.

Taxi A is a taxi 21 whose boarding place is outside the business area and whose destination is within the business area. Taxi B is a taxi 21 whose boarding place is within the business area and whose destination is outside the business area. Taxi A has a waiting time of 20 minutes until it arrives at the boarding place, which is longer than the waiting time of taxi B in the business area of 5 minutes. Has been applied. Therefore, the fare for taxi A is 12,000 yen, while the fare for taxi B is 18,000 yen.

Further, on the selection screen of FIG. 6, a selection button 152 operated when selecting taxi A and a selection button 153 operated when selecting taxi B are displayed.

The user decides whether to use taxi A or taxi B, and presses the selection button 152 or 153. The selection result corresponding to the selection button 152 or 153 is transmitted from the user application 61 to the vehicle allocation integrated management device 12.

Returning to FIG. 8, in step S131, the vehicle allocation management unit 54 receives the taxi selection result transmitted from the user application 61.

In step S132, the vehicle allocation management unit 54 determines the taxi 21 selected by the user as a vehicle allocation candidate, that is, the taxi 21 (taxi A) whose boarding location is outside the business area, or the taxi 21 (taxi B) whose boarding location is within the business area. ), Send a request to confirm the vehicle allocation.

In step S133, the vehicle allocation management unit 54 transmits a vehicle allocation confirmation notification to the user application 61 that has transmitted the vehicle allocation request.

After step S133 or step S123, the process returns to step S121, and the vehicle allocation management unit 54 waits until the next vehicle allocation request is received.

According to the above-mentioned second vehicle allocation process, the vehicle allocation integrated management device 12 allocates as much taxi 21 as possible to return to the inside of the business area from outside the business area even if there is some waiting time for the vehicle allocation request. Take control. Specifically, it is a taxi 21 traveling with the business area of the boarding place designated by the user as a destination, and a taxi 21 traveling outside the business area in which the business area of the boarding place is outside the business area is stored. From the list, the taxi 21 as a vehicle allocation candidate is determined and presented to the user together with the taxi 21 vehicle allocation candidate in the business area. In the taxi 21 of the taxi list traveling outside the business area, there is also a taxi 21 traveling in the business area of the boarding place, and at this stage, it is traveling outside the business area of the boarding place and is scheduled to travel in the business area of the boarding place. Also included. The vehicle allocation integrated management device 12 gives an incentive to the user when the vehicle allocation candidate taxi 21 extracted from the list of taxis traveling outside the business area is selected.

As a result, the taxi 21 that operates for the destination outside the business area can reduce the chance of returning to the business area as a deadhead as much as possible, and reduce the waste of time and fuel when returning from the outside of the business area to the inside of the business area. can.

In addition, the user who is a user of the taxi 21 can obtain an incentive such as a discounted rate by using the taxi 21 which is scheduled to return from outside the business area to the inside of the business area with some waiting time. .. Incentives are not limited to the application of discounted rates. For example, a discount coupon that can be used the next time a taxi is used, a coupon for free pick-up fee, a free ticket for shops that can be used around the boarding place or the destination, or a discount coupon may be used.

Since the user can obtain an incentive, the use of the taxi 21 scheduled to return from outside the business area to the inside of the business area is promoted, and it becomes easy to use the taxi over a long distance such as across the business area.

In the above-mentioned example of the second vehicle allocation process, the taxi 21 traveling outside the business area is registered in the taxi list traveling outside the business area, but the taxi 21 traveling outside the business area is registered as the destination. Not only the taxi 21 of the above, but also the taxi 21 traveling outside the business area by an empty car may be added to the list of taxis traveling outside the business area. In this case, the taxi 21 running outside the business area with an empty car can also be included in the dispatch candidates.

<6. 3rd vehicle allocation process of vehicle allocation integrated management device>
If there is a taxi 21 that is scheduled to return to the business area from outside the business area in response to a vehicle dispatch request from a user that straddles the business area, the business area will be subjected to the above-mentioned first vehicle allocation process or second vehicle allocation process. A taxi 21 that is scheduled to return to the business area from the outside can be used for dispatching, but such a taxi 21 may not exist, especially in the case of a long distance.

FIG. 10 shows the division of business areas in Tokyo.

The business areas of Tokyo include (1) special wards and Takesan districts centered on 23 wards, Tachikawa city, Kunitachi city, etc. (2) Kitatama transportation area, Hachioji city, Machida city, etc. ( It is divided into 3) Minamitama transportation area and (4) Nishitama transportation area including Ome city and Akiruno city.

For example, if the boarding place of the vehicle dispatch request is (1) a predetermined place in the special ward / Takesan district and the destination is (4) a predetermined place within the Nishitama transportation area, (1) outside the business area. ) There may be no taxi 21 scheduled to return to the (4) Nishitama transportation area in the business area from the designated place in the special ward / Takesan area.

However, for example, as shown in FIG. 10, (2) taxi 21 whose business area is the Kitatama transportation area, and (1) taxi A currently in the special zone / Takesan district exists and (4) If there is a taxi 21 that operates in the Nishitama transportation area and currently (2) taxi B is in the Kitatama transportation area, (1) from the boarding area in the special zone / Takesan district (2) north. Respond to user dispatch requests by a relay system that arranges taxi dispatch to taxi A to the Tama transportation area and arranges taxi dispatch to taxi B from (2) Kitatama transportation area to (4) Nishitama transportation area destination. be able to.

FIG. 11 is a flowchart of a third vehicle allocation process that enables vehicle allocation by the relay method. This process is started, for example, when a program that executes the vehicle allocation process is started in the server device as the vehicle allocation integrated management device 12.

First, in step S151, the vehicle allocation management unit 54 of the vehicle allocation integrated management device 12 determines from the user application 61 whether or not the vehicle allocation request has been received, and waits until it is determined that the vehicle allocation request has been received. If it is determined in step S151 that the vehicle allocation request has been received, the process proceeds to step S152.

In step S152, the vehicle allocation management unit 54 determines whether the business area of the destination and the boarding place of the transmitted vehicle allocation request are different.

If it is determined in step S152 that the business area of the boarding place and the destination is the same, the process proceeds to step S153, and the vehicle allocation management unit 54 executes a normal vehicle allocation process without particularly considering the difference in the business area. As the normal vehicle allocation process here, the processes of steps S42 to S47 of the normal vehicle allocation process described with reference to FIG. 4 are executed.

On the other hand, if it is determined in step S152 that the business area of the boarding place and the destination are different, the process proceeds to step S154, and the vehicle allocation management unit 54 uses the vehicle dynamic data stored in the vehicle dynamic data management unit 51. By referring to the taxi 21, the taxi 21 whose status is "empty" is extracted from the taxi 21 which can be dispatched to the boarding place where the dispatch request is made within a predetermined time.

In step S155, the vehicle allocation management unit 54 determines whether or not there is a taxi 21 whose business area is not the boarding place among the extracted taxi 21 that can be allocated. Whether or not the boarding place or the destination is a business area can be identified by checking the company ID or wireless ID of the taxi 21 included in the vehicle dynamic data, for example. In addition, the vehicle dynamic data may include business area information that identifies the business area of the taxi 21, and the determination may be made based on the information.

If it is determined in step S155 that there is no taxi 21 whose boarding location is not the business area, the process proceeds to step S153 described above, and a normal vehicle allocation process that does not particularly consider the difference in the business area is executed.

On the other hand, if it is determined in step S155 that there is a taxi 21 whose boarding place is not a business area, the process proceeds to step S156 described above, and the vehicle allocation management unit 54 extracts the taxi 21 whose boarding place is not a business area. ..

Next, in step S157, the vehicle allocation management unit 54 determines whether or not there is a taxi 21 whose business area is the destination among the taxi 21 that can be allocated in step S156.

If it is determined in step S157 that there is a taxi 21 whose business area is the destination, the process proceeds to step S158, and the vehicle allocation management unit 54 is among the taxi 21 that can be allocated in step S156. The taxi 21 whose business area is the land is extracted, and the business area destination vehicle allocation process for transmitting the vehicle allocation request is executed. As the vehicle allocation process for the business area destination, for example, the processes of steps S126 to S132 of the second vehicle allocation process in FIG. 8 are executed.

On the other hand, if it is determined in step S157 that the taxi 21 having the destination as the business area does not exist, the process proceeds to step S159 described above, and the vehicle allocation management unit 54 moves between the boarding place and the destination. Determine if there is a business area for.

If it is determined in step S159 that there is no other business area between the boarding place and the destination, the process proceeds to step S153, and a normal vehicle allocation process that does not particularly consider the difference in the business area is executed.

On the other hand, if it is determined in step S159 that there is another business area between the boarding place and the destination, the process proceeds to step S160, and the vehicle allocation management unit 54 exists near the boarding place of the vehicle allocation request. It is determined whether or not there is a taxi 21 having a business area (hereinafter, referred to as a relay area) between the business area of the boarding place and the business area of the destination, which can be dispatched.

If it is determined in step S160 that the taxi 21 having the relay area as the business area does not exist, the process proceeds to step S153, and the normal vehicle allocation process that does not particularly consider the difference in the business area is executed.

On the other hand, if it is determined in step S160 that a taxi 21 having a relay area as a business area exists, the process proceeds to step S161, and the vehicle allocation management unit 54 exists near the boarding place of the vehicle allocation request and can allocate a vehicle. , Extract the taxi 21 whose business area is the relay area.

Then, in step S162, the vehicle allocation management unit 54 determines whether or not there is a taxi 21 having a destination as a business area, which exists in the relay area and can be allocated.

If it is determined in step S162 that there is no taxi 21 that exists in the relay area and can be dispatched and whose destination is the business area, the process proceeds to step S153, and the normal vehicle dispatch that does not particularly consider the difference in the business area is performed. The process is executed.

On the other hand, if it is determined in step S162 that there is a taxi 21 having a destination as a business area that exists in the relay area and can be dispatched, the process proceeds to step S163, and the vehicle allocation management unit 54 moves to the relay area. A taxi 21 whose business area is a destination that exists and can be dispatched is extracted.

Next, in step S164, the vehicle allocation management unit 54 includes the taxi 21 that can arrive at the boarding place earliest among the taxis 21 extracted in step S161 and the taxi 21 extracted in step S163. A taxi 21 outside the business area that can arrive at the relay point at the scheduled transfer time is determined as a vehicle allocation candidate, and a vehicle allocation candidate request is transmitted to the taxi 21 that is a vehicle allocation candidate. Here, the relay point is a place where the taxi A transfers to the taxi B in the example of FIG. 10, and the scheduled transfer time is the scheduled time when the taxi A arrives at the relay point. The relay point can be determined according to the current location of the taxi 21 (taxi B) extracted in step S163.

In step S165, the vehicle allocation management unit 54 determines whether or not the request acceptance notification has been received from the two taxis 21 that have transmitted the vehicle allocation candidate request.

In step S165, if the request acceptance notification is not received within a certain period of time (for example, 15 seconds) from the two taxis 21 that have sent the vehicle allocation candidate request, or if the request refusal notification is transmitted, the process is step. Proceeding to S153, a normal vehicle allocation process that does not particularly consider the difference in business areas is executed.

On the other hand, if it is determined in step S165 that the taxi 21 that has sent the vehicle allocation candidate request has received the request acceptance notification, in step S166, the vehicle allocation management unit 54 requests the user application 61 to select two types of taxi 21. To send.

Here, the selection screen displayed on the user application 61 is a screen that allows the user to select one of the two types of taxi 21, similar to the selection screen described with reference to FIG. 6, and one taxi 21 has a discounted charge. Is a relay type taxi 21 to which the above is applied, and the other taxi 21 is a taxi 21 whose boarding place is within the business area. The taxi 21 whose boarding place is in the business area is extracted in step S154.

In step S167, the vehicle allocation management unit 54 receives the taxi selection result transmitted from the user application 61.

In step S168, the vehicle allocation management unit 54 transmits a vehicle allocation confirmation request to the taxi 21 which is a vehicle allocation candidate selected by the user.

In step S169, the vehicle allocation management unit 54 transmits a vehicle allocation confirmation notification to the user application 61 that has transmitted the vehicle allocation request.

After step S169, step S158, or step S153, the process returns to step S151, and the vehicle allocation management unit 54 waits until the next vehicle allocation request is received.

According to the above third vehicle allocation process, the vehicle allocation integrated management device 12 includes the first taxi 21 in which the boarding place specified by the user is outside the business area and the relay area is in the business area, and the relay area is the business area. The user is presented with a relay system for connecting to a second taxi 21 which is outside and whose destination is within the business area. By adopting the relay system, it is possible to control so as to dispatch the taxi 21 scheduled to return from outside the business area to the inside of the business area as much as possible.

As a result, the taxi 21 that operates for the destination outside the business area can reduce the chance of returning to the business area as a deadhead as much as possible, and reduce the waste of time and fuel when returning from the outside of the business area to the inside of the business area. can.

Further, the user who is a user of the taxi 21 can obtain an incentive such as a discount rate by using the taxi 21 which is scheduled to return from outside the business area to the inside of the business area by allowing the relay method. Incentives are not limited to the application of discounted rates. For example, a discount coupon that can be used the next time a taxi is used, a coupon for free pick-up fee, a free ticket for shops that can be used around the boarding place or the destination, or a discount coupon may be used.

Since the user can obtain an incentive, the use of the taxi 21 scheduled to return from outside the business area to the inside of the business area is promoted, and it becomes easy to use the taxi over a long distance such as across the business area.

<7. Other examples of the vehicle allocation request screen of the user application>
In the vehicle allocation control described above, when the business area of the user's destination is a business area different from the business area of the boarding place, the vehicle allocation integrated management device 12 determines the taxi 21 scheduled to return from outside the business area to the inside of the business area. Although the control is such that the taxi is dispatched as much as possible, the user may be able to positively specify the taxi 21 that is scheduled to return to the inside of the business area from outside the business area.

12 and 13 show an example of a vehicle allocation request screen of such a user application 61.

In FIGS. 12 and 13, the description of the portion common to the vehicle allocation request screen of the user application 61 shown in FIG. 3 will be omitted as appropriate.

On the vehicle allocation request screen of FIG. 12, the user's boarding place "5-chome, Takanawa, Shinagawa-ku, Tokyo" input to the boarding place input unit 83 and the user's destination input to the destination input unit 84 " The business area of taxi 21 is different from "3-9, Kawasaki City, Kanagawa Prefecture".

When the business area of the boarding place and the destination are different, specify the selected taxi search mode outside the business area to actively search and use the taxi 21 scheduled to return to the business area from outside the business area in the user application 61. Can be done.

The mode setting unit 161 displayed on the area map 81 of the vehicle allocation request screen of FIG. 12 actively searches for and uses the taxi 21 scheduled to return to the inside of the business area from outside the business area. A button to switch between selection and deselection.

As shown in FIG. 12, when "No" is selected in the mode setting unit 161, the taxi search mode outside the business area is not selected. In this case, the vehicle allocation control that does not consider the business area is executed, and the empty taxi mark 91C indicating the taxi 21 with the status of "empty" displayed on the area map 81 is all the taxi 21 whose business area is the boarding place. Become.

On the other hand, as shown in FIG. 13, when "Yes" is selected in the mode setting unit 161, the taxi search mode outside the business area is selected. In this case, the taxi 21 scheduled to return from outside the business area to the inside of the business area is searched and displayed on the area map 81. The empty taxi mark 91D displayed on the area map 81 of FIG. 13 is a taxi 21 whose business area is "3-9 Kawasaki City, Kanagawa Prefecture", which is the user's destination entered in the destination input unit 84. The taxi 21 whose status is "empty" is represented.

In this way, the user may be able to positively specify the taxi 21 that is scheduled to return from outside the business area to inside the business area. Further, the empty taxi mark 91 displayed on the area map 81 of the vehicle allocation request screen may be displayed in a different color or pattern depending on the business area.

<8. Modification example>
The taxi 21 is generally operated with people on board, but it is also permitted to carry luggage on behalf of people. Therefore, the above-mentioned vehicle allocation process can be applied not to the transportation of people but also to the transportation of luggage.

When the customer data management unit 52 stores the customer's home and work location as customer data and the home and work location are in different business areas, for example, the user may use a Friday night or a rainy day. If there is a taxi 21 that is in the business area near the work location and the business area is near the work location, the function to recommend the use of the taxi 21 that returns from outside the business area near the work location to the business area near the home is recommended. Can have. The user can register his / her home and work location in the user application 61 and set the recommendation function by turning it on / off. When the taxi 21 is used by the recommendation function, the use can be promoted by applying a discounted fare rather than the normal fare.

The driver application 35 mounted on the terminal device 33 of the taxi 21 can display the forecast data for predicting the boarding demand of the taxi 21 based on the history (boarding record) of the past actual vehicle data. For example, the driver application 35 displays the places and landings where the taxi 21 is in high demand by color coding and symbols on the map, and displays the number of predicted passengers. The driver application 35 may perform the prediction process for predicting the passenger demand, or the vehicle allocation integrated management device 12 (for example, the vehicle dynamic data management unit 51) performs the prediction process and transmits the prediction data to the driver application 35 for display. May be.

When the driver application 35 has a function of displaying the boarding demand of the taxi 21, it may have a function of displaying the boarding demand specialized for a place where many passengers move out of the business area. For example, if the business area of a taxi 21 is (2) Kitatama transportation area shown in Fig. 10, and the current location of taxi 21 is (1) in the special zone / Takesan district, (2) Kitatama. It is possible to display the boarding demand of passengers who board in the traffic area as a destination. This makes it easier for the taxi 21 outside the business area to acquire passengers returning to the business area.

In the above-described embodiment, an example of controlling the dispatch of a taxi as a mobile device has been described, but other mobile devices for carrying customers (people), specifically, buses, trains, airplanes, ships, helicopters, etc. , It can also be applied to mobile devices such as mobile devices for loading objects (luggage), trucks, and dumps. Further, the moving device may be an unmanned moving device such as a drone. Further, the business area is not limited to the legal one, and may be a rule inside the transportation service operated by the business entity.

<9. Computer configuration example>
The series of processes described above can be executed by hardware or software. When a series of processes are executed by software, the programs constituting the software are installed on the computer. Here, the computer includes a microcomputer embedded in dedicated hardware and, for example, a general-purpose personal computer capable of executing various functions by installing various programs.

FIG. 14 is a block diagram showing a configuration example of computer hardware when the computer executes each process executed by the vehicle allocation integrated management device 12, the user terminal 13, or the terminal device 33 by a program.

In a computer, a CPU (Central Processing Unit) 201, a ROM (Read Only Memory) 202, and a RAM (Random Access Memory) 203 are connected to each other by a bus 204.

An input / output interface 205 is further connected to the bus 204. An input unit 206, an output unit 207, a storage unit 208, a communication unit 209, and a drive 210 are connected to the input / output interface 205.

The input unit 206 includes operation buttons, a keyboard, a mouse, a microphone, a touch panel, an input terminal, and the like. The output unit 207 includes a display, a speaker, an output terminal, and the like. The storage unit 208 includes a hard disk, a RAM disk, a non-volatile memory, and the like. The communication unit 209 includes a network interface and the like. The drive 210 drives a removable recording medium 211 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.

In the computer configured as described above, the CPU 201 loads the program stored in the storage unit 208 into the RAM 203 via the input / output interface 205 and the bus 204 and executes the above-described series. Is processed. The RAM 203 also appropriately stores data and the like necessary for the CPU 201 to execute various processes.

The program executed by the computer (CPU201) can be recorded and provided on the removable recording medium 211 as a package medium or the like, for example. Programs can also be provided via wired or wireless transmission media such as local area networks, the Internet, and digital satellite broadcasts.

In the computer, the program can be installed in the storage unit 208 via the input / output interface 205 by mounting the removable recording medium 211 in the drive 210. Further, the program can be received by the communication unit 209 and installed in the storage unit 208 via a wired or wireless transmission medium. In addition, the program can be pre-installed in the ROM 202 or the storage unit 208.

In the present specification, the system means a set of a plurality of components (devices, modules (parts), etc.), and it does not matter whether or not all the components are in the same housing. Therefore, a plurality of devices housed in separate housings and connected via a network, and a device in which a plurality of modules are housed in one housing are both systems. ..

Further, in the present specification, the steps described in the flowchart are not necessarily processed in chronological order as well as in chronological order in the order described, but are called in parallel or are called. It may be executed at a necessary timing such as when.

The embodiment of the present technology is not limited to the above-described embodiment, and various changes can be made without departing from the gist of the present technology.

For example, a form in which all or a part of the above-described embodiments are combined can be adopted.

For example, the present technology can have a cloud computing configuration in which one function is shared by a plurality of devices via a network and jointly processed.

Further, each step described in the above-mentioned flowchart can be executed by one device or can be shared and executed by a plurality of devices.

Further, when a plurality of processes are included in one step, the plurality of processes included in the one step can be executed by one device or shared by a plurality of devices.

It should be noted that the effects described in the present specification are merely examples and are not limited, and effects other than those described in the present specification may be obtained.

The present technology can have the following configurations.
(1)
When the boarding place and the destination of the vehicle allocation request sent from the terminal device of the user who is the taxi user are different from the business area, the boarding place is outside the business area and the destination is within the business area. A vehicle allocation management device equipped with a management unit that extracts a certain taxi and sends a vehicle allocation request to the extracted taxi.
(2)
The management unit determines whether the boarding place of the vehicle allocation request sent from the terminal device and the business area of the destination are different, and if it is determined that they are different, the boarding place is outside the business area and the said The vehicle allocation management device according to (1) above, which extracts taxis whose destination is within the business area.
(3)
The management unit has a taxi that can be dispatched to the boarding place of the vehicle dispatch request transmitted from the terminal device within a predetermined time, the boarding place is outside the business area, and the destination is within the business area. The vehicle allocation management device according to (1) or (2) above, which extracts a taxi.
(4)
The management unit is in a taxi that is traveling or is scheduled to travel in the business area of the boarding place of the vehicle allocation request transmitted from the terminal device, the boarding place is outside the business area, and the destination is in the business area. The vehicle allocation management device according to any one of (1) to (3) above, which extracts a taxi.
(5)
The management unit is traveling with the business area of the boarding place of the vehicle allocation request transmitted from the terminal device as the destination, and generates a taxi list for traveling outside the business area, which is a list of taxis whose boarding place is outside the business area. The vehicle allocation management device according to (4) above, which extracts a taxi whose boarding place is outside the business area and whose destination is within the business area from the list of taxis traveling outside the business area.
(6)
The management department requests selection of either the first taxi in the business area or the second taxi in the business area where the boarding place is outside the business area and the destination is the second taxi in the business area. The vehicle allocation management device according to (4) or (5), which is transmitted to the terminal device.
(7)
The vehicle allocation management device according to (6) above, wherein the management unit gives an incentive to the user when the second taxi is selected.
(8)
The incentive is the vehicle allocation management device according to (7) above, which is a discount on the fare.
(9)
The taxi list for traveling outside the business area includes taxis that are running in the business area of the boarding place of the vehicle allocation request transmitted from the terminal device and whose boarding place is outside the business area (7). The vehicle allocation management device according to any one of (8) to (8).
(10)
When another business area exists as a relay area between the business area of the boarding place of the vehicle allocation request transmitted from the terminal device and the business area of the destination, the management unit may perform the boarding place. Extracts a first taxi whose relay area is outside the business area and whose relay area is within the business area, and extracts a second taxi whose relay area is outside the business area and whose destination is within the business area. The vehicle allocation management device according to any one of (5) to (9) above.
(11)
The vehicle allocation management device
When the boarding place and the destination of the vehicle allocation request sent from the terminal device of the user who is the taxi user are different from the business area, the boarding place is outside the business area and the destination is within the business area. A vehicle allocation management method that extracts a taxi and sends a vehicle allocation request to the extracted taxi.
(12)
Computer,
When the boarding place and the destination of the vehicle allocation request sent from the terminal device of the user who is the taxi user are different from the business area, the boarding place is outside the business area and the destination is within the business area. A program that extracts a taxi and makes it function as a management unit that sends a dispatch request to the extracted taxi.

1 Taxi dispatch system, 11 Vehicle allocation management device, 12 Vehicle allocation management device, 13 Terminal device (user terminal), 21 Taxi, 31 In-vehicle device, 33 Terminal device, 34 Vehicle dynamic data generator, 35 Driver application, 41 Vehicle dynamic data Management Department, 42 Order Information Management Department, 51 Vehicle Dynamics Data Management Department, 52 Customer Data Management Department, 53 Order Information Management Department, 54 Vehicle Allocation Management Department, 61 User App, 201 CPU, 202 ROM, 203 RAM, 206 Input Department, 207 output unit, 208 storage unit, 209 communication unit, 210 drive

Claims (12)

When the boarding place and the destination of the vehicle allocation request sent from the terminal device of the user who is the taxi user are different from the business area, the boarding place is outside the business area and the destination is within the business area. A vehicle allocation management device equipped with a management unit that extracts a certain taxi and sends a vehicle allocation request to the extracted taxi. The management unit determines whether the boarding place of the vehicle allocation request sent from the terminal device and the business area of the destination are different, and if it is determined that they are different, the boarding place is outside the business area and the said The vehicle allocation management device according to claim 1, wherein a taxi whose destination is within a business area is extracted. The management unit has a taxi that can be dispatched to the boarding place of the vehicle dispatch request transmitted from the terminal device within a predetermined time, the boarding place is outside the business area, and the destination is within the business area. The vehicle allocation management device according to claim 1, wherein the taxi is extracted. The management unit is in a taxi that is traveling or is scheduled to travel in the business area of the boarding place of the vehicle allocation request transmitted from the terminal device, the boarding place is outside the business area, and the destination is in the business area. The vehicle allocation management device according to claim 1, wherein the taxi is extracted. The management unit is traveling with the business area of the boarding place of the vehicle allocation request transmitted from the terminal device as the destination, and generates a taxi list for traveling outside the business area, which is a list of taxis whose boarding place is outside the business area. The vehicle allocation management device according to claim 4, wherein a taxi whose boarding place is outside the business area and whose destination is within the business area is extracted from the list of taxis traveling outside the business area. The management unit makes a selection request to select either the first taxi in the business area or the second taxi in the business area where the boarding place is outside the business area. The vehicle allocation management device according to claim 4, which is transmitted to the terminal device. The vehicle allocation management device according to claim 6, wherein the management unit gives an incentive to the user when the second taxi is selected. The vehicle allocation management device according to claim 7, wherein the incentive is a discount on the fare. The taxi list for traveling outside the business area includes a taxi that is traveling in the business area of the boarding place of the vehicle allocation request transmitted from the terminal device with an empty vehicle, and the boarding place includes a taxi outside the business area. The vehicle allocation management device described. When another business area exists as a relay area between the business area of the boarding place of the vehicle allocation request transmitted from the terminal device and the business area of the destination, the management unit may perform the boarding place. Extracts a first taxi whose relay area is outside the business area and whose relay area is within the business area, and extracts a second taxi whose relay area is outside the business area and whose destination is within the business area. The vehicle allocation management device according to claim 1. The vehicle allocation management device
When the boarding place and the destination of the vehicle allocation request sent from the terminal device of the user who is the taxi user are different from the business area, the boarding place is outside the business area and the destination is within the business area. A vehicle allocation management method that extracts a taxi and sends a vehicle allocation request to the extracted taxi. Computer,
When the boarding place and the destination of the vehicle allocation request sent from the terminal device of the user who is the taxi user are different from the business area, the boarding place is outside the business area and the destination is within the business area. A program that extracts a taxi and makes it function as a management unit that sends a dispatch request to the extracted taxi.

Images