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

Abstract

To provide a vehicle dispatch management system that is kind to ordinary drivers.SOLUTION: A vehicle dispatch management system 1 comprises a vehicle terminal and a vehicle dispatch management apparatus. A second processor of the vehicle dispatch management apparatus is configured to execute: receiving an input of a vehicle dispatch request having a plurality of setting items including a pick-up location and a drop-off location; and transmitting, to the vehicle terminal, at least some of the plurality of setting items of the vehicle dispatch request, including at least the pick-up location and the drop-off location. A first processor of the vehicle terminal is configured to execute: displaying, on a vehicle display device, a first image including an arrival button after acceptance of a vehicle dispatch target notification corresponding to the vehicle dispatch request and before arrival at the pick-up location; and displaying, on the vehicle display device, a second image 200 including a switching button B2 that enables displaying the pick-up location on the vehicle display device when the arrival button is pressed.SELECTED DRAWING: Figure 12

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

[0003] Recently, the shortage of taxi drivers has become a serious problem in some regions. As a result, there are regions 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 general drivers use their own cars to transport users for a fee, is progressing. For example, Patent Document 2 mentions such a service. [Prior art documents] [Patent documents]

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

[0005] In a ride-sharing environment, there are multiple driver types, including taxi drivers with traditional Class 2 driver's licenses and general drivers with only Class 1 driver's licenses. Therefore, vehicle dispatch management companies may manage multiple driver types.

[0006] A general driver may have less experience than a taxi driver, and therefore may not be familiar with operating the vehicle applications used in the course of their work.

[0007] In view of the above, an object of the present invention is to provide a vehicle dispatch management system that is user-friendly for general drivers. Another object of the present invention is to provide a related vehicle dispatch management device, vehicle dispatch management method, and program. [Means for solving the problem]

[0008] In order to solve the above problem, a vehicle dispatch management system according to one embodiment of the present invention comprises a vehicle terminal used by a driver and a vehicle dispatch management device capable of communicating with the vehicle terminal via a network, wherein the vehicle terminal includes a first processor and a vehicle display device, and the vehicle dispatch management device includes a second processor, wherein the second processor is configured to: accept input of a vehicle dispatch request having a plurality of setting items including a boarding location and a disembarking location; and transmit at least some of the plurality of setting items of the vehicle dispatch request, including at least the boarding location and the disembarking location, to the vehicle terminal; and wherein the first processor is configured to: display a first image on the vehicle display device after acceptance of the dispatch target notification corresponding to the vehicle dispatch request and before arrival at the boarding location, the first image including an arrival button for inputting that the vehicle has arrived at the boarding location; and display a second image on the vehicle display device when the arrival button is pressed, the second image including a switch button that enables the boarding location to be displayed on the vehicle display device.

[0009] The first processor may be configured to, when the current arrival button is pressed, display a second image including the switching button and the current location of the vehicle on the vehicle display device.

[0010] The first image may further include a real vehicle button for inputting that the user has boarded the vehicle, and the first processor may be configured to display the second image on the vehicle display device when at least one of the real vehicle button and the current arrival button is pressed.

[0011] The first processor may be configured to, when the actual vehicle button is pressed, display, on the vehicle display device, a second image including the switching button and the disembarkation location.

[0012] Another aspect of the present invention is a vehicle terminal capable of communicating with a vehicle dispatch management device via a network, comprising a processor and a vehicle display device, wherein the processor is configured to receive from the vehicle dispatch management device at least some of the multiple setting items of a vehicle dispatch request input to the vehicle dispatch management device, including at least the boarding location and the disembarking location; display a first image on the vehicle display device, including an arrival button for inputting that the vehicle has arrived at the boarding location after acceptance of the dispatch target notification corresponding to the vehicle dispatch request and before arrival at the boarding location; and display a second image on the vehicle display device, including a switch button that enables the boarding location to be displayed on the vehicle display device when the arrival button is pressed.

[0013] Yet another aspect of the present invention is a vehicle dispatch management method executed by a computer, comprising: receiving from a vehicle dispatch management device at least some of a plurality of setting items of a vehicle dispatch request input into the vehicle dispatch management device, including at least a boarding location and a disembarking location; displaying a first image on a vehicle display device after accepting a vehicle dispatch target notification corresponding to the vehicle dispatch request and before arriving at the boarding location, the first image including an arrival button for inputting that the vehicle has arrived at the boarding location; and displaying a second image on the vehicle display device when the arrival button is pressed, the second image including a switch button that enables the boarding location to be displayed on the vehicle display device.

[0014] Yet another aspect of the present invention is a program executed by a computer, which causes the computer to receive from a vehicle dispatch management device at least some of the setting items of a vehicle dispatch request input to the vehicle dispatch management device, including at least the boarding location and disembarking location; display on the vehicle display device a first image including an arrival button for inputting that the vehicle has arrived at the boarding location after acceptance of the dispatch target notification corresponding to the vehicle dispatch request and before arrival at the boarding location; and display on the vehicle display device a second image including a switch button that enables the boarding location to be displayed on the vehicle display device when the arrival button is pressed.

