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

Abstract

To efficiently dispatch a vehicle.SOLUTION: A vehicle dispatch management apparatus capable of communicating with a user terminal via a network includes one or more processors. The processor derives a travel value associated with traveling of a vehicle on the basis of a pick-up location and a drop-off location added to a vehicle dispatch request received from the user terminal, dispatches at least a second vehicle (NRS vehicle 42) to the vehicle dispatch request if the travel value satisfies a predetermined travel condition, and does not dispatch the second vehicle to the vehicle dispatch request if the travel value does not satisfy the predetermined travel condition.SELECTED DRAWING: Figure 15

Description

[Technical Field]

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

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

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

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

[0005] The operating area of ​​a ride-sharing vehicle is often smaller than that of a taxi. As a result, if a ride-sharing vehicle transports a user to a distant drop-off location outside the operating area, even if the ride-sharing vehicle is empty on its way back to the operating area, it may be unable to pick up the user depending on the relationship between the pick-up and drop-off locations, resulting in a decrease in vehicle utilization efficiency.

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

[0007] In order to solve the above problem, in the vehicle dispatch management system of the present invention, which includes a user terminal, a vehicle dispatch management device capable of communicating with the user terminal via a network, and vehicles including a first vehicle and a second vehicle having different dispatchability requirements from the first vehicle, the user terminal includes one or more first processors, and the vehicle dispatch management device includes one or more second processors, the first processor sends a vehicle dispatch request to the vehicle dispatch management device, with a boarding location and a disembarking location added in accordance with user input, the second processor derives a driving value associated with the vehicle's driving based on the boarding location and the disembarking location, and if the driving value satisfies predetermined driving conditions, assigns at least the second vehicle to the vehicle dispatch request, and if the driving value does not satisfy the predetermined driving conditions, does not assign the second vehicle to the vehicle dispatch request.

[0008] 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 processors derive driving values ​​associated with the vehicle's driving based on the boarding and disembarking locations attached to the dispatch request received from the user terminal, and if the driving values ​​satisfy predetermined driving conditions, assigns at least a second vehicle to the dispatch request, and if the driving values ​​do not satisfy the predetermined driving conditions, does not assign the second vehicle to the dispatch request.

[0009] Another vehicle dispatch management device of the present invention, capable of communicating with a user terminal via a network, includes one or more processors, which derive a driving value associated with the vehicle's driving based on the boarding and disembarking locations attached to the dispatch request received from the user terminal, and if the driving value satisfies predetermined driving conditions, assigns either a first vehicle or a second vehicle having different dispatchability requirements from the first vehicle to the dispatch request, and if the driving value does not satisfy the predetermined driving conditions, assigns the first vehicle to the dispatch request but does not assign the second vehicle.

[0010] Another vehicle dispatch management device of the present invention, capable of communicating with a user terminal via a network, includes one or more processors, which derive a driving value associated with the vehicle's driving based on the boarding and disembarking locations attached to the dispatch request received from the user terminal, and if the driving value satisfies predetermined driving conditions, allocates a first vehicle or a second vehicle having different dispatchability requirements from the first vehicle to the dispatch request without prioritizing them, and if the driving value does not satisfy the predetermined driving conditions, allocates the first vehicle to the dispatch request with priority over the second vehicle.

[0011] The processor may assign either the first vehicle or the second vehicle to the dispatch request if the received drop-off location is within the operating area of ​​the first vehicle, and may assign the first vehicle to the dispatch request but not the second vehicle if the received drop-off location is not within the operating area of ​​the first vehicle.

[0012] The travel value may be a planned travel distance from the boarding location to the disembarking location, and the predetermined travel condition may be a predetermined distance or less.

[0013] The travel value may be a planned travel time from the boarding location to the disembarking location, and the predetermined travel condition may be a predetermined time or less.

[0014] In order to solve the above problem, the vehicle dispatch management method of the present invention has a computer that derives a driving value associated with the vehicle's driving based on the boarding and disembarking locations attached to a vehicle dispatch request received from a user terminal, and if the driving value satisfies predetermined driving conditions, assigns at least a second vehicle to the vehicle dispatch request, and if the driving value does not satisfy the predetermined driving conditions, does not assign the second vehicle to the vehicle dispatch request.

[0015] In order to solve the above problem, the program of the present invention causes a computer to derive a driving value associated with the vehicle's driving based on the boarding and disembarking locations attached to a dispatch request received from a user terminal, and if the driving value satisfies predetermined driving conditions, allocate at least a second vehicle to the dispatch request, and if the driving value does not satisfy the predetermined driving conditions, not allocate the second vehicle to the dispatch request. [Effects of the Invention]

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

[0017] [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 a first explanatory diagram for explaining the pair creation process. [Figure 10] Fig. 10A is a second explanatory diagram for explaining the pair creating process, and Fig. 10B is a third explanatory diagram for explaining the pair creating process. [Figure 11] Fig. 11A is a first explanatory diagram for explaining the matching process, Fig. 11B is a second explanatory diagram for explaining the matching process, and Fig. 11C is a third explanatory diagram for explaining the matching process. [Figure 12] FIG. 12 is an explanatory diagram showing the results of matching by the dispatch unit. [Figure 13] Fig. 13A is a first explanatory diagram for explaining the processing of the dispatch unit, and Fig. 13B is a second explanatory diagram for explaining the processing of the dispatch unit. [Figure 14] Fig. 14A is a first explanatory diagram for explaining business areas. Fig. 14B is a second explanatory diagram for explaining business areas. Fig. 14C is a third explanatory diagram for explaining business areas. Fig. 14D is a fourth explanatory diagram for explaining business areas. [Figure 15] Fig. 15A is a first explanatory diagram for explaining the processing of the dispatch unit, and Fig. 15B is a second explanatory diagram for explaining the processing of the dispatch unit. [Figure 16] Fig. 16A is a first explanatory diagram for explaining the positional relationship of business districts, and Fig. 16B is a second explanatory diagram for explaining the positional relationship of business districts. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

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

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

[0029] The operating area of ​​the NRS vehicle 42 is included in the operating area of ​​the taxi vehicle 32, and is often narrower than the operating area of ​​the taxi vehicle 32. This is for the following reason. The NRS vehicle 42 is intended to operate in an auxiliary role to the taxi vehicle 32 in areas (or areas and time periods) where a shortage of taxi drivers 3 means that a taxi vehicle 32 cannot be immediately dispatched even if a person wants to ride in it. Therefore, the operating area of ​​the NRS vehicle 42 is set to be limited to areas where a taxi vehicle 32 cannot be immediately dispatched even if a person wants to ride in it. Therefore, the operating area of ​​the NRS vehicle 42 is often narrower than the operating area of ​​the taxi vehicle 32. Furthermore, while the operating area of ​​the taxi vehicle 32 is limited in geographical range, there are no time restrictions, whereas the operating area of ​​the NRS vehicle 42 is not only limited in geographical range, but also in time restrictions, such as only during time periods (including seasons) when the supply of taxi vehicles 32 is insufficient to meet the demand. In this way, a taxi shortage situation in an area, time period, or time zone where there is a shortage of taxi vehicles 32 is considered to be "unavoidable for the public welfare" under Article 78, paragraph 3 of the Road Transportation Act, and a ride-sharing business is permitted. Note that the operating area of ​​the NRS vehicle 42 is managed by a taxi business operator, just like the operating area of ​​the taxi vehicle 32, and is subject to the same regulations as the operating area of ​​the taxi vehicle 32. Note that in this embodiment, an example is given in which the operation of the NRS vehicle 42 is restricted not only in terms of the geographical range of the operating area but also in terms of the time period, but this is not limiting, and there are also cases in which the operating area is restricted only in terms of the geographical range, with no time restrictions.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0046] (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 in operation). The operating state of the vehicle mainly refers to a pick-up state (a state in which the vehicle is traveling toward the boarding location of user 2) and a hire state (a state in which the vehicle is traveling with user 2 on board), and does not include a stopped state in which the vehicle is waiting for a dispatch request. Furthermore, the 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.

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

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

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

