Vehicle dispatch management system, vehicle dispatch management apparatus, method for managing vehicle dispatch, and program

Abstract

To appropriately set a fee associated with the use of a vehicle.SOLUTION: In a vehicle dispatch management apparatus of the present invention capable of communicating via a network with a user terminal 20 and a vehicle terminal provided in a vehicle, the apparatus includes at least one processor. The processor receives, from the user terminal 20, a dispatch request to which information regarding predetermined setting items is added, determines a fee on the basis of the information regarding the predetermined setting items, allocates a vehicle to the dispatch request, causes the vehicle terminal provided in the allocated vehicle to output information indicating that the vehicle has been assigned to the dispatch request, receives information from the vehicle terminal indicating acceptance of the dispatch request, and then causes the determined fee to be output to the user terminal 20.SELECTED DRAWING: Figure 13

Description

[Technical Field]

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

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

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

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

[0005] In Japanese ride-sharing services, private cars are often used as commercial vehicles, which are the means of transportation for users. However, vehicles such as private cars are not equipped with fare meters that update the fare according to the distance traveled, making it impossible to set appropriate fees for vehicle use.

[0006] In view of the above problems, the present invention aims to provide a vehicle dispatch management system, a vehicle dispatch management device, a vehicle dispatch management method, and a program that are capable of appropriately setting fees associated with vehicle use. [Means for solving the problem]

[0007] In order to solve the above problem, in the vehicle dispatch management system of the present invention, which includes a user terminal, a vehicle terminal installed in a vehicle, and a vehicle dispatch management device capable of communicating with the user terminal and the vehicle terminal via a network, the user terminal includes one or more first processors, the vehicle dispatch management device includes one or more second processors, and the vehicle terminal includes one or more third processors, the first processor sends a vehicle dispatch request to the vehicle dispatch management device, with information regarding specified setting items added, in response to user input, the second processor determines a fare based on the information regarding the specified setting items, assigns a vehicle to the vehicle dispatch request, and causes the vehicle terminal installed in the vehicle to which the vehicle dispatch request has been assigned to output information indicating that the vehicle has been the subject of the vehicle dispatch request, the third processor sends information indicating acceptance of the vehicle dispatch request to the vehicle dispatch management device in response to input from the driver of the vehicle to which the vehicle dispatch request has been assigned, and after receiving the information indicating acceptance of the vehicle dispatch request from the vehicle terminal, the second processor outputs the determined fare to the user terminal.

[0008] In order to solve the above problems, the vehicle dispatch management system of the present invention includes a user terminal, a vehicle terminal provided in a vehicle, and a vehicle dispatch management device capable of communicating with the user terminal and the vehicle terminal via a network, wherein the user terminal includes one or more first processors, the vehicle dispatch management device includes one or more second processors, and the vehicle terminal includes one or more third processors, and the first processor transmits a vehicle dispatch request to the vehicle dispatch management device, to which information relating to predetermined setting items is added, in response to a user input, and the second processor allocates a vehicle in response to the vehicle dispatch request, and a vehicle terminal provided in the vehicle to which the vehicle dispatch request has been allocated is the third processor outputs information indicating that the vehicle has been the subject of the vehicle dispatch request to the vehicle dispatch management device in accordance with input from the driver of the vehicle to which the vehicle dispatch request has been assigned, information indicating acceptance of the vehicle dispatch request to the vehicle dispatch management device, the second processor, after receiving the information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputs information that enables modification of information regarding the specified setting items to the user terminal, the first processor transmits information regarding the modified specified setting items to the vehicle dispatch management device in accordance with input from the user, and the second processor outputs information regarding the modified specified setting items to the vehicle to which the vehicle dispatch request has been assigned.

[0009] In order to solve the above problems, the vehicle dispatch management device of the present invention, which is capable of communicating with a user terminal and a vehicle terminal installed in a vehicle via a network, comprises one or more processors, and the processor receives a vehicle dispatch request from the user terminal along with information regarding specified setting items, determines a fare based on the information regarding the specified setting items, assigns the vehicle to the vehicle dispatch request, outputs information to the vehicle terminal installed in the vehicle to which the vehicle dispatch request has been assigned indicating that the vehicle has been the subject of the vehicle dispatch request, and, after receiving information from the vehicle terminal indicating acceptance of the vehicle dispatch request, outputs the determined fare to the user terminal.

[0010] In order to solve the above problem, the vehicle dispatch management device of the present invention, which is capable of communicating with a user terminal and a vehicle terminal installed in a vehicle via a network, has one or more processors, and the processor assigns the vehicle to a vehicle dispatch request to which information regarding specified setting items received from the user terminal is attached, outputs information indicating that the vehicle has been the subject of the vehicle dispatch request to the vehicle terminal installed in the vehicle to which the vehicle dispatch request has been assigned, and after receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputs information to the user terminal that allows the information regarding the specified setting items to be changed, and when information regarding the changed specified setting items is received from the user terminal, outputs information regarding the changed specified setting items to the vehicle to which the vehicle dispatch request has been assigned.

[0011] The processor may determine a fee based on information regarding the specified setting item, output the determined fee to the user terminal, and upon receiving information regarding the specified setting item that has been changed from the user terminal, re-determine the fee based on the information regarding the changed specified setting item, and output the re-determined fee to the user terminal.

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

[0013] The predetermined setting items may include toll road information indicating whether or not toll roads are to be used.

[0014] In order to solve the above problem, the vehicle dispatch management method of the present invention includes a computer that receives a vehicle dispatch request from a user terminal along with information regarding specified setting items, determines a fee based on the information regarding the specified setting items, assigns a vehicle to the vehicle dispatch request, outputs information indicating that the vehicle has been the subject of the vehicle dispatch request to a vehicle terminal installed in the vehicle to which the vehicle dispatch request has been assigned, and, after receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputs the determined fee to the user terminal.