[0015] Yet another aspect of the present invention is a vehicle dispatch management system comprising: a vehicle terminal used by a driver; and a vehicle dispatch management device capable of communicating with the vehicle terminal via a network, wherein the vehicle terminal includes a first processor and a vehicle display device, and the vehicle dispatch management device includes a second processor, wherein the second processor is configured to accept input of a vehicle dispatch request having a plurality of setting items including a boarding location and a disembarking location, and to transmit at least some of the plurality of setting items of the vehicle dispatch request, including at least the boarding location and the disembarking location, to the vehicle terminal, and wherein the first processor is configured to display a first image on the vehicle display device after accepting the dispatch target notification corresponding to the vehicle dispatch request and before arriving at the boarding location, the first image including a real vehicle button for inputting that the user has boarded the vehicle, and to display a second image on the vehicle display device when the real vehicle button is pressed, the second image including a switch button that enables the boarding location to be displayed on the vehicle display device.

[0016] The first processor may be configured to, when the actual vehicle button is pressed, display a second image including a switching button and a disembarkation location on the vehicle display device.

[0017] The first image may further include an arrival button for inputting that the vehicle has arrived at the boarding location, and the first processor may be configured to display the second image on the vehicle display device when at least one of the actual vehicle button and the arrival button is pressed.

[0018] The first processor may be configured to, when the current arrival button is pressed, display a second image including a switching button and the current position of the vehicle on the vehicle display device.

[0019] Yet another aspect of the present invention is a vehicle terminal capable of communicating with a vehicle dispatch management device via a network, comprising a processor and a vehicle display device, wherein the processor is configured to receive from the vehicle dispatch management device at least some of the setting items of a vehicle dispatch request input to the vehicle dispatch management device, including at least a boarding location and a disembarking location; display a first image on the vehicle display device, including a real vehicle button for inputting that the user has boarded a vehicle after accepting the dispatch target notification corresponding to the vehicle dispatch request and before arriving at the boarding location; and display a second image on the vehicle display device, including a switch button that enables the boarding location to be displayed on the vehicle display device when the real vehicle button is pressed.

[0020] Yet another aspect of the present invention is a vehicle dispatch management method executed by a computer, comprising: receiving from a vehicle dispatch management device at least some of a plurality of setting items of a vehicle dispatch request input into the vehicle dispatch management device, including at least a boarding location and a disembarking location; displaying a first image on a vehicle display device, including a real vehicle button for inputting that the user has boarded a vehicle after accepting the dispatch target notification corresponding to the vehicle dispatch request and before arriving at the boarding location; and displaying a second image on the vehicle display device, including a switch button that enables the boarding location to be displayed on the vehicle display device when the real vehicle button is pressed.

[0021] Yet another aspect of the present invention is a program executed by a computer, which causes the computer to receive from a vehicle dispatch management device at least some of the setting items of a vehicle dispatch request input to the vehicle dispatch management device, including at least the boarding location and the disembarking location; display on the vehicle display device a first image including a real vehicle button for inputting that the user has boarded the vehicle after accepting the dispatch target notification corresponding to the vehicle dispatch request and before arriving at the boarding location; and display on the vehicle display device a second image including a switch button that enables the boarding location to be displayed on the vehicle display device when the real vehicle button is pressed. [Effects of the Invention]

[0022] According to the present invention, it is possible to provide a vehicle dispatch management system that is friendly to ordinary drivers. [Brief explanation of the drawings]

[0023] [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 performed 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. 10 is an example of a first image displayed on the vehicle terminal used by the driver. [Figure 11] FIG. 11 shows another example of the first image displayed on the vehicle terminal used by the driver. [Figure 12] FIG. 12 is an example of a second image displayed on the vehicle terminal used by the driver. [Figure 13] FIG. 13 shows another example of the second image displayed on the vehicle terminal used by the driver. [Figure 14] FIG. 14 is an example of the third image displayed on the vehicle terminal used by the driver. [Figure 15] FIG. 15 is another example of the third image displayed on the vehicle terminal used by the driver. DETAILED DESCRIPTION OF THE INVENTION

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

[0025] (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 (vehicle terminals) 30, a plurality of taxi vehicles 32, a plurality of NRS terminals (vehicle terminals) 40, a plurality of NRS vehicles 42, one or more business operator servers 50, and one or more vehicle dispatch management servers (vehicle dispatch management devices) 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.

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

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

[0028] Returning to FIG. 1, 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).

[0029] 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 consent to the dispatch target notification. 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).

[0030] Returning to FIG. 1, 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 this is not limited to this example, and the taxi vehicle 32 may also include, for example, a motorcycle (bike taxi) or the like as long as it is a vehicle capable of transporting people.

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

[0032] 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 consent to the dispatch notification. The storage device 148 is composed of storage means such as an HDD, SD memory, or SSD. The NRS terminal 40 can acquire its own position on a map through location identification means such as GPS.

[0033] Returning to FIG. 1 , 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 the NRS driver 4, the NRS vehicle 42, and the NRS terminal 40. Note that the NRS driver 4 cannot engage in so-called patrol business, which is to search for users 2 who wish 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.

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

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

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

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

[0038] FIG. 6 is a block diagram illustrating the configuration of the vehicle dispatch management server 60. The vehicle dispatch management server 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 includes 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.

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

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

[0041] (Login process S1) When a driver starts a shift, he logs in to the vehicle application. The vehicle application installed in the taxi terminal 30 and the vehicle application installed in the NRS terminal 40 may be different from each other, may be the same as each other, or may have similar functions. In this embodiment, the vehicle application installed in the taxi terminal 30 and the vehicle application installed in the NRS terminal 40 have similar functions.

[0042] For example, login authentication is performed between the vehicle terminal and the vehicle dispatch management server 60. For example, a predetermined login ID and password may be used for login authentication. Alternatively, biometric authentication such as face authentication or iris authentication may be used for login authentication. The driver inputs predetermined information required for login authentication into the vehicle terminal. In the present disclosure, information input for login, such as a login ID, password, and an image of a face or iris, may also be simply referred to as "login information."