[0050] (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 pair candidate 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 pair candidate 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 conditions if any of the vehicle's allowable items does not match the set items of the vehicle allocation request 22. On the other hand, if the vehicle's allowable items match all of the set items of the vehicle allocation request 22, the vehicle allocation unit 172 associates the vehicle with the vehicle allocation request 22 as a pair candidate vehicle that satisfies the pairing conditions of the vehicle allocation request 22.

[0051] FIG. 9 is a first explanatory diagram illustrating the pair generation process. FIG. 10A is a second explanatory diagram illustrating the pair generation process. FIG. 10B is a third explanatory diagram illustrating the pair generation process. Here, it is assumed that all of the vehicles 32a, 42b, 32c, 32d, 32e, 42f, 32g, 32h, 42i, and 42j extracted by the vehicle allocation unit 172 are compatible with the setting items of the vehicle allocation requests 22a to 22c of users 2a to 2c. Furthermore, it is assumed that the extracted vehicles 32a, 32c, 32d, 32e, 32g, and 32h are compatible with the vehicle allocation category "taxi vehicles 32 only" included in the setting items of the vehicle allocation request 22d of user 2d, but that the extracted vehicles 42b, 42f, 42i, and 42j are not compatible.

[0052] 9, in response to the vehicle dispatch request 22a of the user 2a, the vehicle dispatch unit 172 extracts vehicles that satisfy the pairing conditions of the vehicle dispatch request 22a from the vehicles 32a, 42b, 32c, 32d, 32e, 42f, 32g, 32h, 42i, and 42j, and sets these vehicles as pair candidate vehicles 232a, 242b, 232c, 232d, 232e, 242f, 232g, 232h, 242i, and 242j. Here, the taxi vehicles 32 that satisfy the pairing conditions of the vehicle dispatch request 22 are set as pair candidate vehicles 232, and the NRS vehicle 42 that satisfies the pairing conditions of the vehicle dispatch request 22 is set as pair candidate vehicle 242. Then, the vehicle allocation unit 172 associates the pair candidate vehicles 232a, 242b, 232c, 232d, 232e, 242f, 232g, 232h, 242i, and 242j with the vehicle allocation request 22a of user 2a. Similarly, the vehicle allocation unit 172 associates the pair candidate vehicles 232a, 242b, 232c, 232d, 232e, 242f, 232g, 232h, 242i, and 242j with the vehicle allocation request 22b of user 2b. Furthermore, the vehicle allocation unit 172 associates the pair candidate vehicles 232a, 242b, 232c, 232d, 232e, 242f, 232g, 232h, 242i, and 242j with the vehicle allocation request 22c of user 2c.

[0053] In response to the vehicle dispatch request 22d of the user 2d, the vehicle dispatch unit 172 excludes the NRS vehicles 42b, 42f, 42i, and 42j that do not satisfy the pairing condition of the vehicle dispatch request 22d of the user 2d from the vehicles 32a, 42b, 32c, 32d, 32e, 32g, and 32h, and extracts the taxi vehicles 32a, 32c, 32d, 32e, 32g, and 32h that satisfy the pairing condition of the vehicle dispatch request 22d of the user 2d, and sets these vehicles as pair candidate vehicles 232a, 232c, 232d, 232e, 232g, and 232h. The vehicle dispatch unit 172 then associates the pair candidate vehicles 232a, 232c, 232d, 232e, 232g, and 232h with the vehicle dispatch request 22d of the user 2d. In this way, as shown in FIG. 10A, one or more pair candidate vehicles are associated with each of the vehicle allocation requests 22a to 22d.

[0054] Here, the vehicle dispatch unit 172 determines whether the vehicle is suitable for all the setting items of the vehicle dispatch request 22. However, this is not the only case, and if the vehicle dispatch unit 172 has already determined the suitability of some of the setting items, such as the desired vehicle dispatch or the sales office, the vehicle dispatch unit 172 may omit determining the suitability of those setting items. In this way, the processing load on the vehicle dispatch management server 60 can be reduced.

[0055] Next, the vehicle allocation unit 172 estimates the estimated arrival time of the associated pair candidate vehicle at the boarding location for each of the vehicle allocation requests 22a to 22d, and associates the estimated arrival time with each of the pair candidate vehicles. Since the positional relationship between the user 2 who made the vehicle allocation request 22 and the vehicle differs for each vehicle allocation request 22, the estimated arrival time for each vehicle allocation request 22 will differ even for the same pair candidate vehicle.

[0056] Next, the vehicle dispatch unit 172 sets priorities for the pair candidate vehicles associated with each vehicle dispatch request 22. Here, the priority indicates the order in which the vehicle should be assigned as a vehicle to be dispatched. When setting the priorities, the vehicle dispatch unit 172 recalculates the estimated arrival time at the boarding location. At this time, the shorter the recalculated estimated arrival time, the higher the priority. The recalculated estimated arrival time may be calculated by dividing the Euclidean distance by a predetermined speed, as in the case of the extraction conditions. Alternatively, the recalculated estimated arrival time may be calculated by taking into account the travel time of the vehicle's route to the boarding location. Furthermore, the vehicle dispatch unit 172 may derive the travel time by taking into account, in addition to the route, the vehicle's travel direction at the time of vehicle extraction, the stop time at traffic lights along the route, and the like. Therefore, the vehicle dispatch unit 172 can set priorities using estimated arrival times that are equivalent to or more accurate than the estimated arrival times based on the Euclidean distance used by the vehicle dispatch unit 172 as an extraction condition.

[0057] For example, as shown in Figures 10A and 10B, the vehicle dispatch unit 172 rearranges the pair candidate vehicles 232a, 242b, 232c, 232d, 232e, 242f, 232g, 232h, 242i, and 242j associated with the vehicle dispatch request 22a into pair candidate vehicles 242b, 232d, 232c, 232e, 232a, 242f, 242i, 232h, 232g, and 242j in order of shortest recalculated estimated arrival time. Similarly, the vehicle dispatch unit 172 rearranges the pair candidate vehicles 232a, 242b, 232c, 232d, 232e, 242f, 232g, 232h, 242i, and 242j associated with the vehicle dispatch request 22b into pair candidate vehicles 242i, 232h, 242f, 232e, 232g, 232d, 232a, 242b, 242j, and 232c in order of shortest recalculated estimated arrival time. Furthermore, the vehicle allocation unit 172 rearranges the pair candidate vehicles 232a, 242b, 232c, 232d, 232e, 242f, 232g, 232h, 242i, and 242j associated with the vehicle allocation request 22c into pair candidate vehicles 242i, 232e, 232d, 242f, 232h, 232g, 232c, 242b, 242j, and 232a in order of shortest recalculated estimated arrival times. Furthermore, the vehicle allocation unit 172 rearranges the pair candidate vehicles 232a, 232c, 232d, 232e, 232g, and 232h associated with the vehicle allocation request 22d into pair candidate vehicles 232d, 232e, 232h, 232c, 232g, and 232a in order of shortest recalculated estimated arrival times.

[0058] 10B, one or more pair candidate vehicles are prioritized for each of the vehicle allocation requests 22a to 22d, and one or more combinations of vehicle allocation requests 22 and pair candidate vehicles are generated. Here, it can be seen that the priority of the pair candidate vehicles corresponding to each of the vehicle allocation requests 22a to 22d differs depending on the positional relationship between the users 2a to 2d and the pair candidate vehicles.

[0059] 10B, one or more pair candidate vehicles are associated with each of the vehicle dispatch requests 22a to 22d in a prioritized order, i.e., in the order of shortest expected arrival time at the boarding location. Therefore, the vehicle dispatch management server 60 can assign a vehicle with the shortest expected arrival time at the boarding location by extracting pair candidate vehicles in the order of highest priority for each of the vehicle dispatch requests 22a to 22d.

[0060] Furthermore, here, all vehicles available for dispatch are associated with each of the dispatch requests 22a to 22d, and a priority order is set. This is because there are cases where a vehicle selected as a dispatch target vehicle cannot accept the dispatch request. For example, suppose a vehicle is cruising, accepting a ride request from a user 2 it has spotted along the driving route, and simultaneously receiving a ride request from a user 2 nearby the driving route at the same time as a dispatch request 22 from a user 2a to 2d. In this case, the vehicle will not be able to accept the dispatch request 22 because it will be giving a ride to the nearby user 2. Therefore, even if a vehicle selected as a dispatch target vehicle cannot accept the dispatch request for some reason, the dispatch management server 60 can efficiently assign a vehicle with a short estimated time of arrival at the boarding location to each of the dispatch requests 22a to 22d by extracting a pair candidate vehicle with the next highest priority order.

[0061] However, as shown by the dashed line in Fig. 10B, among vehicle allocation requests 22a to 22d, there may be cases where the pair candidate vehicles with the highest priority overlap in vehicle allocation requests 22b and 22c. In this case, vehicle allocation management server 60 will not be able to appropriately assign pair candidate vehicles as vehicles to be allocated to vehicle allocation requests 22b and 22c. Therefore, vehicle allocation unit 172 matches vehicle allocation requests 22 with pair candidate vehicles.

[0062] (Matching process S6) The vehicle allocation unit 172 matches the vehicle allocation requests 22 with the pair candidate vehicles for a plurality of combinations obtained by multiplying the vehicle allocation requests 22 and the pair candidate vehicles associated in the pair generation process S5. In this matching process, the vehicle allocation requests 22 are matched with the pair candidate vehicles so that one pair candidate vehicle with the highest priority among the at least one pair candidate vehicle associated with each vehicle allocation request 22 does not overlap with at least one pair candidate vehicle associated with another vehicle allocation request 22. For example, the vehicle allocation unit 172 exclusively matches, for each of the vehicle allocation requests 22a to 22d, the pair candidate vehicle that has the shortest average estimated arrival time at the boarding location.

[0063] FIG. 11A is a first explanatory diagram illustrating the matching process, FIG. 11B is a second explanatory diagram illustrating the matching process, and FIG. 11C is a third explanatory diagram illustrating the matching process. As shown in FIG. 11A, one or more pair candidate vehicles are associated with each of vehicle allocation requests 22a to 22d, with priority assigned. Here, vehicle allocation unit 172 attempts to extract the pair candidate vehicle with the highest priority for each of vehicle allocation requests 22a to 22d as the vehicle to be allocated. In other words, by extracting pair candidate vehicle 242b for vehicle allocation request 22a, pair candidate vehicle 242i for vehicle allocation request 22b, pair candidate vehicle 242i for vehicle allocation request 22c, and pair candidate vehicle 232d for vehicle allocation request 22d, vehicle allocation unit 172 can allocate a vehicle with the shortest expected arrival time at the boarding location to each of vehicle allocation requests 22a to 22d.

[0064] Here, the pair candidate vehicle 242b of the vehicle allocation request 22a does not overlap with the pair candidate vehicles 242i and 232d with the highest priority in the other vehicle allocation requests 22b, 22c, and 22d. Therefore, the vehicle allocation unit 172 may determine the pair candidate vehicle 242b of the vehicle allocation request 22a as the vehicle to be allocated. Furthermore, the pair candidate vehicle 232d of the vehicle allocation request 22d does not overlap with the pair candidate vehicles 242b and 242i with the highest priority in the other vehicle allocation requests 22a, 22b, and 22c. Therefore, the vehicle allocation unit 172 may determine the pair candidate vehicle 232d of the vehicle allocation request 22d as the vehicle to be allocated. However, the pair candidate vehicles 242i with the highest priority in the vehicle allocation requests 22b and 22c overlap. Even if the same pair candidate vehicle 242i is simultaneously assigned as a vehicle to be allocated to multiple vehicle allocation requests 22b and 22c, the pair candidate vehicle 242i (NRS vehicle 42i) cannot accept both vehicle allocation requests 22b and 22c at the same time.

[0065] Therefore, the vehicle allocation unit 172 performs an exclusion process to change the combinations of the vehicle allocation requests 22b, 22c and the pair candidate vehicles so that the pair candidate vehicles with the highest priority in each of the vehicle allocation requests 22b, 22c are different. Specifically, the vehicle allocation unit 172 assigns the pair candidate vehicle 242i to one of the vehicle allocation requests 22b, 22c in which the pair candidate vehicle 242i overlaps. Then, for the other vehicle allocation requests 22, the vehicle allocation unit 172 assigns pair candidate vehicles with lower priorities until there are no overlaps between the other vehicle allocation requests 22 and the pair candidate vehicles.

[0066] For example, as shown in FIG. 11B, the vehicle allocation unit 172 assigns pair candidate vehicle 242i to vehicle allocation request 22b, and assigns pair candidate vehicle 232e, which has the next highest priority after pair candidate vehicle 242i, to vehicle allocation request 22c. In this manner, the combinations in which pair candidate vehicles 242b, 242i, 232e, and 232d are assigned to vehicle allocation requests 22a to 22d are defined as pair group A. Similarly, as shown in FIG. 11C, the vehicle allocation unit 172 assigns 242i to vehicle allocation request 22c, and assigns pair candidate vehicle 232h, which has the next highest priority after pair candidate vehicle 242i, to vehicle allocation request 22b. In this manner, the combinations in which pair candidate vehicles 242b, 232h, 242i, and 232d are assigned to vehicle allocation requests 22a to 22d are defined as pair group B. In this manner, it is possible to avoid the highest priority pair candidate vehicle being assigned to multiple vehicle allocation requests 22 in each of pair groups A and B.

[0067] FIG. 12 is an explanatory diagram showing the results of matching by the vehicle allocation unit 172. For example, for each of pair groups A and B, the vehicle allocation unit 172 adds up the estimated arrival times of vehicles at the boarding location for all combinations of the vehicle allocation request 22 and the pair candidate vehicles. Then, the vehicle allocation unit 172 identifies the pair group with the shorter total estimated arrival time as a matching result for the combination of the vehicle allocation request 22 and the vehicle to be allocated. For example, suppose that the total estimated arrival times for pair groups A and B are such that pair group B is smaller than pair group A. In this case, the vehicle allocation unit 172 identifies pair group B with the shorter total estimated arrival time as the matching result. When a pair group (for example, pair group B) is identified as a matching result by the matching of the vehicle allocation unit 172, the combination of pair group B is reflected as shown in Figure 12, and pair candidate vehicle 242b becomes the vehicle to be allocated for vehicle allocation request 22a, pair candidate vehicle 232h becomes the vehicle to be allocated for vehicle allocation request 22b, pair candidate vehicle 242i becomes the vehicle to be allocated for vehicle allocation request 22c, and pair candidate vehicle 232d becomes the vehicle to be allocated for vehicle allocation request 22d.

[0068] In this way, by matching multiple vehicle dispatch requests 22 with multiple vehicles at once, the relative positions of user 2 and vehicles can be determined comprehensively compared to when vehicle dispatch requests 22 are matched sequentially and individually, enabling more efficient vehicle dispatch.

[0069] Note that the matching algorithm between the vehicle allocation requests 22 and the pair candidate vehicles is not limited to the above case, and various matching algorithms can be applied as long as at least one pair candidate vehicle in each vehicle allocation request 22, particularly the pair candidate vehicle with the highest priority, does not overlap with the pair candidate vehicle with the highest priority in another vehicle allocation request 22. For example, the vehicle allocation unit 172 estimates the estimated arrival time of the vehicle at the boarding location for all combinations of the vehicle allocation request 22 and the pair candidate vehicle for each of multiple pair groups A and B. Then, the vehicle allocation unit 172 may identify as the matching result the pair group A or B in which the combination of the vehicle allocation request 22 and the pair candidate vehicle with the longest estimated arrival time is the shortest. Furthermore, the vehicle allocation unit 172 may add up the distances (travel distances) to the boarding location for all combinations of the vehicle allocation request 22 and the pair candidate vehicle for each of the pair groups A and B. In this case, the vehicle allocation unit 172 identifies as the matching result the pair group with the shortest total distance. It should be noted that an existing matching algorithm may be used as the matching algorithm between the vehicle allocation request 22 and the pair candidate vehicle.

[0070] Note that the vehicle allocation unit 172 maintains the priorities of the pair candidate vehicles associated with the vehicle allocation requests 22a to 22d even after pair group B is identified as the matching result. This is because, as described above, if a vehicle selected as a vehicle to be allocated cannot accept the vehicle allocation request for some reason, the pair candidate vehicle with the next highest priority is extracted as a vehicle to be allocated.

[0071] FIG. 13A is a first explanatory diagram illustrating the processing of the vehicle allocation unit, and FIG. 13B is a second explanatory diagram illustrating the processing of the vehicle allocation unit. As described above, once a pair group is identified and the pair candidate vehicle with the highest priority is exclusively determined for each of the vehicle allocation requests 22a to 22d, the pair candidate vehicle is deleted from the pair candidate vehicles associated with the other vehicle allocation requests 22. This is because a pair candidate vehicle only has one opportunity to become a vehicle to be allocated in one matching process. That is, once the vehicle terminal control unit 174 notifies the pair candidate vehicle of information indicating that the pair candidate vehicle has become a vehicle to be allocated, the vehicle terminal control unit 174 does not subsequently notify the pair candidate vehicle of information indicating that the pair candidate vehicle has become a vehicle to be allocated for another vehicle allocation request 22, regardless of whether the vehicle allocation request 22 is accepted. Therefore, a pair candidate vehicle that has already become a vehicle to be allocated for a vehicle allocation request 22 will not become a vehicle to be allocated for another vehicle allocation request 22. In this way, for example, pair candidate vehicles 242b, 232h, 242i, and 232d matched with vehicle allocation requests 22a to 22d are deleted from pair candidate vehicles associated with other vehicle allocation requests 22, as shown in Fig. 13A. In this way, new combinations are generated in which pair candidate vehicles are associated with each of vehicle allocation requests 22a to 22d in descending order of priority, as shown in Fig. 13B.

[0072] Here, an example has been described in which matching is performed so that the pair candidate vehicles with the highest priority do not overlap between vehicle allocation requests 22. However, if the pair candidate vehicles with the second highest priority overlap between vehicle allocation requests 22, matching may not be performed for those pair candidate vehicles. This is for the following reason. The pair candidate vehicle with the highest priority is assigned to the vehicle allocation request 22 as the vehicle to be allocated, and the pair candidate vehicle with the second highest priority is merely a backup in case the pair candidate vehicle with the highest priority does not accept the vehicle allocation request 22. Nevertheless, if the pair candidate vehicle with the second highest priority is exclusively associated with the vehicle allocation request 22, there may be cases in which vehicle allocation is not efficient.

[0073] 13B, the pair candidate vehicle with the next highest priority is pair candidate vehicle 232e. Suppose that vehicle allocation unit 172 matches vehicle allocation requests 22c and 22d with pair candidate vehicle 232e with the next highest priority, and, for example, sets pair candidate vehicle 232e as the pair candidate vehicle with the next highest priority for vehicle allocation request 22c, and changes the pair candidate vehicle with the next highest priority for vehicle allocation request 22d from pair candidate vehicle 232e to pair candidate vehicle 232c. Then, the pair candidate vehicles for vehicle allocation request 22c become {242i, 232e, 242f, ...} in descending order of priority, and the pair candidate vehicles for vehicle allocation request 22d become {232d, 232c, 232g, ...} in descending order of priority after pair candidate vehicle 232e is deleted.

[0074] Here, for example, suppose that pair candidate vehicle 242i, which has the highest priority, accepts the vehicle allocation request for vehicle allocation request 22c, and pair candidate vehicle 232d, which has the highest priority, does not accept the vehicle allocation request for vehicle allocation request 22d. In this case, pair candidate vehicle 232e, which has the next highest priority, will not be the vehicle to be allocated for vehicle allocation request 22c, and pair candidate vehicle 232c, which has the next highest priority, will be the vehicle to be allocated for vehicle allocation request 22d. However, pair candidate vehicle 232e, which has a higher priority than pair candidate vehicle 232c, should actually be the vehicle to be allocated for vehicle allocation request 22d.

[0075] Therefore, the vehicle allocation unit 172 does not perform matching for pair candidate vehicles other than the pair candidate vehicle with the highest priority, and allows overlapping pair candidate vehicles between vehicle allocation requests 22. In this way, even if the pair candidate vehicle with the highest priority does not accept the vehicle allocation request 22, it is possible to appropriately allocate the pair candidate vehicle with the next highest priority.

[0076] Note that if matching is not performed for pair candidate vehicles other than the pair candidate vehicle with the highest priority, it is possible that multiple pair candidate vehicles will become vehicles to be allocated for vehicle allocation request 22. For example, in the example of Figure 13B, pair candidate vehicle 242i matched with vehicle allocation request 22c may not accept vehicle allocation request 22c, and pair candidate vehicle 232d matched with vehicle allocation request 22d may also not accept vehicle allocation request 22d. In this case, the pair candidate vehicles with the next highest priority in vehicle allocation requests 22c and 22d are both pair candidate vehicle 232e.

[0077] However, it is unlikely or impossible that the timing when pair candidate vehicle 242i refuses to accept vehicle allocation request 22c and the timing when pair candidate vehicle 232d refuses to accept vehicle allocation request 22d will be exactly the same. Here, the vehicle allocation management server 60 designates the pair candidate vehicle with the next highest priority as the vehicle to be allocated for the vehicle allocation request 22 whose acceptance was previously refused, and deletes that pair candidate vehicle from the pair candidate vehicles associated with other vehicle allocation requests 22. For example, first, assume that pair candidate vehicle 242i matched with vehicle allocation request 22c does not accept vehicle allocation request 22c, and then pair candidate vehicle 232d matched with vehicle allocation request 22d also does not accept vehicle allocation request 22d. In this case, the vehicle allocation management server 60 designates pair candidate vehicle 232e as the vehicle to be allocated for vehicle allocation request 22c whose acceptance was previously refused, and deletes pair candidate vehicle 232e from the pair candidate vehicles associated with vehicle allocation request 22d. In this way, for example, the pair candidate vehicle 232e will not be the vehicle to be allocated for the vehicle allocation request 22d, so that the pair candidate vehicles will not overlap and become the vehicle to be allocated for all vehicle allocation requests 22.

[0078] (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 installed in the vehicle that has become the dispatch target vehicle for the dispatch request 22 of information indicating that the vehicle has become the dispatch target vehicle (dispatch target notification). This dispatch target notification corresponds to a prompt to the driver of the dispatch target vehicle 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 dispatch target vehicle, and can consider whether or not to accept the dispatch request 22.

[0079] (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 become a vehicle to be dispatched 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 the acceptance of the vehicle dispatch request 22, to the vehicle dispatch management server 60.

[0080] 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 that the vehicle with the second highest priority among the vehicles associated with the vehicle allocation request 22 in the matching process S6 is 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 the vehicle has become the vehicle to be allocated (vehicle allocation target notification).

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

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

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

[0084] (Sales management of NRS vehicle 42) As described above, operating areas are set for the taxi vehicles 32 and the NRS vehicles 42. Here, the operating area of ​​the NRS vehicles 42 will be described.

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

[0086] A business area 8 (first business area) is defined as the geographical range of operation of the NRS vehicle 42. As shown by the two-dot chain line in FIG. 14A, the business area 8 of the NRS vehicle 42 is included in the business area 7 (traffic area: third business area) of the taxi vehicle 32, and is often narrower than the business area 7 of the taxi vehicle 32. However, the business area 8 of the NRS vehicle 42 may be equal to the business area 7 of the taxi vehicle 32. In this case, the taxi vehicle 32 can operate outside the business area 7 (traffic area), but as will be described later, the NRS vehicle 42 cannot operate outside the business area 7 (traffic area). Therefore, if the business area 8 of the NRS vehicle 42 is equal to the business area 7 of the taxi vehicle 32, the NRS vehicle 42 cannot operate outside the business area 8. Furthermore, since the NRS vehicle 42 is positioned as a supplement to the taxi vehicle 32, it can charge the user 2 the same fee (fare) as the taxi vehicle 32, as described above. However, if the NRS vehicle 42 is operated as an independent means of transportation rather than as a supplement to the taxi vehicle 32, the NRS vehicle 42 may have a different fare structure from the taxi vehicle 32, for example, by charging a lower fare than the taxi vehicle 32. In this case, the NRS vehicle 42 may be able to operate outside the operating area 7 (traffic zone). Furthermore, while the operation of the taxi vehicle 32 is limited by the geographical area of ​​the operating area 7 but not by the time, the operation of the NRS vehicle 42 is limited by the geographical area of ​​the operating area 8 as well as by the time. Here, for the sake of convenience, the operating area 8 of the NRS vehicle 42 will be mentioned.

[0087] The NRS vehicle 42 can operate within the business area 8 managed by the taxi business to which it belongs. Therefore, as shown in FIG. 14A, the NRS vehicle 42 can transport the user 2 from a boarding location within the business area 8 indicated by the dashed line to a disembarking location within the same business area 8.

[0088] 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. As shown in FIG. 14A, if operations are only possible when the boarding and disembarking locations 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. 14B.

[0089] As shown in FIG. 14B , after transporting user 2 outside the service area 8, the NRS vehicle 42 returns to its own service area 8 to continue business. Since the NRS vehicle 42 drops off user 2 at the drop-off location, user 2 is not on board while 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 and results in a decrease in vehicle efficiency. To prevent this, as shown in FIG. 14C , even if the NRS vehicle 42 is located outside the service area 8, as long as the NRS vehicle 42 is located within the service area 7 of the taxi vehicle 32 and the drop-off location is within its own service area 8, it is considered to be operating in the service area 8 and can transport user 2 from a pick-up location outside the service area 8 to a drop-off location within the service area 8.

[0090] In addition, when the NRS vehicle 42 returns from outside the service area 8, it can adopt an extended service area 9 (second service area) shown by the dashed line in FIG. 14C , which is obtained by evenly expanding the service area 8 outward, for example, by about 5 km. As described above, the service area 8 of the NRS vehicle 42 is often narrower than the service area 7 of the taxi vehicle 32. Therefore, here, the drop-off location, which is a requirement for dispatchability, 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 not within its own service area 8 but is within the extended service area 9, the NRS vehicle 42 can transport user 2 from a boarding location outside the service area 8 to a drop-off location within the extended service area 9. Therefore, if the drop-off location is not within its own service area 8 but is within the extended service area 9, the NRS vehicle 42 can transport user 2 from a boarding location outside the service area 8 but within the extended service area 9 to a drop-off location within the extended service area 9, i.e., within the extended service area 9. In addition, when an NRS vehicle 42 is a candidate for dispatch based on the fact that the drop-off location is not within its own business area 8 but is within its extended business area 9, the dispatch unit 172 may select the NRS vehicle 42 as a vehicle to be dispatched, provided that the NRS vehicle 42 is returning toward its own business area 8 (traveling in the returning direction) when it receives the dispatch request 22.

[0091] In the above description, the expanded service area 9 is an area obtained by uniformly expanding the service area 8 outward by a fixed distance of approximately 5 km. However, the expanded service area 9 is not limited to this example, and may be an area obtained by expanding only a portion of the periphery of the service area 8. The expansion distance does not have to be uniform and may be variable. For example, the vehicle dispatch management server 60 may change the distance by which the service area 8 is expanded outward as the expanded service area 9 in real time. The vehicle dispatch management server 60 may also change the distance by which the service area 8 is expanded outward as the expanded service area 9 depending on the time of day or the operating status of the NRS vehicle 42. Instead of the distance by which the service area 8 is expanded outward (Euclidean distance) as the expanded service area 9, an equivalent time (for example, the time obtained by dividing the Euclidean distance by a predetermined speed (for example, the average speed when the vehicle is operating)) may be used.

[0092] However, when the NRS vehicle 42 is located outside the service area 8, transporting user 2 from outside the service area 8 to a drop-off location outside the expanded service area 9 is not a business within the service area 8 of the NRS vehicle 42 (out-of-area business), even if it is within the service area 7 of the taxi vehicle 32. Therefore, the NRS vehicle 42 cannot transport user 2 from a boarding location outside the service area 8 to a drop-off location outside the expanded service area 9, as shown in Figure 14D.

[0093] In the example of Figure 14D, 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.

[0094] In the vehicle dispatch management system 1, as shown in Figures 14A, 14B, and 14C, 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 14D, 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.

[0095] Here, if the range in which NRS vehicle 42 is a candidate for dispatch is expanded beyond the service area 8 indefinitely, the following problem arises. Ride sharing is originally intended for short-distance transportation of user 2. Furthermore, as described above, the service area 8 of NRS vehicle 42 is included in the service area 7 (traffic area) of taxi vehicle 32, and is often smaller than the service area 7 of taxi vehicle 32. Similarly, although the extended service area 9 of NRS vehicle 42 is an area that extends outward from the service area 8 of NRS vehicle 42, it is included in the service area 7 (traffic area) of taxi vehicle 32. Therefore, the size of the service area has the relationship: service area 8 < extended service area 9 ≦ service area 7. Furthermore, the location of the service area is such that the service area 8 is included in the extended service area 9, and both the service area 8 and the extended service area 9 are included in the service area 7. If the range in which the NRS vehicle 42 can be a candidate for dispatch is unlimited, for example, the NRS vehicle 42 will be a candidate for dispatch even when it is located outside the operating area 7 of the taxi vehicle 32, and the NRS vehicle 42 will transport the user 2 across the operating area 7 of the taxi vehicle 32. In this case, the NRS driver 4 may be forced to transport the user 2 long distances unintentionally.

[0096] Therefore, in the vehicle dispatch management system 1, as shown in Figures 14A, 14B, and 14C, if the boarding location is within its own business area 8 or the disembarking location is included in its own extended 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 within the business area 7 (traffic zone) of the taxi vehicle 32. In this case, 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, if its location is within the business area 7 of the taxi vehicle 32, it can be a candidate for dispatch, provided that the disembarking location is within its own extended business area 9 (return allocation condition), but if its location is outside the business area 7 of the taxi vehicle 32, it is not a candidate for dispatch.

[0097] In this way, the NRS vehicle 42 can transport user 2 long distances as long as it is within the service area 7 of the taxi vehicle 32. However, as described above, ride sharing is originally intended for short-distance transportation of user 2, and the service area 8 of the NRS vehicle 42 is often smaller than the service area 7 (traffic area) of the taxi vehicle 32, which can result in the following inconvenience. That is, because the service area 8 of the NRS vehicle 42 is small, the NRS vehicle 42 is more likely to transport user 2 whose boarding location is within the service area 8 but whose drop-off location is outside the service area 8. After transporting user 2 to a drop-off location outside the service area 8, the NRS vehicle 42 becomes a candidate for dispatch for a dispatch request 22 whose drop-off location is within the expanded service area 9 while returning to the service area 8, but does not become a candidate for dispatch for a dispatch request 22 whose drop-off location is outside the expanded service area 9. Therefore, if the NRS vehicle 42 transports user 2 outside the service area 8, there is a risk that it will lose an opportunity to pick up a new user 2 during its return. Therefore, the vehicle dispatch management system 1 restricts the NRS vehicle 42 from transporting the user 2 over long distances, so that the NRS vehicle 42 can remain within its own business area 8 and continue business.

[0098] FIG. 15A is a first explanatory diagram illustrating the processing of the vehicle dispatch unit 172, and FIG. 15B is a second explanatory diagram illustrating the processing of the vehicle dispatch unit 172. Specifically, when the vehicle dispatch unit 172 of the vehicle dispatch management server 60 receives a vehicle dispatch request 22 from the user terminal 20, it derives a mileage value based on the boarding location and disembarking location added to the vehicle dispatch request 22. The mileage value is a value accumulated as the vehicle travels and is expressed, for example, as a planned riding distance or a planned riding time. The planned riding distance is a Euclidean distance from the boarding location to the disembarking location that is derived in advance. The planned riding distance may be a distance that takes into account the route of the vehicle from the boarding location to the disembarking location. The planned riding distance may also be a distance that takes into account the route and the vehicle's traveling direction, etc. The planned riding time is a time that is derived in advance and is calculated by dividing the planned riding distance by a predetermined speed (for example, the average speed when the vehicle is operating). The planned riding time may also take into account the time spent stopping at traffic lights along the route. In the following description, the planned travel distance is used as the travel value, but it goes without saying that the planned travel time can be substituted.

[0099] If the derived planned ride distance (travel value) satisfies a predetermined travel condition, the dispatch unit 172 assigns either a taxi vehicle 32 or an NRS vehicle 42 to the dispatch request 22. On the other hand, if the derived travel value does not satisfy the predetermined travel condition, the dispatch unit 172 assigns a taxi vehicle 32 to the dispatch request 22 but does not assign an NRS vehicle 42. The travel condition is expressed as a threshold value for comparing the travel value, and indicates, for example, whether the travel value is equal to or less than a predetermined distance or a predetermined time. The predetermined distance is a distance that serves as a threshold and is set to, for example, 20 km. The predetermined time is a time obtained by dividing the predetermined distance by a predetermined speed (for example, the average speed when the vehicle is operating) and is set to, for example, 0.5 hours (20 km / (40 km / h)). In the following description, the predetermined distance is used as the travel condition; however, if the travel value is the planned ride time, it goes without saying that the travel condition can be replaced with the predetermined time.

[0100] Specifically, in the pair generation process S5, the vehicle allocation unit 172 extracts at least one pair candidate vehicle from the vehicles extracted in the vehicle extraction process S4 for each vehicle allocation request 22 if the vehicle satisfies a predetermined pair condition and the planned travel distance is less than or equal to a predetermined distance, and associates the extracted pair candidate vehicle with the vehicle allocation request 22. Therefore, if the planned travel distance is less than or equal to the predetermined distance, the pair candidate vehicles include an NRS vehicle 42, and the vehicle allocation unit 172 can allocate either a taxi vehicle 32 or an NRS vehicle 42 to the vehicle allocation request 22, as shown in FIG. 15A. On the other hand, if the planned travel distance is longer than the predetermined distance, the pair candidate vehicles do not include an NRS vehicle 42, and the vehicle allocation unit 172 allocates a taxi vehicle 32 to the vehicle allocation request 22, but does not allocate an NRS vehicle 42, as shown in FIG. 15B. In addition, the dispatch unit 172 simply compares the planned riding distance with the predetermined distance, and if the planned riding distance is longer than the predetermined distance, regardless of whether the drop-off location is within the business area 8 of the NRS vehicle 42 or outside the business area 8, the NRS vehicle 42 will not be assigned to the dispatch request 22.

[0101] With this configuration, the NRS vehicle 42 is prevented from transporting user 2 over long distances, and can operate by remaining within its own business area 8 for a relatively long period of time. Therefore, in the vehicle dispatch management system 1, the taxi vehicle 32 is mainly responsible for transporting user 2 over long distances, and the NRS vehicle 42 is mainly responsible for transporting user 2 over short distances, so that the roles related to transporting user 2 can be divided according to the planned distance of the ride.

[0102] In the above description, an example has been given in which the vehicle dispatching unit 172 does not assign an NRS vehicle 42 to the vehicle dispatch request 22 if the planned riding distance is longer than a predetermined distance. However, this is not limited to such a case, and the vehicle dispatching unit 172 may assign the NRS vehicle 42 only with a lower priority than the taxi vehicle 32 if the planned riding distance is longer than the predetermined distance. For example, if the derived planned riding distance is equal to or shorter than a predetermined distance, the vehicle dispatching unit 172 assigns either the taxi vehicle 32 or the NRS vehicle 42 to the vehicle dispatch request 22 without prioritizing them. On the other hand, if the planned riding distance is longer than the predetermined distance, the vehicle dispatching unit 172 assigns the taxi vehicle 32 to the vehicle dispatch request 22 with a higher priority than the NRS vehicle 42.

[0103] Specifically, in the pair generation process S5, the vehicle allocation unit 172 matches the vehicle allocation requests 22 with vehicles such that the vehicle with the highest priority among 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. At this time, if the planned travel distance is longer than a predetermined distance, the vehicle allocation unit 172 changes the priority of the vehicles and allocates the taxi vehicle 32 with priority over the NRS vehicle 42. For example, assume that the vehicle allocation unit 172 determines the priority of vehicles for the vehicle allocation request 22 as shown in FIG. 10B. Here, if the planned travel distance is longer than a predetermined distance, the vehicle allocation unit 172 does not allocate the NRS vehicle 42 with a high priority. For example, in the vehicle allocation requests 22a, 22b, and 22c in FIG. 10B, the NRS vehicles 42b (pair candidate vehicle 242b) and 42i (pair candidate vehicle 242i) are associated with the highest priority. If the planned ride distance is longer than a predetermined distance, the vehicle allocation unit 172 does not allocate the NRS vehicle 42b (pair candidate vehicle 242b) or 42i (pair candidate vehicle 242i) to the highest priority. In this case, for example, in the vehicle allocation request 22a in FIG. 10B, the positions of the NRS vehicle 42b (pair candidate vehicle 242b) and the taxi vehicle 32d (pair candidate vehicle 232d) are swapped, and the pair candidate vehicles 232d, 242b, 232c, 232e, 232a, 242f, 242i, 232h, 232g, and 242j are associated in descending order of priority. In the matching process S6, the vehicle allocation unit 172 allocates vehicles to the vehicle allocation request 22 based on the priorities of the pair candidate vehicles. Consequently, the taxi vehicle 32 is allocated to the vehicle allocation request 22 with higher priority than the NRS vehicle 42.

[0104] While the example described above is one in which the dispatch unit 172 does not assign the NRS vehicle 42 the highest priority if the planned travel distance is longer than a predetermined distance, the example is not limited thereto, and the NRS vehicle 42 may not be assigned to multiple priorities, from the highest priority, for example, the highest priority and the second highest priority. While the example described above is one in which the dispatch unit 172 does not assign the NRS vehicle 42 a high priority if the planned travel distance is longer than a predetermined distance, the example is not limited thereto, and the priority of the NRS vehicle 42 may be relatively lowered by one or more levels. For example, if the planned travel distance is longer than a predetermined distance, the dispatch unit 172 lowers only the NRS vehicle 42 by one level among the pair candidate vehicles associated with the dispatch request 22a in FIG. 10B. 10B are rearranged to pair candidate vehicles 232d, 242b, 232c, 232e, 232a, 242f, 242i, 232h, 232g, and 242j. As a result, taxi vehicles 32 are allocated to the vehicle allocation request 22 with priority over NRS vehicles 42.

[0105] With this configuration, the NRS vehicle 42 is prevented from transporting user 2 over long distances, and can operate by remaining within its own business area 8 for a relatively long period of time. Therefore, in the vehicle dispatch management system 1, the taxi vehicle 32 is mainly responsible for transporting user 2 over long distances, and the NRS vehicle 42 is mainly responsible for transporting user 2 over short distances, so that the roles related to transporting user 2 can be divided according to the planned distance of the ride.

[0106] As described above, the operating range of the NRS vehicle 42 is limited to the operating area 7 of the taxi vehicle 32. Therefore, if the drop-off location is included in the operating area 7 of the taxi vehicle 32, the dispatch unit 172 assigns either a taxi vehicle 32 or an NRS vehicle 42 to the dispatch request 22. On the other hand, if the drop-off location is not included in the operating area 7 of the taxi vehicle 32, the dispatch unit 172 assigns a taxi vehicle 32 to the dispatch request 22, but does not assign an NRS vehicle 42.

[0107] Specifically, in the pair generation process S5, for each vehicle dispatch request 22, the vehicle dispatch unit 172 extracts at least one pair candidate vehicle from the vehicles extracted in the vehicle extraction process S4 if the vehicle satisfies a predetermined pair condition and the drop-off location is included in the business area 7 of the taxi vehicle 32, and associates the extracted pair candidate vehicle with the vehicle dispatch request 22. Therefore, if the drop-off location is included in the business area 7 of the taxi vehicle 32, the pair candidate vehicles include an NRS vehicle 42, and the vehicle dispatch unit 172 can assign either a taxi vehicle 32 or an NRS vehicle 42 to the vehicle dispatch request 22. On the other hand, if the drop-off location is not included in the business area 7 of the taxi vehicle 32, the pair candidate vehicles do not include an NRS vehicle 42, and the vehicle dispatch unit 172 assigns a taxi vehicle 32 to the vehicle dispatch request 22, but does not assign an NRS vehicle 42.

[0108] This configuration makes it possible to prevent NRS vehicles 42 from operating outside the operating area 7 of taxi vehicles 32.

[0109] In the above description, the driving conditions are described as being equal to or less than a predetermined distance or a predetermined time. However, the driving conditions are not limited to these examples, and may be set independently for each business area 8 of the NRS vehicle 42. Furthermore, the driving conditions may be set independently for each time period during which the NRS vehicle 42 is available for business in the business area 8. Therefore, for example, the driving conditions may change depending on the time period within the same business area 8.

[0110] In the above description, the driving condition is a fixed predetermined distance or a fixed time, but the driving condition is not limited to this example and may vary based on the operating status of the taxi vehicle 32 or the NRS vehicle 42.

[0111] Here, the operating status may be the on-board rate of the NRS vehicle 42. The on-board rate of the NRS vehicle 42 indicates the proportion of the distance that the NRS vehicle 42 has traveled in an on-board state to the total distance traveled by the NRS vehicle 42. Here, an on-board vehicle refers to a state in which the user 2 is aboard. For example, when the on-board rate of the NRS vehicle 42 in the most recent hour decreases, the dispatch unit 172 increases the predetermined distance of the travel conditions to increase the probability of dispatching the NRS vehicle 42. At this time, the dispatch unit 172 may gradually increase the predetermined distance as the on-board rate of the NRS vehicle 42 decreases, or may increase the predetermined distance in stages as the on-board rate of the NRS vehicle 42 decreases.

[0112] Note that, instead of the above-described occupied rate of the NRS vehicle 42, the empty rate of the NRS vehicle 42 can also be applied as the operating status. The empty rate of the NRS vehicle 42 indicates the proportion of the distance that the NRS vehicle 42 has traveled in an empty state to the total distance traveled by the NRS vehicle 42. An empty vehicle refers to a state in which the user 2 is not aboard. For example, when the empty rate of the NRS vehicle 42 in the most recent hour increases, the dispatch unit 172 increases the predetermined distance in the driving conditions to increase the probability of dispatching the NRS vehicle 42. At this time, the dispatch unit 172 may gradually increase the predetermined distance as the empty rate of the NRS vehicle 42 increases, or may increase the predetermined distance in stages as the empty rate of the NRS vehicle 42 increases.

[0113] Furthermore, the actual vehicle time rate of the NRS vehicle 42 may be applied as the operating status. The actual vehicle time rate of the NRS vehicle 42 indicates the proportion of time during the business hours of the NRS vehicle 42 that the NRS vehicle 42 is in an actual vehicle state. For example, when the actual vehicle time rate of the NRS vehicle 42 in the most recent hour decreases, the dispatch unit 172 increases the predetermined distance of the driving conditions to increase the probability of dispatching the NRS vehicle 42. At this time, the dispatch unit 172 may gradually increase the predetermined distance as the actual vehicle time rate of the NRS vehicle 42 decreases, or may increase the predetermined distance in stages as the actual vehicle time rate of the NRS vehicle 42 decreases.

[0114] Note that, instead of the above-described actual vehicle time rate of the NRS vehicle 42, the empty vehicle time rate of the NRS vehicle 42 can also be applied as the operating status. The empty vehicle time rate of the NRS vehicle 42 indicates the percentage of time that the NRS vehicle 42 is empty during the business hours of the NRS vehicle 42. For example, when the empty vehicle time rate of the NRS vehicle 42 in the most recent hour increases, the dispatch unit 172 increases the predetermined distance in the driving conditions to increase the probability of dispatching the NRS vehicle 42. In this case, the dispatch unit 172 may gradually increase the predetermined distance as the empty vehicle time rate of the NRS vehicle 42 increases, or may increase the predetermined distance in stages as the empty vehicle time rate of the NRS vehicle 42 increases.

[0115] Furthermore, the number of times the NRS vehicle 42 is actually driven per unit time may be applied as the operating status. The number of times the NRS vehicle 42 is actually driven per unit time indicates the number of times per unit time that the NRS vehicle 42 is actually driven in response to the dispatch request 22. When the number of times the NRS vehicle 42 is actually driven decreases, the dispatch unit 172 increases the predetermined distance of the driving conditions to increase the probability of dispatching the NRS vehicle 42. At this time, the dispatch unit 172 may gradually increase the predetermined distance as the number of times the NRS vehicle 42 is actually driven decreases, or may increase the predetermined distance in stages as the number of times the NRS vehicle 42 is actually driven decreases.

[0116] Furthermore, the actual vehicle distance per unit time of the NRS vehicle 42 may be applied as the operating status. The actual vehicle distance per unit time of the NRS vehicle 42 indicates the distance per unit time that the NRS vehicle 42 is an actual vehicle. When the actual vehicle distance becomes shorter, the dispatch unit 172 increases the predetermined distance of the driving conditions to increase the probability of dispatching the NRS vehicle 42. At this time, the dispatch unit 172 may gradually increase the predetermined distance as the actual vehicle distance of the NRS vehicle 42 becomes shorter, or may increase the predetermined distance in stages as the actual vehicle distance of the NRS vehicle 42 becomes shorter.

[0117] Furthermore, the matching rate of the NRS vehicle 42 may be applied as the operating status. The matching rate of the NRS vehicle 42 indicates the rate at which the NRS vehicle 42 is allocated (matched) to the vehicle dispatch request 22 of the user 2. When the matching rate of the NRS vehicle 42 in the most recent hour becomes low, the dispatch unit 172 increases the predetermined distance of the driving conditions to increase the probability of dispatching the NRS vehicle 42. At this time, the dispatch unit 172 may gradually increase the predetermined distance as the matching rate of the NRS vehicle 42 becomes low, or may increase the predetermined distance in stages as the matching rate of the NRS vehicle 42 becomes low.

[0118] Furthermore, the ratio of the number of NRS vehicles 42 may be applied as the operation status. The ratio of the number of NRS vehicles 42 indicates the ratio of the number of NRS vehicles 42 currently operating in the operation area 8 to the number of taxi vehicles 32 currently operating in the operation area 8, and is expressed as (the number of NRS vehicles 42 currently operating in the operation area 8) / (the number of taxi vehicles 32 currently operating in the operation area 8). Note that the ratio of the number of NRS vehicles 42 may also be applied as the ratio of the number of NRS vehicles 42 currently operating in the operation area 8 to the number of NRS vehicles 42 and taxi vehicles 32 currently operating in the operation area 8. In this case, the ratio of the number of NRS vehicles 42 is expressed as (the number of NRS vehicles 42 currently operating in the operation area 8) / (the number of NRS vehicles 42 currently operating in the operation area 8 + the number of taxi vehicles 32 currently operating in the operation area 8). When the ratio of the number of NRS vehicles 42 increases, the dispatch unit 172 increases the predetermined distance of the driving conditions to increase the probability of dispatching the NRS vehicles 42. At this time, the dispatch unit 172 may gradually increase the predetermined distance as the ratio of the number of NRS vehicles 42 increases, or may increase the predetermined distance in stages as the ratio of the number of NRS vehicles 42 increases.

[0119] Furthermore, the operating income per unit time of the NRS vehicle 42 may be applied as the operating status. The operating income per unit time of the NRS vehicle 42 indicates the income associated with the operation of the NRS vehicle 42, i.e., the amount obtained by dividing the total fee for using the NRS vehicle 42 by the actual driving time. When the operating income decreases, the dispatch unit 172 increases the predetermined distance of the driving conditions to increase the probability of dispatching the NRS vehicle 42. In this case, the dispatch unit 172 may gradually increase the predetermined distance as the operating income of the NRS vehicle 42 decreases, or may increase the predetermined distance in stages as the operating income of the NRS vehicle 42 decreases.

[0120] Furthermore, the operating income ratio of the NRS vehicle 42 may be applied as the operating status. The operating income ratio of the NRS vehicle 42 indicates the ratio of the operating income of the NRS vehicle 42 currently operating in the operating area 8 to the operating income of the taxi vehicle 32 currently operating in the operating area 8, and is expressed as (operating income of the NRS vehicle 42 currently operating in the operating area 8) / (operating income of the taxi vehicle 32 currently operating in the operating area 8). Note that the operating income ratio of the NRS vehicle 42 may also be the ratio of the operating income of the NRS vehicle 42 currently operating in the operating area 8 to the operating income of the NRS vehicle 42 and the taxi vehicle 32 currently operating in the operating area 8. In this case, the operating income ratio of the NRS vehicle 42 is expressed as (operating income of the NRS vehicle 42 currently operating in the operating area 8) / (operating income of the NRS vehicle 42 currently operating in the operating area 8 + operating income of the taxi vehicle 32 currently operating in the operating area 8). When the operating income ratio decreases, the dispatch unit 172 increases the predetermined distance of the driving conditions to increase the probability of dispatching the NRS vehicle 42. At this time, the dispatch unit 172 may gradually increase the predetermined distance as the operating income ratio of the NRS vehicle 42 decreases, or may increase the predetermined distance in stages as the operating income ratio of the NRS vehicle 42 decreases.

[0121] In the present embodiment, an example has been described in which the vehicle allocation unit 172 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, vehicle number ratio, operating revenue, and operating revenue ratio. However, the present embodiment is not limited to this example. The vehicle allocation unit 172 may determine the operating status based on 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, vehicle number ratio, operating revenue, and operating revenue ratio. 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, vehicle number ratio, operating revenue, and operating revenue ratio have been described as operating statuses. However, the present embodiment is not limited to this example. Various indices capable of determining the level of the operating status of the NRS vehicle 42 can be applied.

[0122] 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 available for operation 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 manner, during the time periods when the NRS vehicle 42 is available for dispatch, user 2 may be able to input information regarding the boarding location, disembarking location, and automatic payment at his / her discretion, or user 2 may input information regarding the boarding location, disembarking location, and automatic payment in response to viewing a screen prompting input of information regarding the boarding location, disembarking location, and automatic payment, 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.

[0123] 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 of the taxi vehicle 32, 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.

[0124] 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 for the taxi vehicle 32, 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.

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

[0126] In the above-described embodiment, an example was given in which the expanded service area 9 of the NRS vehicle 42 shown by the dashed line in Fig. 14D is an area that is evenly expanded by about 5 km outward from the service area 8 of the NRS vehicle 42 shown by the dashed line in Fig. 14D, and is included in the service area 7 of the taxi vehicle 32 shown by the two-dot chain line in Fig. 14D. However, the area of ​​the expanded service area 9 may change depending on the positional relationship between the service area 8 of the NRS vehicle 42 and the service area 7 of the taxi vehicle 32.

[0127] Figure 16A is a first explanatory diagram for explaining the positional relationship of the service areas, and Figure 16B is a second explanatory diagram for explaining the positional relationship of the service areas. In both Figures 16A and 16B, the service area 8 of NRS vehicle 42 is shown by a dashed line, the expanded service area 9 of NRS vehicle 42 is shown by a dashed line, and the service area 7 of taxi vehicle 32 is shown by a dashed line. Here, the expanded service area 9 of NRS vehicle 42 is assumed to be an area that is evenly spread out about 5 km outward from the service area 8 of NRS vehicle 42.

[0128] However, as shown on the left side of Figure 16A, even if the distance between the outer edge of business area 8 and the outer edge of business area 7 is less than 5 km, expanded business area 9 does not extend outside of business area 7, so expanded business area 9 cannot be an area that is evenly extended outward by about 5 km from business area 8. Here, for areas where the distance between the outer edge of business area 8 and the outer edge of business area 7 is less than 5 km, the distance that extends outward from business area 8 is limited to, for example, 3 km, and the outer edge of expanded business area 9 overlaps with the outer edge of business area 7. In this way, business area 8 is included in expanded business area 9, and it is possible to maintain the relationship that business area 8 and expanded business area 9 are included in business area 7.

[0129] Furthermore, as shown on the left side of Figure 16B, even if part of the outer edge of business district 8 overlaps with part of the outer edge of business district 7, extended business district 9 does not extend outside of business district 7, so, as in Figure 16A, extended business district 9 cannot be an area that is evenly extended outward by about 5 km from business district 8. Here, for the area where the outer edges of business district 8 and business district 7 overlap, an area that extends outward from business district 8, i.e., extended business district 9, is not set, or the extended business district 9 is set with an extension distance of 0, and the outer edges of business district 8 and extended business district 9 overlap with the outer edges of business district 7. In this way, it is possible to maintain the relationship that business district 8 is included in extended business district 9, and business district 8 and extended business district 9 are both included in business district 7.

[0130] As shown in FIG. 14B, an NRS vehicle 42 belonging to the service area 8 can transport user 2 from a boarding location within the service area 8 to a drop-off location outside the extended service area 9, as long as the boarding location in the dispatch request 22 is within the service area 8, even if the drop-off location is outside the extended service area 9. On the other hand, as shown in FIG. 14D, an NRS vehicle 42 belonging to the service area 8 cannot transport user 2 from a boarding location outside the service area 8 to a drop-off location outside the extended service area 9, as long as the boarding location in the dispatch request 22 is outside the service area 8 and the drop-off location is outside the extended service area 9. However, these transportation modes are conditional on being within the service area 7 of the taxi vehicle 32. The NRS vehicle 42 is intended to transport user 2 short distances, and is not intended to operate outside the service area 7 of the taxi vehicle 32. 16A and 16B, an NRS vehicle 42 belonging to the service area 8 cannot transport user 2 to a drop-off location outside the service area 7 of taxi vehicle 32, regardless of whether the boarding location in the dispatch request 22 is within or outside the service area 8. Therefore, the dispatch unit 172 does not assign an NRS vehicle 42 belonging to the service area 8 to a dispatch request 22 in which the drop-off location is outside the service area 7. With this configuration, the NRS vehicle 42 can avoid operating outside the service area 7, and can operate efficiently near the service area 8 of the NRS vehicle 42.

[0131] In the above-described embodiment, the dispatch unit 172 assigns either a taxi vehicle 32 or an NRS vehicle 42 to the dispatch request 22 if the derived driving values ​​satisfy predetermined driving conditions, and assigns a taxi vehicle 32 to the dispatch request 22 but does not assign an NRS vehicle 42 if the derived driving values ​​do not satisfy the predetermined driving conditions. However, this example is not limiting, and it is sufficient that at least whether to assign an NRS vehicle 42 may be determined based on the driving values. For example, the dispatch unit 172 may assign at least an NRS vehicle 42 to the dispatch request 22 if the derived driving values ​​satisfy predetermined driving conditions, and may not assign an NRS vehicle 42 to the dispatch request 22 if the driving values ​​do not satisfy the predetermined driving conditions. With this configuration, the NRS vehicle 42 is prevented from transporting users 2 over long distances and can remain within its own business area 8 for a relatively long period of time.

[0132] Furthermore, for example, if the derived driving values ​​satisfy predetermined driving conditions, the dispatch unit 172 may not assign a taxi vehicle 32 to the dispatch request 22 but may assign an NRS vehicle 42 instead, and if the driving values ​​do not satisfy the predetermined driving conditions, the dispatch unit 172 may assign a taxi vehicle 32 to the dispatch request 22 but not an NRS vehicle 42. That is, if the driving values ​​satisfy the predetermined driving conditions, the dispatch unit 172 assigns only an NRS vehicle 42, and if the driving values ​​do not satisfy the predetermined driving conditions, the dispatch unit 172 assigns only a taxi vehicle 32. With this configuration, if the planned travel distance is less than a predetermined distance, an NRS vehicle 42 driven by an NRS driver 4 who does not hold a Class 2 driver's license for a standard vehicle or who may lack the qualifications, driving skills, and knowledge of a driver is dispatched, making it easier to accumulate knowledge and experience in a narrow business area 8. On the other hand, if the planned distance of the trip is longer than the predetermined distance, a taxi vehicle 32 with a Class 2 driver's license for a standard vehicle and with high driver qualities, driving skills, and knowledge will be dispatched, and that knowledge and experience can be utilized in the wide business area 7. In this way, it is possible to separate the vehicles to be dispatched depending on the planned distance of the trip.

[0133] Thus, the vehicle dispatch management system 1 includes a user terminal 20, a vehicle dispatch management device (e.g., a vehicle dispatch management server 60) that can communicate with the user terminal 20 via a network 6, and vehicles including a first vehicle (e.g., a taxi 32) and a second vehicle (e.g., an NRS vehicle 42) that has different dispatchability requirements from the first vehicle. The user terminal 20 includes one or more first processors, and the vehicle dispatch management device includes one or more second processors. The first processor transmits a vehicle dispatch request 22, which includes a boarding location and a disembarking location, to the vehicle dispatch management device in response to an input from a user 2. The second processor derives a driving value associated with the vehicle's travel based on the boarding location and the disembarking location. If the driving value satisfies a predetermined driving condition, the system assigns at least the second vehicle to the vehicle dispatch request 22. If the driving value does not satisfy the predetermined driving condition, the system does not assign the second vehicle to the vehicle dispatch request 22. This configuration reduces long-distance transportation for the user 2, allowing the NRS vehicle 42 to operate by staying within its own business area 8 for a relatively long period of time. In addition, NRS vehicles 42 are more likely to be dispatched in narrow business areas 8, and taxi vehicles 32 are more likely to be dispatched in wide business areas 7, making it possible to separate vehicles to be dispatched depending on the planned travel distance.

[0134] A vehicle dispatch management device (e.g., vehicle dispatch management server 60) of the present invention, which can communicate with user terminal 20 via network 6, includes one or more processors. The processor derives a driving value associated with vehicle driving based on the boarding and disembarking locations attached to a vehicle dispatch request 22 received from user terminal 20. If the driving value satisfies a predetermined driving condition, at least a second vehicle (e.g., NRS vehicle 42) is assigned to the vehicle dispatch request. If the driving value does not satisfy the predetermined driving condition, the second vehicle is not assigned to the vehicle dispatch request. This configuration reduces long-distance transportation for user 2, allowing NRS vehicle 42 to operate while remaining within its own business area 8 for a relatively long period of time. Furthermore, NRS vehicle 42 is more likely to be dispatched in a narrow business area 8, while taxi vehicle 32 is more likely to be dispatched in a wide business area 7, making it possible to segregate vehicles to be dispatched based on the planned travel distance.

[0135] Furthermore, a vehicle dispatch management device (e.g., vehicle dispatch management server 60) capable of communicating with user terminal 20 via network 6 includes one or more processors, which derive a driving value associated with vehicle driving based on the boarding and disembarking locations attached to vehicle dispatch request 22 received from user terminal 20, and if the driving value satisfies predetermined driving conditions, allocates either a first vehicle (e.g., taxi vehicle 32) or a second vehicle (e.g., NRS vehicle 42) having different dispatchability requirements from the first vehicle to vehicle dispatch request 22, and if the driving value does not satisfy the predetermined driving conditions, allocates the first vehicle but not the second vehicle to vehicle dispatch request 22. With this configuration, NRS vehicle 42 is able to operate by staying within its own business area 8 for a relatively long period of time, reducing long-distance transportation of user 2.

[0136] Furthermore, a vehicle dispatch management device (e.g., vehicle dispatch management server 60) capable of communicating with user terminal 20 via network 6 includes one or more processors, which derive a driving value associated with vehicle driving based on the boarding and disembarking locations added to the dispatch request received from user terminal 20, and if the driving value satisfies predetermined driving conditions, allocates to dispatch request 22 either a first vehicle (e.g., taxi vehicle 32) or a second vehicle (e.g., NRS vehicle 42) having different dispatchability requirements from the first vehicle, without prioritizing them, and if the driving value does not satisfy the predetermined driving conditions, allocates to dispatch request 22 the first vehicle over the second vehicle. With this configuration, NRS vehicle 42 is able to operate by staying within its own business area 8 for a relatively long period of time, reducing long-distance transportation for user 2.

[0137] Furthermore, the processor may allocate either the first vehicle or the second vehicle (e.g., NRS vehicle 42) to the dispatch request if the received drop-off location is included in the service area 7 of the first vehicle (e.g., taxi vehicle 32), and may allocate the first vehicle but not the second vehicle to the dispatch request if the received drop-off location is not included in the service area 7 of the first vehicle. With this configuration, it is possible to prevent the NRS vehicle 42 from operating outside the service area 7 of the taxi vehicle 32.

[0138] The travel value may be a planned travel distance from the boarding location to the disembarking location, and the predetermined travel condition may be a predetermined distance or less. The travel value may be a planned travel time from the boarding location to the disembarking location, and the predetermined travel condition may be a predetermined time or less. With this configuration, it is possible to appropriately suppress long-distance transportation of user 2 by NRS vehicle 42.

[0139] Furthermore, in the vehicle dispatch management method, a computer derives a driving value associated with vehicle driving based on the boarding and disembarking locations attached to the dispatch request 22 received from the user terminal 20, and if the driving value satisfies a predetermined driving condition, assigns at least one second vehicle (e.g., NRS vehicle 42) to the dispatch request 22, and if the driving value does not satisfy the predetermined driving condition, does not assign a second vehicle to the dispatch request 22. With this configuration, the NRS vehicle 42 is prevented from transporting users 2 over long distances, and can operate by remaining within its own business area 8 for a relatively long period of time. Furthermore, NRS vehicles 42 are more likely to be dispatched in narrow business areas 8, and taxi vehicles 32 are more likely to be dispatched in wide business areas 7, making it possible to segregate vehicles to be dispatched depending on the planned travel distance.

[0140] The program also causes the computer to derive a driving value associated with vehicle driving based on the boarding and disembarking locations added to the dispatch request 22 received from the user terminal 20, and if the driving value satisfies a predetermined driving condition, allocate at least one second vehicle (e.g., NRS vehicle 42) to the dispatch request 22, and if the driving value does not satisfy the predetermined driving condition, not allocate a second vehicle to the dispatch request 22. With this configuration, the NRS vehicle 42 is prevented from transporting users 2 over long distances, and can operate by remaining within its own business area 8 for a relatively long period of time. Furthermore, NRS vehicles 42 are more likely to be dispatched in narrow business areas 8, and taxi vehicles 32 are more likely to be dispatched in wide business areas 7, making it possible to segregate vehicles to be dispatched depending on the planned travel distance.

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

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

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

[0144] 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 including a first vehicle and a second vehicle having different dispatchability requirements from the first vehicle; 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 first processor: Transmitting a vehicle dispatch request to the vehicle dispatch management device, to which the boarding location and the disembarking location are added in accordance with the user's input; The second processor: deriving a travel value associated with the travel of the vehicle based on the boarding location and the disembarking location; If the driving value satisfies a predetermined driving condition, allocate at least the second vehicle to the vehicle dispatch request; If the driving value does not satisfy the predetermined driving condition, the second vehicle is not allocated to the vehicle dispatch request. 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 processor: Deriving a travel value associated with the travel of the vehicle based on the boarding location and the disembarking location added to the dispatch request received from the user terminal; If the driving value satisfies a predetermined driving condition, allocate at least a second vehicle to the vehicle dispatch request; If the driving value does not satisfy the predetermined driving condition, the second vehicle is not allocated to the vehicle dispatch request. Vehicle dispatch management device.

3. A vehicle dispatch management device capable of communicating with a user terminal via a network, one or more processors; the processor: Deriving a travel value associated with the travel of the vehicle based on the boarding location and the disembarking location added to the dispatch request received from the user terminal; If the driving value satisfies a predetermined driving condition, the vehicle dispatch request is responded to by assigning either a first vehicle or a second vehicle having different dispatch availability requirements from the first vehicle; If the driving value does not satisfy the predetermined driving condition, the first vehicle is allocated to the vehicle dispatch request, but the second vehicle is not allocated. Vehicle dispatch management device.

4. A vehicle dispatch management device capable of communicating with a user terminal via a network, one or more processors; the processor: Deriving a travel value associated with the travel of the vehicle based on the boarding location and the disembarking location added to the dispatch request received from the user terminal; If the driving value satisfies a predetermined driving condition, the first vehicle and a second vehicle having different dispatchability requirements from the first vehicle are allocated to the vehicle allocation request without any preference; If the travel value does not satisfy the predetermined travel condition, the first vehicle is allocated to the vehicle dispatch request with priority over the second vehicle. Vehicle dispatch management device.

5. The processor: If the received drop-off location is included in the service area of ​​the first vehicle, assign either the first vehicle or the second vehicle to the dispatch request; 5. The vehicle dispatch management device according to claim 3, wherein if the received drop-off location is not included in the service area of ​​the first vehicle, the first vehicle is assigned to the dispatch request, but the second vehicle is not assigned.

6. The travel value is a planned travel distance from the boarding location to the disembarking location, The vehicle dispatch management device according to claim 2 , wherein the predetermined traveling condition is that the vehicle is within a predetermined distance.

7. The travel time is a planned ride time from the boarding location to the disembarking location, The vehicle dispatch management device according to claim 2 , wherein the predetermined traveling condition is that the vehicle is within a predetermined time.

8. The computer Deriving a travel value associated with the travel of the vehicle based on the boarding location and the disembarking location added to the dispatch request received from the user terminal; If the driving value satisfies a predetermined driving condition, allocate at least a second vehicle to the vehicle dispatch request; If the driving value does not satisfy the predetermined driving condition, the second vehicle is not allocated to the vehicle dispatch request. Vehicle allocation management method.

9. On the computer, Deriving a travel value associated with the travel of the vehicle based on the boarding location and the disembarking location added to the dispatch request received from the user terminal; If the driving value satisfies a predetermined driving condition, allocate at least a second vehicle to the vehicle dispatch request; If the driving value does not satisfy the predetermined driving condition, the second vehicle is not allocated to the vehicle dispatch request. A program to make it happen.

Images