[0015] In order to solve the above problem, the vehicle dispatch management method of the present invention involves a computer assigning a vehicle to a vehicle dispatch request that has information regarding specified setting items received from a user terminal, outputting information indicating that the vehicle has been the subject of the vehicle dispatch request to a vehicle terminal installed in the vehicle to which the vehicle dispatch request has been assigned, receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputting information to the user terminal that allows the information regarding the specified setting items to be changed, and upon receiving information regarding the changed specified setting items from the user terminal, outputting information regarding the changed specified setting items to the vehicle to which the vehicle dispatch request has been assigned.

[0016] In order to solve the above problem, the program of the present invention causes a computer to receive a vehicle dispatch request from a user terminal accompanied by information regarding specified setting items, determine a fare based on the information regarding the specified setting items, assign a vehicle to the vehicle dispatch request, output information indicating that the vehicle has been the subject of the vehicle dispatch request to a vehicle terminal installed in the vehicle to which the vehicle dispatch request has been assigned, and, after receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, output the determined fare to the user terminal.

[0017] In order to solve the above problem, the program of the present invention causes a computer to assign a vehicle to a vehicle dispatch request that has information regarding specified setting items received from a user terminal attached thereto, output information indicating that the vehicle has been the subject of the vehicle dispatch request to a vehicle terminal installed in the vehicle to which the vehicle dispatch request has been assigned, and after receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, output information to the user terminal that enables the information regarding the specified setting items to be changed, and upon receiving information regarding the changed specified setting items from the user terminal, output information regarding the changed specified setting items to the vehicle to which the vehicle dispatch request has been assigned. [Effects of the Invention]

[0018] According to the present invention, it is possible to appropriately set fees for vehicle use. [Brief explanation of the drawings]

[0019] [Figure 1] FIG. 1 is a block diagram for explaining an outline of a vehicle dispatch management system. [Figure 2] FIG. 2 is a block diagram illustrating the configuration of a user terminal. [Figure 3] FIG. 3 is a block diagram illustrating the configuration of the taxi terminal. [Figure 4] FIG. 4 is a block diagram illustrating the configuration of the NRS terminal. [Figure 5] FIG. 5 is a block diagram illustrating the configuration of the business server. [Figure 6] FIG. 6 is a block diagram illustrating the configuration of the vehicle dispatch management server. [Figure 7] FIG. 7 is a sequence diagram showing the flow of processing in a vehicle allocation management method by the vehicle allocation management system. [Figure 8] FIG. 8 is an explanatory diagram for explaining the processing of the dispatch unit. [Figure 9] FIG. 9 is an explanatory diagram showing the results of matching by the dispatch unit. [Figure 10] FIG. 1 is a sequence diagram showing a flow of a vehicle transporting a user in a vehicle dispatch management system. [Figure 11] Fig. 11A is a first explanatory diagram for explaining the operation of the user terminal control unit, and Fig. 11B is a second explanatory diagram for explaining the operation of the user terminal control unit. [Figure 12] Fig. 12A is a first explanatory diagram for explaining the operation of the vehicle terminal control unit, and Fig. 12B is a second explanatory diagram for explaining the operation of the vehicle terminal control unit. [Figure 13] FIG. 13 is an explanatory diagram for explaining the operation of the user terminal control unit. [Figure 14] Fig. 14A is a first explanatory diagram for explaining the operation of the user terminal control unit, and Fig. 14B is a second explanatory diagram for explaining the operation of the user terminal control unit. [Figure 15] FIG. 15 is an explanatory diagram for explaining the operation of the user terminal control unit. [Figure 16] FIG. 16 is an explanatory diagram for explaining the operation of the vehicle terminal control unit. [Figure 17] Fig. 17A is a first explanatory diagram for explaining the operation of the user terminal control unit, and Fig. 17B is a second explanatory diagram for explaining the operation of the user terminal control unit. [Figure 18] FIG. 18 is an explanatory diagram for explaining the operation of the user terminal control unit. [Figure 19] Fig. 19A is a first explanatory diagram for explaining the operation of the vehicle terminal control unit, and Fig. 19B is a second explanatory diagram for explaining the operation of the vehicle terminal control unit. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

[0024] The taxi terminal 30 is an electronic device loaned to a taxi driver 3 of a taxi vehicle (first vehicle) 32, or an electronic device owned by the taxi driver 3. The taxi terminal 30 is associated with the taxi vehicle 32. Examples of the taxi terminal 30 include a smartphone, a personal computer, and a tablet PC. The taxi terminal 30 is an example of a vehicle terminal (first vehicle terminal).

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

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

[0027] The NRS terminal 40 is an electronic device owned by the NRS driver 4, and can be placed in the NRS vehicle (second vehicle) 42. Examples of the NRS terminal 40 include a smartphone, a personal computer, and a tablet PC. The NRS driver 4, for example, brings his / her own NRS terminal 40 into the NRS vehicle 42, which is his / her own private car, and drives the NRS vehicle 42. The NRS terminal 40 is not limited to being brought into the vehicle when driving, but may also be pre-installed in the NRS vehicle 42. The NRS terminal 40 is used when the NRS driver 4 is on duty. This makes it possible to use the NRS vehicle 42 as a commercial vehicle in place of the taxi vehicle 32. The NRS terminal 40 is an example of a vehicle terminal (second vehicle terminal).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0061] (Change settings) 10 is a sequence diagram showing the flow of a vehicle transporting a user 2 in the vehicle dispatch management system 1. In this embodiment, the flow of transporting a user 2 will be described according to FIG. 10, focusing on the user application installed on the user terminal 20 and the vehicle application installed on the NRS terminal 40.