[0043] (Login information transmission process S2) The vehicle terminal transmits the login information entered in the login process S1 to the vehicle dispatch management server 60.

[0044] (Login authentication process S3) The vehicle dispatch management server 60 determines whether the driver is a driver registered with the taxi company based on the login information entered in the login process S1. Specifically, the storage device 164 of the vehicle dispatch management server 60 stores identification information for each of the multiple drivers registered with the taxi company in association with the information for each of the multiple drivers. For example, the identification information includes the login information described above. For example, the driver information includes the driver's name, age, gender, and driver type (described later), etc.

[0045] The vehicle dispatch management server 60 searches the storage device 164 for login information that matches the login information received from the vehicle terminal. If matching login information is found, the vehicle dispatch management server 60 determines that the driver having the login information entered in the login process S1 is one of multiple drivers registered with the taxi business operator.

[0046] In this embodiment, drivers are classified into one of a plurality of driver types. The storage device 164 stores the driver type of each driver in association with the login information of each driver. The vehicle dispatch management server 60 reads from the storage device 164 the driver type associated with the login information that matches the login information received from the vehicle terminal.

[0047] In this embodiment, the multiple driver types include at least a taxi driver 3 and an NRS driver 4. In addition, there are drivers who have a Class 2 driver's license for a regular vehicle but are not regularly employed as taxi drivers 3, and who, for example, rent vehicles from taxi companies to transport users 2 (hereinafter, these may also be referred to as special crews). The multiple driver types may include a driver type for identifying such drivers. The multiple driver types are not limited to these and may further include other driver types.

[0048] (Result transmission process S4) The vehicle dispatch management server 60 transmits the result of the login authentication to the vehicle terminal. Furthermore, if the login authentication is successful, the vehicle dispatch management server 60 transmits information including the read driver type to the vehicle terminal. This completes the driver's login to the vehicle application. Therefore, the vehicle terminal can grasp the driver type of the driver currently using the vehicle terminal. In another embodiment, when login is performed at the NRS terminal 40, it may be determined that the user is not a taxi driver 3. Furthermore, in another embodiment, when login information as a special crew member is entered at the taxi terminal 30, it may be determined that the user is a special crew member rather than a taxi driver 3.

[0049] (Vehicle dispatch request processing S5) 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.

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

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

[0052] 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 automatic payment from the user 2, 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 driver needs to input the drop-off location and information regarding automatic payment as a requirement for dispatchability.

[0053] 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. As described above, even drivers who hold Class 2 driver's licenses for standard vehicles are not regularly employed as taxi drivers 3. For example, there are special crews who rent vehicles from taxi companies to transport users 2. Such special crews often vary in their driver qualifications, driving skills, knowledge, etc. Note that when dispatching a special vehicle (hereinafter referred to as a "special vehicle") driven by a special crew, user 2 must also enter information regarding the drop-off location and automatic payment, just as with the NRS vehicle 42. Herein, vehicles with different dispatch requirements from taxi vehicles 32, including NRS vehicles 42 and special vehicles, may be simply referred to as "vehicles with requirements." Because driver qualifications, etc. vary depending on the vehicle, some users 2 may request a taxi vehicle 32 driven by a 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.

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

[0055] (Dispatch request accumulation process S6) 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.

[0056] (Vehicle dispatch request extraction process S7) 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 S7 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 S7 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.

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

[0058] (Vehicle extraction process S8) 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 S7 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 arrival time 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 arrival time at the boarding location is within a predetermined time (e.g., 10 minutes), etc. 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.

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

[0060] The vehicle allocation unit 172 sets extraction conditions for each of the vehicle allocation requests extracted in the vehicle allocation request extraction process S7, 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.

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

[0062] (Pair generation process S9) Returning to FIG. 7 , for each vehicle dispatch request 22 extracted in the vehicle dispatch request extraction process S7, 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 S8, 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.

[0063] (Matching process S10) 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 S9. In this matching process, the vehicle allocation requests 22 are matched with the vehicles such that the vehicle with the highest priority among the at least one vehicle associated with each vehicle allocation request 22 does not overlap with at least one vehicle associated with another vehicle allocation request 22. For example, the vehicle allocation unit 172 exclusively matches the vehicle with the shortest average estimated arrival time with each of the vehicle allocation requests 22a to 22d. Note that various existing matching algorithms can be applied as the matching algorithm between the vehicle allocation requests 22 and vehicles, and therefore detailed description thereof will be omitted in this embodiment.

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

[0065] (Vehicle dispatch notification process S11) Returning to Figure 7, 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 for 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 probing 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.

[0066] (Acceptance response processing S12) When the vehicle dispatch response unit of the vehicle terminal arranged in the vehicle receives information indicating that the vehicle has become the target of the vehicle dispatch request 22 from the vehicle terminal control unit 174, it notifies the driver of this fact, for example, via the vehicle display device. When notifying the information, the vehicle terminal may also display information related to the vehicle dispatch request 22 (for example, the boarding location, user information related to user 2), etc., on the vehicle display device. When accepting the above-mentioned vehicle dispatch target notification, the driver accepts the vehicle dispatch target notification through the vehicle input device of the vehicle terminal, for example, by tapping a position corresponding to the "Request Accept" button displayed on the vehicle display device. The vehicle dispatch response unit transmits information regarding the acceptance of the vehicle dispatch target notification (acceptance response), including acceptance of the vehicle dispatch target notification, to the vehicle dispatch management server 60.

