Systems, methods, computer devices, and programs

Abstract

We provide a novel system capable of executing vehicle dispatch processing. [Solution] A system comprising at least one computer device, the system comprising: a dispatch request receiving means for receiving a first dispatch request for a vehicle from an operation on a user terminal operated by a user; and a display control means for controlling an operator terminal operated by an operator to display information related to the first dispatch request received by the dispatch request receiving means, in order to dispatch a vehicle to a location specified by the user, by issuing a dispatch instruction to a driver to drive the vehicle, or an acceptance request to a driver to accept the dispatch.

Description

Technical Field

[0001] The present invention relates to a system, a method, a computer device, and a program.

Background Art

[0002] Conventionally, services have been provided to assign taxis or accompanying vehicles for driving services to users. In recent years, an information processing system for determining a vehicle to be assigned to a user is also known.

[0003] For example, Patent Document 1 describes an information processing device that assigns a vehicle with a low movement load in response to a taxi reservation request from a user.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] An object of the present invention is to provide a novel system capable of executing vehicle allocation processing.

Means for Solving the Problems

[0006] According to the present invention, the above object is achieved by [1] A system including at least one computer device, the system comprising: a vehicle allocation request receiving means for receiving a first vehicle allocation request from an operation on a user terminal operated by a user; and a display control means for controlling to display information regarding the first vehicle allocation request received by the vehicle allocation request receiving means on an operator terminal operated by an operator who executes a vehicle allocation instruction for allocating a vehicle to a location designated by the user to a driver who drives the vehicle, or a reception request for requesting the driver to accept the vehicle allocation. [2] The system according to [1], comprising a dispatch request input means for receiving information about a second dispatch request from a user by operation of a request receiving terminal operated by a request receiving person who receives a second dispatch request from a user by telephone or facsimile, and a display control means controlling to display information about the second dispatch request received by the dispatch request input means together with information about the first dispatch request; [3] The system according to [1] or [2] above, comprising: a waiting time transmission means that, upon receiving a first dispatch request via a dispatch request receiving means, transmits to a user terminal information regarding the waiting time until the vehicle arrives at the location specified by the user in the first dispatch request; and a dispatch instruction transmission means that, upon receiving a dispatch instruction request from the user terminal that has received the waiting time, transmits a vehicle dispatch instruction to a driver terminal operated by the driver operating the vehicle, either automatically or by operation on the operator terminal, for the first dispatch request, wherein the waiting time information is calculated by the system or accepted by the system by operation on the operator terminal; [4] The system according to [2] or [3] above, comprising dispatch instruction transmission means that automatically or by operation of the operator terminal transmits a vehicle dispatch instruction to a driver terminal operated by a driver operating a vehicle, regarding a first dispatch request received by dispatch request receiving means or a second dispatch request entered by dispatch request input means; [5] The system described in [4] above, comprising dispatch information transmission means for transmitting to a user terminal information about the vehicle to be driven by a driver terminal corresponding to a dispatch instruction, and information about the time the vehicle is scheduled to arrive at the location specified by the user in the first dispatch request or the second dispatch request, wherein the information about the time the vehicle is scheduled to arrive is calculated by the system or is accepted by the system through an operation on the operator terminal; [6] The system according to any one of [1] to [5] above, wherein the display control means controls the display of information related to the first dispatch request among the first dispatch requests received by the dispatch request receiving means that satisfy predetermined conditions; [7] The system described in [6] above, wherein the specified condition is that the waiting time until the vehicle arrives at the location specified by the user in the first dispatch request is equal to or greater than a specified time, or that the waiting time is longer than a specified time; [8] The system according to [6] or [7] above, comprising: a dispatch request transmission means that, with respect to a first dispatch request that does not meet the prescribed conditions, automatically transmits a dispatch request transmission means to a driver terminal operated by a driver who will drive the vehicle, requesting acceptance of the dispatch of the vehicle for the first dispatch request received by the dispatch request receiving means, and a display control means that, if an acceptance notification from the driver terminal accepting the dispatch of the vehicle has not been received even after a second prescribed time has elapsed, displays information regarding the first dispatch request; [9] The system according to any one of [6] to [8] above, comprising dispatch instruction transmission means that automatically transmits vehicle dispatch instructions to a driver terminal operated by a driver operating a vehicle for first dispatch requests received by dispatch request receiving means that do not meet predetermined conditions;

[10] A method to be performed in a system comprising at least one computer device, comprising: a dispatch request receiving step of receiving a first dispatch request for a vehicle from an operation on a user terminal operated by a user; and a display control step of controlling an operator terminal operated by an operator who executes a dispatch instruction to instruct a driver to drive a vehicle in order to dispatch a vehicle to a location specified by a user, or an acceptance request to request a driver to accept a dispatch, to display information related to the first dispatch request received in the dispatch request receiving step;

[11] A program that causes a computer device to function as a dispatch request receiving means for receiving a first dispatch request for a vehicle from an operation on a user terminal operated by a user, and as a display control means for controlling the display of information related to the first dispatch request received by the dispatch request receiving means on an operator terminal operated by an operator who executes a dispatch instruction to instruct a driver to drive a vehicle in order to dispatch a vehicle to a location specified by the user, or an acceptance request to request a driver to accept the dispatch; This can be resolved.

[0007] According to the present invention, the above objective is

[12] A system comprising at least one computer device, comprising control means capable of controlling the execution of dispatch processing for determining a vehicle to be dispatched to a user in two or more different modes;

[13] The system described in

[12] above, comprising a driver terminal operated by the driver of a vehicle dispatched to a user, wherein a control means controls the system to execute dispatch processing in a first mode when predetermined conditions are not met regarding the status of the dispatch request, and to execute dispatch processing in a mode different from the first mode when predetermined conditions are met regarding the status of the dispatch request, and in dispatch processing in the first mode, an acceptance request is sent to the driver terminal, and the driver terminal is capable of receiving input for acceptance;

[14] The system described in

[13] above, comprising an operator terminal operated by an operator who determines which vehicle to dispatch to the user, wherein information regarding the dispatch request is transmitted to the operator terminal in dispatch processing in a mode different from the first mode;

[15] The system described in

[13] above, wherein in dispatch processing using a mode different from the first mode, an assignment instruction is sent to the driver terminal;

[16] The system described in

[12] above, comprising a driver terminal operated by the driver of a vehicle dispatched to a user, and an operator terminal operated by an operator who determines which vehicle is dispatched to a user, wherein the control means controls to execute dispatch processing in a first mode when a first predetermined condition is met regarding the status of the dispatch request, controls to execute dispatch processing in a second mode when a second predetermined condition is met regarding the status of the dispatch request, controls to execute dispatch processing in a third mode when a third predetermined condition is met regarding the status of the dispatch request, in dispatch processing in the first mode a request for assignment is sent to the driver terminal and the driver terminal is capable of receiving input for assignment, in dispatch processing in the second mode information is sent to the operator terminal, and in dispatch processing in the third mode an instruction for assignment is sent to the driver terminal;

[17] The system described in

[14] or

[16] above, wherein, in dispatch processing using a mode different from the first mode, or dispatch processing using the second mode, the length of the user's waiting time until a vehicle is dispatched is transmitted to the operator terminal;

[18] A system described in any of

[12] to

[17] above, wherein the specified conditions are the length of time until a dispatch request is accepted by a driver, the percentage of dispatch requests accepted by drivers, the length of time the user waits until a vehicle is dispatched, the number of dispatch requests, and / or conditions relating to input from the operator;

[19] A method performed in a system comprising at least one computer device, the method comprising a control step of controlling the execution of a dispatch process for determining a vehicle to be dispatched to a user in two or more different modes;

[20] A computer device comprising control means capable of controlling the execution of a dispatch process for determining which vehicle will be dispatched to the user, using two or more different modes;

[21] A program that causes a computer device to function as a control means capable of controlling it to perform dispatch processing for determining which vehicle will be dispatched to a user in two or more different modes; This can be achieved. [Advantages of the Invention]

[0008] According to the present invention, it is possible to provide a novel system capable of executing vehicle allocation processing. [Brief Description of the Drawings]