[0062] (Setting item input process S11) FIG. 11A is a first explanatory diagram illustrating the operation of the user terminal control unit 170. In response to an operation by user 2, the vehicle dispatch request unit 180 of the user terminal 20 launches a user application for making a vehicle dispatch request 22. Then, as shown in FIG. 11A, the user terminal control unit 170 of the vehicle dispatch management server 60 causes the display device 124 of the user terminal 20 to display a map 210 of a predetermined range including the location of the user terminal 20, a location 212 of the user terminal 20, and a vehicle 214 located near the user terminal 20. The user terminal control unit 170 also causes the display device 124 of the user terminal 20 to display an image 216 prompting the user to input a boarding location and a disembarking location. Here, assume that user 2 inputs, via the input device 126, for example, "1-chome, Shinagawa-ku, Tokyo" as the boarding location and "1-chome, Minato-ku, Tokyo" as the disembarking location in the text boxes of the image 216.

[0063] (Fee determination process S12) FIG. 11B is a second explanatory diagram illustrating the operation of the user terminal control unit 170. Based on the boarding and disembarking locations input through the user application, the user terminal control unit 170 derives the vehicle's mileage and driving time when user 2 actually drives the vehicle. Furthermore, the user terminal control unit 170 determines the fare based on the mileage and driving time using a fare table that associates fare with the mileage, driving time, and fare. The fare increases as the mileage and driving time increase. Furthermore, the user terminal control unit 170 adds a pick-up fee based on driving as a pick-up vehicle and an app arrangement fee based on dispatching a vehicle using the app to the fare. As shown in FIG. 11B, the user terminal control unit 170 displays an image 218 indicating the determined fare on the display device 124 of the user terminal 20. User 2 confirms the fare and determines whether to make a vehicle dispatch request 22.

[0064] In this embodiment, when "taxi vehicles 32 and vehicles with requirements" is selected as the dispatch category and the drop-off location is input, the user terminal control unit 170 sets the fare determined in the fare determination process S12 as the pre-determined fare (pre-determined fare) and uses it as the final fare, regardless of whether the vehicle to be dispatched is a taxi vehicle 32 or an NRS vehicle 42. Note that pre-determined fare, which determines the fare in advance, can be applied depending on the business area, taxi business, etc., and when a "plan with pre-determined fare" is selected in the dispatch request 22, which indicates a desire to determine the fare in advance, the user terminal control unit 170 sets the fare determined in the fare determination process S12 as the pre-determined fare and uses it as the final fare, just as when "taxi vehicles 32 and vehicles with requirements" is selected as the dispatch category. Furthermore, even if the "plan with a pre-determined fare" was not selected in the dispatch request 22, when the NRS vehicle 42 becomes the vehicle to be dispatched, the user terminal control unit 170 subsequently sets the fare determined in the fare determination process S12 as the pre-determined fare and uses it as the final fare. In this case, since the NRS vehicle 42 is not equipped with a fare meter, the user 2 cannot change to payment based on the fare accumulated by the fare meter.

[0065] Furthermore, instead of being limited to the example in which the user terminal control unit 170 sets the fare determined in the fare determination process S12 as the pre-determined fare and uses that as the final fare, the user terminal control unit 170 may temporarily display the fare determined in the fare determination process S12 as the predicted fare on the display device 124 of the user terminal 20, and then redetermine the fare when the dispatch of the vehicle to be dispatched in response to the dispatch request 22 is confirmed, and use the redetermined fare as the pre-determined fare as the final fare. In this case, the predicted fare and the pre-determined fare may refer to different fare tables. However, to prevent user 2 from feeling suspicious, the predicted fare and the pre-determined fare are not significantly different even if the fare tables are different.

[0066] Furthermore, if user 2 wishes to pay based on the fare meter, he or she can select "meter fare" in the dispatch request 22. In this case, only taxi vehicles 32 can be dispatched. If "meter fare" is selected in the dispatch request 22 or if the "prior fare plan" is not selected, and the taxi vehicle 32 becomes the dispatched vehicle, the fare is calculated by the fare meter installed on the taxi vehicle 32. After arriving at the drop-off location, user 2 pays the fare calculated by the fare meter with cash or electronic money. In this case, if the drop-off location is input in addition to the dispatch request 22, the user terminal control unit 170 can display the fare determined in the fare determination process S12 as a predicted fare on the display device 124 of the user terminal 20 before the dispatch is confirmed. However, in this case, the fare calculated by the fare meter and the predicted fare may differ relatively significantly depending on the route and traffic conditions of the taxi vehicle 32.

[0067] (Vehicle dispatch request processing S13) When user 2 operates the "Request a vehicle" switch in image 218 to make a vehicle dispatch request 22, the user terminal control unit 170 performs processing corresponding to the vehicle dispatch request 22. Here, it is assumed that "taxi vehicles 32 and vehicles with requirements" is selected as the vehicle dispatch category, and information regarding cashless automatic payment is set as the payment information.

[0068] (Vehicle dispatch processing S14) The vehicle dispatch unit 172 of the vehicle dispatch management server 60 associates a vehicle with the vehicle dispatch request 22. Here, it is assumed that the NRS vehicle 42 is the vehicle to be dispatched in response to the vehicle dispatch request 22 from the user 2.

[0069] (Vehicle dispatch notification process S15) 12A is a first explanatory diagram illustrating the operation of the vehicle terminal control unit 174. As shown in FIG. 12A , the vehicle terminal control unit 174 of the vehicle dispatch management server 60 causes the display device 144 of the NRS terminal 40 disposed in the NRS vehicle 42 that is the dispatch target vehicle in response to the dispatch request 22 to display an image 220 including the message "A dispatch request has been received" as information indicating that the NRS vehicle 42 is the target of the dispatch request 22. When the NRS driver 4 operates the "Dispatch Accept" switch in the image 220 in FIG. 12A to accept the dispatch request 22, the dispatch response unit 184 transmits information indicating the acceptance of the dispatch request to the vehicle dispatch management server 60.

