Vehicle allocation management system, vehicle allocation management device, vehicle allocation management method, and program

Abstract

To efficiently allocate a vehicle.SOLUTION: A vehicle allocation management device communicable with a user terminal 20 via a network includes one or a plurality of processors. A business district of a vehicle includes a first business district, and a second business district different from the first business district. The processor performs: receiving a vehicle allocation request to which a getting-on place is added from the user terminal 20; allowing the user terminal 20 to output information (e.g., image 194 including a message of "a destination has to be designated in this area") related to an additional input of a getting-off place when the getting-on place is included in the second business district; and not allocating a vehicle with respect to the vehicle allocation request until the getting-off place is additionally input.SELECTED DRAWING: Figure 14

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 areas. As a result, there are areas where the supply of taxis is insufficient to meet the demand for taxi dispatch. Meanwhile, in the taxi business, operating areas are defined under the Road Transportation Act, and taxis are prohibited from operating outside of these areas. Therefore, even if a taxi is available, it cannot pick up a user depending on the relationship between the pick-up and drop-off locations, resulting in a decrease in vehicle utilization efficiency.

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

[0006] In order to solve the above problem, in the vehicle dispatch management system of the present invention, which includes a user terminal and a vehicle dispatch management device capable of communicating with the user terminal via a network, the user terminal includes one or more first processors, and the vehicle dispatch management device includes one or more second processors, the vehicle's operating area includes a first operating area and a second operating area different from the first operating area, the first processor sends a vehicle dispatch request to the vehicle dispatch management device with a boarding location added in accordance with user input, the second processor receives the vehicle dispatch request from the user terminal, and if the boarding location is included in the second operating area, outputs information regarding the additional input of a disembarking location to the user terminal, and does not allocate a vehicle to the vehicle dispatch request until the disembarking location is additionally input.

[0007] The vehicle dispatch management device of the present invention, which is capable of communicating with a user terminal via a network, has one or more processors, and the vehicle's operating area includes a first operating area and a second operating area different from the first operating area.The processor receives a vehicle dispatch request with a boarding location attached from the user terminal, and if the boarding location is included in the second operating area, outputs information regarding the additional input of a disembarking location to the user terminal, and does not assign a vehicle to the vehicle dispatch request until the disembarking location is additionally input.

[0008] The processor may allocate a vehicle belonging to the first operating area to the vehicle dispatch request if the received drop-off location is included in the first operating area, and may not allocate a vehicle belonging to the first operating area to the vehicle dispatch request if the received drop-off location is not included in the first operating area.

[0009] The vehicles belonging to the first operating area include a first vehicle and a second vehicle having different dispatchability requirements than the first vehicle, and the processor may assign the first vehicle to the dispatch request if the received drop-off location is included in the first operating area, and may not assign the second vehicle to the dispatch request even if the received drop-off location is included in the first operating area.

[0010] In order to solve the above problem, the vehicle dispatch management method of the present invention involves a computer receiving a vehicle dispatch request with a boarding location attached from a user terminal, and if the boarding location is included in a second operating area that is different from the first operating area, outputting information regarding the additional input of a disembarking location to the user terminal, and not assigning a vehicle belonging to the first operating area to the vehicle dispatch request until the disembarking location is additionally input.

[0011] In order to solve the above problem, the program of the present invention causes a computer to receive a vehicle dispatch request with a boarding location attached from a user terminal, and if the boarding location is included in a second operating area that is different from the first operating area, output information regarding the additional input of a disembarking location to the user terminal, and not assign a vehicle belonging to the first operating area to the vehicle dispatch request until the additional disembarking location is input. [Effects of the Invention]

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

[0013] [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. 10A is a first explanatory diagram for explaining business areas. Fig. 10B is a second explanatory diagram for explaining business areas. Fig. 10C is a third explanatory diagram for explaining business areas. Fig. 10D is a fourth explanatory diagram for explaining business areas. [Figure 11] FIG. 11 is an explanatory diagram for explaining the processing of the dispatch unit. [Figure 12] FIG. 12 is an explanatory diagram for explaining the operation of the user terminal control unit. [Figure 13] FIG. 13 is an explanatory diagram for explaining the processing of the dispatch unit. [Figure 14] FIG. 14 is an explanatory diagram for explaining the operation of the user terminal control unit. [Figure 15] Fig. 15A is a first explanatory diagram for explaining business districts. Fig. 15B is a second explanatory diagram for explaining business districts. Fig. 15C is a third explanatory diagram for explaining business districts. Fig. 15D is a fourth explanatory diagram for explaining business districts. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0055] (Vehicle operating area) As described above, operating areas are defined for each of the taxi vehicle 32 and the NRS vehicle 42. Here, mode transitions related to vehicle dispatch will be described using the operating area of ​​the taxi vehicle 32 as an example.

[0056] Fig. 10A is a first explanatory diagram for explaining the business area, Fig. 10B is a second explanatory diagram for explaining the business area, Fig. 10C is a third explanatory diagram for explaining the business area, and Fig. 10D is a fourth explanatory diagram for explaining the business area. A taxi vehicle 32 can operate in a business area (transportation zone) 7 in which the taxi business office to which it belongs is located. Therefore, as shown in Fig. 10A, the taxi vehicle 32 can transport a user 2 from a boarding point within the business area 7 indicated by a dashed line to a disembarking point within the same business area 7.