[0009] [Figure 1] It is a block diagram showing the configuration of a system according to an embodiment of the present invention. [Figure 2] It is a block diagram showing the hardware configuration of a user terminal according to an embodiment of the present invention. [Figure 3] It is a block diagram showing the hardware configuration of a server device according to an embodiment of the present invention. [Figure 4] It is a flowchart of vehicle allocation mode determination processing according to an embodiment of the present invention. [Figure 5] It is a flowchart of vehicle allocation processing in the first mode according to an embodiment of the present invention. [Figure 6] It is a flowchart of vehicle allocation processing in the second mode according to an embodiment of the present invention. [Figure 7] It is a flowchart of vehicle allocation processing in the third mode according to an embodiment of the present invention. [Figure 8] It is a flowchart of vehicle allocation processing according to an embodiment of the present invention. [Modes for Carrying Out the Invention]

[0010] Hereinafter, embodiments of the present invention will be described. However, the present invention is not limited to the following embodiments as long as it does not conflict with the gist of the present invention. Also, the description of the effects is one aspect of the effects of the embodiments of the present invention and is not limited to what is described here. The order of each process constituting the flowchart described below can be in any order as long as there is no contradiction or inconsistency in the process content. Also, as long as there is no contradiction or inconsistency in the process content, a part of each process constituting the flowchart can be omitted, or a new process can be added to each process constituting the flowchart. Also, the device that is the main body for executing each process constituting the flowchart can be changed to another device as long as it does not conflict with the gist of the present invention. In that case, the process content can be changed so that there is no contradiction or inconsistency in the process content.

[0011] Hereinafter, a mode of determining a vehicle to be dispatched in response to a request from a user using the system of the present invention will be described. The type (use) of the vehicle to be dispatched is not particularly limited. The vehicle to be dispatched may be, for example, a vehicle (e.g., a taxi, etc.) for transporting a user to a destination, or a vehicle (e.g., an attendant vehicle, etc.) for a person performing a driving service to move to a meeting place with the user. Note that the driving service may be a service of driving a user's vehicle on behalf of the user and moving it to a predetermined location.

[0012] [Configuration of the System] FIG. 1 is a block diagram showing the configuration of a system according to an embodiment of the present invention. The system 1 shown in FIG. 1 includes a user terminal 2, a server device 3, an operator terminal 4, and a plurality of driver terminals 5 (5a, 5b, ···, 5z). The user terminal 2, the server device 3, the operator terminal 4, and the plurality of driver terminals 5 are communicably connected to each other via a communication network 6. Note that the user terminal 2, the server device 3, the operator terminal 4, and the plurality of driver terminals 5 do not have to be constantly connected, and it is sufficient if they can be connected as needed.

[0013] In System 1, any of the user terminal 2, server device 3, operator terminal 4, and multiple driver terminals 5 can function as an information processing device. When any of the user terminal 2, server device 3, operator terminal 4, and multiple driver terminals 5 function as an information processing device, information is sent and received between the user terminal 2, server device 3, operator terminal 4, and multiple driver terminals 5 as needed.

[0014] The number and type of computer devices in System 1 are not particularly limited and can be designed as appropriate. System 1 only needs to have at least one computer device. For example, System 1 may consist only of server device 3, or only of operator terminal 4. Depending on the number and type of computer devices in System 1, any of the computer devices in System 1 may perform the necessary processing. For example, if System 1 consists only of operator terminal 4, the operator terminal 4 may perform the control of the vehicle dispatch process.

[0015] User terminal 2 is a terminal operated by the user requesting a ride. User terminal 2 may be a desktop or notebook personal computer, a tablet device, a smartphone, a wearable device, or a conventional mobile phone.

[0016] User terminal 2 may have an application (hereinafter also referred to as the dedicated app) downloaded for requesting a ride using System 1. However, if it is possible to request a ride using System 1 via a web browser, the dedicated app does not need to be downloaded to user terminal 2.

[0017] Users may register their information in advance as users of System 1. User information (hereinafter also referred to as user information) may include the user's name, telephone number, address, age, gender, and information about vehicles owned by the user (hereinafter also referred to as user vehicle information). When user information is registered in System 1, the user may be assigned identification information such as an identification number. User information may be stored in Server Device 3 in association with the user's identification information.

[0018] Users may, for example, request a ride (hereinafter also referred to as a ride request) via a dedicated application. In this case, the user can input information related to the ride request on the user terminal 2 and transmit the information related to the ride request from the user terminal 2 to the server device 3.

[0019] Alternatively, the user may request a ride by, for example, calling a ride-hailing service provider. In this case, system 1 does not need to have a user terminal 2. In this case, the ride-hailing operator may answer the phone, accept the ride request, and input information related to the ride request into the operator terminal 4. The operator can then transmit the information related to the ride request from the operator terminal 4 to the server device 3.

[0020] Furthermore, the user requesting the vehicle and the person at the destination of the dispatched vehicle may be the same person or different people.

[0021] Furthermore, System 1 may be equipped with two or more user terminals 2.

[0022] Server device 3 may be managed by the administrator of system 1. The administrator may be the same person as the dispatching company, or a different person.

[0023] The server device 3 can receive information regarding dispatch requests from the user terminal 2 or the operator terminal 4 and perform dispatch processing to determine which vehicle will be dispatched to the user. The execution of dispatch processing may be controlled by the control unit of the server device 3. The server device 3 may be capable of controlling the execution of dispatch processing in two or more different modes.

[0024] The server device 3 may also function in a distributed manner across multiple computer devices. For example, instead of server device 3, distributed ledger technology such as blockchain may be used.

[0025] Operator terminal 4 is a terminal operated by the operator who determines which vehicle will be dispatched to the user. Operator terminal 4 may be a desktop or notebook personal computer, a tablet terminal, a smartphone, a wearable device, or a conventional mobile phone.

[0026] Operators are not required to always decide which vehicle will be dispatched to the user; as described below, they can dispatch vehicles according to the circumstances of the dispatch request.

[0027] Furthermore, System 1 may be equipped with two or more user terminals 2. Alternatively, if it is possible to receive dispatch requests and dispatch vehicles even without an operator, System 1 may not be equipped with an operator terminal 4.

[0028] The driver terminal 5 is a terminal operated by the driver of the vehicle dispatched to the user. The driver terminal 5 may be a desktop or notebook personal computer, a tablet terminal, a smartphone, a wearable device, or a conventional mobile phone.

[0029] A driver may be the person who actually drives the dispatched vehicle, or the person who rides in the dispatched vehicle.

[0030] It is preferable that the driver terminal 5 has a function that enables it to identify its own location. It is preferable that the location information of the driver terminal 5 is transmitted to the server device 3 in real time. Based on the location information of the driver terminal 5, the server device 3 can identify vehicles that are close to the meeting place with the user, calculate the user's waiting time, and so on.

[0031] The driver may also input the vehicle status into the driver terminal 5 and transmit it to the server device 3. The vehicle status may include empty, occupied, on call, reserved, or out of service. The server device 3 can determine whether or not to send an acceptance request or an acceptance instruction to the vehicle based on its status.

[0032] Furthermore, System 1 may have only one driver terminal 5. Also, if the driver receives assignment requests or instructions from the operator via a wireless device capable of transmitting and receiving voice, System 1 may not need to have a driver terminal 5.

[0033] Operators and drivers may belong to the same company or to different companies. Alternatively, operators and / or drivers may work independently without belonging to a specific company. The drivers to whom operators can request dispatch may be predetermined. For example, operators and drivers may be assigned identification information in advance, and the identification information of operators and drivers who are in a relationship where dispatch requests can be made may be stored in association with each other in the server device 3.

[0034] Furthermore, the number of businesses using System 1 may be one or multiple.

[0035] Figure 2 is a block diagram showing the hardware configuration of a user terminal according to an embodiment of the present invention. The user terminal 2 comprises a control unit 21, RAM 22, storage unit 23, input unit 24, display unit 25, and communication interface 26, all of which are connected by a bus.

[0036] The control unit 21 consists of a CPU and ROM. The control unit 21 executes programs stored in the storage unit 23 and controls the user terminal 2. The RAM 22 is the work area of ​​the control unit 21. The storage unit 23 is a memory area for saving programs and data. In other words, the storage unit 23 functions as a recording medium that stores programs. The control unit 21 performs calculations based on the programs and data read from the RAM 22, as well as the data input at the input unit 24.

