Vehicle allocation device, vehicle allocation system, vehicle allocation method, and program

Abstract

To implement a vehicle allocation in accordance with the policy of a company.SOLUTION: A vehicle allocation device comprises a server which is communicable with a plurality of vehicle terminals provided on a vehicle basis. The server carries out processing for acquiring a vehicle allocation request, processing for extracting one or more vehicles from among a plurality of vehicles in accordance with a predetermined extraction condition on the basis of the acquired vehicle allocation request, and processing for notifying a vehicle terminal which is provided on the extracted vehicle of predetermined information. Vehicle identification information is preset to the vehicle, and the predetermined extraction condition includes a condition on which a vehicle to which specific vehicle identification information is set is to be extracted while taking priority over the other vehicles.SELECTED DRAWING: Figure 13

Description

[Technical Field]

[0001] The present invention relates to a vehicle dispatch device, a vehicle dispatch system, a vehicle dispatch method, and a program. [Background technology]

[0002] A taxi dispatch system that receives a taxi dispatch request from a user and dispatches a taxi is known. For example, Patent Document 1 discloses a technology that estimates the arrival times of the user and a taxi at the user's desired boarding location, matches the estimated results, and dispatches a taxi so as to minimize the difference between the estimated results. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2023-027694 Summary of the Invention [Problem to be solved by the invention]

[0004] The dispatch of taxis through the dispatch system is managed by each operator, but there is a problem in that it is difficult to realize dispatch in accordance with each operator's policy. For example, for taxi operators who aim to reduce their environmental impact, it is desirable to prioritize dispatching taxis with low environmental impact, such as electric vehicles and hybrid vehicles. However, in conventional dispatch systems, priority is given to the arrival time of the taxi at the user's boarding location, which can result in only taxis with high environmental impact being dispatched.

[0005] As such, while each operator has its own policies, the actual dispatch of vehicles by the dispatch system may be contrary to the operator's policies. Therefore, there is a need for technology that can realize dispatch of vehicles in accordance with each operator's policies.

[0006] In view of the above problems, the present invention aims to provide a vehicle dispatching device, a vehicle dispatching system, a vehicle dispatching method, and a program that can realize vehicle dispatch in accordance with the policy of an operator. [Means for solving the problem]

[0007] In order to solve the above problem, the vehicle dispatching device a server capable of communicating with a plurality of vehicle terminals provided in each vehicle; The server A process of obtaining a dispatch request; A process of extracting one or more of the vehicles from the plurality of vehicles in accordance with predetermined extraction conditions based on the acquired vehicle dispatch request; a process of notifying the vehicle terminal provided in the extracted vehicle of predetermined information; and Vehicle identification information is preset in the vehicle, The predetermined extraction conditions include: The vehicle identification information may include a condition that the vehicle having the specific vehicle identification information set is extracted with higher priority than other vehicles.

[0008] The specific vehicle identification information may be set for an electric vehicle.

[0009] The specific vehicle identification information may be set for vehicles that do not operate as a taxi service, vehicles that operate as hire cars, Japanese-style ride-sharing vehicles, or vehicles operated by drivers who work only at specific times.

[0010] In order to solve the above problems, the dispatch system a server capable of communicating with a plurality of vehicle terminals provided in each vehicle; The server A process of obtaining a dispatch request; A process of extracting one or more of the vehicles from the plurality of vehicles in accordance with predetermined extraction conditions based on the acquired vehicle dispatch request; a process of notifying the vehicle terminal provided in the extracted vehicle of predetermined information; and Vehicle identification information is preset in the vehicle, The predetermined extraction conditions include: The vehicle identification information may include a condition that the vehicle having the specific vehicle identification information set is extracted with higher priority than other vehicles.

[0011] In order to solve the above problem, the vehicle dispatch method is as follows: A vehicle dispatch method performed by a server capable of communicating with a plurality of vehicle terminals provided for each vehicle, comprising: The server A process of obtaining a dispatch request; A process of extracting one or more of the vehicles from the plurality of vehicles in accordance with predetermined extraction conditions based on the acquired vehicle dispatch request; a process of notifying the vehicle terminal provided in the extracted vehicle of predetermined information; and Vehicle identification information is preset in the vehicle, The predetermined extraction conditions include: The vehicle identification information may include a condition that the vehicle having the specific vehicle identification information set is extracted with higher priority than other vehicles.

[0012] In order to solve the above problem, the program A server capable of communicating with a plurality of vehicle terminals provided for each vehicle, A process of obtaining a dispatch request; A process of extracting one or more of the vehicles from the plurality of vehicles in accordance with predetermined extraction conditions based on the acquired vehicle dispatch request; a process of notifying the vehicle terminal provided in the extracted vehicle of predetermined information; and Vehicle identification information is preset in the vehicle, The predetermined extraction conditions include: The vehicle identification information may include a condition that the vehicle having the specific vehicle identification information set is extracted with higher priority than other vehicles. [Effects of the Invention]

[0013] According to the present invention, it is possible to realize vehicle allocation in accordance with the operator's policy. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a block diagram for explaining an outline of a vehicle dispatch management system. [Figure 2] FIG. 2 is a block diagram illustrating the configuration of a user terminal. [Figure 3] FIG. 3 is a block diagram illustrating the configuration of the taxi terminal. [Figure 4] FIG. 4 is a block diagram illustrating the configuration of the NRS terminal. [Figure 5] FIG. 5 is a block diagram illustrating the configuration of the business server. [Figure 6] FIG. 6 is a block diagram illustrating the configuration of the vehicle dispatch management server. [Figure 7] FIG. 7 is a sequence diagram showing the flow of processing in a vehicle allocation management method performed by the vehicle allocation management system. [Figure 8] FIG. 8 is an explanatory diagram for explaining the processing of the vehicle extraction unit. [Figure 9] FIG. 9 is a first explanatory diagram for explaining the pair creation process. [Figure 10] FIG. 10 is a second explanatory diagram for explaining the pair creation process. [Figure 11] FIG. 11 is an explanatory diagram of the preferential vehicle setting screen. [Figure 12] FIG. 12 is an explanatory diagram showing the results of matching by the matching unit. [Figure 13] FIG. 13 is a third explanatory diagram for explaining the pair creating process. DETAILED DESCRIPTION OF THE INVENTION

[0015] Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Dimensions, materials, and other specific values ​​shown in the embodiments are merely examples for facilitating understanding of the invention and, unless otherwise specified, do not limit the present invention. In this specification and drawings, elements having substantially the same functions and configurations are designated by the same reference numerals to avoid redundant explanation, and elements not directly related to the present invention are not shown.

[0016] (Vehicle Dispatch Management System 1) FIG. 1 is a block diagram for explaining an overview of a vehicle dispatch management system 1. The vehicle dispatch management system 1 includes a plurality of user terminals 20, a plurality of taxi terminals 30, a plurality of taxi vehicles 32, a plurality of NRS terminals 40, a plurality of NRS vehicles 42, one or more business operator servers 50, and one or more vehicle dispatch management servers 60. In the vehicle dispatch management system 1, NRS vehicles 42 are included in addition to taxi vehicles 32 as commercial vehicles that serve as transportation means for users 2. Here, NRS is an abbreviation for Nippon-style Ride Share or Nihon-gata Ride Share, and refers to a service in which ordinary drivers transport users 2 for a fee using their own cars or the like.

[0017] The user terminal 20 is an electronic device owned by the user 2. The user 2 is a passenger in a commercial vehicle (such as a taxi vehicle 32 or an NRS vehicle 42). Examples of the user terminal 20 include a smartphone, a personal computer, and a tablet PC. In the vehicle dispatch management system 1, there are multiple combinations of users 2 and user terminals 20. Note that the user 2 in this embodiment is not limited to one person, and may refer to multiple people who can ride in one taxi vehicle 32.

[0018] 2 is a block diagram illustrating the configuration of the user terminal 20. The user terminal 20 includes a communication device 120, a processing device 122, a display device 124, an input device 126, and a storage device 128. The communication device 120 is connected to an external device, such as a vehicle dispatch management server 60, via a base station 5 and a network 6 so as to be able to communicate with the external device.

[0019] The processing device 122 has a semiconductor integrated circuit including a processor such as a CPU (Central Processing Unit), a ROM (Read Only Memory) storing programs and the like, and a RAM (Random Access Memory) used as a work area. A user application for the vehicle dispatch management system 1 is installed in the user terminal 20. The processing device 122 controls the user application by running the program, and functions as a vehicle dispatch request unit 180 that supports the user 2 in inputting a vehicle dispatch request, etc.

[0020] The display device 124 includes a liquid crystal display, an organic EL (Electro Luminescence) display, or the like, and displays various information such as an image of a user application for requesting a vehicle dispatch.

[0021] The input device 126 includes a touch panel, switches, buttons, keys, a microphone for voice input, etc., superimposed on the display device 124, and receives input from the user 2, such as information for requesting a vehicle dispatch.

[0022] The storage device 128 is configured by a storage means such as an HDD (Hard Disk Drive), an SD memory, or an SSD (Solid State Drive).

[0023] 3 is a block diagram illustrating the configuration of the taxi terminal 30. The taxi terminal 30 is an electronic device loaned to a taxi driver 3 of a taxi vehicle 32, or an electronic device owned by the taxi driver 3. The taxi terminal 30 is associated with the taxi vehicle 32. Examples of the taxi terminal 30 include a smartphone, a personal computer, and a tablet PC. The taxi terminal 30 is an example of a vehicle terminal.