[0067] If the driver cannot accept the vehicle allocation target notification 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 target notification, 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 target notification (acceptance response) from the vehicle terminal during that waiting time, it determines that the driver of the vehicle to be allocated has not accepted the vehicle allocation target notification. In this case, the vehicle allocation unit 172 determines that the vehicle with the second highest priority among the vehicles associated with the vehicle allocation request 22 in the matching process S10 is the new vehicle to be allocated. Next, the vehicle terminal control unit 174 notifies the vehicle terminal of the other vehicle that has become the new vehicle to be allocated of information (vehicle allocation target notification) indicating that the vehicle has become the subject of the vehicle allocation request 22.

[0068] (Vehicle dispatch completion notification process S13) When the vehicle terminal control unit 174 receives information (acceptance response) regarding acceptance of the dispatch target notification from the vehicle terminal, it confirms the dispatch of the dispatch target vehicle in response to the dispatch request 22 and sends a dispatch completion notification to the vehicle terminal indicating that the dispatch has been confirmed.

[0069] (Boarding location display process S14) The vehicle display device of the vehicle terminal displays information related to the ride dispatch request 22, such as the boarding location and the route to the boarding location. Alternatively, the route to the boarding location may be displayed by a separate navigation application instead of the vehicle application. The images displayed on the vehicle display device will be described in detail later. With this configuration, the vehicle driver can grasp the information related to the ride dispatch request 22, drive an appropriate route to the boarding location, and find the user 2 early.

[0070] (User vehicle dispatch completion notification process S15) 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.

[0071] 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 (S10) can be increased, thereby enabling efficient vehicle dispatch while maintaining convenience for the user 2.

[0072] Next, an image displayed on the vehicle display device after the vehicle dispatch target notification is accepted will be described.

[0073] FIG. 10 is an example of a first image 100 displayed on the vehicle terminal (NRS terminal 40) used by the driver.

[0074] Images 100 and 400 in Figure 10 and images 100A, 200, 200A, and 300 in Figures 11 to 14 appearing below are displayed on the display device 144 of the NRS terminal 40 when the NRS driver 4 is logged in to the NRS terminal 40. However, these images may also be displayed on the display device 134 of the taxi terminal 30 when the NRS driver 4 is logged in to the taxi terminal 30, or on the display device 134 or 144 when the taxi driver 3 is logged in to the taxi terminal 30 or the NRS terminal 40, or on the display device 134 or 144 when a special crew member is logged in to the taxi terminal 30 or the NRS terminal 40. These images are displayed while the vehicle application is in use.

[0075] The first image 100 is displayed on the display device 144 after the acceptance response process S12. That is, the first image 100 is displayed on the display device 144 after the acceptance of the dispatch target notification and before arrival at the boarding location. In other words, the first image 100 is displayed on the display device 144 during pick-up.

[0076] For example, the first image 100 includes the current position 101 of the vehicle on a map. Also, for example, the first image 100 includes the address 102 of the boarding location included in the ride-dispatch request 22. Also, for example, if both the current position 101 of the vehicle and the position 103 of the boarding location fit within the map on the display device 144, the first image 100 includes the position 103 of the boarding location on the map in addition to the current position 101 of the vehicle.

[0077] The first image 100 includes an actual vehicle button B1. The actual vehicle button B1 is intended to be pressed when the user who sent the vehicle allocation request 22 actually gets into the vehicle. When the actual vehicle button B1 is pressed, a signal indicating that the user has gotten into the vehicle is transmitted from the NRS terminal 40 to the vehicle allocation management server 60.

[0078] For example, the first image 100 includes a details button B2, which will be described in detail later.

[0079] For example, the first image 100 includes a navigation button B3. In this embodiment, when the navigation button B3 is pressed, a navigation application different from the vehicle application is launched, and an image 400 showing a route to the boarding location is displayed. The vehicle application and the navigation application may be switchable with each other. Alternatively, the route to the boarding location may be displayed in the first image 100, i.e., in the vehicle application.

[0080] For example, the first image 100 includes a call button B4. The driver can press the call button B4 to make a call to the user terminal 20 of the user who sent the ride-hailing request 22. For example, the first image 100 includes a message button B5. The driver can press the message button B5 to send a message to the user terminal 20 of the user who sent the ride-hailing request 22.

[0081] 11 is another example of the first image 100A displayed on the vehicle terminal (NRS terminal 40) used by the driver. The first image 100A differs from the first image 100 described above in that it includes an arrival button B6. In other respects, the first image 100A may be the same as the first image 100.

[0082] The Arrival button B6 is intended to be pressed when the vehicle actually arrives at the boarding location. When the Arrival button B6 is pressed, a signal indicating that the vehicle has arrived at the boarding location is transmitted from the NRS terminal 40 to the user terminal 20 via the vehicle dispatch management server 60.

[0083] For example, the arrival button B6 may be added to the image 100 when the vehicle arrives within a predetermined distance from the boarding location. Alternatively, the arrival button B6 may be displayed in the image 100A after the vehicle dispatch target notification is accepted, regardless of the distance from the boarding location.

[0084] 12 is an example of a second image 200 displayed on the vehicle terminal (NRS terminal 40) used by the driver. In the second image 200, the same parts as the first images 100 and 100A will not be described.