[0037] The display unit 25 has a display screen. The control unit 21 outputs a video signal for displaying an image on the display screen according to the result of the calculation processing. Here, the display screen of the display unit 25 may be a touch panel equipped with a touch sensor. In this case, the touch panel functions as an input unit 24.

[0038] The communication interface 26 can be connected to the communication network 6 wirelessly or via a wired connection, and can send and receive data with other computer devices via the communication network 6. Data received via the communication interface 26 is loaded into the RAM 22, and calculation processing is performed by the control unit 21.

[0039] The hardware configurations of operator terminal 4 and driver terminal 5 can be adapted from the description of the hardware configuration of user terminal 2 to the extent necessary.

[0040] Figure 3 is a block diagram showing the hardware configuration of a server device according to an embodiment of the present invention. The server device 3 comprises at least a control unit 31, RAM 32, storage unit 33, and communication interface 34, each connected by an internal bus.

[0041] The control unit 31 consists of a CPU and ROM, and executes programs stored in the storage unit 33 to control the server device 3. The control unit 31 also has an internal timer for timing. The RAM 32 is the work area of ​​the control unit 31. The storage unit 33 is a storage area for saving programs and data. In other words, the storage unit 33 functions as a recording medium that stores programs. The control unit 31 reads programs and data from the RAM 32 and performs program execution processing based on information received from the user terminal 2, operator terminal 4, and driver terminal 5.

[0042] Furthermore, the program may be stored on a recording medium such as a CD-ROM. In this case, the program stored on the recording medium may be installed on the user terminal 2, server device 3, operator terminal 4, and / or driver terminal 5 to perform predetermined functions.

[0043] Alternatively, the program may be delivered from a computer device outside the system. In this case, the program delivered from the computer device outside the system may be installed on the user terminal 2, server device 3, operator terminal 4, and / or driver terminal 5 to perform predetermined functions.

[0044] <First Embodiment> The following describes how dispatch processing is performed using one of two or more different modes, depending on the status of the dispatch request from the user. The explanation of Figures 1 to 3 above applies to the first embodiment.

[0045] Furthermore, "mode" refers to a method, and "performing dispatch processing using different modes" refers to performing processing to determine which vehicle will be dispatched using different information processing methods. Also, "dispatch processing" only needs to be a process aimed at determining which vehicle will be dispatched to the user, and the entity that actually determines which vehicle is dispatched may be System 1 (for example, Server Device 3), an operator, or a driver.

[0046] In the example shown below, the server device 3 can be controlled to execute the dispatch process using one of three modes: the first to the third mode. System 1 normally executes the dispatch process using the first mode, and when predetermined conditions are met regarding the status of the dispatch request, it is controlled to execute the dispatch process using the second mode or the third mode. In System 1, the mode of the dispatch process may be determined according to the status of the dispatch request in the dispatch mode determination process as shown below. Figure 4 is a flowchart of the dispatch mode determination process according to an embodiment of the present invention.

[0047] [Dispatch mode determination process] First, user terminal 2 receives input of the dispatch request details (step S101). User terminal 2 transmits the input dispatch request details to server device 3 (step S102). Server device 3 receives the transmitted dispatch request details (step S103). Server device 3 stores the received dispatch request details in storage unit 33 (step S104). Server device 3 determines whether the dispatch request status meets predetermined conditions (step S105).

[0048] In step S105, if it is determined that a predetermined condition is met (YES in step S105), the server device 3 changes the dispatch processing mode (step S106), and the dispatch mode determination process ends.

[0049] On the other hand, if it is determined in step S105 that the predetermined conditions are not met (NO in step S105), step S106 is not executed, and the dispatch mode determination process ends.

[0050] The acceptance of the dispatch request details in step S101 may be performed on the dispatch request screen for entering the details of the dispatch request. The user may be able to input the details on the user terminal 2 by typing letters, numbers, symbols, etc., selecting from predetermined options, tapping on the map, etc.

[0051] The content of the dispatch request accepted in step S101 is not particularly limited and can be designed as appropriate. For example, the content of the dispatch request may include information about the user, the meeting place between the user and the vehicle (e.g., pick-up location, drop-off location, etc.), the desired dispatch time, and the destination.

[0052] The user information may include any information about the user requesting the ride, but is not particularly limited. This information may include the user's name, phone number, user identification information, and vehicle information.

[0053] The meeting place is not particularly limited, as long as it is information that allows the user and vehicle to identify the location where they will meet. The meeting place may be represented by an address or by the name of a facility. Furthermore, if user terminal 2 is equipped with a function that allows the location information of user terminal 2 to be identified, the location information of user terminal 2 detected by user terminal 2 may be used as the meeting place.

[0054] The desired dispatch time is not limited to any information that allows the user to specify the time when the vehicle will arrive at the user's location. The desired dispatch time may be expressed as a specific time (e.g., "10:00 AM"), as a time range (e.g., "10:30-10:40 AM", "10 o'clock hour", "morning"), or as a time starting from a predetermined point in time (e.g., "10 minutes from now").

[0055] Step S102 may be executed when the details of the dispatch request are entered on the dispatch request screen, and the button for submitting the dispatch request is pressed.

[0056] In step S102, the details of the dispatch request desired by the user are sent to the server device 3, but at this point, the dispatch request is not actually made (a confirmed dispatch request is not sent). As will be described later, at a later time than step S102, the user can decide whether or not to actually make a dispatch request.

[0057] Furthermore, as mentioned above, when a user requests a vehicle by telephone, steps S101 to S102 may be performed by the operator terminal 4.

[0058] In step S104, the server device 3 stores the details of the dispatch request entered in step S101 as information related to the dispatch request. At this time, the information related to the dispatch request may also include identification information for identifying the dispatch request (hereinafter also referred to as dispatch request identification information), the status of the dispatch request, etc., associated with the details of the dispatch request. The dispatch request identification information may be assigned by the server device 3. At this time, the time when the details of the dispatch request were received in step S103 may also be stored as information related to the dispatch request.

[0059] The content (setting method) of the dispatch request status is not particularly limited and can be designed as appropriate. For example, a dispatch request in which the vehicle to be dispatched has not yet been determined may be set to the status "Not Dispatched," and a dispatch request in which the vehicle to be dispatched has been determined may be set to the status "Dispatch Confirmed." In step S104, since the vehicle to be dispatched for the dispatch request has not yet been determined, the status "Not Dispatched" may be stored.

[0060] The predetermined conditions in step S105 are not particularly limited and can be designed as appropriate. The predetermined conditions may be, for example, conditions in which a driver is considered busier than usual, based on the status of dispatch requests in System 1 or the status of dispatch requests from the operator's perspective. For example, the predetermined conditions may be the length of time until a dispatch request is accepted by a driver, the percentage of dispatch requests accepted by a driver, the length of time the user waits until a vehicle is dispatched, the number of dispatch requests, and / or conditions related to input from the operator.

[0061] When the predetermined condition relates to the length of time it takes for a dispatch request to be accepted by a driver (hereinafter also referred to as the length of acceptance time), the content of the condition is not particularly limited and can be designed as appropriate. For example, the content of the condition may be that the length of acceptance time is longer than a predetermined time. The method for calculating the length of acceptance time is not particularly limited. For example, the length of acceptance time may be calculated as the length of time from when the dispatch request is received in step S207 of the dispatch processing in the first mode described later, until when the acceptance information is received in step S215, or it may be calculated as the length of time from when the acceptance request is sent in step S210 of the dispatch processing in the first mode described later, until when the acceptance information is received in step S215. Furthermore, the number of dispatch requests or vehicles used to determine whether the predetermined condition is met is not particularly limited. For example, the server device 3 may make a determination using the length of acceptance time for one dispatch request, or it may make a determination using the average of the length of acceptance time for multiple dispatch requests. Furthermore, the determination may be made using, for example, the length of time spent on a single vehicle, or the average length of time spent on multiple vehicles.

