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

Abstract

To improve user satisfaction and convenience when vehicle dispatch is difficult during congested time periods.SOLUTION: In a dispatch management system 1, a user terminal 20 executes processing for transmitting a dispatch request to a dispatch management server 60 in response to input from a user 2. The dispatch management server 60 executes: a vehicle searching process (S110, S120) for searching for a vehicle that matches the dispatch request received from the user terminal 20; and a display control process (S112, S122, S132) for controlling information displayed on the user terminal 20 according to the progress of the vehicle searching process. The vehicle searching process includes a normal dispatch mode and a priority dispatch mode having a higher dispatch priority than the normal dispatch mode. In the display control process, the user terminal 20 displays, during continuation of the vehicle searching process in the normal dispatch mode, first progress information 221 indicating that the vehicle searching process in the normal dispatch mode is being continuously executed, and first proposal information 225 for proposing switching to the priority dispatch mode.SELECTED DRAWING: Figure 11

Description

[Technical Field]

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

[0002] There are known technologies for dispatching a taxi in response to a user's request for dispatching a taxi. For example, Patent Document 1 discloses a technology for estimating the arrival times of the user and the taxi at the user's desired boarding location, matching the estimated results, and dispatching a taxi so as to minimize the difference between the estimated results. [Prior art documents] [Patent documents]

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

[0004] Recently, the shortage of taxi drivers has become a serious problem in some regions. As a result, there are areas where the supply of taxis is insufficient to meet the demand for taxi dispatch. As a result, the introduction of ride-sharing (Japanese-style ride-sharing), in which ordinary drivers use their own cars to transport users for a fee, is progressing.

[0005] In times and areas where there is sufficient supply to meet the demand for dispatched vehicles such as taxis, it is possible to quickly search for vehicles available for dispatch in the vicinity in response to a user's dispatch request and confirm the dispatch. On the other hand, in congested times and areas (for example, times and areas with excessive demand where there is a high demand for dispatched vehicles but not enough supply), even if an available vehicle is searched for, there may be a delay in dispatching a vehicle to a user's dispatch request.

[0006] In this regard, in the taxi business and the like, during peak hours or in congested areas where the supply of vehicles is insufficient to meet the demand for vehicles as described above, it is conceivable to provide a priority vehicle dispatch service in which users pay an additional fee in addition to the regular fare, and are given priority over other users in dispatching vehicles. Users who use this priority vehicle dispatch service and pay the additional fee can receive a vehicle earlier than users who make regular vehicle dispatch requests that do not involve the payment of an additional fee. Therefore, for users who need to get into a taxi or the like in a hurry, it is useful to specify the use of the priority vehicle dispatch service when initially requesting a vehicle dispatch.

[0007] Another possible use case of the priority vehicle dispatch service is when a user who has made a normal vehicle dispatch request during the above-mentioned busy hours or in a congested area realizes from information such as the vehicle dispatch wait time displayed on the user terminal that it will take a long time to confirm the dispatch, and switches from the original normal vehicle dispatch request to a vehicle dispatch request using the priority vehicle dispatch service (hereinafter referred to as a "priority vehicle dispatch request"). In this use case, even if the vehicle dispatch management system performs a vehicle search process for the normal vehicle dispatch request, if the vehicle to be dispatched cannot be found, it is possible to temporarily halt the vehicle search process and display an image on the user terminal suggesting switching to a priority vehicle dispatch request.

[0008] However, with this specification, if a vehicle to be dispatched is found and dispatch is confirmed immediately after the user switches to a priority vehicle dispatch request in accordance with the proposed image, the user may have negative feelings, such as suspicion that the vehicle dispatch would have been confirmed even if the user had not switched to a priority vehicle dispatch request, or reluctance to pay the additional fee for the priority vehicle dispatch service, which could reduce the user's satisfaction and sense of acceptance.In addition, with the specification that proposes switching to a priority vehicle dispatch request after terminating the vehicle search process as described above, the user is limited to two options: switching to a priority vehicle dispatch request or canceling the original regular vehicle dispatch request, and is unable to select the option of continuing the vehicle search process while maintaining the original regular vehicle dispatch request, which is inconvenient.

[0009] Therefore, in conventional vehicle dispatch management systems, there was a desire to improve user satisfaction and convenience, including by providing priority vehicle dispatch services when vehicle dispatch is difficult during peak hours, etc.

[0010] 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, a user terminal, and a vehicle dispatch request method that can improve user satisfaction and convenience when vehicle dispatch is difficult during peak hours, etc. [Means for solving the problem]

[0011] In order to solve the above-mentioned problems, according to one aspect of the present invention, there is provided 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, wherein the user terminals include one or more first processors and a display device, and the vehicle dispatch management device includes one or more second processors, wherein the first processor of the user terminal executes a process of transmitting a vehicle dispatch request to the vehicle dispatch management device in response to a user input, and the second processor of the vehicle dispatch management device executes a vehicle search process of searching for a vehicle that matches the vehicle dispatch request received from the user terminal from among a plurality of vehicles, and and a display control process for controlling information displayed on the user terminal, wherein the first processor of the user terminal executes a process for displaying information on the display device in accordance with the display control process by the vehicle dispatch management device, the modes of the vehicle detection process include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatching is higher than that of the normal vehicle dispatch mode, and the display control process causes the user terminal to display first progress information indicating that the vehicle detection process in the normal vehicle dispatch mode is being continuously executed and first proposal information for proposing switching to the priority vehicle dispatch mode while the vehicle detection process in the normal vehicle dispatch mode is continuing.

[0012] In addition, 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 that execute a search process for searching for a vehicle that matches a vehicle dispatch request received from the user terminal from among a plurality of vehicles, and a display control process that controls information displayed on the user terminal depending on the progress of the search process, the modes of the search process include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatching is higher than that of the normal vehicle dispatch mode, and the display control process displays on the user terminal first proposal information for proposing switching to the priority vehicle dispatch mode, together with first progress information indicating that the search process in the normal vehicle dispatch mode is being continuously executed, while the search process in the normal vehicle dispatch mode is continuing.

[0013] The display control process may include a first display control process that, after the vehicle detection process in the normal vehicle dispatch mode starts to be executed, causes the user terminal to display second progress information indicating that the vehicle detection process in the normal vehicle dispatch mode is being executed, and a second display control process that, while the vehicle detection process in the normal vehicle dispatch mode is continuing, causes the user terminal to display the first proposal information together with the first progress information when a predetermined time or more has elapsed since the start of the vehicle detection process.

[0014] The plurality of vehicles may include at least one first vehicle driven by a first driver and at least one second vehicle driven by a second driver having a different type of driving qualification from the first driver, and when a setting condition specifying the first vehicle as the vehicle to be dispatched is added to the dispatch request received from the user terminal, the display control process may include a third display control process that causes the user terminal to display second proposal information for proposing the cancellation or change of the setting condition when a predetermined time or more has elapsed since the start of the vehicle detection process while the vehicle detection process is continuing.