[0024] The taxi terminal 30 includes a communication device 130, a processing device 132, a display device 134, an input device 136, and a storage device 138. The communication device 130 is connected to an external device, such as an operator server 50 or a vehicle dispatch management server 60, via a base station 5 and a network 6 so as to be able to communicate with the external device.

[0025] The processing device 132 has a semiconductor integrated circuit including a processor (CPU), a ROM storing programs and the like, a RAM used as a work area, and the like. A vehicle application for the vehicle dispatch management system 1 is installed in the taxi terminal 30. The processing device 132 controls the vehicle application by running the program, and functions as a dispatch response unit 182 that supports the taxi driver 3 in inputting responses to dispatch requests, etc.

[0026] The display device 134 includes a liquid crystal display and an organic EL display, and displays various information such as the fact that one's own taxi vehicle 32 has become the target of a dispatch request (dispatch target notification), information related to the dispatch request (boarding location, user information related to user 2, disembarking location), etc. Hereinafter, the target of the dispatch request may be referred to as the "dispatch target," and the vehicle that has become the dispatch target may be referred to as the "dispatch target vehicle."

[0027] The input device 136 includes a touch panel, switches, buttons, keys, a microphone for voice input, etc., superimposed on the display device 134, and receives input from the taxi driver 3, such as acceptance of a request for dispatching a taxi.

[0028] The storage device 138 is composed of storage means such as an HDD, SD memory, or SSD. The taxi terminal 30 can acquire its own location on a map through location identification means such as a GPS (Global Positioning System). The storage device 138 also stores information indicating vehicle attributes, which will be described in detail later, and vehicle identification information. The vehicle identification information classifies vehicles according to their environmental load, and is information that can identify, for example, whether the vehicle is an electric vehicle, a hybrid vehicle, or a gasoline-powered vehicle.

[0029] The taxi driver 3 is a driver who holds a Class 2 driver's license for a standard vehicle and belongs to a taxi business (general passenger automobile transportation business). The taxi vehicle 32 is, for example, a vehicle that belongs to a taxi business and can transport the user 2 as a taxi business for a fee. In the vehicle dispatch management system 1, there are multiple combinations of taxi drivers 3, taxi vehicles 32, and taxi terminals 30. Note that in this embodiment, an example of a four-wheeled taxi (hire car) is given as the taxi vehicle 32 to be dispatched, but the taxi vehicle 32 is not limited to this example, and may include, for example, a motorcycle (motorcycle taxi) or the like as long as it is a vehicle capable of transporting people.

[0030] FIG. 4 is a block diagram illustrating the configuration of the NRS terminal 40. The NRS terminal 40 is an electronic device owned by the NRS driver 4 and can be installed in the NRS vehicle 42. Examples of the NRS terminal 40 include a smartphone, a personal computer, and a tablet PC. The NRS driver 4, for example, brings his / her own NRS terminal 40 into the NRS vehicle 42, which is his / her personal car, and drives the NRS vehicle 42. The NRS terminal 40 is not limited to being brought into the vehicle while driving, but may also be pre-installed in the NRS vehicle 42. The NRS terminal 40 is used when the NRS driver 4 is on duty. This allows the NRS vehicle 42 to be used as a commercial vehicle in place of the taxi vehicle 32. The NRS terminal 40 is an example of a vehicle terminal.

[0031] The NRS terminal 40 includes a communication device 140, a processing device 142, a display device 144, an input device 146, and a storage device 148. The communication device 140 is connected to an external device, such as an operator server 50 or a vehicle dispatch management server 60, via a base station 5 and a network 6 so as to be able to communicate with the external device.

[0032] The processing device 142 has a semiconductor integrated circuit including a processor (CPU), a ROM storing programs and the like, and a RAM used as a work area. A vehicle application for the vehicle dispatch management system 1 is installed in the NRS terminal 40. The processing device 142 controls the vehicle application by running the program and functions as a vehicle dispatch response unit 184 that supports the NRS driver 4 in inputting responses to vehicle dispatch requests, etc.

[0033] The display device 144 includes an LCD display and an organic EL display, and displays various information such as the fact that the user's NRS vehicle 42 has become a target for dispatch (dispatch target notification), information regarding the dispatch request (boarding location, disembarking location, user information regarding user 2), etc.

[0034] The input device 146 includes a touch panel, switches, buttons, keys, a microphone for voice input, etc., superimposed on the display device 144, and receives input from the NRS driver 4, such as approval of a vehicle dispatch request.

[0035] The storage device 148 is configured with storage means such as an HDD, SD memory, SSD, etc. The NRS terminal 40 can acquire its own position on a map through location identification means such as GPS. The storage device 148 also stores information indicating vehicle attributes and vehicle identification information.

[0036] The NRS driver 4 is a driver who holds a Class 1 driver's license for a standard vehicle and is involved in a ride-sharing business (a private vehicle passenger transportation business for a fee). However, in this embodiment, an example will be described in which a taxi business also manages the ride-sharing business based on Article 78, Paragraph 3 of the Road Transportation Act. Therefore, the NRS driver 4 can be said to be a driver who is involved in a taxi business.

[0037] The NRS driver 4 differs from the taxi driver 3 in that he / she may not have a Class 2 driver's license for a regular vehicle or may have poor driving skills and knowledge. The NRS vehicle 42 is, for example, a vehicle driven by the NRS driver 4, and can transport the user 2 for a fee as part of a ride-sharing business. The NRS vehicle 42 can be a private car or an idle taxi vehicle 32.

[0038] In the vehicle dispatch management system 1, there are multiple combinations of NRS drivers 4, NRS vehicles 42, and NRS terminals 40. Note that the NRS drivers 4 cannot operate a so-called cruising business, which is to say, search for users 2 who want to ride while driving the taxi vehicles 32, as the taxi drivers 3 do. However, in the case of paid passenger transportation by private car based on Article 78, Paragraph 3 of the Road Transportation Act, the NRS drivers 4 can charge the users 2 a fee (fare) equivalent to that of a general passenger automobile transportation business as compensation for transporting the users 2.

[0039] Such taxi vehicles 32 and NRS vehicles 42 have designated operating areas in which they can operate. A taxi vehicle 32 can operate in the operating area where its taxi business office is located. For example, if the operating area is within Tokyo's special wards, the taxi vehicle 32 can operate in Tokyo's 23 wards, Musashino City, and Mitaka City. The operating area of ​​such a taxi vehicle 32 may be referred to as a transportation area.

[0040] The operating area of ​​the NRS vehicle 42 is included in the operating area of ​​the taxi vehicle 32, and is often smaller than the operating area of ​​the taxi vehicle 32. Furthermore, the operating area of ​​the taxi vehicle 32 is limited in geographical area but not in time, whereas the operating area of ​​the NRS vehicle 42 is limited in geographical area and also in time, for example, only during hours (including periods) when the supply of taxi vehicles 32 is insufficient to meet the demand.

[0041] In this way, a taxi shortage situation in an area, time period, or time zone where there is a shortage of taxi vehicles 32 is considered to be "unavoidable for the public welfare" under Article 78, paragraph 3 of the Road Transportation Act, and a ride-sharing business is permitted. Note that the operating area of ​​the NRS vehicle 42 is managed by a taxi business operator, just like the operating area of ​​the taxi vehicle 32, and is subject to the same regulations as the operating area of ​​the taxi vehicle 32. Note that in this embodiment, an example is given in which the operation of the NRS vehicle 42 is restricted not only in terms of the geographical range of the operating area but also in terms of the time period, but this is not limiting, and there are also cases in which the operating area is restricted only in terms of the geographical range, with no time restrictions.

[0042] Hereinafter, for the sake of convenience, when there is no need to distinguish between taxi vehicle 32 and NRS vehicle 42, automobiles that transport user 2 for a fee, including taxi vehicle 32 and NRS vehicle 42, may be collectively referred to simply as "vehicles." Also, when there is no need to distinguish between taxi driver 3 and NRS driver 4, drivers, including taxi driver 3 and NRS driver 4, may be collectively referred to simply as "drivers."

[0043] Furthermore, when there is no need to distinguish between the taxi terminal 30 and the NRS terminal 40, the devices possessed by the driver, including the taxi terminal 30 and the NRS terminal 40, may be collectively referred to simply as the "vehicle terminal," the display devices of the vehicle terminal, including the display device 134 and the display device 144, may be collectively referred to simply as the "vehicle display device," the input devices of the vehicle terminal, including the input device 136 and the input device 146, may be collectively referred to simply as the "vehicle input device," and the dispatch response units of the vehicle terminal, including the dispatch response unit 182 and the dispatch response unit 184, may be collectively referred to simply as the "vehicle dispatch response unit."

[0044] 5 is a block diagram illustrating the configuration of the business operator server 50. The business operator server 50 is an information processing device (computer) owned by a business operator that operates a taxi business. The business operator server 50 manages taxi vehicles 32 driven by taxi drivers 3 belonging to a taxi business and NRS vehicles 42 driven by NRS drivers 4. The business operator server 50 includes a communication device 150, a processing device 152, a display device 154, an input device 156, and a storage device 158.

[0045] The communication device 150 is connected to external devices, such as a taxi terminal 30, an NRS terminal 40, and a vehicle dispatch management server 60, via a network 6 so as to be able to communicate with each other.