[0062] Furthermore, the time information used to calculate the length of the assignment can be calculated based on the time each process was executed. For example, the server device 3 may store in the storage unit 33 the time when the dispatch request was received in step S207, the time when the assignment request was sent in step S210, and the time when the assignment information was received in step S215, as information related to the dispatch request.

[0063] When a predetermined condition relates to the percentage of dispatch requests accepted by drivers (hereinafter also referred to as the acceptance rate), the content of the condition is not particularly limited and can be designed as appropriate. For example, the content of the condition may be that the acceptance rate within a certain period of time in the most recent time is lower than the predetermined rate. The method for calculating the acceptance rate is not particularly limited. For example, the acceptance rate for one dispatch request may be calculated as the reciprocal of the number of driver terminals 5 that sent an acceptance request by step S210 (i.e., the number of people who sent an acceptance request before it was accepted) between the time the acceptance information is received in step S215 of the dispatch processing in the first mode described below and the time the acceptance information is received. For example, if the acceptance request is accepted by the first driver to whom it was sent (the first driver), the number of people will be 1, and the acceptance rate will be 1 (100%). On the other hand, if the acceptance request is accepted by the fifth driver to whom it was sent (the fifth driver), the number of people will be 5, and the acceptance rate will be 1 / 5 (20%). In step S105, if the average percentage of accepted cases within a recent period of time is lower than a predetermined percentage, it may be determined that the predetermined conditions are met.

[0064] When a predetermined condition relates to the length of the user's waiting time until a vehicle is dispatched (hereinafter also referred to as the length of waiting time), the content of the condition is not particularly limited and can be designed as appropriate. The content of the condition may be, for example, that the length of waiting time is longer than a predetermined time. The method for calculating the length of waiting time is not particularly limited. For example, the length of waiting time may be calculated by determining the estimated time required for the actual route to the meeting place for multiple vehicles that are close in a straight line from the meeting place, and the shortest of these times may be used as the length of waiting time. Any method can be used to calculate the required time. Furthermore, the target of the length of waiting time used to determine whether or not the predetermined condition is met is not particularly limited. For example, the server device 3 may make a determination using the length of waiting time of one user, or it may make a determination using the average of the length of waiting times of multiple users. Also, for example, the server device 3 may make a determination using the length of waiting time in a predetermined area. The method for calculating the length of waiting time in a predetermined area is not particularly limited. For example, the length of waiting time in a given area may be calculated by summing the waiting times of users who have designated the area as their meeting place.

[0065] When the specified conditions relate to the number of dispatch requests, the content of the conditions is not particularly limited and can be designed as appropriate. For example, the content of the conditions may be that the number of dispatch requests with the status "not dispatched" in server device 3 is greater than a specified number.

[0066] When the specified conditions relate to input from an operator, the content of the conditions is not particularly limited and can be designed as appropriate. For example, the content of the conditions may be that the operator terminal 4 has received input to change the dispatch processing mode. The operator terminal 4 may be capable of changing the dispatch processing mode and / or receiving input for the mode to be changed. If the operator terminal 4 receives input for the mode to be changed, the change to the input mode may be executed in step S106.

[0067] In normal circumstances where the predetermined conditions are not met, the system is controlled to execute the dispatch process using the first mode. Therefore, if it is determined in step S105 that the predetermined conditions are met and the dispatch process mode is changed in step S106, the system will be controlled to execute the dispatch process using a mode different from the first mode.

[0068] The above process makes it possible to switch the dispatch processing mode when the driver is expected to be busier than usual. Furthermore, since dispatch processing in the first mode is being performed while steps S101 to S105 are being executed, in step S105 it is possible to determine whether the status of the dispatch request identified based on the status of the dispatch processing meets predetermined conditions.

[0069] Furthermore, if multiple businesses use System 1, the predetermined conditions in step S105 may differ for each business. Businesses using System 1 may, for example, input the predetermined conditions at their business terminal. The predetermined conditions may be transmitted from the business terminal to the server device 3, and the server device 3 may perform the determination in step S105 based on the received predetermined conditions.

[0070] Furthermore, the mode of dispatch processing in step S106 may be changed for each predetermined area. For example, if drivers in the area around the station are busy, but drivers in other areas are not, the mode of dispatch processing in the area around the station may be changed only.

[0071] The following describes the details of the dispatch process using the first mode, and the details of the dispatch process using the second mode and the dispatch process using the third mode, which are different from the first mode. In the dispatch process using the first mode, a request for acceptance is sent from system 1 to the driver, and the driver can choose whether or not to accept the request. In the dispatch process using the second mode, the operator decides which vehicle to dispatch. In the dispatch process using the third mode, system 1 decides which vehicle to dispatch. In step S106, the dispatch process mode may be changed from the first mode to the second mode, or from the first mode to the third mode.

[0072] [Dispatch processing using Mode 1] Figure 5 is a flowchart of the dispatch process in the first mode according to an embodiment of the present invention. In the dispatch process in the first mode, a dispatch request is sent to the driver terminal 5, and the driver terminal 5 may be capable of receiving input for dispatch.

[0073] First, the server device 3 calculates an estimated waiting time for the dispatch request stored in step S104 (step S201) and sends it to the user terminal 2 (step S202). The user terminal 2 receives the transmitted estimated waiting time (step S203) and displays it on the display screen (step S204).

[0074] The method for calculating the estimated waiting time in step S201 is not particularly limited and can be designed as appropriate. The estimated waiting time may be calculated, for example, by adding a predetermined time range to the length of the waiting time calculated by the method described in step S105 above. For example, if the waiting time is calculated to be 10 minutes, then 10 to 15 minutes, which is calculated by adding 0 to 5 minutes to the waiting time, may be used as the estimated waiting time.

[0075] The user checks the estimated waiting time displayed on user terminal 2 and decides whether or not to actually request a ride. If the user decides to request a ride, they can input information to confirm the request by pressing a button to confirm the ride request displayed on user terminal 2.

[0076] User terminal 2 receives input to confirm the dispatch request (step S205) and sends the dispatch request to server device 3 (step S206). Server device 3 receives the transmitted dispatch request (step S207) and stores it in storage unit 33 (step S208).

[0077] In step S208, the dispatch request may be stored in association with the content of the dispatch request stored in step S104, that is, in association with the identification information of the dispatch request. The manner in which the dispatch request is stored in association with the content of the dispatch request is not particularly limited and can be designed as appropriate. It is sufficient that the server device 3 can manage the content of the dispatch request in a manner that allows it to identify that the dispatch request has been finalized.

[0078] Next, the server device 3 identifies the driver who will accept the dispatch request stored in step S208 (hereinafter also referred to as the driver making the acceptance request) (step S209). The server device 3 sends a request to the driver terminal 5 operated by the identified driver to accept the dispatch request (hereinafter also referred to as the acceptance request) (step S210). The driver terminal 5 receives the transmitted acceptance request (step S211) and displays the acceptance request (step S212).

[0079] The method for identifying the driver to be assigned in step S209 is not particularly limited and can be designed as appropriate. For example, the server device 3 may identify a driver whose travel time to the meeting place in the dispatch request is short. Also, in step S209, one driver may be identified, or multiple drivers may be identified.

[0080] In step S210, the details of the dispatch request may be sent along with the request for acceptance of the assignment. Also, in step S212, the details of the dispatch request may be displayed along with the request for acceptance of the assignment.

[0081] The driver can check the details of the dispatch request displayed on the driver terminal 5 and decide whether or not to accept the dispatch request. If the driver decides to accept the request, the driver can input the information to accept the request by pressing the acceptance button displayed on the driver terminal 5.

[0082] If the driver terminal 5 receives input to accept the assignment (YES in step S213), information indicating acceptance of the assignment (hereinafter also referred to as assignment information) is transmitted from the driver terminal 5 to the server device 3 (step S214). The server device 3 receives the transmitted assignment information (step S215). The server device 3 stores information indicating that the vehicle assignment has been confirmed (hereinafter also referred to as vehicle assignment confirmation information) in the storage unit 33 (step S216), and the vehicle assignment process in the first mode is completed.

[0083] On the other hand, if the driver terminal 5 does not accept input to accept the assignment within the predetermined time (NO in step S213), step S209 is executed again, and the server device 3 identifies the next driver to request the assignment from. Steps S209 to S213 are repeated until input to accept the assignment is accepted by any of the driver terminals 5.