[0015] In the second display control process, together with the first progress information and the first proposal information, information representing the number of users waiting for a ride in the same area as the user of the user terminal with the same ride setting conditions as the user may be displayed on the user terminal.

[0016] In the second display control process, together with the first progress information and the first proposal information, information representing a first predicted waiting time until dispatch is confirmed if the vehicle search process is continued in the normal vehicle dispatch mode may be displayed on the user terminal.

[0017] The first proposal information may include information indicating a second predicted waiting time until vehicle dispatch is confirmed when the mode is switched to the priority vehicle dispatch mode.

[0018] The processor may further perform the following processes: after displaying the first progress information and the first proposal information on the user terminal while the vehicle search process in the normal vehicle dispatch mode is continuing through the display control process; receiving a vehicle dispatch request in the priority vehicle dispatch mode from the user terminal; and executing the vehicle search process in the priority vehicle dispatch mode in response to the vehicle dispatch request in the priority vehicle dispatch mode received from the user terminal.

[0019] In addition, 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 search process for searching for a vehicle from among a plurality of vehicles that matches a vehicle dispatch request received from a user terminal, and a display control process for controlling information displayed on the user terminal depending on the progress of the search process, wherein the modes of the search process include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of dispatching is higher than that of the normal vehicle dispatch mode, and the display control process displays on the user terminal first proposal information for proposing switching to the priority vehicle dispatch mode, together with first progress information indicating that the search process in the normal vehicle dispatch mode is being continuously executed, while the search process in the normal vehicle dispatch mode is continuing.

[0020] In addition, 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 search process that searches for a vehicle from among a plurality of vehicles that matches a vehicle dispatch request received from a user terminal, and a display control process that controls information displayed on the user terminal depending on the progress of the vehicle search process, wherein the modes of the vehicle search process include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatch is higher than that of the normal vehicle dispatch mode, and the display control process displays on the user terminal first proposal information that suggests switching to the priority vehicle dispatch mode, along with first progress information indicating that the vehicle search process in the normal vehicle dispatch mode is being continuously executed, while the vehicle search process in the normal vehicle dispatch mode is continuing.

[0021] In addition, 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 to a vehicle dispatch management device via a network, the user terminal comprising one or more processors and a display device, the processor executing a process of sending a vehicle dispatch request to the vehicle dispatch management device in accordance with user input, and a process of displaying information on the display device in accordance with display control processing by the vehicle dispatch management device, the modes of vehicle detection processing by the vehicle dispatch management device include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatching is higher than that of the normal vehicle dispatch mode, and in the process of displaying information on the display device, while the vehicle detection processing in the normal vehicle dispatch mode is continuing, first proposal information for proposing switching to the priority vehicle dispatch mode is displayed on the display device together with first progress information indicating that the vehicle detection processing in the normal vehicle dispatch mode is being continuously executed.

[0022] the processor displays the first proposed information together with the first progress information on the display device by the process of displaying information on the display device, and then transmits a dispatch request in the priority dispatch mode to the vehicle dispatch management device in response to an input from the user. may be further executed.

[0023] In addition, in order to solve the above problem, according to another aspect of the present invention, there is provided a vehicle dispatch request method executed by a computer, which executes a process of sending a vehicle dispatch request to a vehicle dispatch management device in accordance with user input, and a display process of displaying information on a display device in accordance with display control processing by the vehicle dispatch management device, wherein the modes of vehicle detection processing by the vehicle dispatch management device include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatching is higher than that of the normal vehicle dispatch mode, and in the display process, while the vehicle detection processing in the normal vehicle dispatch mode executed by the vehicle dispatch management device continues, first proposal information for proposing switching to the priority vehicle dispatch mode is displayed on the display device together with first progress information indicating that the vehicle detection processing in the normal vehicle dispatch mode is being continuously executed.

[0024] In addition, in order to solve the above problem, according to another aspect of the present invention, there is provided a vehicle dispatch request method, which causes a computer to execute a process of sending a vehicle dispatch request to a vehicle dispatch management device in accordance with user input, and a display process of displaying information on a display device in accordance with display control processing by the vehicle dispatch management device, wherein the modes of vehicle detection processing by the vehicle dispatch management device include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatching is higher than that of the normal vehicle dispatch mode, and in the display process, while the vehicle detection processing in the normal vehicle dispatch mode executed by the vehicle dispatch management device continues, first proposal information for proposing switching to the priority vehicle dispatch mode is displayed on the display device together with first progress information indicating that the vehicle detection processing in the normal vehicle dispatch mode is being continuously executed. [Effects of the Invention]

[0025] According to the present invention, it is possible to improve user satisfaction and convenience when vehicle dispatch is difficult during peak hours or the like. [Brief explanation of the drawings]

[0026] [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] FIG. 10 is an explanatory diagram showing an example of a display image of a user terminal when requesting vehicle dispatch according to the embodiment. [Figure 11] FIG. 11 is a sequence diagram showing the flow of the vehicle detection process according to the embodiment and the display control process according to the progress of the vehicle detection process. [Figure 12] 12A and 12B are diagrams illustrating an example of a display image of a user terminal when requesting vehicle allocation according to the embodiment. [Figure 13] FIG. 13 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 14] 14A and 14B 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 15] 15A and 15B 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 16] FIG. 16 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 17] FIG. 17 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 18] 18A and 18B 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 embodiment. [Figure 19] 19A and 19B 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

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

[0028] [1. First embodiment] [1.1. Vehicle dispatch management system configuration] First, the overall configuration of a vehicle dispatch management system 1 according to a first embodiment of the present invention 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0045] As shown in Figure 7, the vehicle dispatch request method of this embodiment includes a vehicle dispatch request process (S1), a vehicle dispatch request accumulation process (S2), a vehicle dispatch request extraction process (S3), a vehicle extraction process (S4), a pair generation process (S5), a matching process (S6), a vehicle dispatch inquiry notification process (S7), an acceptance response process (S8), and a vehicle dispatch completion notification process (S9, S10).

[0046] Among these processes (S1) to (S10), processes (S2) to (S6) correspond to an example of a "vehicle allocation process." The "vehicle allocation process" is a process of searching for at least one vehicle (candidate vehicle) that matches a vehicle allocation request from among a plurality of vacant vehicles (vehicle search process), determining one vehicle (vehicle to be allocated) from among the searched vehicles (candidate vehicles), and allocating it to the vehicle allocation request. The "vehicle search process" is a process of the above-mentioned "vehicle allocation process" that searches for a vehicle (candidate vehicle) that matches a vehicle allocation request from among a plurality of vacant vehicles. The "continuous vehicle search process" is a process of the "vehicle search process" that continuously searches for at least one vehicle (candidate vehicle) that matches a vehicle allocation request even after a predetermined time has elapsed since the start of execution of the "vehicle search process." The "vehicle to be allocated" is a vehicle that is ultimately determined as a vehicle to be allocated for one vehicle allocation request. The "candidate vehicle" is a vehicle that is a candidate for a vehicle to be allocated, and is at least one vehicle that is allocated for one vehicle allocation request.

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

