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. A first service area (service area 8) and a second service area (extended service area 9), which includes the first service area and is wider than the first service area, are defined. The processor does not dispatch a vehicle (NRS vehicle 42) belonging to the first service area to a vehicle dispatch request which is received from the user terminal and in which a pick-up location is outside the first service area and a drop-off location is outside the second service area, and dispatches the vehicle belonging to the first service area to a vehicle dispatch request which is received from the user terminal and in which the pick-up location is outside the first service area and the drop-off location is inside the second service area.SELECTED DRAWING: Figure 10

Description

[Technical Field]

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

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

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

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

[0005] In ride-sharing, operating areas are determined by the Road Transportation Act, and ride-sharing vehicles are prohibited from operating outside of those areas. Therefore, even if a ride-sharing vehicle is empty, it cannot accommodate users 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 and a vehicle dispatch management device capable of communicating with the user terminal via a network, the user terminal includes one or more first processors, and the vehicle dispatch management device includes one or more second processors, a first business area and a second business area that includes the first business area but is larger than the first business area are defined, the first processor sends a vehicle dispatch request to the vehicle dispatch management device, with a boarding location and a disembarking location added according to user input, and the second processor does not assign a vehicle belonging to the first business area to a vehicle dispatch request where the boarding location is outside the first business area and the disembarking location is outside the second business area, and assigns a vehicle belonging to the first business area to a vehicle dispatch request where the boarding location is outside the first business area and the disembarking location is within the second business area.