[0085] The second image 200 is displayed on the display device 144 after the Arrival button B6 is pressed and before the Actual Vehicle button B1 is pressed. As described above, the Arrival button B6 is originally intended to be pressed when the vehicle actually arrives at the pickup location. However, as described above, in some embodiments, the Arrival button B6 is displayed in the image 100A after the vehicle dispatch notification is accepted, regardless of the distance from the pickup location. In this case, the Arrival button B6 may be mistakenly pressed even when the vehicle is not approaching the pickup location. The example of FIG. 12 illustrates such a situation. For example, as described above, NRS driver 4 may have less experience than taxi driver 3. Therefore, a situation like the example of FIG. 12 may be envisioned.

[0086] For example, the second image 200 includes the vehicle's current location 101 on a map. For example, the second image displays a larger map with the vehicle at the center to show the vehicle's surroundings in more detail in preparation for the ride. Therefore, for example, if the vehicle is far from the ride location, the ride location may not be displayed on the map. In the example of FIG. 12, as described above, even though the vehicle is not actually approaching the ride location, the arrival button B6 was mistakenly pressed, causing the vehicle application to recognize the vehicle as having arrived at the ride location, and the ride location is not displayed on the map. In this case, although the ride location address 102 is displayed, the NRS driver 4 may not be able to arrive at the ride location because the ride location 103 on the map is unknown.

[0087] For example, the second image 200 includes the customer information 104 of the user who sent the vehicle dispatch request 22.

[0088] 13 is another example of the second image 200A displayed on the vehicle terminal (NRS terminal 40) used by the driver. In the second image 200A, the same parts as the above images 100, 100A, and 200 will not be described.

[0089] The second image 200A is displayed on the display device 144 after the actual vehicle button B1 is pressed. As described above, the actual vehicle button B1 is intended to be pressed when the user who sent the vehicle dispatch request 22 actually gets into the vehicle. However, the actual vehicle button B1 may be pressed by mistake even though the user has not yet gotten into the vehicle. The example of FIG. 13 illustrates such a situation. For example, as described above, the NRS driver 4 may have less experience than the taxi driver 3. Therefore, a situation like the example of FIG. 13 may be envisioned.

[0090] For example, the second image 200A includes the location 105 of the drop-off location on the map and the address 106 of the drop-off location. However, as described above, in the example of FIG. 13, the actual vehicle button B1 was pressed by mistake, so the vehicle application recognizes that the user 2 has boarded the vehicle, and the information about the boarding location is no longer displayed in the second image 200A. In this case, the NRS driver 4 may not be able to arrive at the boarding location because the boarding location is unknown.

[0091] In this embodiment, in order to address the above-mentioned problem, the second images 200 and 200A include a details button (switch button) B2.

[0092] 14 is an example of a third image 300 displayed on the vehicle terminal (NRS terminal 40) used by the driver. In the third image 300, the same parts as the above-mentioned images 100, 100A, 200, and 200A will not be described.

[0093] The third image 300 is displayed on the display device 144 when the details button B2 is pressed on the second image 200, 200A. In the example of Fig. 14, the boarding location tab 107 is selected from the boarding location tab 107 indicating the boarding location and the disembarking location tab 108 indicating the disembarking location. The boarding location tab 107 and the disembarking location tab 108 can be switched between each other, and either may be displayed first when the details button B2 is pressed.

[0094] For example, the boarding location tab 107 includes an address 102 of the boarding location. Also, for example, the boarding location tab 107 includes a position 103 of the boarding location on a map. Also, for example, if the boarding location has a name, the boarding location tab 107 includes a name 109 of the boarding location. Also, for example, the boarding location tab 107 includes customer information 104 of the user who sent the ride dispatch request 22. Also, for example, the boarding location tab 107 includes landmark information 110 for finding the user.

[0095] According to this configuration, even if the driver accidentally presses the Arrival button B6 or the Actual Vehicle button B1 while being picked up, the driver can reconfirm the pickup location by pressing the Details button B2 in the second image 200, 200A. The taxi vehicle 32 may be equipped with a taxi meter. If the taxi terminal 30 is linked to the taxi meter, pressing the Actual Vehicle button on the taxi meter may switch the display on the taxi terminal 30. In this case, the Actual Vehicle button B1 on the taxi terminal 30 is essentially unnecessary. In contrast, the NRS vehicle 42 does not have a taxi meter. Therefore, pressing the Actual Vehicle button B1 is essential on the NRS terminal 40. Therefore, the configuration described above that allows the driver to reconfirm the pickup location by pressing the Details button B2 when the Actual Vehicle button B1 is accidentally pressed is effective for the NRS terminal 40. If the Actual Vehicle button B1 on the taxi terminal 30 is accidentally pressed, the taxi meter is temporarily changed to an empty vehicle, a pick-up, or the like. Otherwise, the taximeter will go into fare mode and fees will start accruing.

[0096] Fig. 15 is another example of the third image 300 displayed on the vehicle terminal (NRS terminal 40) used by the driver. In the example of Fig. 15, the drop-off location tab 108 is selected from the boarding location tab 107 and the drop-off location tab 108. When the drop-off location tab 108 is selected, information about the drop-off location is displayed in the drop-off location tab 108.

[0097] For example, the drop-off location tab 108 includes an address 111 of the drop-off location. Also, for example, the drop-off location tab 108 includes a location 112 of the drop-off location on a map. Also, for example, if the drop-off location has a name, the drop-off location tab 108 includes a name 113 of the drop-off location. Also, for example, the drop-off location tab 108 includes information 114 of a parking location where the vehicle will stop at the drop-off location.

[0098] The driver can return to the image before the third image 300 by pressing the back button B9.

[0099] 10 and 11, in this embodiment, the detail button B2 is also displayed on the first image 100, 100A. Therefore, in this embodiment, even when the detail button B2 is pressed on the first image 100, 100A, the third image 300 is displayed on the display device 144.