[0048] The setting items include the initial set-up request for dispatch, as well as, for example, boarding location, disembarking location, payment information, dispatch category, taxi company, vehicle attributes, etc.

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

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

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

[0052] Here, a dispatch mode in which a taxi vehicle 32 (first vehicle) is assigned in response to a dispatch request but a vehicle with a requirement (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 a requirement (second vehicle) is assigned in response to a dispatch request is referred to as a second dispatch mode. User 2 can transition from the first dispatch mode to the second dispatch mode by inputting information regarding the boarding location, the drop-off 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 a requirement" as the dispatch category. Therefore, even if information regarding the drop-off 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 use of the vehicle (e.g., use for business) 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 automatically targeted for dispatch (first dispatch mode). If user 2 does not input a 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.

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

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

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

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

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

[0058] (Vehicle extraction process S4) The vehicle dispatch unit 172 extracts one or more vehicles that satisfy predetermined extraction conditions related to the vehicle dispatch request extracted in the vehicle dispatch request extraction process S3 from among multiple vehicles that can accommodate the user 2. Here, the extraction conditions include the conditions of the various setting items in the vehicle dispatch request, such as the vehicle dispatch category. If the vehicle dispatch category in the vehicle dispatch request is set to "taxi vehicles 32 only," the vehicle dispatch unit 172 extracts only taxi vehicles 32 for the vehicle dispatch request. If the vehicle dispatch category in the vehicle dispatch request is set to "taxi vehicles 32 and vehicles with special requirements," the vehicle dispatch unit 172 extracts taxi vehicles 32 and vehicles with special requirements for the vehicle dispatch request. Another extraction condition is, for example, that the estimated time of arrival at the boarding location is short. Specifically, the extraction condition is, for example, that the distance between the boarding location and the vehicle's current location is within a predetermined distance (e.g., 10 km), or that the estimated time of arrival at the boarding location is within a predetermined time (e.g., 10 minutes). In this case, the distance is the Euclidean distance between the boarding location and the current location of the vehicle, and the estimated arrival time is the time obtained by dividing the Euclidean distance by a predetermined speed (for example, the average speed when the vehicle is operating). Furthermore, the vehicle dispatch unit 172 may further limit the number of vehicles to be extracted to a predetermined number (for example, 10 vehicles) as an extraction condition in order of the shortest distance between the boarding location and the current location of the vehicle or the shortest estimated arrival time at the boarding location.

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

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

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

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

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

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

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

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

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

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

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

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

[0071] [1.8. Priority Vehicle Allocation] Next, a priority vehicle dispatch service in the vehicle dispatch management system 1 according to this embodiment and a vehicle dispatch process for a priority vehicle dispatch request to realize this service will be described.

[0072] In the vehicle dispatch management system 1 according to this embodiment, a user 2 can use the priority vehicle dispatch service, for example, when he or she wants to board a taxi or the like during peak hours or in a congested area, or when he or she needs to board a taxi or the like in a hurry. Here, peak hours and congested areas refer to times and areas where vehicle dispatch is difficult due to a shortage of vehicle supply, and include, for example, not only times and areas with high demand for vehicle dispatch but also late-night hours, rural areas, and depopulated areas where the supply of vehicle dispatch is extremely low.

[0073] A priority vehicle dispatch service is useful when riding in a taxi or the like during such busy hours or in a congested area. The priority vehicle dispatch service is a service that allows the user 2 to increase the priority of vehicle dispatch over other normal vehicle dispatch requests by charging an additional priority vehicle dispatch fee. In the vehicle dispatch management system 1, when a vehicle dispatch request sent from the user terminal 20 to the vehicle dispatch management server 60 is a priority vehicle dispatch request, the vehicle dispatch management server 60 searches for and dispatches candidate vehicles for the priority vehicle dispatch request, giving priority over other normal vehicle dispatch requests.

[0074] When requesting vehicle dispatch using the user terminal 20, the user 2 can select a desired vehicle dispatch request from multiple types of vehicle dispatch requests. For example, the user 2 can select either a priority vehicle dispatch request or a regular vehicle dispatch request depending on whether or not an additional fee is to be paid (charged). A priority vehicle dispatch request is a vehicle dispatch request that requires payment of an additional fee (e.g., a priority vehicle dispatch arrangement fee) in addition to the basic fee. On the other hand, a regular vehicle dispatch request is a vehicle dispatch request that does not require payment of the predetermined additional fee (charged). A priority vehicle dispatch request has a higher priority in the vehicle dispatch processing by the vehicle dispatch management server 60 than a regular vehicle dispatch request. In other words, in the vehicle search processing that searches for candidate vehicles for the vehicle dispatch request, the priority of searching for candidate vehicles that match the vehicle dispatch request is higher.

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

[0076] Here, with reference to the above-mentioned FIG. 7, the vehicle allocation process (S2 to S6) for a normal vehicle allocation request and the vehicle allocation process for a priority vehicle allocation request will be described in detail.

[0077] When making an initial vehicle dispatch request (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. When making a vehicle dispatch request, for example, a setting image 100 for setting the type of vehicle dispatch request, as shown in FIG. 10, is displayed on the display device 124 of the user terminal 20. In this setting image 100, user 2 can select a desired vehicle dispatch request from multiple types of vehicle dispatch requests, such as "normal vehicle dispatch," "priority vehicle dispatch," and "reserved vehicle dispatch," and then tap the confirm button 104 to make the vehicle dispatch request. For example, when user 2 taps and selects the "normal vehicle dispatch" button 101, the user terminal 20 transmits a normal vehicle dispatch request to the vehicle dispatch management server 60 for searching for a vehicle in normal vehicle dispatch mode. When user 2 taps and selects the "priority vehicle dispatch" button 102, the user terminal 20 transmits a priority vehicle dispatch request to the vehicle dispatch management server 60 for searching for a vehicle in priority vehicle dispatch mode. Furthermore, when user 2 taps and selects the "reserve vehicle dispatch" button 103 and sets the desired boarding date and time, boarding location, etc. on another setting screen (not shown), user terminal 20 transmits a vehicle dispatch request, together with the desired boarding date and time, boarding location, etc., to vehicle dispatch management server 60. In this way, user 2 can select a desired vehicle dispatch request from multiple types of vehicle dispatch requests and request a vehicle dispatch by inputting information into user terminal 20. Note that, although the above describes an example in which user 2 can select priority vehicle dispatch when making an initial vehicle dispatch request (S1 in FIG. 7), the present invention is not limited to such an example. For example, user 2 may be prevented from selecting priority vehicle dispatch when making an initial vehicle dispatch request (S1 in FIG. 7), and user 2 may be allowed to select priority vehicle dispatch when the subsequent vehicle search process (S120 in FIG. 11), which will be described later, is executed.

[0078] Next, the vehicle allocation unit 172 of the vehicle allocation management server 60 executes the above-mentioned vehicle allocation process when it receives a vehicle allocation request from the user terminal 20. The vehicle allocation unit 172 switches the vehicle allocation mode executed in the vehicle allocation process based on whether the vehicle allocation request received from the user terminal 20 is a priority vehicle allocation request or a normal vehicle allocation request.

[0079] The vehicle dispatch mode is a vehicle search mode executed in the vehicle dispatch process. The vehicle dispatch mode corresponds to a "vehicle search process mode." The vehicle dispatch mode includes a normal vehicle dispatch mode and a priority vehicle dispatch mode.

[0080] The normal vehicle dispatch mode is a vehicle dispatch mode performed for normal vehicle dispatch requests. In the normal vehicle dispatch mode, as shown in Figure 7, the vehicle dispatch unit 172 executes the above-mentioned vehicle dispatch request accumulation process (S2), vehicle dispatch request extraction process (S3), vehicle extraction process (S4), pair generation process (S5), and matching process (S6). In the normal vehicle dispatch mode, the vehicle dispatch unit 172 matches multiple normal vehicle dispatch requests accumulated over a predetermined period with multiple vehicles at once through these processes (S2 to S6), and determines the vehicle to be dispatched for each vehicle dispatch request 22.

[0081] In contrast, the priority vehicle allocation mode is a vehicle allocation mode performed in response to a priority vehicle allocation request, and is a vehicle allocation mode in which the priority of vehicle allocation is higher than in the normal vehicle allocation mode. In the priority vehicle allocation mode, for example, the vehicle allocation unit 172 performs a vehicle search process in the priority vehicle allocation mode without performing the processes (S2, S3, S4, and S6 shown in FIG. 7) performed in response to a normal vehicle allocation request in the normal vehicle allocation mode described above, thereby preferentially allocating a vehicle to the priority vehicle allocation request.

[0082] In detail, the vehicle allocation unit 172 distinguishes between other normal vehicle allocation requests and priority vehicle allocation requests stored in the storage device 164, and searches for candidate vehicles for priority vehicle allocation requests before normal vehicle allocation requests to determine a vehicle to be allocated. At this time, for a priority vehicle allocation request, at least one candidate vehicle that meets the set conditions (e.g., vehicle allocation category, sliding door compatibility, etc.) specified by user 2 at the time of the priority vehicle allocation request is extracted from available vehicles, and a vehicle that is closest to user 2's boarding location is determined as the vehicle to be allocated from among the extracted candidate vehicles. Meanwhile, for other normal vehicle allocation requests, for example, the vehicle search process (S2 to S6) in the normal vehicle allocation mode described above is executed to match pairs of normal vehicle allocation requests and candidate vehicles so as to minimize the total estimated arrival time, and the final vehicle to be allocated is determined. For priority vehicle allocation requests, for example, special processing such as expanding the search range for candidate vehicles may be executed, and vehicle search processing may be executed continuously until an available candidate vehicle is found, thereby allowing for higher priority vehicle allocation.

[0083] In this way, the vehicle allocation unit 172 handles priority vehicle allocation requests differently from other normal vehicle allocation requests, and prioritizes allocating candidate vehicles to priority vehicle allocation requests through the vehicle search process in priority vehicle allocation mode over allocating candidate vehicles to normal vehicle allocation requests through the vehicle search process (S2 to S6) in normal vehicle allocation mode. As a result, priority vehicle allocation requests that involve the charging of an additional fee are prioritized over other normal vehicle allocation requests. Therefore, user 2 who has made a priority vehicle allocation request can receive a prompt vehicle allocation that is commensurate with the additional fee. This improves user 2 satisfaction, especially when vehicles are allocated during peak hours or in congested areas.

[0084] Furthermore, the method for preferentially allocating a vehicle to a priority vehicle allocation request in the priority vehicle allocation mode is not limited to the example of matching a priority vehicle allocation request and a normal vehicle allocation request in separate matching processes as described above. For example, a method may be used in which priority vehicle allocation requests and normal vehicle allocation requests are matched together in the same matching process to make it easier to match a priority vehicle allocation request within the same matching process. In this method, for example, the priority of a priority vehicle allocation request may be raised above a normal vehicle allocation request, or the search range for a priority vehicle allocation request may be expanded.

[0085] [1.9. Image control processing of user terminal during vehicle detection processing] Next, with reference to Figs. 11 to 19, a vehicle search process by the vehicle dispatch management system 1 according to this embodiment and a display control process of a GUI (Graphical User Interface) image of the user terminal 20 while the vehicle search process is ongoing will be described.

[0086] As described above, a possible use case of the priority vehicle dispatch service is when user 2, who has made a normal vehicle dispatch request during a busy time period or in a crowded area, realizes that it will take a long time to confirm the dispatch from information such as the vehicle dispatch waiting time displayed on user terminal 20, and switches from the initial normal vehicle dispatch request to a priority vehicle dispatch request. In this use case, even if the vehicle dispatch management system 1 performs vehicle search processing (S2 to S6 in FIG. 7) in normal vehicle dispatch mode for the normal vehicle dispatch request, if no candidate vehicle to be dispatched is found, it is possible to temporarily terminate the vehicle search processing (S2 to S6 in FIG. 7) and then display an image on user terminal 20 suggesting switching to a priority vehicle dispatch request.

[0087] However, with this specification, if a candidate vehicle to be dispatched is found and dispatch is confirmed immediately after User 2 switches to a priority vehicle dispatch request in accordance with the proposed image, User 2 may have negative feelings, such as suspicion that the vehicle dispatch would have been confirmed even if User 2 had not switched to a priority vehicle dispatch request, or reluctance to pay the additional fee for the priority vehicle dispatch service, which may reduce User 2's satisfaction and sense of satisfaction. Furthermore, with the specification that proposes switching to a priority vehicle dispatch request after terminating the vehicle search process in normal vehicle dispatch mode (S2 to S6 in FIG. 7) as described above, User 2 is limited to two options: to pay the additional fee and switch to a priority vehicle dispatch request (priority vehicle dispatch mode), or to cancel the current normal vehicle dispatch request. User 2 cannot select the option of continuing the vehicle search process in normal vehicle dispatch mode (S2 to S6 in FIG. 7) while maintaining the normal vehicle dispatch request, which is inconvenient.

[0088] Furthermore, during the above-mentioned peak hours or in congested areas, there are few vacant taxi vehicles 32, making it difficult to board, but there may be vacant NRS vehicles 42. In this case, if user 2 has added a setting condition specifying a taxi as the vehicle to be dispatched (dispatch category) when initially requesting a normal vehicle dispatch, canceling this setting condition makes it possible to dispatch an NRS vehicle 42 relatively quickly instead of a taxi vehicle 32. In such a case, if it can be suggested to user 2 while he is waiting for a vehicle to be dispatched that an earlier vehicle can be dispatched by canceling or changing the setting condition such as the dispatch category, it is possible to present user 2 with a useful option, thereby improving user 2's convenience and satisfaction.

[0089] Therefore, the vehicle dispatch management system 1 according to this embodiment aims to improve user satisfaction and convenience by suitably suggesting to the user 2 options such as switching from normal vehicle dispatch mode to priority vehicle dispatch mode, or canceling or changing the conditions set when requesting a vehicle dispatch, when vehicle dispatch is difficult during peak hours, etc. Below, the vehicle search process and display control process procedures of the vehicle dispatch management server 60 and the transition of the GUI image on the user terminal 20 to achieve this purpose will be described in detail.

[0090] [1.9.1. Image control process to suggest switching to wired vehicle dispatch request while vehicle search process is ongoing] 11 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 dispatch during a busy time period or in a busy area where demand for vehicles is greater than supply.

[0091] As shown in Fig. 11, 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. 12A, 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. 12B) and a confirmation button 202 for confirming the vehicle dispatch request.

[0092] When user 2 taps the transition button 201 on the image 200 for requesting a ride, a ride-hailing category setting image 205 shown in FIG. 12B is displayed on the display device 124 of the user terminal 20 (S200). By selecting vehicle designation buttons 206 and 207 on the ride-hailing category setting image 205, user 2 can specify the category of the vehicle (i.e., the ride-hailing category) that the user desires to be dispatched, thereby setting the conditions for the ride-hailing category (S202). In the example ride-hailing category setting image 205 of FIG. 12B, the conditions for the ride-hailing category can be set to either "taxi / ride-share" or "taxi." If "taxi / ride-share" is selected, the vehicles available for dispatch are set to include both taxi vehicles 32 (first vehicle) and NRS vehicles 42 (second vehicle). On the other hand, if "taxi" is selected, the vehicles available for dispatch are limited to taxi vehicles 32 (first vehicle). In addition, User 2 can tap taxi company setting button 208 on vehicle dispatch category setting image 205 to specify a desired taxi company and select a taxi company of a vehicle to be dispatched.

[0093] In the following explanation, an example will be described in which user 2 sets the setting condition of the vehicle dispatch category to "taxi / ride share." 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."

[0094] After setting the vehicle dispatch category in the vehicle dispatch category setting image 205 (FIG. 12B), the user 2 taps the decision button 209 to return to the vehicle dispatch request image 200 (FIG. 12A), 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. 11).

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