[0084] In step S216, the dispatch confirmation information may be stored in association with the details of the dispatch request stored in step S104, that is, in association with the dispatch request identification information. For example, the status of the dispatch request, which is stored in association with the dispatch request identification information, may be updated to "dispatch confirmed". Alternatively, for example, the identification information of the assigned driver may be stored in association with the dispatch request identification information.

[0085] When dispatch processing is performed in the first mode, the driver can decide whether or not to accept the assignment, so the driver is responsible for determining which vehicle will actually be dispatched. When dispatch processing is performed in the first mode, information regarding the dispatch request may or may not be sent to the operator terminal 4. When dispatch processing is performed in the first mode, an acceptance instruction does not need to be sent to the driver terminal 5.

[0086] Next, the dispatch process using the second mode will be described. Figure 6 is a flowchart of the dispatch process using the second mode according to an embodiment of the present invention. In the dispatch process using the second mode, information regarding the dispatch request may be transmitted to the operator terminal 4. In addition, in the dispatch process using the second mode, the length of the user's waiting time until a vehicle is dispatched may be transmitted to the operator terminal 4.

[0087] First, the server device 3 calculates an estimated waiting time for the dispatch request stored in step S104 (step S301). The server device 3 transmits the calculated estimated waiting time and the details of the dispatch request stored in step S104 (i.e., information related to the dispatch request) to the operator terminal 4 (step S302). The operator terminal 4 receives the transmitted estimated waiting time and the details of the dispatch request (i.e., information related to the dispatch request) (step S303) and displays them on the display screen (step S304).

[0088] The method for calculating the estimated waiting time in step S301 can adopt the explanation for dispatch processing in the first mode to the extent necessary.

[0089] In step S304, the operator terminal 4 may display a list of information stored in the server device 3 regarding dispatch requests with the status "Not Dispatched" and an estimated waiting time.

[0090] The operator may confirm the estimated waiting time and the details of the dispatch request displayed on the operator terminal 4 and then call the user to receive a formal dispatch request from the user. Alternatively, the server device 3 may send the estimated waiting time to the user terminal 2, and the operator may receive a dispatch request from the user terminal 2. In this case, the description used in the dispatch process in the first mode can be adopted to the extent necessary. The operator may also input information indicating that a formal dispatch request has been received into the operator terminal 4 and send it from the operator terminal 4 to the server device 3.

[0091] After receiving a formal dispatch request from a user, the operator can decide which vehicle to dispatch based on factors such as waiting time and the location information of available vehicles. The operator may then, for example, instruct the driver of the dispatched vehicle to accept the dispatch request via wireless communication. Alternatively, the operator may, for example, send an instruction to accept the dispatch request (hereinafter also referred to as an acceptance instruction) from the operator terminal 4 to the driver terminal 5 operated by the driver of the vehicle. After conveying the acceptance instruction to the driver of the dispatched vehicle, the operator may input dispatch confirmation information into the operator terminal 4.

[0092] The operator terminal 4 accepts the input of dispatch confirmation information (step S305). The operator terminal 4 transmits the dispatch confirmation information to the server device 3 (step S306). The server device 3 receives the transmitted dispatch confirmation information (step S307) and stores it in the storage unit 33 (step S308). This completes the dispatch process in the second mode.

[0093] Regarding dispatch confirmation information, the description used in dispatch processing under Mode 1 can be adopted to the extent necessary.

[0094] When dispatch processing is performed using the second mode, the operator is responsible for determining which vehicle will actually be dispatched. When dispatch processing is performed using the second mode, it is not necessary for the driver terminal 5 to be able to accept input for assignment.

[0095] Next, the dispatch process using the third mode will be described. Figure 7 is a flowchart of the dispatch process using the third mode according to an embodiment of the present invention. In the dispatch process using the third mode, an assignment instruction may be sent to the driver terminal 5.

[0096] First, the server device 3 calculates an estimated waiting time for the dispatch request stored in step S104 (step S401) and sends it to the user terminal 2 (step S402). The user terminal 2 receives the transmitted estimated waiting time (step S403) and displays it on the display screen (step S404).

[0097] The method for calculating the estimated waiting time in step S401 can adopt the explanation for dispatch processing in the first mode to the extent necessary.

[0098] Regarding the manner in which users input information to confirm their dispatch request, the explanation in the dispatch process using the first mode can be adopted to the extent necessary.

[0099] User terminal 2 accepts input to confirm the dispatch request (step S405) and sends the dispatch request to server device 3 (step S406). Server device 3 receives the transmitted dispatch request (step S407) and stores it in storage unit 33 (step S408).

[0100] Regarding the manner in which the dispatch request is stored in step S408, the explanation in the dispatch processing in the first mode can be adopted to the extent necessary.

[0101] Next, the server device 3 identifies a driver (hereinafter also referred to as the driver issuing the acceptance instruction) who is instructed to accept the dispatch request stored in step S408 (step S409). The server device 3 sends the acceptance instruction to the driver terminal 5 operated by the identified driver (step S410). The driver terminal 5 receives the transmitted acceptance instruction (step S411) and displays the acceptance instruction (step S412).

[0102] The method for identifying the driver to be assigned in step S409 is not particularly limited and can be designed as appropriate. For example, the server device 3 may identify the driver whose travel time to the meeting place in the dispatch request is short. In step S409, driver 1 is identified.

[0103] In step S410, the details of the dispatch request may be transmitted along with the assignment instruction. In step S412, the details of the dispatch request may be displayed along with the assignment instruction.

[0104] Regarding dispatch confirmation information, the description used in dispatch processing under Mode 1 can be adopted to the extent necessary.

[0105] When dispatch processing is performed in the third mode, system 1 (for example, server device 3) is responsible for determining which vehicle will actually be dispatched. When dispatch processing is performed in the third mode, information regarding the dispatch request may or may not be sent to the operator terminal 4. When dispatch processing is performed in the third mode, it may be impossible for the driver terminal 5 to accept input for assignment.

[0106] In addition to receiving dispatch requests from System 1, drivers may also be approached by customers (different from users who make dispatch requests using System 1) while actually driving, and may be asked to transport or drive these customers. When it rains, when events such as fireworks displays are held, or during peak commuting hours, there are many customers who want to use vehicles, resulting in a shortage of vehicles. In such situations of vehicle shortage, if dispatch processing is performed in a mode where drivers can freely accept dispatch requests, there is a possibility that no drivers will be available to accept the requests. Therefore, when it is expected that drivers will be busy and it will be difficult for them to accept dispatch requests, as described above, dispatch processing will be performed in a mode where drivers cannot freely accept dispatch requests, making it possible to appropriately dispatch vehicles in response to dispatch requests received through System 1.

[0107] Furthermore, if the dispatch request status no longer meets the prescribed conditions, the server device 3 may control the dispatch processing mode to change to the first mode.

[0108] In the above, the second and third modes were given as examples of modes different from the first mode, but the number and content of modes different from the first mode are not particularly limited and can be designed as appropriate. Similarly, the content of the first mode is not particularly limited and can be designed as appropriate. In each different mode, the content of each process constituting the dispatch process (content of information, content of calculations, etc.), the type of computer device that is the main component of each process (user terminal 2, server device 3, operator terminal 4, driver terminal 5, etc.), and the order of sending and receiving information may differ. In addition, some processes may be the same in each different mode.

[0109] Furthermore, although the above describes a configuration in which dispatch processing is normally performed using the first mode, and dispatch processing is performed using a mode different from the first mode when predetermined conditions are met, System 1 may also be capable of performing dispatch processing using two or more modes depending on two or more conditions.

[0110] For example, System 1 (e.g., Server Device 3) may be controlled to execute dispatch processing in the first mode when the status of the dispatch request satisfies a first predetermined condition, to execute dispatch processing in the second mode when the status of the dispatch request satisfies a second predetermined condition, and to execute dispatch processing in the third mode when the status of the dispatch request satisfies a third predetermined condition. Furthermore, in dispatch processing in the first mode, an acceptance request may be sent to the driver terminal 5, and the driver terminal 5 may be able to accept input for acceptance; in dispatch processing in the second mode, information regarding the dispatch request may be sent to the operator terminal 4; and in dispatch processing in the third mode, an acceptance instruction may be sent to the driver terminal 5.