[0057] In the dispatch request 22 for the taxi vehicle 32, the drop-off location is not required input information, so there are cases where the user 2 does not input the drop-off location. In this case, the user 2 verbally communicates the drop-off location directly to the taxi driver 3 after getting into the taxi vehicle 32. In this case, even if the pick-up location is within the operating area 7, the drop-off location is not necessarily within the operating area 7. However, if the taxi driver 3 is unable to transport the user 2 because the drop-off location is outside the operating area 7 (another operating area), the taxi driver 3 must refuse to pick up the user 2, which results in a decrease in the convenience for the user 2 and the dispatch efficiency. Therefore, the taxi vehicle 32 can transport the user 2 from the pick-up location within the operating area 7 to the drop-off location outside the operating area 7, as shown in FIG. 10B.

[0058] As shown in FIG. 10B, after transporting user 2 outside the business area 7, taxi vehicle 32 returns to its own business area 7 to continue business. If taxi vehicle 32 is restricted from transporting new users 2 while returning to its own business area 7, it will lose business opportunities and experience a decline in vehicle utilization efficiency. Therefore, even if taxi vehicle 32 is located outside the business area 7, as shown in FIG. 10C, it can transport user 2 from a boarding location outside the business area 7 to a drop-off location within its own business area 7, as long as the drop-off location is within its own business area 7.

[0059] However, when the taxi vehicle 32 is located outside the operating area 7, the business of transporting the user 2 to a drop-off point outside the operating area 7 is not business within the operating area 7 (out-of-area business). Therefore, the taxi vehicle 32 cannot transport the user 2 from a boarding point outside the operating area 7 to a drop-off point outside the operating area 7, as shown in FIG. 10D.

[0060] 10A and 10B, in the vehicle dispatch management system 1, when the taxi vehicle 32 is located within the business area 7, the taxi vehicle 32 can transport the user 2 to the drop-off location regardless of whether the drop-off location is within or outside the business area 7 of the taxi vehicle 32's own. On the other hand, in the vehicle dispatch management system 1, when the taxi vehicle 32 is located outside the business area 7, as shown in FIGS. 10C and 10D, whether the taxi vehicle 32 can transport the user 2 to the drop-off location depends on whether the drop-off location is within or outside the business area 7 of the taxi vehicle 32's own.

[0061] In this case, when the taxi vehicle 32 is located outside the service area 7, the taxi driver 3 can ask the user 2 requesting a ride about their drop-off location, and if the drop-off location is within the taxi driver's service area 7, the taxi driver 3 can transport the user 2. However, if the drop-off location is not within the taxi driver's service area 7, the taxi driver 3 cannot transport the user 2 and must refuse the user 2's ride, resulting in a decrease in user 2's convenience. Furthermore, such a response requires the taxi driver 3 to spend time processing the ride for the user 2, resulting in a decrease in the taxi driver's utilization efficiency. If the taxi driver 3 were to completely prohibit the taxi vehicle 32 from transporting the user 2 when the taxi vehicle 32 is returning to the service area 7 in order to avoid having to deal with the user 2 whose ride must be refused, the user 2 would lose the opportunity to ride the taxi vehicle 32 returning to the service area 7, which would also result in a decrease in the taxi driver's utilization efficiency.

[0062] FIG. 11 is an explanatory diagram for explaining the processing of the dispatch unit 172. FIG. 11 shows taxi vehicles 32a, 32b, and 32c belonging to a service area 7A (first service area), and a user 2 making a dispatch request 22 in a service area 7B (second service area) different from the service area 7A. In the example of FIG. 11, it is assumed that taxi vehicle 32a is operating in the service area 7A, and taxi vehicles 32b and 32c are returning to the service area 7A from a service area 7B different from the service area 7A. For ease of explanation, it is also assumed that the dispatch category is set to "taxi vehicle 32 only" (first dispatch mode) in the dispatch request.

[0063] In response to the dispatch request 22, the dispatch unit 172 sets an extraction condition 24, shown by a dashed arc in FIG. 11, that the distance between the boarding location (the current location of user 2) and the current location of taxi 32 is equal to or less than a predetermined distance. In the example of FIG. 11, taxi 32a is far from user 2 and does not satisfy extraction condition 24. On the other hand, taxis 32b and 32c are close to user 2 and satisfy extraction condition 24.

[0064] In this case, the taxi vehicle 32a does not satisfy the extraction condition 24, and therefore the dispatch unit 172 cannot select the taxi vehicle 32a as a vehicle to be dispatched. Furthermore, if the user 2 does not include a drop-off location in the dispatch request 22, the dispatch unit 172 cannot determine whether the drop-off location desired by the user 2 is within the business area 7A. Therefore, the dispatch unit 172 cannot select the taxi vehicles 32b and 32c as vehicles to be dispatched even if the extraction condition 24 is satisfied. In this case, it becomes difficult for the user 2 to board the taxi vehicle 32 early.

[0065] Therefore, in a situation where there is a shortage of taxi vehicles 32 in the operating area 7B, the vehicle dispatch management server 60 prompts the user 2 to make additional input so that taxi vehicles 32b and 32c belonging to the operating area 7A can be dispatched depending on the drop-off location. Hereinafter, a vehicle dispatch mode that does not assign a taxi vehicle 32 belonging to the operating area 7A to a vehicle dispatch request 22 whose boarding location is in the operating area 7B different from the operating area 7A is referred to as a vehicle dispatch restriction mode. Also, a vehicle dispatch mode that assigns a taxi vehicle 32 belonging to the operating area 7A to a vehicle dispatch request 22 whose boarding location is in the operating area 7B is referred to as a vehicle dispatch possible mode.