[0070] (Vehicle dispatch completion notification process S16) FIG. 12B is a second explanatory diagram illustrating the operation of the vehicle terminal control unit 174. Upon receiving information indicating acceptance of the dispatch request, the vehicle terminal control unit 174 confirms the NRS vehicle 42 as a dispatch target vehicle for the dispatch request 22 and causes the display device 144 of the NRS terminal 40 to display an image 222 indicating the boarding location. The image 222 shows, for example, an address of "1-chome, Shinagawa-ku, Tokyo" as the boarding location. In addition to the image 222, the display device 144 also shows a map location 224 of the current NRS terminal 40 and a map location 226 of the boarding location. Note that while the image 222 shows an example of the boarding location, the image 222 may also show a disembarking location, for example, an address of "1-chome, Minato-ku, Tokyo," in addition to the boarding location. By the vehicle terminal control unit 174 displaying the disembarking location in addition to the boarding location, the driver can, to some extent, understand the driving route to the disembarking location after picking up the user 2. In addition, the driver can suggest to user 2 that they board the vehicle on the side of the lane that is easiest to get to the drop-off location.

[0071] (User vehicle dispatch completion notification process S17) FIG. 13 is an explanatory diagram illustrating the operation of the user terminal control unit 170. When the dispatch of a vehicle to be dispatched in response to the vehicle dispatch request 22 is confirmed, the user terminal control unit 170 causes the display device 124 of the user terminal 20 to display an image 228 showing information about the vehicle dispatch. The image 228 shows, for example, the fare (predetermined fare) "¥1,600" determined in the fare determination process S12 as the fare for using the vehicle, the address "1-chome, Minato-ku, Tokyo" as the drop-off location, and the toll road information, for example, toll road "OFF" (no toll road will be used). Note that if an estimated fare, rather than a predetermined fare, was determined in the fare determination process S12 and temporarily displayed on the display device 124 of the user terminal 20, the user terminal control unit 170 re-determines the fare in the user vehicle dispatch completion notification process S17. The user terminal control unit 170 then displays the re-determined fare as the predetermined fare in the image 228. With this configuration, even if the vehicle to be dispatched does not have a toll meter, user 2 can easily understand the fare associated with the ride. The toll road information is initially set to "OFF." However, if a location that cannot be reached without using a toll road, such as Umihotaru or Kansai International Airport, is entered as the drop-off location, the user terminal control unit 170 sets the toll road information to "ON" (using a toll road), and executes the following processing based on the toll road information. Specifically, as processing based on the toll road information, the user terminal control unit 170 executes the following processing: using a toll table (described later) to determine the fare from the distance and travel time when using a toll road; and adding the fare paid by the driver for traveling on a toll road.

[0072] However, even after a ride dispatch has been confirmed, User 2 may wish to change the request details. The request details may be, for example, setting items such as a drop-off location included in the ride dispatch request. However, changing the setting items is not easy for the following reasons. As described above, in Japanese ride-sharing services, User 2 often uses a private car as a commercial vehicle, which serves as his or her means of transportation. However, vehicles such as private cars are not equipped with a fare meter that updates the fare according to the mileage. Therefore, in Japanese ride-sharing services, User 2 must input the pick-up and drop-off locations through a user application as a setting item, and the fare for using the vehicle is determined in advance. In this case, if User 2 directly instructs the driver to change the setting items verbally, the fare determined in advance will differ from the fare for the actual trip, which would cause a disadvantage to either User 2 or the NRS driver 4. Therefore, we have made it possible for User 2 to change the setting items through the user application.

[0073] (Setting item change process S18) First, an example of a process for changing a drop-off location among the setting items will be shown. A "change" switch is associated with information indicating the drop-off location in image 228 in Fig. 13 as information that allows information related to the setting item to be changed. When user 2 wishes to change the drop-off location among the setting items, he or she operates the "change" switch corresponding to the drop-off location in image 228 in Fig. 13.

[0074] 14A is a first explanatory diagram illustrating the operation of the user terminal control unit 170. When the "change" switch corresponding to the drop-off location in image 228 in FIG. 13 is operated, the user terminal control unit 170 causes the display device 124 of the user terminal 20 to display an image 230 prompting the user to input the new drop-off location, as shown in FIG. 14A. Here, assume that user 2 inputs, via the input device 126, the address "1-chome, Chuo-ku, Tokyo" as the new drop-off location in the text box of image 230.

[0075] (Fee redetermination process S19) FIG. 14B is a second explanatory diagram illustrating the operation of the user terminal control unit 170. Based on the boarding location and the changed disembarking location, the user terminal control unit 170 again derives the vehicle's travel distance and travel time if user 2 actually drives the vehicle. Furthermore, the user terminal control unit 170 determines the fare from the travel distance and travel time using a fare table. As shown in FIG. 14B, the user terminal control unit 170 displays an image 232 showing the changed ride dispatch information on the display device 124 of the user terminal 20. The image 232 shows the re-determined fare, for example, a fare (pre-determined fare) of "¥1,800," the address "1-chome, Chuo-ku, Tokyo" as the new disembarking location, and the toll road information showing the toll road "OFF" (no toll roads will be used).

[0076] FIG. 15 is an explanatory diagram illustrating the operation of the user terminal control unit 170. Assume that user 2 operates the slide switch corresponding to the toll road information in image 232 in FIG. 14B. Using a toll table, the user terminal control unit 170 re-determines the toll fare based on the travel distance and travel time if the toll road is used. The user terminal control unit 170 also adds, as the toll fare, the fee that the NRS driver 4 will pay in advance for traveling on the toll road. As shown in FIG. 15, the user terminal control unit 170 causes the display device 124 of the user terminal 20 to display an image 236 showing the revised ride-hailing information. Image 236 shows, for example, a toll (predetermined toll) of "¥2,500" as the re-determined toll, the address "1-chome, Chuo-ku, Tokyo" as the drop-off location, and the toll road "ON" (using a toll road) as the revised toll road information.