[0046] The processing device 152 has a semiconductor integrated circuit including a processor (CPU), a ROM storing programs and the like, a RAM used as a work area, etc. By running a program, the processing device 152 functions as a vehicle management unit 186 that manages vehicles belonging to the taxi business operator.

[0047] The display device 154 includes a liquid crystal display or an organic EL display, and displays various information such as driver or vehicle information obtained directly from the vehicle or obtained via the vehicle dispatch management server 60.

[0048] The input device 156 includes a keyboard, a touch panel superimposed on the display device 154, a microphone for voice input, etc., and receives input from an operator at the business. For example, the operator can talk to the driver or check images of the inside and outside of the vehicle, including an image of the driver, through the business server 50.

[0049] The storage device 158 is configured with storage means such as an HDD, SD memory, or SSD.

[0050] FIG. 6 is a block diagram for explaining the configuration of the vehicle dispatch management server 60. The vehicle dispatch management server 60 is an information processing device (computer) that manages vehicles belonging to a taxi company based on a contract between the vehicle dispatch management company and the taxi company. The vehicle dispatch management server 60 is an example of a vehicle dispatch management device with server functions, and is operated by the vehicle dispatch management company. The vehicle dispatch management server 60 can dispatch a vehicle to a user 2 in response to a vehicle dispatch request from a user terminal 20. The vehicle dispatch management server 60 includes a communication device 160, a processing device 162, and a storage device 164.

[0051] The communication device 160 is connected to external devices, such as a user terminal 20, a taxi terminal 30, an NRS terminal 40, and an operator server 50, via a network 6 so as to be able to communicate with each other.

[0052] The processing device 162 has a semiconductor integrated circuit including a processor (CPU), a ROM storing programs and the like, a RAM used as a work area, etc. By running programs, the processing device 162 functions as functional units such as a user terminal control unit 170, a vehicle dispatch unit 172, and a vehicle terminal control unit 174.

[0053] The user terminal control unit 170 controls the user applications installed in the user terminal 20. The vehicle allocation unit 172 allocates a vehicle in response to a vehicle allocation request. The vehicle terminal control unit 174 controls the vehicle applications installed in the vehicle terminal.

[0054] The storage device 164 is configured with storage means such as an HDD, SD memory, or SSD, and stores information about the user 2 and the vehicle.

[0055] In the vehicle dispatch management system 1, for example, one vehicle is assigned to one vehicle dispatch request from one user 2. However, if multiple users 2 each make a vehicle dispatch request at different times, the vehicle assigned to the first user 2 may be located near another user 2 who made a later vehicle dispatch request, resulting in inefficient vehicle dispatch. Here, vehicle dispatch requests made within a specified period are accumulated, and multiple vehicle dispatch requests are matched with multiple vehicles at once, thereby enabling efficient vehicle dispatch.

[0056] (Vehicle allocation management method) FIG. 7 is a sequence diagram showing the processing flow of the vehicle dispatch management method by the vehicle dispatch management system 1. The vehicle dispatch management system 1 extracts one or more vehicles that can be dispatched from a plurality of vehicles for each dispatch request, and identifies one vehicle to be dispatched through matching. The vehicle dispatch management system 1 then asks the driver of the vehicle that has been selected as the dispatch target vehicle to dispatch the vehicle, and when the driver accepts the dispatch inquiry, the dispatch is confirmed. Each process in the vehicle dispatch management method will be described in detail below.

[0057] (Vehicle dispatch request processing S1) When user 2 wishes to ride in a vehicle, user 2 makes a vehicle dispatch request through user terminal 20. Specifically, vehicle dispatch request unit 180 of user terminal 20 launches a user application for making a vehicle dispatch request. The user application displays a map of a predetermined range including the current location of user terminal 20, and displays vehicles (e.g., taxi vehicles 32 and NRS vehicles 42) located near user terminal 20. Vehicle dispatch request unit 180 accepts user 2's vehicle dispatch request through input device 126. At this time, user 2 can set setting items for the vehicle to be boarded. Vehicle dispatch request unit 180 adds information related to the setting items set by user 2 and transmits the vehicle dispatch request to vehicle dispatch management server 60.

[0058] In addition to the initial setting of desired dispatch, the setting items include, for example, boarding location, disembarking location, payment information, dispatch category, taxi company, vehicle attributes, toll road information, etc.

[0059] The boarding location indicates the location on the map where User 2 wishes to board the vehicle. User 2 can set User 2's current location as the boarding location, or can set a desired location different from User 2's current location as the boarding location.

[0060] The drop-off location indicates the location on the map where User 2 wishes to get off. When User 2 sets the boarding location and the drop-off location among the setting items, the fare calculated based on the set time, boarding location, and drop-off location is displayed on the display device 124. In this way, User 2 can know in advance the fare that will be paid by getting on the vehicle.

[0061] When user 2 limits the vehicle dispatch targets to taxi vehicles 32 only, the drop-off location is not required input information but is information that can be input optionally. On the other hand, when user 2 includes NRS vehicles 42 in the vehicle dispatch targets, the drop-off location becomes required input information. This is because, in ride-sharing based on Article 78, Paragraph 3 of the Road Transportation Act, a requirement for dispatch (a requirement for dispatching an NRS vehicle 42) is that the fare must be determined in advance. Therefore, when including NRS vehicles 42 in the vehicle dispatch targets, user 2 must input the drop-off location in addition to the boarding location in order to calculate the fare in advance.

[0062] The payment information is information regarding payment of fees associated with vehicle use (e.g., fares and other additional fees). When an NRS vehicle 42 is included in the vehicle dispatch target, in addition to inputting the drop-off location, payment information also requires information regarding cashless automatic payment by credit card or the like (e.g., a credit card number). This is because ride-sharing services based on Article 78, Paragraph 3 of the Road Transportation Act require that a vehicle dispatch request be made through a user application and that cashless automatic payment be made as a requirement for vehicle dispatch. Here, automatic payment refers to a process in which, after the vehicle arrives at the drop-off location, the driver can bill User 2 for the fee associated with vehicle use based on User 2's automatic payment information, without User 2 paying cash or entering electronic money information into a cashless terminal. Thus, the NRS vehicle 42 differs from the taxi vehicle 32 in that the NRS vehicle 42 requires inputting the drop-off location and automatic payment information as a requirement for vehicle dispatch.

[0063] The dispatch category indicates the category of the vehicle to be dispatched. For example, as described above, taxi drivers 3 often have a Class 2 driver's license for a standard vehicle and have high driver qualifications, driving skills, knowledge, etc. On the other hand, NRS drivers 4 vary in driver qualifications, driving skills, knowledge, etc. Furthermore, there are certain drivers who have a Class 2 driver's license for a standard vehicle but are not regularly employed as taxi drivers 3, and who, for example, rent vehicles from taxi companies to transport users 2.

[0064] Even among such specific drivers, there are often variations in driver qualifications, driving skills, knowledge, etc. When a specific vehicle driven by a specific driver is to be dispatched, the user 2 must input information regarding the drop-off location and automatic payment, just as with the NRS vehicle 42. Here, vehicles that have different dispatch requirements from the taxi vehicle 32, including the NRS vehicle 42 and specific vehicles, may be simply referred to as "vehicles with requirements."

[0065] As the driver's qualifications vary depending on the vehicle, some user 2 may wish to be dispatched with a taxi vehicle 32 driven by a taxi driver 3. In this case, user 2 selects "taxi vehicle 32 only" as the dispatch category. On the other hand, if the dispatch target is limited to taxi vehicles 32, user 2 will miss the opportunity to ride in a vehicle with requirements even in a situation where a vehicle with requirements can be dispatched quickly. Therefore, user 2 may not limit the dispatch target to taxi vehicles 32, but may wish to dispatch taxi vehicles 32 and vehicles with requirements so that he or she can ride in a vehicle quickly. In this case, user 2 may select "taxi vehicle 32 and vehicles with requirements" as the dispatch category.

[0066] Here, a dispatch mode in which a taxi vehicle 32 is allocated in response to a dispatch request but a vehicle with requirements is not allocated is referred to as a first dispatch mode, and a dispatch mode in which either a taxi vehicle 32 or a vehicle with requirements is allocated in response to a dispatch request is referred to as a second dispatch mode. User 2 can transition from the first dispatch mode to the second dispatch mode by inputting the boarding location, disembarking location, and information regarding automatic payment through user terminal 20. Also, as described above, user 2 can select "taxi vehicle 32 only" or "taxi vehicle 32 and vehicle with requirements" as the dispatch category.

[0067] Therefore, even if information about the drop-off location and automatic payment has been input, if user 2 selects "only taxi vehicles 32" as the dispatch category, the mode transitions from the second dispatch mode to the first dispatch mode. User 2 can set the purpose of using the vehicle (for example, use for business purposes) or can set not to input the drop-off location in advance. In this case, even if the user does not input a specific dispatch category, only taxi vehicles 32 will be dispatched automatically (first dispatch mode). If user 2 does not input the drop-off location in advance, the driver may be notified directly, or the drop-off location may be input via the user terminal 20 after getting in. Furthermore, when user 2 uses taxi vehicles 32 for business purposes, an additional fee may be charged to user 2 personally, or may be charged to the company or business entity to which user 2 belongs.

[0068] In this embodiment, an example will be described in which there are a first dispatch mode and a second dispatch mode as the dispatch mode. However, the present invention is not limited to this example, and if there are other circumstances, such as a cheaper fare to ride in a vehicle with special requirements than in a taxi vehicle 32, a third dispatch mode may be provided as the dispatch mode in which a taxi vehicle 32 is not allocated to a dispatch request, but a vehicle with special requirements is allocated.