[0066] As explained using FIG. 10C, in the vehicle dispatch management system 1, even if a taxi vehicle 32 belonging to the operating area 7 is located outside the operating area 7, the vehicle dispatch management system 1 can transport the user 2 to a location within the operating area 7 as long as the drop-off location is within the operating area 7. Therefore, the vehicle dispatch management server 60 prompts the user 2 to additionally input a drop-off location through the user terminal 20. Then, if the additionally input drop-off location is included in the operating area 7, the vehicle dispatch management server 60 shifts the dispatch mode from the vehicle dispatch restriction mode to the vehicle dispatchable mode for the taxi vehicles 32 belonging to the operating area 7 but located outside the operating area 7. In this way, the user 2 can target taxi vehicles 32b and 32c that are close to the user 2 for dispatch.

[0067] Even if the user 2 additionally inputs a drop-off location through the user terminal 20, the vehicle dispatch management server 60 will not transition the vehicle dispatch mode from the vehicle dispatch restriction mode to the vehicle dispatch possible mode unless the additionally input drop-off location is within the service area 7A. In this way, it is possible to prevent out-of-service operations as described with reference to FIG. 10D.

[0068] Specifically, the user terminal control unit 170 outputs information regarding the transition from the dispatch restriction mode to the dispatch available mode to the user terminal 20 based on the operating status of the taxi vehicles 32 belonging to the operating area 7B in the operating area 7B. In this embodiment, the operation of outputting information regarding the transition from the dispatch restriction mode to the dispatch available mode to the user terminal 20 is simply referred to as "transition output."

[0069] It is possible that the user terminal control unit 170 outputs the transition information to all user terminals 20 for which dispatching has not been completed. However, it is not necessary to output information regarding the transition to user terminals 20 for which dispatching in the dispatchable mode is already possible (for which a drop-off location has been input). Therefore, the user terminal control unit 170 may output the transition information only to user terminals 20 for which a drop-off location has not been input, based on the operating status of the operation of the taxi vehicle 32.

[0070] Here, the operating status may be the occupied vehicle rate of taxi vehicles 32 belonging to operating area 7B in operating area 7B. The occupied vehicle rate of taxi vehicles 32 indicates the proportion of the distance traveled by taxi vehicles 32 in an occupied state to the total distance traveled by taxi vehicles 32. Here, an occupied vehicle refers to a state in which user 2 is in the vehicle. For example, when the occupied vehicle rate of taxi vehicles 32 in the most recent hour is equal to or greater than a predetermined rate, the user terminal control unit 170 determines that there is an insufficient supply of taxi vehicles 32 belonging to operating area 7B and that the dispatch efficiency of taxi vehicles 32 can be improved by including taxi vehicles 32 belonging to operating area 7A in the dispatch targets, and performs a transition output.

[0071] Note that, instead of the occupied vehicle rate of taxi vehicles 32 belonging to operating area 7B in operating area 7B, the vacant vehicle rate of taxi vehicles 32 belonging to operating area 7B in operating area 7B can also be applied as the operating status. The vacant vehicle rate of taxi vehicles 32 indicates the proportion of the distance traveled by the taxi vehicle 32 in an empty state to the total distance traveled by the taxi vehicle 32. An empty vehicle refers to a state in which no user 2 is in the vehicle. For example, when the vacant vehicle rate of taxi vehicles 32 in the most recent hour falls below a predetermined rate, the user terminal control unit 170 determines that there is an insufficient supply of taxi vehicles 32 belonging to operating area 7B and that the dispatch efficiency of taxi vehicles 32 can be improved by including taxi vehicles 32 belonging to operating area 7A in the dispatch targets, and performs a transition output.

[0072] Furthermore, the operating status may be the actual vehicle time rate of the taxi vehicles 32 belonging to the operating area 7B in the operating area 7B. The actual vehicle time rate of the taxi vehicles 32 indicates the proportion of time during the business hours of the taxi vehicles 32 that the taxi vehicles 32 are in an actual vehicle state. For example, when the actual vehicle time rate of the taxi vehicles 32 in the most recent hour is equal to or greater than a predetermined rate, the user terminal control unit 170 determines that there is an insufficient supply of taxi vehicles 32 belonging to the operating area 7B, and that the dispatch efficiency of the taxi vehicles 32 can be improved by including taxi vehicles 32 belonging to the operating area 7A in the dispatch targets, and performs a transition output.

[0073] Note that, instead of the above-described actual vehicle time rate of the taxi vehicles 32 belonging to the operating area 7B in the operating area 7B, the empty time rate of the taxi vehicles 32 belonging to the operating area 7B in the operating area 7B can also be applied as the operating status. The empty time rate of the taxi vehicles 32 indicates the proportion of time that the taxi vehicles 32 are empty during the business hours of the taxi vehicles 32. For example, when the empty time rate of the taxi vehicles 32 in the most recent hour is equal to or less than a predetermined rate, the user terminal control unit 170 determines that there is an insufficient supply of taxi vehicles 32 belonging to the operating area 7B, and that the dispatch efficiency of the taxi vehicles 32 can be improved by including the taxi vehicles 32 belonging to the operating area 7A in the dispatch targets, and performs a transition output.

[0074] Furthermore, the number of times per unit time that a taxi vehicle 32 belonging to the operating area 7B is actually driven in the operating area 7B may be applied as the operating status. The number of times per unit time that a taxi vehicle 32 is actually driven in response to a dispatch request 22 indicates the number of times per unit time that a taxi vehicle 32 is actually driven in response to a dispatch request 22. When the number of times that a taxi vehicle 32 is actually driven is equal to or exceeds a predetermined number, the user terminal control unit 170 determines that there is an insufficient supply of taxi vehicles 32 belonging to the operating area 7B and that the dispatch efficiency of taxi vehicles 32 can be improved by including taxi vehicles 32 belonging to the operating area 7A in the targets for dispatch, and performs a transition output.