[0111] In this case as well, the content of the specified conditions is not particularly limited and can be designed as appropriate. For example, the specified conditions may be the length of time until a dispatch request is accepted by a driver, the percentage of dispatch requests accepted by drivers, the length of time the user waits until a vehicle is dispatched, the number of dispatch requests, and / or conditions related to input from the operator.

[0112] Furthermore, one of the multiple modes may be set as the normal mode. For example, the first mode may be the normal mode, and the first predetermined condition may not satisfy the second predetermined condition and the third predetermined condition.

[0113] The predetermined conditions may be, for example, conditions regarding the driver's workload, determined from the dispatch request status in System 1 or the dispatch request status from the operator's perspective. For example, the second predetermined condition may be a condition in which the driver is considered busier than the first predetermined condition, and the third predetermined condition may be a condition in which the driver is considered busier than the second predetermined condition. In this case, it is possible to switch the dispatch processing mode according to the driver's workload.

[0114] Thus, by providing a control means that enables a system comprising at least one computer device to perform dispatch processing to determine which vehicle will be dispatched to the user in two or more different modes, a system capable of performing dispatch processing in two or more different modes can be provided.

[0115] Furthermore, the system includes a driver terminal operated by the driver of the vehicle dispatched to the user, and the control means controls the system to execute dispatch processing in a first mode if predetermined conditions are not met regarding the status of the dispatch request, and to execute dispatch processing in a mode different from the first mode if predetermined conditions are met regarding the status of the dispatch request, and in dispatch processing in the first mode, an acceptance request is sent to the driver terminal, and the driver terminal is capable of receiving input for acceptance, so that when predetermined conditions are met regarding the status of the dispatch request, dispatch processing can be executed in a mode different from the mode in which the driver can make input for acceptance.

[0116] Furthermore, the system includes an operator terminal operated by an operator who determines which vehicle will be dispatched to the user. In dispatch processing using a mode different from the first mode, information regarding the dispatch request is transmitted to the operator terminal, allowing the operator to understand the dispatch request information.

[0117] Furthermore, in dispatch processing using a mode different from the first mode, an assignment acceptance instruction can be sent to the driver's terminal, thereby instructing the driver to accept the assignment.

[0118] Furthermore, the system includes a driver terminal operated by the driver of the vehicle dispatched to the user, and an operator terminal operated by the operator who determines which vehicle is dispatched to the user. The control means controls the system to execute dispatch processing in a first mode when the status of the dispatch request satisfies a first predetermined condition, to execute dispatch processing in a second mode when the status of the dispatch request satisfies a second predetermined condition, and to execute dispatch processing in a third mode when the status of the dispatch request satisfies a third predetermined condition. In dispatch processing in the first mode, the system sends a request to the driver terminal. A request is sent, and the driver terminal is capable of receiving input to accept the assignment. In dispatch processing using the second mode, information regarding the dispatch request is sent to the operator terminal. In dispatch processing using the third mode, an assignment acceptance instruction is sent to the driver terminal. Depending on the status of the dispatch request, dispatch processing can be performed in a mode in which the driver can make input to accept the assignment, in a mode in which the operator can grasp information regarding the dispatch request, or in a mode in which the operator can instruct the driver to accept the assignment.

[0119] Furthermore, in dispatch processing using a mode different from the first mode, or in dispatch processing using the second mode, the length of the user's waiting time until a vehicle is dispatched is transmitted to the operator terminal, allowing the operator to understand the length of the user's waiting time. Note that "the length of the user's waiting time until a vehicle is dispatched" only needs to be information that allows the user to understand the length of their waiting time, and may be displayed as a fixed time length (e.g., "10 minutes") or as a time length with a range (e.g., "10-15 minutes").

[0120] Furthermore, if the predetermined conditions are the length of time until a dispatch request is accepted by a driver, the percentage of dispatch requests accepted by drivers, the length of time the user waits until a vehicle is dispatched, the number of dispatch requests, and / or conditions related to input from the operator, then the dispatch processing mode can be determined according to the length of time until a dispatch request is accepted by a driver, the percentage of dispatch requests accepted by drivers, the length of time the user waits until a vehicle is dispatched, the number of dispatch requests, and / or conditions related to input from the operator.

[0121] <Second Embodiment> The following describes a dispatch system that performs dispatch processing in response to dispatch requests from users. The explanations in Figures 1 to 3 above also apply to the second embodiment. The dispatch system can be applied to dispatching vehicles for users to utilize designated driver services or to dispatch vehicles for users to utilize taxi services.

[0122] The dispatch system allows users to request a ride via telephone or fax, and also allows them to request a ride using an application (hereinafter referred to as "app") installed on their user terminal 2 (for example, a smartphone or tablet). Here, the app may be a dedicated application for using the dispatch system (a so-called native app), or it may be a web app that uses a browser.

[0123] The dispatch process in the second embodiment will now be described with reference to Figure 8. Figure 8 is a flowchart of the dispatch process according to an embodiment of the present invention.

[0124] In step S1, information regarding dispatch requests from users via telephone or fax is registered in server device 3. In step S1, information regarding dispatch requests from users via communication tools such as LINE®, Messenger®, SMS, and e-mail may also be registered in server device 3. When a user makes a dispatch request using these communication tools, they may contact the official account of the operator running the dispatch system, or they may contact the account owned by the request recipient.

[0125] Step S1 is performed as follows: For example, when a user calls a designated phone number, a request receiver answers the phone. The request receiver may be a person who also acts as an operator, or a person who is different from an operator. When the request receiver answers the phone, the request receiver asks the user for the location where they would like the vehicle to be dispatched (i.e., the location the user designates for dispatch), the date and time the user would like the vehicle to be dispatched (this may be a specific time, or an abstract request without a time designation, such as "I would like the vehicle dispatched as soon as possible"), the destination of the vehicle after dispatch, and any information that can identify the user. The location where the user would like the vehicle to be dispatched (i.e., the location the user designates for dispatch) may be, for example, an address or a facility name. The information that can identify the user is not particularly limited as long as it can identify the user, and may include, for example, the user's name, membership number for using the dispatch system, and mobile phone number. Furthermore, when using a dispatch system for dispatching designated drivers, information that can identify the user may include the user's name, membership number, mobile phone number, and other information related to the vehicle for which the designated driver service is requested (for example, vehicle type, body color, and license plate number (vehicle registration number)).

[0126] The request receiver can inform the user who has requested a vehicle by telephone of the estimated waiting time until the vehicle arrives at the location specified by the user. The request receiver may refer to the list of unassigned requests (meaning requests for which a vehicle has not yet been assigned) described later and inform the user of the waiting time they predict based on their experience, or they may inform the user of the waiting time calculated by server device 3. Server device 3 can calculate the waiting time based on the desired location for vehicle dispatch, the number of dispatch requests from multiple users (for example, the number of dispatch requests for which a vehicle has not yet been assigned), the number and location of vehicles that can be dispatched by the dispatch system, the number and location of vehicles that have not yet been dispatched, and the route from the vehicle's location to the desired location. The waiting time calculated by server device 3 is transmitted from server device 3 to operator terminal 4 and displayed on the display screen of the request receiver terminal.

[0127] The user asks the request handler about the waiting time and informs the request handler by phone whether or not they want to formally request a vehicle dispatch. The request handler who receives the request for a vehicle dispatch from the user inputs the desired location for vehicle dispatch, the desired date and time for vehicle dispatch, the destination of the vehicle after dispatch, and any information that can identify the user, using the request handler's terminal (or operator terminal 4 if the request handler is also an operator).

[0128] Even when a user requests a ride using a communication tool instead of by phone, the request receiver will communicate with the user using the communication rules, informing them of the waiting time and confirming whether they wish to formally request a ride. Once the request receiver receives a ride request from the user, the request receiver operates their terminal to input the information obtained from the user using the communication tool (desired location for vehicle dispatch, desired date and time for vehicle dispatch, destination of the vehicle after dispatch, information that can identify the user, etc.).