[0069] The taxi company indicates the company to which the taxi driver 3 or NRS driver 4 belongs as a taxi business. The user 2 can specify a desired taxi company by inputting information into the taxi company setting item.

[0070] The vehicle attributes indicate the type and equipment of the vehicle. Examples of vehicle attributes include whether the vehicle is a high-class vehicle (a so-called hire car), whether it is wheelchair accessible, whether it has sliding doors, etc. User 2 can specify the attributes of the vehicle he or she wishes to dispatch by inputting the vehicle attribute setting items.

[0071] The toll road information indicates whether or not to use a toll road such as an expressway. If the toll road information indicates that a toll road will be used, the toll road will be actively included in the route from the boarding point to the disembarking point.

[0072] (Dispatch request accumulation process S2) The user terminal control unit 170 of the vehicle dispatch management server 60 controls the user application of the user terminal 20 and performs processing corresponding to the dispatch request input through the user application. When the user terminal control unit 170 receives a dispatch request from the user terminal 20, it first identifies which of multiple operating areas the boarding location in the setting items is included in. The user terminal control unit 170 assigns the same identifier (taxi operating area ID) to dispatch requests sent in the same operating area. The user terminal control unit 170 associates the dispatch request received from the user terminal 20, including information on the various setting items described above, with the operating area identifier and the time of receipt of the dispatch request, and sequentially stores them in the storage device 164.

[0073] (Vehicle dispatch request extraction process S3) The vehicle dispatch unit 172 of the vehicle dispatch management server 60 extracts all vehicle dispatch requests that have occurred in a specified business area up to a specified execution timing from among the multiple vehicle dispatch requests stored in the storage device 164. Here, the execution timing indicates the timing at which the vehicle dispatch request extraction process S3 is started for the multiple vehicle dispatch requests, and is expressed, for example, as a time. The execution timing is set periodically and repeatedly at a specified processing interval. Therefore, a new execution timing is set after a specified processing period has elapsed since the vehicle dispatch request extraction process S3 was started at the previous execution timing. Here, the specified processing period is the length of time for which vehicle dispatch requests to be processed at one time are accumulated, and is set to, for example, 5 seconds.

[0074] However, in reality, in the matching started at the previous execution timing, a vehicle to be allocated may not have been determined for a vehicle allocation request. Such vehicle allocation requests for which a vehicle to be allocated has not been determined are carried over to the current execution timing, and matching continues. Therefore, the vehicle allocation unit 172 extracts, as vehicle allocation requests accumulated up to the current execution timing, vehicle allocation requests for which a vehicle to be allocated has not been determined in the previous matching, in addition to vehicle allocation requests accumulated from the previous execution timing to the current execution timing.

[0075] (Vehicle extraction process S4) The vehicle dispatch unit 172 extracts one or more vehicles that satisfy predetermined extraction conditions related to the vehicle dispatch request extracted in the vehicle dispatch request extraction process S3 from among multiple vehicles that can accommodate the user 2. Here, the extraction conditions include conditions for the various setting items in the vehicle dispatch request, such as the vehicle dispatch category. If the vehicle dispatch category in the vehicle dispatch request is set to "taxi vehicles 32 only," the vehicle dispatch unit 172 extracts only taxi vehicles 32 for the vehicle dispatch request. Also, if the vehicle dispatch category in the vehicle dispatch request is set to "taxi vehicles 32 and vehicles with requirements," the vehicle dispatch unit 172 extracts taxi vehicles 32 and vehicles with requirements for the vehicle dispatch request.

[0076] Further, an example of an extraction condition is that the estimated time of arrival at the boarding location is short. Specifically, an example of the extraction condition is that the distance between the boarding location and the current location of the vehicle is within a predetermined distance (e.g., 10 km), or that the estimated time of arrival at the boarding location is within a predetermined time (e.g., 10 minutes). In this case, the distance is the Euclidean distance between the boarding location and the current location of the vehicle, and the estimated time of arrival is the time obtained by dividing the Euclidean distance by a predetermined speed (e.g., the average speed when the vehicle is operating). Furthermore, the dispatch unit 172 may further limit the number of vehicles to be extracted to a predetermined number (e.g., 10 vehicles) as an extraction condition in order of the shortest distance between the boarding location and the current location of the vehicle or the shortest estimated time of arrival at the boarding location.

[0077] 8 is an explanatory diagram for explaining the processing of the vehicle dispatch unit 172. FIG. 8 shows four users 2a to 2d who have made vehicle dispatch requests within the service area A, and eleven vehicles 32a, 42b, 32c, 32d, 32e, 42f, 32g, 32h, 42i, 42j, and 32k that exist within the service area A. In this embodiment, seven taxi vehicles 32a, 32c, 32d, 32e, 32g, 32h, and 32k and four NRS vehicles 42b, 42f, 42i, and 42j are shown. It is assumed that the service area A is a service area where the service area of ​​the taxi vehicle 32 and the service area of ​​the NRS vehicle 42 are the same.

[0078] The vehicle allocation unit 172 sets extraction conditions for each of the vehicle allocation requests extracted in the vehicle allocation request extraction process S3, i.e., for each of the vehicle allocation requests 22a to 22d of the users 2a to 2d. Here, the extraction condition is that the distance between the boarding location and the current location of the vehicle is equal to or less than a predetermined distance. Therefore, extraction conditions 24a to 24d, shown by dashed arcs in FIG. 8, are set for each of the vehicle allocation requests 22a to 22d of the users 2a to 2d.

[0079] The vehicle dispatch unit 172 extracts vehicles that satisfy extraction conditions 24a to 24d for each of the vehicle dispatch requests 22a to 22d of users 2a to 2d. For example, the vehicles that satisfy extraction condition 24a for user 2a's vehicle dispatch request 22a are vehicles 32a, 42b, 32c, 32d, and 32e. The vehicles that satisfy extraction condition 24b for user 2b's vehicle dispatch request 22b are vehicles 32e, 42f, 32g, 32h, and 42i. The vehicles that satisfy extraction condition 24c for user 2c's vehicle dispatch request 22c are vehicles 32d, 32e, 42f, 32h, and 42i. The vehicles that satisfy extraction condition 24d for user 2d's vehicle dispatch request 22d are vehicles 32d, 42i, and 42j.

[0080] The vehicle dispatch unit 172 extracts all of the vehicles 32a, 42b, 32c, 32d, 32e, 42f, 32g, 32h, 42i, and 42j, which are surrounded by solid lines in Figure 8 and satisfy any one of the extraction conditions 24a to 24d for each of the vehicle dispatch requests 22a to 22d, and excludes vehicle 32k, which does not satisfy any of the extraction conditions 24a to 24d, as a vehicle that has no possibility of being dispatched.

[0081] (Pair generation process S5) The vehicle allocation unit 172 extracts at least one vehicle that satisfies a predetermined pairing condition from the vehicles 32a, 42b, 32c, 32d, 32e, 42f, 32g, 32h, 42i, and 42j extracted in the vehicle extraction process S4 for each vehicle allocation request 22 extracted in the vehicle allocation request extraction process S3, and associates the extracted vehicle with the vehicle allocation request 22. Here, the pairing condition is that the vehicle satisfies all of the setting items of the vehicle allocation request 22.

[0082] For example, if the attribute of a vehicle included in the setting items of the vehicle allocation request 22 is "sliding door compatible," the vehicle is determined to be "compatible" if the attribute of the vehicle has a sliding door. Also, for example, if the vehicle allocation category included in the setting items of the vehicle allocation request 22 is "taxi vehicles 32 only," the vehicle is determined to be "compatible" if it is a taxi vehicle 32. The vehicle allocation unit 172 determines that a vehicle that does not comply with one or more setting items of the vehicle allocation request 22 does not satisfy the pairing condition. On the other hand, the vehicle allocation unit 172 associates a vehicle that complies with all setting items of the vehicle allocation request 22 with the vehicle allocation request 22 as a vehicle that satisfies the pairing condition of the vehicle allocation request 22.

[0083] Fig. 9 is a first explanatory diagram for explaining the pair generation process, and Fig. 10 is a second explanatory diagram for explaining the pair generation process. Here, it is assumed that all of the vehicles 32a, 42b, 32c, 32d, 32e, 42f, 32g, 32h, 42i, and 42j extracted by the vehicle allocation unit 172 are compatible with the setting items of the vehicle allocation requests 22a to 22c of the users 2a to 2c. Also, it is assumed that all of the extracted vehicles 42b, 32c, 32d, 32e, 32g, 32h, and 42i are compatible with the vehicle attributes (e.g., sliding door compatibility) included in the setting items of the vehicle allocation request 22d of the user 2d, but that the vehicles 32a, 42f, and 42j are not compatible.

[0084] In the example of FIG. 9, in response to the vehicle allocation request 22a from user 2a, the vehicle allocation unit 172 extracts vehicles that satisfy the pairing conditions of the vehicle allocation request 22a from vehicles 32a, 42b, 32c, 32d, 32e, 42f, 32g, 32h, 42i, and 42j, and sets these vehicles as pair candidate vehicles 220a-220j. Here, taxi vehicles 32 and NRS vehicles 42 are identified as pair candidate vehicles 220 without distinction. Then, the vehicle allocation unit 172 associates the pair candidate vehicles 220a-220j with the vehicle allocation request 22a from user 2a. Similarly, the vehicle allocation unit 172 associates the pair candidate vehicles 220a-220j with the vehicle allocation request 22b from user 2b. Furthermore, the vehicle allocation unit 172 associates the pair candidate vehicles 220a-220j with the vehicle allocation request 22c from user 2c.