[0077] (Actual vehicle start processing S20) FIG. 16 is an explanatory diagram illustrating the operation of the vehicle terminal control unit 174. When the NRS vehicle 42 arrives at or near the boarding location, the NRS driver 4 operates, for example, an "arrived" switch via the input device 146 to transmit information indicating arrival at the location to the vehicle dispatch management server 60. Then, as shown in FIG. 16, the vehicle terminal control unit 174 displays an image 240 indicating the drop-off location in the vehicle dispatch request 22 on the display device 144 of the NRS terminal 40. The image 240 shows the drop-off location, for example, an address of "1-chome, Chuo-ku, Tokyo." In addition to the image 240, the display device 144 also shows a map location 242 of the current NRS terminal 40 and a map location 244 of the drop-off location. After getting the user 2 into the NRS vehicle 42, the NRS driver 4 transports the user 2 to the drop-off location by referring to the display device 144. As described above, if image 222 in Figure 12B shows the drop-off location in addition to the pick-up location, the driver can have some idea of ​​the driving route to the drop-off location after picking up user 2, or can wait in a lane that makes it easier for user 2 to head to the drop-off location, making it possible to transport user 2 to the drop-off location efficiently.

[0078] Note that user 2 may wish to change the setting items, such as the drop-off location, even while riding in the NRS vehicle 42. In this embodiment, user 2 can change the setting items through the user application not only after the vehicle dispatch is confirmed and before riding, but also after riding.

[0079] (Setting item change process S21) 17A is a first explanatory diagram illustrating the operation of user terminal control unit 170. When the "change" switch corresponding to the drop-off location in image 236 in FIG. 15 is operated, user terminal control unit 170 causes display device 124 of user terminal 20 to display image 250, which prompts the user to input the new drop-off location, as shown in FIG. 17A. Here, assume that user 2 inputs, via input device 126, the address "1-chome, Chiyoda-ku, Tokyo" as the new drop-off location in the text box of image 250.

[0080] (Fee redetermination process S22) FIG. 17B is a second explanatory diagram illustrating the operation of the user terminal control unit 170. Based on the boarding location and the changed drop-off location, the user terminal control unit 170 again derives the vehicle's mileage and driving time since the user 2 actually drove the vehicle. Furthermore, the user terminal control unit 170 uses a fare table to re-determine the fare based on the mileage and driving time if a toll road is used. Furthermore, the user terminal control unit 170 adds, as the fare, the fare that the NRS driver 4 will pay in advance for driving on the toll road. As shown in FIG. 17B, the user terminal control unit 170 displays an image 252 showing the changed vehicle dispatch information on the display device 124 of the user terminal 20. The image 252 shows the re-determined fare, for example, a fare (predetermined fare) of "¥2,700," the address "1-chome, Chiyoda-ku, Tokyo" as the new drop-off location, and the toll road information indicating the toll road "ON" (using a toll road).

[0081] However, the route from the boarding location to the previous drop-off location is not necessarily the same as the route from the boarding location to the new drop-off location. In this case, the NRS driver 4 may be forced to change the route he or she is traveling due to the change in drop-off location. When the route is changed in this way, the trip to the previous drop-off location may become a detour to the new drop-off location. In order to ensure the NRS driver 4's profit for the additional trip resulting from such a change in drop-off location, the user terminal control unit 170 may reflect the new location, which is the location of the NRS vehicle 42 at the time the drop-off location is changed, in the fare. For example, the user terminal control unit 170 may add the fare from the new location to the fare from the boarding location to the new location and bill the user 2.

[0082] Furthermore, when a setting item such as the drop-off location is changed, the NRS driver 4 may incur driving burdens, such as being forced to change lanes or make a U-turn, or taking time to move from a toll road to a regular road. Therefore, when a setting item is changed, in order to ensure the NRS driver 4's benefit for the driving burden, the user terminal control unit 170 may add a change fee based on the change in the setting item to the fare. However, some users 2 may be dissatisfied with the addition of such a change fee. Therefore, when charging such a change fee, the user terminal control unit 170 may not explicitly indicate this to the user application.

[0083] Conversely, when charging such a change fee, the user terminal control unit 170 may clearly indicate this in the user application. This configuration can prevent the user 2 from changing the setting items unnecessarily multiple times. Furthermore, to reduce the driving burden on the NRS driver 4, the number of times the setting items can be changed may be limited to a predetermined number, for example, up to five times.

[0084] FIG. 18 is an explanatory diagram illustrating the operation of the user terminal control unit 170. Assume that user 2 operates the slide switch corresponding to the toll road information in image 252 in FIG. 17B. Using a fare table, the user terminal control unit 170 re-determines the fare based on the travel distance and travel time. As shown in FIG. 18, the user terminal control unit 170 causes image 256 showing the revised ride-hailing information to be displayed on the display device 124 of the user terminal 20. Image 256 shows the revised fare (pre-determined fare) of "¥2,000," the address "1-chome, Chiyoda-ku, Tokyo" as the drop-off location, and the toll road "OFF" (no toll roads will be used) as the revised toll road information.

[0085] (Setting item change notification process S23) FIG. 19A is a first explanatory diagram illustrating the operation of the vehicle terminal control unit 174. When the drop-off location is changed while user 2 is aboard the vehicle, the vehicle terminal control unit 174 displays an image 260 indicating the changed drop-off location on the display device 144 of the NRS terminal 40 as information related to the changed setting item, as shown in FIG. 19A . The image 260 indicates that the drop-off location has been changed and that the new drop-off location is the address "1-chome, Chiyoda-ku, Tokyo." In addition to the image 260, the display device 144 also displays a current location 262 of the vehicle terminal on a map and a location 264 of the drop-off location on a map. When the NRS driver 4 learns through the NRS terminal 40 that the drop-off location has been changed, he or she transports user 2 to the changed drop-off location by referring to the display device 144.