[0100] In the example of FIG. 12, the Arrival button B6 is displayed on image 100A after the dispatch target notification is accepted, regardless of the distance from the boarding location. However, the configuration that allows the boarding location to be reconfirmed by pressing the Details button B2 is also applicable to an embodiment in which the Arrival button B6 is added to image 100 depending on the distance from the boarding location. Conversely, the above configuration does not need to be applied to an embodiment in which the Arrival button B6 is added to image 100 depending on the distance from the boarding location. For example, in such an embodiment, the Details button B2 may be pressed, but only the Drop-off location tab 108 may be displayed.

[0101] The vehicle dispatch management system 1 as described above includes an NRS terminal 40 used by an NRS driver 4, and a vehicle dispatch management server 60 that can communicate with the NRS terminal 40 via a network 6. The NRS terminal 40 includes a processing device 142 including a processor, and a display device 144, and the vehicle dispatch management server includes a processing device 162 including a processor. The processing device 162 of the vehicle dispatch management server 60 is configured to accept input of a vehicle dispatch request 22 having multiple setting items including a boarding location and a disembarking location, and to transmit at least some of the multiple setting items of the vehicle dispatch request 22, including at least the boarding location and the disembarking location, to the NRS terminal 40. The processing device 142 of the NRS terminal 40 is configured to: display, on the display device 144, a first image 100, 100A including at least one of an Arrival button B6 for inputting that the vehicle has arrived at the boarding location and an Actual Vehicle button B1 for inputting that the user has boarded the vehicle after accepting the dispatch notification and before arriving at the boarding location; and, when at least one of the Arrival button B6 and the Actual Vehicle button B1 is pressed, display a second image 200, 200A including a Details button B2 that enables the boarding location to be displayed on the display device 144. With this configuration, even if the NRS driver 4 accidentally presses the Arrival button B6 or the Actual Vehicle button B1 while being picked up, the NRS driver 4 can reconfirm the boarding location by pressing the Details button B2 in the second image 200, 200A. Therefore, a vehicle dispatch management system 1 that is user-friendly for general drivers can be provided.

[0102] Furthermore, in the vehicle dispatch management system 1, the processing device 142 of the NRS terminal 40 is configured to execute the following: after accepting the dispatch target notification and before arriving at the boarding location, displaying a first image 100, 100A including a real vehicle button B1 on the display device 144; and, when the real vehicle button B1 is pressed, displaying a second image 200A (see FIG. 13) including a details button B2 and a disembarkation location on the display device 144. As described above, after the real vehicle button B1 is pressed, information about the disembarkation location is displayed on the second image 200A, and information about the boarding location is no longer displayed. However, the NRS driver 4 can reconfirm the boarding location by pressing the details button B2 in the second image 200A.

[0103] Furthermore, in the vehicle dispatch management system 1, the processing device 142 of the NRS terminal 40 is configured to execute the following: after the dispatch target notification is accepted and before arrival at the boarding location, display a first image 100A including an arrival button B6 on the display device 144; and, when the arrival button B6 is pressed, display a second image 200 (see FIG. 12 ) including a details button B2 and the vehicle's current location 101 on the display device 144. As described above, after the arrival button B6 is pressed, the second image 200 displays the vehicle's current location 101, but may not display the boarding location location 103. However, the NRS driver 4 can reconfirm the boarding location by pressing the details button B2 in the second image 200.

[0104] The NRS terminal 40 includes a processing device 142 including a processor and a display device 144. The processing device 142 receives from the vehicle dispatch management server 60 at least some of the setting items of the vehicle dispatch request 22 input to the vehicle dispatch management server 60, including at least the boarding location and the disembarking location. After accepting the vehicle dispatch notification and before arriving at the boarding location, the processing device 142 displays on the display device 144 a first image 100, 100A including at least one of an arrival button B6 for inputting that the vehicle has arrived at the boarding location and an actual vehicle button B1 for inputting that the user has boarded the vehicle. When at least one of the arrival button B6 and the actual vehicle button B1 is pressed, the processing device 142 displays on the display device 144 a second image 200, 200A including a details button B2 that enables the boarding location to be displayed on the display device 144. This configuration allows the vehicle dispatch management system 1 to be provided that is user-friendly to ordinary drivers.

[0105] The vehicle dispatch management method executed by the NRS terminal 40 as described above includes receiving, from the vehicle dispatch management server 60, at least some of the setting items of the vehicle dispatch request 22 input to the vehicle dispatch management server 60, including at least the boarding location and the disembarking location; displaying, on the display device 144, a first image 100, 100A, which includes at least one of an arrival button B6 for inputting that the vehicle has arrived at the boarding location and an actual vehicle button B1 for inputting that the user has boarded the vehicle, after accepting the vehicle dispatch target notification and before arriving at the boarding location; and displaying, on the display device 144, a second image 200, 200A, which includes a details button B2 that enables the boarding location to be displayed on the display device 144 when at least one of the arrival button B6 and the actual vehicle button B1 is pressed. With this configuration, it is possible to provide a vehicle dispatch management system 1 that is user-friendly to ordinary drivers, as described above.