[0085] In addition, in response to the vehicle allocation request 22d of user 2d, the vehicle allocation unit 172 extracts vehicles 42b, 32c, 32d, 32e, 32g, 32h, and 42i that satisfy the pairing conditions of the vehicle allocation request 22d of user 2d from vehicles 32a, 42b, 32c, 32d, 32e, 42f, 32g, 32h, 42i, and 42j, and sets these vehicles as pair candidate vehicles 220b, 220c, 220d, 220e, 220g, 220h, and 220i. Then, the vehicle allocation unit 172 associates the pair candidate vehicles 220b, 220c, 220d, 220e, 220g, 220h, and 220i with the vehicle allocation request 22d of user 2d. In this way, as shown in FIG. 10(a), one or more pair candidate vehicles 220 are associated with each of the vehicle allocation requests 22a to 22d.

[0086] Here, the vehicle dispatch unit 172 determines whether the vehicle is suitable for all the setting items of the vehicle dispatch request 22. However, this is not the only case, and if the vehicle dispatch unit 172 has already determined the suitability of some of the setting items, such as the desired vehicle dispatch or the sales office, the vehicle dispatch unit 172 may omit determining the suitability of those setting items. In this way, the processing load on the vehicle dispatch management server 60 can be reduced.

[0087] Next, the vehicle allocation unit 172 estimates the estimated arrival time of the associated pair candidate vehicle 220 at the desired boarding location for each of the vehicle allocation requests 22a to 22d, and associates the estimated arrival time with each of the pair candidate vehicles 220. Since the positional relationship between the user 2 who made the vehicle allocation request 22 and the vehicle differs for each vehicle allocation request 22, the estimated arrival time for each vehicle allocation request 22 differs even for the same pair candidate vehicle 220.

[0088] Next, the vehicle allocation unit 172 sets priorities for the pair candidate vehicles 220 associated with each vehicle allocation request 22. Here, the priorities indicate the order in which the vehicle should be allocated. When setting the priorities, the vehicle allocation unit 172 recalculates the estimated time of arrival at the desired boarding location. At this time, the shorter the recalculated estimated time of arrival, the higher the priority. The recalculated estimated time of arrival is the travel time taking into account the route until the vehicle arrives at the desired boarding location. Furthermore, the vehicle allocation unit 172 may derive the travel time by taking into account, in addition to the route, the vehicle's travel direction at the time of vehicle extraction, the stop time at traffic lights along the route, and the like. Therefore, the vehicle allocation unit 172 can set priorities using estimated arrival times that are more accurate than the estimated arrival times based on the extraction conditions (Euclidean distance) used by the vehicle allocation unit 172.

[0089] Here, the vehicle dispatch management company or the taxi company can set in advance a vehicle that will be preferentially dispatched over other vehicles. A "vehicle that will be preferentially dispatched" refers to a vehicle that is more likely to be determined as the vehicle to be dispatched than other vehicles when multiple pair candidate vehicles 220 are associated with the vehicle dispatch request 22. In this embodiment, a case will be described in which a vehicle that will be preferentially dispatched over other vehicles is set by the vehicle dispatch management company. However, a vehicle that will be preferentially dispatched over other vehicles may also be set by the taxi company. Hereinafter, a vehicle that has been set by the vehicle dispatch management company or the taxi company as a "vehicle that will be preferentially dispatched" will be referred to as a preferred vehicle.

[0090] For example, a vehicle dispatching management company can pre-select vehicles with low environmental impact as preferred vehicles. Specifically, the vehicle dispatching management company can select either or both of electric vehicles and hybrid vehicles as preferred vehicles. In this case, electric vehicles or hybrid vehicles are more likely to be selected as vehicles to be dispatched than gasoline-powered vehicles.

[0091] FIG. 11 is an explanatory diagram of a preferred vehicle setting screen. Here, it is assumed that an operator of the vehicle dispatch management business can set a preferred vehicle by inputting a setting operation into the input device 156 of the business server 50. For example, the preferred vehicle setting screen shown in FIG. 11 is displayed on the display device 154 of the business server 50. This preferred vehicle setting screen is provided with a setting operation unit 154a1 that accepts an operation to set an electric vehicle as a preferred vehicle, and a cancellation operation unit 154a2 that accepts a cancellation operation to cancel the setting of the preferred vehicle. When an operation input is made to the setting operation unit 154a1, a state in which it is tentatively selected to set the electric vehicle as a preferred vehicle is achieved, and when an operation input is made to the cancellation operation unit 154a2, a state in which it is tentatively selected not to set the electric vehicle as a preferred vehicle is achieved.

[0092] The preferred vehicle setting screen also has a setting operation unit 154b1 that accepts an operation to set a hybrid vehicle as a preferred vehicle, and a cancellation operation unit 154b2 that accepts a cancellation operation to cancel the preferred vehicle setting. When an operation input is made to the setting operation unit 154b1, the hybrid vehicle is provisionally selected to be set as a preferred vehicle, and when an operation input is made to the cancellation operation unit 154b2, the hybrid vehicle is provisionally selected not to be set as a preferred vehicle.

[0093] 11 shows a state in which it has been provisionally selected to set electric vehicles as preferred vehicles and to not set hybrid vehicles as preferred vehicles. As shown in FIG. 11, on the preferred vehicle setting screen, the operation unit corresponding to the provisionally selected state is highlighted out of the setting operation units 154a1, 154b1 or the cancellation operation units 154a2, 154b2.

[0094] The preferential vehicle setting screen is provided with a transmission operation unit 154c, and when an operation input is made to the transmission operation unit 154c, setting information indicating whether or not a preferential vehicle is set is transmitted to the vehicle allocation management server 60. When the setting information is received, the setting information is stored in the storage device 164 of the vehicle allocation management server 60.

[0095] An input device may be provided in the vehicle dispatch management server 60, and the preferred vehicle may be set directly in the vehicle dispatch management server 60. Here, it is assumed that the setting information of the preferred vehicle can be updated, but for example, a program for executing the pair generation process S5 may be configured in advance so that the preferred vehicle is preferentially dispatched.

[0096] As described above, when setting the priority order, the vehicle allocation unit 172 recalculates the estimated arrival time of each pair candidate vehicle 220 at the desired boarding location. At this time, the vehicle allocation unit 172 determines whether the pair candidate vehicle 220 is a preferred vehicle, adjusts the estimated arrival time of the pair candidate vehicle 220 determined to be a preferred vehicle, and calculates an adjusted estimated arrival time that is shorter than the recalculated estimated arrival time. Note that, for ease of understanding, a case where no preferred vehicle is included among the pair candidate vehicles 220 will be described first, and then a case where a preferred vehicle is included among the pair candidate vehicles 220 will be described. Therefore, the examples shown in FIGS. 9 and 10 show a case where all of the pair candidate vehicles 220a to 220j are not preferred vehicles, i.e., are gasoline vehicles.

[0097] 10(a) and 10(b), the vehicle allocation unit 172 rearranges the pair candidate vehicles 220a to 220j associated with the vehicle allocation request 22a into pair candidate vehicles 220b, 220d, 220c, 220e, 220a, 220f, 220i, 220h, 220g, and 220j in order of shortest recalculated estimated arrival times. Similarly, the vehicle allocation unit 172 rearranges the pair candidate vehicles 220a to 220j associated with the vehicle allocation request 22b into pair candidate vehicles 220i, 220h, 220f, 220e, 220g, 220d, 220a, 220b, 220j, and 220c in order of shortest recalculated estimated arrival times. Furthermore, the vehicle allocation unit 172 rearranges the pair candidate vehicles 220a to 220j associated with the vehicle allocation request 22c into pair candidate vehicles 220i, 220e, 220d, 220f, 220h, 220g, 220c, 220b, 220j, and 220a in order of shortest recalculated estimated arrival times. The vehicle allocation unit 172 also rearranges the pair candidate vehicles 220b, 220c, 220d, 220e, 220g, 220h, and 220i associated with the vehicle allocation request 22d into pair candidate vehicles 220i, 220d, 220h, 220e, 220c, 220g, and 220b in order of shortest recalculated estimated arrival times.

[0098] 10(b), one or more pair candidate vehicles 220 are prioritized for each of the vehicle allocation requests 22a to 22d, and one or more combinations of vehicle allocation requests 22 and pair candidate vehicles 220 are generated. Here, it can be seen that the priority of the pair candidate vehicles 220 corresponding to each of the vehicle allocation requests 22a to 22d differs depending on the positional relationship between the users 2a to 2d and the pair candidate vehicles 220.

[0099] 10(b), one or more pair candidate vehicles 220 are associated with each of the vehicle allocation requests 22a to 22d in a prioritized order, i.e., in the order of shortest expected arrival time at the desired boarding location. Therefore, the vehicle allocation management server 60 can assign a vehicle with the shortest expected arrival time by extracting pair candidate vehicles 220 in the order of highest priority for each of the vehicle allocation requests 22a to 22d.