[0129] If a user sends a fax to a designated fax number instead of making a phone call, the request receiver will receive the fax. The fax will contain information such as the desired location for vehicle dispatch, the desired date and time for vehicle dispatch, the vehicle's destination after dispatch, and information that can identify the user. The request receiver will then input this information using their terminal.

[0130] Information regarding the dispatch request, such as the desired location for vehicle dispatch, the desired date and time for vehicle dispatch, the destination of the vehicle after dispatch, and information that can identify the user, is transmitted from the request recipient terminal to the server device 3 and received by the server device 3. The received dispatch request information is stored in the storage means of the server device 3 and registered as an undispatched request. This entered information, such as the desired location for vehicle dispatch, the desired date and time for vehicle dispatch, the destination of the vehicle after dispatch, and information that can identify the user, is registered in association with each other. Information regarding the registered undispatched dispatch requests is transmitted to the operator terminal 4 and displayed as a list of undispatched requests on the display screen of the operator terminal 4.

[0131] Next, we will explain step S2. In step S2, information regarding dispatch requests from users using the app is registered in server device 3. Step S2 is executed as follows: The user operates user terminal 2 and uses the app to input information regarding the dispatch request, such as the desired location for vehicle dispatch, the desired date and time for vehicle dispatch, the destination of the vehicle after dispatch, and information that can identify the user. Information that can identify the user may also be entered when logging into the app.

[0132] Information regarding the dispatch request, such as the desired location for vehicle dispatch, the desired date and time for vehicle dispatch, the destination of the vehicle after dispatch, and information that can identify the user, is transmitted from the user terminal 2 to the server device and stored in the storage means of the server device 3, where it is registered as an undispatched request. This entered information, such as the desired location for vehicle dispatch, the desired date and time for vehicle dispatch, the destination of the vehicle after dispatch, and information that can identify the user, is registered in association with each other. Information regarding the registered undispatched dispatch requests is transmitted to the operator terminal 4 and displayed as a list of undispatched requests on the display screen of the operator terminal 4.

[0133] Server device 3 stores information regarding dispatch requests from users via telephone or fax, as well as information regarding dispatch requests from users via the app. This information is then displayed on the operator terminal 4's display screen as undispatched requests. The operator refers to the information regarding the undispatched requests displayed on the screen and sends dispatch instructions to drivers to operate the vehicles, or sends acceptance requests to drivers to accept the dispatch.

[0134] Once step S2 is completed, step S3 is executed. In step S3, in order to request a driver to accept the dispatch, the operator operates the operator terminal 4 and inputs the estimated waiting time for each dispatch request registered using the app until the vehicle arrives at the location desired by the user. The operator may input a waiting time predicted by the operator based on experience while referring to a list of undispatched cases, or they may input a waiting time calculated by the server device 3. The server device 3 can calculate the waiting time based on the desired location for vehicle dispatch, the number of dispatch requests from multiple users (for example, the number of dispatch requests for which dispatch has not yet been decided), the number and location of vehicles that can be dispatched by the dispatch system, the number and location of vehicles that have not yet been dispatched, and the route from the vehicle's location to the desired location. The waiting time calculated by the server device 3 is transmitted from the server device 3 to the operator terminal 4 and displayed on the display screen of the operator terminal 4.

[0135] Once step S3 is completed, step S4 is executed. In step S4, the user terminal 2 receives a response indicating whether or not to formally request a vehicle dispatch order. First, the waiting time entered or calculated in the operator terminal 4 in step S3 is sent from the operator terminal 4 to the server device 3, and then from the server device 3 to the user terminal 2. The user terminal 2 displays the received waiting time along with options to choose whether or not to formally request a vehicle dispatch order. After confirming the waiting time, the user operates the user terminal 2 to select whether or not to formally request a vehicle dispatch order. Information on which option was selected by the user terminal 2 is sent to the server device 3.

[0136] If a user operates user terminal 2 and selects not to request a dispatch order, the dispatch process is terminated. Server device 3 registers the information regarding the registered dispatch order for the user who selected not to request a dispatch order as having been canceled. Information regarding the dispatch order that has been registered as canceled is removed from the list of undispatched cases on the display screen of operator terminal 4 and displayed in the list of processed cases (list of cases where dispatch has been completed and cases that have been canceled).

[0137] On the other hand, if in step S4 the user terminal 2 selects a response indicating that they are formally requesting a vehicle dispatch order, the process proceeds from step S4 to step S5.

[0138] Next, step S5 will be explained. In step S5, dispatch instructions are issued for dispatch requests that were registered as undispatched cases in step S1, and for dispatch requests for which a formal dispatch instruction request was sent from the user terminal 2 in step S4. The timing of the dispatch instructions in step S5 can be designed as appropriate, but for example, it may be executed a predetermined time before the scheduled time when the vehicle is expected to arrive at the location desired by the user. Here, the scheduled time when the vehicle is expected to arrive at the location desired by the user may be a time determined based on the waiting time mentioned above. The scheduled time may be a time determined based on the waiting time entered by the operator into the operator terminal 4, or it may be a time determined based on the waiting time calculated by the server device 3.

[0139] The predetermined time is not particularly limited and can be set as appropriate. The predetermined time may be 10 minutes, 8 minutes, or 5 minutes. For example, if the predetermined time is 10 minutes, the dispatch instruction will be issued 10 minutes before the scheduled arrival time of the vehicle.

[0140] A dispatch order is issued by selecting one vehicle from among several vehicles that have not yet been dispatched. Even if a vehicle has already been dispatched and is en route to its destination, if its arrival time at the destination is predicted and dispatch is possible, these vehicles can also be included in the dispatch order. Dispatch orders may be issued by operating the operator terminal 4, or they may be issued automatically by the server device 3.

[0141] When a dispatch order is issued by an operator, the operator can select which vehicle to dispatch, taking into account the user's desired location, while checking the vehicle's position on the map screen displayed on the operator terminal 4. The vehicle's position can be determined based on the location identified by the GPS installed in the driver terminal 5 owned by the driver operating the vehicle.

[0142] When a dispatch instruction is issued by server device 3, server device 3 can identify the vehicle to be dispatched based on information such as the location where the user wishes to dispatch the vehicle, and the locations of multiple vehicles.

[0143] A dispatch instruction is sent from the server device 3 to the driver terminal 5 corresponding to the identified vehicle. The server device 3 sends information related to the dispatch request to the driver terminal 5, including information that can identify the user who requested the dispatch and the location where the user wishes to have the vehicle dispatched. In addition, the server device 3 may also send information to the driver terminal such as the destination of the vehicle after dispatch and the estimated arrival time of the vehicle that was sent to the user terminal 2. This information sent from the server device 3 is displayed on the display screen of the driver terminal 5. The driver who owns the driver terminal 5 moves the vehicle to the location where the user wishes to have the vehicle dispatched, according to the information displayed on the display screen.

[0144] In step S6, the server device 3 registers that the dispatch instruction has been executed for the dispatch request for which a vehicle dispatch instruction was executed in step S5. Information regarding the dispatch request for which the dispatch instruction has been executed is removed from the list of undispatched cases on the display screen of the operator terminal 4 and displayed in the list of processed cases (list of cases for which dispatch has been completed and cases that have been canceled). When step S6 is executed, the dispatch process is completed.

[0145] By the way, in the above, when information regarding a vehicle dispatch request is entered on the user terminal 2 using the application and the dispatch request information is sent to the server device 3, the system proceeds to step S2. However, instead of step S2, the system may proceed to step S7. Whether to proceed to step S2 or step S7 when the dispatch request information is sent to the server device 3 can be selected and switched by the dispatch system administrator.

[0146] Step S7 will now be explained. When the server device 3 receives information regarding a vehicle dispatch request from the user terminal 2, the server device 3 calculates the estimated waiting time until the vehicle arrives at the location the user desires, based on the location the user desires the vehicle to arrive at. The waiting time can be calculated not only based on the location the user desires the vehicle to arrive at, but also based on the number of dispatch requests from multiple users (for example, the number of dispatch requests for which a dispatch has not yet been decided), the number and location of vehicles that can be dispatched by the dispatch system, and the number and location of vehicles that have not yet been dispatched.