[0075] Furthermore, the operating status may be the actual driving distance per unit time of the taxi vehicles 32 belonging to the operating area 7B in the operating area 7B. The actual driving distance of the taxi vehicles 32 indicates the distance per unit time that the taxi vehicles 32 are actually driving. When the actual driving distance is equal to or greater than a predetermined distance, the user terminal control unit 170 determines that there is an insufficient supply of taxi vehicles 32 belonging to the operating area 7B, and that the dispatch efficiency of the taxi vehicles 32 can be improved by including the taxi vehicles 32 belonging to the operating area 7A in the targets for dispatch, and performs a transition output.

[0076] Furthermore, the operation status may be the dispatch waiting time in the operating area 7B of the taxi vehicles 32 belonging to the operating area 7B. The dispatch waiting time of the taxi vehicles 32 indicates the time from when the dispatch request 22 is received from the user terminal 20 until the dispatch is confirmed. For example, when the average dispatch waiting time of the taxi vehicles 32 in the last hour is equal to or greater than a predetermined time, the user terminal control unit 170 determines that the dispatch efficiency of the taxi vehicles 32 can be improved by including the taxi vehicles 32 belonging to the operating area 7A in the targets for dispatch, and performs a transition output.

[0077] In the present embodiment, an example has been described in which the user terminal control unit 170 individually determines the operating status based on the occupied vehicle rate, empty vehicle rate, occupied vehicle time rate, empty vehicle time rate, number of occupied vehicles, occupied vehicle distance, matching rate, and vehicle dispatch wait time. However, the present embodiment is not limited to this example, and the user terminal control unit 170 may determine a combination of multiple operating statuses selected from the occupied vehicle rate, empty vehicle rate, occupied vehicle time rate, empty vehicle time rate, number of occupied vehicles, occupied vehicle distance, matching rate, and vehicle dispatch wait time. Furthermore, in the present embodiment, the occupied vehicle rate, empty vehicle rate, occupied vehicle time rate, empty vehicle time rate, number of occupied vehicles, occupied vehicle distance, matching rate, and vehicle dispatch wait time have been described as operating statuses, but the present embodiment is not limited to this example, and various indices that can determine the level of the operating status of taxi vehicles 32 in the operating area 7B can be applied.

[0078] Next, the transition output will be described. As a transition output relating to the transition from the vehicle allocation restriction mode to the vehicle allocation available mode, the user terminal control unit 170 causes the display device 124 of the user terminal 20 to display an image requesting additional input of a drop-off location, for example.

[0079] 12 is an explanatory diagram illustrating the operation of the user terminal control unit 170. As shown in Fig. 12, the user terminal control unit 170 causes the display device 124 of the user terminal 20 to display an image 190 including a message prompting the user to additionally input a drop-off location: "Specifying a destination in this area increases the likelihood of vehicle dispatch." In this way, the user terminal control unit 170 can prompt the user 2 to additionally input a drop-off location.

[0080] By visually recognizing this message, user 2 can easily input an additional drop-off location via the input device 126 in a situation where the dispatch of taxi vehicle 32 is not confirmed for a long time. In this way, the dispatch unit 172 can dispatch a taxi vehicle 32 belonging to the operating area 7A in the dispatchable mode. This allows user 2 to quickly board any vehicle, including taxi vehicles 32b and 32c belonging to the operating area 7A, depending on the drop-off location, for example, in the example of FIG. 11. Note that after causing the user terminal 20 to output information regarding the additional input of a drop-off location, the user terminal control unit 170 can also prevent the message from being deleted until user 2 inputs an additional drop-off location.

[0081] Furthermore, if cashless automatic payment is already set as payment information in the user application, when user 2 additionally inputs a drop-off location via input device 126, the dispatch requirement for the vehicle with the condition is met. In this way, the dispatch unit 172 can also dispatch the vehicle with the condition in the second dispatch mode. In this way, if an NRS vehicle 42b is located nearby, user 2 can board the vehicle early.

[0082] In the present embodiment, the user terminal control unit 170 has been described as displaying, as a transition output, an image including a message requesting additional input of predetermined setting items through the user terminal 20. However, the present invention is not limited to this example. The user terminal control unit 170 can, for example, display on the display device 124 of the user terminal 20 various images for making taxi vehicles 32 belonging to the operating area 7A eligible for dispatch, such as a message directly requesting that taxi vehicles 32 belonging to the operating area 7A be included in the targets for dispatch, such as "Vehicles from other operating areas are available for dispatch."

[0083] With this configuration, even in a situation where there is an insufficient supply of taxi vehicles 32 belonging to the operating area 7B and a taxi vehicle 32 cannot be dispatched immediately, it may be possible to dispatch a taxi vehicle 32 that does not belong to the operating area 7B but belongs to the operating area 7A, increasing the likelihood that the user 2 will board a taxi vehicle 32 early. In this way, by expanding the targets for dispatch from taxi vehicles 32 belonging to the operating area 7B to taxi vehicles 32 belonging to the operating area 7B and taxi vehicles 32 belonging to the operating area 7A, the dispatch management system 1 enables efficient dispatch. Furthermore, a taxi vehicle 32 belonging to the operating area 7A is targeted for dispatch if the drop-off location is input and the drop-off location is in the operating area 7A, so that the utilization rate of the taxi vehicle 32 itself can be improved.