[0100] Furthermore, in this example, all vehicles available for dispatch are associated with each of the dispatch requests 22a to 22d, and a priority order is set. This is because there are cases where the dispatch-requested vehicle cannot accept the dispatch request. For example, suppose that a vehicle is cruising, accepting a ride request from a user 2 it finds on the driving route, and simultaneously receiving a ride request from a user 2 nearby the driving route, at the same time as the dispatch request 22 from user 2a to 2d. In this case, the vehicle cannot accept the dispatch request 22 because it is trying to pick up the nearby user 2. Therefore, even if the dispatch-requested vehicle cannot accept the dispatch request for some reason, the dispatch management server 60 can efficiently assign a vehicle with a short estimated arrival time to each of the dispatch requests 22a to 22d by extracting the pair candidate vehicle 220 with the next highest priority order.

[0101] However, as shown by the dashed line in Figure 10(b), among the vehicle allocation requests 22a to 22d, there may be cases where the pair candidate vehicles 220 with the highest priority overlap in the vehicle allocation requests 22b, 22c, and 22d. In this case, the vehicle allocation management server 60 will not be able to appropriately assign the pair candidate vehicles 220 as the vehicle allocation requested vehicles for the vehicle allocation requests 22b, 22c, and 22d. Therefore, the vehicle allocation unit 172 matches the vehicle allocation requests 22 with the pair candidate vehicles 220.

[0102] (Matching process S6) The vehicle allocation unit 172 matches the vehicle allocation requests 22 with vehicles for multiple combinations of the vehicle allocation requests 22 associated with the vehicles in the pair generation process S5. In this matching process, the vehicle allocation requests 22 are matched with the vehicles such that the vehicle with the highest priority among the at least one vehicle associated with each vehicle allocation request 22 does not overlap with at least one vehicle associated with another vehicle allocation request 22. For example, the vehicle allocation unit 172 exclusively matches the vehicle with the shortest average estimated arrival time with each of the vehicle allocation requests 22a to 22d. Note that various existing matching algorithms can be applied as the matching algorithm between the vehicle allocation requests 22 and vehicles, and therefore detailed description thereof will be omitted in this embodiment.

[0103] 12 is an explanatory diagram showing the results of matching by the vehicle allocation unit 172. The vehicle allocation unit 172 uses a predetermined matching algorithm to, for example, exclusively determine the NRS vehicle 42b (pair candidate vehicle 220b) for the vehicle allocation request 22a. Similarly, exclusively determine the taxi vehicle 32h (pair candidate vehicle 220h) for the vehicle allocation request 22b. Similarly, exclusively determine the NRS vehicle 42i (pair candidate vehicle 220i) for the vehicle allocation request 22c. Similarly, exclusively determine the taxi vehicle 32d (pair candidate vehicle 220d) for the vehicle allocation request 22d.

[0104] Then, the vehicle allocation unit 172 determines one vehicle 42b, 32h, 42i, 32d associated with each of the vehicle allocation requests 22a to 22d as a vehicle to be allocated that is the vehicle to be allocated for the vehicle allocation requests 22a to 22d. In this way, the vehicle allocation unit 172 matches multiple vehicle allocation requests 22 with multiple vehicles at once and determines a vehicle to be allocated for each vehicle allocation request 22. In this way, compared to matching vehicle allocation requests 22 individually and sequentially, it is possible to optimize matching by comprehensively determining the positional relationships between the positions of multiple users 2 and multiple vehicles, thereby enabling efficient vehicle allocation.

[0105] (Vehicle dispatch notification process S7) The vehicle terminal control unit 174 of the vehicle dispatch management server 60 controls the vehicle application of the vehicle terminal and performs vehicle dispatch management through the vehicle application. The vehicle terminal control unit 174 notifies the vehicle terminal disposed in the vehicle that has become the dispatch target vehicle in response to the dispatch request 22 of information (dispatch target notification) indicating that the vehicle has become the target of the dispatch request 22. This dispatch target notification corresponds to a prompt to the driver of the dispatch target vehicle as to whether or not to accept the dispatch request 22. In this way, the driver of the vehicle recognizes that his or her vehicle has become the target of the dispatch request 22, and can consider whether or not to accept the dispatch request 22.

[0106] (Acceptance response processing S8) When the vehicle dispatch response unit of the vehicle terminal arranged in the vehicle receives information indicating that the vehicle has been the target of the vehicle dispatch request 22 from the vehicle terminal control unit 174, the vehicle dispatch response unit notifies the driver of this fact, for example, via a vehicle display device. When notifying the information, the vehicle terminal may also display information about the vehicle dispatch request 22 (for example, the boarding location, user information about user 2) on the vehicle display device. Note that if a drop-off location has been input by user 2, for example, after the vehicle arrives at user 2's boarding location, the vehicle terminal may display the information about the drop-off location on the vehicle display device as information about the vehicle dispatch request 22. When accepting the vehicle dispatch request 22, the driver accepts the vehicle dispatch request 22 via the vehicle input device of the vehicle terminal, for example, by tapping a position corresponding to a "request acceptance" button displayed on the vehicle display device. The vehicle dispatch response unit transmits information about the acceptance of the vehicle dispatch request 22 (acceptance response), including acceptance of the vehicle dispatch request 22, to the vehicle dispatch management server 60.

[0107] If the driver cannot accept the vehicle allocation request 22 for some reason, the driver taps the "request reject" button displayed on the vehicle input device of the vehicle terminal to reject the vehicle allocation request 22, or does not tap the position corresponding to "request accept." The vehicle terminal control unit 174 waits for a predetermined time (e.g., 10 seconds) from the time the vehicle allocation target notification is sent, and if it does not receive information regarding acceptance of the vehicle allocation request 22 (acceptance response) from the vehicle terminal during the waiting time, it determines that the driver of the vehicle to be allocated has not accepted the vehicle allocation request 22. In this case, the vehicle allocation unit 172 determines the vehicle with the second highest priority among the vehicles associated with the vehicle allocation request 22 in the matching process S6 as the new vehicle to be allocated. Next, the vehicle terminal control unit 174 notifies the vehicle terminal of the other vehicle that has become the new vehicle to be allocated of information indicating that it has become the target of the vehicle allocation request 22 (vehicle allocation target notification).

[0108] (Vehicle dispatch completion notification process S9) When the vehicle terminal control unit 174 receives information (acceptance response) regarding acceptance of the vehicle allocation request 22 from the vehicle terminal, it confirms the allocation of the vehicle to be allocated in response to the vehicle allocation request 22 and transmits a vehicle allocation completion notification indicating that the vehicle allocation has been confirmed to the vehicle terminal. At this time, information regarding the vehicle allocation request 22, such as the boarding location and the route to the boarding location, is displayed on the vehicle display device of the vehicle terminal. With this configuration, the driver of the vehicle can grasp the information regarding the vehicle allocation request 22, drive an appropriate route toward the boarding location, and quickly find the user 2. Note that if the vehicle to be allocated is a vehicle with requirements (an NRS vehicle 42 or a specified vehicle), the vehicle terminal control unit 174 may display other information, such as the drop-off location, in addition to the boarding location, as information regarding the vehicle allocation request 22 on the vehicle display device of the vehicle terminal of such a vehicle.

[0109] (User vehicle dispatch completion notification process S10) When the user terminal control unit 170 confirms the dispatch of the vehicle to be dispatched in response to the vehicle dispatch request 22, it transmits a user vehicle dispatch completion notification to the user terminal 20 indicating that the vehicle dispatch has been confirmed. At this time, the display device 124 of the user terminal 20 displays the location of the vehicle to be dispatched, the estimated arrival time, etc. In this way, user 2 can appropriately board the vehicle at the boarding location. Note that if the vehicle dispatch unit 172 is unable to assign a vehicle to be dispatched in response to the vehicle dispatch request 22, the vehicle dispatch request 22 temporarily enters a vehicle dispatch failed (vehicle dispatch impossible) state. In this case, the display device 124 of the user terminal 20 displays information indicating that the vehicle dispatch was not possible and information indicating that the vehicle dispatch request 22 can be executed again. User 2 will execute the vehicle dispatch request 22 again based on this information.

[0110] Next, the pair generation process S5 in the case where the vehicles extracted by the vehicle allocation unit 172 include a preferential vehicle will be described.

[0111] 13 is a third explanatory diagram illustrating the pair generation process. Here, it is assumed that all of the vehicles 32a, 42b, 32c, 32d, 32e, and 42f extracted by the vehicle allocation unit 172 match the setting items of the vehicle allocation request 22a of the user 2a. Also, it is assumed that all of the extracted vehicles 32a, 42b, 32c, 32d, and 32e match the vehicle attributes included in the setting items of the vehicle allocation request 22b of the user 2b, but that vehicle 42f does not match.

[0112] 13, in response to a vehicle allocation request 22a from user 2a, the vehicle allocation unit 172 extracts vehicles that satisfy the pairing conditions of the vehicle allocation request 22a from vehicles 32a, 42b, 32c, 32d, 32e, and 42f, and sets these vehicles as pair candidate vehicles 220a-220f. Then, the vehicle allocation unit 172 associates the pair candidate vehicles 220a-220f with the vehicle allocation request 22a from user 2a. Similarly, in response to a vehicle allocation request 22b from user 2b, the vehicle allocation unit 172 extracts vehicles 32a, 42b, 32c, 32d, 32e, and 42f, and sets these vehicles as pair candidate vehicles 220a, 220b, 220c, 220d, and 220e. Then, the vehicle allocation unit 172 associates the pair candidate vehicles 220a, 220b, 220c, 220d, and 220e with the vehicle allocation request 22b of the user 2b. In this way, one or more pair candidate vehicles 220 are associated with each of the vehicle allocation requests 22a and 22b.