[0096] 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, for convenience of explanation, in FIG. 11, the series of detection processes (S110, S120) are distinguished as 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 convenience of explanation. Furthermore, the continuous vehicle detection process (S120) is executed continuously without interruption within a predetermined time limit (for example, 30 minutes or 60 minutes).

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

[0098] 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. 13 (S210). As shown in FIG. 13, 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.

[0099] 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. 14A and 14B (S220). As shown in FIGS. 14A and 14B, 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.

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

[0101] As shown in Fig. 11, 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. 13 on the display device 124 (S210).

[0102] 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 text information such as that shown in FIG. 13, 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.

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

[0104] 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. 14A on the display device 124 (S220).

[0105] The second progress image 220 shown in FIG. 14A 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. 14A, 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.

[0106] Here, the above-mentioned predetermined time will be explained. The predetermined time is a reference time for determining the timing for switching from the above-mentioned vehicle detection process (S110) to the continued vehicle detection process (S120). This predetermined time corresponds to the time for determining the timing for switching from the first progress image 210 (FIG. 13) displayed on the user terminal 20 to the second progress image 220 (FIG. 14). 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 that the waiting time until the vehicle dispatch is confirmed will be longer than usual.

[0107] Furthermore, the second progress image 220 shown in FIG. 14A 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. 14A, 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.