[0106] The program executed by the NRS terminal 40 as described above causes the NRS terminal 40 to receive, from the vehicle dispatch management server 60, at least some of the setting items of the vehicle dispatch request 22 input to the vehicle dispatch management server 60, including at least the boarding location and the disembarking location; display, after acceptance of the vehicle dispatch target notification and before arrival at the boarding location, a first image 100, 100A including at least one of an arrival button B6 for inputting that the vehicle has arrived at the boarding location and an actual vehicle button B1 for inputting that the user has boarded the vehicle, on the display device 144; and display, when at least one of the arrival button B6 and the actual vehicle button B1 is pressed, a second image 200, 200A including a details button B2 that enables the boarding location to be displayed on the display device 144. With this configuration, as described above, a vehicle dispatch management system 1 that is user-friendly for ordinary drivers can be provided.

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

[0108] For example, in the above embodiment, the taxi vehicle 32 may be used by both the taxi driver 3 and the special crew, and the NRS vehicle 42 may be used by the NRS driver 4. In this case, the taxi terminal 30 may be used by both the taxi driver 3 and the special crew, and the NRS terminal 40 may be used only by the NRS driver 4. In other embodiments, the special crew may use a specific vehicle (the above-mentioned special vehicle) other than the taxi vehicle 32 and the NRS vehicle 42. In this case, the taxi vehicle 32, the special vehicle, and the NRS vehicle 42 may have different settings. For example, the special vehicle may be a luxury car with a higher grade of interior and equipment than the taxi vehicle 32. In the above embodiment, the special vehicle may be treated as one of the "vehicles," just like the taxi vehicle 32 and the NRS vehicle 42. Furthermore, in this case, the special crew may use a terminal (hereinafter, also referred to as a special terminal) other than the taxi terminal 30 and the NRS terminal 40. In this case, determining the driver type after logging in may not be necessary. For example, the special terminal may have a hardware configuration similar to that of at least one of the taxi terminal 30 and the NRS terminal 40. In the above embodiment, the special terminal may be treated as one of the "vehicle terminals," similar to the taxi terminal 30 and the NRS terminal 40. The vehicle application installed on the taxi terminal 30, the vehicle application installed on the special terminal, and the vehicle application installed on the NRS terminal 40 may be different from each other, may be the same as each other, or may have similar functions.

[0109] Furthermore, for example, in the above embodiment, the configuration that allows the driver to reconfirm the boarding location by pressing the details button B2 is applied to the NRS terminal 40. This configuration may also be applied to the taxi terminal 30 and the special terminal. For example, if the taxi terminal 30 is not linked to the taxi meter (i.e., if the driver needs to press the actual vehicle button on the taxi meter and then press the actual vehicle button B1 on the taxi terminal 30), it is possible that the taxi driver 3 accidentally presses the actual vehicle button B1 on the taxi terminal 30. Also, if a predetermined fare is applied to the taxi vehicle 32, the taxi meter is not used for fare calculation. In these cases, applying the above configuration to the taxi terminal 30 may be beneficial. Furthermore, as described above, special crew members, like the NRS drivers 4, often have variations in their driver qualifications, driving skills, knowledge, and the like. Therefore, applying the above configuration to the taxi terminal 30 or the special terminal used by the special crew members may be beneficial.

[0110] In the above embodiment, the first image includes both the actual vehicle button B1 and the current arrival button B6. In other embodiments, the first image does not need to display either the actual vehicle button B1 or the current arrival button B6.

[0111] Also provided are programs that cause at least one computer to function as the vehicle dispatch management system 1 or vehicle dispatch management server 60, and computer-readable storage media such as flexible disks, magneto-optical disks, ROMs, CDs, DVDs, and BDs that store the programs. Here, the program refers to data processing means written in any language or description method.

[0112] 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 sequence diagram, and may include parallel or subroutine processes. [Explanation of symbols]

[0113] 1. Vehicle dispatch management system 3 Taxi Driver (Driver) 4 NRS Driver (Driver) 6 Network 22 Vehicle Request 30 Taxi terminal (vehicle terminal) 40 NRS terminal (vehicle terminal) 60 Vehicle dispatch management server (vehicle dispatch management device) 100 1st image 100A 1st image 132 Taxi terminal processing unit (first processor) 134 Taxi terminal display device (vehicle display device) 142 NRS terminal processing unit (first processor) 144 NRS terminal display device (vehicle display device) 162 Processing device of vehicle dispatch management server (second processor) 200 2nd image 200A 2nd image B1 Actual car button B2 Details button (switch button) B6 Arrival button

Claims

1. a vehicle terminal used by a driver; a vehicle dispatch management device capable of communicating with the vehicle terminal via a network; Equipped with the vehicle terminal includes a first processor and a vehicle display device; the vehicle dispatch management device includes a second processor; The second processor Accepting input of a dispatch request having a plurality of setting items including a boarding location and a disembarking location; transmitting at least a part of the plurality of setting items of the vehicle dispatch request, including at least the boarding location and the disembarking location, to the vehicle terminal; configured to run The first processor After accepting the vehicle allocation target notification corresponding to the vehicle allocation request and before arriving at the boarding location, displaying a first image on the vehicle display device, the first image including an arrival button for inputting that the vehicle has arrived at the boarding location; When the arrival button is pressed, a second image including a switching button that enables the boarding location to be displayed on the vehicle display device is displayed on the vehicle display device. configured to perform Vehicle dispatch management system.

2. The first processor When the current arrival button is pressed, the second image including the switching button and the current position of the vehicle is displayed on the vehicle display device. configured to perform The vehicle dispatch management system according to claim 1 .

3. The first image further includes an actual vehicle button for inputting that the user has boarded the vehicle; The first processor When at least one of the actual vehicle button and the current arrival button is pressed, the second image is displayed on the vehicle display device. configured to perform The vehicle dispatch management system according to claim 1 .