[0084] However, the user terminal control unit 170 will require the user 2 to input an additional drop-off location in the transition output. Therefore, some users 2 may find such additional input bothersome. Therefore, the user terminal control unit 170 strictly limits the transition output to areas where the supply of taxi vehicles 32 is insufficient. For example, the user terminal control unit 170 may limit the business area 7 of taxi vehicles 32 to an area of ​​1 km 2 For each of the mesh-shaped divided sections, the vehicle operation status is checked, for example, every 30 minutes, and transition output is sent to users 2 included in the divided section where the vehicle operation status satisfies a predetermined condition. In this way, by limiting the geographical range to which the transition output is applied, additional input is not required from an unnecessarily large number of users 2, and the number of users 2 who find the additional input bothersome can be reduced.

[0085] In the present embodiment, an example has been described in which the user terminal control unit 170 performs transition output through the user terminal 20 based on the operating status of the vehicle. However, the present invention is not limited to this example, and the user terminal control unit 170 may forcibly perform transition output regardless of the operating status of the vehicle.

[0086] FIG. 13 is an explanatory diagram for explaining the processing of the dispatch unit 172, and FIG. 14 is an explanatory diagram for explaining the operation of the user terminal control unit 170. In FIG. 13, for example, the Osaka city transportation area (first service area) is shown as the service area 7A of the taxi vehicle 32, and for example, the Senshu transportation area (second service area) is shown as the service area 7B of the taxi vehicle 32. FIG. 13 also shows the taxi vehicle 32 belonging to the service area 7A, a major facility 10 such as Kansai International Airport included in the service area 7B, and a user 2 who makes a dispatch request 22 at the major facility 10. For example, if the major facility 10 such as Kansai International Airport is located near the boundary 192 between the service area 7A and the service area 7B, in a business in which the major facility 10 is the boarding point, a different service area 7A is often the disembarking point. In this case, a taxi vehicle 32 belonging to a service area 7A different from the service area 7B including the main facility 10 cannot pick up user 2 at the main facility 10 unless user 2 enters a location within the service area 7A as the drop-off location. After transporting user 2 from its own service area 7A to a main facility 10 in another service area 7B, the taxi vehicle 32 returns to its own service area 7A to continue its business. Since the taxi vehicle 32 drops off user 2 at the drop-off location, user 2 is not on board while returning to its own service area 7A. If the taxi vehicle 32 is unable to transport a new user 2 while returning to its own service area 7A, the taxi vehicle 32 loses a business opportunity and reduces its operational efficiency. Therefore, if there are certain circumstances, such as the main facility 10 being located near the boundary 192 of the service area 7, the user terminal control unit 170 may always output a transition command via the user terminal 20, regardless of the operating status of the taxi vehicle 32 in the service area 7B including the main facility 10.

[0087] For example, if user 2 includes a major facility 10 near the boundary 192 of the operating area 7 as a boarding location in the vehicle dispatch request 22, the user terminal control unit 170, based on the fact that the boarding location is the major facility 10 or that the boarding location is within the operating area 7B that includes the major facility 10, outputs information regarding the additional input of a drop-off location to the user terminal 20, for example, an image 194 including the message "Destination specification is required in this area," as shown in FIG. 14, to prompt the user to additionally input a drop-off location, and then transitions to a standby state for additional input of a drop-off location. At this time, the user terminal control unit 170 can also strongly prompt the user 2 to additionally input a drop-off location by preventing the message from being deleted until the user 2 additionally inputs a drop-off location. Furthermore, the user terminal control unit 170 does not assign a vehicle to the vehicle dispatch request 22 until the additional drop-off location is input. In this way, by requiring the additional input of the drop-off location, it is possible to increase the opportunities for dispatching taxi vehicles 32 belonging to different operating areas 7 for dispatch requests 22 in which the boarding location is a major facility 10 or its vicinity, thereby enabling efficient dispatch of taxi vehicles 32.

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

[0089] In addition, in this embodiment, an example has been described in which the dispatch category in the dispatch request 22 is set to "taxi vehicles 32 only" (first dispatch mode). However, the example is not limited to this, and the dispatch category may be set to "taxi vehicles 32 and vehicles with requirements" (second dispatch mode) or "vehicles with requirements only" (third dispatch mode). However, as will be described later, taxi vehicles 32 can operate across the business area 7 of taxi vehicles 32, but NRS vehicles 42 cannot operate across the business area 7 of taxi vehicles 32. Below, mode transitions related to dispatch will be described using the business area of ​​NRS vehicles 42 as an example.

[0090] FIG. 15A is a first explanatory diagram for explaining the business area, FIG. 15B is a second explanatory diagram for explaining the business area, FIG. 15C is a third explanatory diagram for explaining the business area, and FIG. 15D is a fourth explanatory diagram for explaining the business area.

[0091] The NRS vehicle 42 can operate in the service area 8 where the taxi business office to which it belongs is located. Therefore, like the taxi vehicle 32 described using Fig. 10A, the NRS vehicle 42 can transport the user 2 from a boarding point within the service area 8 indicated by the dashed line to a disembarking point within the same service area 8, as shown in Fig. 15A.

[0092] However, even if user 2's boarding location is within the operating area 8, it does not necessarily mean that the disembarking location will also be within the operating area 8. However, as shown in FIG. 15A, if operation is only possible when the boarding location and disembarking location are within the operating area 8, then even if the boarding location is within the operating area 8, user 2 cannot be transported because the disembarking location is outside the operating area 8 (another operating area). To prevent such a decrease in user 2's convenience and dispatch efficiency, NRS vehicle 42 can transport user 2 from a boarding location within the operating area 8 to a disembarking location outside the operating area 8, as shown in FIG. 15B.