[0086] (Payment process S24) 19B is a second explanatory diagram for explaining the operation of the vehicle terminal control unit 174. When the NRS vehicle 42 arrives at the drop-off location, the vehicle terminal control unit 174 displays an image 266 related to payment on the display device 144 of the NRS terminal 40. The image 266 shows the fare (predetermined fare) of "¥2,000." When the NRS driver 4 operates the "Pay" switch on the image 266, the vehicle terminal control unit 174 automatically makes payment for the NRS vehicle 42.

[0087] If the user 2 does not change the setting items, the user 2 only needs to pay the fare that is predetermined in the user vehicle dispatch completion notification process S17. Even if the user 2 changes the setting items, the user 2 only needs to pay the fare that is predetermined in the fare redetermination processes S19 and S22. Here, the fare to be paid is predetermined regardless of the route selected by the NRS driver 4, so the user 2 can ride the NRS vehicle 42 with peace of mind.

[0088] In this way, by configuring the user 2 to change the setting items through the user application, the change in the setting items is accurately transmitted to the NRS driver 4 as electronic data (characters). This allows for efficient transportation for the user 2. Furthermore, since the fare is re-determined in accordance with the change in the setting items, there is no problem of the fare being different from the pre-determined fare for the actual trip.

[0089] In the vehicle dispatch management system 1 of this embodiment, the NRS driver 4 can transport user 2 from outside the service area of ​​the NRS vehicle 42 to within the service area. On the other hand, the NRS driver 4 cannot transport user 2 from outside the service area of ​​the NRS vehicle 42 to outside the service area. In this case, if the boarding location included in the vehicle dispatch request 22 is outside the service area and the disembarking location is within the service area, the vehicle dispatch management server 60 may dispatch the NRS vehicle 42, but the user 2 may change the setting items so that the disembarking location is outside the service area of ​​the NRS vehicle 42. However, even in such a case, since the vehicle dispatch is confirmed, the NRS driver 4 can transport user 2 from outside the service area of ​​the NRS vehicle 42 to outside the service area.

[0090] However, in order to avoid transporting user 2 from outside the operating area of ​​NRS vehicle 42 to outside the operating area, the vehicle dispatch management server 60 may restrict (prohibit) changing the drop-off location to outside the operating area of ​​NRS vehicle 42.

[0091] In addition, in the present embodiment, an example has been described in which user 2 changes the setting items through the user application when NRS vehicle 42 is determined as the vehicle to be dispatched. However, the present invention is not limited to this example. Even when taxi vehicle 32 is determined as the vehicle to be dispatched, user 2 may change the setting items through the user application before or during boarding.

[0092] Furthermore, in the present embodiment, as an example of outputting various information to the user terminal 20 or the vehicle terminal, the user terminal control unit 170 displays an image including various information on the display device 124 of the user terminal 20, and the vehicle terminal control unit 174 displays an image including various information on the vehicle display device of the vehicle terminal. However, the present invention is not limited to such an example. The user terminal control unit 170 may output various information from the user terminal 20 as sound or vibration. The vehicle terminal control unit 174 may output various information from the vehicle terminal as sound or vibration.

[0093] In this way, the vehicle dispatch management system 1 comprises a user terminal 20, a vehicle terminal provided in a vehicle, and a vehicle dispatch management device (e.g., a vehicle dispatch management server 60) that can communicate with the user terminal 20 and the vehicle terminal via the network 6, the user terminal 20 comprises one or more first processors, the vehicle dispatch management device comprises one or more second processors, and the vehicle terminal comprises one or more third processors, and the first processor transmits a vehicle dispatch request to the vehicle dispatch management device, to which information relating to a predetermined setting item (e.g., drop-off location) is added, in response to an input from the user 2, and the second processor transmits the information relating to the predetermined setting item to the vehicle dispatch management device. The system determines a fare based on information regarding the request, allocates a vehicle to the vehicle allocation request 22, and causes a vehicle terminal provided in the vehicle to which the vehicle allocation request has been allocated to output information indicating that the vehicle has been the subject of a vehicle allocation request (for example, image 220 including the message "Vehicle allocation request has been received"). The third processor transmits information indicating acceptance of the vehicle allocation request to the vehicle allocation management device in response to input by the driver of the vehicle to which the vehicle allocation request has been allocated, and after receiving the information indicating acceptance of the vehicle allocation request from the vehicle terminal, the second processor outputs the determined fare (for example, the fare "¥1,600" in image 228 of FIG. 13) to the user terminal 20. With this configuration, it is possible to set an appropriate fare even if the vehicle to be allocated does not have a fare meter installed.

[0094] The vehicle dispatch management system 1 also includes a user terminal 20, a vehicle terminal provided in a vehicle, and a vehicle dispatch management device (e.g., a vehicle dispatch management server 60) capable of communicating with the user terminal 20 and the vehicle terminal via a network 6, the user terminal 20 including one or more first processors, the vehicle dispatch management device including one or more second processors, and the vehicle terminal including one or more third processors, and the first processor transmits a vehicle dispatch request to the vehicle dispatch management device in response to an input from the user 2, to which information relating to a predetermined setting item (e.g., a drop-off location) is added, and the second processor allocates a vehicle in response to the vehicle dispatch request 22 and notifies the vehicle terminal provided in the vehicle to which the vehicle dispatch request has been allocated that the vehicle has become the subject of a vehicle dispatch request. The third processor outputs information indicating acceptance of the vehicle dispatch request to the vehicle dispatch management device in response to input from the driver of the vehicle to which the vehicle dispatch request has been assigned, the second processor, after receiving the information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputs information enabling modification of information regarding a predetermined setting item (e.g., the "Change" switch in image 228) to the user terminal 20, the first processor transmits information regarding the modified predetermined setting item to the vehicle dispatch management device in response to input from the user, and the second processor outputs information regarding the modified predetermined setting item (e.g., the modified drop-off location) to the vehicle to which the vehicle dispatch request has been assigned. With this configuration, the modification of the information regarding the setting item is accurately communicated to the driver as electronic data (characters). This enables efficient transportation of User 2.

