Dispatch management system, dispatch management device, method for dispatch management, and program

Abstract

To perform vehicle dispatch efficiently.SOLUTION: A dispatch management device communicable with a user terminal 20 via a network includes at least one processor. The at least one processor executes: a first dispatch mode in which, for a dispatch request received from the user terminal 20, a first vehicle is assigned while a second vehicle having dispatch requirements different from those of the first vehicle is not assigned; or a second dispatch mode in which one of the first vehicle and the second vehicle is assigned for the dispatch request. The at least one processor cause the user terminal 20 to output information regarding a transition from the first dispatch mode to the second dispatch mode on the basis of operating conditions of the first vehicle or the second vehicle.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present invention relates to a vehicle allocation management system, a vehicle allocation management device, a vehicle allocation management method, and a program for managing vehicle allocation. [Background technology]

[0002] There are known technologies for dispatching a taxi in response to a user's request for dispatching a taxi. For example, Patent Document 1 discloses a technology for estimating the arrival times of the user and the taxi at the user's desired boarding location, matching the estimated results, and dispatching 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] Recently, the shortage of taxi drivers has become a serious problem in some regions. As a result, there are areas where the supply of taxis is insufficient to meet the demand for taxi dispatch. As a result, the introduction of ride-sharing (Japanese-style ride-sharing), in which ordinary drivers use their own cars to transport users for a fee, is progressing.

[0005] A user can use either a taxi or a ride-sharing vehicle as a means of transportation. In addition, while a user can select either a taxi or a ride-sharing vehicle, the user can also limit the vehicle dispatch options to taxis. However, limiting the vehicle dispatch options to taxis may result in the user missing out on opportunities to ride in a ride-sharing vehicle, which could result in a long wait time before boarding.

[0006] In view of the above problems, the present invention aims to provide a vehicle dispatch management system, a vehicle dispatch management device, a vehicle dispatch management method, and a program that enable efficient vehicle dispatch. [Means for solving the problem]

[0007] In order to solve the above problem, in the vehicle dispatch management system of the present invention, which includes a user terminal and a vehicle dispatch management device capable of communicating with the user terminal via a network, the user terminal includes one or more first processors, and the vehicle dispatch management device includes one or more second processors, wherein the first processor sends a vehicle dispatch request to the vehicle dispatch management device in accordance with user input, and the second processor executes a first vehicle dispatch mode in which a first vehicle is assigned to the vehicle dispatch request but a second vehicle having different dispatch availability requirements from the first vehicle is not assigned, or a second vehicle dispatch mode in which either the first vehicle or the second vehicle is assigned to the vehicle dispatch request, and outputs information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal based on the operating status of the first vehicle or the second vehicle.

[0008] In order to solve the above problem, the vehicle dispatch management device of the present invention, which is capable of communicating with a user terminal via a network, includes one or more processors, and the processors execute a first vehicle dispatch mode in which a first vehicle is assigned to a dispatch request received from the user terminal, but a second vehicle having different dispatch availability requirements from the first vehicle is not assigned, or a second vehicle dispatch mode in which either the first vehicle or the second vehicle is assigned to the dispatch request, and output information regarding the transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal based on the operating status of the first vehicle or the second vehicle.

[0009] The information regarding the transition from the first vehicle dispatch mode to the second vehicle dispatch mode may be information regarding additional input of specified setting items required in the second vehicle dispatch mode, and when the specified setting items are additionally input in the user terminal, the processor may transition from the first vehicle dispatch mode to the second vehicle dispatch mode and assign either the first vehicle or the second vehicle to the vehicle dispatch request.

[0010] The predetermined setting items may include a destination where the user wishes to get off.

[0011] The predetermined setting items may include the destination where the user wishes to get off and information regarding automatic payment.

[0012] The operating status may include an on-board rate of the second vehicle, and when the on-board rate of the second vehicle becomes equal to or lower than a predetermined rate, the processor may output information regarding a transition from the first dispatch mode to the second dispatch mode to the user terminal.

[0013] The operating status may include an actual vehicle time rate of the second vehicle, and when the actual vehicle time rate of the second vehicle becomes equal to or less than a predetermined rate, the processor may output information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal.

[0014] The operating status may include the number of times the second vehicle is actually driven per unit time, and the processor may output information regarding the transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal when the number of times the second vehicle is actually driven per unit time becomes a predetermined number or less.

[0015] The operating status may include an actual vehicle distance per unit time of the second vehicle, and the processor may output information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal when the actual vehicle distance per unit time of the second vehicle becomes less than a predetermined distance.

[0016] The operating status may include a matching rate at which the second vehicle is assigned to the dispatch request, and the processor may output information regarding a transition from the first dispatch mode to the second dispatch mode to the user terminal when the matching rate at which the second vehicle is assigned falls below a predetermined rate.

[0017] The operating status may include a ratio of the number of the second vehicles currently in operation to the number of the first vehicles currently in operation, and the processor may output information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal when the ratio of the number of the second vehicles currently in operation falls below a predetermined rate.

[0018] The operating status may include the operating income per unit time of the second vehicle, and the processor may output information regarding transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal when the operating income per unit time of the second vehicle falls below a predetermined amount.

[0019] The operating status may include an operating income ratio of the second vehicle currently in operation to the first vehicle currently in operation, and the processor may output information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal when the operating income ratio of the second vehicle currently in operation falls below a predetermined rate.

[0020] In order to solve the above problem, the vehicle dispatch management method of the present invention executes a first vehicle dispatch mode in which a computer assigns a first vehicle to a dispatch request received from a user terminal but does not assign a second vehicle that has different dispatch availability requirements from the first vehicle, or a second vehicle dispatch mode in which a computer assigns either the first vehicle or the second vehicle to the dispatch request, and outputs information regarding the transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal based on the operating status of the first vehicle or the second vehicle.

[0021] In order to solve the above problem, the program of the present invention causes a computer to execute a first dispatch mode in which a first vehicle is assigned to a dispatch request received from a user terminal, but a second vehicle having different dispatch availability requirements from the first vehicle is not assigned, or a second dispatch mode in which either the first vehicle or the second vehicle is assigned to the dispatch request, and output information regarding the transition from the first dispatch mode to the second dispatch mode to the user terminal based on the operating status of the first vehicle or the second vehicle. [Effects of the Invention]

[0022] According to the present invention, efficient vehicle allocation is possible. [Brief explanation of the drawings]