[0113] Next, the vehicle allocation unit 172 estimates the estimated arrival time of the associated pair candidate vehicle 220 at the desired boarding location for each of the vehicle allocation requests 22a, 22b, and associates it with each of the pair candidate vehicles 220. Next, the vehicle allocation unit 172 sets priorities for the pair candidate vehicles 220 associated with each of the vehicle allocation requests 22a, 22b. When setting the priorities, the vehicle allocation unit 172 recalculates the estimated arrival time at the desired boarding location as shown in FIG. 13(a).

[0114] At this time, the vehicle allocation unit 172 determines whether the pair candidate vehicles 220 include a preferential vehicle based on the vehicle identification information received from the vehicle terminal. Then, for the preferential vehicles, the vehicle allocation unit 172 calculates an adjusted estimated arrival time by uniformly subtracting a preset preferential time from the recalculated estimated arrival time. Here, the preferential time is set to, for example, 3 minutes. As shown in the bold box in FIG. 13(b), it is assumed that the pair candidate vehicles 220a and 220e are preferential vehicles among the extracted pair candidate vehicles 220. In this case, as is clear from a comparison between FIGS. 13(a) and 13(b), the pair candidate vehicles 220a and 220e have their adjusted estimated arrival times calculated by subtracting 3 minutes from the recalculated estimated arrival times.

[0115] 13(b) and 13(c), the vehicle allocation unit 172 rearranges the pair candidate vehicles 220a to 220f associated with the vehicle allocation request 22a into pair candidate vehicles 220b, 220a, 220c, 220e, 220f, and 220d in order of shortest recalculated estimated arrival times or adjusted estimated arrival times. Similarly, the vehicle allocation unit 172 rearranges the pair candidate vehicles 220a to 220e associated with the vehicle allocation request 22b into pair candidate vehicles 220e, 220b, 220a, 220d, and 220c in order of shortest recalculated estimated arrival times or adjusted estimated arrival times.

[0116] 13(c), one or more pair candidate vehicles 220 are prioritized for each of the vehicle allocation requests 22a and 22b, and one or more combinations of the vehicle allocation request 22 and the pair candidate vehicles 220 are generated. In this example, the NRS vehicle 42b is determined as the vehicle to be allocated for the vehicle allocation request 22a, and the taxi vehicle 32e is determined as the vehicle to be allocated for the vehicle allocation request 22b.

[0117] If the taxi vehicle 32e (pair candidate vehicle 220e) is a gasoline-powered vehicle, the estimated arrival time of the taxi vehicle 32e (pair candidate vehicle 220e) in response to the vehicle dispatch request 22b is estimated to be 3 minutes 45 seconds. As a result, the vehicle determined to have the shortest estimated arrival time in response to the vehicle dispatch request 22b is the NRS vehicle 42b (pair candidate vehicle 220b) with an estimated arrival time of 3 minutes 20 seconds, and the vehicle determined to have the second shortest estimated arrival time is the taxi vehicle 32a (pair candidate vehicle 220a) with an estimated arrival time of 3 minutes 35 seconds. Therefore, if the taxi vehicle 32e (pair candidate vehicle 220e) is a gasoline-powered vehicle, the priority of the taxi vehicle 32e (pair candidate vehicle 220e) in response to the vehicle dispatch request 22b will be third. In other words, because the taxi vehicle 32e is an electric vehicle or a hybrid vehicle, its priority will be raised by two places compared to if it were a gasoline-powered vehicle.

[0118] Furthermore, if the taxi vehicle 32a (pair candidate vehicle 220a) is a gasoline-powered vehicle, the estimated arrival time of the taxi vehicle 32a (pair candidate vehicle 220a) for the vehicle dispatch request 22a is estimated to be 6 minutes 00 seconds. As a result, the priority of the taxi vehicle 32a for the vehicle dispatch request 22a becomes fourth. If the taxi vehicle 32a (pair candidate vehicle 220a) is an electric vehicle or a hybrid vehicle, the priority of the taxi vehicle 32a (pair candidate vehicle 220a) becomes second, as shown in FIG. 13(c). In other words, because the taxi vehicle 32a (pair candidate vehicle 220a) is an electric vehicle or a hybrid vehicle, its priority is raised by two places compared to if it were a gasoline-powered vehicle.

[0119] The vehicle dispatch management method using the vehicle dispatch management system 1 described above makes it possible to preferentially dispatch vehicles with low environmental impact to vehicle dispatch management businesses that have a policy of reducing environmental impact. Note that, although electric vehicles and hybrid vehicles have been described above as examples of vehicles with low environmental impact, fuel cell vehicles, hydrogen engine vehicles, and even compact cars may also be set as vehicles with low environmental impact or environmentally friendly vehicles.

[0120] In the above embodiment, both the taxi vehicle 32 and the NRS vehicle 42 can be preferred vehicles. However, for example, the preferred vehicle may be only one of the taxi vehicle 32 and the NRS vehicle 42 to which the preferential time is applied.

[0121] In the above embodiment, a uniform preferential time (3 minutes in the above example) is applied to preferential vehicles. However, the preferential time applied to preferential vehicles may differ for each vehicle. For example, a vehicle dispatch management company or a taxi company may be able to set an arbitrary preferential time for each vehicle identification information.

[0122] Furthermore, the preferential time for a vehicle may differ depending on, for example, fuel economy or electricity efficiency. For example, a five-minute preferential time may be applied to a vehicle with a fuel economy of 30 km / L or more, a three-minute preferential time may be applied to a vehicle with a fuel economy of 20 km / L or more but less than 30 km / L, and a one-minute preferential time may be applied to a vehicle with a fuel economy of 10 km / L or more but less than 20 km / L. In this way, different preferential time may be set depending on the fuel economy of the vehicle, or a uniform preferential time may be set for vehicles with a predetermined fuel economy or higher. Alternatively, a standard based on environmental load may be set, and the preferential time may be set according to the environmental load of the vehicle. For example, a three-minute preferential time may be applied to electric vehicles and hydrogen vehicles, a two-minute preferential time may be applied to hybrid vehicles and biofuel vehicles, and a one-minute preferential time may be applied to clean diesel vehicles.

[0123] Furthermore, in the above embodiment, the case where the vehicle dispatch management company's policy is to reduce the environmental impact has been described, but the vehicle dispatch management company's policy is not limited to this. In other words, vehicles that are preferentially dispatched are not limited to vehicles with a low environmental impact. For example, in the above embodiment, either the taxi vehicle 32 or the NRS vehicle 42 may be designated as a preferred vehicle. In other words, information identifying the taxi vehicle 32 and the NRS vehicle 42 may be included in the vehicle identification information.

[0124] In this case, for example, a preferred vehicle may be identified based on the vehicle identification information, and the preferential time may be applied to the preferred vehicle only when the distance from the boarding location to the disembarking location is equal to or greater than a predetermined distance, or less than the predetermined distance. As an example, when the distance from the boarding location to the disembarking location is equal to or greater than a predetermined distance, a taxi vehicle 32 may be dispatched with priority over an NRS vehicle 42. Alternatively, when the distance from the boarding location to the disembarking location is less than the predetermined distance, an NRS vehicle 42 may be dispatched with priority over a taxi vehicle 32. In this way, the vehicle identification information that is preset for the vehicle is not particularly limited, as long as a vehicle with specific vehicle identification information set is preferentially selected over other vehicles. In any case, by preferentially selecting a vehicle with specific vehicle identification information over other vehicles, vehicle dispatch in accordance with the policy of the vehicle dispatch management business operator can be realized.

[0125] Furthermore, for example, the vehicle identification information may include a plurality of pieces of information, and each of the pieces of information may be linked to information on whether or not to give preferential treatment to vehicle dispatch. For example, the vehicle identification information may include information such as the taxi company, vehicle model, and license plate number. In this case, it may be set in advance that vehicles of a specific taxi company, a specific vehicle model, and a specific license plate number are given priority in dispatch.

[0126] In addition, for example, vehicles that do not operate as taxis, vehicles operating as hire cars, NRS vehicles 42, or vehicles operated by drivers who work only at specific times, i.e., drivers with short working hours, may be set as preferred vehicles.

[0127] Furthermore, for example, whether or not the preferential time is applicable, or the preferential time applied to each preferential vehicle, may differ depending on the date, time, area, etc. In this case, for example, the vehicle dispatch unit 172 may determine whether or not the preferential time is applicable and the preferential time applied to each preferential vehicle based on the date, time, or area.

[0128] In the above embodiment, the estimated arrival time is calculated for each pair candidate vehicle 220, and the priority is set so that the shorter the estimated arrival time, the higher the priority. However, the method of setting the priority is not limited to this. For example, points may be assigned to each extracted vehicle according to a preset algorithm, and the higher the assigned points, the higher the priority. In this case, the shorter the estimated arrival time, the higher the assigned points, making it possible to realize vehicle allocation similar to that of the above embodiment.