[0095] Furthermore, a vehicle dispatch management device (e.g., vehicle dispatch management server 60) capable of communicating with user terminal 20 and vehicle terminals installed in vehicles via network 6 includes one or more processors, and the processor receives a vehicle dispatch request from user terminal 20 along with information on predetermined setting items (e.g., drop-off location), determines a fare based on the information on the predetermined setting items, assigns a vehicle to the vehicle dispatch request, causes the vehicle terminal installed in the vehicle to which the vehicle dispatch request has been assigned to output information indicating that the vehicle has been the subject of a vehicle dispatch request (e.g., image 220 including the message "Vehicle dispatch request has been received"), and after receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, causes the determined fare (e.g., the fare "¥1,600" in image 228 in FIG. 13) to be output to user terminal 20. With this configuration, it is possible to set an appropriate fare even if the vehicle to be dispatched does not have a fare meter installed.

[0096] Furthermore, a vehicle dispatch management device (e.g., vehicle dispatch management server 60) capable of communicating with user terminal 20 and vehicle terminals installed in vehicles via network 6 includes one or more processors. The processor assigns a vehicle to a vehicle dispatch request to which information related to a predetermined setting item (e.g., a drop-off location) is added, received from user terminal 20, and causes the vehicle terminal installed in the vehicle to which the vehicle dispatch request is assigned to output information indicating that the vehicle has been requested for dispatch (e.g., image 220 including the message "Vehicle dispatch request received"). After receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, the processor outputs information enabling modification of the information related to the predetermined setting item (e.g., a "Change" switch in image 228) to user terminal 20. Upon receiving information related to the modified predetermined setting item from the user terminal, the processor outputs information related to the modified predetermined setting item (e.g., a modified drop-off location) to the vehicle to which the vehicle dispatch request is assigned. The specified setting item may include a drop-off location where the user wishes to get off. The specified setting item may also include toll road information indicating whether or not to use a toll road. With this configuration, changes to the information on the setting items are accurately transmitted to the driver as electronic data (characters), thereby enabling efficient transportation of the user 2.

[0097] Alternatively, the processor may determine the fare based on information relating to predetermined setting items, output the determined fare to the user terminal 20, and upon receiving information relating to a changed predetermined setting item from the user terminal 20, redetermine the fare based on the information relating to the changed predetermined setting item, and output the redetermined fare to the user terminal 20. Because the processor redetermines the fare in accordance with changes in the information relating to the setting items, there is no problem that the fare determined in advance differs from the fare associated with the actual driving.

[0098] Furthermore, in the vehicle dispatch management method, a computer receives a vehicle dispatch request from a user terminal 20 with information on predetermined setting items (e.g., drop-off location) attached, determines a fare based on the information on the predetermined setting items, assigns a vehicle to the vehicle dispatch request, causes a vehicle terminal provided in the vehicle to which the vehicle dispatch request has been assigned to output information indicating that the vehicle has been the subject of a vehicle dispatch request (e.g., image 220 including the message "Vehicle dispatch request has been received"), and, after receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputs the determined fare (e.g., the fare "¥1,600" in image 228 of FIG. 13) to the user terminal 20. With this configuration, it is possible to set an appropriate fare even if the vehicle to be dispatched does not have a fare meter installed.

[0099] In addition, the vehicle dispatch management method involves a computer assigning a vehicle to a vehicle dispatch request that includes information about a predetermined setting item (e.g., a drop-off location) received from a user terminal 20, outputting information indicating that the vehicle has been requested for dispatch (e.g., image 220 including the message "Vehicle dispatch request received") to the vehicle terminal installed in the vehicle to which the vehicle dispatch request has been assigned, outputting information enabling the information about the predetermined setting item to be changed (e.g., the "Change" switch in image 228) to the user terminal 20 after receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, and outputting information about the changed setting item (e.g., the changed drop-off location) to the vehicle to which the vehicle dispatch request has been assigned. This configuration allows changes to the setting item information to be accurately communicated to the driver as electronic data (text). This enables efficient transportation of user 2.

[0100] The program also causes the computer to receive a vehicle dispatch request with information on predetermined setting items (e.g., drop-off location) from the user terminal 20, determine a fare based on the information on the predetermined setting items, allocate a vehicle to the vehicle dispatch request, output information indicating that the vehicle has been requested for dispatch (e.g., image 220 including the message "Vehicle dispatch request received") to the vehicle terminal provided in the vehicle to which the vehicle dispatch request has been allocated, and, after receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, output the determined fare (e.g., the fare "¥1,600" in image 228 of FIG. 13) to the user terminal 20. With this configuration, it is possible to set an appropriate fare even if the vehicle to be dispatched does not have a fare meter installed.

[0101] The program also causes the computer to: allocate a vehicle to a dispatch request with information about a predetermined setting item (e.g., a drop-off location) received from the user terminal 20; output information indicating that the vehicle has been requested for dispatch (e.g., image 220 containing the message "Dispatch Requested") to the vehicle terminal installed in the vehicle to which the dispatch request has been allocated; after receiving information indicating acceptance of the dispatch request from the vehicle terminal, output information enabling modification of the information about the predetermined setting item (e.g., the "Change" switch in image 228) to the user terminal 20; and, upon receiving information about the modified setting item from the user terminal, output information about the modified setting item (e.g., the modified drop-off location) to the vehicle to which the dispatch request has been allocated. This configuration allows changes to the setting item information to be accurately communicated to the driver as electronic data (text). This enables efficient transportation of User 2.

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

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

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

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

Claims