[0093] As shown in FIG. 15B , after transporting user 2 outside the service area 8, the NRS vehicle 42 returns to its own service area 8 to continue business. Because the NRS vehicle 42 drops off user 2 at the drop-off location, user 2 is not on board while the NRS vehicle 42 is returning to its own service area 8. If the NRS vehicle 42 is unable to transport a new user 2 while returning to its own service area 8, the NRS vehicle 42 loses a business opportunity, resulting in a decrease in vehicle efficiency. To prevent this, as shown in FIG. 15C , even if the NRS vehicle 42 is located outside the service area 8, if the drop-off location is within its own service area 8, the NRS vehicle 42 is considered to be operating in the service area 8, and can transport user 2 from a boarding location outside the service area 8 to a drop-off location within the service area 8.

[0094] In addition, when the NRS vehicle 42 returns from outside the service area 8, it can adopt an extended service area 9 shown by the dashed line in Figure 15C, which expands the area of ​​the service area 8 outward by, for example, 5 km. As described above, the service area 8 of the NRS vehicle 42 is often smaller than the service area 7 of the taxi vehicle 32. Therefore, here, the drop-off location, which is a dispatchable condition, is not limited to the service area 8, but is expanded to an extended service area 9 near the service area 8, thereby improving the dispatch efficiency of the NRS vehicle 42. For example, if the drop-off location is within the extended service area 9 even if it is not within the NRS vehicle's own service area 8, the NRS vehicle 42 can transport the user 2 from the boarding location outside the service area 8 to the drop-off location within the extended service area 9.

[0095] However, when NRS vehicle 42 is located outside the operating area 8, business transporting user 2 from outside the operating area 8 to a drop-off location outside the expanded operating area 9 is not business within the operating area 8 (out-of-area business). Therefore, NRS vehicle 42 cannot transport user 2 from a boarding location outside the operating area 8 to a drop-off location outside the operating area 8 or in the expanded operating area 9, as shown in FIG. 15D.

[0096] 15D, if the boarding location is outside the business area 8, even if it is within the extended business area 9, i.e., if the boarding location is between the outer edge of the business area 8 and the outer edge of the extended business area 9, the NRS vehicle 42 cannot transport user 2 to a drop-off location outside the extended business area 9. However, this example is not limited to this, and for example, even if the boarding location is outside the business area 8, if it is within the extended business area 9, the NRS vehicle 42 may be able to transport user 2 from a boarding location within the extended business area 9 to a drop-off location outside the extended business area 9.

[0097] In the vehicle dispatch management system 1, as shown in Figures 15A, 15B, and 15C, if the boarding location is within its own business area 8 or the disembarking location is within its own expanded business area 9, the NRS vehicle 42 can transport user 2 from the boarding location to the disembarking location. On the other hand, in the vehicle dispatch management system 1, as shown in Figure 15D, if the boarding location is outside its own business area 8 and the disembarking location is outside its own expanded business area 9, the NRS vehicle 42 cannot transport user 2 from the boarding location to the disembarking location.

[0098] Here, if the range in which the NRS vehicle 42 is a candidate for dispatch is expanded beyond the service area 8 indefinitely, the following problem occurs. Ride sharing is originally intended to transport user 2 over short distances. Therefore, the service area 8 of the NRS vehicle 42 is included in the service area 7 (traffic zone) of the taxi vehicle 32, and is often narrower than the service area 7 of the taxi vehicle 32. If the range in which such an NRS vehicle 42 is a candidate for dispatch is expanded indefinitely, for example, the NRS vehicle 42 will be a candidate for dispatch even when it is located outside the service area 7 of the taxi vehicle 32, and will end up transporting user 2 across the service area 7 of the taxi vehicle 32. In this case, the NRS driver 4 may be forced to unintentionally transport user 2 over long distances.

[0099] Therefore, in the vehicle dispatch management system 1, as shown in Figures 15A, 15B, and 15C, if the boarding location is within its own business area 8 or the disembarking location is included in its own expanded business area 9, the NRS vehicle 42 can transport the user 2 from the boarding location to the disembarking location, but the business range is limited to the business area 7 of the taxi vehicle 32. Therefore, as shown in Figures 10 and 11, the taxi vehicle 32 can operate across the business area 7 of the taxi vehicle 32, but the NRS vehicle 42 cannot operate across the business area 7 of the taxi vehicle 32. Therefore, when the NRS vehicle 42 is located outside its business area 8, it can be a candidate for dispatch if its location is within the business area 7 of the taxi vehicle 32, but it is not a candidate for dispatch if its location is outside the business area 7 of the taxi vehicle 32.

[0100] Therefore, as described above, for a business that crosses business areas 7, transporting user 2 from business area 7B (e.g., Senshu transportation area: second business area) to business area 7A (e.g., Osaka city area transportation area: first business area), if the dispatch request 22 includes a drop-off location and the drop-off location is included in business area 7A (e.g., Osaka city area transportation area), taxi vehicles 32 that belong to business area 7A will be candidates for dispatch in response to the dispatch request 22, but NRS vehicles 42 cannot be candidates for dispatch even if they belong to business area 7A.

[0101] The vehicle dispatch management server 60 prompts the user 2 for additional input depending on the vehicle dispatch status so that an NRS vehicle 42 belonging to the operating area 8 can be dispatched depending on the drop-off location. Hereinafter, a vehicle dispatch mode that does not assign an NRS vehicle 42 belonging to the operating area 8 to a vehicle dispatch request 22 in which the boarding location is in an operating area (second operating area) different from the operating area (first operating area) 8 is referred to as a vehicle dispatch restriction mode. Also, a vehicle dispatch mode that assigns an NRS vehicle 42 belonging to the operating area 8 to a vehicle dispatch request 22 in which the boarding location is in an operating area different from the operating area 8 is referred to as a vehicle dispatch available mode. The vehicle dispatch management server 60 may output information regarding a transition from the vehicle dispatch restriction mode to the user terminal 20 based on the operating status of vehicles in operating areas different from the operating area 8.