[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 defines a first operating area and a second operating area that includes the first operating area but is larger than the first operating area, and the processor does not assign a vehicle belonging to the first operating area to a vehicle dispatch request received from the user terminal in which the boarding location is outside the first operating area and the disembarking location is outside the second operating area, and assigns a vehicle belonging to the first operating area to a vehicle dispatch request received from the user terminal in which the boarding location is outside the first operating area and the disembarking location is within the second operating area.

[0009] A third business area is defined that includes the first business area and is larger than the first business area, and the processor may output information to the user terminal located within the third business area that identifies the vehicle located outside the first business area but within the third business area as a candidate for dispatch.

[0010] The second business area may be included in a third business area that is larger than the second business area, the third business area being an area in which a first vehicle can operate, and the first business area being an area in which a second vehicle different from the first vehicle can operate.

[0011] The first business area may be included in a third business area which is larger than the first business area, and the second business area may not be set in the area where the outer edges of the first business area and the third business area overlap.

[0012] A third operating area may be defined that includes the second operating area and is larger than the second operating area, and the processor may not assign a vehicle belonging to the first operating area to a ride-hailing request received from the user terminal where the drop-off location is outside the third operating area.

[0013] In order to solve the above problem, the vehicle dispatch management method of the present invention is such that, in response to a vehicle dispatch request received from a user terminal in which the boarding location is outside a first operating area and the disembarking location is outside a second operating area that includes the first operating area but is larger than the first operating area, the computer does not assign a vehicle belonging to the first operating area, and in response to a vehicle dispatch request received from the user terminal in which the boarding location is outside the first operating area and the disembarking location is within the second operating area, the computer assigns a vehicle belonging to the first operating area.

[0014] In order to solve the above problem, the program of the present invention causes a computer to not allocate a vehicle belonging to the first operating area to a ride request received from a user terminal in which the boarding location is outside a first operating area and the disembarking location is outside a second operating area that includes the first operating area but is larger than the first operating area, and to allocate a vehicle belonging to the first operating area to a ride request received from the user terminal in which the boarding location is outside the first operating area and the disembarking location is within the second operating area.

[0015] In order to solve the above problem, in the vehicle dispatch management system of the present invention, which includes a user terminal and a vehicle dispatch management device capable of communicating with the user terminal via a network, the user terminal includes one or more first processors, and the vehicle dispatch management device includes one or more second processors, the 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, and the second processor does not assign a vehicle belonging to the first operating area to a vehicle dispatch request where the boarding location is outside the first operating area and the disembarking location is outside the first operating area, and assigns a vehicle belonging to the first operating area to a vehicle dispatch request where the boarding location is outside the first operating area and the disembarking location is within the first operating area. [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 an explanatory diagram showing the results of matching by the dispatch unit. [Figure 10] Fig. 10A is a first explanatory diagram for explaining business areas. Fig. 10B is a second explanatory diagram for explaining business areas. Fig. 10C is a third explanatory diagram for explaining business areas. Fig. 10D is a fourth explanatory diagram for explaining business areas. [Figure 11] FIG. 11 is an explanatory diagram for explaining the processing of the dispatch unit. [Figure 12] Fig. 12A is a first explanatory diagram for explaining the operation of the user terminal control unit, and Fig. 12B is a second explanatory diagram for explaining the operation of the user terminal control unit. [Figure 13] Fig. 13A is a first explanatory diagram for explaining the positional relationship of business districts, and Fig. 13B 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 vehicle that satisfies a predetermined pairing condition from the vehicles 32a, 42b, 32c, 32d, 32e, 42f, 32g, 32h, 42i, and 42j extracted in the vehicle extraction process S4, and associates the extracted vehicle with the vehicle dispatch request 22. Here, the pairing condition is that the vehicle's allowable items conform to all of the setting items of the vehicle dispatch request 22. For example, if the vehicle attribute included in the setting items of the vehicle dispatch request 22 is "sliding door compatible," the vehicle dispatch unit 172 determines that the vehicle is "suitable" if the vehicle's allowable items include sliding doors. Furthermore, for example, if the vehicle dispatch category included in the setting items of the vehicle dispatch request 22 is "taxi vehicles 32 only," the vehicle dispatch unit 172 determines that the vehicle is "suitable" if it is a taxi vehicle 32. The vehicle allocation unit 172 determines that a vehicle does not satisfy the pairing condition if any of the allowable items of the vehicle do not match the setting items of the vehicle allocation request 22. On the other hand, if the allowable items of the vehicle match all of the setting items of the vehicle allocation request 22, the vehicle allocation unit 172 associates the vehicle with the vehicle allocation request 22 as a vehicle that satisfies the pairing condition of the vehicle allocation request 22.

[0051] (Matching process S6) The vehicle allocation unit 172 matches the vehicle allocation requests 22 with vehicles for multiple combinations of the vehicle allocation requests 22 associated with the vehicles in the pair generation process S5. In this matching process, the vehicle allocation requests 22 are matched with the vehicles so that the vehicle with the highest priority among the at least one vehicle associated with each vehicle allocation request 22 does not overlap with at least one vehicle associated with another vehicle allocation request 22. For example, the vehicle allocation unit 172 exclusively matches the vehicle with the shortest average estimated arrival time with each of the vehicle allocation requests 22a to 22d. Note that various matching algorithms can be applied as the matching algorithm between the vehicle allocation requests 22 and vehicles, and therefore detailed description thereof will be omitted in this embodiment.

[0052] 9 is an explanatory diagram showing the results of matching by the vehicle dispatch unit 172. Using a predetermined matching algorithm, the vehicle dispatch unit 172 associates vehicles 42b, 32c, 32e, 32a, 42f, 32g, and 42j with the vehicle dispatch request 22a, and exclusively determines the NRS vehicle 42b with the highest priority. Similarly, the vehicle dispatch unit 172 associates vehicles 32h, 42f, 32e, 32g, 32a, 42j, and 32c with the vehicle dispatch request 22b, and exclusively determines the taxi vehicle 32h with the highest priority. Similarly, the vehicle dispatch unit 172 associates vehicles 42i, 32e, 42f, 32g, 32c, 42j, and 32a with the vehicle dispatch request 22c, and exclusively determines the NRS vehicle 42i with the highest priority. Similarly, vehicles 32d, 32e, 32c, and 32g are associated with the vehicle allocation request 22d, and the taxi vehicle 32d with the highest priority is exclusively determined. Here, "exclusive determination" means that the highest priority vehicles 42b, 32h, 42i, and 32d associated with the vehicle allocation requests 22a to 22d are determined so that they do not overlap with each other. The vehicle allocation unit 172 then determines the highest priority vehicle 42b, 32h, 42i, or 32d associated with each of the vehicle allocation requests 22a to 22d as the vehicle to be allocated for the vehicle allocation request 22a to 22d. In this way, the vehicle allocation unit 172 matches multiple vehicle allocation requests 22 with multiple vehicles at once and determines the vehicle to be allocated for each vehicle allocation request 22. In this way, compared to matching vehicle dispatch requests 22 sequentially and individually, matching can be optimized by comprehensively determining the relative positions of multiple users 2 and multiple vehicles, enabling efficient vehicle dispatch.

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

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

[0055] If the driver cannot accept the vehicle allocation request 22 for some reason, the driver taps the "request reject" button displayed on the vehicle input device of the vehicle terminal to reject the vehicle allocation request 22, or does not tap the position corresponding to "request accept." The vehicle terminal control unit 174 waits for a predetermined time (e.g., 10 seconds) from the time the vehicle allocation target notification is sent, and if it does not receive information regarding acceptance of the vehicle allocation request 22 (acceptance response) from the vehicle terminal during the waiting time, it determines that the driver of the vehicle to be allocated has not accepted the vehicle allocation request 22. In this case, the vehicle allocation unit 172 determines the vehicle with the second highest priority among the vehicles associated with the vehicle allocation request 22 in the matching process S6 as the new vehicle to be allocated. Next, the vehicle terminal control unit 174 notifies the vehicle terminal of the other vehicle that has become the new vehicle to be allocated of information indicating that it has become the target of the vehicle allocation request 22 (vehicle allocation target notification).

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

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

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

[0059] (Vehicle operating area) 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.

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

[0061] An operating area 8 (first operating area) is defined as the geographical range of operation of the NRS vehicle 42. The operating area 8 of the NRS vehicle 42 is included in the operating area (traffic area) of the taxi vehicle 32 and is often smaller than the operating area of ​​the taxi vehicle 32. However, the operating area 8 of the NRS vehicle 42 may be equal to the operating area 7 of the taxi vehicle 32. In this case, the taxi vehicle 32 can operate outside the operating area 7 (traffic area), but as will be described later, the NRS vehicle 42 cannot operate outside the operating area 7 (traffic area). Therefore, if the operating area 8 of the NRS vehicle 42 is equal to the operating area 7 of the taxi vehicle 32, the NRS vehicle 42 cannot operate outside the operating 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 (transportation area). Furthermore, while the operation of the taxi vehicle 32 is limited by the geographical area of ​​the operating area but not by time, the operation of the NRS vehicle 42 is limited by time in addition to the geographical area of ​​the operating area. For the sake of convenience, only the operating area 8 of the NRS vehicle 42 will be mentioned here.

[0062] 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. 10A, 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.

[0063] 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. 10A, 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. 10B.

[0064] As shown in FIG. 10B , 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. 10C , even if the NRS vehicle 42 is located outside the service area 8, as long as the drop-off location is within its own service area 8, the NRS vehicle 42 is considered to be operating in the service area 8, and can transport user 2 from a pick-up location outside the service area 8 to a drop-off location within the service area 8, provided that the NRS vehicle 42 is located within the service area 7 of a taxi vehicle 32 (described later).

[0065] 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. 10C , 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.

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

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

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

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

[0070] In this way, even if the NRS vehicle 42 is located outside the service area 8, such as while returning after transporting a user 2 outside the service area 8, the NRS vehicle 42 can transport the user 2 if a new user 2 wishing to board inputs a drop-off location and that drop-off location is within the NRS vehicle's expanded service area 9. However, since the NRS vehicle 42 is premised on operating within the service area 8 to which it belongs, it is extracted as a candidate for dispatch within the service area 8, but outside the service area 8 of the NRS vehicle 42, there is no way to extract an NRS vehicle 42 belonging to the service area 8 as a candidate for dispatch.

[0071] Fig. 11 is an explanatory diagram for explaining the processing of the vehicle dispatch unit 172. Fig. 11 shows NRS vehicles 42a, 42b, and 42c that belong to the service area 8, and a user 2 who makes a vehicle dispatch request 22 outside the service area 8. In the example of Fig. 11, it is assumed that the NRS vehicle 42a is operating within the service area 8, and the NRS vehicles 42b and 42c are returning to the service area 8 from outside the service area 8. Also, for ease of explanation, it is assumed that the vehicle dispatch category is set to "taxi vehicles 32 and vehicles with requirements" (second vehicle dispatch mode) in the vehicle dispatch request.

[0072] In response to the dispatch request 22, the dispatch unit 172 of the dispatch management server 60 sets an extraction condition 24, shown by a dashed arc in FIG. 11, that the distance between the boarding location (e.g., the current location of user 2) and the current location of the vehicle must be less than a predetermined distance. In the example of FIG. 11, NRS vehicle 42a is far from user 2 and does not satisfy extraction condition 24. On the other hand, NRS vehicles 42b and 42c are close to user 2 and satisfy extraction condition 24.

[0073] At this time, since NRS vehicle 42a does not satisfy extraction condition 24, the dispatch unit 172 cannot select NRS vehicle 42a as a vehicle to be dispatched. Furthermore, since NRS vehicles 42b and 42c do not belong to the business area where user 2 is located, they are not candidates for dispatch in the business area where user 2 is located, and so the dispatch unit 172 cannot select NRS vehicles 42b and 42c as vehicles to be dispatched.

[0074] However, if an NRS vehicle 42 is not located within the operating area 8, it cannot be a candidate for dispatch, and user 2 will lose the opportunity to ride in an NRS vehicle 42 returning to the operating area 8, resulting in a decrease in vehicle utilization efficiency. Therefore, in the dispatch management system 1, even if NRS vehicles 42b and 42c belonging to the operating area 8 are located outside the operating area 8, NRS vehicles 42b and 42c are considered as candidates for dispatch, and one vehicle to be dispatched is identified through matching.

[0075] Here, if the range in which the NRS vehicle 42 is a candidate for dispatch is expanded beyond the service area 8 indefinitely, the following problem arises. Ride sharing is originally intended to transport users 2 over short distances. Therefore, as described above, the service area 8 of the NRS vehicle 42 is included in the service area 7 (third service area) of the taxi vehicle 32 shown by the two-dot chain line in FIG. 11 and is often smaller than the service area 7 of the taxi vehicle 32. Similarly, the extended service area 9 of the NRS vehicle 42 shown by the one-dot chain line in FIG. 11 is an area expanded outward from the service area 8 of the NRS vehicle 42 shown by the solid line in FIG. 11, but is included in the service area 7 (traffic area) of the taxi vehicle 32 shown by the two-dot chain line in FIG. 11. Therefore, the size of the service area has the relationship of 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.

[0076] Therefore, in the vehicle dispatch management system 1, when NRS vehicles 42b, 42c belonging to the business area 8 are located outside the business area 8, if their location is within the business area 7 of the taxi vehicle 32, the NRS vehicles 42b, 42c are candidates for dispatch, provided that the drop-off point is within their own extended business area 9 (return allocation condition).

[0077] Specifically, even if an NRS vehicle 42 is located outside the service area 8, if its location is within the service area 7 of the taxi vehicle 32 and the extraction condition 24 is satisfied, the dispatch unit 172 extracts the NRS vehicle 42 in the vehicle extraction process S4. In the example of FIG. 11, NRS vehicles 42b and 42c are located outside the service area 8 but within the service area 7 of the taxi vehicle 32, and satisfy the extraction condition 24 that the distance between the boarding location for user 2's dispatch request 22 (e.g., user 2's current location) and the vehicle's current location is less than a predetermined distance. Therefore, the dispatch unit 172 extracts at least NRS vehicles 42b and 42c as dispatch candidates. The user terminal control unit 170 displays the extracted NRS vehicles 42b and 42c on the display device 124 of the user terminal 20.

[0078] 12A is a first explanatory diagram illustrating the operation of the user terminal control unit 170. In response to an operation by user 2, the vehicle allocation request unit 180 of the user terminal 20 launches a user application for making a vehicle allocation request 22. As a result, the user terminal control unit 170 of the vehicle allocation management server 60 causes the display device 124 of the user terminal 20 to display a map 210 of a predetermined range including the location of the user terminal 20, the location 212 of the user terminal 20, and NRS vehicles 42b and 42c located near the user terminal 20 (information indicating that the vehicles are candidates for allocation), as shown in FIG. 12A. User 2 can visually confirm on the display device 124 that NRS vehicles 42b and 42c are located nearby and can understand that, according to the vehicle allocation request 22, vehicles may be allocated quickly. However, even if the display device 124 displays NRS vehicles 42b, 42c located outside the service area 8, the NRS vehicles 42b, 42c will not be dispatched unless the user 2 inputs at least the boarding location and disembarking location in the dispatch request 22. Therefore, the user terminal control unit 170 causes the display device 124 of the user terminal 20 to display an image 216 requesting input of the boarding location and disembarking location.

[0079] Fig. 12B is a second explanatory diagram for explaining the operation of the user terminal control unit 170. Assume that user 2 inputs a boarding location into the boarding location text box 216a and a disembarking location into the disembarking location text box 216b of image 216 in Fig. 12A via the input device 126. Once the boarding location is input, a vehicle can be dispatched, so the user terminal control unit 170 causes image 218 including a "vehicle dispatch request" switch 218a to be displayed on the display device 124 of the user terminal 20, as shown in Fig. 12B. User 2 then operates the "vehicle dispatch request" switch 218a to request a vehicle dispatch.

[0080] Here, it is assumed that a location outside the service area 8 is input as the boarding location. Therefore, if the drop-off location input by the user 2 is within the expanded service area 9 (if the return allocation condition is satisfied), the dispatch unit 172 can select the NRS vehicles 42b and 42c as candidates for dispatch.

[0081] Specifically, in the pair generation process S5, if the drop-off location entered by user 2 is within the expanded service area 9 and the NRS vehicles 42b and 42c extracted in the vehicle extraction process S4 satisfy the pairing conditions, the vehicle allocation unit 172 matches the vehicle allocation request 22 with the NRS vehicles 42b and 42c. In the matching process S6, the vehicle allocation unit 172 matches the vehicle allocation request 22 with multiple combinations of the vehicle allocation request 22 matched in the pair generation process S5 with multiple vehicles including the NRS vehicles 42b and 42c. In this way, the NRS vehicles 42b and 42c can be vehicles to be allocated on the condition that they are located outside the service area 8 but within the service area 7 of the taxi vehicle 32. In this way, the vehicle allocation management server 60 can target the NRS vehicles 42b and 42c that are close to user 2 as vehicles to be allocated in response to the vehicle allocation request from user 2.

[0082] On the other hand, even if user 2 inputs a boarding location and a drop-off location, if NRS vehicles 42b and 42c are located outside service area 8 and the drop-off location input by user 2 is outside expanded service area 9, dispatch unit 172 will not consider NRS vehicles 42b and 42c as candidates for dispatch. Therefore, even if NRS vehicles 42b and 42c are displayed on display device 124 of user terminal 20, NRS vehicles 42b and 42c will not be dispatched because they do not satisfy the return allocation conditions. In this way, it is possible to prevent out-of-service operations as described using FIG. 10D.

[0083] In the above example, when user 2 inputs the boarding and disembarking locations, the user terminal control unit 170 displays an image 218 including a "Request a ride" switch 218a on the display device 124 of the user terminal 20, while maintaining the display of NRS vehicles 42b and 42c located outside the service area 8, as shown in FIG. 12B . However, the present invention is not limited to this example. Since the user terminal control unit 170 can determine whether the return allocation conditions are met when user 2 inputs the boarding and disembarking locations, the NRS vehicles 42b and 42c that do not meet the return allocation conditions may be deleted from the display device 124. This configuration prevents NRS vehicles 42b and 42c that cannot be allocated from continuing to be displayed on the display device 124, thereby preventing user 2 from feeling suspicious.

[0084] With this configuration, even in a situation where there is a shortage of vehicles near user 2 and a vehicle cannot be dispatched immediately, it may be possible to dispatch an NRS vehicle 42 that does not belong to the operating area where user 2 is located but does belong to operating area 8, increasing the possibility that user 2 will be able to board an NRS vehicle 42 quickly. In this way, by expanding the scope of vehicles to be dispatched to NRS vehicles 42 that belong to operating area 8, the vehicle dispatch management system 1 enables efficient vehicle dispatch.

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

[0086] 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, 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.

[0087] Here, an example has been given in which the operating hours differ based on the operating area 8 of the NRS vehicle 42, but this is not the only example. From a different perspective, it can also be interpreted that the operating area 8 of the NRS vehicle 42 differs based on the operating hours. For example, within the same operating area 7 of the taxi vehicle 32, the first operating area 8 of the NRS vehicle 42 that is operating during a first time period may be different from the second operating area 8 of the NRS vehicle 42 that is operating during a second time period. Furthermore, within the first operating area 7 of the taxi vehicle 32, the first operating area 8 of the NRS vehicle 42 that is operating during a first time period may be different from the second operating area 8 of the NRS vehicle 42 that is operating during a second time period within the second operating area 7 of the taxi vehicle 32.

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

[0089] 11 and 12, an example was described in which the dispatch unit 172 extracts NRS vehicles 42b and 42c that are located outside the service area 8 but within the service area 7 of the taxi vehicle 32 and satisfy the extraction condition 24 for the dispatch request 22 from the user 2 as dispatch candidates, and the user terminal control unit 170 displays them on the display device 124 of the user terminal 20 as dispatch candidates. However, the example is not limited to this. The dispatch unit 172 may extract such NRS vehicles 42b and 42c as dispatch candidates, but the user terminal control unit 170 may not display them on the display device 124 of the user terminal 20 as dispatch candidates. In other words, although the NRS vehicles 42b and 42c are candidates for matching within the dispatch management server 60, the user 2 is not notified that they are candidates for matching, and is notified only when dispatch is confirmed. This configuration can avoid the following events. For example, suppose that user 2 makes a vehicle dispatch request 22 specifying a drop-off location outside the expanded service area 9 of NRS vehicles 42b and 42c. In this case, NRS vehicles 42b and 42c located outside service area 8 do not satisfy the return allocation condition, and therefore are not eligible vehicles for dispatch in response to vehicle dispatch request 22. If NRS vehicles 42b and 42c, which cannot be eligible vehicles for dispatch, are displayed on display device 124 of user terminal 20, user 2 may develop a sense of distrust, thinking that NRS vehicles 42b and 42c are nearby but are not being dispatched. In this case, by not displaying NRS vehicles 42b and 42c on display device 124 of user terminal 20 until dispatch is confirmed, it is possible to prevent user 2 from developing a sense of distrust.

[0090] Furthermore, 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. 11, 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 solid line in Fig. 11, and is included in the service area 7 of the taxi vehicle 32, shown by the dashed line in Fig. 11. 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.

[0091] Figure 13A is a first explanatory diagram for explaining the positional relationship of the service areas, and Figure 13B is a second explanatory diagram for explaining the positional relationship of the service areas. In both Figures 13A and 13B, the service area 8 of NRS vehicle 42 is shown by a solid 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.

[0092] However, as shown on the left side of Figure 13A, 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.

[0093] Furthermore, as shown on the left side of Figure 13B, 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 13A, extended business district 9 cannot be an area that is an even extension of business district 8 by about 5 km. 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 extension distance is set to 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.

[0094] As shown in FIG. 10B, 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, if 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. 10D, 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, if 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. 13A and 13B, 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.

[0095] In this way, the vehicle dispatch management system 1 comprises a user terminal 20 and a vehicle dispatch management device (e.g., a vehicle dispatch management server 60) capable of communicating with the user terminal 20 via a network 6, the user terminal 20 comprising one or more first processors, the vehicle dispatch management device comprising one or more second processors, a first business area (e.g., business area 8 of NRS vehicle 42) and a second business area (e.g., extended business area 9 of NRS vehicle 42) including the first business area but larger than the first business area are defined, the first processor sends a vehicle dispatch request 22 to the vehicle dispatch management device with a boarding location and a disembarking location added in accordance with user input, and the second processor does not assign a vehicle (e.g., NRS vehicle 42) belonging to the first business area to a vehicle dispatch request 22 whose boarding location is outside the first business area and whose disembarking location is outside the second business area, and assigns a vehicle belonging to the first business area to a vehicle dispatch request 22 whose boarding location is outside the first business area and whose disembarking location is within the second business area. This configuration enables efficient dispatch of NRS vehicles 42. Furthermore, by expanding the drop-off location, which is a dispatch requirement, from the first operating area to a second operating area near the first operating area, it becomes possible to improve the dispatch efficiency of NRS vehicles 42.

[0096] 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, and defines a first service area (e.g., service area 8 of NRS vehicle 42) and a second service area (e.g., extended service area 9 of NRS vehicle 42) that includes the first service area but is larger than the first service area. The processor does not assign a vehicle (e.g., NRS vehicle 42) belonging to the first service area to a dispatch request 22 received from user terminal 20 in which the boarding location is outside the first service area and the disembarking location is outside the second service area, but assigns a vehicle belonging to the first service area to a dispatch request 22 received from user terminal 20 in which the boarding location is outside the first service area and the disembarking location is within the second service area. This configuration enables efficient dispatch of NRS vehicles 42. Furthermore, by expanding the disembarking location, which is a requirement for dispatchability, from the first service area to a second service area nearby the first service area, it becomes possible to improve the dispatch efficiency of NRS vehicles 42.

[0097] Furthermore, a third service area (e.g., service area 7 of taxi vehicle 32) that is wider than and includes the first service area (e.g., service area 8 of NRS vehicle 42) may be defined, and the processor may output information indicating that vehicles located outside the first service area but within the third service area are candidates for dispatch (e.g., NRS vehicles 42b, 42c displayed on display device 124 of user terminal 20) to user terminal 20 located within the third service area. With this configuration, user 2 can visually confirm on display device 124 that a vehicle is located nearby, and by executing dispatch request 22, user 2 can understand that a vehicle can be dispatched quickly.

[0098] The second service area (e.g., expanded service area 9 of NRS vehicle 42) may be included in a third service area (e.g., service area 7 of taxi vehicle 32) that is larger than the second service area, and the third service area may be an area in which a first vehicle (e.g., taxi vehicle 32) can operate, and the first service area may be an area in which a second vehicle (e.g., NRS vehicle 42) different from the first vehicle can operate. With this configuration, the size of the service area may be in the relationship of first service area < second service area ≦ third service area, and the locations of the service areas may be in the relationship of first service area being included in the second service area, and first service area and second service area being included in the third service area.

[0099] The first operating area (e.g., operating area 8 of NRS vehicle 42) may be included in a third operating area (e.g., operating area 7 of taxi vehicle 32) that is larger than the first operating area, and a second operating area (e.g., expanded operating area 9 of NRS vehicle 42) may not be set in the area where the outer edges of the first operating area and the third operating area overlap. With this configuration, it is possible to maintain the relationship in which the first operating area, which is operating area 8 of NRS vehicle 42, is included in the second operating area, and the first operating area and the second operating area are included in the third operating area, which is operating area 7 of taxi vehicle 32.

[0100] A third service area (e.g., service area 7 of taxi vehicle 32) is defined that includes a second service area (e.g., expanded service area 9 of NRS vehicle 42) and is larger than the second service area, and the processor may not assign a vehicle belonging to the first service area to a dispatch request 22 received from user terminal 20 in which the drop-off location is outside the third service area. With this configuration, NRS vehicle 42 can avoid operating outside service area 7, and can operate efficiently near service area 8 of NRS vehicle 42.

[0101] In addition, in the vehicle dispatch management method, the computer does not assign a vehicle (e.g., NRS vehicle 42) belonging to the first service area to a dispatch request 22 received from a user terminal 20 in which the boarding location is outside the first service area (e.g., service area 8 of NRS vehicle 42) and the disembarking location is outside a second service area (e.g., extended service area 9 of NRS vehicle 42) that includes the first service area but is larger than the first service area, but assigns a vehicle belonging to the first service area to a dispatch request 22 received from a user terminal 20 in which the boarding location is outside the first service area and the disembarking location is within the second service area. This configuration enables efficient dispatch of NRS vehicles 42. Furthermore, by not limiting the disembarking location, which is a requirement for dispatchability, to the first service area but expanding it to a second service area near the first service area, it becomes possible to improve the dispatch efficiency of NRS vehicles 42.

[0102] The program also causes the computer to execute the following: not to allocate a vehicle (e.g., NRS vehicle 42) belonging to the first operating area in response to a dispatch request 22 received from the user terminal 20 in which the boarding location is outside the first operating area (e.g., operating area 8 of NRS vehicle 42) and the disembarking location is outside the second operating area (e.g., expanded operating area 9 of NRS vehicle 42) that includes the first operating area but is larger than the first operating area; and to allocate a vehicle belonging to the first operating area in response to a dispatch request 22 received from the user terminal 20 in which the boarding location is outside the first operating area and the disembarking location is within the second operating area. This configuration enables efficient dispatch of NRS vehicles 42. Furthermore, by expanding the disembarking location, which is a requirement for dispatchability, from the first operating area to a second operating area nearby the first operating area, it becomes possible to improve the dispatch efficiency of NRS vehicles 42.

[0103] The vehicle dispatch management system 1 also includes a user terminal 20 and a vehicle dispatch management device (e.g., vehicle dispatch management server 60) capable of communicating with the user terminal 20 via network 6, the user terminal 20 including one or more first processors, the vehicle dispatch management device including one or more second processors, the first processor transmitting a vehicle dispatch request 22 with a boarding location and a disembarking location added in accordance with a user's input to the vehicle dispatch management device, the second processor not allocating a vehicle (e.g., NRS vehicle 42) belonging to the first operating area to a vehicle dispatch request 22 with a boarding location outside the first operating area (e.g., operating area 8 of NRS vehicle 42) and a disembarking location outside the first operating area, and allocating a vehicle belonging to the first operating area to a vehicle dispatch request 22 with a boarding location outside the first operating area and a disembarking location within the first operating area. This configuration enables efficient dispatch of NRS vehicles 42.

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

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

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

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

Claims

1. A user terminal; a vehicle dispatch management device capable of communicating with the user terminal via a network; A vehicle dispatch management system comprising: The user terminal one or more first processors; The vehicle dispatch management device one or more second processors; A first business area and a second business area that includes the first business area and is larger than the first business area are defined; 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: Do not allocate a vehicle belonging to the first operating area to a vehicle dispatch request in which the boarding location is outside the first operating area and the disembarking location is outside the second operating area, Allocating a vehicle belonging to the first operating area in response to a vehicle dispatch request in which the boarding location is outside the first operating area and the disembarking location is within the second operating area. Vehicle dispatch management system.

2. A vehicle dispatch management device capable of communicating with a user terminal via a network, one or more processors; A first business area and a second business area that includes the first business area and is larger than the first business area are defined; the processor: not assigning a vehicle belonging to the first operating area to a vehicle dispatch request received from the user terminal in which the boarding location is outside the first operating area and the disembarking location is outside the second operating area; Allocating a vehicle belonging to the first operating area in response to a vehicle dispatch request received from the user terminal, in which the boarding location is outside the first operating area and the disembarking location is within the second operating area. Vehicle dispatch management device.

3. A third business area is defined that includes the first business area and is wider than the first business area; The processor: outputting, to the user terminal located within the third service area, information that identifies the vehicle located outside the first service area and within the third service area as a candidate for dispatch; The vehicle allocation management device according to claim 2.

4. The second business area is included in a third business area that is larger than the second business area, the third operating area is an area in which the first vehicle can operate, The first operating area is an area in which a second vehicle different from the first vehicle can operate. The vehicle allocation management device according to claim 2.

5. The first business area is included in a third business area that is larger than the first business area, The second business area is not set in an area where the outer edge of the first business area and the outer edge of the third business area overlap. The vehicle allocation management device according to claim 2.

6. a third business area is defined that includes the second business area and is wider than the second business area; The processor: not assigning a vehicle belonging to the first operating area to a vehicle dispatch request received from the user terminal in which the drop-off location is outside the third operating area; The vehicle allocation management device according to claim 2.

7. The computer In response to a vehicle dispatch request received from a user terminal in which the boarding location is outside a first operating area and the disembarking location is outside a second operating area that includes the first operating area and is larger than the first operating area, a vehicle belonging to the first operating area is not allocated; Allocating a vehicle belonging to the first operating area in response to a vehicle dispatch request received from the user terminal, in which the boarding location is outside the first operating area and the disembarking location is within the second operating area. Vehicle allocation management method.

8. On the computer, In response to a vehicle dispatch request received from a user terminal in which the boarding location is outside a first operating area and the disembarking location is outside a second operating area that includes the first operating area and is larger than the first operating area, a vehicle belonging to the first operating area is not allocated; Allocating a vehicle belonging to the first operating area in response to a vehicle dispatch request received from the user terminal, in which the boarding location is outside the first operating area and the disembarking location is within the second operating area. A program to make it happen.

9. A user terminal; a vehicle dispatch management device capable of communicating with the user terminal via a network; A vehicle dispatch management system comprising: The user terminal one or more first processors; The vehicle dispatch management device one or more second processors; The 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: Do not allocate a vehicle belonging to the first operating area to a vehicle dispatch request in which the boarding location is outside the first operating area and the disembarking location is outside the first operating area, Allocating a vehicle belonging to the first operating area in response to a vehicle dispatch request in which the boarding location is outside the first operating area and the disembarking location is within the first operating area. Vehicle dispatch management system.

Images