[0108] Furthermore, as shown in FIG. 14A , the second progress image 220 displays information 224 (e.g., “14 people have arranged for a ride in the vicinity” in FIG. 14A ) 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. 14A, 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.

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

[0110] 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. 13 ) to the second progress image 220 ( FIG. 14A ) 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 a 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. 14A upward on the screen to change it to the full-screen display state shown in FIG. 14B , and attempts to obtain information on a method for quickly confirming vehicle dispatch as a countermeasure to the long vehicle dispatch waiting time. 14A and 14B, the second progress image 220 is transitioned from the partial display state of Fig. 14A to the full-screen display state of Fig. 14B 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. 14B from the beginning, and the second progress image 220 in the partial display state of Fig. 14A may not be displayed.

[0111] 14B, 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.

[0112] Furthermore, as shown in FIG. 14B , 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. 14B . For example, it may be an indicator, graph, graphic, icon, character image, or the like that indicates the level or progress of the estimated waiting time.

[0113] 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. 15A on the display device 124. User 2 sets a payment method using change payment method button 231 on this application image 230, if 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. 14B.

[0114] 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 priority vehicle dispatch request command (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 third image switching command to the user terminal 20 (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. 15B on the display device 124 (S240).

[0115] 15B, 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.

[0116] 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. 15B , 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.

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

[0118] Once the vehicle dispatch is confirmed as described above and the user terminal 20 receives a vehicle dispatch completion notification (S10) from the vehicle dispatch management server 60, the fourth progress image 250 shown in FIG. 16 is displayed on the display device 124 (S300). The fourth progress image 250 includes text information such as "Vehicle 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 vehicle 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.

[0119] 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, and automatically switches the display image on the user terminal 20 from a simple first progress image 210 ( FIG. 13 ) for the vehicle search process (S110) to a more comprehensive second progress image 220 ( FIG. 14 ) 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.

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

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

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

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

[0124] In the above embodiment, as shown in FIG. 14B, 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 representing the predicted waiting time (first predicted waiting time) shown in FIG. 14B and the information 223 representing the number of users waiting for a ride may be displayed in different images or at different times.

[0125] [1.9.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. 11 will be described with reference to Fig. 17. Fig. 17 is a sequence diagram showing the flow of the vehicle detection process according to the modified example of the present embodiment and the display control process according to the progress of the process.

[0126] As shown in Figure 17, the processing flow of the modified example of this embodiment differs from the processing flow of the first embodiment described above (see Figure 11) 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, as with the embodiment shown in Figure 11, the modified example of this embodiment shown in Figure 17 also assumes a case in which user 2 requests a vehicle dispatch during a busy time period or in a busy area where demand for vehicles exceeds supply.

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

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

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

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

[0131] 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 13 on the display device 124 of the user terminal 20.

[0132] 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. 18A (S224). As shown in FIG. 18A, 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.

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

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

[0135] 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. 18A on the display device 124 (S224).

[0136] As shown in FIG. 18A, 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. 14B) (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 canceling the setting conditions specified by user 2 when inputting the setting conditions (S204). In the example of FIG. 18A, the second proposal information 262 includes a cancel button 264 for canceling the setting condition of specifying a taxi.

[0137] 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. 18B 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. 18B) 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. 18A. 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.

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

[0139] 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. 19A on the display device 124 (S260).

[0140] 19A, 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.

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

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

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

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

[0145] 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. 19B 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.

[0146] As described above, according to the modified example of this embodiment, the second progress image 260 shown in FIG. 18A 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.

[0147] The procedure for displaying multiple types of proposed information is not limited to the example shown in FIG. 18A 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 then, only if a vehicle dispatch is still not determined, to be gradually suggested to switch 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.

[0148] [1.10. Summary of this embodiment] 1. As described above, according to this embodiment, there is provided a vehicle dispatch management system including a plurality of user terminals (20) and a vehicle dispatch management device (60) communicably connected to the user terminals (20) via a network (6), wherein the user terminals (20) include one or more first processors (122) and a display device (124), the vehicle dispatch management device (60) includes one or more second processors (162), the first processor of the user terminal (20) executes a process of transmitting a vehicle dispatch request to the vehicle dispatch management device (60) in response to an input from a user (2), and the second processor (162) of the vehicle dispatch management device (60) executes a vehicle search process of searching for a vehicle that matches the vehicle dispatch request received from the user terminal (20) from among a plurality of vehicles. and a display control process for controlling information displayed on the user terminal (20) according to the progress of the vehicle detection process, wherein a first processor (122) of the user terminal (20) executes a process for displaying information on a display device (124) in accordance with the display control process by the vehicle dispatch management device (60), wherein the vehicle detection process modes include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatching is higher than that of the normal vehicle dispatch mode, and the display control process causes the user terminal (20) to display first progress information (221) indicating that the vehicle detection process in the normal vehicle dispatch mode is being continuously executed and first proposal information (225) for proposing switching to the priority vehicle dispatch mode while the vehicle detection process in the normal vehicle dispatch mode is continuing. With this configuration, while the vehicle detection process is continuously executed by the vehicle dispatch management device (60), the first progress information (221) and the first proposal information (225) can be displayed on the user terminal (20) at appropriate timing according to the progress of the vehicle detection process and presented to the user (2). Therefore, when dispatching a vehicle is difficult during peak hours, etc., user satisfaction and convenience can be improved.

[0149] 2. Also, according to this embodiment, there is provided a vehicle dispatch management device (60) communicably connected to a user terminal (20) via a network (6), the vehicle dispatch management device (60) having one or more processors (162), the processor (162) executes a search process for searching for a vehicle that matches a vehicle dispatch request received from the user terminal (20) from among a plurality of vehicles, and a display control process for controlling information displayed on the user terminal (20) according to the progress of the search process, the modes of the search process include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatching is higher than that of the normal vehicle dispatch mode, and the display control process displays on the user terminal (20) first proposal information (225) for proposing switching to the priority vehicle dispatch mode together with first progress information (221) indicating that the search process in the normal vehicle dispatch mode is being continuously executed while the search process in the normal vehicle dispatch mode is continuing. With this configuration, the vehicle dispatch management device (60) continuously executes the vehicle detection process, and the first progress information (221) and the first proposal information (225) can be displayed on the user terminal (20) at an appropriate timing according to the progress of the vehicle detection process, and presented to the user (2). Therefore, when vehicle dispatch is difficult during peak hours, etc., user satisfaction and convenience can be improved.

[0150] 3. The display control process may include a first display control process for displaying, on the user terminal (20), second progress information (211) indicating that the vehicle detection process in the normal vehicle dispatch mode is being executed after the vehicle detection process in the normal vehicle dispatch mode has started, and a second display control process for displaying, on the user terminal (20), first proposed information (225) together with the first progress information (221) when a predetermined time or more has elapsed since the start of the vehicle detection process while the vehicle detection process in the normal vehicle dispatch mode is continuing. With this configuration, while the vehicle detection process is continuously executed by the vehicle dispatch management device (60), the second progress information (211) is first displayed on the user terminal (20) after the vehicle detection process starts, and after the predetermined time or more has elapsed, the first progress information (221) and the first proposed information (225) are displayed on the user terminal (20) and presented to the user (2). This can further improve user satisfaction and convenience.

[0151] 4. The plurality of vehicles may include at least one first vehicle (32) driven by a first driver (3) and at least one second vehicle (42) driven by a second driver (4) who has a different type of driving qualification from the first driver (3). When a setting condition specifying the first vehicle (32) as the vehicle to be allocated is added to a vehicle allocation request received from a user terminal (20), the display control process may include a third display control process for displaying second proposal information (262) on the user terminal (20) to propose canceling or changing the setting condition when a predetermined time or more has elapsed since the start of the vehicle exploration process while the vehicle exploration process is continuing. With this configuration, while the vehicle exploration process is continuously executed by the vehicle allocation management device (60), the second proposal information (262) can be displayed on the user terminal (20) and presented to the user (2) after the predetermined time or more has elapsed since the vehicle exploration process began. This can further improve user satisfaction and convenience.

[0152] 5. In the second display control process, information indicating the number of users waiting for a vehicle dispatch under the same vehicle dispatch setting conditions as the user in the same area as the user of the user terminal 20 may be displayed on the user terminal 20, together with the first progress information 221 and the first proposal information 225. With this configuration, the vehicle dispatch congestion situation in the area where the user 2 is located can be appropriately presented to the user 2.

[0153] 6. In the second display control process, information indicating a first predicted waiting time until the dispatch of a vehicle is confirmed if the vehicle search process in the normal dispatch mode is continued may be displayed on the user terminal (20) together with the first progress information (221) and the first proposal information (225). With this configuration, the congestion status of the dispatch of vehicles and the expected dispatch time can be appropriately presented to the user (2).

[0154] 7. The first proposal information (225) may include information indicating a second predicted waiting time until dispatch is confirmed when switching to the priority dispatch mode. With this configuration, the expected dispatch time when switching from the normal dispatch mode to the priority dispatch mode can be appropriately presented to the user (2).

[0155] 8. The processor (162) may further execute a process of receiving a dispatch request in the priority dispatch mode from the user terminal (20) and a process of executing the dispatch process in the priority dispatch mode in response to the dispatch request in the priority dispatch mode received from the user terminal (20) after displaying the first progress information (221) and the first proposal information (225) on the user terminal (20) by the display control process while the vehicle search process in the normal vehicle dispatch mode is continuing. With this configuration, when the user (2) switches from the normal vehicle dispatch mode to the priority vehicle dispatch mode, a vehicle can be dispatched to the user (2) with priority.

[0156] 9. Also, according to this embodiment, there is provided a vehicle dispatch management method executed by a computer (60), which includes a search process for searching for a vehicle that matches a vehicle dispatch request received from a user terminal (20) from among a plurality of vehicles, and a display control process for controlling information displayed on the user terminal (20) according to the progress of the search process, wherein the modes of the search process include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatching is higher than that of the normal vehicle dispatch mode, and the display control process displays on the user terminal (20) first proposal information (225) for proposing switching to the priority vehicle dispatch mode together with first progress information (221) indicating that the search process in the normal vehicle dispatch mode is being continuously executed while the search process in the normal vehicle dispatch mode is continuing. With this configuration, the vehicle dispatch management device (60) continuously executes the vehicle detection process, and the first progress information (221) and the first proposal information (225) can be displayed on the user terminal (20) at an appropriate timing according to the progress of the vehicle detection process, and presented to the user (2). Therefore, when vehicle dispatch is difficult during peak hours, etc., user satisfaction and convenience can be improved.

[0157] 10. Also, according to this embodiment, there is provided a program for causing a computer (60) to execute a vehicle search process for searching for a vehicle that matches a vehicle dispatch request received from a user terminal (20) from among a plurality of vehicles, and a display control process for controlling information displayed on the user terminal (20) according to the progress of the vehicle search process, wherein the modes of the vehicle search process include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatching is higher than that of the normal vehicle dispatch mode, and the display control process causes the user terminal (20) to display, while the vehicle search process in the normal vehicle dispatch mode is continuing, first progress information (221) indicating that the vehicle search process in the normal vehicle dispatch mode is being continuously executed, as well as first proposal information (225) for proposing switching to the priority vehicle dispatch mode. With this configuration, while the vehicle search process is continuously executed by the vehicle dispatch management device (60), the first progress information (221) and the first proposal information (225) can be displayed on the user terminal (20) at appropriate times according to the progress of the vehicle search process, and presented to the user (2). Therefore, when dispatching a vehicle is difficult during peak hours, etc., user satisfaction and convenience can be improved.

[0158] 11. Also, according to this embodiment, there is provided a user terminal (20) communicably connected to a vehicle dispatch management device (60) via a network (6), the user terminal (20) comprising one or more processors and a display device (124), the processor (122) executing a process of transmitting a vehicle dispatch request to the vehicle dispatch management device (60) in response to an input from a user (2) and a process of displaying information on the display device (124) in accordance with a display control process by the vehicle dispatch management device (60), the modes of vehicle discovery processing by the vehicle dispatch management device (60) include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatching is higher than that of the normal vehicle dispatch mode, and in the process of displaying information on the display device (124), the user terminal (20) displays, on the display device (124), first progress information (221) indicating that vehicle discovery processing in the normal vehicle dispatch mode is being continuously executed, together with first proposal information (225) for proposing switching to the priority vehicle dispatch mode, while the vehicle discovery processing in the normal vehicle dispatch mode is continuing. With this configuration, the vehicle dispatch management device (60) continuously executes the vehicle detection process, and the first progress information (221) and the first proposal information (225) can be displayed on the user terminal (20) at an appropriate timing according to the progress of the vehicle detection process, and presented to the user (2). Therefore, when vehicle dispatch is difficult during peak hours, etc., user satisfaction and convenience can be improved.

[0159] 12. The processor 122 may further execute a process of transmitting a dispatch request in the priority dispatch mode to the dispatch management device 60 in response to an input from the user 2, after displaying the first proposed information 225 together with the first progress information 221 on the display device 124 by performing a process of displaying information on the display device 124. With this configuration, when the user 2 switches from the normal dispatch mode to the priority dispatch mode, a vehicle can be dispatched preferentially to the user 2.

[0160] 13. Also, according to this embodiment, there is provided a vehicle dispatch request method executed by a computer (20), which executes a process of sending a vehicle dispatch request to a vehicle dispatch management device (60) in response to a user input (2), and a display process of displaying information on a display device (124) in accordance with a display control process by the vehicle dispatch management device (60), wherein the vehicle detection process modes by the vehicle dispatch management device (60) include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatching is higher than that of the normal vehicle dispatch mode, and in the display process, while the vehicle detection process in the normal vehicle dispatch mode executed by the vehicle dispatch management device (60) is continuing, first progress information (221) indicating that the vehicle detection process in the normal vehicle dispatch mode is being continuously executed, and first proposal information (225) for proposing switching to the priority vehicle dispatch mode are displayed on the display device (124). With this configuration, the vehicle dispatch management device (60) continuously executes the vehicle detection process, and the first progress information (221) and the first proposal information (225) can be displayed on the user terminal (20) at an appropriate timing according to the progress of the vehicle detection process, and presented to the user (2). Therefore, when vehicle dispatch is difficult during peak hours, etc., user satisfaction and convenience can be improved.

[0161] 14. Furthermore, according to this embodiment, there is provided a vehicle dispatch request method, which is a program that causes a computer (20) to execute a process of sending a vehicle dispatch request to a vehicle dispatch management device (60) in response to input by a user (2), and a display process of displaying information on a display device (124) in accordance with display control processing by the vehicle dispatch management device (60), wherein the modes of vehicle detection processing by the vehicle dispatch management device (60) include a normal vehicle dispatch mode and a priority vehicle dispatch mode in which the priority of vehicle dispatching is higher than that of the normal vehicle dispatch mode, and in the display process, while the vehicle detection processing in the normal vehicle dispatch mode executed by the vehicle dispatch management device (60) is continuing, first proposal information (225) for proposing switching to the priority vehicle dispatch mode is displayed on the display device (124) together with first progress information (221) indicating that the vehicle detection processing in the normal vehicle dispatch mode is being continuously executed. With this configuration, the vehicle dispatch management device (60) continuously executes the vehicle detection process, and the first progress information (221) and the first proposal information (225) can be displayed on the user terminal (20) at an appropriate timing according to the progress of the vehicle detection process, and presented to the user (2). Therefore, when vehicle dispatch is difficult during peak hours, etc., user satisfaction and convenience can be improved.

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

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

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

[0165] 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) 124 Display 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 211 Progress Information (Second Progress Information) 225 1st proposal information 221 Progress Information (First Progress Information) 262 Second proposal information S110, S120 Vehicle detection processing using normal vehicle dispatch mode S112, S122, S124, S132, S162 Display control processing

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; A display device; Equipped with 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 search process for searching for a vehicle that matches the vehicle dispatch request received from the user terminal from among a plurality of vehicles; a display control process for controlling information displayed on the user terminal according to the progress of the vehicle detection process; Run The first processor of the user terminal: A process of displaying information on the display device in accordance with the display control process by the vehicle dispatch management device. Run The mode of the detection processing is: Normal dispatch mode and a priority vehicle dispatch mode having a higher priority of vehicle dispatch than the normal vehicle dispatch mode; Including, In the display control process, A vehicle dispatch management system that displays, on the user terminal, first progress information indicating that the vehicle dispatch processing in the normal vehicle dispatch mode is being continuously executed and first proposal information proposing switching to the priority vehicle dispatch mode while the vehicle dispatch processing in the normal vehicle dispatch mode continues.

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 search process for searching for a vehicle that matches the vehicle dispatch request received from the user terminal from among a plurality of vehicles; a display control process for controlling information displayed on the user terminal according to the progress of the vehicle detection process; Run The mode of the detection processing is: Normal dispatch mode and a priority vehicle dispatch mode having a higher priority of vehicle dispatch than the normal vehicle dispatch mode; Including, In the display control process, A vehicle dispatch management device that displays, on the user terminal, first proposal information proposing switching to the priority vehicle dispatch mode, along with first progress information indicating that the vehicle dispatch process is being continuously executed in the normal vehicle dispatch mode while the vehicle dispatch process is continuing in the normal vehicle dispatch mode.

3. The display control process includes: a first display control process for displaying, on the user terminal, second progress information indicating that the vehicle detection process in the normal vehicle dispatch mode is being executed after the execution of the vehicle detection process in the normal vehicle dispatch mode has started; a second display control process for displaying the first proposed information together with the first progress information on the user terminal when a predetermined time or more has elapsed since the start of the vehicle search process while the vehicle search process is continuing in the normal vehicle dispatch mode; The vehicle dispatch management device according to claim 2 , further comprising:

4. 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, When a setting condition specifying the first vehicle as a vehicle to be allocated is added to the vehicle allocation request received from the user terminal, The display control process includes: a third display control process for displaying second proposal information for proposing cancellation or change of the setting condition on the user terminal when a predetermined time or more has elapsed since the start of the vehicle detection process during the continuation of the vehicle detection process; The vehicle dispatch management device according to claim 2 , further comprising:

5. In the second display control process, The vehicle dispatch management device of claim 3, wherein, together with the first progress information and the first proposal information, information representing the number of users waiting for dispatch under the same dispatch setting conditions as the user in the same area as the user of the user terminal is displayed on the user terminal.

6. In the second display control process, The vehicle dispatch management device of claim 3, wherein information representing a first predicted waiting time until dispatch is confirmed if the vehicle search process is continued in the normal vehicle dispatch mode is displayed on the user terminal together with the first progress information and the first proposal information.

7. The vehicle dispatch management device according to claim 3 , wherein the first proposal information includes information representing a second predicted waiting time until vehicle dispatch is confirmed when the priority vehicle dispatch mode is switched to.

8. The processor: a process of receiving a dispatch request in the priority dispatch mode from the user terminal after displaying the first progress information and the first proposal information on the user terminal during the continuation of the vehicle search process in the normal dispatch mode by the display control process; A process of executing a vehicle search process in the priority vehicle dispatch mode in response to a vehicle dispatch request in the priority vehicle dispatch mode received from the user terminal; The vehicle dispatch management device according to claim 2 , further comprising:

9. A vehicle dispatch management method executed by a computer, comprising: A vehicle search process for searching for a vehicle that matches the vehicle dispatch request received from the user terminal from among a plurality of vehicles; a display control process for controlling information displayed on the user terminal according to the progress of the vehicle detection process; Including, The mode of the detection processing is: Normal dispatch mode and a priority vehicle dispatch mode having a higher priority of vehicle dispatch than the normal vehicle dispatch mode; Including, In the display control process, A vehicle dispatch management method in which, while the vehicle detection process in the normal vehicle dispatch mode is continuing, first progress information indicating that the vehicle detection process in the normal vehicle dispatch mode is being continuously executed, and first proposal information proposing switching to the priority vehicle dispatch mode are displayed on the user terminal.

10. A vehicle search process for searching for a vehicle that matches the vehicle dispatch request received from the user terminal from among a plurality of vehicles; a display control process for controlling information displayed on the user terminal according to the progress of the vehicle detection process; A program for causing a computer to execute the above, The mode of the detection processing is: Normal dispatch mode and a priority vehicle dispatch mode having a higher priority of vehicle dispatch than the normal vehicle dispatch mode; Including, In the display control process, A program that displays, on the user terminal, first progress information indicating that the vehicle detection process in the normal vehicle dispatch mode is being continuously executed, along with first proposal information proposing switching to the priority vehicle dispatch mode, while the vehicle detection process in the normal vehicle dispatch mode is continuing.

11. A user terminal communicably connected to the vehicle dispatch management device via a network, The user terminal one or more processors; A display device; Equipped with The processor: a process of transmitting a vehicle dispatch request to the vehicle dispatch management device in response to a user input; a process of displaying information on the display device in accordance with a display control process by the vehicle dispatch management device; Run The vehicle search processing mode by the vehicle dispatch management device is Normal dispatch mode and a priority vehicle dispatch mode having a higher priority of vehicle dispatch than the normal vehicle dispatch mode; Including, In the process of displaying information on the display device, A user terminal that displays on the display device, while the vehicle detection process in the normal vehicle dispatch mode is continuing, first progress information indicating that the vehicle detection process in the normal vehicle dispatch mode is being continuously executed, together with first proposal information proposing switching to the priority vehicle dispatch mode.

12. The processor: a process of displaying the first proposed information together with the first progress information on the display device by the process of displaying information on the display device, and then transmitting a dispatch request in the priority dispatch mode to the vehicle dispatch management device in response to an input from the user. The user terminal of claim 11 , further comprising:

13. A vehicle dispatch request method executed by a computer, A process of transmitting a vehicle dispatch request to the vehicle dispatch management device in response to an input from a user; a display process for displaying information on a display device in accordance with a display control process by the vehicle dispatch management device; Run The vehicle search processing mode by the vehicle dispatch management device is Normal dispatch mode and a priority vehicle dispatch mode having a higher priority of vehicle dispatch than the normal vehicle dispatch mode; Including, In the display process, A vehicle dispatch request method in which, while the vehicle dispatch management device continues to execute the vehicle detection process in the normal vehicle dispatch mode, the display device displays first progress information indicating that the vehicle detection process in the normal vehicle dispatch mode is being continuously executed, together with first proposal information proposing switching to the priority vehicle dispatch mode.

14. A process of transmitting a vehicle dispatch request to the vehicle dispatch management device in response to an input from a user; a display process for displaying information on a display device in accordance with a display control process by the vehicle dispatch management device; A program that causes a computer to execute the The vehicle search processing mode by the vehicle dispatch management device is Normal dispatch mode and a priority vehicle dispatch mode having a higher priority of vehicle dispatch than the normal vehicle dispatch mode; Including, In the display process, A vehicle dispatch request method in which, while the vehicle dispatch management device continues to execute the vehicle detection process in the normal vehicle dispatch mode, the display device displays first progress information indicating that the vehicle detection process in the normal vehicle dispatch mode is being continuously executed, together with first proposal information proposing switching to the priority vehicle dispatch mode.

Images