Dispatch management system, dispatch management device, method for managing dispatch management, program, and user terminal

Abstract

To provide a high-quality driving service in return for an additional fee paid by a user.SOLUTION: A dispatch management system (1) includes a plurality of user terminals (20) and a dispatch management device, such as a dispatch management server (60). Each user terminal (20) executes processing (S1) of transmitting a dispatch request to the dispatch management device in response to an input from a user. The dispatch management device executes dispatch processing (S2-S6) of assigning a vehicle to the dispatch request on the basis of evaluation criteria related to driving performance of a driver. In the dispatch processing (S2-S6), when the dispatch request is a paid dispatch request that increases the dispatch priority through payment of an additional fee, the dispatch management device assigns, to the paid dispatch request, a vehicle of a driver satisfying the evaluation criteria.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present invention relates to a vehicle dispatch management system for managing vehicle dispatch, a vehicle dispatch management device, a vehicle dispatch management method, a program, and a user terminal. [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, ride-sharing (Japanese-style ride-sharing) services, in which ordinary drivers use their own cars to transport users for a fee, are being introduced. With the introduction of ride-sharing services, it is expected that the number of drivers with little driving experience will increase. Furthermore, even among taxi drivers, the quality of the driving service they can provide to passengers varies depending on factors such as their driving history and driving skills.

[0005] In the taxi business, etc., there are priority dispatch services in which users are given priority over other users by paying an additional fee in addition to the regular fare during peak times when the supply of dispatched vehicles is insufficient to meet the demand for dispatched vehicles, and reservation dispatch services in which users can reserve a desired ride date and time in advance. Users who pay an additional fee for these dispatch services often expect higher quality driving service from the driver than with regular dispatch. Therefore, when dispatching a vehicle with a driver who provides relatively low quality driving service in a dispatch service that requires an additional fee, user satisfaction may decrease. Furthermore, in reservation dispatch services, the driver is responsible for arriving at the pickup location by the specified pickup time, even during times of heavy traffic, which puts pressure on the driver.

[0006] In this way, dispatching a vehicle that involves the payment of an additional fee may involve higher expectations from the user and greater responsibility and pressure on the driver compared to regular dispatching that does not involve an additional fee. Therefore, in dispatching a vehicle that involves an additional fee, it is desirable to dispatch a vehicle with a driver who can provide high-quality driving service in return for the additional fee paid by the user.

[0007] In view of these problems, the present invention aims to provide a vehicle dispatch management system, a vehicle dispatch management device, a vehicle dispatch management method, a program, and a user terminal that can provide high-quality driving services in exchange for an additional fee paid by the user. [Means for solving the problem]

[0008] In order to solve the above problem, according to one aspect of the present invention, there is provided a vehicle dispatch management system comprising a plurality of user terminals and a vehicle dispatch management device communicatively connected to the user terminals via a network, wherein the user terminals comprise one or more first processors, and the vehicle dispatch management device comprises one or more second processors, wherein the first processor of the user terminal executes a process of sending a vehicle dispatch request to the vehicle dispatch management device in accordance with user input, and the second processor of the vehicle dispatch management device executes a vehicle dispatch process of allocating a vehicle to the vehicle dispatch request received from the user terminal based on evaluation criteria related to the driver's driving, and wherein, in the vehicle dispatch process, if the vehicle dispatch request is a charging vehicle dispatch request that increases the priority of the vehicle dispatch by charging an additional fee, a vehicle of a driver who meets the evaluation criteria is allocated to the charging vehicle dispatch request.

[0009] In order to solve the above problem, according to another aspect of the present invention, there is provided a vehicle dispatch management device that is communicatively connected to a user terminal via a network, the vehicle dispatch management device having one or more processors, the processors executing a vehicle dispatch process that allocates a vehicle to a vehicle dispatch request received from the user terminal based on evaluation criteria related to the driver's driving, and in the vehicle dispatch process, if the vehicle dispatch request is a charging vehicle dispatch request that increases the priority of the vehicle dispatch by charging an additional fee, the vehicle dispatch management device allocates a vehicle of a driver that meets the evaluation criteria to the charging vehicle dispatch request.

[0010] In the vehicle allocation process, if the vehicle allocation request is a charging vehicle allocation request, a vehicle of a driver who does not satisfy the evaluation criteria may not be allocated to the charging vehicle allocation request, or the allocation priority of the vehicle may be lowered.

[0011] In the vehicle allocation process, if the vehicle allocation request is not a charging vehicle allocation request, a vehicle may be allocated to the vehicle allocation request regardless of the evaluation criterion.

[0012] The evaluation criteria may include criteria relating to the driver's driving qualifications.

[0013] The evaluation criteria may include criteria related to at least one of the driver's driving experience, the driver's driving education, the driver's traffic violation history, a user's rating of the driver, and the driver's driving score calculated by the driving analysis software.

[0014] The charging vehicle dispatch request may include a priority vehicle dispatch request that, by charging the additional fee, increases the priority of vehicle dispatch over a normal vehicle dispatch request that does not involve charging the additional fee.

[0015] The charging vehicle dispatch request may include a reservation vehicle dispatch request in which a desired boarding date and time can be specified in advance by charging the additional fee.

[0016] In order to solve the above problem, according to another aspect of the present invention, there is provided a vehicle dispatch management method executed by a computer, which includes a vehicle dispatch process that allocates a vehicle to a vehicle dispatch request received from a user terminal based on evaluation criteria related to the driver's driving, and in the vehicle dispatch process, if the vehicle dispatch request is a charged vehicle dispatch request that increases the priority of the vehicle dispatch by charging an additional fee, a vehicle of a driver who meets the evaluation criteria is allocated to the charged vehicle dispatch request.

[0017] In order to solve the above problem, according to another aspect of the present invention, there is provided a program for causing a computer to execute a vehicle dispatch process that allocates a vehicle to a vehicle dispatch request received from a user terminal based on evaluation criteria related to the driver's driving, wherein in the vehicle dispatch process, if the vehicle dispatch request is a charged vehicle dispatch request that increases the priority of the vehicle dispatch by charging an additional fee, a vehicle of a driver who meets the evaluation criteria is allocated to the charged vehicle dispatch request.

[0018] In order to solve the above problem, according to another aspect of the present invention, there is provided a user terminal that is communicatively connected via a network to a vehicle dispatch management device that dispatches a vehicle selected from a plurality of vehicles, wherein the user terminal is equipped with one or more processors, and the processors execute a transmission process that sends a vehicle dispatch request to the vehicle dispatch management device in accordance with a user's specification, wherein the plurality of vehicles include at least one first vehicle driven by a first driver and at least one second vehicle driven by a second driver who has a different type of driving qualification than the first driver, and wherein the transmission process is capable of sending a first vehicle dispatch request to the vehicle dispatch management device as the vehicle dispatch request, designating both the first vehicle and the second vehicle as vehicles to be dispatched in accordance with the user's specification.

[0019] In the transmission process, in accordance with the user's specification, a second dispatch request that designates only the first vehicle as the vehicle to be dispatched can be sent to the dispatch management device as the dispatch request instead of the first dispatch request.

[0020] In the transmission process at the time of the first vehicle dispatch request, the first vehicle dispatch request can be sent to the vehicle dispatch management device according to the user's specifications, and in the transmission process at the time of the second or subsequent re-dispatch request, or at the time of a charged vehicle dispatch request that involves charging an additional fee, the second vehicle dispatch request may be sent to the vehicle dispatch management device as the vehicle dispatch request. [Effects of the Invention]

[0021] According to the present invention, a high-quality driving service can be provided in return for the additional fee paid by the user. [Brief explanation of the drawings]

[0022] [Figure 1] FIG. 1 is a block diagram for explaining an outline of a vehicle dispatch management system according to a first embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram illustrating the configuration of a user terminal according to the embodiment. [Figure 3] FIG. 3 is a block diagram illustrating the configuration of the taxi terminal according to the embodiment. [Figure 4] FIG. 4 is a block diagram illustrating the configuration of the NRS terminal according to the embodiment. [Figure 5] FIG. 5 is a block diagram illustrating the configuration of the business server according to the embodiment. [Figure 6] FIG. 6 is a block diagram illustrating the configuration of the vehicle dispatch management server according to the embodiment. [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 according to the embodiment. [Figure 8] FIG. 8 is an explanatory diagram for explaining the processing of the dispatch unit according to the embodiment. [Figure 9] FIG. 9 is an explanatory diagram showing a result of matching by the dispatch unit according to the embodiment. [Figure 10] 10A and 10B are explanatory diagrams illustrating an example of a display screen of a user terminal when a vehicle dispatch request is made according to the embodiment, and when a vehicle dispatch request is changed. [Figure 11] FIG. 11 is an explanatory diagram showing the result of matching by the vehicle dispatch unit at the time of priority vehicle dispatch according to the embodiment. [Figure 12] FIG. 12 is a sequence diagram showing the flow of processing in a vehicle allocation management method by a vehicle allocation management system according to the second embodiment of the present invention. [Figure 13] 13A and 13B are explanatory diagrams illustrating an example of a display screen of a vehicle terminal during pickup according to the embodiment, and a user terminal when reporting cancellation of vehicle dispatch according to the embodiment. [Figure 14] FIG. 14 is a sequence diagram showing the flow of the vehicle detection process and the display control process according to the progress of the process according to the third embodiment of the present invention. [Figure 15] 15A and 15B are diagrams illustrating an example of a display image of a user terminal when requesting vehicle allocation according to the embodiment. [Figure 16]FIG. 16 is an explanatory diagram showing an example of a display image of a user terminal during vehicle search processing in the normal vehicle dispatch mode according to the embodiment. [Figure 17] 17A and 17B are explanatory diagrams showing examples of images displayed on the user terminal during the continuous vehicle search process in the normal vehicle dispatch mode according to the embodiment. [Figure 18] 18A and 18B are explanatory diagrams showing examples of a display image of a user terminal when a priority vehicle dispatch request is made according to the embodiment, and a display image of a user terminal when a vehicle search process is performed in priority vehicle dispatch mode according to the embodiment. [Figure 19] FIG. 19 is an explanatory diagram showing an example of a display image of the user terminal when vehicle dispatch is confirmed according to the embodiment. [Figure 20] FIG. 20 is a sequence diagram showing the flow of a vehicle detection process according to a modification of the embodiment and a display control process according to the progress of the process. [Figure 21] 21A and 21B are explanatory diagrams showing an example of a display image of a user terminal during a continuous vehicle search process in a normal vehicle dispatch mode according to a modification of the same embodiment. [Figure 22] 22A and 22B are explanatory diagrams showing examples of a display image of a user terminal when a continuous vehicle search process is performed in a normal vehicle dispatch mode according to a modified example of the embodiment, and when a vehicle dispatch is confirmed according to a modified example of the embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0024] [1. First embodiment] A vehicle dispatch management system according to a first embodiment of the present invention will be described below. The vehicle dispatch management system according to the first embodiment performs a vehicle dispatch process that adjusts the vehicle to be assigned to a user's vehicle dispatch request based on evaluation criteria related to the driver's driving. In this case, the vehicle dispatch management system according to the first embodiment is characterized in that, when a vehicle dispatch request from a user is a paid vehicle dispatch request that requires payment of an additional fee in addition to the normal fare, the vehicle dispatch management system preferentially dispatches a vehicle of a highly rated driver who can provide high-quality driving service in response to the paid vehicle dispatch request. The configuration of the vehicle dispatch management system and the vehicle dispatch management method for realizing such features will be described below in order.

[0025] [1.1. Vehicle dispatch management system configuration] First, the overall configuration of a vehicle dispatch management system 1 according to the first embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram for explaining an outline of the vehicle dispatch management system 1 according to this embodiment.

[0026] As shown in Figure 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 are means of transportation 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.

[0027] [1.2. User terminal configuration] 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.

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

[0029] [1.3. Taxi terminal configuration] The taxi terminal 30 is an electronic device loaned to a taxi driver (first 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).

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

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

[0032] [1.4. NRS Terminal Configuration] The NRS terminal 40 is an electronic device owned by the NRS driver (second 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 the NRS terminal 40 that he or she owns into the NRS vehicle 42, which is his or her own personal car, and drives the NRS vehicle 42. 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).

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

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

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

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

[0037] 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."

[0038] [1.5. Provider Server Configuration] 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.

[0039] [1.6. Vehicle dispatch management server configuration] 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.

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

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

[0042] As shown in Figure 7, the vehicle allocation request method according to this embodiment includes a vehicle allocation request process (S1), a vehicle allocation request accumulation process (S2), a vehicle allocation request extraction process (S3), a vehicle extraction process (S4), a pair generation process (S5), a matching process (S6), a vehicle allocation inquiry notification process (S7), an acceptance response process (S8), and a vehicle allocation completion notification process (S9, S10). Of these processes (S1) to (S10), processes (S2) to (S6) correspond to a process of searching for a vehicle that matches the vehicle allocation request and assigning the searched vehicle to the vehicle allocation request (hereinafter referred to as "vehicle allocation process"). Note that, hereinafter, the process of searching for a vehicle that matches the vehicle allocation request within the vehicle allocation process may also be referred to as "vehicle search process."

[0043] (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 also 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 transmits the vehicle dispatch request to vehicle dispatch management server 60, including information related to the setting items set by user 2.

[0044] The setting items include, in addition to the initial taxi dispatch request, for example, boarding location, disembarking location, payment information, dispatch category, taxi company, vehicle attributes, etc.

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

[0046] 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 automatic payment from the user 2, 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 driver needs to input the drop-off location and information regarding automatic payment as a requirement for dispatchability.

[0047] 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 vehicle dispatch category (second vehicle dispatch request). On the other hand, if the vehicle dispatch target is limited to taxi vehicles 32, user 2 will miss the opportunity to ride in a vehicle with requirements, even if a vehicle with requirements can be dispatched quickly. Therefore, user 2 may not limit the vehicle dispatch target to taxi vehicles 32, but may wish to ride in a vehicle as well as taxi 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 vehicle dispatch category (first vehicle dispatch request).

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

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

[0050] 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 the vehicle is a high-class vehicle (a so-called hire car), whether or not it is wheelchair accessible, whether or not it has sliding doors, etc. User 2 can specify the attributes of the vehicle he or she wishes to dispatch by inputting information into the vehicle attribute setting items.

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

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

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

[0054] (Vehicle extraction process S4) The vehicle dispatch unit 172 extracts one or more vehicles that satisfy predetermined extraction conditions related to the vehicle dispatch request extracted in the vehicle dispatch request extraction process S3 from among multiple vehicles that can accommodate the user 2. Here, the extraction conditions include conditions for the various setting items in the vehicle dispatch request, such as the vehicle dispatch category. When the vehicle dispatch category in the vehicle dispatch request is set to "taxi vehicles 32 only" (second vehicle dispatch request), the vehicle dispatch unit 172 extracts only taxi vehicles 32 for the vehicle dispatch request. When the vehicle dispatch category in the vehicle dispatch request is set to "taxi vehicles 32 and vehicles with requirements" (first vehicle dispatch request), the vehicle dispatch unit 172 extracts taxi vehicles 32 and vehicles with requirements for the vehicle dispatch request. Another extraction condition includes, for example, a short estimated arrival time at the boarding location. Specifically, examples of extraction conditions include that the distance between the boarding location and the current location of the vehicle is within a predetermined distance (e.g., 10 km), or that the estimated arrival time 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 (e.g., the average speed when the vehicle is operating). Furthermore, the dispatch unit 172 may further limit the number of vehicles to be extracted to a predetermined number (e.g., 10 vehicles) as an extraction condition, in order of the shortest distance between the boarding location and the current location of the vehicle or the shortest estimated arrival time at the boarding location.

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

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

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

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

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

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

[0061] (Vehicle dispatch inquiry notification processing 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 inquiry notice) indicating that the vehicle has become the target of the dispatch request 22. This dispatch inquiry notice corresponds to a question 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.

[0062] (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 the vehicle display device. When notifying the driver of this information, the vehicle terminal may also display information about the vehicle dispatch request 22 (e.g., 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 the driver accepts 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.

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

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

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

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

[0067] [1.8. Paid Vehicle Request] In the vehicle dispatch management system 1 according to this embodiment, when a vehicle dispatch request sent from a user terminal 20 to the vehicle dispatch management server 60 is a charging vehicle dispatch request, the vehicle dispatch management server 60 preferentially dispatches a vehicle of a highly rated driver who can provide high-quality driving service in response to the charging vehicle dispatch request. Therefore, first, a charging vehicle dispatch request according to this embodiment (for example, a priority vehicle dispatch request, a reserved vehicle dispatch request, a premium vehicle dispatch request, etc.) will be described in detail.

[0068] When requesting vehicle dispatch using the user terminal 20, the user 2 can select from multiple types of vehicle dispatch requests. For example, the user 2 can select either a charged vehicle dispatch request or a normal vehicle dispatch request depending on whether or not an additional fee is to be paid (charged). A charged vehicle dispatch request is a vehicle dispatch request that requires payment of an additional fee (for example, a priority vehicle dispatch fee, a reservation vehicle dispatch fee, or a premium fee, which will be described later) in addition to the basic fee. Such a charged vehicle dispatch request is a vehicle dispatch request that can increase the priority of the vehicle dispatch by charging an additional fee. On the other hand, a normal vehicle dispatch request is a vehicle dispatch request that does not require payment of the predetermined additional fee (charged). A charged vehicle dispatch request has a higher priority of vehicle dispatch in the vehicle dispatch processing by the vehicle dispatch management server 60 than a normal vehicle dispatch request. Examples of charged vehicle dispatch requests include a priority vehicle dispatch request, a reservation vehicle dispatch request, and a premium vehicle dispatch request.

[0069] The additional fee may be, for example, an additional fee added to the basic fee (e.g., at least one of the fare, basic dispatch fee, other basic fee, etc.). In this case, the additional fee (additional fee) may be a predetermined fee set separately from the basic fee. On the other hand, when the total fare is set in multiple stages, the additional fee may be the difference between the total fare for each stage. For example, if the total fare is set in three stages, namely, fare A (regular dispatch), fare B (priority dispatch), and fare C (reserved dispatch), the additional fee for the priority dispatch service may be the difference (= BA) between fare B (priority dispatch) and fare A (regular dispatch), and the additional fee for the reserved dispatch service may be the difference (= CA) between fare C (reserved dispatch) and fare A (regular dispatch). Even in this case, a user requesting priority dispatch at fare B (priority dispatch) will pay (be charged) an additional fee that is higher by the difference (= BA) than a user requesting regular dispatch at fare A (regular dispatch). Therefore, the priority vehicle allocation request corresponds to a charged vehicle allocation request that requires payment of an additional fee (charge).

[0070] (1) Priority dispatch request First, a priority vehicle dispatch request will be described. In the vehicle dispatch management system 1 according to this embodiment, the user 2 can use the priority vehicle dispatch service, for example, when he / she wants to ride during peak hours or in a congested area where demand for vehicles is greater than supply, or when he / she wants to ride in a hurry. The priority vehicle dispatch service is a service that allows the user 2 to increase the priority of vehicle dispatch over other vehicle dispatch requests by charging an additional priority vehicle dispatch fee.

[0071] A priority vehicle dispatch request is a vehicle dispatch request when User 2 uses a priority vehicle dispatch service. In other words, a priority vehicle dispatch request is a vehicle dispatch request in which User 2 charges a priority vehicle dispatch fee as an additional fee, thereby increasing the priority of vehicle dispatch compared to a normal vehicle dispatch request that does not involve charging the priority vehicle dispatch fee.

[0072] When requesting a vehicle dispatch (S1 in FIG. 7), user 2 can set the use of the priority vehicle dispatch service using the display device 124 and input device 126 of the user terminal 20. For example, as shown in FIG. 10A, when making an initial vehicle dispatch request, a setting image 300 for setting the type of vehicle dispatch request is displayed on the display device 124 of the user terminal 20. In this setting image 300, user 2 can select and set a desired vehicle dispatch request from multiple types of vehicle dispatch requests, such as "normal vehicle dispatch," "priority vehicle dispatch," and "reserved vehicle dispatch." For example, if user 2 sets "normal vehicle dispatch," the user terminal 20 transmits a normal vehicle dispatch request to the vehicle dispatch management server 60 as a vehicle dispatch request. On the other hand, if user 2 sets "priority vehicle dispatch," the user terminal 20 transmits a priority vehicle dispatch request to the vehicle dispatch management server 60 as a vehicle dispatch request.

[0073] Furthermore, when user 2 initially requests a vehicle dispatch (S1 in FIG. 7) during a peak time period or in a congested area, the vehicle dispatch management server 60 may be unable to find a vehicle available for dispatch within a short timeframe due to a shortage of available vehicles. In this case, the user terminal control unit 170 of the vehicle dispatch management server 60 notifies the user terminal 20 on the display device 124 that a vehicle cannot be arranged and displays an image promoting the use of the priority vehicle dispatch service. For example, as shown in FIG. 10B, a setting image 310 is displayed on the display device 124 of the user terminal 20 to promote the use of the priority vehicle dispatch service and to switch the type of vehicle dispatch request from "normal vehicle dispatch" to "priority vehicle dispatch." In this setting image 310, user 2 can choose to switch from "normal vehicle dispatch" to "priority vehicle dispatch" by paying an additional fee. When the user 2 requests a vehicle after switching the setting to "priority vehicle allocation," the user terminal 20 transmits a priority vehicle allocation request as a second vehicle allocation request to the vehicle allocation management server 60. As a result, the vehicle allocation management server 60 executes vehicle allocation processing (S2 to S6 in FIG. 7) so that the priority vehicle allocation request from the user terminal 20 is allocated with priority over other normal vehicle allocation requests.

[0074] As described above, by using the priority vehicle dispatch service that requires payment of an additional fee (priority vehicle dispatch fee), User 2 can have the vehicle dispatch management server 60 dispatch a vehicle to User 2's priority vehicle dispatch request earlier than vehicle dispatch requests from other Users 2. This allows User 2 to receive a prompt vehicle dispatch that is commensurate with the additional fee. This improves User 2's satisfaction, especially when dispatching a vehicle during peak hours or in a congested area.

[0075] (2) Reservation request In the vehicle dispatch management system 1 according to this embodiment, a user 2 can use a reservation vehicle dispatch service in which the user 2 specifies a desired date and time of boarding in advance. The reservation vehicle dispatch service is a service that allows the user 2 to increase the priority of vehicle dispatch over other vehicle dispatch requests by charging a reservation fee as an additional fee.

[0076] A reservation car dispatch request is a car dispatch request when user 2 uses a reservation car dispatch service. In other words, a reservation car dispatch request is a car dispatch request in which user 2 specifies a desired boarding date and time in advance and the car can be dispatched with priority over other car dispatch requests by paying an additional reservation fee. In this reservation car dispatch request, for example, it is also possible to specify a boarding location in addition to the desired boarding date and time. Note that a reservation car dispatch request means "reserving a car dispatch request" and is not "a request for a car dispatch reservation (car dispatch reservation) (car dispatch reservation request)."

[0077] When requesting a vehicle dispatch (S1 in FIG. 7), user 2 can set up the use of the reservation vehicle dispatch service using the display device 124 and input device 126 of the user terminal 20. For example, in the setting image 300 shown in FIG. 10A described above, user 2 sets "reservation vehicle dispatch," and then, on a subsequent setting screen (not shown), additional settings are made, such as the desired boarding date and time, boarding location, disembarking location, number of passengers, desired vehicle model, and desired vehicle attributes. Then, the user terminal 20 transmits a reservation vehicle dispatch request including this setting information to the vehicle dispatch management server 60 as a vehicle dispatch request. As a result, the vehicle dispatch management server 60 executes a vehicle dispatch process (S2 to S6 in FIG. 7) so that the reservation vehicle dispatch request from user 2 is dispatched with priority over other regular vehicle dispatch requests, a predetermined time before the desired boarding date and time.

[0078] As described above, by using the reservation car dispatch service that requires payment of an additional fee (reservation fee), User 2 can have the car dispatch management server 60 prioritize the reservation car dispatch request of User 2 over car dispatch requests from other Users 2 a predetermined time before the desired boarding date and time. This allows User 2 to almost certainly board the car at the reserved boarding location on the desired boarding date and time specified in the reservation car dispatch request, thereby improving User 2 satisfaction.

[0079] (3) Premium vehicle dispatch request In the vehicle dispatch management system 1 according to this embodiment, a premium vehicle dispatch service is available to the user 2. The premium vehicle dispatch service is a service that allows the user 2 to specify a premium vehicle (such as a luxury minivan taxi or hire car) by paying a premium fee as an additional fee, thereby increasing the priority of the vehicle dispatch over other vehicle dispatch requests.

[0080] A premium vehicle dispatch request is a vehicle dispatch request when using a premium vehicle dispatch service. In other words, a premium vehicle dispatch request is a vehicle dispatch request in which User 2 specifies a premium vehicle by paying a premium fee as an additional fee, and the vehicle can be dispatched with priority over other vehicle dispatch requests.

[0081] When requesting vehicle dispatch (S1 in FIG. 7), user 2 can set the use of the premium vehicle dispatch service using the display device 124 and input device 126 of the user terminal 20. For example, when user 2 sets "premium vehicle dispatch" on a predetermined setting screen (not shown) of the user terminal 20, the user terminal 20 transmits the premium request as a vehicle dispatch request to the vehicle dispatch management server 60. As a result, the vehicle dispatch management server 60 executes the vehicle dispatch process (S2 to S6 in FIG. 7) so that the premium vehicle dispatch request is dispatched with priority over other normal vehicle dispatch requests.

[0082] As described above, by User 2 using the premium vehicle dispatch service that involves the payment of an additional fee (premium fee), the vehicle dispatch management server 60 dispatches a premium vehicle to User 2's premium vehicle dispatch request more quickly and reliably than when a premium vehicle is exceptionally dispatched free of charge in response to a normal vehicle dispatch request from another User 2. This allows User 2 to receive a prompt and reliable vehicle dispatch that is commensurate with the additional fee, and also allows User 2 to enjoy a comfortable ride in the premium vehicle, greatly improving User 2's satisfaction.

[0083] [1.9. Driver evaluation criteria and vehicle dispatch processing based on driver evaluation criteria] Next, the evaluation criteria for driver driving and the vehicle dispatch process based on the evaluation criteria will be described in detail.

[0084] When the vehicle dispatch management server 60 of this embodiment executes the vehicle dispatch process (S2 to S6 in Figure 7) for a vehicle dispatch request, it distinguishes between a vehicle to be allocated for the above-mentioned paid vehicle dispatch request and a vehicle to be allocated for the above-mentioned normal vehicle dispatch request (a non-paid vehicle dispatch request) based on an evaluation criterion related to the driver's driving.

[0085] The evaluation criteria for the driver's driving (hereinafter sometimes simply referred to as "evaluation criteria") may be any evaluation criteria that can evaluate the driver's driving, and may be, for example, one or a combination of the various evaluation criteria exemplified below.

[0086] Furthermore, the evaluation criteria may be a two-stage evaluation based on whether one type of evaluation criterion (for example, driver's license criteria) is met, or a composite, multi-stage evaluation criterion based on whether multiple types of evaluation criteria (for example, driver's license criteria and driving experience criteria) are met. Even if the evaluation criteria are one type of evaluation criterion (for example, driver's license criteria), the evaluation may be a two-stage evaluation based on whether one criterion related to that one type of evaluation criterion (for example, whether or not the driver is licensed) is met, or a multi-stage evaluation of three or more stages based on multiple criteria related to that one type of evaluation criterion (for example, a first criterion related to whether or not the driver is licensed and a second criterion related to the period for which the license has been held).

[0087] In this way, by using multi-level or composite evaluation criteria, the driving service of a driver can be evaluated in detail using a variety of criteria. Therefore, the detailed evaluation of the driver can be suitably used to allocate vehicles to vehicle dispatch requests, so that vehicles of drivers who can provide appropriate driving services commensurate with the fee for the vehicle dispatch request can be allocated in detail according to the level of the vehicle dispatch request (for example, the amount or type of additional fee). Specific examples of various evaluation criteria related to driver driving are described below.

[0088] (1) Evaluation criteria for driver qualifications The driver's driving qualification may be a driver's license established by various laws or ordinances, or may be a public driving qualification established by a public organization or qualification organization, or may be a private driving qualification established by a taxi business, taxi establishment, or private company. In this embodiment, an example will be described in which the driver's driving qualification is a driver's license established by Japanese law, but is not limited to such an example. Evaluation criteria for driving qualification can be set in a variety of ways, for example, as follows.

[0089] (1a) Example 1 of the evaluation criteria for driver qualifications The evaluation (two-level evaluation) is based on the type of driver's license held by the driver, whether it is a Class 2 ordinary vehicle driver's license (for taxi drivers) or a Class 1 ordinary vehicle driver's license (for NRS drivers). <Highly rated>: When the driver has a Class 2 driver's license (Taxi Driver 3) <Medium rating>: If the driver holds a Class 1 driver's license (NRS Driver 4)

[0090] When using the above-described example 1 of the evaluation criteria for driving qualifications, in response to a request for paid vehicle dispatch, a taxi vehicle 32 of a taxi driver 3 with a "high" evaluation for driving qualifications may be preferentially allocated, and an NRS vehicle 42 of an NRS driver 4 with a "medium" evaluation may not be allocated, or the priority for allocating an NRS vehicle 42 with a "medium" evaluation may be lowered. This allows a taxi vehicle 32 of a taxi driver 3 to be preferentially dispatched in response to a request for paid vehicle dispatch. Therefore, a high-quality driving service by the taxi driver 3 can be provided to the user 2 who has made a request for paid vehicle dispatch, thereby improving the satisfaction of the user 2.

[0091] On the other hand, for a normal vehicle dispatch request, a vehicle may be allocated regardless of the driver qualification evaluation, or an NRS vehicle 42 of an NRS driver 4 with a "medium" driver qualification evaluation may be preferentially allocated. This reduces the number of taxi vehicles 32 allocated for normal vehicle dispatch requests, and allows taxi vehicles 32 to be allocated with higher priority to fee-charging vehicle dispatch requests. This increases the opportunities for a taxi driver 3 to provide high-quality driving service to a user 2 who has made a fee-charging vehicle dispatch request, thereby further improving the satisfaction of the user 2.

[0092] (1b) Example 2 of evaluation criteria for driver qualifications Evaluation (three-level evaluation) based on criteria regarding whether the driver holds a Class 2 driver's license for a regular vehicle (Criterion 1) and criteria regarding the period of time the driver has held the Class 2 driver's license (Criterion 2). <Highly Evaluated>: The driver holds a Class 2 driver's license and has held it for a specified period of time (e.g., 3 years) or more (Experienced Taxi Driver 3) <Medium rating>: The driver holds a Class 2 driver's license and has held it for less than a specified period of time (e.g., 3 years) (inexperienced taxi driver 3) <Low rating>: When the driver does not have a Class 2 driver's license but has a Class 1 driver's license (NRS Driver 4)

[0093] When using the above-described example 2 of the evaluation criteria for driving qualifications, in response to a request for paid vehicle dispatch, a taxi vehicle 32 of a taxi driver 3 whose driving qualification is evaluated as "highly rated" or "averagely rated" may be preferentially allocated, and an NRS vehicle 42 of an NRS driver 4 whose driving qualification is evaluated as "lowly rated" may not be allocated, or the priority for allocating an NRS vehicle 42 may be lowered. In this case, a taxi vehicle 32 of a taxi driver 3 whose driving qualification is evaluated as "highly rated" may be allocated with higher priority for a request for paid vehicle dispatch. This makes it possible to preferentially dispatch a taxi vehicle 32 of a taxi driver 3, particularly a taxi vehicle 32 of an experienced taxi driver 3, in response to a request for paid vehicle dispatch. Therefore, a high-quality driving service by a taxi driver 3 can be provided to a user 2 who has requested a paid vehicle dispatch, thereby improving the satisfaction of the user 2.

[0094] On the other hand, for a normal vehicle dispatch request, a vehicle may be allocated regardless of the driver's qualification evaluation, or a taxi vehicle 32 of a taxi driver 3 with a "medium evaluation" in terms of driving qualification, or an NRS vehicle 42 of an NRS driver 4 with a "low evaluation" in terms of driving qualification, may be preferentially allocated. In this case, an NRS vehicle 42 of an NRS driver 4 with a "low evaluation" may be preferentially allocated for a normal vehicle dispatch request. This reduces the number of taxi vehicles 32 allocated for normal vehicle dispatch requests, and therefore allows taxi vehicles 32 to be preferentially allocated for fee-charging vehicle dispatch requests. Therefore, it is possible to further increase the opportunities for a taxi driver 3 to provide high-quality driving service to a user 2 who has made a fee-charging vehicle dispatch request, thereby further improving the satisfaction of the user 2.

[0095] (2) Evaluation criteria for driver experience The driving experience of a driver may be the length of time that the driver has held the various driving qualifications described above, the length of time that the driver has experience driving (commercial driving) in the taxi business or NRS business, etc. (for example, the number of years of work experience), the length of driving time or the number of miles driven in commercial driving, etc. In this embodiment, an example will be described in which the driving experience of a driver is the number of years of work experience or the number of miles driven in commercial driving, but the example is not limited to this. The evaluation criteria for driving experience can be set in a variety of ways, for example, as follows.

[0096] (2a) Example 1 of the evaluation criteria for driving experience Evaluation (3-level evaluation) based on criteria (1st and 2nd criteria) of whether the driver has a specified number of years of commercial driving experience or not. <Highly Evaluated>: If the number of years of practical experience in commercial driving is equal to or greater than the number of years specified in the first standard (e.g., 10 years) (sufficiently skilled driver) <Medium evaluation>: If the number of years of practical experience in commercial driving is less than the number of years specified in the first standard (e.g., 10 years) and more than the number of years specified in the second standard (e.g., 3 years) (somewhat skilled drivers) <Low evaluation>: If the number of years of practical experience in commercial driving is less than the specified number of years (e.g., 3 years) in the second standard (inexperienced driver)

[0097] (2b) Example 2 of evaluation criteria for driving experience Evaluation (3-level evaluation) based on criteria (1st and 2nd criteria) of whether the driver's cumulative commercial driving mileage is greater than or equal to a specified distance. <Highly Evaluated>: If the cumulative mileage of commercial driving is equal to or greater than the first standard distance (e.g., 500,000 km) (sufficiently skilled driver) <Medium rating>: When the cumulative mileage of commercial driving is less than the specified distance of the first standard (e.g., 500,000 km) and more than the specified distance of the second standard (e.g., 100,000 km) (somewhat skilled driver) <Low rating>: If the cumulative driving distance of commercial driving is less than the specified distance of the second standard (e.g., 100,000 km) (inexperienced driver)

[0098] When using the above-described examples 1 and 2 of the evaluation criteria for driving experience, vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "high" or "medium" rating for driving experience may be preferentially allocated to a request for a paid vehicle dispatch, and vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "low" rating may not be allocated, or the priority for allocating vehicles of "low" drivers may be lowered. In this case, vehicles of "highly rated" drivers may be allocated with higher priority to a request for a paid vehicle dispatch. This makes it possible to preferentially allocate vehicles of drivers with experienced practical experience, particularly vehicles of sufficiently experienced drivers, to a request for a paid vehicle dispatch. Therefore, a high-quality driving service by an experienced driver can be provided to a user 2 who has requested a paid vehicle dispatch, thereby improving the satisfaction of the user 2.

[0099] On the other hand, for a normal vehicle dispatch request, a vehicle may be assigned regardless of the driver's driving experience rating, or vehicles of drivers with a "medium" or "low" driving experience rating may be preferentially assigned. In this case, vehicles of "low" drivers may be preferentially assigned to a normal vehicle dispatch request. This reduces the number of vehicles of "highly" and "medium" drivers assigned to a normal vehicle dispatch request, so that vehicles of "highly" and "medium" drivers can be preferentially assigned to a paid vehicle dispatch request. Therefore, it is possible to further increase the opportunities for a user 2 who has made a paid vehicle dispatch request to receive high-quality driving service from a driver with skilled practical experience, thereby further improving the satisfaction of the user 2.

[0100] (3) Evaluation criteria for driver training received by the driver The driving education received by the driver may be, for example, a history of attending courses (practical or classroom) on educational items such as driving techniques, traffic laws or manners, and customer service in the taxi business or NRS business, or may be the number of credits acquired in the course or test results. In this embodiment, an example will be described in which the driving education is a history of attending the various courses, but the example is not limited to this. Evaluation criteria for driving education can be set in a variety of ways, for example, as follows.

[0101] (3a) Example 1 of evaluation criteria for driver education Evaluation (two-level evaluation) based on the criterion (first criterion) of whether or not the driver has received driving education. <Highly Evaluated>: If you have taken beginner to advanced courses on driving skills and customer service (well-trained driver) <Medium rating>: Drivers who have attended beginner to intermediate courses on driving skills and customer service, but have not attended advanced courses (drivers with some training)

[0102] When using the above-described example 1 of the evaluation criteria for driving education, in response to a request for a paid vehicle dispatch, vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "high" rating for driving education may be preferentially allocated, and vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "medium" rating may not be allocated, or the priority for allocating vehicles of "medium" drivers may be lowered. This allows vehicles of drivers who have received driving education, particularly vehicles of drivers who have received sufficient driving education, to be preferentially allocated in response to a request for a paid vehicle dispatch. Therefore, high-quality driving service and customer service by drivers who have received driving education can be provided to user 2 who has made a request for a paid vehicle dispatch, thereby improving the satisfaction of user 2.

[0103] On the other hand, for a normal vehicle dispatch request, a vehicle may be assigned regardless of the driver's education rating, or vehicles of drivers with a "medium" driver education rating may be preferentially assigned. This reduces the number of vehicles of "highly rated" drivers assigned to a normal vehicle dispatch request, and allows vehicles of "highly rated" drivers to be preferentially assigned to a fee-charging vehicle dispatch request. Therefore, it is possible to further increase the opportunities for users 2 who have made fee-charging vehicle dispatch requests to receive high-quality driving and customer service from drivers who have received driving education, thereby further improving the satisfaction of users 2.

[0104] (3b) Example 2 of evaluation criteria for driver education The evaluation (three-level evaluation) is based on the first criterion of whether the driver has received driver's education, and the second criterion of the number of credits earned in driver's education courses. <Highly Evaluated>: If you have attended beginner to advanced courses on driving skills and customer service, and have acquired more than the first predetermined number of credits (for example, 100 credits) (a well-trained driver) <Medium evaluation>: If you have attended beginner to intermediate courses on driving skills and customer service, and have acquired more than the second predetermined number of credits (for example, 50 credits) (a driver with some training) <Low rating>: Drivers who have taken beginner courses on driving skills and customer service, but have not taken intermediate to advanced courses (new drivers who are still undergoing training)

[0105] When using the above-described example 2 of the evaluation criteria for driver education, vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "high" or "average" rating for driver education may be preferentially allocated to a request for a paid vehicle dispatch, while vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "low" rating may not be allocated, or the priority for allocating vehicles of "low" drivers may be lowered. In this case, vehicles of "highly rated" drivers may be allocated with higher priority to a request for a paid vehicle dispatch. This allows vehicles of drivers who have received driver education, particularly vehicles of drivers who have received sufficient driver education, to be preferentially dispatched to a request for a paid vehicle dispatch. Therefore, high-quality driving service and customer service by drivers who have received driver education can be provided to a user 2 who has made a request for a paid vehicle dispatch, thereby improving the satisfaction of the user 2.

[0106] On the other hand, for a normal vehicle dispatch request, a vehicle may be assigned regardless of the driver's education rating, or vehicles of drivers with a "medium" or "low" driver education rating may be assigned preferentially. In this case, vehicles of "low" drivers may be assigned preferentially to a normal vehicle dispatch request. This reduces the number of vehicles of "highly" and "medium" drivers assigned to a normal vehicle dispatch request, so that vehicles of "highly" and "medium" drivers can be assigned preferentially to a paid vehicle dispatch request. Therefore, it is possible to further increase the opportunities for users 2 who have made paid vehicle dispatch requests to receive high-quality driving and customer service from drivers who have received driving education, thereby further improving the satisfaction of the users 2.

[0107] (4) Evaluation criteria for the driver's traffic violation and traffic accident history The driver may be evaluated based on either or both of the driver's traffic violation history and the driver's traffic accident history. The evaluation criteria regarding the driver's traffic violation history or the driver's traffic accident history can be set in various ways, for example, as follows.

[0108] (4a) Example 1 of evaluation criteria for traffic violation and traffic accident history Evaluation (3-level rating) based on the driver's traffic violation history (first criterion) and traffic accident history (second criterion). <Highly rated>: If you have never committed a traffic violation or caused a traffic accident during your previous commercial driving (good driver) <Medium rating>: No serious traffic violations or traffic accidents in the past three years, and fewer than three minor traffic violations (good driver) <Low rating>: If you have committed at least one of a serious traffic violation and a traffic accident in the past three years, or if you have committed three or more minor traffic violations (passable driver)

[0109] When using the above-described example of evaluation criteria regarding drivers' traffic violation and accident histories, vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of excellent drivers with a "high rating" may be preferentially allocated to a request for a paid vehicle dispatch, while vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "low rating" may not be allocated, and vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "medium rating" may not be allocated, or the priority for allocating vehicles of "medium rating" drivers may be lowered. In this case, vehicles of "highly rated" drivers may be allocated with higher priority to a paid vehicle dispatch request. This allows vehicles of excellent drivers with no history of traffic violations or accidents to be preferentially allocated to a paid vehicle dispatch request. Therefore, a safe driving service by an excellent driver can be provided to the user 2 who has requested a paid vehicle dispatch, thereby improving the satisfaction of the user 2.

[0110] On the other hand, for normal vehicle dispatch requests, vehicles may be assigned regardless of the driver's evaluation of traffic violation history or traffic accident history, or vehicles of drivers with a "medium evaluation" or "low evaluation" may be preferentially assigned. In this case, vehicles of drivers with a "low evaluation" may be preferentially assigned to normal vehicle dispatch requests. This reduces the number of vehicles of "highly rated" excellent drivers assigned to normal vehicle dispatch requests, so that vehicles of "highly rated" excellent drivers can be preferentially assigned to paid vehicle dispatch requests. Therefore, it is possible to further increase the opportunities to provide safe driving services by excellent drivers to users 2 who have made paid vehicle dispatch requests, thereby further improving the satisfaction of users 2.

[0111] (5) Evaluation criteria for user driver ratings A user 2 using the vehicle dispatch management system 1 according to this embodiment can enter an evaluation of the driver's driving service, for example, on a user evaluation input screen of a user application on the user terminal 20 or on an evaluation site of the vehicle dispatch management system 1. The driver evaluation entered by the user 2 in this manner is useful as an index for evaluating the actual driving service, for example, of each driver. Such a user's evaluation of the driver (hereinafter sometimes referred to as a "user evaluation") may be, for example, a numerical evaluation score for predetermined evaluation items such as careful driving, text information describing impressions of the driver's driving service, or the presence or absence of complaints from the user. In this embodiment, an example will be described in which the user evaluation is a numerical evaluation score for predetermined evaluation items (hereinafter sometimes referred to as a "user evaluation score"), but this is not limited to this example. Evaluation criteria for driving experience can be set in a variety of ways, for example, as follows:

[0112] (5a) Example 1 of evaluation criteria for user evaluation of drivers Evaluation (3-level evaluation) based on criteria (first and second criteria) of whether the driver's user evaluation score is above a predetermined value. <Highly Rated>: When the user evaluation score is equal to or greater than the specified value of the first criterion (for example, 3.5 or more out of 5 points) (highly rated driver) <Medium rating>: When the user rating score is less than the specified value of the first criterion (e.g., less than 3.5 / 5 points) and greater than or equal to the specified value of the second criterion (e.g., 2.5 or greater / 5 points) (medium rating driver) <Low Rating>: When the user rating score is less than the specified value of the second standard (for example, less than 2.5 / 5 points) (low rating driver)

[0113] (5b) Example 2 of evaluation criteria for user evaluation of drivers The evaluation (3-level evaluation) is based on the criterion of whether the driver's user evaluation score is equal to or greater than a predetermined value (first criterion) and whether there are any complaints from user 2 (second criterion). <Highly Rated>: The user evaluation score is above a predetermined value (for example, 3.0 or above / out of 5 points) and there have been no complaints from User 2 in the past (highly rated driver) <Medium rating>: The user rating score is below a predetermined value (for example, below 3.0 / 5 points), but there has never been a complaint from User 2 in the past (medium rating driver). <Low Rating>: The user rating score is below a certain value (for example, below 3.0 / 5 points) and there has been a complaint from User 2 in the past (low-rated driver).

[0114] When using the above-described example of evaluation criteria related to user ratings, for a fee-charging vehicle dispatch request, vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with "high" or "average" user ratings may be preferentially allocated, and vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with "low" ratings may not be allocated, or the priority for allocating vehicles of "low" drivers may be lowered. In this case, vehicles of "highly rated" drivers may be allocated with higher priority for a fee-charging vehicle dispatch request. This makes it possible to preferentially dispatch vehicles of drivers with high user ratings, especially vehicles of highly rated drivers, for a fee-charging vehicle dispatch request. Therefore, a user 2 who has made a fee-charging vehicle dispatch request can be provided with high-quality driving service and customer service by a driver with a high user rating, thereby improving the satisfaction of the user 2.

[0115] On the other hand, for normal vehicle dispatch requests, vehicles may be assigned regardless of user ratings, or vehicles of drivers with "average" or "low" user ratings may be assigned preferentially. In this case, vehicles of "low" drivers may be assigned preferentially to normal vehicle dispatch requests. This reduces the number of vehicles of "highly" and "average" drivers assigned to normal vehicle dispatch requests, so vehicles of "highly" and "average" drivers can be assigned preferentially to paid vehicle dispatch requests. Therefore, it is possible to further increase opportunities for users 2 who have made paid vehicle dispatch requests to receive high-quality driving and customer service from drivers with high user ratings, thereby further improving the satisfaction of users 2.

[0116] (6) Evaluation criteria for the driver's driving score calculated by the driving analysis software Driving analysis software (not shown) is installed on the vehicle dispatch management server 60 or the business operator server 50 of the vehicle dispatch management system 1 according to this embodiment. The driving analysis software records and analyzes the driver's driving behavior during commercial driving based on various information related to the driver's driving, and calculates the driver's driving score. Here, the various information related to the driver's driving includes, for example, images of the vehicle's surroundings taken while driving by a drive recorder or camera mounted on the vehicle, images of the driver inside the vehicle, vehicle position information obtained from a navigation device, and information on driver operations such as accelerator, brake, and steering obtained from a vehicle control device.

[0117] Driving behaviors include those associated with high-risk driving, those associated with safe driving that allows passengers to ride comfortably and without anxiety, and normal driving behaviors. Driving analysis software can identify risky driving by analyzing each driver's driving behavior. Examples of risky driving include sudden acceleration / deceleration, inattentive driving, drowsy driving, insufficient following distance, inattention to the road ahead, inattention when turning, ignoring traffic signals, and the presence or absence of warnings for high-risk or emergency driving (forward collision warning, following distance warning, inattentive driving warning, etc.).

[0118] Furthermore, based on the driving route history acquired from a navigation device, etc., the driving analysis software can also analyze and evaluate whether the driver's vehicle is driving according to a predetermined route, whether it is driving an efficient route, whether it is picking up passengers at the destination as reported, etc. In addition to the above driving behavior, the driving analysis software can also reflect evaluations of these driving routes in the driving score.

[0119] The driving score of a driver calculated by such driving analysis software is useful as an index for objectively evaluating each driver's actual driving situation, driving service, etc. Evaluation criteria for the driving score can be set in a variety of ways, for example, as follows.

[0120] (6a) Example 1 of the evaluation criteria for the driver's driving score Evaluation (3-level evaluation) based on criteria (1st and 2nd criteria) of whether the driver's driving score is above a specified value. <Highly Evaluated>: If the driving score is above the specified value of the first standard (for example, 80 points or more out of 100 points) (Highly Evaluated Driver) <Medium rating>: When the driving score is below a specified value of the first standard (e.g., below 80 points) and above a specified value of the second standard (e.g., 50 points or above) (medium rating driver) <Low Rating>: When the driving score is less than the specified value of the second standard (for example, less than 50 points) (low rating driver)

[0121] (6b) Example 2 of the evaluation criteria for the driver's driving score The evaluation (three-level evaluation) is based on the criteria of whether the driving score is above a certain value (first criteria) and whether or not the driver engaged in risky driving as described above (second criteria). <Highly Evaluated>: The driving score is above a certain value (for example, 70 points or more out of 100 points) and there has never been any risky driving in the past (highly rated driver) <Medium rating>: The driving score is below a certain value (for example, below 70 points), but there has never been any risky driving in the past (medium rating driver) <Low Rating>: If the driving score is below a certain value (e.g., below 70) and there is a history of risky driving (low-rated driver)

[0122] When using the above-described examples 1 and 2 of the evaluation criteria for driving scores, vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with "highly rated" or "average" driving scores may be preferentially allocated to a paid vehicle dispatch request, and vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with "lowly rated" driving scores may not be allocated, or the priority for allocating vehicles of "lowly rated" drivers may be lowered. In this case, vehicles of "highly rated" drivers may be allocated with higher priority to a paid vehicle dispatch request. This makes it possible to preferentially dispatch vehicles of drivers with high driving scores, particularly vehicles of highly rated drivers with very high driving scores, to a paid vehicle dispatch request. Therefore, a safe driving service provided by a driver with a high driving score can be provided to a user 2 who has made a paid vehicle dispatch request, thereby improving the satisfaction and sense of security of the user 2.

[0123] On the other hand, for a normal vehicle dispatch request, a vehicle may be assigned regardless of the driving score evaluation, or vehicles of drivers with a driving score of "average" or "low" may be preferentially assigned. In this case, vehicles of "low" drivers may be preferentially assigned to a normal vehicle dispatch request. This reduces the number of vehicles of "highly" and "average" drivers assigned to a normal vehicle dispatch request, so that vehicles of "highly" and "average" drivers can be preferentially assigned to a paid vehicle dispatch request. Therefore, it is possible to further increase the opportunities for a user 2 who has made a paid vehicle dispatch request to receive a safe driving service from a driver with a high driving score, thereby further improving the satisfaction and sense of security of the user 2.

[0124] [1.10. Chargeable vehicle dispatch request and vehicle dispatch processing based on evaluation criteria] Next, with reference to FIG. 7 mentioned above, a supplementary explanation will be given of the vehicle allocation process (S2 to S6) for allocating a vehicle in response to a charging vehicle allocation request based on the driver evaluation criteria, which is a feature of this embodiment.

[0125] As shown in FIG. 7, first, when user 2 wishes to use the priority vehicle dispatch service, user 2 selects "priority vehicle dispatch" from among multiple types of vehicle dispatch requests by inputting information into user terminal 20 (see FIG. 10A) and requests a vehicle dispatch. Then, vehicle dispatch request unit 180 of user terminal 20 transmits the priority vehicle dispatch request as a vehicle dispatch request to vehicle dispatch management server 60 (S1). Also, when user 2 wishes to use the reservation vehicle dispatch service, user 2 selects "reservation vehicle dispatch" from among multiple types of vehicle dispatch requests by inputting information into user terminal 20 and requests a vehicle dispatch (see FIG. 10A). Then, vehicle dispatch request unit 180 of user terminal 20 transmits a reservation vehicle dispatch request as a vehicle dispatch request to vehicle dispatch management server 60 (S1). These priority vehicle dispatch requests and reservation vehicle dispatch requests are charged vehicle dispatch requests that involve the charging of an additional fee.

[0126] Next, when the vehicle allocation unit 172 of the vehicle allocation management server 60 receives a vehicle allocation request from the user terminal 20, it executes the above-mentioned vehicle allocation process (S2 to S6 in FIG. 7). Based on whether the vehicle allocation request received from the user terminal 20 is a charging vehicle allocation request, the vehicle allocation unit 172 executes vehicle allocation process to simultaneously allocate multiple vehicles to multiple vehicle allocation requests including the vehicle allocation request.

[0127] Here, if the vehicle dispatch request received from the user terminal 20 is a reservation vehicle dispatch request, the vehicle dispatch unit 172 does not yet execute vehicle dispatch processing at the time of receiving the reservation vehicle dispatch request. Thereafter, a predetermined time (e.g., 5 minutes) before the desired boarding date and time specified in the reservation vehicle dispatch request, the vehicle dispatch unit 172 preferentially allocates a vehicle to the reservation vehicle dispatch request, separately from other regular vehicle dispatch requests stored in the storage device 164. At this time, for the reservation vehicle dispatch request, a vehicle that satisfies the conditions specified in the reservation vehicle dispatch request and is close to the reserved boarding location and is driven by a highly rated driver or an average rated driver, preferably a vehicle driven by a highly rated driver, is preferentially allocated. On the other hand, for other regular vehicle dispatch requests, a vehicle is allocated by matching a pair group with the shortest total estimated arrival time using, for example, the above-mentioned vehicle search process (S2 to S6). As a result, a reservation vehicle dispatch request that requires an additional fee is preferentially dispatched over other regular vehicle dispatch requests. Furthermore, as described above, in response to a reservation request for a vehicle from User 2, a vehicle near the boarding location is dispatched immediately before the desired boarding date and time, thereby enabling efficient vehicle dispatch without the vehicle to be dispatched wasting time waiting at the boarding location or driving a long distance unnecessarily to pick up the passenger.

[0128] Furthermore, if the vehicle allocation request received from the user terminal 20 is a priority vehicle allocation request, the vehicle allocation unit 172 preferentially allocates a vehicle to the priority vehicle allocation request. Specifically, the vehicle allocation unit 172 preferentially allocates a vehicle to the priority vehicle allocation request, separate from other normal vehicle allocation requests stored in the storage device 164. At this time, for the priority vehicle allocation request, a vehicle that satisfies the conditions specified in the priority vehicle allocation request, is preferentially allocated to a vehicle that is close to the boarding location of the user 2 and is driven by a highly or averagely rated driver, preferably a vehicle driven by a highly rated driver. On the other hand, for other normal vehicle allocation requests, a vehicle is allocated by matching a pair group with the shortest total estimated arrival time using the above-mentioned vehicle search process (S2 to S6). Furthermore, for example, for a priority vehicle allocation request, a process such as expanding the search range for candidate vehicles may be performed, and the search process may be continued until a candidate vehicle is found, thereby preferentially allocating a vehicle. As a result, a priority vehicle allocation request that requires an additional fee is preferentially allocated over other normal vehicle allocation requests.

[0129] Next, a description will be given of the vehicle allocation process based on the evaluation criteria relating to the driving of the driver, which is a feature of this embodiment.

[0130] In the vehicle dispatch processing (S2 to S6) of this embodiment, when the vehicle dispatch unit 172 of the vehicle dispatch management server 60 receives a vehicle dispatch request from the user terminal 20, it assigns a vehicle to the vehicle dispatch request received from the user terminal 20 based on the evaluation criteria related to the driver's driving described above.

[0131] In this characteristic vehicle allocation process (S2 to S6), when the vehicle allocation request received from the user terminal 20 is a charging vehicle allocation request (for example, a priority vehicle allocation request or a reservation vehicle allocation request), the vehicle allocation unit 172 allocates a vehicle of a driver who satisfies the above-mentioned driving-related evaluation criteria to the charging vehicle allocation request. At this time, it is preferable that the vehicle allocation unit 172 does not allocate a vehicle of a driver who does not satisfy the evaluation criteria to the charging vehicle allocation request, or lowers the priority of allocating a vehicle of a driver who does not satisfy the evaluation criteria compared to the priority of allocating a vehicle of a driver who satisfies the evaluation criteria.

[0132] On the other hand, if the vehicle dispatch request received from the user terminal 20 is not a billing vehicle dispatch request, for example, if it is the above-mentioned normal vehicle dispatch request, the vehicle dispatch unit 172 allocates a vehicle to the normal vehicle dispatch request regardless of the above-mentioned evaluation criteria. In this case, the vehicle dispatch unit 172 may preferentially allocate a vehicle of a driver who does not satisfy the above-mentioned evaluation criteria to the normal vehicle dispatch request, or may increase the priority of allocating a vehicle of a driver who does not satisfy the evaluation criteria above the priority of allocating a vehicle of a driver who satisfies the evaluation criteria.

[0133] This vehicle allocation process (S2 to S6) allows vehicles with highly rated drivers to be preferentially allocated in response to a request for paid vehicle allocation. Therefore, a high-quality driving service from a highly rated driver can be provided to a user 2 who has requested a paid vehicle allocation in exchange for paying an additional fee. Therefore, the user 2 who has paid the additional fee will be more satisfied with the cost-effectiveness of the vehicle allocation.

[0134] 9 and 11, a specific example of the vehicle allocation process (S2 to S6) based on the driver evaluation criteria according to this embodiment will be described. FIG. 9 shows the result of vehicle allocation when all of the vehicle allocation requests 22a to 22d are normal vehicle allocation requests, and FIG. 11 shows the result of vehicle allocation when, among the vehicle allocation requests 22a to 22d, only the vehicle allocation request 22c is a priority vehicle allocation request, and the other vehicle allocation requests 22a, 22b, and 22d are normal vehicle allocation requests. In the case of FIG. 11, the driver evaluation criteria used as the basis for vehicle allocation process for a charged vehicle allocation request are, for example, the criteria related to the driving qualifications described above, and specifically, the criteria are whether the driver has a Class 2 driver's license, as described in "(1a) Example 1 of Evaluation Criteria Related to Driving Qualifications" above.

[0135] 9, when all of the vehicle dispatch requests 22a to 22d from users 2a to 2d are normal vehicle dispatch requests, vehicles 42b, 32h, 42i, and 32d are assigned to the vehicle dispatch requests 22a to 22d, respectively, and are determined as the vehicles to be dispatched. In this case, vehicles 42b, 32h, 42i, and 32d are determined as the vehicles to be dispatched so that the sum of the distances between each of users 2a to 2d and vehicles 42b, 32h, 42i, and 32d is minimized. In this case, NRS vehicle 42i, which is closest to user 2c, is determined as the vehicle to be dispatched for vehicle dispatch request 22c.

[0136] In contrast, as shown in Figure 11, if only vehicle dispatch request 22c among vehicle dispatch requests 22a to 22d is a priority vehicle dispatch request, NRS vehicle 42i is not assigned to priority vehicle dispatch request 22c, and taxi vehicle 32e, which is closest to user 2c among taxi vehicles 32, is assigned and becomes the vehicle to be dispatched for vehicle dispatch request 22c.

[0137] The reason for this is that in the vehicle dispatch process according to this embodiment, vehicle dispatch is performed based on the above-mentioned "(1a) Evaluation criteria related to the driver's driving qualifications," so that a taxi vehicle 32 is assigned to the priority vehicle dispatch request 22c, rather than an NRS vehicle 42. Since the user 2c who made the priority vehicle dispatch request 22c has paid a priority vehicle dispatch fee as an additional fee, it is desirable to provide the user 2c with a high-quality driving service in return for the additional fee.

[0138] Therefore, in this embodiment, the NRS vehicle 42i, which is the closest vehicle to the user 2c, is excluded from the vehicles to be dispatched in the priority dispatch request 22c of the user 2c, and the taxi vehicle 32e, which is the second closest vehicle to the user 2c, is selected. As a result, a high-quality driving service can be provided to the user 2c by the taxi driver 3 of the taxi vehicle 32e, and the satisfaction of the user 2c can be improved.

[0139] [1.11. Summary of the First Embodiment] (1) As described above, according to the first embodiment, a vehicle dispatch management system 1 is provided that includes a plurality of user terminals 20 and a vehicle dispatch management device (e.g., a vehicle dispatch management server 60) communicatively connected to the user terminals 20 via a network 6, wherein the user terminals 20 include one or more first processors (e.g., a processor of the processing device 122), and the vehicle dispatch management device includes one or more second processors (e.g., a processor of the processing device 162), and the first processor of the user terminal 20 executes a process of sending a vehicle dispatch request to the vehicle dispatch management device in response to input from a user 2, and the second processor of the vehicle dispatch management device executes a vehicle dispatch process (S2 to S6) that allocates a vehicle to the vehicle dispatch request received from the user terminal 20 based on evaluation criteria related to the driver's driving, and in the vehicle dispatch process, if the vehicle dispatch request is a charging vehicle dispatch request that increases the priority of the vehicle by charging an additional fee, a vehicle of a driver who meets the evaluation criteria is allocated to the charging vehicle dispatch request.

[0140] With this configuration, a vehicle with a driver who can provide high-quality driving service can be dispatched in response to a request for paid vehicle dispatch that involves the payment of an additional fee. Therefore, high-quality driving service can be provided in return for the additional fee paid by User 2, thereby improving User 2's satisfaction with the cost-effectiveness of the vehicle dispatch service.

[0141] (2) Also, according to this embodiment, there is provided a vehicle dispatch management device (e.g., vehicle dispatch management server 60) communicatively connected to user terminal 20 via network 6, the vehicle dispatch management device having one or more processors (e.g., processor of processing device 162), the processor executes a vehicle dispatch process (S2 to S6) that allocates a vehicle to a vehicle dispatch request received from user terminal 20 based on evaluation criteria related to the driver's driving, and in the vehicle dispatch process, when the vehicle dispatch request is a charging vehicle dispatch request that increases the priority of the vehicle dispatch by charging an additional fee, a vehicle of a driver who meets the evaluation criteria is allocated to the charging vehicle dispatch request.

[0142] With this configuration, it is possible to dispatch a vehicle of a highly rated driver who can provide high-quality driving service in response to a request for vehicle dispatch that involves an additional fee. Therefore, in return for the additional fee paid by User 2, high-quality driving service can be provided, thereby improving User 2's satisfaction with the cost-effectiveness of the vehicle dispatch service.

[0143] (3) Furthermore, in the above-described vehicle dispatch process, if the vehicle dispatch request is a paid vehicle dispatch request, a vehicle of a driver who does not meet the evaluation criteria may not be allocated to the paid vehicle dispatch request, or the allocation priority of the vehicle may be lowered. With this configuration, a vehicle of a driver with a relatively low evaluation may not be dispatched to a paid vehicle dispatch request that involves an additional fee, or the rate at which vehicles of such drivers are dispatched may be reduced. This reduces the number of cases in which a relatively low-quality driving service is provided to a user 2 who has paid an additional fee, thereby preventing a decrease in user 2's satisfaction with the cost-effectiveness of the vehicle dispatch service.

[0144] (4) Furthermore, in the above-described vehicle dispatch process, if the vehicle dispatch request is not a fee-charging vehicle dispatch request, a vehicle may be assigned to the vehicle dispatch request regardless of the evaluation criteria. With this configuration, vehicles of highly rated drivers who can provide high-quality driving service are less likely to be assigned to vehicle dispatch requests that are not fee-charging vehicle dispatch requests, and vehicles of highly rated drivers are more likely to be assigned to fee-charging vehicle dispatch requests. Therefore, the probability of providing high-quality driving service to user 2 who has made a fee-charging vehicle dispatch request can be further increased, thereby further improving the satisfaction of user 2.

[0145] (5) The evaluation criteria may also include criteria related to the driver's driving qualifications. With this configuration, in response to a request for paid vehicle dispatch, a taxi vehicle 32 operated by a taxi driver 3 or a vehicle operated by a qualified, experienced driver can be preferentially dispatched. Therefore, a high-quality driving service by a taxi driver 3 or an experienced driver can be provided to a user 2 who has made a request for paid vehicle dispatch, thereby further improving the satisfaction of the user 2.

[0146] (6) The evaluation criteria may also include at least one of the following criteria: the driver's driving experience, the driver's driving education, the driver's traffic violation history, the user's evaluation of the driver, and the driver's driving score calculated by driving analysis software. This configuration allows vehicles driven by drivers who are highly rated based on these various evaluation criteria to be preferentially dispatched in response to a paid vehicle dispatch request. Therefore, a high-quality driving service provided by a highly rated driver can be provided to a user 2 who has requested a paid vehicle dispatch, further improving the satisfaction of the user 2.

[0147] (7) The charged vehicle dispatch request may also include a priority vehicle dispatch request that, by charging an additional fee, increases the priority of the vehicle dispatch over a normal vehicle dispatch request that does not involve an additional fee. With this configuration, a vehicle of a driver who can provide high-quality driving service can be dispatched in response to a priority vehicle dispatch request that involves the payment of an additional fee. Therefore, in return for the priority vehicle dispatch fee paid by User 2, high-quality driving service can be provided, thereby improving User 2's satisfaction with the cost-effectiveness of the priority vehicle dispatch service.

[0148] (8) The above-mentioned paid vehicle dispatch request may include a reservation request in which the desired ride date and time can be specified in advance by charging an additional fee. With this configuration, a vehicle with a driver who can provide high-quality driving service can be dispatched in response to a reservation request that requires payment of an additional fee. Therefore, high-quality driving service can be provided in exchange for the reservation fee paid by User 2, thereby improving User 2's satisfaction with the cost-effectiveness of the reservation vehicle dispatch service.

[0149] (9) Furthermore, according to this embodiment, a vehicle dispatch management method executed by a computer is provided, which includes a vehicle dispatch process (S2 to S6) for allocating a vehicle to a vehicle dispatch request received from a user terminal 20 based on evaluation criteria related to the driver's driving, and in the vehicle dispatch process, when the vehicle dispatch request is a charged vehicle dispatch request that increases the priority of the vehicle dispatch by charging an additional fee, a vehicle of a driver who meets the evaluation criteria is allocated to the charged vehicle dispatch request.

[0150] With this configuration, a vehicle with a driver who can provide high-quality driving service can be dispatched in response to a request for vehicle dispatch that involves an additional fee. Therefore, in return for the additional fee paid by User 2, high-quality driving service can be provided, thereby improving User 2's satisfaction with the cost-effectiveness of the vehicle dispatch service.

[0151] (10) Furthermore, according to this embodiment, a program is provided for causing a computer (e.g., the vehicle dispatch management server 60) to execute a vehicle dispatch process (S2 to S6) for allocating a vehicle to a vehicle dispatch request received from the user terminal 20 based on evaluation criteria related to the driver's driving. In the vehicle dispatch process, when the vehicle dispatch request is a charging vehicle dispatch request that increases the priority of the vehicle dispatch by charging an additional fee, a program (e.g., a vehicle dispatch unit 172 installed in the processing device 162 of the vehicle dispatch management server 60) is provided for allocating a vehicle of a driver who meets the evaluation criteria to the charging vehicle dispatch request.

[0152] With this configuration, a vehicle with a driver who can provide high-quality driving service can be dispatched in response to a request for vehicle dispatch that involves an additional fee. Therefore, in return for the additional fee paid by User 2, high-quality driving service can be provided, thereby improving User 2's satisfaction with the cost-effectiveness of the vehicle dispatch service.

[0153] [2. Second Embodiment] Next, a vehicle dispatch management system 1 according to a second embodiment of the present invention will be described. The vehicle dispatch management system 1 according to the second embodiment performs a vehicle dispatch process that adjusts the vehicle to be assigned to a user's vehicle dispatch request based on evaluation criteria related to the driver's driving when redistributing a vehicle in the event that the first vehicle dispatch is canceled for some reason. In this case, the vehicle dispatch management system 1 according to the second embodiment is characterized in that, when redistributing a vehicle in response to a user's vehicle dispatch request, it preferentially dispatches a vehicle of a highly rated driver who can provide high-quality driving service in response to the vehicle dispatch request. The configuration of the vehicle dispatch management system 1 and the like, the vehicle dispatch management method, the evaluation criteria related to the driver's driving, and the vehicle redistribution process using the evaluation criteria that are required to realize such characteristics will be described below in order.

[0154] [2.1. Configuration of vehicle dispatch management system, etc.] The configuration of the vehicle dispatch management system 1 according to the second embodiment and each device provided in the vehicle dispatch management system 1 is substantially the same as the configuration of the vehicle dispatch management system 1 according to the first embodiment described above and each device (see Figures 1 to 6), so a detailed explanation of the configuration will be omitted (see [1.1. Configuration of the vehicle dispatch management system], [1.2. Configuration of the user terminal], [1.3. Configuration of the taxi terminal], [1.4. Configuration of the NRS terminal], [1.5. Configuration of the operator server] and [1.6. Configuration of the vehicle dispatch management server] described above).

[0155] [2.2. Vehicle allocation management method] Next, a vehicle allocation management method by the vehicle allocation management system 1 according to the second embodiment will be described with reference to Fig. 12. Fig. 12 is a sequence diagram showing the processing flow of the vehicle allocation management method by the vehicle allocation management system 1 according to the second embodiment.

[0156] As shown in FIG. 12, the vehicle allocation request method according to the second embodiment includes a vehicle allocation request process (S1), a vehicle allocation request accumulation process (S2), a vehicle allocation request extraction process (S3), a vehicle extraction process (S4), a pair generation process (S5), a matching process (S6), a vehicle allocation inquiry notification process (S7), an acceptance response process (S8), and a vehicle allocation completion notification process (S9, S10).

[0157] In the vehicle allocation process (S2 to S6), the vehicle allocation unit 172 of the vehicle allocation management server 60 allocates one vehicle to be allocated selected from a plurality of vehicles in response to the vehicle allocation request 22 received from the user terminal 20 of the user 2. Here, it is assumed that the vehicle of driver A (taxi driver 3 or NRS driver 4) is the vehicle to be allocated in response to the vehicle allocation request 22.

[0158] In the dispatch inquiry notification process (S7), the vehicle terminal control unit 174 of the dispatch management server 60 sends a dispatch inquiry notification to the vehicle terminal (taxi terminal 30 or NRS terminal 40) of driver A's vehicle (vehicle to be dispatched) indicating an inquiry regarding acceptance of the dispatch request 22 (S7).

[0159] In the acceptance response process (S8), when the vehicle terminal of driver A's vehicle to be allocated receives the vehicle allocation inquiry notice (S7) from the vehicle allocation management server 60, it replies with an acceptance response to the vehicle allocation management server 60 in accordance with the input of driver A. Specifically, the vehicle allocation response unit of driver A's vehicle terminal transmits an acceptance response representing acceptance of the vehicle allocation request 22 to the vehicle allocation management server 60 as a response to the vehicle allocation inquiry notice (S7) in accordance with the input of driver A of the vehicle to be allocated (S8).

[0160] In the vehicle dispatch completion notification process (S9, S10), first, when the vehicle dispatch management server 60 receives an acceptance response (S8) from the vehicle terminal of the vehicle to be dispatched of driver A, it confirms the dispatch of a vehicle in response to user 2's dispatch request 22. Then, the user terminal control unit 170 and vehicle terminal control unit 174 of the vehicle dispatch management server 60 send a vehicle dispatch completion notification to the vehicle terminal of driver A's vehicle to be dispatched and the user terminal 20 of user 2, respectively (S9, S10).

[0161] Each of these processes (S1 to S10) of the vehicle dispatch request method according to the second embodiment is substantially identical to each of the processes of the vehicle dispatch management method according to the first embodiment described above (see S1 to S10 in Figure 7), so a detailed description of the configuration will be omitted (see [1.7. Vehicle dispatch management method] described above).

[0162] Furthermore, as shown in FIG. 12, the vehicle allocation request method according to the second embodiment includes a cancellation notification process (S11), a cancellation report process (S12), a re-allocation instruction process (S13), a re-allocation process (S22 to S26), a re-allocation inquiry notification process (S27), an acceptance response process (S28), and a re-allocation completion notification process (S29, S30).

[0163] (Cancellation notification processing S11) After the dispatch is confirmed in the dispatch completion notification process (S9, S10), driver A, who accepted the dispatch request 22 in S8, may intentionally cancel the dispatch of the dispatch request 22 that he accepted for various reasons. Possible reasons for the driver to cancel include, for example, the following cases:

[0164] - If the vehicle to be dispatched cannot reach the pickup location specified in the dispatch request 22 due to road conditions (for example, traffic congestion, road construction, bad weather, etc.), or if the arrival time at the pickup location is likely to be significantly delayed. If the vehicle being dispatched cannot reach the pickup location due to a breakdown or malfunction (for example, a flat tire) of the vehicle being dispatched during the pickup. If the vehicle being dispatched is unable to reach the pickup location due to a traffic accident or traffic violation while being dispatched If the driver suddenly falls ill or is unwell during the pickup and the vehicle cannot reach the pickup location. If the driver accidentally picks up another user who has raised their hand to call a taxi on the street in front of the driver immediately after accepting the dispatch request 22 or while picking up the driver. After the driver accepts the request for dispatch 22, he / she checks the displayed pickup location and, for example, finds that the pickup location is in a narrow back alley and is difficult to reach due to the size of the vehicle, and so he / she unavoidably wishes to cancel the dispatch request 22 that he / she accepted.

[0165] If driver A of a vehicle to be dispatched whose dispatch has been confirmed wishes to cancel the dispatch, the driver operates the vehicle terminal (taxi terminal 30 or NRS terminal 40) to input a cancellation of acceptance of the dispatch request 22. For example, FIG. 13A is an example of a display screen of the taxi terminal 30 for the taxi driver 3 to cancel the dispatch. As shown in FIG. 13A, while the taxi driver 3 is being picked up after the dispatch has been confirmed, an image 320 is displayed on the display device 134 of the taxi terminal 30, displaying information about the boarding location and other information in the dispatch request 22. This image 320 also displays a cancel button that the taxi driver 3 can use to cancel the dispatch. The taxi driver 3 can input a cancellation notice by tapping the cancel button on this image 320.

[0166] In response to the input of the cancellation notice by driver A, driver A's vehicle terminal transmits the cancellation notice to the vehicle dispatch management server 60 (S11). In this way, driver A can cancel the dispatch of a vehicle for the vehicle dispatch request 22 after once agreeing to accept the vehicle dispatch request 22.

[0167] (Cancellation report process S12) When the vehicle dispatch management server 60 receives a cancellation notification (S11) from the vehicle terminal of the dispatch target vehicle of driver A, the user terminal control unit 170 of the vehicle dispatch management server 60 transmits a cancellation report to the user terminal 20 indicating that the dispatch confirmed in S10 has been canceled by driver A (S12). Then, as shown in FIG. 13B, an image 330 indicating the cancellation report is displayed on the display device 124 of the user terminal 20. This image 330 allows user 2 to recognize that a cancellation has occurred.

[0168] (Redispatch instruction processing S13) If user 2 accepts the cancellation and wishes to have the vehicle redeployed, he or she inputs a vehicle redeployment instruction into user terminal 20 to request a vehicle redeployment. For example, as shown in FIG. 13B, when image 330 representing the cancellation report is displayed on display device 124 of user terminal 20, this image 330 also displays a button that user 2 can use to instruct a vehicle redeployment. User 2 can input an instruction to redeploy the vehicle by tapping this button. In response to the input of the instruction to redeploy the vehicle by user 2, vehicle allocation request unit 180 of user terminal 20 transmits the instruction to vehicle allocation management server 60 (S13).

[0169] (Redispatch process S22~S26) When driver A cancels the accepted vehicle allocation request (S11) as described above, vehicle allocation management server 60 executes vehicle re-allocation processing (S22 to S26). For example, when vehicle allocation management server 60 receives a cancellation notice (S11) from the vehicle terminal of driver A's vehicle to be allocated, vehicle re-allocation processing (S22 to S26) is executed. When driver A cancels the acceptance of vehicle allocation request 22 as described above, vehicle re-allocation processing (S22 to S26) is executed to search again for a vehicle that matches vehicle allocation request 22 and reallocate the searched vehicle to the vehicle allocation request.

[0170] In the vehicle allocation management system 1 according to the present embodiment, after executing the cancellation report process (S12) and the vehicle re-allocation instruction process (S13), the vehicle allocation management server 60 starts executing the vehicle re-allocation process (S22 to S26) upon receiving a vehicle re-allocation instruction (S13) from the user terminal 20. However, the present invention is not limited to this exemplary process procedure. For example, the vehicle re-allocation instruction process (S13) may be omitted. In this case, the vehicle allocation management server 60 may start executing the vehicle re-allocation process (S22 to S26) upon receiving a cancellation notice (S11) from the vehicle terminal of driver A. This eliminates the need to wait for the re-allocation instruction (S13) to be received from the user terminal 20, and allows the vehicle re-allocation process (S22 to S26) to be started quickly, thereby reallocating a new vehicle (vehicle to be re-allocated) in response to the vehicle allocation request 22 of user 2 as soon as possible.

[0171] The vehicle redistribution process (S22 to S26) according to the second embodiment includes a vehicle allocation request accumulation process (S22), a vehicle allocation request extraction process (S23), a vehicle extraction process (S24), a pair generation process (S25), and a matching process (S26). Each process in the vehicle redistribution process (S22 to S26) according to the second embodiment is the same as each process in the vehicle allocation process (S2 to S6) according to the first embodiment, except for a difference related to the vehicle allocation process based on driver evaluation criteria, which will be described later. Therefore, in the following explanation, a detailed explanation of the commonalities between the vehicle redistribution process (S22 to S26) according to the second embodiment and the vehicle allocation process (S2 to S6) according to the first embodiment will be omitted, and the differences between the two will be mainly described, with the details of these differences being described later.

[0172] In the vehicle re-allocation processing (S22 to S26) according to the second embodiment, the vehicle allocation unit 172 of the vehicle allocation management server 60 reallocates, as a vehicle to be re-allocated, a vehicle of a driver who satisfies the evaluation criteria related to the driver's driving, to the vehicle allocation request 22 of the user 2. On the other hand, in the vehicle allocation processing (S2 to S6) according to the second embodiment, similar to the vehicle allocation processing (S2 to S6) according to the first embodiment, the vehicle allocation unit 172 of the vehicle allocation management server 60 allocates, as a vehicle to be allocated, a vehicle of an arbitrary driver to the vehicle allocation request 22 of the user 2, regardless of the evaluation criteria related to the driver's driving.

[0173] In the vehicle re-allocation process (S22 to S26), the vehicle allocation unit 172 of the vehicle allocation management server 60 allocates one vehicle to be re-allocated selected from among a plurality of vehicles to the vehicle allocation request 22 that has become the target of re-allocation due to the cancellation of the first vehicle allocation by the driver described above. Here, it is assumed that the vehicle of driver B (taxi driver 3 or NRS driver 4) is the vehicle to be re-allocated allocated to the vehicle allocation request 22.

[0174] In the vehicle re-allocation inquiry notification process (S27), the vehicle terminal control unit 174 of the vehicle allocation management server 60 transmits a vehicle re-allocation inquiry notification indicating an inquiry regarding acceptance of the vehicle allocation request 22 to the vehicle terminal (taxi terminal 30 or NRS terminal 40) of driver B's vehicle (vehicle to be re-allocated) (S7). The information content of the vehicle re-allocation inquiry notification (S27) at the time of re-allocation may be the same as or different from the information content of the vehicle allocation inquiry notification (S7) at the time of initial vehicle allocation. If different, information indicating that the vehicle allocation of the vehicle allocation request 22 is a re-allocation may be added to the vehicle re-allocation inquiry notification (S27). This allows driver B to recognize that the vehicle allocation request 22 in the vehicle re-allocation inquiry notification (S27) is a vehicle allocation request for a re-allocation, and therefore allows driver B to take care to provide high-quality driving service to user 2 who has been re-allocated.

[0175] In the acceptance response process (S28), when the vehicle terminal of driver B's vehicle to be redistributed receives the vehicle allocation inquiry notice (S27) from the vehicle allocation management server 60, it replies with an acceptance response to the vehicle allocation management server 60 in accordance with the input of driver B. Specifically, in accordance with the input of driver B of the vehicle to be redistributed, the vehicle allocation response unit of driver A's vehicle terminal transmits an acceptance response representing acceptance of the vehicle allocation request 22 to the vehicle allocation management server 60 as a response to the vehicle allocation inquiry notice (S27) (S28).

[0176] In the redistribution completion notification process (S29, S30), first, when the vehicle allocation management server 60 receives an acceptance response (S28) from the vehicle terminal of the vehicle to be redistributed of driver B, it confirms the redistribution of the vehicle allocation request 22 of user 2. Then, the user terminal control unit 170 and the vehicle terminal control unit 174 of the vehicle allocation management server 60 send a redistribution completion notification to the vehicle terminal of the vehicle to be redistributed of driver B and the user terminal 20 of user 2, respectively (S29, S30).

[0177] By the above processing (S22 to S30), the redistribution is confirmed, and Driver B drives the vehicle to be redistributed to the boarding location of User 2 to pick up User 2. Note that, similar to the cancellation of the vehicle allocation by Driver A, if Driver B also cancels the redistribution, the above-mentioned redistribution processing (S22 to S26) and the subsequent processing (S27 to S30) can be repeated to execute the second redistribution.

[0178] [2.3. Vehicle redistribution process based on evaluation criteria] Next, the evaluation criteria related to driver driving according to the second embodiment and the vehicle redistribution process based on the evaluation criteria will be described in detail.

[0179] As described above, when a driver cancels a vehicle dispatch, User 2 is inconvenienced by the delay in the arrival of the vehicle due to the redistribution, even though User 2 is not at fault.

[0180] Therefore, the vehicle dispatch management system 1 according to the second embodiment is characterized in that, when a vehicle is redistributed in response to a vehicle request from a user 2 due to a driver's cancellation, a vehicle of a highly rated driver who can provide high-quality driving service in response to the vehicle dispatch request is preferentially dispatched. That is, in the vehicle redistribution process (S22 to S26 in FIG. 12) due to a driver's cancellation, the vehicle dispatch management server 60 according to the second embodiment preferentially assigns a vehicle of a highly rated driver to the vehicle dispatch request from the user 2 based on the driver's driving evaluation criteria, and redistributes the vehicle. This makes it possible to provide high-quality driving service from a highly rated driver to the user 2 who has had to wait longer than usual for the arrival of the vehicle to be redistributed due to the vehicle redistribution. This reduces or eliminates the dissatisfaction of the user 2 who has been kept waiting, and in some cases, can also improve the satisfaction of the user 2.

[0181] Note that the vehicle re-allocation according to the second embodiment is intended for vehicle re-allocation when the driver cancels the accepted vehicle allocation request before the vehicle to be allocated arrives at the boarding location of user 2. On the other hand, each time the vehicle to be allocated arrives at the boarding location of user 2, if user 2 who requested the vehicle allocation does not appear at the boarding location even after a predetermined time (for example, five minutes) has elapsed, the driver may cancel the accepted vehicle allocation request, citing user 2's absence as the reason. In this case, the driver's cancellation is due to user 2's absence, and therefore the vehicle is not subject to re-allocation of the highly rated driver according to the second embodiment. Note that in the case of a driver's cancellation in this case, vehicle re-allocation processing may not be performed in the first place (for example, the user terminal 20 may not display an image for vehicle re-allocation, and the vehicle allocation management server 60 may not automatically perform vehicle re-allocation).

[0182] The evaluation criteria for the driver's driving (hereinafter sometimes simply referred to as "evaluation criteria") may be any evaluation criteria that can evaluate the driver's driving, and may be, for example, one or a combination of the various evaluation criteria exemplified below.

[0183] Furthermore, the evaluation criteria may be a two-stage evaluation based on whether one type of evaluation criterion (for example, driver's license criteria) is met, or a composite, multi-stage evaluation criterion based on whether multiple types of evaluation criteria (for example, driver's license criteria and driving experience criteria) are met. Even if the evaluation criteria are one type of evaluation criterion (for example, driver's license criteria), the evaluation may be a two-stage evaluation based on whether one criterion related to that one type of evaluation criterion (for example, whether or not the driver is licensed) is met, or a multi-stage evaluation of three or more stages based on multiple criteria related to that one type of evaluation criterion (for example, a first criterion related to whether or not the driver is licensed and a second criterion related to the period for which the license has been held).

[0184] In this way, by using multi-level or composite evaluation criteria, the driving service of a driver can be evaluated in detail using a variety of criteria. Therefore, the detailed evaluation of the driver can be suitably used for allocating vehicles to vehicle dispatch requests, so that vehicles of drivers who can provide appropriate driving services commensurate with the fee for a vehicle dispatch request can be allocated in detail according to the level of the vehicle dispatch request (for example, the amount or type of additional fee).

[0185] The following describes in detail the vehicle redistribution process based on specific examples of evaluation criteria related to driver driving according to the second embodiment. Note that the specific examples of evaluation criteria according to the second embodiment are the same as the specific examples of evaluation criteria according to the first embodiment described above, so detailed explanation of the specific examples of evaluation criteria will be omitted below (see [1.9. Driver evaluation criteria and vehicle redistribution process based on driver evaluation criteria] above).

[0186] (1) Evaluation criteria for driver qualifications See "(1a) Example 1 of the evaluation criteria for driving qualifications" above. See "(1b) Example 2 of the evaluation criteria for driving qualifications" above.

[0187] The following describes the redistribution process (S22 to S26 in FIG. 12) when the above-mentioned example evaluation criteria related to driving qualifications are used as the evaluation criteria. When the redistribution process (S22 to S26 in FIG. 12) is performed for a vehicle allocation request canceled by a driver, the vehicle allocation request subject to the redistribution process (hereinafter sometimes referred to as a "vehicle allocation request") may be preferentially allocated to a taxi vehicle 32 of a taxi driver 3 with a "high" or "medium" evaluation related to driving qualifications, and an NRS vehicle 42 of an NRS driver 4 with a "low" evaluation may not be allocated, or the priority for allocating an NRS vehicle 42 may be lowered. In this case, a taxi vehicle 32 of a taxi driver 3 with a "high" evaluation may be allocated to a redistribution request with higher priority. This allows a taxi vehicle 32 of a taxi driver 3, particularly a taxi vehicle 32 of an experienced taxi driver 3, to be preferentially allocated to a redistribution request. Therefore, a high-quality driving service can be provided by the taxi driver 3 to the user 2 who requests a re-allocation, thereby reducing or eliminating the dissatisfaction of the user 2 caused by the re-allocation, and improving the satisfaction of the user 2.

[0188] Meanwhile, simultaneously with the re-allocation process (S22 to S26) for the re-allocation request due to the cancellation, the allocation process (S2 to S6) for other initial allocation requests is also performed. For such other normal allocation requests for initial allocation, a vehicle may be allocated regardless of the driver's qualification evaluation, or a taxi vehicle 32 of a taxi driver 3 with a "medium" driver qualification evaluation or an NRS vehicle 42 of an NRS driver 4 with a "low" driver qualification evaluation may be preferentially allocated. In this case, an NRS vehicle 42 of an NRS driver 4 with a "low" driver qualification may be preferentially allocated for a normal allocation request. This reduces the number of taxi vehicles 32 allocated for normal allocation requests, thereby allowing taxi vehicles 32 to be allocated with higher priority for re-allocation requests. This further increases the opportunities for the taxi driver 3 to provide high-quality driving service to the user 2 requesting re-allocation. This further reduces the dissatisfaction of the user 2 caused by re-allocation, thereby further improving satisfaction.

[0189] (2) Evaluation criteria for driver experience See "(2a) Example 1 of the Driving Experience Evaluation Criteria" above. See "(2b) Example 2 of the Driving Experience Evaluation Criteria" above.

[0190] When using the above-described example of the evaluation criteria for driving experience, vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "high" or "medium" rating for driving experience may be preferentially allocated to a redistribution request, while vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "low" rating may not be allocated, or the priority for allocating vehicles of "low" drivers may be lowered. In this case, vehicles of "highly rated" drivers may be preferentially allocated to a redistribution request. This allows vehicles of drivers with experienced practical experience, particularly vehicles of sufficiently experienced drivers, to be preferentially allocated to a redistribution request. Therefore, a high-quality driving service by an experienced driver can be provided to the user 2 who requests a redistribution, thereby reducing or eliminating the dissatisfaction of the user 2 caused by the redistribution, and improving the satisfaction of the user 2.

[0191] On the other hand, for normal vehicle dispatch requests other than the initial dispatch, vehicles may be assigned regardless of the driver's driving experience rating, or vehicles of drivers with a "medium" or "low" driving experience rating may be assigned preferentially. In this case, vehicles of "low" drivers may be assigned preferentially to normal vehicle dispatch requests. This reduces the number of vehicles of "highly" and "medium" drivers assigned to normal vehicle dispatch requests, so vehicles of "highly" and "medium" drivers can be assigned preferentially to redispatch requests. This further increases the opportunities to provide high-quality driving services by drivers with experienced experience to users 2 who request redispatch. This further reduces user 2's dissatisfaction with vehicle redispatch and further improves satisfaction.

[0192] (3) Evaluation criteria for driver training received by the driver See "(3a) Example 1 of the Driver's Education Evaluation Criteria" above. See "(3b) Example 2 of the Driver's Education Evaluation Criteria" above.

[0193] When using the above-described example of evaluation criteria related to driver education, vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "high" or "average" driver education rating may be preferentially allocated to a redistribution request, while vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "low" rating may not be allocated, or the priority for allocating vehicles of "low" drivers may be lowered. In this case, vehicles of "highly rated" drivers may be allocated with higher priority to a redistribution request. This allows vehicles of drivers who have received driver education, particularly vehicles of drivers who have received sufficient driver education, to be preferentially allocated to a redistribution request. Therefore, high-quality driving and customer service provided by drivers who have received driver education can be provided to User 2 who requests a redistribution, thereby reducing or eliminating User 2's dissatisfaction due to redistribution and improving User 2's satisfaction.

[0194] On the other hand, for regular vehicle dispatch requests other than the initial dispatch, vehicles may be assigned regardless of the driver's education rating, or vehicles of drivers with a "medium" or "low" driver education rating may be assigned preferentially. In this case, vehicles of "low" drivers may be assigned preferentially to regular vehicle dispatch requests. This reduces the number of vehicles of "highly" and "medium" drivers assigned to regular vehicle dispatch requests, allowing vehicles of "highly" and "medium" drivers to be assigned preferentially to redispatch requests. This further increases the opportunities for users 2 requesting redispatch to receive high-quality driving and customer service from drivers who have received driving education. This further reduces user 2's dissatisfaction with vehicle redispatch and further improves satisfaction.

[0195] (4) Evaluation criteria for the driver's traffic violation and traffic accident history See "(4a) Example 1 of the evaluation criteria for traffic violation and traffic accident history" above.

[0196] Using the above-described example of evaluation criteria for drivers' traffic violation and accident histories, vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of excellent drivers with a "high" rating for traffic violation and accident histories may be preferentially allocated to vehicle re-allocation requests, while vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "low" rating may not be allocated, and vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with a "medium" rating may not be allocated, or the priority for allocating vehicles of "medium" drivers may be lowered. In this case, vehicles of "highly rated" drivers may be preferentially allocated to vehicle re-allocation requests. This allows vehicles of excellent drivers with no history of traffic violations or accidents to be preferentially allocated to vehicle re-allocation requests. Therefore, a safe driving service by an excellent driver can be provided to user 2 who requests vehicle re-allocation, thereby reducing or eliminating user 2's dissatisfaction due to vehicle re-allocation and improving user 2's satisfaction.

[0197] On the other hand, for normal vehicle dispatch requests other than the initial dispatch, vehicles may be assigned regardless of the driver's evaluation of traffic violation history or traffic accident history, or vehicles of drivers with a "medium evaluation" or "low evaluation" may be preferentially assigned. In this case, vehicles of drivers with a "low evaluation" may be preferentially assigned to normal vehicle dispatch requests. This reduces the number of vehicles of "highly rated" excellent drivers assigned to normal vehicle dispatch requests, so vehicles of "highly rated" excellent drivers can be preferentially assigned to redispatch requests. Therefore, it is possible to further increase the opportunities to provide safe driving services by excellent drivers to User 2 who requests redispatch. This can further reduce User 2's dissatisfaction due to redispatch and further improve satisfaction.

[0198] (5) Evaluation criteria for user driver ratings See "(5a) Example 1 of the evaluation criteria for user evaluation of drivers" above. See "(5b) Example 2 of the evaluation criteria for user evaluation of drivers" above.

[0199] When using the above-described example of evaluation criteria related to user ratings, vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with "high" or "average" user ratings may be preferentially allocated to vehicle re-allocation requests, while vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with "low" ratings may not be allocated, or the priority for allocating vehicles of "low" drivers may be lowered. In this case, vehicles of "highly rated" drivers may be allocated with higher priority to vehicle re-allocation requests. This allows vehicles of drivers with high user ratings, particularly vehicles of highly rated drivers with very high user ratings, to be preferentially allocated to vehicle re-allocation requests. Therefore, high-quality driving and customer service can be provided to user 2 who requests vehicle re-allocation by a driver with high user ratings, thereby reducing or eliminating user 2's dissatisfaction due to vehicle re-allocation and improving user 2's satisfaction.

[0200] On the other hand, for normal vehicle dispatch requests other than the initial dispatch, vehicles may be assigned regardless of the user rating, or vehicles of drivers with a user rating of "average" or "low" may be preferentially assigned. In this case, vehicles of "low" drivers may be preferentially assigned to normal vehicle dispatch requests. This reduces the number of vehicles of "highly" and "average" drivers assigned to normal vehicle dispatch requests, so vehicles of "highly" and "average" drivers can be preferentially assigned to redispatch requests. This increases the opportunities for users 2 requesting redispatch to receive high-quality driving and customer service from drivers with high user ratings. This further reduces user 2's dissatisfaction due to redispatch and further improves satisfaction.

[0201] (6) Evaluation criteria for the driver's driving score calculated by the driving analysis software See "(6a) Example 1 of the evaluation criteria for driver driving scores" above. See "(6b) Example 2 of the evaluation criteria for driver driving scores" above.

[0202] When using the above-described example of evaluation criteria related to driving scores, vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with "highly rated" or "average" driving scores may be preferentially allocated to vehicle redistribution requests, while vehicles (which may be either taxi vehicles 32 or NRS vehicles 42) of drivers with "lowly rated" driving scores may not be allocated, or the priority for allocating vehicles of "lowly rated" drivers may be lowered. In this case, vehicles of "highly rated" drivers may be allocated with higher priority to vehicle redistribution requests. This allows vehicles of drivers with high driving scores, particularly vehicles of highly rated drivers with extremely high driving scores, to be preferentially allocated to vehicle redistribution requests. Therefore, a safe driving service provided by a driver with a high driving score can be provided to user 2 who requests vehicle redistribution, thereby reducing or eliminating user 2's dissatisfaction due to vehicle redistribution, and improving user 2's satisfaction and sense of security.

[0203] On the other hand, for normal vehicle dispatch requests other than the initial dispatch, vehicles may be assigned regardless of the driving score evaluation, or vehicles of drivers with driving scores of "average" or "low" may be preferentially assigned. In this case, vehicles of "low" drivers may be preferentially assigned to normal vehicle dispatch requests. This reduces the number of vehicles of "highly" and "average" drivers assigned to normal vehicle dispatch requests, so vehicles of "highly" and "average" drivers can be preferentially assigned to redispatch requests. Therefore, it is possible to further increase the opportunities to provide safe driving services by drivers with high driving scores to User 2 who requests redispatch. This further reduces User 2's dissatisfaction due to redispatch, and further improves the user's satisfaction and sense of security.

[0204] [2.4. Vehicle re-allocation and dispatch processing based on evaluation criteria] Next, with reference to FIG. 12 described above, a supplementary explanation will be given of the vehicle redistribution process (S22 to S26) of allocating vehicles in response to a vehicle redistribution request based on the driver evaluation criteria, which is a feature of the second embodiment.

[0205] In the redistribution processing (S22 to S26) of the second embodiment, the vehicle allocation unit 172 of the vehicle allocation management server 60 is characterized in that it searches for and allocates a vehicle again for a vehicle allocation request 22 (hereinafter sometimes referred to as a "redistribution request") that has become the subject of redistribution due to a driver's cancellation, based on the evaluation criteria related to the driver's driving described above.

[0206] In this characteristic vehicle redistribution process (S22 to S26), when one of the multiple vehicle redistribution requests 22 that are simultaneously matched is a vehicle redistribution request, the vehicle allocation unit 172 allocates a vehicle of a driver who satisfies the above-mentioned driving evaluation criteria to the vehicle redistribution request. At this time, it is preferable that the vehicle allocation unit 172 does not allocate a vehicle of a driver who does not satisfy the evaluation criteria to the vehicle redistribution request, or lowers the priority of allocating a vehicle of a driver who does not satisfy the evaluation criteria compared to the priority of allocating a vehicle of a driver who satisfies the evaluation criteria.

[0207] On the other hand, if one of the multiple vehicle allocation requests 22 that are simultaneously matched is not a re-allocation request but a first-time vehicle allocation request, and is not a priority vehicle allocation request or a reservation vehicle allocation request (for example, if the one vehicle allocation request is a normal vehicle allocation request for the first time), the vehicle allocation unit 172 allocates a vehicle to the normal vehicle allocation request regardless of the above evaluation criteria. In this case, the vehicle allocation unit 172 may preferentially allocate a vehicle of a driver who does not satisfy the above evaluation criteria to the normal vehicle allocation request, or may increase the priority of allocating a vehicle of a driver who does not satisfy the evaluation criteria above the priority of allocating a vehicle of a driver who satisfies the evaluation criteria.

[0208] This vehicle redistribution process (S22 to S26) allows vehicles with highly rated drivers to be preferentially allocated in response to a vehicle redistribution request. Therefore, for users 2 who have been redistributed due to a driver's cancellation of a vehicle allocation, high-quality driving services from highly rated drivers can be provided in compensation for the boarding delay caused by the redistribution. This reduces or eliminates the dissatisfaction of users 2 who have been redistributed, and in some cases, can even improve their satisfaction.

[0209] 9 and 11, a specific example of the vehicle re-allocation process (S22 to S26) based on the driver evaluation criteria according to the second embodiment will be described. FIG. 9 shows the vehicle allocation result when all of the vehicle allocation requests 22a to 22d are regular vehicle allocation requests, and FIG. 11 shows the vehicle allocation result when, among the vehicle allocation requests 22a to 22d, only the vehicle allocation request 22c is a re-allocation request, and the other vehicle allocation requests 22a, 22b, and 22d are regular vehicle allocation requests. In the case of FIG. 11, the driver evaluation criteria used as the criteria for the vehicle allocation process for the re-allocation requests are, for example, the criteria related to the driving qualifications described above, and specifically, the criteria are whether the driver has a Class 2 driver's license, as in the above-mentioned "(1a) Example 1 of Evaluation Criteria Related to Driving Qualifications."

[0210] As shown in Figure 9, when all of the vehicle dispatch requests 22a to 22d from users 2a to 2d are normal vehicle dispatch requests for initial vehicle dispatch, vehicles 42b, 32h, 42i, and 32d are assigned to the vehicle dispatch requests 22a to 22d, respectively, and are determined as the vehicles to be dispatched. In this case, vehicles 42b, 32h, 42i, and 32d are determined as the vehicles to be dispatched so that the sum of the distances between each of users 2a to 2d and vehicles 42b, 32h, 42i, and 32d is minimized. In this case, NRS vehicle 42i, which is closest to user 2c, is determined as the vehicle to be dispatched for vehicle dispatch request 22c.

[0211] In contrast to this, consider a case where, among the vehicle allocation requests 22a to 22d, only the vehicle allocation request 22c is a re-allocation request, and the other vehicle allocation requests 22a, 22b, and 22d are normal vehicle allocation requests for initial vehicle allocation, as shown in Fig. 11. In this case, the NRS vehicle 42i is not allocated to the re-allocation request 22c, but the taxi vehicle 32e is allocated, becoming the vehicle to be allocated for the vehicle re-allocation request 22c.

[0212] The reason for this is that in the vehicle dispatch process according to the second embodiment, vehicle dispatch process is performed based on the above-mentioned "(1a) Evaluation criteria related to the driver's driving qualifications," so that a taxi vehicle 32 is assigned to the vehicle re-dispatch request 22c, rather than an NRS vehicle 42. User 2c, who has been re-dispatched due to the driver's cancellation of the vehicle dispatch, will have to wait longer than usual until boarding, so it is desirable to provide high-quality driving service to user 2c in compensation for the vehicle dispatch delay.

[0213] Therefore, in the second embodiment, the NRS vehicle 42i, which is the closest vehicle to the user 2c, is excluded as a vehicle to be redistributed in the vehicle redistribution request 22c of the user 2c, and the taxi vehicle 32e, which is the second closest vehicle to the user 2c, is selected. This makes it possible to provide a high-quality driving service to the user 2c by having the taxi driver 3 of the taxi vehicle 32e drive the vehicle. This also reduces or eliminates the dissatisfaction of the user 2c caused by the redistribution, thereby improving satisfaction.

[0214] In addition, users who pay an additional fee to use a reservation-based car dispatch service often expect higher quality driving service from the driver than in a regular car dispatch. Therefore, if a vehicle with a driver who provides relatively low quality driving service is dispatched in a reservation-based car dispatch, user satisfaction may decrease. In addition, in a reservation-based car dispatch, the driver is responsible for arriving at the boarding location by the specified boarding time, even during traffic congestion, which puts pressure on the driver.

[0215] In this way, reserved car dispatching involves higher expectations from users and greater responsibility and pressure on drivers compared to regular car dispatching, which does not incur additional fees. Therefore, when reserved car dispatching is used, it is desirable to dispatch vehicles with drivers who can provide high-quality driving services.

[0216] Therefore, according to the first and second embodiments, when the vehicle dispatch request 22 is a reservation-based vehicle dispatch request, vehicles of highly rated drivers are preferentially dispatched based on the driver's evaluation in both the initial vehicle dispatch process (S2 to S6) and the second and subsequent vehicle re-dispatch processes (S22 to S26). This allows reservation-based vehicle dispatch requests to be treated more favorably than other vehicle dispatch requests, making it possible to provide high-quality driving services when a reservation-based vehicle dispatch is made. In other words, in cases such as reservation-based vehicle dispatch, which involve high expectations from the user 2 and great responsibility and pressure on the driver, it is possible to avoid dispatching vehicles of drivers with relatively low evaluations. This reduces the driver's responsibility and pressure, which is beneficial for beginners and inexperienced drivers.

[0217] [2.5. Summary of the Second Embodiment] (1) As described above, according to the second embodiment, there is provided a vehicle dispatch management system 1 including a plurality of user terminals 20, a plurality of vehicle terminals 30, 40 disposed in a plurality of vehicles 32, 42, respectively, and a vehicle dispatch management device (e.g., a vehicle dispatch management server 60) communicably connected to the user terminals 20 and the vehicle terminals 30, 40 via a network 6, wherein the user terminals 20 include one or more first processors (e.g., a processor of the processing device 122), the vehicle dispatch management device includes one or more second processors (e.g., a processor of the processing device 162), and the vehicle terminals 30, 40 include one or more third processors (e.g., a processor of the processing devices 132, 142), and the first processor of the user terminal 20 executes a process of transmitting a vehicle dispatch request to the vehicle dispatch management device in response to an input from a user 2, and the second processor of the vehicle dispatch management device executes a process of transmitting a vehicle dispatch request to the vehicle dispatch management device in response to the vehicle dispatch request received from the user terminal 20. The vehicle dispatch management system then executes a dispatch process (S2 to S6) of allocating one vehicle to be dispatched selected from a plurality of vehicles 32, 42, and a process of sending a dispatch inquiry notice representing an inquiry regarding the dispatch request to the vehicle terminal 30, 40 of the vehicle to be dispatched, and the third processor of the vehicle terminal 30, 40 of the vehicle to be dispatched executes a process of sending an acceptance response representing acceptance of the dispatch inquiry notice to the vehicle dispatch management device in accordance with input from driver A of the vehicle to be dispatched, and a process of sending a cancellation notice representing cancellation of acceptance to the vehicle dispatch management device in accordance with input from driver A of the vehicle to be dispatched, and when the second processor of the vehicle dispatch management device receives a cancellation notice from the vehicle terminal 30, 40 of the vehicle to be dispatched, it executes a re-dispatch process (S22 to S26) of allocating, to the dispatch request, a vehicle of driver B that satisfies evaluation criteria regarding the driver's driving.

[0218] With this configuration, when a vehicle is redistributed due to a driver's cancellation, a vehicle of a highly rated driver who can provide high-quality driving service can be redistributed. Therefore, for User 2 whose waiting time until boarding has increased due to the redistribution, high-quality driving service can be provided in compensation for the delay in vehicle delivery. This reduces or eliminates User 2's dissatisfaction caused by the delay in vehicle delivery, and also improves satisfaction.

[0219] (2) Furthermore, according to this embodiment, there is provided a vehicle dispatch management device (e.g., a vehicle dispatch management server 60) that is communicatively connected via a network 6 to a plurality of user terminals 20 and a plurality of vehicle terminals 30, 40 that are respectively disposed in a plurality of vehicles 32, 42, and the vehicle dispatch management device has one or more processors (e.g., the processor of the processing device 162), and the processor executes the following processes: a dispatch process (S2 to S6) that assigns one vehicle to be dispatched selected from the plurality of vehicles 32, 42 in response to a dispatch request received from the user terminal 20; a process that sends a vehicle dispatch inquiry notification representing an inquiry regarding the vehicle dispatch request to the vehicle terminal 30, 40 of the vehicle to be dispatched; and a re-dispatch process (S22 to S26) that, when a cancellation notification representing a cancellation of acceptance of the vehicle dispatch inquiry notification is received from the vehicle terminal 30, 40 of the vehicle to be dispatched, assigns a vehicle of driver B that meets the evaluation criteria regarding the driver's driving as a vehicle to be re-dispatched to the vehicle dispatch request.

[0220] With this configuration, when a vehicle is redistributed due to a driver's cancellation, a vehicle of a highly rated driver who can provide high-quality driving service can be redistributed. Therefore, for User 2 whose waiting time until boarding has increased due to the redistribution, high-quality driving service can be provided in compensation for the delay in vehicle delivery. This reduces or eliminates User 2's dissatisfaction caused by the delay in vehicle delivery, and also improves satisfaction.

[0221] (3) In the above-described vehicle redistribution process (S22 to S26), a vehicle of a driver who does not meet the evaluation criteria may not be allocated to a vehicle allocation request as a vehicle eligible for redistribution, or the allocation priority of the vehicle to the vehicle allocation request may be lowered. With this configuration, a vehicle of a driver with a relatively low evaluation may not be allocated to a vehicle allocation request that has been redistributed, or the rate at which vehicles of such a driver are allocated may be reduced. This reduces the number of cases in which a relatively low-quality driving service is provided to a user 2 who has paid an additional fee, thereby preventing further increase in user 2 dissatisfaction due to vehicle allocation delays.

[0222] (4) In the above vehicle allocation process (S2 to S6), when a vehicle is initially allocated in response to a vehicle allocation request, a vehicle to be allocated to the vehicle allocation request may be allocated regardless of the evaluation criteria. With this configuration, a vehicle of a highly rated driver who can provide high-quality driving service is less likely to be allocated to a vehicle allocation request for an initial vehicle allocation that is not a re-allocation, and a vehicle of a highly rated driver is more likely to be allocated to a paid vehicle allocation request. Therefore, the probability of providing high-quality driving service to User 2 who has been re-allocated can be further increased, further reducing User 2's dissatisfaction.

[0223] (5) The evaluation criteria may include criteria related to the driver's driving qualifications. With this configuration, when redispatching a vehicle, priority can be given to dispatching a taxi vehicle 32 operated by a taxi driver 3 or a vehicle operated by a qualified, experienced driver. Therefore, high-quality driving services by a taxi driver 3 or an experienced driver can be provided to the user 2, which can further reduce or eliminate the dissatisfaction of the user 2 caused by delays in vehicle dispatch and further improve satisfaction.

[0224] (6) The evaluation criteria may include at least one of the following criteria: the driver's driving experience, the driver's driving education, the driver's traffic violation history, the user's evaluation of the driver, and the driver's driving score calculated by driving analysis software. This configuration allows vehicles driven by drivers who are highly rated based on these various evaluation criteria to be preferentially dispatched when redistributing vehicles. Therefore, a high-quality driving service provided by a highly rated driver can be provided to the redistributed User 2, further reducing or eliminating User 2's dissatisfaction due to delays in vehicle dispatch and further improving satisfaction.

[0225] (7) The vehicle dispatch request may include a reservation request that allows the user to specify a desired ride date and time in advance by paying an additional fee. With this configuration, when a reservation request requiring payment of an additional fee is redistributed, a vehicle of a driver who can provide high-quality driving service can be dispatched in response to the reservation request. Therefore, in exchange for the reservation fee paid by User 2, high-quality driving service can be provided, thereby improving User 2's satisfaction with the cost-effectiveness of the reservation service.

[0226] (8) Furthermore, according to this embodiment, a vehicle dispatch management method executed by a computer is provided, which includes a vehicle dispatch process (S2 to S6) that assigns one vehicle to be dispatched selected from a plurality of vehicles in response to a vehicle dispatch request received from a user terminal 20, a process that sends a vehicle dispatch inquiry notification representing an inquiry regarding the vehicle dispatch request to the vehicle terminal 30, 40 of the vehicle to be dispatched, and a re-dispatch process (S22 to S26) that, when a cancellation notification representing a cancellation of acceptance of the vehicle dispatch inquiry notification is received from the vehicle terminal 30, 40 of the vehicle to be dispatched, assigns a vehicle of a driver who meets evaluation criteria regarding the driver's driving as a vehicle to be re-dispatched to the vehicle dispatch request.

[0227] With this configuration, when a vehicle is redistributed due to a driver's cancellation, a vehicle of a highly rated driver who can provide high-quality driving service can be redistributed. Therefore, for User 2 whose waiting time until boarding has increased due to the redistribution, high-quality driving service can be provided in compensation for the delay in vehicle delivery. This reduces or eliminates User 2's dissatisfaction caused by the delay in vehicle delivery, and also improves satisfaction.

[0228] (9) Furthermore, according to this embodiment, a program is provided to cause a computer to execute the following processes: a dispatch process (S2 to S6) for assigning one vehicle to be dispatched selected from a plurality of vehicles in response to a dispatch request received from a user terminal 20; a process for sending a dispatch inquiry notification representing an inquiry regarding the dispatch request to the vehicle terminal 30, 40 of the vehicle to be dispatched; and a redistribution process (S22 to S26) for assigning, to the dispatch request, a vehicle of a driver who meets the evaluation criteria regarding the driver's driving, as a vehicle to be redistributed.

[0229] With this configuration, when a vehicle is redistributed due to a driver's cancellation, a vehicle of a highly rated driver who can provide high-quality driving service can be redistributed. Therefore, for User 2 whose waiting time until boarding has increased due to the redistribution, high-quality driving service can be provided in compensation for the delay in vehicle delivery. This reduces or eliminates User 2's dissatisfaction caused by the delay in vehicle delivery, and also improves satisfaction.

[0230] 3. Third Embodiment Next, a vehicle dispatch management system 1 and the like according to a third embodiment of the present invention will be described.

[0231] [3.1. Image control processing to suggest switching to wired vehicle dispatch request while vehicle detection processing is ongoing] 14 is a sequence diagram showing the flow of the vehicle search process according to this embodiment and the display control process according to the progress of the process. In the following explanation, it is assumed that User 2 requests a vehicle during a busy time period or in a busy area where demand for vehicles is greater than supply.

[0232] As shown in Fig. 14, first, the user 2 sets the vehicle dispatch conditions (S200, S202) using a user application for the vehicle dispatch management system 1 installed on the user terminal 20, and then makes a normal vehicle dispatch request (S1). When making this vehicle dispatch request, as shown in Fig. 15A, a vehicle dispatch request image 200 of the user application is displayed on the display device 124 of the user terminal 20 (S200). The vehicle dispatch request image 200 includes a transition button 201 for transitioning to a vehicle dispatch category setting image 205 (see Fig. 15B) and a confirmation button 202 for confirming the vehicle dispatch request.

[0233] When user 2 taps transition button 201 on the image 200 for requesting a vehicle dispatch, a vehicle dispatch category setting image 205 shown in FIG. 15B is displayed on the display device 124 of the user terminal 20 (S200). By selecting vehicle designation buttons 206 and 207 on the image 205, user 2 can designate the category of the vehicle to be dispatched (i.e., the dispatch category) and set the dispatch category setting conditions (S202). In the example image 205 of FIG. 15B, the dispatch category setting conditions can be set to either "taxi ride share" or "taxi." When "taxi ride share" is selected, the dispatch target vehicles are set to include both taxi vehicle 32 (first vehicle) and NRS vehicle 42 (second vehicle) (this corresponds to a "first vehicle dispatch request in which both the first vehicle and the second vehicle are designated as vehicles to be dispatched"). On the other hand, if "Taxi" is selected, the vehicles to be dispatched are limited to taxi vehicle 32 (first vehicle) only (corresponding to "a second dispatch request specifying only the first vehicle as the vehicle to be dispatched"). User 2 can also select the taxi company of the vehicle to be dispatched by tapping the taxi company setting button 208 on the dispatch category setting image 205 to specify the desired taxi company.

[0234] In the following explanation, an example will be described in which user 2 sets the setting condition of the dispatch category to "taxi / ride share" (corresponding to "a first dispatch request that designates both the first vehicle and the second vehicle as vehicles to be dispatched"). Also, for the sake of convenience, an example will be described in which the vehicle to be dispatched is either a taxi vehicle 32 or an NRS vehicle 42, but the NRS vehicle 42 in the following explanation may be replaced with the above-mentioned "vehicle with requirements."

[0235] After setting the vehicle dispatch category in the vehicle dispatch category setting image 205 (FIG. 15B), the user 2 taps the decision button 209 to return to the vehicle dispatch request image 200 (FIG. 15A), and then taps the decision button 202 to execute the vehicle dispatch request on the vehicle dispatch request image 200. Then, in response to the input by the user 2 as described above, the user terminal 20 transmits a command for a normal vehicle dispatch request to the vehicle dispatch management server 60 (S1 in FIG. 14).

[0236] When the vehicle dispatch management server 60 receives a command for a normal vehicle dispatch request from user 2, it executes a vehicle search process in normal vehicle dispatch mode (S110, S120). This vehicle search process in normal vehicle dispatch mode (S110, S120) is a process for searching for at least one candidate vehicle that matches the normal vehicle dispatch request received from user 2 from among multiple vacant vehicles that exist in the same business area as user 2. Note that this vehicle search process in normal vehicle dispatch mode (S110, S120) corresponds to a part of the vehicle dispatch process (S2 to S7) shown in FIG. 7 described above. The vehicle dispatch management server 60 executes the vehicle search process (S110, S120) continuously and continuously until a candidate vehicle that matches the normal vehicle dispatch request is found and a vehicle to be assigned to the normal vehicle dispatch request is determined.

[0237] In order to clearly explain the relationship between the series of detection processes (S110, S120) that are continuously executed in this manner and the display control processes (S112, S122, S132) that will be described later, in FIG. 14, for the sake of convenience, the series of detection processes (S110, S120) are distinguished into a detection process (S110) and a continued detection process (S120). The detection process (S110) is a detection process that is executed during a period from the start of execution of the detection process until a predetermined time (e.g., 5 seconds, 10 seconds, or 30 seconds) has elapsed. On the other hand, the continued detection process (S120) is a detection process that is executed after the predetermined time has elapsed. The processing content of the vehicle search in the latter continued detection process (S120) is the same as the processing content of the vehicle search in the former detection process (S110) (corresponding to processes S2 to S6 shown in FIG. 7), and the two are distinguished merely for the sake of convenience. Furthermore, the continuous vehicle detection process (S120) is executed continuously without interruption within a predetermined time limit (for example, 30 minutes or 60 minutes).

[0238] Furthermore, while the vehicle detection process (S110, S120) is being continuously executed, the user terminal control unit 170 of the vehicle dispatch management server 60 executes a display control process (S112, S122, S132) that controls the images displayed on the user terminal 20 in accordance with the progress of the vehicle detection process (S110, S120) (for example, the duration of the vehicle detection process). In accordance with the display control process (S112, S122, S132) by the vehicle dispatch management server 60, the user terminal 20 displays a plurality of images on the display device 124 in accordance with the progress of the vehicle detection process (S110, S120) that is being continued by the vehicle dispatch management server 60 (S210, S220, S240).

[0239] The display control processing (S112, S122, S132) by the vehicle dispatch management server 60 includes a first display control processing (S112) and a second display control processing (S122). In the first display control processing (S122), after starting execution of the vehicle detection processing (S110) in the normal vehicle dispatch mode, the vehicle dispatch management server 60 causes the display device 124 of the user terminal 20 to display a first progress image 210 shown in FIG. 16 (S210). As shown in FIG. 16, the first progress image 210 is an image including progress information 211 (second progress information). The progress information 211 is information indicating that the vehicle detection processing (S110) is being executed by the vehicle dispatch management server 60.

[0240] Next, in the second display control process (S122), when a predetermined time (e.g., 5, 10, or 30 seconds) has elapsed since the start of the vehicle search process (S110) in the normal vehicle dispatch mode, i.e., immediately after the start of the continuous vehicle search process (S120), the vehicle dispatch management server 60 causes the display device 124 of the user terminal 20 to display a second progress image 220 shown in FIGS. 17A and 17B (S220). As shown in FIGS. 17A and 17B, the second progress image 220 is an image including progress information 221 (first progress information) and proposed information 225 (first proposed information). The progress information 221 (first progress information) is information indicating that the vehicle dispatch management server 60 is currently executing the continuous vehicle search process (S120). The proposed information 225 (first proposed information) is information for proposing to the user 2 waiting for a vehicle to switch from the normal vehicle dispatch mode to the priority vehicle dispatch mode.

[0241] The display control processing (S112, S122, S132) by the vehicle dispatch management server 60 and the display processing (S210 to S240) by the user terminal 20 will be described in detail below in order.

[0242] As shown in Fig. 14, when the vehicle dispatch management server 60 receives a normal vehicle dispatch request command (S1) sent from the user terminal 20, it starts executing a vehicle search process (S110) in normal vehicle dispatch mode. Next, immediately after starting the vehicle search process (S110), the vehicle dispatch management server 60 sends a first image switching command to the user terminal 20 (S112). When the user terminal 20 receives the first image switching command from the vehicle dispatch management server 60, it displays the first progress image 210 shown in Fig. 16 on the display device 124 (S210).

[0243] The first progress image 210 includes text information, "A vehicle is being arranged," as progress information 211 indicating that the vehicle detection process (S110) is being executed by the vehicle dispatch management server 60. By presenting this progress information 211, the user 2 can recognize that the vehicle detection process (S110) is being executed. Note that the progress information 211 may be something other than the text information shown in FIG. 16 , and may be, for example, an indicator, graph, graphic, icon, character image, or the like indicating that the vehicle detection process (S110) is being executed by the vehicle dispatch management server 60, or the progress of the process.

[0244] Additionally, information 212 (e.g., "0:01") indicating the elapsed time from the start of execution of the vehicle detection process (S110) is displayed in seconds in the first progress image 210. By presenting this information 212 indicating the elapsed time, the user 2 can recognize the elapsed time from the time when the vehicle dispatch request (S1) was made, and can grasp how much time the vehicle dispatch management server 60 is taking to perform the vehicle detection process (S110).

[0245] Next, immediately after a predetermined time (for example, 5, 10, or 30 seconds) has elapsed since the start of execution of the vehicle detection process (S110) and the vehicle dispatch management server 60 enters the continuous vehicle detection process (S120), the vehicle dispatch management server 60 transmits a command to instruct the user terminal 20 to switch to the second image (S122). Upon receiving the command to instruct the user terminal 20 to switch to the second image from the vehicle dispatch management server 60, the user terminal 20 displays the second progress image 220 shown in Fig. 17A on the display device 124 (S220).

[0246] The second progress image 220 shown in FIG. 17A includes text information saying "Searching for available vehicles" as progress information 221 indicating that the vehicle dispatch management server 60 is currently executing the continuous vehicle search process (S120). By presenting this progress information 221, the user 2 can recognize that the vehicle search process (S110, S120) is being executed continuously. Note that the progress information 221 may be something other than the text information shown in FIG. 17A, and may be, for example, an indicator, graph, graphic, icon, character image, or the like indicating that the vehicle dispatch management server 60 is currently executing the continuous vehicle search process (S120) or the progress of the process.

[0247] Here, the above-mentioned predetermined time will be explained. The predetermined time is a reference time for determining the timing for changing from the above-mentioned vehicle detection process (S110) to the continuous vehicle detection process (S120). This predetermined time corresponds to the time for determining the timing for switching from the first progress image 210 (FIG. 16) displayed on the user terminal 20 to the second progress image 220 (FIG. 17). Therefore, the predetermined time is preferably a time (e.g., 5 seconds, 10 seconds, or 30 seconds) determined based on the average vehicle detection time when the vehicle detection process is performed in a normal time period or area that is not a congested time period or a congested area. This makes it easier for the user 2 to intuitively recognize that the vehicle detection process is continuing beyond the normal average vehicle detection time when the first progress image 210 displayed on the user terminal 20 is switched to the second progress image 220, and therefore the waiting time until the vehicle dispatch is confirmed will likely be longer than usual.

[0248] Furthermore, the second progress image 220 shown in FIG. 17A displays information 222 (e.g., "0:30") indicating the elapsed time since the start of execution of the vehicle search process (S110) in seconds, and also displays information 223 indicating the predicted waiting time (first predicted waiting time) until vehicle allocation is confirmed in response to User 2's vehicle allocation request in minutes (e.g., "approximately 20 to 30 minutes"). By displaying this information 223 indicating the predicted waiting time, User 2 can accurately understand that there are few available vehicles in the area surrounding User 2 and how long he or she is expected to have to wait until vehicle allocation is confirmed. Note that the information 223 indicating the predicted waiting time may be other than text information indicating a specific number of hours as shown in FIG. 17A, and may be, for example, an indicator, graph, graphic, icon, character image, or the like indicating the level or transition of the predicted waiting time.

[0249] Furthermore, as shown in FIG. 17A , the second progress image 220 displays information 224 (e.g., “14 people have arranged for a ride in the vicinity” in FIG. 17A ) indicating the number of users currently waiting for a ride in the same area as user 2 (hereinafter, sometimes referred to as the “number of users waiting for a ride”). This number of users waiting for a ride is preferably the number of other users waiting for a ride with the same ride-hailing conditions as user 2 (e.g., a regular ride-hailing request with a taxi / ride-share option specified) in the same area as user 2 (e.g., within the business district where user 2 is located or within a range of several kilometers around user 2). By displaying this information 224 indicating the number of users waiting for a ride, user 2 can more accurately grasp the specific number of other users waiting for a ride with the same ride-hailing conditions as user 2 and the associated degree of congestion in the ride-hailing area. The information 224 representing the number of users waiting for a ride may be other than text information representing a specific number of people as shown in FIG. 17A, and may be, for example, an indicator, graph, figure, icon, character image, etc. representing the level or trend of the number of users waiting for a ride.

[0250] In addition, the vehicle dispatch management server 60 can estimate the predicted waiting time and number of users waiting for a vehicle for user 2 using a predetermined algorithm based on data such as the number of vehicle dispatch requests received from other users in the same area as user 2, the vehicle dispatch settings made by those other users, the number of vehicles currently in operation, the number of vehicles in operation, the number of vehicles available, the most recent vehicle dispatch record, and statistics on past vehicle dispatch record.

[0251] As described above, in this embodiment, the image representing the progress displayed on the user terminal 20 automatically switches from the first progress image 210 ( FIG. 16 ) to the second progress image 220 ( FIG. 17A ) depending on the progress of the vehicle search process (S110, S120) by the vehicle dispatch management server 60 (e.g., the elapsed time of the vehicle search process). As a result, user 2 recognizes that the vehicle search process (S110, S120) is still being performed by the vehicle dispatch management system 1 even after a certain amount of time has passed since user 2's dispatch request (S1). User 2 also recognizes that the waiting time for vehicle dispatch is likely to be long due to the limited number of available vehicles around user 2, which can cause frustration. Therefore, user 2 slides the second progress image 220 shown in FIG. 17A upward on the screen to change it to the full-screen display state shown in FIG. 17B , and attempts to obtain information on a method for quickly confirming vehicle dispatch as a countermeasure to the long vehicle dispatch waiting time. 17A and 17B, the second progress image 220 is transitioned from the partial display state of Fig. 17A to the full-screen display state of Fig. 17B by an operation of the user 2. However, the present invention is not limited to such an example. For example, when transitioning from the above-mentioned vehicle detection process (S110) to the continued vehicle detection process (S120), the second progress image 220 may be displayed in the full-screen display state of Fig. 17B from the beginning, and the second progress image 220 in the partial display state of Fig. 17A may not be displayed.

[0252] 17B, ​​the second progress image 220 in the full-screen display state displays proposal information 225 proposing the use of a priority vehicle dispatch service. This proposal information 225 is information (first proposal information) for proposing to user 2 to switch from the normal vehicle dispatch mode currently being executed by the vehicle dispatch management server 60 to a priority vehicle dispatch mode. By presenting such proposal information 225, user 2 can recognize that switching to the priority vehicle dispatch mode exists as a method for shortening the waiting time until vehicle dispatch is confirmed, and user 2 can be made aware of and, in some cases, encouraged to use the priority vehicle dispatch service.

[0253] Furthermore, as shown in FIG. 17B , the suggested information 225 displayed in the second progress image 220 includes information 226 regarding the estimated waiting time when switching to the priority dispatch mode, information 227 regarding the additional fee required to use the priority dispatch service, and a switch button 228 for switching to the priority dispatch mode. By presenting the information 226 regarding the estimated waiting time, user 2 can understand the difference in the estimated waiting time between maintaining the current normal dispatch mode (S120) and switching to the normal dispatch mode (S130). Taking this difference in estimated waiting time into consideration, user 2 can consider whether to switch to the priority dispatch mode. Furthermore, by presenting information 227 regarding the additional fee, user 2 can compare the difference in the estimated waiting time with the additional fee and appropriately consider whether to switch to the priority dispatch mode even if it means paying the additional fee. Note that the information 223 indicating the estimated waiting time may be other than text information indicating a specific number of hours, as shown in FIG. 17B , and may be, for example, an indicator, graph, graphic, icon, character image, or the like, indicating the level or progress of the estimated waiting time.

[0254] If user 2 checks the proposed information 225 presented in the second progress image 220 and decides to switch to the priority vehicle dispatch mode, user 2 taps switch button 228 in the second progress image 220. Then, user terminal 20 displays an application image 230 for the priority vehicle dispatch service shown in FIG. 18A on the display device 124. User 2 sets a payment method using change payment method button 231 on this application image 230 as necessary, and then taps confirm button 232 to instruct switching to the priority vehicle dispatch mode. If user 2 wishes to cancel the application for the priority vehicle dispatch service, user 2 taps back button 233 to return to the original second progress image 220 shown in FIG. 17B.

[0255] When user 2 taps the OK button 232 on the application image 230 for the priority vehicle dispatch service, the user terminal 20 transmits a command for a priority vehicle dispatch request (corresponding to a "vehicle dispatch request in priority vehicle dispatch mode") indicating a switch from normal vehicle dispatch mode to priority vehicle dispatch mode to the vehicle dispatch management server 60 (S232). Upon receiving the priority vehicle dispatch request command transmitted from the user terminal 20, the vehicle dispatch management server 60 begins executing a vehicle search process (S130) in priority vehicle dispatch mode. Next, immediately after the start of execution of the vehicle search process (S130), the vehicle dispatch management server 60 transmits a command for instructing the user terminal 20 to switch to a third image (S132). Upon receiving the third image switching command from the vehicle dispatch management server 60, the user terminal 20 displays a third progress image 240 shown in FIG. 18B on the display device 124 (S240).

[0256] 18B, the third progress image 240 includes text information "Searching for available vehicles in priority vehicle dispatch mode" as progress information 241 (third progress information) indicating that the vehicle search process (S130) in priority vehicle dispatch mode is being executed by the vehicle dispatch management server 60. By presenting this progress information 241, user 2 can recognize that the vehicle search process (S130) in priority vehicle dispatch mode is being executed successfully.

[0257] The third progress image 240 also displays information 242 (e.g., "0:01") indicating the elapsed time since the start of the vehicle search process (S130) in the priority vehicle dispatch mode in seconds, and information 243 indicating the estimated wait time (second estimated wait time) until vehicle dispatch is confirmed in response to User 2's vehicle dispatch request in minutes (e.g., "approximately 5 to 15 minutes"). By displaying this information 243 indicating the estimated wait time, User 2 can recognize that switching to the priority vehicle dispatch mode has reduced the vehicle dispatch wait time. Note that the information 243 indicating the estimated wait time may be other than text information indicating a specific number of hours as shown in FIG. 18B , and may be, for example, an indicator, graph, graphic, icon, character image, or the like indicating the level or transition of the estimated wait time.

[0258] Thereafter, the vehicle allocation management server 60 finds an available candidate vehicle through a search process (S130) in priority vehicle allocation mode, and when a vehicle to be allocated in response to the priority vehicle allocation request (S232) from the user terminal 20 is determined (S140), it transmits a vehicle allocation inquiry notice to the vehicle terminal of the vehicle to be allocated (S7). Next, when the vehicle terminal receives an acceptance response to the vehicle allocation inquiry notice (S8), the vehicle allocation management server 60 transmits a vehicle allocation completion notice to the vehicle terminal of the vehicle to be allocated and to the user terminal 20 (S9, S10). These processes (S7 to S10) are the same as those in Figure 7, and therefore redundant explanations will be omitted.

[0259] Once the vehicle dispatch is confirmed as described above and the user terminal 20 receives a dispatch completion notification (S10) from the vehicle dispatch management server 60, the fourth progress image 250 shown in FIG. 19 is displayed on the display device 124 (S300). The fourth progress image 250 includes text information such as "Vehicle has been arranged" as progress information 251 indicating that the vehicle dispatch by the vehicle dispatch management server 60 has been confirmed. By presenting this progress information 251, user 2 can recognize that the vehicle dispatch in the priority dispatch mode has been confirmed. The fourth progress image 250 also displays information 253 indicating the estimated arrival time of the vehicle to be dispatched at user 2's boarding location.

[0260] The vehicle search process (S110, S120, S130) and display control process (S112, S122, S132, S10) of the vehicle dispatch management server 60, which are features of this embodiment, have been described above. According to this embodiment, if the vehicle dispatch management server 60 cannot find an available vehicle during the vehicle search process (S110) in the normal dispatch mode, the vehicle dispatch management server 60 continues the continuous vehicle search process (S120) within a predetermined time limit. The display image on the user terminal 20 automatically switches from a simple first progress image 210 ( FIG. 16 ) for the vehicle search process (S110) to a more comprehensive second progress image 220 ( FIG. 17 ) for the continuous vehicle search process (S120). This second progress image 220 displays information useful to the user 2 waiting for a vehicle, such as the fact that the continuous vehicle search process (S120) is continuing, the estimated waiting time, the number of users waiting for a vehicle, and information 225 suggesting switching to the priority vehicle dispatch mode.

[0261] By displaying the second progress image 220 on the user terminal 20, the user 2 can be optionally suggested that the vehicle search process (S110, S120) in the normal vehicle dispatch mode can be continued while switching to the vehicle search process (S130) in the priority vehicle dispatch mode. Therefore, the user 2 can compare the option of continuing the vehicle search process (S110, S120) in the normal vehicle dispatch mode with the option of switching to the vehicle search process (S130) in the priority vehicle dispatch mode, and freely select the desired option at the desired timing. For example, a user 2 who is in a hurry due to an urgent matter or who cannot tolerate a long vehicle dispatch wait time can switch to the priority vehicle dispatch mode by paying an additional fee. On the other hand, a user 2 who wants to save on the additional fee even if it means waiting a relatively long vehicle dispatch wait time can maintain the normal vehicle dispatch mode and wait until the vehicle dispatch is confirmed or until the continuous vehicle dispatch process (S120) times out within a predetermined time limit.

[0262] Furthermore, according to this embodiment, the vehicle dispatch management server 60 continues the continuous vehicle search process (S120) in the normal vehicle dispatch mode without terminating it until the user 2 inputs a switch to the priority vehicle dispatch mode. Therefore, in some cases, even if the user 2 does not switch to the priority vehicle dispatch mode, there is a chance that an available vehicle will be found by luck in the continuous vehicle search process (S120) in the normal vehicle dispatch mode, and the vehicle dispatch will be confirmed.

[0263] Furthermore, by continuing to display the second progress image 220 on the user terminal 20, which indicates that the continuous vehicle search process (S120) is continuing, it is possible to appeal to the user 2 that the vehicle dispatch management server 60 is not terminating the continuous vehicle search process (S120) but is continuing to steadily search for vehicles over a long period of time.

[0264] Therefore, according to this embodiment, the satisfaction and convenience of user 2 can be significantly improved compared to the specification that completely terminates the vehicle search process as described above and then proposes switching to priority vehicle dispatch mode.

[0265] In the above embodiment, as shown in FIG. 17B, an example has been described in which the progress information 221 (first progress information) and the proposed information 225 (first proposed information) are simultaneously displayed in the same second progress image 220 on the user terminal 20. However, the present invention is not limited to this example. For example, the progress information 221 (first progress information) and the proposed information 225 (first proposed information) may be displayed separately in multiple images. Furthermore, the progress information 221 (first progress information) and the proposed information 225 (first proposed information) may be displayed at different times. Similarly, the information 223 indicating the predicted waiting time (first predicted waiting time) shown in FIG. 17B and the information 223 indicating the number of users waiting for a ride may be displayed in different images or at different times.

[0266] [3.2. Image control process that proposes canceling the setting conditions while the detection process is ongoing] Next, a modified example of the present embodiment shown in Fig. 14 will be described with reference to Fig. 20. Fig. 20 is a sequence diagram showing the flow of the search process according to the modified example of the present embodiment and the display control process according to the progress of the process.

[0267] As shown in Fig. 20, the processing flow of the modified example of this embodiment differs from the processing flow of the first embodiment described above (see Fig. 14) in the processes of S204, S224, S250, S252, S260, and S303 of the user terminal 20 and S110, S120, and S162 of the vehicle dispatch management server 60, but the other processes are substantially the same. Therefore, the following description will focus on these different processes. Note that, in the modified example of this embodiment shown in Fig. 20, as in the embodiment shown in Fig. 14, it is assumed that user 2 requests a vehicle dispatch during a busy time period or in a busy area where demand for vehicles exceeds supply.

[0268] 20 differs from the embodiment shown in Fig. 14 above in that, in the setting condition input process (S202), consider a case in which user 2 taps vehicle designation button 207 in the vehicle dispatch category setting image 205 shown in Fig. 15B to designate the vehicle to be dispatched (dispatch category) as "taxi," thereby limiting the setting condition of the vehicle dispatch category to only taxi vehicle 32 (first vehicle). In this case, user terminal 20 of user 2 transmits a normal vehicle dispatch request command with the setting condition designated as taxi added to vehicle dispatch management server 60 (S1).

[0269] When the vehicle dispatch management server 60 receives a command for a normal vehicle dispatch request (S1) with a setting condition specifying a taxi, it starts executing a vehicle search process (S110) in normal vehicle dispatch mode. In the vehicle search process (S110, S120), the vehicle dispatch management server 60 searches only for taxi vehicles 32 (first vehicles) as vehicles that match the normal vehicle dispatch request received from the user terminal 20, and does not search for NRS vehicles 42 (second vehicles). However, if there is a shortage of vacant taxi vehicles 32 during peak hours or in congested areas, it may be difficult to find a taxi vehicle 32 that matches the dispatch request in the vehicle search process (S110, S120) in normal vehicle dispatch mode specifying a taxi, which may increase the wait time for dispatch.

[0270] Therefore, while the vehicle dispatch management server 60 is continuously executing the vehicle detection process (S110, S120), it executes a display control process (S112, S124, S162) that controls the images displayed on the user terminal 20 in accordance with the progress of the vehicle detection process (S110, S120) (for example, the duration of the vehicle detection process). In accordance with the display control process (S112, S124, S162) by the vehicle dispatch management server 60, the user terminal 20 displays on the display device 124 a plurality of images (S210, S224, S260) that correspond to the progress of the vehicle detection process (S110, S120) that is being continued by the vehicle dispatch management server 60.

[0271] The display control process (S112, S124, S162) by the vehicle dispatch management server 60 includes a first display control process (S112), a second display control process, and a third display control process (S124). In a modification of this embodiment, the second display control process and the third display control process are executed simultaneously in one step (S124). However, this is not limiting, and the second display control process and the third display control process may be separated into separate steps and executed at different times.

[0272] In the first display control process (S122), after starting the search process (S110) in normal dispatch mode, the dispatch management server 60 displays an image (not shown) similar to the first progress image 210 shown in Figure 16 on the display device 124 of the user terminal 20.

[0273] On the other hand, in the second display control process and the third display control process (S124), when a predetermined time or more has elapsed since the start of the vehicle search process (S110) in the normal vehicle dispatch mode, the vehicle dispatch management server 60 causes the display device 124 of the user terminal 20 to display the second progress image 260 shown in FIG. 21A (S224). As shown in FIG. 21A, the second progress image 260 is an image including progress information 221 (first progress information), first proposal information 225, and second proposal information 262. As described above, the progress information 221 is information indicating that the vehicle dispatch management server 60 is currently executing the continuous vehicle search process (S120). As described above, the first proposal information 225 is information for proposing switching to the priority vehicle dispatch mode.

[0274] The second proposal information 262 is proposal information specific to the modified example of this embodiment, and is information for proposing the cancellation or change of the set conditions added to the normal vehicle dispatch request (S1) by user 2. For example, the second proposal information 262 may be information for proposing the cancellation or change of the set conditions for the vehicle dispatch category, and specifically, may be information for proposing the cancellation of the set condition for taxi designation. If the set condition for taxi designation is cancelled, it becomes easier to find a vehicle that matches the normal vehicle dispatch request received in S1 from both taxi vehicles 32 and NRS vehicles 42, thereby shortening the vehicle dispatch waiting time of user 2.

[0275] Furthermore, the setting conditions specified by User 2 may be, for example, a taxi company or vehicle attributes (e.g., sliding door compatible, wheelchair accessible, high-class vehicle, etc.) other than the example of specifying a dispatch category such as "specify taxi" above. When various setting conditions such as dispatch category, taxi company, and vehicle attributes are specified by User 2 in this way, some or all of these setting conditions may be able to be canceled. Canceling the various setting conditions makes it easier to find a vehicle that matches the normal dispatch request received in S1, which may further shorten User 2's waiting time for a dispatch.

[0276] Therefore, immediately after a predetermined time has elapsed since the start of execution of the vehicle detection process (S110) and the continuation vehicle detection process (S120) has begun, the vehicle dispatch management server 60 transmits a command to instruct the user terminal 20 to switch to the second image (S124). Upon receiving the command to instruct the user terminal 20 to switch to the second image from the vehicle dispatch management server 60, the user terminal 20 displays the second progress image 260 shown in Fig. 21A on the display device 124 (S224).

[0277] As shown in FIG. 21A, a second progress image 260 according to a modified example of this embodiment includes second proposal information 262 in addition to the various information included in the second progress image 220 according to the above embodiment (FIG. 17B) (e.g., progress information 221, predicted waiting time, number of people waiting for dispatch, first proposal information 225 for proposing switching to priority dispatch mode, etc.). The second proposal information 262 is information for proposing to cancel the setting conditions specified by user 2 when inputting the setting conditions (S204). In the example of FIG. 21A, the second proposal information 262 includes a cancel button 264 for canceling the setting condition of specifying a taxi.

[0278] When user 2 taps the set condition release button 264 on the vehicle dispatch request image 200, the user terminal 20 displays a set condition release image 270 shown in FIG. 21B on the display device 124. In this set condition release image 270, user 2 checks the set condition (for example, the set condition of specifying a taxi in the example of FIG. 21B) specified when setting the conditions before requesting a vehicle dispatch (S204), and then determines whether or not to release the set condition. If user 2 consequently wishes to maintain the original set condition, he or she can tap the back button 272 to return to the second progress image 260 shown in FIG. 21A. In this case, the vehicle dispatch management server 60 continues the continuous vehicle search process (S120) in the normal vehicle dispatch mode while maintaining the set condition.

[0279] On the other hand, if the user 2 wishes to cancel the set conditions in order to prioritize early vehicle allocation confirmation, the user taps the decision button 271 to cancel the set conditions. The user terminal 20 then transmits a condition change notification command to the vehicle allocation management server 60, instructing the cancellation of the set conditions that were set at the time of the vehicle allocation request (S252). Upon receiving the condition change notification command transmitted from the user terminal 20, the vehicle allocation management server 60 resumes execution of the continuous vehicle search process (S120) in the normal vehicle allocation mode with the set conditions canceled. For example, if the set condition specifying a taxi is canceled, the vehicle allocation management server 60 can search for both taxi vehicles 32 and NRS vehicles 42 as candidate vehicles to be allocated, making it easier to find candidate vehicles quickly.

[0280] Next, immediately after resuming the continuous vehicle search process (S120), the vehicle dispatch management server 60 transmits a fourth image switching command to the user terminal 20 (S162). Upon receiving the fourth image switching command from the vehicle dispatch management server 60, the user terminal 20 displays the fifth progress image 280 shown in Fig. 22A on the display device 124 (S260).

[0281] 22A, the fifth progress image 280 includes text information saying, "Since the conditions were lifted, we are searching for available vehicles, including RS vehicles," as progress information 281 indicating that the vehicle dispatch management server 60 is currently executing the continuous vehicle search process (S120) in the normal vehicle dispatch mode. By presenting this progress information 281, the user 2 can recognize that the continuous vehicle search process (S120) in the normal vehicle dispatch mode is continuing without any problems, even after the set conditions have been lifted.

[0282] Furthermore, the fifth progress image 280 displays information 282 in seconds indicating the elapsed time since the start of the resumed continuous vehicle search process (S120), and also displays information 283 in minutes (e.g., "approximately 10 to 20 minutes") indicating the predicted waiting time until vehicle allocation is confirmed in response to the vehicle allocation request of user 2. By presenting information 283 indicating this predicted waiting time, user 2 can recognize that the vehicle allocation waiting time has been reduced by canceling the set conditions.

[0283] Furthermore, the fifth progress image 280 also displays information 224 indicating the number of users 284 currently waiting for a ride with the same ride setting conditions (for example, a regular ride request and a taxi / ride share request) in the same area as user 2. By presenting information 284 indicating the number of users waiting for a ride, user 2 can more accurately grasp the specific number of other users waiting for a ride and the resulting degree of congestion in the ride distribution area.

[0284] Although not shown, it is preferable that when the fifth progress image 280 shown in Fig. 22A is slid upward, the first proposal information 225 (see Fig. 17B) for proposing switching to the priority vehicle dispatch mode described above is included in the fifth progress image 280. This makes it possible to cancel the set conditions (S250 in Fig. 20) and then switch to the priority vehicle dispatch mode (S230 in Fig. 14), thereby further shortening the vehicle dispatch waiting time.

[0285] Thereafter, the vehicle allocation management server 60 finds an available candidate vehicle through a search process (S130) in the normal vehicle allocation mode with the set conditions canceled, and when the vehicle to be allocated in response to the normal vehicle allocation request (S1) from the user terminal 20 is determined (S140), it transmits a vehicle allocation inquiry notice to the vehicle terminal of the vehicle to be allocated (S7). Next, when the vehicle terminal receives an acceptance response to the vehicle allocation inquiry notice (S8), the vehicle allocation management server 60 transmits a vehicle allocation completion notice to the vehicle terminal of the vehicle to be allocated and to the user terminal 20 (S9, S10). These processes (S7 to S10) are the same as those in Figure 7, and therefore detailed explanations will be omitted.

[0286] Once the vehicle allocation is confirmed as described above and the user terminal 20 receives a vehicle allocation completion notification (S10) from the vehicle allocation management server 60, the sixth progress image 290 shown in FIG. 22B is displayed on the display device 124 (S302). The sixth progress image 290 includes text information such as "Vehicle allocation has been arranged" as progress information 291 indicating that the vehicle allocation by the vehicle allocation management server 60 has been confirmed. The sixth progress image 290 also displays text information such as "The ride-share vehicle is scheduled to arrive" as information 292 indicating the category of the vehicle to be allocated. This allows user 2 to recognize that the vehicle allocation has been confirmed early by canceling the setting conditions in S250 and that the NRS vehicle 42 will be dispatched. The sixth progress image 290 also displays information 293 indicating the drop-off location (destination) specified by user 2 and the fare of the NRS vehicle 42 from the boarding location to the drop-off location (destination). The information 293 allows the user 2 to confirm the fare and destination of the NRS vehicle 42 before boarding. If the user 2 agrees to board the NRS vehicle 42 as a result of this confirmation, the user 2 can tap the confirmation button 294 to confirm the dispatch of the NRS vehicle 42. Note that the dispatch of the NRS vehicle 42 may be automatically confirmed without the user 2 performing a user operation such as tapping the confirmation button 294.

[0287] As described above, according to the modified example of this embodiment, the second progress image 260 shown in FIG. 21A simultaneously displays the first proposal information 225 for proposing switching to the priority vehicle dispatch mode and the second proposal information 262 for proposing the cancellation of the set conditions. This allows user 2 to easily recognize that there are two methods for reducing vehicle dispatch wait time: "switching to the priority vehicle dispatch mode" and "cancelling the set conditions for the specified vehicle." Therefore, user 2 can appropriately compare and consider which of the two methods to adopt, or whether to continue the vehicle search process in the normal vehicle dispatch mode without adopting either method. Therefore, when vehicle dispatch takes a long time during a peak time period or in a congested area, user 2 can be provided with three options, further improving user 2's convenience and satisfaction.

[0288] The procedure for displaying multiple types of proposed information is not limited to the example shown in FIG. 21A in which the first proposed information 225 (proposal for priority vehicle dispatch) and the second proposed information 262 (proposal for canceling the set conditions) are simultaneously displayed on the user terminal 20. For example, in a case where a vehicle dispatch request is searched for with a set condition specifying only a taxi, if a vehicle dispatch is not determined in the initial vehicle dispatch process (S110), only the second proposed information 262 proposing the cancellation of the set conditions may be displayed on the user terminal 20, and the first proposed information 225 proposing switching to the priority vehicle dispatch mode may not be displayed. After that, if the user 2 cancels the set conditions in accordance with the second proposed information 262 but a vehicle dispatch is still not determined in the continuous vehicle dispatch process (S120), the first proposed information 225 proposing switching to the priority vehicle dispatch mode may be displayed on the user terminal 20. This allows the user 2 to first be first suggested to cancel the free set conditions, and only if a vehicle dispatch is still not determined, to gradually suggest switching to the paid priority vehicle dispatch mode. By displaying multiple types of proposed information in stages in this manner, User 2 can feel satisfied with the price and also feel satisfied with the multiple types of proposals being presented in stages to shorten the waiting time for vehicle dispatch.

[0289] [3.3. Summary of the third embodiment] (1) As described above, according to the third embodiment of the present invention, there is provided a user terminal 20 that is communicatively connected via a network 6 to a vehicle dispatch management device (e.g., a vehicle dispatch management server 60) that dispatches a vehicle selected from a plurality of vehicles, and the user terminal 20, wherein the user terminal 20 has one or more processors (e.g., the processor of the processing device 122), and the processor executes a transmission process (S1) that transmits a vehicle dispatch request to the vehicle dispatch management device in accordance with the specification of user 2, wherein the plurality of vehicles includes at least one first vehicle (e.g., taxi vehicle 32) driven by a first driver and at least one second vehicle (e.g., NRS vehicle 42) driven by a second driver (e.g., NRS driver 4) who has a different type of driving qualification from the first driver (e.g., taxi driver 3), and the transmission process (S1) is capable of transmitting a first vehicle dispatch request to the vehicle dispatch management device as a vehicle dispatch request, designating both the first vehicle and the second vehicle as vehicles to be dispatched in accordance with the specification of user 2.

[0290] With this configuration, when user 2 makes a vehicle dispatch request (S1), he or she can specify both the first vehicle (e.g., taxi vehicle 32) and the second vehicle (e.g., NRS vehicle 42) as vehicles to be dispatched. Therefore, the vehicle dispatch management device (e.g., vehicle dispatch management server 60) can find one vacant vehicle from among a large number of candidate vehicles including the first vehicle and the second vehicle, and quickly dispatch the vehicle to user 2. This can improve the satisfaction of user 2.

[0291] (2) In the transmission process (S1), a second vehicle dispatch request that designates only the first vehicle as the vehicle to be dispatched may be transmitted to the vehicle dispatch management device as a vehicle dispatch request, instead of the first vehicle dispatch request, in accordance with the designation of user 2. With this configuration, user 2 can designate only the first vehicle (e.g., taxi 32) as the vehicle to be dispatched when making a vehicle dispatch request. Therefore, the vehicle dispatch management device (e.g., vehicle dispatch management server 60) can find one available first vehicle (e.g., taxi 32) and appropriately dispatch the first vehicle (e.g., taxi 32) of the type desired by user 2 to user 2. This can further improve user 2 satisfaction.

[0292] (3) In the transmission process (S1) at the time of the first vehicle dispatch request, a first vehicle dispatch request (designating a taxi or ride share) can be sent to the vehicle dispatch management device according to the designation of user 2. In the transmission process (S13 in FIG. 12) at the time of a second or subsequent vehicle re-dispatch request, or in the transmission process (S232 in FIG. 14) at the time of a chargeable vehicle dispatch request involving an additional fee (e.g., a priority vehicle dispatch request), a second vehicle dispatch request (designating only a taxi) may be sent as a vehicle dispatch request to the vehicle dispatch management device. With this configuration, at the time of the first vehicle dispatch request (S1), user 2 can designate both a first vehicle (e.g., taxi vehicle 32) and a second vehicle (e.g., NRS vehicle 42) as vehicles to be dispatched and request a vehicle dispatch (first vehicle dispatch request). On the other hand, when making a second or subsequent vehicle re-allocation request (S13 in FIG. 12) or a charging vehicle allocation request involving an additional fee (S232 in FIG. 14), the user terminal 20 can automatically designate only the first vehicle (e.g., taxi 32) as the vehicle to be allocated and request a vehicle allocation (second vehicle allocation request), regardless of whether or not the user 2 has specified a vehicle type. This allows the first vehicle (e.g., taxi 32) to be allocated preferentially for a vehicle re-allocation request (S13 in FIG. 12) or a charging vehicle allocation request (S232 in FIG. 14) compared to the initial vehicle allocation request (S1). Therefore, the user 2 making a vehicle re-allocation request or a charging vehicle allocation request can be treated more preferentially than other users, and a high-quality driving service using the first vehicle (e.g., taxi 32) can be provided to the user 2. This further improves the satisfaction of the user 2.

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

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

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

[0296] 1. Vehicle dispatch management system 2 users 3 Taxi Driver (First Driver) 4 NRS driver (second 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 vehicle dispatch management system including a plurality of user terminals and a vehicle dispatch management device communicably connected to the user terminals via a network, The user terminal one or more first processors; The vehicle dispatch management device one or more second processors; The first processor of the user terminal: A process of transmitting a vehicle dispatch request to the vehicle dispatch management device in response to a user input. Run The second processor of the vehicle dispatch management device A vehicle allocation process for allocating a vehicle in response to the vehicle allocation request received from the user terminal based on an evaluation criterion related to the driver's driving. Run In the vehicle dispatch process, When the vehicle dispatch request is a charging vehicle dispatch request that increases the priority of vehicle dispatch by charging an additional fee, a vehicle of a driver who satisfies the evaluation criterion is assigned to the charging vehicle dispatch request. Vehicle dispatch management system.

2. A vehicle dispatch management device communicably connected to a user terminal via a network, The vehicle dispatch management device one or more processors; The processor: A vehicle allocation process for allocating a vehicle in response to a vehicle allocation request received from the user terminal based on an evaluation criterion related to the driver's driving. Run In the vehicle dispatch process, When the vehicle dispatch request is a charging vehicle dispatch request that increases the priority of vehicle dispatch by charging an additional fee, the vehicle dispatch management device assigns a vehicle of a driver who satisfies the evaluation criteria to the charging vehicle dispatch request.

3. In the vehicle dispatch process, 3. The vehicle dispatch management device according to claim 2, wherein, when the vehicle dispatch request is a charging vehicle dispatch request, a vehicle of a driver who does not satisfy the evaluation criteria is not assigned to the charging vehicle dispatch request, or the allocation priority of the vehicle is lowered.

4. In the vehicle dispatch process, The vehicle allocation management device according to claim 2 , wherein when the vehicle allocation request is not a charging vehicle allocation request, a vehicle is allocated to the vehicle allocation request regardless of the evaluation criterion.

5. The vehicle dispatch management device according to claim 2 , wherein the evaluation criteria include criteria related to the driver's driving qualifications.

6. The evaluation criteria are: the driver's driving experience, the driving education the driver received; Driver's traffic violation history, User ratings of the driver, and Driver's driving score calculated by driving analysis software The vehicle dispatch management device according to claim 2 , further comprising criteria relating to at least one of the following:

7. The vehicle dispatch management device according to claim 2 , wherein the charging vehicle dispatch request includes a priority vehicle dispatch request that, by charging the additional fee, gives a higher priority to vehicle dispatch than a normal vehicle dispatch request that does not involve charging the additional fee.

8. The vehicle dispatch management device according to claim 2 , wherein the charging vehicle dispatch request includes a reservation vehicle dispatch request in which a desired boarding date and time can be specified in advance by charging the additional fee.

9. A vehicle dispatch management method executed by a computer, comprising: A vehicle dispatch process that allocates vehicles to dispatch requests received from user terminals based on evaluation criteria related to the driver's driving. Including, In the vehicle dispatch process, A vehicle dispatch management method in which, when the vehicle dispatch request is a charging vehicle dispatch request that increases the priority of vehicle dispatch by charging an additional fee, a vehicle of a driver who satisfies the evaluation criteria is assigned to the charging vehicle dispatch request.

10. A vehicle dispatch process that allocates vehicles to dispatch requests received from user terminals based on evaluation criteria related to the driver's driving. A program for causing a computer to execute the above, In the vehicle dispatch process, When the vehicle dispatch request is a charging vehicle dispatch request that increases the priority of vehicle dispatch by charging an additional fee, the program allocates a vehicle of a driver who satisfies the evaluation criteria to the charging vehicle dispatch request.

11. A vehicle dispatch management device that dispatches a vehicle selected from a plurality of vehicles, and a user terminal that is communicably connected via a network, The user terminal one or more processors; The processor: A transmission process for transmitting a vehicle dispatch request according to a user's specification to the vehicle dispatch management device. Run The plurality of vehicles include: at least one first vehicle driven by a first driver; at least one second vehicle driven by a second driver having a different type of driving qualification than the first driver; Including, In the transmission process, A user terminal capable of transmitting a first vehicle dispatch request, which designates both the first vehicle and the second vehicle as vehicles to be dispatched, to the vehicle dispatch management device as the vehicle dispatch request in accordance with the user's designation.

12. In the transmission process, The user terminal of claim 11, wherein, in accordance with the user's specification, a second dispatch request that designates only the first vehicle as the vehicle to be dispatched, instead of the first dispatch request, can be sent to the dispatch management device as the dispatch request.

13. In the transmission process at the time of a first vehicle dispatch request, the first vehicle dispatch request can be transmitted to the vehicle dispatch management device in accordance with a designation by the user, The user terminal of claim 12, wherein in the transmission process when a second or subsequent re-dispatch request is made, or in the transmission process when a charged dispatch request is made involving an additional fee, the second dispatch request is transmitted to the dispatch management device as the dispatch request.

Images