[0129] In the above embodiment, a case has been described in which preferred vehicles are given priority when prioritizing the extracted pair candidate vehicles 220. Alternatively, preferred vehicles may be preferentially extracted when extracting pair candidate vehicles 220. For example, the extraction conditions for preferred vehicles include that the distance between the boarding location and the vehicle's current location is within a predetermined distance (e.g., 15 km) or that the estimated arrival time at the boarding location is within a predetermined time (e.g., 15 minutes). On the other hand, the extraction conditions for vehicles other than preferred vehicles include that the distance between the boarding location and the vehicle's current location is within a predetermined distance (e.g., 10 km) or that the estimated arrival time at the boarding location is within a predetermined time (e.g., 10 minutes). Even in this case, preferred vehicles are more likely to be selected as dispatch target vehicles than other vehicles.

[0130] In the above embodiment, a vehicle allocation target notification is sent to a vehicle terminal installed in a vehicle that has become a target vehicle for allocation in response to the vehicle allocation request 22, as information indicating that the vehicle has become a target vehicle for allocation. At this time, the driver who receives the target vehicle for allocation notification can reject the vehicle allocation request 22. However, a notification that the vehicle that has become a target vehicle for allocation cannot reject the vehicle allocation request 22 may be sent to the vehicle. In this case, for example, a vehicle allocation completion notification may be sent without sending a target vehicle for allocation notification.

[0131] Furthermore, in the above embodiment, the process of extracting one vehicle eligible for allocation is merely an example. For example, only a part of the processes from S3 to S6 in the above embodiment may be executed. Also, for example, only multiple preferred vehicles may be extracted for the vehicle allocation request 22, and one vehicle eligible for allocation may be extracted from among these. In this case, if no preferred vehicle that satisfies all other conditions related to vehicle allocation is extracted, one vehicle eligible for allocation may be extracted from vehicles other than the preferred vehicles.

[0132] In any case, the vehicle dispatching device includes a server (in the embodiment, as an example, a vehicle dispatching management server 60) that can communicate with a plurality of vehicle terminals (in the embodiment, as an example, a taxi terminal 30 and an NRS terminal 40) provided for each vehicle, The server A process of acquiring a dispatch request (S2 in the embodiment as an example); A process (S3, S4, S5, and S6 in the embodiment) of extracting one or more vehicles from a plurality of vehicles (taxi vehicles 32 and NRS vehicles 42 as examples in the embodiment) based on the acquired vehicle dispatch request and in accordance with predetermined extraction conditions; A process (S7 in the embodiment as an example) of notifying predetermined information (a notification of a vehicle to be dispatched, as an example in the embodiment) to a vehicle terminal provided in the extracted vehicle; and Vehicle identification information is preset in the vehicle. The specified extraction conditions include: It is sufficient if the vehicle having the specific vehicle identification information (in the embodiment, as an example, an electric vehicle or a hybrid vehicle) is selected as a vehicle to be preferentially extracted over other vehicles (in the embodiment, as an example, subtracting a preferential time from the estimated arrival time) is included.

[0133] The vehicle dispatch system also includes a server (in the embodiment, as an example, a vehicle dispatch management server 60) that can communicate with a plurality of vehicle terminals (in the embodiment, as an example, a taxi terminal 30 and an NRS terminal 40) provided for each vehicle, The server A process of acquiring a dispatch request (S2 in the embodiment as an example); A process (S4, S5, S6 in the embodiment) of extracting one or more vehicles from a plurality of vehicles (taxi vehicles 32 and NRS vehicles 42 as examples in the embodiment) based on the acquired vehicle dispatch request and in accordance with predetermined extraction conditions; A process (S7 in the embodiment as an example) of notifying predetermined information (a notification of a vehicle to be dispatched, as an example in the embodiment) to a vehicle terminal provided in the extracted vehicle; and Vehicle identification information is preset in the vehicle. The specified extraction conditions include: It is sufficient if the vehicle having the specific vehicle identification information (in the embodiment, as an example, an electric vehicle or a hybrid vehicle) is selected as a vehicle to be preferentially extracted over other vehicles (in the embodiment, as an example, subtracting a preferential time from the estimated arrival time) is included.

[0134] The vehicle dispatch method is a vehicle dispatch method performed by a server (in the embodiment, as an example, a vehicle dispatch management server 60) capable of communicating with a plurality of vehicle terminals (in the embodiment, as an example, a taxi terminal 30 and an NRS terminal 40) provided for each vehicle, The server A process of acquiring a dispatch request (S2 in the embodiment as an example); A process (S4, S5, S6 in the embodiment) of extracting one or more vehicles from a plurality of vehicles (taxi vehicles 32 and NRS vehicles 42 as examples in the embodiment) based on the acquired vehicle dispatch request and in accordance with predetermined extraction conditions; A process (S7 in the embodiment as an example) of notifying predetermined information (a notification of a vehicle to be dispatched, as an example in the embodiment) to a vehicle terminal provided in the extracted vehicle; and Vehicle identification information is preset in the vehicle. The specified extraction conditions include: It is sufficient if the vehicle having the specific vehicle identification information (in the embodiment, as an example, an electric vehicle or a hybrid vehicle) is selected as a vehicle to be preferentially extracted over other vehicles (in the embodiment, as an example, subtracting a preferential time from the estimated arrival time) is included.

[0135] The program is also installed in a server (in the embodiment, as an example, the vehicle dispatch management server 60) that can communicate with a plurality of vehicle terminals (in the embodiment, as an example, the taxi terminal 30 and the NRS terminal 40) provided for each vehicle. A process of acquiring a dispatch request (S2 in the embodiment as an example); A process (S4, S5, S6 in the embodiment) of extracting one or more vehicles from a plurality of vehicles (taxi vehicles 32 and NRS vehicles 42 as examples in the embodiment) based on the acquired vehicle dispatch request and in accordance with predetermined extraction conditions; A process (S7 in the embodiment as an example) of notifying predetermined information (a notification of a vehicle to be dispatched, as an example in the embodiment) to a vehicle terminal provided in the extracted vehicle; and Vehicle identification information is preset in the vehicle. The specified extraction conditions include: It is sufficient if the vehicle having the specific vehicle identification information (in the embodiment, as an example, an electric vehicle or a hybrid vehicle) is selected as a vehicle to be preferentially extracted over other vehicles (in the embodiment, as an example, subtracting a preferential time from the estimated arrival time) is included.

[0136] While the preferred embodiments of the present invention have been described above with reference to the accompanying drawings, it goes without saying that the present invention is not limited to such embodiments. It is clear that those skilled in the art can conceive of various modifications and alterations within the scope of the claims, and it is understood that such modifications and alterations also fall within the technical scope of the present invention.

[0137] Also provided are programs that cause a computer to function as the vehicle dispatch management server 60, and computer-readable storage media, such as flexible disks, magneto-optical disks, ROMs, CDs, DVDs, and BDs, on which the programs are recorded. Here, the program refers to data processing means written in any language or description method.

[0138] It should be noted that the processes shown in this specification do not necessarily have to be performed in chronological order according to the order shown in the flowcharts, and may include parallel or subroutine processes. [Explanation of symbols]

[0139] 1. Vehicle dispatch management system 30 Taxi terminal 32 Taxi vehicles 40 NRS terminals 42 NRS vehicles 60 Vehicle dispatch management server

Claims

1. a server capable of communicating with a plurality of vehicle terminals provided in each vehicle; The server A process of obtaining a dispatch request; A process of extracting one or more vehicles from the plurality of vehicles in accordance with predetermined extraction conditions based on the acquired vehicle dispatch request; a process of notifying the vehicle terminal provided in the extracted vehicle of predetermined information; and Vehicle identification information is preset in the vehicle, The predetermined extraction conditions include: a condition that the vehicle to which specific vehicle identification information is set is preferentially extracted over other vehicles; Dispatch device.

2. The specific vehicle identification information is set for an electric vehicle. The vehicle dispatching device according to claim 1 .

3. The specific vehicle identification information is set to a vehicle that does not operate as a taxi, a vehicle that operates as a hire car, a Japanese-style ride-sharing vehicle, or a vehicle that is operated by a driver who works only at specific times. The vehicle dispatching device according to claim 1 or 2.

4. a server capable of communicating with a plurality of vehicle terminals provided in each vehicle; The server A process of obtaining a dispatch request; A process of extracting one or more vehicles from the plurality of vehicles in accordance with predetermined extraction conditions based on the acquired vehicle dispatch request; a process of notifying the vehicle terminal provided in the extracted vehicle of predetermined information; and Vehicle identification information is preset in the vehicle, The predetermined extraction conditions include: a condition that the vehicle to which specific vehicle identification information is set is preferentially extracted over other vehicles; Vehicle dispatch system.

5. A vehicle dispatch method performed by a server capable of communicating with a plurality of vehicle terminals provided for each vehicle, comprising: The server A process of obtaining a dispatch request; A process of extracting one or more vehicles from the plurality of vehicles in accordance with predetermined extraction conditions based on the acquired vehicle dispatch request; a process of notifying the vehicle terminal provided in the extracted vehicle of predetermined information; and Vehicle identification information is preset in the vehicle, The predetermined extraction conditions include: a condition that the vehicle to which specific vehicle identification information is set is preferentially extracted over other vehicles; Delivery method.

6. A server capable of communicating with a plurality of vehicle terminals provided for each vehicle, A process of obtaining a dispatch request; A process of extracting one or more of the vehicles from the plurality of vehicles in accordance with predetermined extraction conditions based on the acquired vehicle dispatch request; a process of notifying the vehicle terminal provided in the extracted vehicle of predetermined information; and Vehicle identification information is preset in the vehicle, The predetermined extraction conditions include: a condition that the vehicle to which specific vehicle identification information is set is extracted with priority over other vehicles; program.

Images