[0102] In a situation where a vehicle is not dispatched for a long time, user 2 may obtain information regarding the transition from the dispatch restriction mode to the dispatch available mode and input an additional drop-off location via input device 126. In this case, if cashless automatic payment has already been set as payment information in the user application, the dispatch unit 172 can dispatch an NRS vehicle 42 belonging to the business area 8 in the dispatch available mode if user 2 inputs the drop-off location and the drop-off location is included in the business area 8. This allows user 2 to board an NRS vehicle 42 belonging to the business area 8 early.

[0103] As described above, the operation of the NRS vehicle 42 may be limited not only by the geographical area of ​​the business area 8 but also by time. Therefore, the NRS vehicle 42 may be able to operate only during specific restricted time periods in a specified business area 8. In this case, the vehicle dispatch management server 60 sets the NRS vehicle 42 as a candidate for dispatch only during specific time periods in the specified business area 8. In this way, during the time periods when the NRS vehicle 42 can be dispatched, user 2 may be able to optionally input information regarding the boarding location, disembarking location, and automatic payment, or user 2 may input information regarding the boarding location, disembarking location, and automatic payment in accordance with the transition output described above, or user 2 may be required (mandatory input) to input information regarding the boarding location, disembarking location, and automatic payment only during specific time periods.

[0104] Furthermore, as described above, the service area 8 of the NRS vehicle 42 is included in the service area 7 of the taxi vehicle 32 and is often smaller than the service area 7 of the taxi vehicle 32. Therefore, the service area 7 of the taxi vehicle 32 may include multiple service areas 8 of the NRS vehicle 42. Furthermore, the multiple service areas 8 of the NRS vehicle 42 may each have independent operating time periods. For example, within the same service area 7 of the taxi vehicle 32, the first operating time period in the first service area 8 of the NRS vehicle 42 may be different from the second operating time period in the second service area 8 of the NRS vehicle 42. Furthermore, when there are multiple service areas 7, the first operating time period in the first service area 8 of the NRS vehicle 42 within the first service area 7 of the taxi vehicle 32 may be different from the second operating time period in the second service area 8 of the NRS vehicle 42 within the second service area 7 of the taxi vehicle 32.

[0105] Here, an example is given in which the operating hours differ for each service area 8 of the NRS vehicle 42, but this is not the only example. Alternatively, it can be interpreted that the operating hours differ for each service area 8 of the NRS vehicle 42. For example, within the same service area 7 of the taxi vehicle 32, the first service area 8 of the NRS vehicle 42 that is open during a first time period may be different from the second service area 8 of the NRS vehicle 42 that is open during a second time period. Furthermore, when there are multiple service areas 7, the first service area 8 of the NRS vehicle 42 that is open during a first time period within the first service area 7 of the taxi vehicle 32 may be different from the second service area 8 of the NRS vehicle 42 that is open during a second time period within the second service area 7 of the taxi vehicle 32.

[0106] Furthermore, in a predetermined operating area 8 of the NRS vehicle 42, a first time period during which the dispatch candidates are taxi vehicles 32 and NRS vehicles 42, and a second time period during which only the NRS vehicle 42 is available for dispatch may be set. However, in order to dispatch an NRS vehicle 42, the user 2 must attach information regarding the boarding location, the disembarking location, and automatic payment to the dispatch request 22. Therefore, in the dispatch request 22 for the second time period during which only the NRS vehicle 42 is available for dispatch, the user 2 must input information regarding the boarding location, the disembarking location, and automatic payment.

[0107] It goes without saying that the above-described embodiment relating to the taxi vehicle 32 can also be applied to the NRS vehicle 42.

[0108] In this way, the vehicle dispatch management system 1 comprises a user terminal 20 and a vehicle dispatch management device (e.g., vehicle dispatch management server 60) that can communicate with the user terminal 20 via a network, the user terminal 20 comprises one or more first processors, the vehicle dispatch management device comprises one or more second processors, the vehicle's operating area includes a first operating area (e.g., operating area 7A) and a second operating area (e.g., operating area 7B) different from the first operating area, the first processor sends a vehicle dispatch request with a boarding location added according to user input to the vehicle dispatch management device, the second processor receives the vehicle dispatch request 22 from the user terminal 20, and if the boarding location is included in the second operating area, outputs information regarding the additional input of a disembarkation location (e.g., image 194 including the message "Destination specification is required in this area") to the user terminal 20, and does not allocate a vehicle to the vehicle dispatch request 22 until the disembarkation location is additionally input. In this way, by requiring the additional input of the drop-off location, it is possible to increase the opportunities for dispatching taxi vehicles 32 belonging to different operating areas 7 for dispatch requests 22 in which the boarding location is a major facility 10 or its vicinity, thereby enabling efficient dispatch of taxi vehicles 32.

[0109] Furthermore, a vehicle dispatch management device (e.g., vehicle dispatch management server 60) that can communicate with user terminal 20 via a network includes one or more processors, and vehicle service areas include a first service area (e.g., service area 7A) and a second service area (e.g., service area 7B) that is different from the first service area. When the processor receives a vehicle dispatch request 22 with a boarding location added from user terminal 20 and the boarding location is included in the second service area, it outputs information regarding the additional input of a drop-off location (e.g., image 194 including the message "Destination specification is required in this area") to user terminal 20, and does not allocate a vehicle to vehicle dispatch request 22 until the drop-off location is additionally input. In this way, by requiring the additional input of a drop-off location, it is possible to increase the chances of dispatching a taxi vehicle 32 belonging to a different service area 7 for a vehicle dispatch request 22 with a boarding location at or near a major facility 10, thereby enabling efficient dispatch of taxi vehicles 32.