[0023] [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 by the vehicle allocation management system. [Figure 8] FIG. 8 is an explanatory diagram for explaining the processing of the dispatch unit. [Figure 9] FIG. 9 is an explanatory diagram showing the results of matching by the dispatch unit. [Figure 10] FIG. 10 is an explanatory diagram for explaining the processing of the dispatch unit. [Figure 11]Fig. 11A is a first explanatory diagram for explaining the operation of the user terminal control unit, and Fig. 11B is a second explanatory diagram for explaining the operation of the user terminal control unit. [Figure 12] Fig. 12A is a first explanatory diagram for explaining the operation of the user terminal control unit, and Fig. 12B is a second explanatory diagram for explaining the operation of the user terminal control unit. [Figure 13] Fig. 13A is a first explanatory diagram for explaining the operation of the user terminal control unit, and Fig. 13B is a second explanatory diagram for explaining the operation of the user terminal control unit. DETAILED DESCRIPTION OF THE INVENTION

[0024] 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.

[0025] (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.

[0026] 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.

[0027] FIG. 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 communicatively connected to an external device, such as a vehicle dispatch management server 60, via a base station 5 and a network 6. The processing device 122 includes a semiconductor integrated circuit including a processor such as a central processing unit (CPU), a read-only memory (ROM) storing programs, and a random access memory (RAM) used as a work area. A user application for the vehicle dispatch management system 1 is installed on the user terminal 20. The processing device 122 runs the program to control the user application and function as a vehicle dispatch request unit 180 that supports the user 2 in inputting a vehicle dispatch request. The display device 124 includes a liquid crystal display, an organic electroluminescence (EL) display, or the like, and displays various information, such as an image of the user application used to make a vehicle dispatch request. The input device 126 includes a touch panel, switches, buttons, keys, a microphone for voice input, etc. superimposed on the display device 124, and accepts input from the user 2, such as information for requesting a vehicle dispatch. The storage device 128 is configured with storage means such as an HDD (Hard Disk Drive), SD memory, SSD (Solid State Drive), etc.

[0028] The taxi terminal 30 is an electronic device loaned to a taxi driver 3 of a taxi vehicle (first 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 (first vehicle terminal).

[0029] FIG. 3 is a block diagram illustrating the configuration of the taxi terminal 30. 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 communicatively connected to external devices, such as the operator server 50 and the dispatch management server 60, via a base station 5 and a network 6. The processing device 132 includes 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 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. The display device 134 includes a liquid crystal display and an organic electroluminescence (EL) display, and displays various information, such as a notification that the taxi 32 has been the subject of a dispatch request (dispatch target notification) and information related to the dispatch request (boarding location, user information about the user 2, and disembarking location). Hereinafter, the target of a dispatch request may be referred to as the "dispatch target," and the vehicle that has been dispatched may be referred to as the "dispatch target vehicle." 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 the dispatch request. 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 position on a map through location identification means such as a GPS (Global Positioning System).

[0030] 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.

[0031] The NRS terminal 40 is an electronic device owned by the NRS driver 4, and can be placed in the NRS vehicle (second 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 own private car, and drives the NRS vehicle 42. The NRS terminal 40 is not limited to being brought into the vehicle when 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 makes it possible to use the NRS vehicle 42 as a commercial vehicle in place of the taxi vehicle 32. The NRS terminal 40 is an example of a vehicle terminal (second vehicle terminal).

[0032] FIG. 4 is a block diagram illustrating the configuration of the NRS terminal 40. 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 communicatively connected to external devices, such as the operator server 50 and the vehicle dispatch management server 60, via the base station 5 and the network 6. The processing device 142 includes a semiconductor integrated circuit including a processor (CPU), a ROM storing programs, 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 dispatch response unit 184 that supports the NRS driver 4 in inputting responses to vehicle dispatch requests. The display device 144 includes a liquid crystal display and an organic electroluminescence (EL) display, and displays various information, such as a notification that the NRS vehicle 42 has been selected for dispatch (dispatch target notification) and information related to the dispatch request (boarding location, disembarking location, and user information related to the user 2). 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 acceptance of a vehicle dispatch request. The storage device 148 is composed of storage means such as an HDD, SD memory, or SSD. The NRS terminal 40 can obtain its own position on a map through location identification means such as GPS.

[0033] 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 a 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. The NRS driver 4 differs from the taxi driver 3 in that he or she does not hold a Class 2 driver's license for a standard vehicle or may have poor driver qualifications, driving skills, and knowledge. The NRS vehicle 42 is, for example, a vehicle driven by the NRS driver 4 and can transport users 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. The vehicle dispatch management system 1 has multiple combinations of NRS drivers 4, NRS vehicles 42, and NRS terminals 40. Note that the NRS driver 4 cannot engage in so-called patrol business, which is to search for users 2 who want to ride while driving the taxi vehicle 32, as the taxi driver 3 does. However, in the case of paid passenger transportation by private car based on Article 78, Paragraph 3 of the Road Transportation Act, NRS Driver 4 may charge User 2 a fee (fare) equivalent to that charged for general passenger automobile transportation business as compensation for transporting User 2.

[0034] 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.

[0035] The operating area of ​​the NRS vehicle 42 is included in the operating area of ​​the taxi vehicle 32 and is often smaller than that of the taxi vehicle 32. Furthermore, while the operating area of ​​the taxi vehicle 32 is limited in geographical area but not in time, the operating area of ​​the NRS vehicle 42 is not only limited in geographical area but also in time, such as only during periods (including seasons) when the supply of taxi vehicles 32 is insufficient to meet the demand. Thus, a taxi shortage in an area, period, or time zone where there is a shortage of taxi vehicles 32 is considered an "unavoidable case for the public welfare" under Article 78, Paragraph 3 of the Road Transportation Act, and a ride-sharing business is permitted. The operating area of ​​the NRS vehicle 42, like the operating area of ​​the taxi vehicle 32, is managed by a taxi operator, and is subject to the same regulations as the operating area of ​​the taxi vehicle 32. While this embodiment describes an example in which the operating area of ​​the NRS vehicle 42 is limited in both geographical area and time zone, the present invention is not limited to such an example, and there are also cases in which the operating area is limited only in geographical area and not in time zone.

[0036] Hereinafter, for convenience of explanation, 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." Furthermore, 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." Furthermore, when there is no need to distinguish between taxi terminal 30 and NRS terminal 40, devices possessed by drivers, including taxi terminal 30 and NRS terminal 40, may be collectively referred to simply as "vehicle terminals," display devices of vehicle terminals, including display device 134 and display device 144, may be collectively referred to simply as "vehicle display devices," input devices of vehicle terminals, including input device 136 and input device 146, may be collectively referred to simply as "vehicle input devices," and vehicle dispatch response units of vehicle terminals, including vehicle dispatch response unit 182 and vehicle dispatch response unit 184, may be collectively referred to simply as "vehicle dispatch response units."

[0037] FIG. 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 operating 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. The communication device 150 is communicatively connected to external devices, such as taxi terminals 30, NRS terminals 40, and a vehicle dispatch management server 60, via a network 6. The processing device 152 includes a semiconductor integrated circuit including a processor (CPU), a ROM storing programs, and a RAM used as a work area. By running a program, the processing device 152 functions as a vehicle management unit 186 that manages vehicles belonging to the taxi business. The display device 154 includes a liquid crystal display (LCD) or an organic electroluminescence (EL) display, and displays various information, such as driver or vehicle information, obtained directly from the vehicles or via the vehicle dispatch management server 60. 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. The storage device 158 is composed of storage means such as an HDD, SD memory, or SSD.

[0038] FIG. 6 is a block diagram illustrating the configuration of the vehicle dispatch management server 60. The vehicle dispatch management server (vehicle dispatch management device) 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. The communication device 160 is communicatively connected to external devices, such as the user terminal 20, the taxi terminal 30, the NRS terminal 40, and the company server 50, via the network 6. 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, and the like. 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. The user terminal control unit 170 controls the user application 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 application installed in the vehicle terminal. The storage device 164 is composed of storage means such as an HDD, SD memory, or SSD, and stores information about the user 2 and the vehicle.

[0039] In the vehicle dispatch management system 1, when allocating a vehicle in response to a vehicle dispatch request (i.e., when dispatching a vehicle), for example, by matching a plurality of vehicle dispatch requests with a plurality of vehicles, one vehicle is allocated to, for example, one vehicle dispatch request from one user 2. Here, matching refers to a process of exclusively associating any vehicle dispatch request with any vehicle in a state where there are multiple vehicle dispatch requests and multiple vehicles. In the following, an example of allocating one vehicle to one vehicle dispatch request will be described, but if multiple users 2 are allowed to ride in one vehicle, so-called carpooling, one vehicle may also be allocated to multiple vehicle dispatch requests from multiple users 2.

[0040] (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.

[0041] (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.

[0042] 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.

[0043] 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. The disembarking location indicates the location on the map where User 2 wishes to disembark. When User 2 sets the boarding location and disembarking location among the setting items, the fare calculated based on the set time, boarding location, and disembarking location is displayed on display device 124. In this way, User 2 can know in advance the fare that will be paid by boarding the vehicle.

[0044] When user 2 limits the vehicle dispatch target to taxi vehicles 32 only, the drop-off location is not required input information but is optional information that can be input. On the other hand, when user 2 includes NRS vehicles 42 in the vehicle dispatch target, the drop-off location is required input information. This is because ride-sharing services based on Article 78, Paragraph 3 of the Road Transportation Act require that the fare be determined in advance as a vehicle dispatch requirement (a requirement for dispatching an NRS vehicle 42). Therefore, when an NRS vehicle 42 is included in the vehicle dispatch target, user 2 must input the drop-off location in addition to the pick-up location in order to calculate the fare in advance. Payment information is information related to the payment of fees associated with vehicle use (e.g., fares and other additional fees). Note that when an NRS vehicle 42 is included in the vehicle dispatch target, in addition to inputting the drop-off location, information related to cashless automatic payment by credit card or the like (e.g., credit card number) is required as payment information. 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 vehicle dispatch requirement. Here, automatic payment refers to a process in which, after the vehicle arrives at the drop-off location, the driver can charge the user 2 the fee for using the vehicle based on information regarding the user 2's automatic payment, without the user 2 paying cash or inputting information regarding electronic money into the cashless terminal. In this way, the NRS vehicle 42 differs from the taxi vehicle 32 in that the dispatch requirement requires input of information regarding the drop-off location and automatic payment. However, this is not the only example, and the taxi vehicle 32 may also require a dispatch requirement (a requirement that allows the taxi vehicle 32 to be dispatched). For example, in an operation mode such as a hire car that does not operate as a so-called street car, the taxi vehicle 32 also requires input of information regarding the drop-off location and automatic payment as a dispatch requirement, similar to the NRS vehicle 42.

[0045] The dispatch category indicates the category of the vehicle to be dispatched. For example, as described above, taxi drivers 3 often hold Class 2 driver's licenses for standard vehicles and have high driver qualifications, driving skills, knowledge, etc. On the other hand, NRS drivers 4 vary in their driver qualifications, driving skills, knowledge, etc. Furthermore, even drivers who hold Class 2 driver's licenses for standard vehicles are not regularly employed as taxi drivers 3, and there are specific drivers who, for example, rent vehicles from taxi companies to transport users 2. These specific drivers often vary in their driver qualifications, driving skills, knowledge, etc. Note that when dispatching a specific vehicle driven by a specific driver, user 2 must also enter information about the drop-off location and automatic payment, just as with the NRS vehicle 42. Herein, vehicles with different dispatch requirements than taxi vehicle 32, including NRS vehicles 42 and specific vehicles, may be simply referred to as "required vehicles." Because driver qualifications, etc., vary depending on the vehicle, some users 2 may request a taxi vehicle 32 driven by taxi driver 3. In this case, user 2 selects "only taxi vehicles 32" 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 prefer taxi vehicles 32 and vehicles with requirements so that he or she can board a vehicle quickly. In this case, user 2 should select "taxi vehicles 32 and vehicles with requirements" as the dispatch category.

[0046] Here, a dispatch mode in which a taxi vehicle 32 is assigned to a dispatch request but a vehicle with a condition is not assigned is referred to as a first dispatch mode, and a dispatch mode in which either a taxi vehicle 32 or a vehicle with a condition is assigned 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 information about the boarding location, the drop-off location, and automatic payment through the user terminal 20. As described above, user 2 can select "taxi vehicle 32 only" or "taxi vehicle 32 and vehicle with a condition" as the dispatch category. Therefore, even if information about the drop-off location and automatic payment has been input, if user 2 selects "taxi vehicle 32 only" as the dispatch category, the system transitions from the second dispatch mode to the first dispatch mode. User 2 can set the purpose of use of the vehicle (e.g., use for business purposes) or set it so that the drop-off location is not input in advance. In this case, even if the user does not specify and input a dispatch category, only taxi vehicles 32 are automatically dispatched (first dispatch mode). If user 2 does not input the drop-off location in advance, the drop-off location may be communicated directly to the driver, or may be input after getting in via user terminal 20. Furthermore, when user 2 uses taxi vehicle 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.

[0047] 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.

[0048] The taxi company indicates the company to which the taxi driver 3 or NRS driver 4 belongs as a taxi business. User 2 can specify the desired taxi company by inputting information into the taxi company setting items. Vehicle attributes indicate the type and equipment of the vehicle. Examples of vehicle attributes include whether or not it is a high-class vehicle (a so-called hire car), whether or not it is wheelchair accessible, and whether or not it has sliding doors. User 2 can specify the attributes of the vehicle he or she wishes to dispatch by inputting information into the vehicle attribute setting items. Toll road information indicates whether or not toll roads, such as expressways, will be used. If the toll road information indicates the use of toll roads, toll roads will be actively included in the route from the pick-up point to the drop-off point.

[0049] (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.

[0050] (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.

[0051] 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.

[0052] (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 the conditions of 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. If the vehicle dispatch category in the vehicle dispatch request is set to "taxi vehicles 32 and vehicles with special requirements," the vehicle dispatch unit 172 extracts taxi vehicles 32 and vehicles with special requirements for the vehicle dispatch request. Another extraction condition is, for example, that the estimated time of arrival at the boarding location is short. Specifically, the extraction condition is, for example, 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 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 arrival time is the time obtained by dividing the Euclidean distance by a predetermined speed (for example, the average speed when the vehicle is operating). Furthermore, the vehicle dispatch unit 172 may further limit the number of vehicles to be extracted to a predetermined number (for example, 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 arrival time at the boarding location.

[0053] 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.

[0054] 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.

[0055] 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. 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.

[0056] (Pair generation process S5) For each vehicle dispatch request 22 extracted in the vehicle dispatch request extraction process S3, the vehicle dispatch 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, and associates the extracted vehicle with the vehicle dispatch request 22. Here, the pairing condition is that the vehicle's allowable items conform to all of the setting items of the vehicle dispatch request 22. For example, if the vehicle attribute included in the setting items of the vehicle dispatch request 22 is "sliding door compatible," the vehicle dispatch unit 172 determines that the vehicle is "suitable" if the vehicle's allowable items include sliding doors. Furthermore, for example, if the vehicle dispatch category included in the setting items of the vehicle dispatch request 22 is "taxi vehicles 32 only," the vehicle dispatch unit 172 determines that the vehicle is "suitable" if it is a taxi vehicle 32. The vehicle allocation unit 172 determines that a vehicle does not satisfy the pairing condition if any of the allowable items of the vehicle do not match the setting items of the vehicle allocation request 22. On the other hand, if the allowable items of the vehicle match all of the setting items of the vehicle allocation request 22, the vehicle allocation unit 172 associates the vehicle with the vehicle allocation request 22 as a vehicle that satisfies the pairing condition of the vehicle allocation request 22.

[0057] (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.

[0058] 9 is an explanatory diagram showing the results of matching by the vehicle dispatch unit 172. Using a predetermined matching algorithm, the vehicle dispatch unit 172 associates vehicles 42b, 32c, 32e, 32a, 42f, 32g, and 42j with the vehicle dispatch request 22a, and exclusively determines the NRS vehicle 42b with the highest priority. Similarly, the vehicle dispatch unit 172 associates vehicles 32h, 42f, 32e, 32g, 32a, 42j, and 32c with the vehicle dispatch request 22b, and exclusively determines the taxi vehicle 32h with the highest priority. Similarly, the vehicle dispatch unit 172 associates vehicles 42i, 32e, 42f, 32g, 32c, 42j, and 32a with the vehicle dispatch request 22c, and exclusively determines the NRS vehicle 42i with the highest priority. Similarly, vehicles 32d, 32e, 32c, and 32g are associated with the vehicle allocation request 22d, and the taxi vehicle 32d with the highest priority is exclusively determined. Here, "exclusive determination" means that the highest priority vehicles 42b, 32h, 42i, and 32d associated with the vehicle allocation requests 22a to 22d are determined so that they do not overlap with each other. The vehicle allocation unit 172 then determines the highest priority vehicle 42b, 32h, 42i, or 32d associated with each of the vehicle allocation requests 22a to 22d as the vehicle to be allocated for the vehicle allocation request 22a to 22d. In this way, the vehicle allocation unit 172 matches multiple vehicle allocation requests 22 with multiple vehicles at once and determines the vehicle to be allocated for each vehicle allocation request 22. In this way, compared to matching vehicle dispatch requests 22 sequentially and individually, matching can be optimized by comprehensively determining the relative positions of multiple users 2 and multiple vehicles, enabling efficient vehicle dispatch.

[0059] (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.

[0060] (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.

[0061] 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).

[0062] (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.

[0063] (User vehicle dispatch completion notification process S10) When the dispatch of the vehicle to be dispatched in response to the vehicle dispatch request 22 is confirmed, the user terminal control unit 170 transmits a vehicle dispatch completion notification indicating that the vehicle dispatch has been confirmed to the user terminal 20. 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, the 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. The user 2 will execute the vehicle dispatch request 22 again based on this information.

[0064] In the vehicle dispatch management method using the vehicle dispatch management system 1 described above, information on a plurality of vehicle dispatch requests 22 and a plurality of vehicles is accumulated and matched at once. In this case, by shortening the accumulation time, the frequency of execution of the vehicle dispatch matching process (S6) can be increased, thereby enabling efficient vehicle dispatch while maintaining convenience for the user 2.

[0065] (Mode transition for vehicle dispatch) As described above, NRS drivers 4 vary in their driver qualifications, driving skills, knowledge, etc., whereas taxi drivers 3 often have high levels of these. Therefore, some users 2 may limit the vehicles they dispatch to only taxi vehicles 32. However, if the vehicles they dispatch are limited to taxi vehicles 32, users 2 may miss the opportunity to ride in a vehicle with a specified condition, even in a situation where a vehicle with a specified condition could be dispatched earlier, and this may result in a longer waiting time until they can ride in the vehicle.

[0066] 10 is an explanatory diagram for explaining the processing of the vehicle dispatch unit 172. FIG. 10 shows a user 2 who has made a vehicle dispatch request 22 within business area A, and six vehicles 32a, 42b, 32c, 32d, 32e, and 42f that exist within business area A. In this embodiment, four taxi vehicles 32a, 32c, 32d, and 32e and two NRS vehicles 42b and 42f are shown. It is assumed that business area A is a business area where the business area of ​​taxi vehicle 32 and the business area of ​​NRS vehicle 42 are the same.

[0067] The dispatch unit 172 sets an extraction condition 24, shown by a dashed arc in Fig. 10, for the dispatch request 22, that the distance between the boarding location (the current location of user 2) and the current location of the vehicle is equal to or less than a predetermined distance. In the example of Fig. 10, taxi vehicles 32a, 32c, 32d, and 32e are far from user 2 and do not satisfy the extraction condition 24, but NRS vehicles 42b and 42f are close to user 2 and satisfy the extraction condition 24.

[0068] At this time, it is assumed that user 2 has limited the vehicles to be dispatched to only taxi vehicle 32. In this case, none of taxi vehicles 32a, 32c, 32d, and 32e satisfy extraction condition 24, and therefore the dispatch unit 172 cannot extract taxi vehicle 32. At this time, NRS vehicles 42b and 42f are close to user 2 and can be dispatched quickly, but user 2 has not targeted vehicles with requirements for dispatch, and therefore the dispatch unit 172 cannot extract NRS vehicle 42 either.

[0069] Therefore, the vehicle dispatch management server 60 realizes efficient vehicle dispatch by encouraging the dispatch of the vehicle with requirements according to the dispatch status of either or both of the taxi vehicle 32 and the vehicle with requirements. Specifically, the user terminal control unit 170 outputs to the user terminal 20 information regarding a transition from a first vehicle dispatch mode in which a taxi vehicle 32 is assigned without assigning a vehicle with requirements to the vehicle dispatch request 22, to a second vehicle dispatch mode in which either a taxi vehicle 32 or a vehicle with requirements is assigned to the vehicle dispatch request 22, based on the operational status regarding the operation of the taxi vehicle 32 or the vehicle with requirements. In this embodiment, the operation of outputting information regarding the transition from the first vehicle dispatch mode to the user terminal 20 is simply referred to as "transition output."

[0070] The user terminal control unit 170 may output the transition information to all user terminals 20 for which dispatching has not been completed. However, it is not necessary to output the transition information to user terminals 20 for which dispatching in the second dispatch mode is already possible (for which information on the drop-off location and automatic payment has been input). Therefore, the user terminal control unit 170 may output the transition information only to user terminals 20 for which information on the drop-off location or automatic payment has not been input, based on the operating status of the taxi vehicle 32 or the vehicle with requirements.

[0071] Here, the operating status can be exemplified by the actual vehicle rate of vehicles with requirements. The actual vehicle rate of vehicles with requirements indicates the proportion of the distance traveled by a vehicle with requirements in an actual vehicle state to the total distance traveled by the vehicle with requirements. Here, an actual vehicle refers to a state in which user 2 is riding in the vehicle. For example, when the actual vehicle rate of vehicles with requirements in the most recent hour falls below a predetermined rate, the user terminal control unit 170 determines that user 2 is unaware that including vehicles with requirements in the vehicle dispatch targets increases the probability of being able to ride in a vehicle earlier, and performs a transition output.

[0072] Note that, instead of the above-mentioned occupied vehicle rate of the vehicle with requirements, the empty vehicle rate of the vehicle with requirements can also be applied as the operating status. The empty vehicle rate of the vehicle with requirements indicates the proportion of the distance traveled by the vehicle with requirements in an empty state to the total distance traveled by the vehicle with requirements. Note that an empty vehicle refers to a state in which user 2 is not riding in the vehicle. For example, when the empty vehicle rate of the vehicle with requirements in the most recent hour is equal to or greater than a predetermined rate, the user terminal control unit 170 determines that user 2 is unaware that including the vehicle with requirements in the vehicle dispatch targets increases the probability of being able to ride in a vehicle earlier, and performs a transition output.

[0073] Furthermore, the actual vehicle time rate of the vehicle with requirements may be applied as the operating status. The actual vehicle time rate of the vehicle with requirements indicates the percentage of time during the business hours of the vehicle with requirements that the vehicle with requirements is in an actual vehicle state. For example, if the actual vehicle time rate of the vehicle with requirements in the most recent hour is equal to or less than a predetermined rate, the user terminal control unit 170 determines that the user 2 is unaware that including the vehicle with requirements in the vehicle dispatch targets increases the probability of getting on a vehicle earlier, and performs transition output.

[0074] Note that, instead of the above-described actual vehicle time rate of the vehicle with requirements, the empty time rate of the vehicle with requirements can also be applied as the operating status. The empty time rate of the vehicle with requirements indicates the percentage of time that the vehicle with requirements is empty during the business hours of the vehicle with requirements. For example, when the empty time rate of the vehicle with requirements in the most recent hour is equal to or greater than a predetermined rate, the user terminal control unit 170 determines that user 2 is unaware that including the vehicle with requirements in the vehicle dispatch targets increases the probability of getting a vehicle earlier, and performs transition output.

[0075] Furthermore, the number of times a vehicle with requirements is actually driven per unit time may be applied as the operating status. The number of times a vehicle with requirements is actually driven per unit time indicates the number of times per unit time that a vehicle with requirements is actually driven in response to a vehicle dispatch request 22. When the number of times that a vehicle with requirements is actually driven falls below a predetermined number, the user terminal control unit 170 determines that the user 2 is unaware that including a vehicle with requirements in the vehicle dispatch targets increases the probability of being able to board a vehicle early, and performs transition output. Note that instead of the number of times a vehicle with requirements is actually driven per unit time, the number of times a vehicle with requirements is actually driven per unit day (one day) may also be used as the operating status.

[0076] Furthermore, the actual vehicle distance per unit time of the vehicle with requirements may be applied as the operating status. The actual vehicle distance per unit time of the vehicle with requirements indicates the distance per unit time that the vehicle with requirements becomes an actual vehicle. When the actual vehicle distance falls below a predetermined distance, the user terminal control unit 170 determines that the user 2 is unaware that including the vehicle with requirements in the vehicle dispatch targets increases the probability of getting into a vehicle early, and performs transition output. Note that instead of the actual vehicle distance per unit time of the vehicle with requirements, the actual vehicle distance per unit day (day) of the vehicle with requirements can also be used as the operating status.

[0077] Furthermore, the matching rate of vehicles with requirements may be applied as the operating status. The matching rate of vehicles with requirements indicates the rate at which vehicles with requirements are allocated (matched) to vehicle dispatch requests 22 from user 2. When the matching rate of vehicles with requirements in the most recent hour falls below a predetermined rate, the user terminal control unit 170 determines that user 2 is unaware that including vehicles with requirements in the dispatch targets increases the probability of getting into a vehicle early, and performs transition output.

[0078] Furthermore, the ratio of the number of vehicles with requirements may be applied as the operating status. The ratio of the number of vehicles with requirements indicates the ratio of the number of vehicles with requirements currently operating in the operating area to the number of taxi vehicles 32 currently operating in the operating area, and is expressed as (the number of vehicles with requirements currently operating in the operating area) / (the number of taxi vehicles 32 currently operating in the operating area). Note that the ratio of the number of vehicles with requirements may also be the ratio of the number of vehicles with requirements currently operating in the operating area to the number of vehicles with requirements and taxi vehicles 32 currently operating in the operating area. In this case, the ratio of the number of vehicles with requirements is expressed as (the number of vehicles with requirements currently operating in the operating area) / (the number of vehicles with requirements currently operating in the operating area + the number of taxi vehicles 32 currently operating in the operating area). When the number ratio reaches a predetermined rate or more, the user terminal control unit 170 determines that the user 2 is unaware that the probability of getting into a vehicle early increases by including vehicles with requirements that have a relatively high number ratio in the vehicles to be dispatched, and outputs a transition signal.

[0079] In addition, the operating income per unit time of a vehicle with requirements may be applied as the operating status. The operating income per unit time of a vehicle with requirements indicates the income associated with the operation of the vehicle with requirements, i.e., the amount obtained by dividing the total fee associated with the use of the vehicle with requirements by the actual driving time. When the operating income falls below a predetermined amount, the user terminal control unit 170 determines that user 2 is unaware that including vehicles with requirements in the vehicle allocation targets increases the probability of being able to board a vehicle early, and performs transition output. Note that instead of the operating income per unit time of a vehicle with requirements, the operating income per unit day (day) of a vehicle with requirements can also be used as the operating status.

[0080] Furthermore, the operating income ratio of vehicles with conditions may be applied as the operating status. The operating income ratio of vehicles with conditions indicates the ratio of operating income of vehicles with conditions currently operating in the operating area to the operating income of taxi vehicles 32 currently operating in the operating area, and is expressed as (operating income of vehicles with conditions currently operating in the operating area) / (operating income of taxi vehicles 32 currently operating in the operating area). Note that the ratio of operating income of vehicles with conditions currently operating in the operating area to the operating income of vehicles with conditions currently operating in the operating area and taxi vehicles 32 may also be applied as the operating income ratio of vehicles with conditions. In this case, the operating income ratio of vehicles with conditions is expressed as (operating income of vehicles with conditions currently operating in the operating area) / (operating income of vehicles with conditions currently operating in the operating area + operating income of taxi vehicles 32 currently operating in the operating area). When the operating income ratio falls below a predetermined rate, the user terminal control unit 170 determines that user 2 is unaware that the probability of getting into a vehicle early increases by including vehicles with requirements in the vehicles to be dispatched, and outputs a transition.

[0081] In the present embodiment, an example has been described in which the user terminal control unit 170 individually determines the operating status based on the vehicle availability rate, empty vehicle availability rate, vehicle time rate, empty vehicle availability rate, number of vehicle availability times, vehicle distance traveled, matching rate, vehicle number ratio, operating revenue, and operating revenue ratio. However, the present embodiment is not limited to this example. The user terminal control unit 170 may also determine a combination of multiple operating statuses selected from the vehicle availability rate, empty vehicle availability rate, vehicle time rate, empty vehicle availability rate, number of vehicle availability times, vehicle distance traveled, matching rate, vehicle number ratio, operating revenue, and operating revenue ratio. In addition, in the present embodiment, the operating status has been described based on the vehicle availability rate, empty vehicle availability rate, vehicle time rate, empty vehicle availability rate, number of vehicle availability times, vehicle distance traveled, matching rate, vehicle number ratio, operating revenue, and operating revenue ratio. However, the present embodiment is not limited to this example. Various indices capable of determining the level of the operating status of a vehicle with requirements can be applied.

[0082] Next, the transition output will be described. As a transition output related to the transition from the first vehicle dispatch mode to the second vehicle dispatch mode, the user terminal control unit 170, for example, displays an image on the display device 124 of the user terminal 20 requesting additional input of a predetermined setting item. Such transition outputs for requesting additional input of a setting item include a first transition output and a second transition output. In such transition outputs, the strength of the prompt to transition from the first vehicle dispatch mode to the second vehicle dispatch mode is such that the first transition output is less than the second transition output. In the first transition output, for example, the user is prompted to additionally input the drop-off location as a setting item, and in the second transition output, for example, the user is prompted to additionally input information related to the drop-off location and automatic payment as setting items. For example, the user terminal control unit 170 performs the first transition output when the actual vehicle time rate becomes 1% or less, and performs the second transition output when the actual vehicle time rate becomes 2% or less, which is lower than 1%.

[0083] 11A is a first explanatory diagram illustrating the operation of the user terminal control unit 170. In response to an operation by the user 2, the vehicle dispatch request unit 180 of the user terminal 20 launches a user application for making a vehicle dispatch request 22. Then, the user terminal control unit 170 of the vehicle dispatch management server 60 causes the display device 124 of the user terminal 20 to display a map 210 of a predetermined range including the location of the user terminal 20, the location 212 of the user terminal 20, and vehicles 214 located near the user terminal 20, as shown in FIG. 11A. The user terminal control unit 170 also causes the display device 124 of the user terminal 20 to display an image 216 that prompts the user to input a boarding location and a disembarking location.

[0084] 11B is a second explanatory diagram for explaining the operation of the user terminal control unit 170. Assume that user 2 inputs a boarding location into boarding location text box 216a of image 216 in FIG. 11A via input device 126. Once the boarding location is input, a vehicle can be dispatched, so the user terminal control unit 170 displays image 218 including a "vehicle dispatch request" switch 218a on the display device 124 of the user terminal 20, as shown in FIG. 11B. If operation of the "vehicle dispatch request" switch 218a is enabled, user 2 can request a vehicle dispatch by operating the "vehicle dispatch request" switch 218a.

[0085] FIG. 12A is a first explanatory diagram illustrating the operation of the user terminal control unit 170. As described above, the user terminal control unit 170 may perform a first transition output based on the operational status of the taxi vehicle 32 or the vehicle with requirements. The user terminal control unit 170 outputs information regarding the additional input of a drop-off location to the user terminal 20 as the first transition output. Specifically, as shown in FIG. 12A, the user terminal control unit 170 displays an image 220 on the display device 124 of the user terminal 20, including a message prompting the user to additionally input a drop-off location: "Dispatch available in this area with specified drop-off location." When performing the first transition output, the user terminal control unit 170 disables the "Request a Vehicle Dispatch" switch 218a in the image 218 by graying it out or the like so that the vehicle dispatch request is not executed until the drop-off location input is complete. In this way, the user terminal control unit 170 prompts the user 2 to additionally input a drop-off location.

[0086] FIG. 12B is a second explanatory diagram illustrating the operation of the user terminal control unit 170. In a situation where it is difficult to dispatch a taxi vehicle 32 for a long period of time, user 2 may visually recognize the message in image 220 in FIG. 12A and input an additional drop-off location via the input device 126. Assume that user 2 operates the “Enter Drop-Off Location” switch 220a in image 220 in FIG. 12A via the input device 126. In response, the user terminal control unit 170 displays an image 222 prompting the user to input a drop-off location on the display device 124 of the user terminal 20, as shown in FIG. 12B. Assume that user 2 then inputs a drop-off location in the drop-off location text box 222a in image 222 in FIG. 12B via the input device 126. At this time, if cashless automatic payment has already been set as payment information in the user application, the dispatchability requirements for a vehicle with a condition are met, and the dispatch unit 172 is able to dispatch the vehicle with a condition in the second dispatch mode. When the vehicle dispatch requirement is met, the user terminal control unit 170 activates the "Request a vehicle dispatch" switch 218a in the image 218 in FIG. 12A. This allows user 2 to request a vehicle dispatch. With this configuration, user 2 can board NRS vehicle 42b early in the example of FIG. 10, for example.

[0087] Note that the description given here has been given of an example in which the user terminal control unit 170 displays an image 222 prompting the user to input a drop-off location on the display device 124 of the user terminal 20 in response to the user 2 operating the "Enter drop-off location" switch 220a in the image 220 of Fig. 12A. However, the present invention is not limited to this example. The user terminal control unit 170 may display a text box 222a prompting the user to input a drop-off location on the display device 124 instead of the "Enter drop-off location" switch 220a in the image 220 of Fig. 12A, and may display a message "Dispatch is available in this area with a specified drop-off location" while simultaneously prompting the user to input a drop-off location.

[0088] FIG. 13A is a first explanatory diagram illustrating the operation of the user terminal control unit 170. The user terminal control unit 170 may perform a second transition output based on the operational status of the taxi vehicle 32 or the vehicle with requirements. As the second transition output, the user terminal control unit 170 outputs information regarding the drop-off location and additional input of information regarding automatic payment to the user terminal 20. Specifically, if the drop-off location is entered in the drop-off location text box 222a of the image 222 in FIG. 12B but cashless automatic payment has not yet been set as payment information, the user terminal control unit 170 displays an image 230 on the display device 124 of the user terminal 20, as shown in FIG. 13A, that includes a message that reads, "Only automatic payment is available in this area," requesting additional input of information regarding automatic payment. When performing the second transition output, the user terminal control unit 170 disables the "Request a Vehicle Dispatch" switch 218a in the image 218 by graying it out or the like so that the vehicle dispatch request is not executed until the input of information regarding automatic payment is complete. In addition, various guidance messages such as "Additional settings for a faster ride" can be applied as a message prompting the user 2 to input additional information related to automatic payment. In this way, the user terminal control unit 170 prompts the user 2 to input additional information related to the drop-off location and automatic payment.

[0089] FIG. 13B is a second explanatory diagram illustrating the operation of the user terminal control unit 170. In a situation where it is difficult to dispatch a taxi vehicle 32 for a long period of time, user 2 may visually recognize the message in image 230 in FIG. 13A and additionally input information about the drop-off location and automatic payment via the input device 126. Assume that user 2 operates the “input payment information” switch 230a in image 230 in FIG. 13A via the input device 126. In response, the user terminal control unit 170 displays an image 232, as shown in FIG. 13B, on the display device 124 of the user terminal 20, requesting input of information about automatic payment. Here, assume that user 2 enters his or her credit card information via the input device 126 in the card number text box 232a, expiration date text box 232b, security code text box 232c, and cardholder text box 232d in image 232 in FIG. 13B. In this way, by inputting information regarding the drop-off location and automatic payment, the dispatch requirement for the vehicle with the conditions is met, and the dispatch unit 172 can dispatch the vehicle with the conditions in the second dispatch mode. When the dispatch requirement is met, the user terminal control unit 170 activates the "Request Dispatch" switch 218a in the image 218 of FIG. 13A. In this way, user 2 can request a vehicle dispatch. With this configuration, user 2 can board NRS vehicle 42b early, for example, in the example of FIG. 10.

[0090] Note that the description given here has been given of an example in which the user terminal control unit 170 displays an image 232 prompting input of information regarding automatic payment on the display device 124 of the user terminal 20 in response to user 2 operating the "Enter payment information" switch 230a in image 230 in Fig. 13A. However, the present invention is not limited to this example. Instead of the "Enter payment information" switch 230a in image 230 in Fig. 13A, the user terminal control unit 170 may display text boxes 232a-232d prompting input of information regarding automatic payment on the display device 124, and may display the message "Only automatic payment is available in this area" while simultaneously prompting input of information regarding automatic payment.

[0091] In the present embodiment, when the user terminal control unit 170 performs the second transition output, if the drop-off location has not been entered, the user terminal control unit 170 displays the image 220 shown in FIG. 12A containing the message "Dispatch available with specified drop-off location in this area" on the display device 124 to prompt the user to enter the drop-off location. If the drop-off location has been entered but no information regarding automatic payment has been entered, the user terminal control unit 170 displays the image 230 shown in FIG. 13A containing the message "Only automatic payment is available in this area" on the display device 124 to prompt the user to enter information regarding automatic payment. However, the present invention is not limited to this example. The user terminal control unit 170 may determine whether information regarding the drop-off location and automatic payment has been entered, and may display either the image 220 or the image 230 on the display device 124 for the setting items that have not been entered to prompt the user to enter the information. Here, if neither the drop-off location nor the automatic payment setting items have been entered, the user terminal control unit 170 may simultaneously display the image 220 and the image 230 on the display device 124. Furthermore, for example, if user 2 has previously input the boarding location and disembarking location in image 216 in Figure 11A, which prompts the user to input the boarding location and disembarking location, the user terminal control unit 170 may omit displaying image 220 shown in Figure 12A, which includes the message "Dispatch is available in this area with a specified disembarking location," and if information regarding automatic payment has not been input, may display image 230 shown in Figure 13A, which includes the message "Only automatic payment is available in this area," on display device 124 to prompt the user to input information regarding automatic payment.

[0092] In addition, in the present embodiment, an example has been described in which the user terminal control unit 170, after causing the user terminal 20 to output information regarding the additional input of information about the drop-off location or automatic payment, disables the "Ride Dispatch Request" switch 218a in the image 218 in FIG. 12A or 13A until the user 2 additionally inputs information about the drop-off location or automatic payment, and then enables the "Ride Dispatch Request" switch 218a in the image 218 in FIG. 12A or 13A once the user 2 additionally inputs information about the drop-off location or automatic payment, thereby enabling a ride dispatch request. However, the present invention is not limited to this example. The user terminal control unit 170 may also strongly urge the user 2 to additionally input information about the drop-off location or automatic payment by not displaying the image 218 in FIG. 12A or 13A itself until the user 2 additionally inputs information about the drop-off location and automatic payment. In addition, after the user terminal control unit 170 outputs information regarding additional input of information regarding the drop-off location and automatic payment to the user terminal 20, the user terminal control unit 170 may strongly urge the user 2 to input additional information regarding the drop-off location or automatic payment by preventing the image 220 or the image 230 from being deleted until the user 2 inputs additional information regarding the drop-off location and automatic payment.

[0093] Furthermore, in the present embodiment, an example has been described in which, after the user terminal control unit 170 causes the user terminal 20 to output information regarding the additional input of information regarding the drop-off location or automatic payment, a taxi dispatch request is not possible until the user 2 additionally inputs information regarding the drop-off location or automatic payment, i.e., additional input is forced. However, the present invention is not limited to such an example. In a case where a taxi can be dispatched without information regarding the drop-off location or automatic payment, such as when a taxi can be dispatched over time, the user terminal control unit 170 may keep the "taxi dispatch request" switch 218a in the image 218 of FIG. 12A or 13A in an enabled state rather than disabled, so that a taxi dispatch request can be made even when information regarding the drop-off location or automatic payment has not been input. As described above, if the user terminal control unit 170 causes the user terminal 20 to output information regarding the drop-off location and additional input of information regarding automatic payment, and then prevents the image 218 of Figure 12A or Figure 13A from being displayed until the user 2 inputs additional information regarding automatic payment, the user terminal control unit 170 may cause the display device 124 to display the image 218 of Figure 12A or Figure 13A when the user 2 proceeds with the operation by using a ``Next'' switch (not shown) or switching the screen, etc.

[0094] In the present embodiment, the user terminal control unit 170 has been described as displaying, as a transition output, an image including a message requesting additional input of a predetermined setting item through the user terminal 20. However, the present invention is not limited to this example. The user terminal control unit 170 can, for example, display on the display device 124 of the user terminal 20 various images for making a vehicle with requirements available for dispatch, such as a message directly requesting that the user include a vehicle with requirements in the vehicle dispatch target, such as "If it is an NRS vehicle, it can be dispatched." At this time, the user terminal control unit 170 may also display on the display device 124 the message "If it is an NRS vehicle, it can be dispatched," along with an "Input to make an NRS vehicle available for dispatch" switch, prompting the user 2 to make an additional input to make the NRS vehicle 42 available for dispatch.

[0095] With this configuration, even in a situation where the supply of taxi vehicles 32 is insufficient and taxi vehicles 32 cannot be dispatched immediately, it is possible to dispatch a vehicle with a condition, and user 2 can get into a vehicle early. In this way, by expanding the targets for dispatch from taxi vehicles 32 to taxi vehicles 32 and vehicles with a condition, the vehicle dispatch management system 1 enables efficient vehicle dispatch. Furthermore, although vehicles with a condition may be more limited in dispatch than taxi vehicles 32, with this configuration, the dispatchability requirements for vehicles with a condition are more likely to be met, and therefore the utilization rate of the vehicles with a condition themselves can be improved.

[0096] However, the user terminal control unit 170 will request the user 2 to additionally input the drop-off location in the first transition output, and in the second transition output, in addition to inputting the drop-off location, will request the user 2 to additionally input information related to cashless automatic payment as payment information. Therefore, some users 2 may find such additional input bothersome or may not want to set up cashless automatic payment. Therefore, the user terminal control unit 170 will strictly limit the first transition output or second transition output to areas where the supply of taxi vehicles 32 is insufficient. The user terminal control unit 170 may, for example, limit the business area to an area of ​​1 km 2 For each of the mesh-shaped divided sections, the vehicle operation status is checked, for example, every 30 minutes, and the first transition output or the second transition output is performed for users 2 included in the divided section where the vehicle operation status satisfies a predetermined condition. In this way, by limiting the geographical range to which the first transition output or the second transition output is applied, additional input is not required of an unnecessarily large number of users 2, and the number of users 2 who find the additional input bothersome can be reduced.

[0097] In the present embodiment, an example has been described in which the user terminal control unit 170 performs transition output through the user terminal 20 based on the vehicle's operating status. However, the present invention is not limited to this example, and the user terminal control unit 170 may perform transition output regardless of the vehicle's operating status. For example, if there are time restrictions on the operation of the requirement vehicle in the vehicle's operating area, the user terminal control unit 170 may perform transition output through the user terminal 20 during the time period when the requirement vehicle is able to operate in the operating area, regardless of the operating status.

[0098] Furthermore, in the present embodiment, an example has been described in which the user terminal control unit 170 displays an image including information about the mode transition on the display device 124 of the user terminal 20 as an example of outputting information about the mode transition to the user terminal 20. However, the present invention is not limited to this example, and the user terminal control unit 170 may also output information about the mode transition from the user terminal 20 as sound or vibration.

[0099] In this way, the vehicle dispatch management system 1 comprises a user terminal 20 and a vehicle dispatch management device (e.g., a vehicle dispatch management server 60) that can communicate with the user terminal 20 via a network, the user terminal 20 comprising one or more first processors, the vehicle dispatch management device comprising one or more second processors, the first processor sending a vehicle dispatch request to the vehicle dispatch management device in accordance with user input, the second processor executing a first vehicle dispatch mode in which a first vehicle (e.g., a taxi vehicle 32) is assigned to the vehicle dispatch request but a second vehicle (e.g., a vehicle with requirements including an NRS vehicle 42) that has different dispatch requirements from the first vehicle is not assigned, or a second vehicle dispatch mode in which either the first vehicle or the second vehicle is assigned to the vehicle dispatch request, and outputting information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal 20 based on the operating status of the first vehicle or the second vehicle (e.g., when the actual vehicle time rate of the NRS vehicle 42 becomes equal to or less than a predetermined rate). With this configuration, even in a situation where the supply of taxi vehicles 32 is insufficient and taxi vehicles 32 cannot be dispatched immediately, a vehicle with requirements can be dispatched, and user 2 can get into a vehicle early. In this way, efficient vehicle dispatch is possible.

[0100] Furthermore, a vehicle dispatch management device (e.g., vehicle dispatch management server 60) capable of communicating with user terminal 20 via a network includes one or more processors. The processor executes a first dispatch mode in which a first vehicle (e.g., taxi vehicle 32) is assigned to a dispatch request received from user terminal 20, but a second vehicle (e.g., a conditional vehicle including NRS vehicle 42) with different dispatchability requirements from the first vehicle is not assigned, or a second dispatch mode in which either the first vehicle or the second vehicle is assigned to a dispatch request. Based on the operating status of the first vehicle or the second vehicle (e.g., when the actual vehicle time rate of NRS vehicle 42 falls below a predetermined rate), information regarding a transition from the first dispatch mode to the second dispatch mode is output to user terminal 20. With this configuration, even in a situation where taxi vehicle 32 supply is insufficient and a taxi vehicle 32 cannot be dispatched immediately, a conditional vehicle can be dispatched, allowing user 2 to board a vehicle early. This enables efficient vehicle dispatch.

[0101] Furthermore, the information regarding the transition from the first vehicle dispatch mode to the second vehicle dispatch mode may be information regarding the additional input of a predetermined setting item required in the second vehicle dispatch mode (e.g., a drop-off location), and when the predetermined setting item is additionally input in the user terminal 20, the processor may transition from the first vehicle dispatch mode to the second vehicle dispatch mode and assign either a first vehicle (e.g., a taxi vehicle 32) or a second vehicle (e.g., a vehicle with requirements including an NRS vehicle 42) to the vehicle dispatch request. The predetermined setting item may include a drop-off location where the user wishes to get off. The predetermined setting item may include a drop-off location where the user wishes to get off and information regarding automatic payment. With this configuration, the vehicle dispatch management server 60 can provide the user 2 with an opportunity to select the dispatch of a vehicle with requirements.

[0102] The operating status may include the on-board rate of the second vehicle (for example, a vehicle with requirements including the NRS vehicle 42), and when the on-board rate of the second vehicle falls below a predetermined rate, the processor may output information regarding the transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal 20. With this configuration, the vehicle dispatch management server 60 can appropriately determine that the user 2 is unaware that the probability of getting into a vehicle early increases by including a vehicle with requirements in the targets for dispatch, and can give the user 2 an opportunity to select dispatch of a vehicle with requirements.

[0103] The operating status may include the actual vehicle time rate of the second vehicle (for example, a vehicle with requirements including the NRS vehicle 42), and when the actual vehicle time rate of the second vehicle becomes equal to or less than a predetermined rate, the processor may output information regarding the transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal 20. With this configuration, the vehicle dispatch management server 60 can appropriately determine that the user 2 is unaware that the probability of getting into a vehicle early increases by including a vehicle with requirements in the vehicle dispatch targets, and can give the user 2 an opportunity to select dispatch of a vehicle with requirements.

[0104] The operating status may include the number of times the second vehicle (e.g., a vehicle with requirements including the NRS vehicle 42) is actually driven per unit time, and the processor may output information regarding the transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal 20 when the number of times the second vehicle is actually driven per unit time falls below a predetermined number. With this configuration, the vehicle dispatch management server 60 can appropriately determine that the user 2 is unaware that the probability of getting into a vehicle early increases by including a vehicle with requirements in the vehicle dispatch targets, and can give the user 2 an opportunity to select the dispatch of a vehicle with requirements.

[0105] The operating status may include the actual vehicle distance per unit time of the second vehicle (for example, a vehicle with requirements including NRS vehicle 42), and the processor may output information regarding the transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal when the actual vehicle distance per unit time of the second vehicle becomes equal to or less than a predetermined distance. With this configuration, the vehicle dispatch management server 60 can appropriately determine that user 2 is unaware that including vehicles with requirements in the vehicle dispatch targets increases the probability of being able to board a vehicle early, and can give user 2 an opportunity to select dispatch of a vehicle with requirements.

[0106] The operating status includes a matching rate at which a second vehicle (e.g., a vehicle with requirements including NRS vehicle 42) is allocated in response to a vehicle allocation request, and the processor may output information regarding a transition from the first vehicle allocation mode to the second vehicle allocation mode to the user terminal 20 when the matching rate at which the second vehicle is allocated falls below a predetermined rate. With this configuration, the vehicle allocation management server 60 can appropriately determine that the user 2 is unaware that the probability of getting into a vehicle early increases by including a vehicle with requirements in the vehicle allocation targets, and can give the user 2 an opportunity to select allocation of a vehicle with requirements.

[0107] The operating status includes the ratio of the number of second vehicles (e.g., vehicles with requirements including NRS vehicles 42) currently in operation to the number of first vehicles (e.g., taxi vehicles 32) currently in operation, and the processor may output information regarding the transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal 20 when the ratio of the number of second vehicles currently in operation falls below a predetermined rate. With this configuration, the vehicle dispatch management server 60 can appropriately determine that the user 2 is unaware that the probability of getting into a vehicle early increases by including vehicles with requirements in the vehicles to be dispatched, and can give the user 2 an opportunity to select the dispatch of a vehicle with requirements.

[0108] The operating status may include the operating income per unit time of the second vehicle (for example, a vehicle with requirements including the NRS vehicle 42), and the processor may output information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal 20 when the operating income per unit time of the second vehicle falls below a predetermined amount. With this configuration, the vehicle dispatch management server 60 can appropriately determine that the user 2 is unaware that the probability of getting on a vehicle early increases by including a vehicle with requirements in the vehicle dispatch targets, and can give the user 2 an opportunity to select dispatch of a vehicle with requirements.

[0109] The operating status includes the operating income ratio of a second vehicle currently in operation (e.g., a vehicle with requirements including an NRS vehicle 42) to a first vehicle currently in operation (e.g., a taxi vehicle 32), and the processor may output information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal 20 when the operating income ratio of the second vehicle currently in operation falls below a predetermined rate. With this configuration, the vehicle dispatch management server 60 can appropriately determine that the user 2 is unaware that the probability of getting into a vehicle early increases by including a vehicle with requirements in the vehicle dispatch targets, and can give the user 2 an opportunity to select dispatch of a vehicle with requirements.

[0110] In addition, the vehicle dispatch management method executes a first vehicle dispatch mode in which a first vehicle (e.g., a taxi vehicle 32) is assigned to a dispatch request received from a user terminal 20, but a second vehicle (e.g., a vehicle with requirements including an NRS vehicle 42) having different dispatch requirements from the first vehicle is not assigned, or a second vehicle dispatch mode in which either the first vehicle or the second vehicle is assigned to a dispatch request, and outputs information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal 20 based on the operating status of the first vehicle or the second vehicle (e.g., when the actual vehicle time rate of the NRS vehicle 42 falls below a predetermined rate). With this configuration, even in a situation where the supply of taxi vehicles 32 is insufficient and a taxi vehicle 32 cannot be dispatched immediately, an NRS vehicle 42 can be dispatched, allowing the user 2 to board the vehicle early. This enables efficient vehicle dispatch.

[0111] The program also causes the computer to execute a first vehicle dispatch mode in which a first vehicle (e.g., a taxi vehicle 32) is assigned to a dispatch request received from the user terminal 20, but a second vehicle (e.g., a conditional vehicle including an NRS vehicle 42) with different dispatch requirements from the first vehicle is not assigned, or a second vehicle dispatch mode in which either the first vehicle or the second vehicle is assigned to the dispatch request, and to output information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal 20 based on the operating status of the first vehicle or the second vehicle (e.g., when the actual vehicle time rate of the NRS vehicle 42 falls below a predetermined rate). With this configuration, even in a situation where the supply of taxi vehicles 32 is insufficient and taxi vehicles 32 cannot be dispatched immediately, a conditional vehicle can be dispatched, allowing the user 2 to board a vehicle early. This enables efficient vehicle dispatch.

[0112] 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.

[0113] 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.

[0114] 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]

[0115] 1. Vehicle dispatch management system 2 users 3. Taxi Driver 4 NRS Driver 20 User terminal 30 Taxi terminal 32 Taxi vehicle (first vehicle) 40 NRS terminals 42 NRS vehicle (2nd vehicle) 50 Business Server 60 Vehicle dispatch management server (vehicle dispatch management device) 170 User terminal control unit 172 Dispatch Department 174 Vehicle terminal control unit 180 Vehicle Dispatch Request Department 182 Dispatch Response Unit 184 Dispatch Response Unit 186 Vehicle Management Department

Claims

1. A user terminal; a vehicle dispatch management device capable of communicating with the user terminal via a network; A vehicle dispatch management system comprising: The user terminal one or more first processors; The vehicle dispatch management device one or more second processors; The first processor: Transmitting a vehicle dispatch request to the vehicle dispatch management device in response to a user input; The second processor: execute a first vehicle allocation mode in which a first vehicle is allocated in response to the vehicle allocation request, but a second vehicle having different vehicle allocation availability requirements from the first vehicle is not allocated, or a second vehicle allocation mode in which either the first vehicle or the second vehicle is allocated in response to the vehicle allocation request; outputting, to the user terminal, information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode based on an operating status of the first vehicle or the second vehicle; Vehicle dispatch management system.

2. A vehicle dispatch management device capable of communicating with a user terminal via a network, one or more processors; the processor: executes a first vehicle allocation mode in which a first vehicle is allocated in response to a vehicle allocation request received from the user terminal, but a second vehicle having different vehicle allocation availability requirements from the first vehicle is not allocated, or a second vehicle allocation mode in which either the first vehicle or the second vehicle is allocated in response to the vehicle allocation request; outputting, to the user terminal, information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode based on an operating status of the first vehicle or the second vehicle; Vehicle dispatch management device.

3. the information regarding the transition from the first vehicle dispatch mode to the second vehicle dispatch mode is information regarding additional input of a predetermined setting item required in the second vehicle dispatch mode; The processor: When the predetermined setting item is additionally input in the user terminal, the mode transitions from the first vehicle dispatch mode to the second vehicle dispatch mode, The vehicle allocation management device according to claim 2 , wherein either the first vehicle or the second vehicle is allocated in response to the vehicle allocation request.

4. The vehicle dispatch management device according to claim 3 , wherein the predetermined setting items include a destination at which the user wishes to get off.

5. The vehicle dispatch management device according to claim 3 , wherein the predetermined setting items include a destination where the user wishes to get off and information regarding automatic payment.

6. The operation status includes an actual vehicle rate of the second vehicle, The vehicle dispatch management device according to claim 2 , wherein the processor outputs information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal when the actual vehicle rate of the second vehicle becomes equal to or less than a predetermined rate.

7. The operating status includes an actual vehicle time rate of the second vehicle, 3. The vehicle dispatch management device according to claim 2, wherein the processor outputs information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal when the actual vehicle time rate of the second vehicle becomes equal to or less than a predetermined rate.

8. The operating status includes the number of actual vehicle trips per unit time of the second vehicle, 3. The vehicle dispatch management device according to claim 2, wherein the processor outputs information regarding the transition from the first dispatch mode to the second dispatch mode to the user terminal when the number of actual vehicle trips per unit time of the second vehicle becomes equal to or less than a predetermined number.

9. the operating status includes an actual vehicle distance per unit time of the second vehicle; 3. The vehicle dispatch management device according to claim 2, wherein the processor outputs information regarding a transition from the first dispatch mode to the second dispatch mode to the user terminal when the actual vehicle distance per unit time of the second vehicle becomes less than a predetermined distance.

10. The operation status includes a matching rate at which the second vehicle is assigned to the vehicle dispatch request, and 3. The vehicle dispatch management device according to claim 2, wherein the processor outputs information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode to the user terminal when the matching rate at which the second vehicle is assigned becomes equal to or lower than a predetermined rate.

11. the operation status includes a ratio of the number of the second vehicles currently in operation to the number of the first vehicles currently in operation; 3. The vehicle dispatch management device according to claim 2, wherein the processor outputs information regarding a transition from the first dispatch mode to the second dispatch mode to the user terminal when the ratio of the number of second vehicles currently in operation falls below a predetermined ratio.

12. The operating status includes an operating income per unit time of the second vehicle, 3. The vehicle dispatch management device according to claim 2, wherein the processor outputs information regarding a transition from the first dispatch mode to the second dispatch mode to the user terminal when the operating income per unit time of the second vehicle falls below a predetermined amount.

13. The operation status includes an operating income ratio of the second vehicle currently in operation to the first vehicle currently in operation; The vehicle dispatch management device of claim 2, wherein the processor outputs information regarding a transition from the first dispatch mode to the second dispatch mode to the user terminal when the operating income ratio of the second vehicle currently in operation falls below a predetermined rate.

14. The computer execute a first vehicle allocation mode in which a first vehicle is allocated in response to a vehicle allocation request received from a user terminal, but a second vehicle having different vehicle allocation availability requirements from the first vehicle is not allocated, or a second vehicle allocation mode in which either the first vehicle or the second vehicle is allocated in response to the vehicle allocation request; outputting, to the user terminal, information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode based on an operating status of the first vehicle or the second vehicle; Vehicle allocation management method.

15. On the computer, execute a first vehicle allocation mode in which a first vehicle is allocated in response to a vehicle allocation request received from a user terminal, but a second vehicle having different vehicle allocation availability requirements from the first vehicle is not allocated, or a second vehicle allocation mode in which either the first vehicle or the second vehicle is allocated in response to the vehicle allocation request; outputting, to the user terminal, information regarding a transition from the first vehicle dispatch mode to the second vehicle dispatch mode based on an operating status of the first vehicle or the second vehicle; A program to make it happen.

Images