[0147] If the information regarding the dispatch request meets the predetermined conditions, the process moves from step S7 to S2. The predetermined conditions can be set as appropriate, but examples include the calculated waiting time being equal to or greater than a predetermined time, the calculated waiting time being longer than a predetermined time, the number of dispatch requests from multiple users being equal to or greater than a predetermined number, or the number of dispatch requests from multiple users being greater than a predetermined number. For example, if the calculated waiting time is equal to or greater than a predetermined time, or if the calculated waiting time is longer than a predetermined time, the process moves from step S7 to S2. Here, the predetermined time can be set as appropriate. The predetermined time may be, for example, 7 minutes, 5 minutes, or 3 minutes.

[0148] Furthermore, if the number of users who have not been assigned a vehicle is significantly larger than the number of vehicles that can be assigned, the server device 3 may not be able to calculate the waiting time. Even in such cases where the waiting time cannot be calculated, the condition that the calculated waiting time is equal to or greater than a predetermined time can be met.

[0149] If the dispatch request information does not meet the specified conditions, the process proceeds to step S8 or S9. For example, if the calculated waiting time is less than or equal to the specified time, or if the calculated waiting time is less than the specified time, the process proceeds to step S8 or S9. The dispatch system administrator can select and switch between proceeding to step S8 or step S9 when the calculated waiting time is less than or equal to the specified time, or if the calculated waiting time is less than the specified time.

[0150] In step S8, the server device 3 sends a dispatch request to one of the multiple driver terminals 5, asking it to accept the dispatch assignment, and the dispatch request and vehicle matching is performed. The vehicle to which the dispatch request is sent from the server device 3 is selected from among multiple vehicles that have not yet been instructed to be dispatched. Even if a vehicle has already been dispatched and is heading to its destination, if the time of its arrival at the destination is predicted and dispatch is possible, these vehicles can also be included in the dispatch request. Based on information such as the location where the user wishes to have the vehicle dispatched and the locations of multiple vehicles, the server device 3 identifies the one vehicle to which the dispatch request is sent and sends the dispatch request to the corresponding driver terminal 5. The dispatch request sent to the driver terminal 5 includes information about the dispatch request, such as the location where the user wishes to have the vehicle dispatched.

[0151] When the driver terminal 5 receives a dispatch request, the display screen of the driver terminal 5 shows that a dispatch request has been received and the location where the user wishes to have the vehicle dispatched. The driver confirms the displayed information and then operates the driver terminal 5 to input whether or not to accept the dispatch request. If the option to accept the dispatch request is selected on the driver terminal 5, the driver terminal 5 notifies the server device 3 that the dispatch request has been accepted. Then, the process proceeds from step S8 to step S6.

[0152] If the driver terminal 5 selects the option to decline the assignment request, it notifies the server device 3 that it will not accept the assignment request. In this case, the server device 3 sends an assignment request to another driver terminal 5. The other driver terminal 5 that receives the assignment request is asked whether to accept or decline the request. In this way, matching a vehicle (driver) with a user is repeatedly performed for one dispatch request until an assignment request is accepted by one of the driver terminals 5 and a match is made.

[0153] In step S8, if a predetermined time has elapsed since the vehicle-user matching process began, or since the first dispatch request was received, and no driver terminal 5 has accepted the request, and matching has not been completed, the dispatch request may proceed to step S2.

[0154] In step S9, the server device 3 automatically sends a dispatch instruction to the driver terminal 5. The server device 3 identifies one of several vehicles that have not yet received a dispatch instruction, which is the vehicle to be dispatched. Upon receiving the dispatch instruction, the driver terminal 5 moves the vehicle according to the dispatch request without refusing the instruction. Once the dispatch instruction is automatically sent from the server device 3 to the driver terminal 5 in step S9, the process moves from step S9 to step S6. [Explanation of Symbols]

[0155] 1 System 2 User terminals 3 Server equipment 4. Operator terminal 5. Driver terminal 6. Communication Network 21 Control Unit 22 RAM 23 Storage Section 24 Input section 25 Display section 26 Communication Interfaces 31 Control Unit 32 RAM 33 Storage Section 34 Communication Interfaces

Claims

1. A system comprising at least one computer device, A dispatch request receiving means that receives a first dispatch request for a vehicle from an operation on a user terminal operated by the user, In order to dispatch a vehicle to a location specified by a user, the operator's terminal, which is operated by an operator who issues a dispatch instruction to a driver to dispatch a vehicle, or an acceptance request to a driver to accept a dispatch, is controlled by a display control means to display information related to the first dispatch request received by the dispatch request receiving means. A system equipped with these features.

2. A dispatch request input means that receives information regarding a second dispatch request from a user via telephone or fax, through an operation on a request reception terminal operated by a request receptionist who receives a second dispatch request from a user. Equipped with, The system according to claim 1, wherein the display control means controls the display of information regarding a second dispatch request received by the dispatch request input means, along with information regarding a first dispatch request.

3. A waiting time transmission means, upon receiving a first dispatch request via a dispatch request receiving means, transmits to the user terminal information regarding the waiting time until the vehicle arrives at the location specified by the user in the first dispatch request. A dispatch instruction transmission means that, upon receiving a dispatch instruction request from a user terminal that has received a waiting time, automatically or by operation on the operator terminal transmits a vehicle dispatch instruction to a driver terminal operated by a driver operating a vehicle, for the first dispatch request. Equipped with, The system according to claim 1 or 2, wherein information regarding waiting times is calculated by the system, or the system receives input through an operation on an operator terminal.

4. A dispatch instruction transmission means automatically or via operation to an operator terminal transmits a vehicle dispatch instruction to a driver terminal operated by a driver operating a vehicle, based on a first dispatch request received by a dispatch request receiving means, or a second dispatch request entered by a dispatch request input means. The system according to claim 2, comprising:

5. A dispatch information transmission means transmits to a user terminal information regarding the vehicle to be driven by the driver terminal corresponding to the dispatch instruction, and information regarding the estimated time of arrival of the vehicle at the location specified by the user in the first dispatch request or the second dispatch request. Equipped with, The system according to claim 4, wherein information regarding the expected arrival time of the vehicle is calculated by the system, or the system receives input through an operation on the operator terminal.

6. The system according to claim 1 or 2, wherein the display control means controls the display of information relating to the first dispatch request for first dispatch requests that meet predetermined conditions among the first dispatch requests received by the dispatch request receiving means.

7. The specified conditions are that the waiting time until the vehicle arrives at the location specified by the user in the first dispatch request is equal to or greater than a specified time, or that the waiting time is longer than a specified time. The system according to claim 6.

8. For a first dispatch request that does not meet the specified conditions, the dispatch request receiving means transmits an acceptance request to the driver terminal operated by the driver who will automatically drive the vehicle, requesting acceptance of the dispatch of the vehicle for the first dispatch request received by the dispatch request receiving means. Equipped with, The system according to claim 6, wherein the display control means is controlled to display information regarding the first dispatch request if it has not received an acceptance notification from the driver terminal acknowledging acceptance of the vehicle dispatch request even after a second predetermined time has elapsed.

9. A dispatch instruction transmission means automatically transmits a vehicle dispatch instruction to a driver terminal operated by a driver who will be driving the vehicle, for first dispatch requests received by the dispatch request receiving means that do not meet the predetermined conditions. The system according to claim 6, comprising:

10. A method performed in a system comprising at least one computer device, A dispatch request receiving step, which receives a first dispatch request for a vehicle from an operation on a user terminal operated by the user, In order to dispatch a vehicle to a location specified by the user, the operator's terminal, which is operated by an operator who issues a dispatch instruction to a driver to dispatch a vehicle, or an acceptance request to a driver to accept a dispatch, is controlled to display information related to the first dispatch request received in the dispatch request reception step. A method having

11. Computer equipment, A dispatch request receiving means that receives a first dispatch request for a vehicle from an operation on a user terminal operated by the user, Display control means for an operator terminal operated by an operator who issues a dispatch instruction to a driver to dispatch a vehicle to a location specified by a user, or an acceptance request to a driver to accept a dispatch, to display information related to the first dispatch request received by the dispatch request receiving means. A program that makes something function as such.

Images