[0110] Furthermore, if the received drop-off location is included in the first service area (for example, service area 7A), the processor may allocate a vehicle belonging to the first service area to the dispatch request 22, and if the received drop-off location is not included in the first service area, the processor may not allocate a vehicle belonging to the first service area to the dispatch request 22. With this configuration, it is possible to prevent the taxi vehicle 32 from operating outside the area, while increasing the opportunities to transport users 2 across service areas 7, and to efficiently dispatch the taxi vehicle 32.

[0111] Vehicles belonging to the first service area include a first vehicle (e.g., taxi vehicle 32) and a second vehicle (e.g., NRS vehicle 42) having different dispatchability requirements from the first vehicle. The processor may assign the first vehicle to the dispatch request 22 if the received drop-off location is included in the first service area (e.g., service area 7A), and may not assign the second vehicle to the dispatch request 22 even if the received drop-off location is included in the first service area. Here, for transportation of user 2 across service areas 7, if the dispatch request 22 includes a drop-off location and the drop-off location is included in the first service area, taxi vehicles 32 belonging to the first service area are candidates for dispatch in response to the dispatch request 22, but NRS vehicles 42 are not candidates for dispatch even if they belong to the first service area. This configuration enables efficient dispatch of taxi vehicles 32 while restricting the operation of NRS vehicles 42 across service areas 7.

[0112] Furthermore, in the vehicle dispatch management method, the computer receives a vehicle dispatch request 22 with an additional boarding location from the user terminal 20, and if the boarding location is included in a second service area (e.g., service area 7B) different from the first service area (e.g., service area 7A), it outputs information regarding the additional input of a drop-off location (e.g., image 194 including the message "Destination specification is required in this area") to the user terminal 20, and does not assign a vehicle belonging to the first service area to the vehicle dispatch request 22 until the drop-off location is additionally input. In this way, by requiring the additional input of a drop-off location, it is possible to increase the chances of dispatching a taxi vehicle 32 belonging to a different service area 7 for a vehicle dispatch request 22 with a boarding location at or near a major facility 10, thereby enabling efficient dispatch of taxi vehicles 32.

[0113] The program also causes the computer to receive a dispatch request 22 with an additional boarding location from the user terminal 20, and if the boarding location is included in a second service area (e.g., service area 7B) different from the first service area (e.g., service area 7A), output information regarding the additional input of a drop-off location (e.g., image 194 including the message "Destination specification is required in this area") to the user terminal 20, and not allocate a vehicle belonging to the first service area to the dispatch request 22 until the drop-off location is additionally input. In this way, by requiring the additional input of a drop-off location, it is possible to increase the chances of dispatching a taxi vehicle 32 belonging to a different service area 7 for a dispatch request 22 with a boarding location at or near a major facility 10, thereby enabling efficient dispatch of taxi vehicles 32.

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

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

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

[0117] 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 dispatch management device capable of communicating with the user terminal via a network; A vehicle dispatch management system comprising: The user terminal one or more first processors; The vehicle dispatch management device one or more second processors; The vehicle's operating area includes a first operating area and a second operating area different from the first operating area, The first processor: Transmitting a vehicle dispatch request to the vehicle dispatch management device, to which a boarding location is added in accordance with an input by the user; The second processor: receiving the vehicle dispatch request from the user terminal; If the boarding location is included in the second operating area, output information regarding additional input of a disembarking location to the user terminal; Do not allocate a vehicle to the vehicle dispatch request until the drop-off location is additionally input. Vehicle dispatch management system.

2. A vehicle dispatch management device capable of communicating with a user terminal via a network, one or more processors; The vehicle's operating area includes a first operating area and a second operating area different from the first operating area, the processor: receiving a vehicle dispatch request with a boarding location added from the user terminal; If the boarding location is included in the second operating area, output information regarding additional input of a disembarking location to the user terminal; Do not allocate a vehicle to the vehicle dispatch request until the drop-off location is additionally input. Vehicle dispatch management device.

3. The processor: If the received drop-off location is included in the first operating area, a vehicle belonging to the first operating area is assigned to the vehicle dispatch request; The vehicle dispatch management device according to claim 2 , wherein if the received drop-off location is not included in the first operational area, a vehicle belonging to the first operational area is not assigned to the vehicle dispatch request.

4. The vehicles belonging to the first operating area include a first vehicle and a second vehicle having different dispatchability requirements from the first vehicle, The processor: If the received drop-off location is included in the first operating area, the first vehicle is allocated to the vehicle dispatch request; The vehicle dispatch management device according to claim 3 , wherein the second vehicle is not assigned to the vehicle dispatch request even if the received drop-off location is included in the first service area.

5. The computer A request for dispatching a vehicle with a boarding location attached is received from the user terminal, If the boarding location is included in a second operating area different from the first operating area, output information regarding additional input of a disembarking location to the user terminal; A vehicle belonging to the first operating area is not allocated to the vehicle dispatch request until the drop-off location is additionally input. Vehicle allocation management method.

6. On the computer, A request for dispatching a vehicle with a boarding location attached is received from the user terminal, If the boarding location is included in a second operating area different from the first operating area, output information regarding additional input of a disembarking location to the user terminal; A vehicle belonging to the first operating area is not allocated to the vehicle dispatch request until the drop-off location is additionally input. A program to make it happen.

Images