4. The first processor When the actual vehicle button is pressed, the second image including the switching button and the disembarkation location is displayed on the vehicle display device. configured to perform The vehicle dispatch management system according to claim 3 .

5. A vehicle terminal capable of communicating with a vehicle dispatch management device via a network, a processor and a vehicle display device, The processor: receiving, from the vehicle dispatch management device, at least a part of a plurality of setting items of a vehicle dispatch request input to the vehicle dispatch management device, the setting items including at least a boarding location and a disembarking location; After accepting the vehicle allocation target notification corresponding to the vehicle allocation request and before arriving at the boarding location, displaying a first image on the vehicle display device, the first image including an arrival button for inputting that the vehicle has arrived at the boarding location; When the arrival button is pressed, a second image including a switching button that enables the boarding location to be displayed on the vehicle display device is displayed on the vehicle display device. configured to perform Vehicle terminal.

6. A vehicle dispatch management method executed by a computer, comprising: receiving, from a vehicle dispatch management device, at least some of a plurality of setting items of a vehicle dispatch request input to the vehicle dispatch management device, the setting items including at least a boarding location and a disembarking location; After accepting the vehicle allocation target notification corresponding to the vehicle allocation request and before arriving at the boarding location, displaying a first image on a vehicle display device, the first image including an arrival button for inputting that the vehicle has arrived at the boarding location; When the arrival button is pressed, a second image including a switching button that enables the boarding location to be displayed on the vehicle display device is displayed on the vehicle display device. A vehicle dispatch management method, including:

7. A program executed by a computer, The computer, receiving, from a vehicle dispatch management device, at least some of a plurality of setting items of a vehicle dispatch request input to the vehicle dispatch management device, the setting items including at least a boarding location and a disembarking location; After accepting the vehicle allocation target notification corresponding to the vehicle allocation request and before arriving at the boarding location, displaying a first image on a vehicle display device, the first image including an arrival button for inputting that the vehicle has arrived at the boarding location; When the arrival button is pressed, a second image including a switching button that enables the boarding location to be displayed on the vehicle display device is displayed on the vehicle display device. A program that executes.

8. a vehicle terminal used by a driver; a vehicle dispatch management device capable of communicating with the vehicle terminal via a network; Equipped with the vehicle terminal includes a first processor and a vehicle display device; the vehicle dispatch management device includes a second processor; The second processor Accepting input of a dispatch request having a plurality of setting items including a boarding location and a disembarking location; transmitting at least a part of the plurality of setting items of the vehicle dispatch request, including at least the boarding location and the disembarking location, to the vehicle terminal; configured to run The first processor displaying, on the vehicle display device, a first image including an actual vehicle button for inputting that the user has boarded the vehicle after accepting the vehicle allocation target notification corresponding to the vehicle allocation request and before arriving at the boarding location; When the actual vehicle button is pressed, a second image including a switching button that enables the boarding location to be displayed on the vehicle display device is displayed on the vehicle display device. configured to perform Vehicle dispatch management system.

9. The first processor When the actual vehicle button is pressed, the second image including the switching button and the disembarkation location is displayed on the vehicle display device; configured to perform The vehicle dispatch management system according to claim 8.

10. The first image further includes an arrival button for inputting that the vehicle has arrived at the boarding location, The first processor When at least one of the actual vehicle button and the current arrival button is pressed, the second image is displayed on the vehicle display device. configured to perform The vehicle dispatch management system according to claim 8.

11. The first processor When the current arrival button is pressed, the second image including the switching button and the current position of the vehicle is displayed on the vehicle display device. configured to perform The vehicle dispatch management system according to claim 10.

12. A vehicle terminal capable of communicating with a vehicle dispatch management device via a network, a processor and a vehicle display device, The processor: receiving, from the vehicle dispatch management device, at least a part of a plurality of setting items of a vehicle dispatch request input to the vehicle dispatch management device, the setting items including at least a boarding location and a disembarking location; displaying, on the vehicle display device, a first image including an actual vehicle button for inputting that the user has boarded the vehicle after accepting the vehicle allocation target notification corresponding to the vehicle allocation request and before arriving at the boarding location; When the actual vehicle button is pressed, a second image including a switching button that enables the boarding location to be displayed on the vehicle display device is displayed on the vehicle display device. configured to perform Vehicle terminal.

13. A vehicle dispatch management method executed by a computer, comprising: receiving, from a vehicle dispatch management device, at least some of a plurality of setting items of a vehicle dispatch request input to the vehicle dispatch management device, the setting items including at least a boarding location and a disembarking location; displaying, on a vehicle display device, a first image including an actual vehicle button for inputting that the user has boarded the vehicle after accepting the vehicle allocation target notification corresponding to the vehicle allocation request and before arriving at the boarding location; When the actual vehicle button is pressed, a second image including a switching button that enables the boarding location to be displayed on the vehicle display device is displayed on the vehicle display device. A vehicle dispatch management method, including:

14. A program executed by a computer, The computer, receiving, from a vehicle dispatch management device, at least some of a plurality of setting items of a vehicle dispatch request input to the vehicle dispatch management device, the setting items including at least a boarding location and a disembarking location; displaying, on a vehicle display device, a first image including an actual vehicle button for inputting that the user has boarded the vehicle after accepting the vehicle allocation target notification corresponding to the vehicle allocation request and before arriving at the boarding location; When the actual vehicle button is pressed, a second image including a switching button that enables the boarding location to be displayed on the vehicle display device is displayed on the vehicle display device. A program that executes.

Images