1. A user terminal; a vehicle terminal provided in a vehicle; a vehicle dispatch management device capable of communicating with the user terminal and the vehicle terminal via a network; A vehicle dispatch management system comprising: The user terminal one or more first processors; The vehicle dispatch management device one or more second processors; The vehicle terminal one or more third processors; The first processor: transmitting a vehicle dispatch request to the vehicle dispatch management device, the vehicle dispatch request having information on predetermined setting items added thereto, in response to an input from a user; The second processor: determining a fee based on information about the predetermined setting items; Allocating a vehicle to the dispatch request; outputting information indicating that the vehicle has been the subject of the vehicle dispatch request to a vehicle terminal provided in the vehicle to which the vehicle dispatch request has been assigned; The third processor: transmitting information indicating acceptance of the vehicle dispatch request to the vehicle dispatch management device in response to an input from the driver of the vehicle to which the vehicle dispatch request has been assigned; The second processor: After receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputting the determined fare to the user terminal. Vehicle dispatch management system.

2. A user terminal; a vehicle terminal provided in a vehicle; a vehicle dispatch management device capable of communicating with the user terminal and the vehicle terminal via a network; A vehicle dispatch management system comprising: The user terminal one or more first processors; The vehicle dispatch management device one or more second processors; The vehicle terminal one or more third processors; The first processor: transmitting a vehicle dispatch request to the vehicle dispatch management device, the vehicle dispatch request having information on predetermined setting items added thereto, in response to an input from a user; The second processor: Allocating a vehicle to the dispatch request; outputting information indicating that the vehicle has been the subject of the vehicle dispatch request to a vehicle terminal provided in the vehicle to which the vehicle dispatch request has been assigned; The third processor: transmitting information indicating acceptance of the vehicle dispatch request to the vehicle dispatch management device in response to an input from the driver of the vehicle to which the vehicle dispatch request has been assigned; The second processor: After receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputting information that enables the user terminal to change information related to the predetermined setting item, The first processor: transmitting information about the changed predetermined setting item to the vehicle dispatch management device in response to the user's input; The second processor: outputting information about the changed predetermined setting item to the vehicle to which the vehicle dispatch request has been assigned; Vehicle dispatch management system.

3. A vehicle dispatch management device capable of communicating with a user terminal and a vehicle terminal provided in a vehicle via a network, one or more processors; the processor: receiving a vehicle dispatch request to which information regarding predetermined setting items is added from the user terminal; determining a fee based on information about the predetermined setting items; Allocating the vehicle to the vehicle dispatch request; outputting information indicating that the vehicle has been the subject of the vehicle dispatch request to a vehicle terminal provided in the vehicle to which the vehicle dispatch request has been assigned; After receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputting the determined fare to the user terminal. Vehicle dispatch management device.

4. A vehicle dispatch management device capable of communicating with a user terminal and a vehicle terminal provided in a vehicle via a network, one or more processors; the processor: Allocating the vehicle in response to a vehicle dispatch request to which information regarding a predetermined setting item is added, received from the user terminal; outputting information indicating that the vehicle has been the subject of the vehicle dispatch request to a vehicle terminal provided in the vehicle to which the vehicle dispatch request has been assigned; After receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputting information that enables the user terminal to change information related to the predetermined setting item, When receiving information about the changed predetermined setting item from the user terminal, the vehicle to which the vehicle dispatch request is assigned outputs information about the changed predetermined setting item. Vehicle dispatch management device.

5. The processor: determining a fee based on information about the predetermined setting item, and outputting the determined fee to the user terminal; when receiving information about the changed predetermined setting item from the user terminal, redetermine the fee based on the information about the changed predetermined setting item, and output the redetermined fee to the user terminal; The vehicle allocation management device according to claim 4.

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

7. 5. The vehicle dispatch management device according to claim 4, wherein the predetermined setting items include toll road information indicating whether or not toll roads are to be used.

8. The computer receiving a vehicle dispatch request with information regarding predetermined setting items added from a user terminal; determining a fee based on information about the predetermined setting items; Allocating a vehicle to the dispatch request; outputting information indicating that the vehicle has been the subject of the vehicle dispatch request to a vehicle terminal provided in the vehicle to which the vehicle dispatch request has been assigned; After receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputting the determined fare to the user terminal. Vehicle allocation management method.

9. The computer Allocating a vehicle in response to a vehicle dispatch request with information regarding predetermined setting items received from a user terminal; outputting information indicating that the vehicle has been the subject of the vehicle dispatch request to a vehicle terminal provided in the vehicle to which the vehicle dispatch request has been assigned; After receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputting information that enables the user terminal to change information related to the predetermined setting item, When receiving information about the changed predetermined setting item from the user terminal, the vehicle to which the vehicle dispatch request is assigned outputs information about the changed predetermined setting item. Vehicle allocation management method.

10. On the computer, receiving a vehicle dispatch request with information regarding predetermined setting items added from a user terminal; determining a fee based on information about the predetermined setting items; Allocating a vehicle to the dispatch request; outputting information indicating that the vehicle has been the subject of the vehicle dispatch request to a vehicle terminal provided in the vehicle to which the vehicle dispatch request has been assigned; After receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputting the determined fare to the user terminal. A program to make it happen.

11. On the computer, Allocating a vehicle in response to a vehicle dispatch request with information regarding predetermined setting items received from a user terminal; outputting information indicating that the vehicle has been the subject of the vehicle dispatch request to a vehicle terminal provided in the vehicle to which the vehicle dispatch request has been assigned; After receiving information indicating acceptance of the vehicle dispatch request from the vehicle terminal, outputting information that enables the user terminal to change information related to the predetermined setting item, When receiving information about the changed predetermined setting item from the user terminal, the vehicle to which the vehicle dispatch request is assigned outputs information about the changed predetermined setting item. A program to make it happen.

Images