WO2024101140A1

WO2024101140A1 - Information processing system, information processing method, and program

Info

Publication number: WO2024101140A1
Application number: PCT/JP2023/038252
Authority: WO
Inventors: 洋平橋本; 誠一郎松本
Original assignee: ソニーグループ株式会社
Priority date: 2022-11-08
Filing date: 2023-10-24
Publication date: 2024-05-16

Abstract

The present technology relates to an information processing system, an information processing method, and a program that allow a vehicle allocation request with excellent convenience to be made from a terminal device of a passenger at the time of boarding a mobile device such as a cruising taxi or a taxi waiting for passengers. The information processing system comprises: a plurality of vehicles; a vehicle allocation management device that manages vehicle allocation of the vehicles; and a first terminal that sets contents of a vehicle allocation request as vehicle allocation request information. On the basis of the current location of the first terminal and the dynamic state data of the vehicles, a virtual waiting position is determined.

Description

Information processing system, information processing method, and program

This technology relates to an information processing system, an information processing method, and a program, and in particular to an information processing system, an information processing method, and a program that enable early boarding of a mobile device such as a cruising taxi.

Patent document 1 discloses a dispatch system that enables taxis to be dispatched more quickly.

JP 2003-281692 A

It can be difficult to find a taxi on the road, and it can take a long time to get one.

This technology was developed in light of these circumstances, and allows passengers to board taxis and other mobile devices more quickly.

The information processing system according to the first aspect of the present technology is an information processing system that includes a plurality of vehicles, a vehicle dispatch management device that manages the dispatch of the vehicles, and a first terminal that sets the contents of a dispatch request as dispatch request information, and has a processing unit that determines a virtual waiting position based on the current location of the first terminal and the dynamic data of the vehicles.

The information processing method according to the first aspect of the present technology is an information processing system including a plurality of vehicles, a vehicle dispatch management device that manages the dispatch of the vehicles, and a first terminal that sets the contents of a dispatch request as dispatch request information, and the processing unit of the information processing system having a processing unit determines a virtual waiting position based on the current location of the first terminal and the dynamic data of the vehicles.

The information processing system and information processing method according to the first aspect of the present technology include a plurality of vehicles, a vehicle dispatch management device that manages the dispatch of the vehicles, and a first terminal that sets the contents of a dispatch request as dispatch request information, and a virtual waiting position is determined based on the current location of the first terminal and the dynamic data of the vehicles.

The program of the second aspect of this technology is a program for causing a computer to function as a processing unit that determines a virtual waiting position suitable for the boarding position when boarding a cruising vehicle, based on the current location of the terminal that sets the dispatch request information indicating the contents of the dispatch request and the dynamic data of the vehicle for which dispatch is managed.

In the program of the second aspect of this technology, a virtual waiting position suitable for the boarding position when boarding a cruising vehicle is determined based on the current location of the terminal that sets the dispatch request information indicating the contents of the dispatch request and the dynamic data of the vehicle for which dispatch is managed.

1 is a block diagram showing a configuration example of an embodiment of a taxi dispatch system to which the present technology is applied; FIG. 13 is a diagram illustrating an outline of a procedure for requesting a vehicle when boarding a vehicle for patrol or waiting. FIG. 13 is a diagram illustrating an outline of a procedure for requesting a vehicle when boarding a vehicle for patrol or waiting. FIG. 13 is a diagram illustrating an outline of a procedure for requesting a vehicle when boarding a vehicle for patrol or waiting. FIG. 2 is a sequence diagram illustrating an overview of a process up to boarding a taxi when a user makes a taxi dispatch request for pick-up use in the taxi dispatch system of FIG. 1. FIG. 2 is a sequence diagram illustrating a process performed when a user makes a taxi dispatch request for circulating use or waiting use in the taxi dispatch system of FIG. 1. FIG. 13 is a diagram showing an example of a display on a boarding terminal. 2 is an example of a screen displayed on a user terminal when a user makes a taxi dispatch request using a virtual stop in the taxi dispatch system of FIG. 1 . FIG. 2 is a sequence diagram illustrating a process up to boarding a taxi when a user makes a taxi dispatch request using a virtual stop in the taxi dispatch system of FIG. 1 . FIG. 2 is a block diagram showing an example of a functional configuration of the taxi dispatch system shown in FIG. 1 . 1 is a block diagram showing an example of the configuration of an embodiment of a computer to which the present technology is applied.

Below, we will explain the implementation of this technology with reference to the drawings.

<Embodiment of Taxi Dispatch System>
FIG. 1 is a block diagram showing a configuration example of an embodiment of a taxi dispatch system to which the present technology is applied.

The taxi dispatch system 1 in FIG. 1 is a taxi dispatch system according to an embodiment to which the present technology is applied, and is a system that dispatches a taxi as a mobile device to a user based on a dispatch request from a user who is a user of the taxi (mobile device). In this specification, dispatch refers to running a taxi (vehicle) to transport a passenger to a destination (drop-off point) designated by the passenger. A dispatch request includes both a case where the passenger specifies in advance the boarding point where the passenger boards the taxi and the destination (drop-off point) where the passenger disembarks from the taxi, and a case where the passenger specifies only the destination before or after the passenger boards the taxi. Therefore, a request in which the passenger specifies only the destination when the passenger boards a taxi by signaling by raising his/her hand (when boarding a so-called cruising taxi) or boards a taxi at a specified location (waiting position) such as a taxi stand (when boarding a so-called waiting taxi) also corresponds to a dispatch request. In addition, when a passenger uses a taxi that is waiting for them, it is called "using a taxi that is waiting for them," and when a passenger uses a taxi that is waiting for them, it is called "using a waiting taxi." In addition, when a passenger uses a taxi by requesting a pick-up, it is called "using a pick-up taxi."

In addition, the taxi dispatch system 1 of FIG. 1 also manages a form of boarding (dispatch request) called virtual stop use. A virtual stop is a virtual waiting position (virtual taxi stand), and is different from a waiting position that actually exists in front of a station, etc., and represents a position where a user is predicted to easily find a cruising taxi 12, depending on the current location of the user (user terminal 11) and the positions of the taxis 12 traveling around the user's current location. When making a dispatch request using a virtual stop, the position of the virtual stop is presented to the user (user terminal 11). A boarding using a virtual stop is one form of boarding using cruising or waiting, but has the following characteristics. A boarding using a virtual stop is different from a boarding using a pick-up service, and like a boarding using a cruising service, a pick-up fee is not incurred, and there is a possibility that a taxi 12 can be boarded earlier than a boarding using normal cruising or waiting, or a boarding using a pick-up service. However, unlike a boarding using a pick-up service, there is no guarantee of a car being dispatched to the user, and a user waiting at a virtual stop may not necessarily be able to board as planned. In addition, when riding at a virtual stop, a fee may be charged in addition to the fee (fare) charged for riding a regular cruising or waiting ride, and whether or not a ride is at a virtual stop does not depend on whether or not a special fee is charged for using a virtual stop.

The taxi dispatch system 1 has a user terminal 11, taxis 12 (12A, 12B, 12C, 12D, 12E), a dispatch management device 13 (13A, 13B, 13C), and an integrated dispatch management device 14.

The taxis 12 managed by the taxi dispatch system 1 (taxis 12 managed by the taxi dispatch system 1) may include vehicles operated by a specific taxi company and vehicles operated by individuals. The former are referred to as company taxis, and the latter are referred to as private taxis.

The taxi dispatch system 1 in Figure 1 assumes the existence of taxi companies A, B, C, and D. Company A taxis 12A, B taxis 12B, C taxis 12C, and D taxis 12D represent company taxis operated by companies A, B, C, and D, respectively. Private taxis 12E represent private taxis operated by individuals. However, the number of taxi companies shown in Figure 1, the number of company taxis operated by each taxi company, and the number of private taxis are just examples, and there are no particular limitations on these numbers.

Some taxi companies build their own company-specific taxi dispatch system that includes a company-specific dispatch management device (including a device that manages operations) to manage the dispatch of their company taxis. In the taxi dispatch system 1 of Figure 1, it is assumed that companies A, B, and C each have their own company-specific dispatch management device, and company D does not have its own company-specific dispatch management device.

Dispatch management devices

13A, 13B, and 13C represent the dispatch management devices of companies A, B, and C, respectively.

When there is no distinction between the dispatch management device 13A of Company A, the dispatch management device 13B of Company B, and the dispatch management device 13C of Company C, they will be referred to simply as the dispatch management device 13. The company taxi 12D of a taxi company (Company D) that does not have a dispatch management device incorporated in the taxi dispatch system 1 will be treated as a taxi equivalent to the private taxi 12E in the taxi dispatch system 1 of FIG. 1. In the following, when there is no distinction between Company A taxi 12A, Company B taxi 12B, and Company C taxi 12C that are company taxis of taxi companies that have the dispatch management device 13, they will be referred to simply as company taxis 12, and when referring to private taxi 12E, it will include Company D taxi 12D that is a company taxi of a taxi company that does not have the dispatch management device 13. When there is no distinction between the company taxi 12 and the private taxi 12E, they will be referred to simply as taxi 12 or vehicle, and when referring to simply taxi 12 or vehicle, it will be understood that it is a taxi managed by the taxi dispatch system 1 of FIG. 1.

In the taxi dispatch system 1 of FIG. 1, a taxi dispatch system is shown in which a company taxi 12, the dispatch of which is managed by a company-dedicated dispatch management device 13, and other private taxis 12E are dispatched, but the application of the present technology is not limited to this. The present technology can be applied to a taxi dispatch system that does not include a dispatch management device 13 and manages the dispatch of one or more taxis (not limited to private taxis) for the taxi dispatch system 1 of FIG. 1. The present technology can be applied to a taxi dispatch system that manages the dispatch of taxis, the dispatch of which is managed by one or more dispatch management devices 13, and other taxis, regardless of whether they are dedicated to a company or not, for the taxi dispatch system 1 of FIG. 1. In this case, the dispatch management device 13 may be, for example, a dispatch management device that manages the dispatch of taxis by region other than by company.

In the taxi dispatch system 1 of FIG. 1, when information is exchanged between two devices that are separated from each other, they are connected (communicatively connected) so that they can communicate with each other via a communication network or communication path of any communication standard.

The communication network or communication path that connects two devices that are separated from each other may be the Internet, a public telephone network, a wide area communication network for mobile communication such as the so-called 4G line or 5G line, a WAN (Wide Area Network), a LAN (Local Area Network), a wireless communication network that communicates in accordance with the Bluetooth (registered trademark) standard, a communication path for short-range wireless communication such as NFC (Near Field Communication), a communication path for infrared communication, a wired communication network that complies with standards such as HDMI (registered trademark) (High-Definition Multimedia Interface) or USB (Universal Serial Bus), etc. In the following, even if not specifically stated, the exchange of information between two devices will be performed by communication via a specified communication network or communication path.

The user terminal 11 (terminal device) is, for example, an information processing device such as a smartphone or tablet terminal used by a user who requests dispatch of a taxi 12. The user terminal 11 is communicatively connected to the integrated dispatch management device 14. The user terminal 11 represents one user terminal used by any one of multiple users who use the taxi dispatch system 1. When simply referring to a user, it represents a user who uses the user terminal 11 shown in FIG. 1.

A user application 21, which is an application program for the user (a vehicle dispatch application), is installed on the user terminal 11. Hereinafter, the user application 21 refers to a processing unit that executes the application program for the user. The user application 21 may be a case in which a specific program executed in the vehicle dispatch integrated management device 14 is used via an API (Application Programming Interface). For example, the user application 21 may operate the user terminal 11 as a device that inputs and outputs information requested and information generated by the execution of a program in the vehicle dispatch integrated management device 14.

The user application 21 requests the integrated vehicle dispatch management device 14 to dispatch a taxi 12 based on user operations, and displays a confirmation of dispatch in response to the dispatch request. The user application 21 can also display the current operating status of the taxi 12 on the display by acquiring vehicle movement data in the vicinity of the user's current location from the integrated vehicle dispatch management device 14.

The user application 21 (user terminal 11) supplies (transmits) various information to the vehicle dispatch integrated management device 14. Information supplied to the vehicle dispatch integrated management device 14 includes vehicle dispatch request information related to a vehicle dispatch request set (specified) by the user. In the case of a vehicle dispatch request for pick-up use, the vehicle dispatch request information includes information on the current location of the user terminal 11. For example, information on the current location of the user terminal 11 is detected by a GPS (Global Positioning System) receiver equipped in the user terminal 11 and is automatically included in the vehicle dispatch request information. The user application 21 can register candidates or default settings that can be set as vehicle dispatch request information in advance. Such vehicle dispatch request information includes, for example, favorite locations that can be destinations or boarding locations, default destinations, default desired settings for air conditioning (high, low), default desired settings for driving speed (slow, etc.), default desired settings for driver behavior while driving (do not talk, etc.), on/off of pre-determination when using a cruising service, on/off of destination linkage, on/off of route setting, etc. In addition, passengers can also set their preferred genre of advertisements to be displayed on the passenger terminal 15 in advance as part of the dispatch request information.

The user application 21 acquires (receives) various information from the vehicle dispatch integrated management device 14. Information acquired from the vehicle dispatch integrated management device 14 includes a vehicle dispatch confirmation notification, an arrival notification, and vehicle status data, etc.

As shown in Company A's taxi 12A in Figure 1, the taxi 12 has an on-board device 31, a communication unit 32, and a driver's terminal 33.

The vehicle-mounted device 31 (taxi meter) is equipped with a vehicle dynamics data acquisition unit 41. The vehicle dynamics data acquisition unit 41 acquires necessary data from the fare meter, GPS receiver, gyro sensor, speedometer, etc. (none of which are shown), and generates vehicle dynamics data that represents the dynamics log of the taxi 12 (host vehicle) in which it is mounted.

Vehicle status data includes various information such as company ID, radio ID, driver ID, tablet ID, status, status time, fare (fare), current location, driving speed, direction of travel, boarding location, and destination (drop-off location). The company ID represents information that identifies the taxi company to which the vehicle belongs. The radio ID represents information that identifies the vehicle. The driver ID represents information that identifies the driver who is on duty in the vehicle. The tablet ID represents information that identifies (specifies) the passenger terminal 15.

The status indicates the operating state (business state) of the vehicle obtained from the fare meter, and indicates one of the following states: "occupied vehicle", "vacant vehicle", "paid vehicle", and "pick-up". However, the type of status is not limited to these. The status time indicates the time when the status information was generated (obtained). The fare (fare) is obtained from the fare meter and indicates the fare (fare) previously received and the current fare when the status is "occupied vehicle". The current location, running speed, and traveling direction indicate the current location (place), running speed, and traveling direction of the vehicle obtained from, for example, a GPS receiver, a gyro sensor, a speedometer, etc. The boarding point indicates the location (place) where current and past passengers boarded the vehicle. The destination (drop-off point) indicates the location (place) where past passengers disembarked from the vehicle (location of the transport destination).

The vehicle status data acquisition unit 41 generates vehicle status data periodically or irregularly, and supplies (transmits) the data to the vehicle dispatch management device 13 or the vehicle dispatch integrated management device 14 via the communication unit 32. If the vehicle is a company taxi 12, the vehicle status data acquisition unit 41 supplies vehicle status data to the vehicle dispatch management device 13 that manages the vehicle. The vehicle status data supplied to the vehicle dispatch management device 13 is supplied from the vehicle dispatch management device 13 to the vehicle dispatch integrated management device 14. If the vehicle is a private taxi 12E (including company taxi 12D), the vehicle status data acquisition unit 41 supplies vehicle status data to the vehicle dispatch integrated management device 14. Note that if the vehicle is a company taxi 12, the vehicle status data may be supplied to the vehicle dispatch integrated management device 14 from the vehicle status data acquisition unit 41, rather than from the vehicle dispatch management device 13.

The communication unit 32 controls communication with other devices located away from the taxi 12 in which the communication unit 32 is installed.

The driver terminal 33 is an information processing device such as a smartphone or tablet terminal used by the driver (crew member) who is on duty in the vehicle. The driver terminal 33 may be installed in the vehicle, or the vehicle-mounted device 31 may have the functions of the driver terminal 33. The driver terminal 33 is communicatively connected to the vehicle dispatch integrated management device 14. The driver terminal 33 and the vehicle dispatch integrated management device 14 can be communicatively connected without going through the communication unit 32 by the communication function of the driver terminal 33, but may also be connected via the communication unit 32.

If the vehicle is a company taxi 12, the exchange of various information between the driver terminal 33 and the vehicle dispatch integrated management device 14 is not limited to being direct, but may be relayed through the vehicle dispatch management device 13 that manages the vehicle, or may be via the communication unit 32 of the vehicle.

A driver app 51, which is an application program for the driver (a vehicle dispatching app), is installed on the driver terminal 33. Hereinafter, the driver app 51 refers to a processing unit that executes the application program for the driver. The driver app 51 may be a case in which a specific program executed in the vehicle dispatch integrated management device 14 is used via an API. For example, the driver app 51 may operate the driver terminal 33 as a device that inputs and outputs information requested and information generated by the execution of a program in the vehicle dispatch integrated management device 14.

The driver app 51 displays dispatch request information, operation information, various notification screens, and various input screens on the display.

The driver app 51 acquires (receives) various information from the vehicle dispatch integrated management device 14. Information acquired from the vehicle dispatch integrated management device 14 includes a vehicle dispatch request notification, vehicle dispatch request information, and vehicle dispatch confirmation notification. A vehicle dispatch request notification is information notifying that a vehicle dispatch request has been made. Vehicle dispatch request information is information related to the vehicle dispatch request, such as the boarding location, destination, and payment method (fare confirmation method, payment method) specified by the user. The vehicle dispatch request information set by the user on the user terminal 11 is displayed on the driver terminal 33 by the driver app 51, so the driver can understand the request content desired by the user.

The driver app 51 supplies (transmits) various information, such as a request acceptance notification, to the vehicle dispatch integrated management device 14. The request acceptance notification is information that notifies the driver that he or she has accepted the vehicle dispatch request.

The vehicle dispatch management device 13 manages the dispatch of company taxis 12. The vehicle dispatch management device 13 is configured, for example, as a server device or a cloud device (information processing device) with a network connection function. Note that the vehicle dispatch management device 13A for company A, the vehicle dispatch management device 13B for company B, and the vehicle dispatch management device 13C for company C are each configured in the same way, and the vehicle dispatch management device 13A for company A will be used as an example for explanation.

The vehicle dispatch management device 13A is communicatively connected to the communication unit 32 of Company A's taxi 12A and the vehicle dispatch integrated management device 14. When the vehicle dispatch management device 13A uses the driver's terminal 33 for vehicle dispatch management, or when the vehicle dispatch management device 13A relays communication between the driver's terminal 33 of Company A's taxi 12A and the vehicle dispatch integrated management device 14, the vehicle dispatch management device 13A is also communicatively connected to the driver's terminal 33.

The vehicle dispatch management device 13A has a vehicle status data management unit 81, an order information management unit 82, and a communication unit 83.

The vehicle movement data management unit 81 manages vehicle movement data supplied periodically or irregularly from the vehicle movement data acquisition unit 41 of each Company A taxi 12A via the communication unit 32. Specifically, the vehicle movement data management unit 81 stores the vehicle movement data from the vehicle movement data acquisition unit 41 of each Company A taxi 12A in an internal memory unit. Each time new vehicle movement data is supplied from the vehicle movement data acquisition unit 41 of each Company A taxi 12A, the vehicle movement data management unit 81 updates the vehicle movement data in the memory unit to data including the latest movement log using the new vehicle movement data. The vehicle movement data management unit 81 supplies the vehicle movement data from each Company A taxi 12A to the vehicle dispatch integrated management device 14 via the communication unit 83.

The vehicle status data management unit 81 can display the vehicle status data of each Company A taxi 12A stored in the memory unit on a display (not shown). For example, when an operator who manages the operation of Company A taxis 12A receives a call requesting dispatch to Company A, the operator displays the vehicle status data stored in the memory unit on the display. The operator checks the current location and current status of each Company A taxi 12A, and searches for a Company A taxi 12A that can fulfill the dispatch request. As a result of the search, the operator makes a dispatch request to a driver of a Company A taxi 12A that can fulfill the dispatch request by any method, such as calling the driver.

The order information management unit 82 manages information on advance vehicle dispatch requests from customers, etc., i.e., vehicle dispatch reservations, which are vehicle dispatch requests with a specified pick-up time. For example, when an operator of Company A receives a vehicle dispatch reservation call from a customer, the operator inputs vehicle dispatch reservation information (vehicle dispatch reservation information), such as the customer name, pick-up time, pick-up location (boarding location), and destination, from an operation terminal and stores the information in the order information management unit 82.

When it is a predetermined time before the pick-up time in the stored vehicle reservation information, the order information management unit 82 prompts the operator to make a vehicle dispatch request corresponding to the vehicle reservation information by displaying a warning on the display, etc. The operator searches for a Company A taxi 12A that can fulfill the vehicle dispatch reservation in the same way as in the case of a vehicle dispatch request without a specified pick-up time, and makes a dispatch request to the driver.

The communication unit 83 controls communication with other devices that are remote from the vehicle dispatch management device 13.

The vehicle dispatch management device 13 is not limited to the form shown in FIG. 1. Another form of the vehicle dispatch management device 13 may be configured similarly to the integrated vehicle dispatch management device 14, the details of which will be described later. In that case, for example, the vehicle dispatch management device 13 of Company A can accept a vehicle dispatch request to Company A from the user terminal 11 without an operator. The vehicle dispatch management device 13A of Company A searches for a Company A taxi 12A that can respond to the dispatch request based on the vehicle status data of each Company A taxi 12A. As a result of the search, the vehicle dispatch management device 13 of Company A notifies the driver terminal 33 of the Company A taxi 12A that matches the dispatch request of the dispatch request, confirms that the driver has accepted the dispatch request, and confirms the dispatch.

As yet another embodiment of the vehicle dispatch management device 13, when a vehicle dispatch request is received from a telephone or user terminal 11, the vehicle dispatch management device 13 may transmit the received vehicle dispatch request to the vehicle dispatch integrated management device 14. In this case, the vehicle dispatch integrated management device 14 treats the vehicle dispatch request from the vehicle dispatch management device 13 in the same way as a vehicle dispatch request from the user terminal 11.

The vehicle dispatch management device 13 is not limited to a specific form, but for the sake of simplicity, it is assumed that the device only has the function of relaying the vehicle status data of each company taxi 12 from each company taxi 12 to the vehicle dispatch integrated management device 14. Regardless of whether the taxi 12 is a company taxi 12 or not, the vehicle status data of each taxi 12 is supplied to the vehicle dispatch integrated management device 14 from each taxi 12 without explicitly stating the existence of the vehicle dispatch management device 13.

The integrated dispatch management device 14 is a dispatch management device that manages the dispatch of all taxis 12, namely, Company A taxis 12A, Company B taxis 12B, Company C taxis 12C, company taxis 12D, and private taxis 12E (company taxis 12 and private taxis 12E). The integrated dispatch management device 14 is composed of, for example, a server device or a cloud device (information processing device) with a network connection function. The integrated dispatch management device 14 is communicatively connected to each of the user terminal 11, the communication unit 32 of the taxi 12, the driver terminal 33 of the taxi 12, the dispatch management device 13 (communication unit 83), and the passenger terminal 15.

The vehicle dispatch integrated management device 14 has a vehicle status data management unit 101, a customer data management unit 102, an order information management unit 103, a vehicle dispatch management unit 104, a taxi company communication unit 105, and an app communication unit 106.

The vehicle status data management unit 101 manages the vehicle status data of each taxi 12. The vehicle status data of each taxi 12 is supplied to the vehicle status data management unit 101 on a regular or irregular basis from the vehicle status data acquisition unit 41 of each taxi 12 via the communication unit 32 and the taxi company communication unit 105.

The vehicle movement data management unit 101 stores the vehicle movement data of each taxi 12 supplied from each taxi 12 in an internal memory unit. Each time new vehicle movement data is supplied, the vehicle movement data management unit 101 updates the vehicle movement data in the memory unit to data including the latest movement log using the new vehicle movement data. The vehicle movement data of each taxi 12 stored in the memory unit can be displayed on a display (not shown).

The customer data management unit 102 generates customer data based on data entered by an operator or data supplied from the user terminal 11, and stores it in an internal storage unit. For example, the customer data management unit 102 stores information such as the customer's name, the customer's favorite taxi company or taxi company that the customer prefers for dispatch, frequently used taxi stand, and average waiting time for pick-up in association with user identification information (customer ID) that identifies the customer. The customer data management unit 102 may store information linking the taxi stand, destination, driving route, and usage time for each customer. The customer data may be data entered by the user at the user terminal 11, or may be data generated by the customer data management unit 102 based on the user's riding history, etc.

The order information management unit 103 manages advance vehicle dispatch requests from customers, etc., i.e., information on vehicle dispatch reservations with specified pick-up times. The order information management unit 103 manages information on vehicle dispatch reservations received by the representative reservation center that oversees each taxi company or by the user terminal 11.

The order information management unit 103 stores vehicle reservation information related to vehicle reservations. When a vehicle reservation is received by telephone at a reservation center or the like, an operator inputs vehicle reservation information from an operation terminal and stores it in the order information management unit 103. In the case of a vehicle reservation from the user application 21 of the user terminal 11, that is, when vehicle request information for a pick-up service with a specified pick-up time is supplied from the user application 21, the order information management unit 103 stores the vehicle request information as vehicle reservation information. Note that the vehicle reservation information includes information such as the boarding location, destination, and payment method (fare determination method, payment method) that is the same as vehicle request information for a pick-up service without a specified pick-up time, as well as information on the pick-up time (reservation time).

When it is a predetermined time before the pick-up time in the stored vehicle dispatch reservation information, the order information management unit 103 supplies the vehicle dispatch request notification and vehicle dispatch request information to the vehicle dispatch management unit 104 based on the vehicle dispatch reservation information. As a result, vehicle dispatch reservations are processed in the same way as vehicle dispatch requests that do not specify a pick-up time. In the following, to simplify the explanation, the explanation of vehicle dispatch reservations is omitted.

The dispatch management unit 104 manages the dispatch of managed taxis 12 based on dispatch request information, etc. For example, when a dispatch request operation is performed on the user terminal 11, the dispatch management unit 104 acquires the dispatch request information, etc. supplied from the user terminal 11 (user application 21) via the application communication unit 106. In the case of a dispatch request for pick-up use, the dispatch management unit 104 detects the optimal taxi 12 (optimal vehicle) for dispatch to the boarding location (boarding location specified by the user) included in the dispatch request information. In addition, in the case of a dispatch request for use of a virtual stop, the dispatch management unit 104 detects the position of the virtual stop suitable for the current location of the user (user terminal 11) included in the dispatch request information, and the optimal taxi 12 (optimal vehicle) for boarding at the virtual stop position. The vehicle dispatch management unit 104 supplies predetermined information such as vehicle dispatch request information (or vehicle dispatch information) to the driver terminal 33 (driver app 51), user terminal 11 (user app 21), and passenger terminal 15 (passenger app 121) of the detected optimal vehicle via the app communication unit 106. As a result, the vehicle dispatch management unit 104 performs various management related to vehicle dispatch, such as selecting a vehicle corresponding to the vehicle dispatch request based on the vehicle dispatch request information, notifying the selected vehicle of the vehicle dispatch request information (pick-up location, destination, driving route, etc.), and issuing operating instructions corresponding to the information.

In response to a request for dispatching a taxi for pick-up use, the dispatch management unit 104 searches (detects) the optimal taxi 12 (optimal vehicle) for dispatching to the boarding location specified by the user, based on the vehicle status data of each taxi 12 in the vehicle status data management unit 101. For example, the dispatch management unit 104 searches for the taxi 12 that can arrive at the boarding location the fastest as the optimal vehicle.

The taxi company communication unit 105 controls communication with the communication unit 83 of the vehicle dispatch management device 13 and the communication unit 32 of each taxi 12, and mainly receives vehicle status data of each vehicle.

The app communication unit 106 controls communication with the user app 21 of the user terminal 11, the driver app 51 of the driver terminal 33 of each taxi 12, and the passenger app 121 of the passenger terminal 15. The taxi company communication unit 105 and the app communication unit 106 may communicate using the same communication line, and do not necessarily need to be distinguished.

The passenger terminal 15 is, for example, an information processing device such as a tablet terminal installed in the partition between the front and rear seats of the taxi 12 (such as the back of the front seat). A passenger terminal 15 is installed in each taxi 12, but FIG. 1 shows one of them. The passenger terminal 15 is connected to the vehicle dispatch integrated management device 14 for communication via the application communication unit 106. A passenger application 121, which is an application program (dispatch application) for passengers, is installed in the passenger terminal 15. In the following, the passenger application 121 refers to a processing unit that executes the application program for passengers. The passenger application 121 may be a case where a specific program executed in the vehicle dispatch integrated management device 14 is used via an API (Application Programming Interface). For example, the passenger application 121 may operate the passenger terminal 15 as a device that inputs and outputs information requested or generated by the execution of a program in the vehicle dispatch integrated management device 14. The passenger application 121 mainly presents various information to passengers, such as input and output of vehicle dispatch request information, operation status, and payment information. In addition, the passenger terminal 15 can also display information displayed on the user terminal 11 by linking with the user terminal 11, and users on board can watch videos and the like on the passenger terminal 15, which has a larger screen than the user terminal 11.

<Request for dispatch of a vehicle for idling or waiting use>
2 to 4 are diagrams for explaining the outline of a procedure for requesting a dispatch when riding in a taxi for cruising or waiting for a ride. In the following explanation, a user is a passenger who rides in a taxi 12 for cruising or waiting for a ride, a user terminal 11 is a user terminal owned by the user, and a taxi 12 is a taxi that the user rides in.

When a user gets into a taxi 12 by cruising or waiting, the screen 201 of the passenger terminal 15 of the taxi 12 displays the standby image of FIG. 2 (screen 201 is called standby screen 201 in FIG. 2). A guide image is displayed on the standby screen 201, urging the user to hold (touch) the user terminal 11 owned by the user over the passenger terminal 15. When the user holds the user terminal 11 over the passenger terminal 15, the user terminal 11 and the passenger terminal 15 are communicatively connected (NFC connection) by NFC (Near field communication), which is one of the short-range wireless communication standards. Note that the communication connection between the user terminal 11 and the passenger terminal 15 is not limited to NFC. When the user terminal 11 and the passenger terminal 15 are communicatively connected by NFC, the passenger terminal 15 supplies the user terminal 11 with vehicle information and the like that identifies the taxi 12 in which the user has boarded, i.e., the taxi 12 in which the passenger terminal 15 is installed. The vehicle information for identifying the taxi 12 is not limited to identification information attached to the vehicle, but may be information associated with the vehicle, such as a wireless ID, a driver ID, or a tablet ID (information for identifying the passenger terminal 15). The user terminal 11 may acquire vehicle information, etc., by photographing and reading a two-dimensional code (including a one-dimensional code) such as a QR code (registered trademark) or text information displayed on the screen of the passenger terminal 15, rather than acquiring vehicle information, etc., from the passenger terminal 15 via a communication connection such as NFC.

The user terminal 11 supplies the vehicle information acquired from the passenger terminal 15 to the vehicle dispatch integrated management device 14. The user terminal 11 also supplies the vehicle dispatch request information set by the user to the vehicle dispatch integrated management device 14. The vehicle dispatch request information includes, for example, user information (name, etc.), destination (drop-off point), driving route, and payment method (fare determination method, payment method). However, in the case of a ride using a cruising vehicle or a waiting vehicle, information specifying the boarding point is not included in the boarding request information. Note that the vehicle dispatch request information may include information regarding the riding environment, such as air conditioning and driving speed, as described above. For example, the user may be able to set the vehicle interior temperature (high, low, etc.) and driving speed (slow, etc.) desired by the user as the vehicle dispatch request information.

The fare determination method in the dispatch request information is the fare determination method selected (specified) by the user. Fare determination methods include, for example, a pre-determined fare and a meter fare based on a fare meter. The meter fare is a fare determined according to the distance traveled from the time the passenger boards the taxi (the time the status of the taxi 12 is set to actual vehicle) to the time the taxi arrives at the destination (the time the status of the taxi 12 is set to paid). In contrast, a pre-determined fare is a fare that is determined at the time of boarding based on the distance traveled on the route on the map from the boarding point to the disembarking point (destination). When selecting a pre-determined fare, the user can select a driving route from among multiple candidates. When selecting a driving route, the fare for each driving route may be presented.

The payment method in the dispatch request information is the payment method selected by the user for the taxi 12 fare. Payment methods include, for example, in-car payment and online payment. In-car payment is a method of paying the fare directly to the driver, and also includes paying the fare by handing the driver a payment card such as a credit card instead of cash. Online payment is a method of paying the fare online using a payment card such as a credit card, debit card, prepaid card, or taxi-specific payment card (CAB CARD mobile) registered in the user application 21 of the user terminal 11. In the case of online payment, the user can select the card to use for payment from multiple cards registered in advance in the user application 21. Online payment is not limited to using a payment card, but also includes the use of various payment services (described below).

The integrated vehicle dispatch management device 14 (vehicle dispatch management unit 104) identifies and confirms the taxi 12 that the user has boarded using the vehicle information acquired from the user terminal 11. This enables the integrated vehicle dispatch management device 14 to manage the dispatch of the taxi 12 that the user has boarded based on the dispatch request information from the user terminal 11. The integrated vehicle dispatch management device 14 (vehicle dispatch management unit 104) also determines the driving route of the taxi 12 based on the vehicle status data of the identified taxi 12 and the destination included in the dispatch request information from the user terminal 11, and calculates (predicts) the time to arrive at the destination (arrival time), etc. However, if a pre-determined fare is selected as the fare determination method, the driving route and fare are determined in advance. The integrated vehicle dispatch management device 14 (vehicle dispatch management unit 104) supplies the dispatch request information to which the calculated driving route, arrival time, and other information has been added to the dispatch request information from the user terminal 11 to the driver terminal 33 and passenger terminal 15 of the identified taxi 12. As a result, the driver terminal 33 displays the dispatch request information set on the user terminal 11, etc., and the driver can know the destination and payment method requested by the user. Also, on the passenger terminal 15, as shown in FIG. 2, a message is displayed indicating that the destination setting and prepayment have been completed. Prepayment is a service in which, if the user selects online payment, payment is made at the time the user boards the vehicle. The message indicating that prepayment has been completed is displayed only when prepayment has been made.

When the completion of the destination setting, etc. is displayed on the standby screen 201 in FIG. 2, the screen 201 of the passenger terminal 15 switches to the request confirmation image in FIG. 3 (referred to as the request confirmation screen 201 in FIG. 3). The request confirmation screen 201 is a screen that indicates that the dispatch request has been notified to the dispatch integrated management device 14 and the driver terminal 33 by displaying user information such as the user's name, and that the dispatch request specified by the user has been confirmed and that the vehicle is heading to the destination. The request confirmation screen 201 may display details of information that has been set in advance as dispatch request information. For example, the specific destination that has been set, the set route, the desired air conditioning setting (high, low), the desired driving speed setting (slow, etc.), the desired driver's behavior while driving (do not talk, etc.), and the preferred genre of advertisements. The information that has been set in advance as dispatch request information may be confirmed by the user on the request confirmation screen 201 and changed by operating the user terminal 11 or the passenger terminal 15. When the dispatch request is confirmed, the operation information image of FIG. 4 (referred to as operation information screen 201 in FIG. 4) is displayed on the screen 201 of the passenger terminal 15. The operation information screen 201 displays the driving route to the destination and the arrival time on a map of the current location of the vehicle in which the user is riding, and the like. This operation information screen 201 is updated successively until the vehicle arrives at the destination. Since the passenger terminal 15 can share information with the user terminal 11 via the dispatch integrated management device 14, the screen 201 of the passenger terminal 15 can display content (websites, videos, application screens, advertisements, etc.) that matches the user's hobbies and preferences in addition to the operation information. Operations such as the selection of content to be displayed on the passenger terminal 15 can be performed on the user terminal 11, not limited to operations on the touch panel of the passenger terminal 15. In addition, before or after riding, the content to be displayed on the passenger terminal 15 and the setting of the riding environment as dispatch request information can be performed by operating the user terminal 11 or the passenger terminal 15. Among the dispatch request information, information related to the driver's operation (driving speed, etc.) is transmitted to the driver's terminal 33 via the dispatch integrated management device 14 and displayed, so that the driver can recognize it.

<Processing overview for a pick-up vehicle dispatch request in the taxi dispatch system 1>
In order to clarify the difference between the process of a dispatch request for a cruising use, waiting use, or virtual stop use in the taxi dispatch system 1 of Fig. 1 and the process of a dispatch request for a pick-up use, the process of the dispatch request for a pick-up use will be described first. Fig. 5 is a sequence diagram for explaining an outline of the process up to boarding when a user makes a dispatch request for a pick-up use in the taxi dispatch system 1 of Fig. 1. Note that the process by the user application 21, which is a dispatch application of the user terminal 11, will be simply described as the process of the user terminal 11, and the process by the driver application 51, which is a dispatch application of the driver terminal 33, will be simply described as the process of the driver terminal 33. Also, the process by the dispatch management unit 104 of the dispatch integration management device 14 will be simply described as the process of the dispatch integration management device 14.

The driver and driver terminal 33 shown in the sequence diagram of FIG. 5 are the driver and driver terminal 33 of the taxi 12 in which the user boarded. FIG. 5 shows existing processing, and in this technology, processing of the passenger terminal 15 that is characteristically used when boarding a taxi while cruising, waiting to be picked up, or using a virtual stop is omitted in FIG. 5. Vehicle status data of each taxi 12 is transmitted to the integrated dispatch management device 14 on a regular or irregular basis, and the integrated dispatch management device 14 is assumed to constantly be aware of the vehicle status data of each taxi 12.

In FIG. 5, in step S1, the user launches a vehicle dispatch application (user application 21) on the user terminal 11. In step S2, the user terminal 11 and the vehicle dispatch integrated management device 14 are connected for communication. In step S3, the user inputs (sets) vehicle dispatch request information for pick-up use into the user terminal 11. The vehicle dispatch request information to be input includes the boarding location, destination, payment method, etc. Note that in FIG. 5, a vehicle dispatch request is made without specifying a pick-up time. In step S4, the user performs a vehicle dispatch request operation on the user terminal 11. The vehicle dispatch request operation is an operation to request a vehicle dispatch from the vehicle dispatch integrated management device 14. In step S5, the user terminal 11 transmits the vehicle dispatch request information input in step S3 to the vehicle dispatch integrated management device 14.

In step S6, the vehicle dispatch integrated management device 14 searches for a candidate vehicle suitable for dispatch based on the dispatch request information acquired in step S5. In step S7, the vehicle dispatch integrated management device 14 transmits the dispatch request information acquired in step S5 to the driver terminal 33 of the candidate vehicle searched in step S6. This starts the request acceptance process in the driver terminal 33. In step S8, the driver terminal 33 displays the contents of the dispatch request information acquired in step S7 and a request acceptance screen on which the driver can select whether or not to accept the dispatch request. In step S9, the driver performs an operation to accept the request on the driver terminal 33. It is also possible for the driver not to accept the request. In step S10, the driver terminal 33 transmits a request acceptance notice to the vehicle dispatch integrated management device 14 notifying that the dispatch request has been accepted. In step S11, the vehicle dispatch integrated management device 14 determines the vehicle to be dispatched.

The processing of steps S7 to S11 is a processing of determining one vehicle (dispatch vehicle) to be dispatched from among the candidate vehicles that are suitable for dispatching in response to the dispatch request information from the user terminal 11 and have been entrusted with a dispatch request by the driver. For example, in the processing of steps S7 to S11, the dispatch integrated management device 14 searches for one optimal vehicle that can arrive at the boarding location the earliest or that is closest to the boarding location as a candidate vehicle, and if the dispatch request for that candidate vehicle is not accepted, it searches for the next optimal candidate vehicle and repeats this process to determine the dispatch vehicle until the driver accepts the dispatch request. Alternatively, the dispatch integrated management device 14 searches for multiple candidate vehicles that can be dispatched within a specified distance or a specified reachable time, notifies the driver terminal 33 of the dispatch request at the same time, and determines the optimal vehicle or the vehicle that has accepted the dispatch request the earliest from among the candidate vehicles that have been entrusted with a dispatch request. Candidate vehicles may be included in the list of candidates even if they are not available at the time of the dispatch request, if they are expected to become available within a specified time and meet the above conditions. Also, if the request is not accepted, vehicles that have not accepted the request may be excluded, and candidate vehicles may be searched for using the same search method or a different search method, and a dispatch request may be sent. However, the method by which the dispatch integrated management device 14 determines the vehicle to be dispatched is not limited to these examples.

In step S12, the vehicle dispatch integrated management device 14 transmits a vehicle dispatch confirmation notification to the driver terminal 33 of the confirmed vehicle, notifying the driver that the dispatch has been confirmed. In step S13, the vehicle dispatch integrated management device 14 transmits a vehicle dispatch confirmation notification to the user terminal 11. In step S14, the driver terminal 33 that received the vehicle dispatch confirmation notification in step S12 displays a vehicle dispatch confirmation message indicating that the driver's vehicle has been confirmed as the vehicle to be dispatched. In step S15, the user terminal 11 displays a vehicle dispatch confirmation message indicating that the vehicle to be dispatched has been confirmed.

In step S16, the driver who has been notified that the dispatch has been confirmed on the driver terminal 33 in step S14 sets the status (operating status (business status)) on the fare meter to pick up. Alternatively, the status on the fare meter may be automatically set to pick up when the dispatch is confirmed. In step S17, the vehicle dispatch integrated management device 14 notifies the driver terminal 33 that the status has been set to pick up. This causes the driver terminal 33 to start processing for picking up. In step S18, the vehicle dispatch integrated management device 14 creates operation information to be displayed on the user terminal 11 and the driver terminal 33 based on the vehicle movement data of the vehicle whose status has been set to pick up. The operation information includes information such as the boarding location, current location, destination, driving route to the boarding location, and required time (or arrival time) to the boarding location for a map of the area around the current location of the vehicle or the area around the current location of the user terminal 11. In step S19, the vehicle dispatch integrated management device 14 transmits the operation information created in step S18 to the driver terminal 33. In step S20, the vehicle dispatch integrated management device 14 transmits the operation information created in step S18 to the user terminal 11. In step S21, the driver terminal 33 displays the operation information acquired in step S19. In step S22, the user terminal 11 displays the operation information acquired in step S20. The processes of steps S18 to S22 are repeated until the vehicle arrives at the boarding location. When the vehicle arrives at the boarding location, the process proceeds to step S23.

In step S23, the vehicle dispatch integrated management device 14 transmits a boarding location arrival notification to the driver terminal 33, notifying the driver that the vehicle has arrived at the boarding location. In step S24, the vehicle dispatch integrated management device 14 transmits a boarding location arrival notification to the user terminal 11. In step S25, the driver terminal 33 displays a boarding location arrival notification to the driver that the vehicle has arrived at the boarding location. In step S26, the user terminal 11 transmits a boarding location arrival notification.

In step S27, the user boards the vehicle that has arrived. In step S28, the driver, having confirmed that the user has boarded in step S27, sets the status on the fare meter to actual vehicle. Alternatively, the status on the fare meter may be automatically set to actual vehicle when the vehicle dispatch is confirmed. In step S29, the vehicle dispatch integrated management device 14 notifies the driver terminal 33 that the status has been set to actual vehicle. This causes the driver terminal 33 to start processing for the actual vehicle. The subsequent processing is the same as the sequence diagram explained in the following Figure 6, so a description thereof will be omitted here.

<Processing for requesting a taxi for circulating or waiting in taxi dispatch system 1> Figure 6 is a sequence diagram that explains the processing when a user requests a taxi for circulating or waiting in taxi dispatch system 1 of Figure 1. Note that processing by user application 21, which is a dispatch application of user terminal 11, is simply described as processing by user terminal 11, and processing by driver application 51, which is a dispatch application of driver terminal 33, is simply described as processing by driver terminal 33. Processing by passenger application 121, which is a dispatch application of passenger terminal 15, is simply described as processing by passenger terminal 15. Processing by dispatch management unit 104 of integrated dispatch management device 14 is simply described as processing by integrated dispatch management device 14. Note that the driver, passenger terminal 15, and driver terminal 33 shown in the sequence diagram of Figure 6 are the driver, passenger terminal 15, and driver terminal 33 of taxi 12 that the user boarded. In addition, vehicle status data of each taxi 12 is transmitted to the vehicle dispatch integrated management device 14 on a regular or irregular basis, and the vehicle dispatch integrated management device 14 is configured to constantly monitor the vehicle status data of each taxi 12.

In FIG. 6, in step S51, the user boards a taxi 12 for cruising or waiting. In step S52, the user starts a dispatch application (user application 21) on the user terminal 11. In step S53, the user terminal 11 and the integrated dispatch management device 14 are connected for communication. As a result, the integrated dispatch management device 14 starts dispatch control for the user of the user terminal 11. In step S54, the user inputs dispatch request information for cruising or waiting, such as a destination and a payment method (fare determination method, payment method), to the user terminal 11. Note that steps S52 to S54 may be performed before boarding the taxi 12 as described above. The dispatch request information may also include information on the riding environment desired by the user, such as air conditioning and driving speed. In step S54, when the user sets the dispatch request information, the user terminal 11 may recommend a destination based on past data if there are multiple default destinations registered in advance. For example, the user terminal 11 learns from data on destinations associated with conditions such as the day of the week, time period, and weather when the user used the taxi 12 in the past (past user's taxi 12 usage history), and presents, as recommendations, destinations that are expected under the conditions when the dispatch request information was set. The user confirms the default destination presented as a recommendation, and performs an operation such as deciding or changing it to set the dispatch request information. In addition, in step S54, when the user sets the dispatch request information, it may be possible to specify a specific temperature for air conditioning, and to set the air conditioning in direct cooperation with the in-vehicle air conditioning system. The settings of the dispatch request information related to air conditioning may be automatically changed depending on the season, weather, and time period. The user terminal 11 may learn the optimal air conditioning from the air conditioning settings when the user used the taxi 12 in the past, and automatically set the air conditioning based on the learning results. In addition, the user terminal 11 may use an IoT (Internet of Things) mobile device (e.g., a smart watch, etc.), or may be configured to link a smartphone with an IoT mobile device. In this case, data on the user's body temperature, heart rate, etc., measured using an IoT (Internet of Things) mobile device can be acquired by a smartphone, and the air conditioning settings in the vehicle dispatch request information can be automatically changed by the smartphone's user application 21.

In step S55, the user holds the user terminal 11 over the passenger terminal 15. In step S56, the user terminal 11 and the passenger terminal 15 are communicatively connected via NFC. In step S57, the passenger terminal 15 transmits vehicle information identifying the user's vehicle to the user terminal 11. The vehicle information may be acquired by the user terminal 11 using a two-dimensional code or the like. In step S58, the user terminal 11 transmits information including the dispatch request information input (or set) in step S54 and the vehicle information acquired in step S57 as dispatch request information to the dispatch integrated management device 14. Note that in steps S57 and S58, the roles of the user terminal 11 and the passenger terminal 15 may be reversed. That is, in step S57, the user terminal 11 connected via NFC in step S56 transmits the dispatch request information input (or set) in step S54 to the passenger terminal 15, and in step S58, the passenger terminal 15 transmits the dispatch request information acquired in step S57 and information including the vehicle information to the dispatch integration management device 14 as dispatch request information. In step S59, the dispatch integration management device 14 confirms the vehicle in which the user boarded based on the dispatch request information acquired in step S58, and creates dispatch request information such as the current location, destination, driving route to the destination, fare in the case of a pre-determined fare, payment reservation (details in the case of online payment, etc.) based on the vehicle status data of the vehicle. In step S60, the dispatch integration management device 14 transmits the dispatch request information created in step S59 to the driver terminal 33. This starts the request acceptance process in the driver terminal 33.

In step S61, the vehicle dispatch integrated management device 14 transmits the dispatch request information created in step S59 to the passenger terminal 15. Note that the passenger terminal 15 is executing processing for when the vehicle is empty. In step S62, the driver terminal 33 displays the contents of the dispatch request information acquired in step S60 and a request acceptance screen on which the driver can select whether or not to accept the dispatch request. In step S63, the driver performs an operation to accept the request on the driver terminal 33. Note that the driver can also not accept the request. In step S64, the driver terminal 33 transmits a request acceptance notice to the vehicle dispatch integrated management device 14 notifying that the dispatch request has been accepted. In step S65, the vehicle dispatch integrated management device 14 transmits a request acceptance notice to the passenger terminal 15 notifying that the dispatch request has been accepted. In step S66, the vehicle dispatch integrated management device 14 transmits a request acceptance notice to the user terminal 11 notifying that the dispatch request has been accepted. In step S67, the passenger terminal 15 displays that the dispatch request has been accepted. If the driver does not accept the request in step S63, the user is notified of this and gets off the vehicle. The processes in steps S61 to S67 may be omitted.

In step S68, the driver sets the status on the fare meter to actual vehicle. Regardless of the driver's setting, the driver terminal 33 or the vehicle dispatch integrated management device 14 and the fare meter may be connected to communicate with each other by any method, and the status may be automatically changed to actual vehicle. When the status is set to actual vehicle in step S68, the process proceeds to step S69. In step S69, the vehicle dispatch integrated management device 14 notifies the driver terminal 33 that the status has been set to actual vehicle. This starts the process for the actual vehicle in the driver terminal 33. In step S70, the vehicle dispatch integrated management device 14 notifies the passenger terminal 15 that the status has been set to actual vehicle. This starts the process for the actual vehicle in the passenger terminal 15. In step S71, the vehicle dispatch integrated management device 14 creates operation information based on the vehicle status data. The operation information includes information such as the current location, destination, route to the destination, and time required to reach the destination (or arrival time at the destination) on a map of the area around the vehicle's current location. In step S72, the vehicle dispatch integrated management device 14 transmits the operation information created in step S71 to the passenger terminal 15. In step S73, the vehicle dispatch integrated management device 14 transmits the operation information created in step S71 to the driver terminal 33. In step S74, the passenger terminal 15 displays the operation information acquired in step S72. In step S75, the driver terminal 33 displays the operation information acquired in step S73. The processes of steps S71 to S75 are repeated until the vehicle arrives at the destination. When the vehicle arrives at the destination, the process proceeds to step S76. The operation information may be displayed on the user terminal 11. That is, the operation information created in step S71 is transmitted directly to the user terminal 11 or to the user terminal 11 via the passenger terminal 15, and the user terminal 11 displays the acquired operation information. This allows the user to check the operation information on the user terminal 11 at hand.

In step S72, the vehicle dispatch integrated management device 14 can transmit information on any content other than the operation information to the passenger terminal 15 and display it. For example, the vehicle dispatch integrated management device 14 can transmit content specified by the user through the operation of the user terminal 11 or the like, or content set in advance as vehicle dispatch request information, to the passenger terminal 15 and display it. The vehicle dispatch integrated management device 14 can display the screen of the user terminal 11 on the screen of the passenger terminal 15 by mirroring with the screen of the user terminal 11. This allows the user to view the continuation of a video that was being viewed on the user terminal 11 on the passenger terminal 15. In addition to videos, multiple contents and applications available on the user terminal 11, such as online conference applications, electronic books, and music management applications, can be displayed on the screen of the passenger terminal 15 by mirroring. In this case, it is desirable to be able to set whether or not to permit mirroring for each individual content or application by setting the user application 21. In addition, before starting mirroring, a display of whether or not to permit mirroring may be displayed on the screen of the user terminal 11 or the passenger terminal 15 to the user, so that the user can determine in advance whether or not to perform mirroring. In addition, the dispatch integrated management device 14 can set advertisements displayed on the passenger terminal 15 to a preferred genre previously set in the user terminal 11 as dispatch request information, etc. The dispatch integrated management device 14 can also set the use of various displays on the passenger terminal 15 as a premium user limited service (service limited to paid users). Using a sensor (not shown) such as a camera mounted on the taxi 12, the dispatch integrated management device 14 or the passenger terminal 15 can generate and display any content based on information acquired from the sensor such as a camera. As an example of the content, an image of the surroundings of the taxi acquired from a sensor such as a camera may be displayed as it is, or content information may be superimposed on the image of the surroundings of the taxi using AR (Augmented Reality) or the like, as shown in FIG. 7. The content information to be superimposed and displayed may be information on shops and roads included in the image of the surroundings of the taxi, or information indicating the distance to the destination. In this case, the store and road information may be information on the map application of the user terminal 11, map information (map) stored in the dispatch integrated management device 14, or other map information acquired from outside. The content information to be displayed in a superimposed manner may be selectable by the user through an operation on the passenger terminal 15. When the user selects the content to be displayed in a superimposed manner through an operation on the passenger terminal 15, information related to the selected content may be further displayed. For example, when the content to be displayed in a superimposed manner is information related to a store and the content is selected, information related to the store is displayed. If the store is a ramen shop, the store name, menu items, and reviews of the ramen shop may be displayed using an application on the user terminal 11 or other information acquired from outside. The store may also be changed as a destination. The content to be displayed in a superimposed manner may be filtered according to specific conditions, such as by a user's setting of the user application 11. For example, if a user sets a restaurant as the content to be displayed in a superimposed manner, stores that fall under other categories are not displayed as the content to be displayed in a superimposed manner, and only restaurants are displayed. Furthermore, only restaurants that fall under a specific type may be displayed from restaurants. Such a filter may be set by the user through an operation on the user terminal 11 as dispatch request information, or may be set by an operation on the passenger terminal 15 during a ride.

In step S76, the driver sets the status of the fare meter to payment. In step S77, the dispatch integrated management device 14 creates payment information. The payment information differs depending on the payment method (fare determination method and payment method) in the dispatch request information set by the user. For example, if the fare determination method is the meter fare, the fare obtained from the fare meter is included in the payment information. For example, if the payment method is online payment, the payment information includes information specifying the payment service such as a payment card used for online payment and the usage fee. In step S78, the dispatch integrated management device 14 transmits the arrival and payment information to the passenger terminal 15. In step S79, the dispatch integrated management device 14 transmits the arrival and payment information to the driver terminal 33. In step S80, the passenger terminal 15 displays the arrival and payment information. The passenger terminal 15 also displays a payment acceptance screen for accepting payment of the displayed usage fee. In step S81, the driver terminal 33 displays the arrival and payment information. In step S82, the user performs an operation to accept the payment acceptance screen displayed on the passenger terminal 15 in step S80.

In step S83, the passenger terminal 15 transmits to the vehicle dispatch integrated management device 14 an acceptance notification indicating that the payment was accepted in step S82. In step S84, the vehicle dispatch integrated management device 14 executes a payment process. In the payment process, for example, the vehicle dispatch integrated management device 14 communicates with a payment server and transmits to the payment server information on the payment service used in the online payment and payment information such as the usage fee. If the payment is made properly, the payment server notifies the vehicle dispatch integrated management device 14 to that effect. In step S85, the vehicle dispatch integrated management device 14 transmits to the passenger terminal 15 a payment completion notification indicating that the payment has been completed. In step S86, the passenger terminal 15 displays a payment completion message indicating that the payment has been completed. In step S87, the vehicle dispatch integrated management device 14 transmits a payment completion message to the user terminal 11. In step S88, the vehicle dispatch integrated management device 14 transmits a payment completion message to the driver terminal 33. In step S89, the user terminal 11 displays a payment completion message. In step S90, the driver terminal 33 displays the completion of payment. When the user confirms that the payment is completed in step S86, the process proceeds to step S91. Note that some of the payment processing may be performed before or during the ride. In this case, the user terminal 11 transmits information on the payment service used in the online payment, or information on the payment consent in advance, to the vehicle dispatch integrated management device 14 in advance. The consent to the payment may be made after the usage fee is determined. After the usage fee is determined, the vehicle dispatch integrated management device 14 connects to the payment server and transmits information on the payment service used in the online payment and payment information such as the usage fee to the payment server. When the user consents to the payment in advance, it is desirable to determine the fare in advance using a fare calculation based on a pre-determined fare, or, when a meter fare is used, to present the user with an approximate fare by the same method as the pre-determined fare or any other method. In this way, by performing some of the payment processing before or during the ride, some or all of the actions required of the user after arriving at the destination are omitted, improving the user's convenience.

In step S91, the user gets off the vehicle. In step S92, the driver sets the fare meter status to "empty". The fare meter status may be automatically set to "empty". In step S93, the vehicle dispatch integrated management device 14 notifies the passenger terminal 15 that the status is "empty". This causes the passenger terminal 15 to start processing when the vehicle is empty. In step S94, the vehicle dispatch integrated management device 14 notifies the driver terminal 33 that the status is "empty". This causes the passenger terminal 15 to start processing when the vehicle is empty.

According to the above process for a request for dispatching a taxi for cruising or waiting to be picked up in FIG. 6, even if the user boards a taxi 12 for cruising or waiting to be picked up, the user can easily make a request for dispatching a taxi using the user application 21. That is, even if the user boards a taxi 12 for cruising or waiting to be picked up, the integrated dispatch management device 14 can identify the taxi 12 the user boarded using the vehicle information (specific information) by simply holding the user terminal 11 over the passenger terminal 15. In addition, the user can make the contents of the dispatch request, such as the destination, using the user application 21 in the same way as in the case of a request for dispatching a taxi for picking up, so there is no need to verbally convey the contents of the dispatch request to the driver, improving convenience when boarding a taxi 12 for cruising or waiting to be picked up. The process for a request for dispatching a taxi for cruising or waiting to be picked up can be appropriately applied as a request for dispatching a taxi for using a virtual stop or a request for dispatching a taxi for picking up.

<Taxi dispatch request when using virtual stop in taxi dispatch system 1>
Fig. 8 is an example of a screen displayed on the user terminal 11 when a user makes a dispatch request using a virtual stop in the taxi dispatch system 1 of Fig. 1. In Fig. 8, a dispatch request image using a virtual stop by the user application 21 (referred to as a dispatch request screen 251 in Fig. 8) is displayed on a screen 251 of the display unit of the user terminal 11.

The dispatch request screen 251 has a virtual stop display section 261, a dispatch request operation section 262, a current location setting section 263, a destination setting section 264, a fare determination method setting section 265, a payment method setting section 266, a dispatch setting section 267, request

method selection sections

268 and 269, etc.

The virtual stop display unit 161 displays a map of the area around the current location of the user terminal 11. A current location mark 271, a virtual stop mark 272, a virtual stop route 273, taxi marks 274A to 274C, a taxi route 275, and the like are displayed on the map. The current location mark 271 indicates the current location of the user terminal 11. The virtual stop mark 272 indicates the location of the virtual stop. The virtual stop route 273 indicates the travel route (shortest walking route) from the current location of the user terminal 11 to the virtual stop. The taxi marks 274A to 274C indicate the location of a taxi 12 (a taxi 12 whose status is empty) that exists in the area around the current location of the user terminal 11. This is not limited to taxis 12 whose status is empty, and may similarly indicate the location of a taxi whose status may soon become empty, for example, after reaching the destination and being processed for disembarking. The taxi route 275 shows the planned driving route of the taxi 12 (taxi 12 with taxi mark 274A) that is optimal for boarding at the virtual stop among the taxis 12 shown by the taxi marks 274A to 274C. Detailed information about the driver and taxi company is additionally displayed on the taxi mark 274A of the optimal taxi 12.

The dispatch request operation unit 262 accepts user operations (dispatch request operations) when notifying the vehicle dispatch integrated management device 14 of a dispatch request. An operation bar 262A is displayed on the dispatch request operation unit 262. When the user slides the operation bar 262A to the right, the user application 21 supplies (sends) a dispatch request notification to the vehicle dispatch integrated management device 14. When a dispatch request notification is notified to the vehicle dispatch integrated management device 14 by operating the operation bar 262A, the dispatch request operation unit 262 displays the time required to travel (walk) from the current location of the user terminal 11 to the virtual stop.

The current location setting unit 263 is an input unit that sets an address indicating the current location of the user terminal 11. If the user terminal 11 is equipped with a GPS (Global Positioning System), the address of the location determined by the GPS is automatically set. It is also possible for the user to manually input the address by specifying a location on the map of the virtual stop display unit 161, etc.

The destination setting unit 264 is an input unit for setting the desired destination (drop-off point) of the taxi 12 by the user. The address of the destination to be set in the destination setting unit 264 is manually input by the user, for example, by specifying a location on the map of the virtual stop display unit 161.

The fare determination method setting unit 265 is a setting unit that sets the fare determination method (meter fare, pre-determined fare, etc.). When the fare determination method setting unit 265 sets a pre-determined fare, the user is presented with multiple candidate driving routes from the virtual stop to the destination and fares (fees) according to the driving distance of each driving route, etc., and the user may be able to select a driving route or a fee from among these candidates, or the shortest driving route or the cheapest fee may be automatically set.

The payment method setting unit 266 is a setting unit that sets whether payment is to be made in the vehicle or online. In the case of online payment, the user can select from payment cards registered in the user application 21 of the user terminal 11, such as credit cards, debit cards, prepaid cards, or taxi-specific payment cards (CAB CARD Mobile), as well as other payment services.

The dispatch setting unit 267 is a setting unit that sets which dispatch request to apply among dispatch requests with different setting contents that have been registered in advance in the user application 21. For example, by registering multiple locations (addresses) as destinations (drop-off locations), the destination can be set in the destination setting unit 264 by selecting a destination from among them.

The request

method selection units

268 and 269 are selection units for selecting whether to make a request for dispatch immediately or to request a pick-up at a specified time at a specified boarding location (dispatch reservation). Although omitted in FIG. 8, the dispatch request screen on the user terminal 11 can be switched to a screen for setting information required for making a dispatch request for a pick-up service that specifies a pick-up time, a dispatch request for a pick-up service that does not specify a pick-up time (a time with the shortest possible waiting time), a dispatch request for a cruising service or a waiting service, and a dispatch request for a virtual stop. For example, when making a dispatch request for a virtual stop, the user selects the request method selection unit 268. The dispatch request screen 251 in FIG. 8 is a screen when the request method selection unit 268 is selected. When there is a long queue of passengers waiting to be picked up and there are only a few waiting taxis 12, the user may be able to board a taxi 12 earlier by making a dispatch request for a virtual stop. Also, in order to detect whether or not there is a queue of passengers waiting to be picked up, a sensor that detects the presence or absence of a queue may be installed at the location where the passengers are waiting to be picked up (such as a taxi stop), and the detection result of the sensor may be transmitted to the user terminal 11. In addition to the presence or absence of a queue, the waiting time for the passengers waiting to be picked up may be estimated and displayed on the user terminal 11.

Furthermore, when a vehicle dispatch request is made by the user terminal 11, the waiting time until boarding for each of the vehicle dispatch requests using pick-up, cruising, waiting, and virtual stop may be displayed at the same time. Alternatively, only the setting screen of the vehicle dispatch request with the shortest waiting time until boarding may be displayed on the user terminal 11. The user terminal 11 may display the expected time required until boarding (waiting time) for each of the multiple types of vehicle dispatch requests and allow the user to select one. Furthermore, the user terminal 11 may display the user's preferred vehicle dispatch request method set in advance as a default, while calculating the waiting time until boarding for other vehicle dispatch request methods, and displaying that fact if the waiting time is less than a certain time that can be set by the user (user setting, for example, less than 5 minutes).

<Processing in case of dispatch request using virtual stop in taxi dispatch system 1>
Fig. 9 is a sequence diagram for explaining the processing up to boarding when a user makes a taxi dispatch request using a virtual stop in the taxi dispatch system 1 of Fig. 1. Note that the processing by the user application 21, which is a dispatch application of the user terminal 11, will be simply described as the processing of the user terminal 11, and the processing by the driver application 51, which is a dispatch application of the driver terminal 33, will be simply described as the processing of the driver terminal 33. Also, the processing by the dispatch management unit 104 of the dispatch integration management device 14 will be simply described as the processing of the dispatch integration management device 14.

The driver and driver terminal 33 shown in the sequence diagram of FIG. 9 are the driver and driver terminal 33 of the taxi 12 that the user plans to board at the virtual stop. In addition, in the process up to boarding using a virtual stop, the passenger terminal 15 simply displays the standby screen of FIG. 2, so the processing of the passenger terminal 15 is omitted in FIG. 9. Although omitted in FIG. 9, the vehicle status data of each taxi 12 is transmitted to the vehicle dispatch integrated management device 14 on a regular or irregular basis, and the vehicle dispatch integrated management device 14 is constantly aware of the vehicle status data of each taxi 12.

9, in step S201, the user launches a dispatch application (user application 21) on the user terminal 11. In step S202, the user terminal 11 and the dispatch integrated management device 14 are connected for communication. As a result, the dispatch integrated management device 14 starts dispatch control for the user of the user terminal 11. In step S203, the user inputs virtual stop dispatch request information to the user terminal 11. A dispatch request using a virtual stop is referred to as a virtual stop dispatch request, etc. The virtual stop dispatch request information input by the user is the destination (drop-off point), payment method (fare determination method, payment method), etc., among the information set on the dispatch request screen 251 of FIG. 8. In step S204, the user performs a virtual stop dispatch request operation on the user terminal 11. The virtual stop dispatch request information is an operation of sliding the operation bar 262A in the dispatch request operation section 262 of the dispatch request screen 251 of FIG. 8, and is an operation of requesting dispatch to the dispatch integrated management device 14. In step S205, the user terminal 11 transmits virtual stop dispatch request information to the dispatch integration management device 14. The virtual stop dispatch request information transmitted to the dispatch integration management device 14 includes information such as the current location of the user terminal 11 in addition to the virtual stop dispatch request information set in step S203.

In step S206, the vehicle dispatch integrated management device 14 determines the location of the virtual stop and the optimal vehicle for the user to board based on the current location of the user terminal 11 of the virtual stop dispatch request information and the vehicle status data of each vehicle. For example, the vehicle dispatch integrated management device 14 analyzes past vehicle status data and obtains locations where there are many pedestrian rides as statistical data. Then, the vehicle dispatch integrated management device 14 determines the location where the travel time from the current location of the user terminal 11 is the shortest as the virtual stop from the locations where there are many pedestrian rides, and detects the optimal vehicle with a status of vacant that arrives (passes) at the virtual stop in the shortest time. Alternatively, without being limited to the case of using such statistical data, the vehicle dispatch integrated management device 14 determines the optimal vehicle from vehicles with a status of vacant that exist around the current location of the user based on the current location and destination of the user (user terminal 11), the vehicle status data of each vehicle, etc. For example, the proximity of the vehicle's travel route to the user's current location, the proximity of the vehicle's current direction to the destination, whether the virtual stop is located on the opposite side of the lane or in front of the user's current location, etc. are taken into consideration. If the virtual stop is located on the opposite side of the lane, movement due to a traffic light is also taken into consideration. However, in consideration of usability, it is not desirable to cross as large a lane as possible. In addition, the road conditions around the user's current location (presence or absence of one-way streets, congestion, no-stop zones for taxis, etc.) may be taken into consideration. The integrated vehicle dispatch management device 14 determines the position of the virtual stop based on the determined optimal vehicle travel route and the user's current location. In addition, the determined position of the virtual stop may be corrected by the user's operation of the user terminal 11 or the driver of the taxi 12's operation of the driver terminal 33. The determined virtual stop is not necessarily set to a suitable location, or may be set to a location that the user or taxi cannot enter due to some bug, etc., and in such a case, convenience for both parties can be provided by making the virtual stop correctable. Furthermore, if the determined virtual stop is revised, the revised information may be transmitted to the integrated vehicle dispatch management device 14, stored by the integrated vehicle dispatch management device 14, and taken into consideration when determining a virtual stop thereafter. In this way, the accuracy of determining the virtual stop and the convenience of the user and the taxi can be improved from the next time onwards.

In step S207, the vehicle dispatch integrated management device 14 creates virtual stop dispatch information. In addition to the virtual stop dispatch request information acquired in step S205, the virtual stop dispatch information includes information necessary for displaying the virtual stop display unit 261 and the dispatch request operation unit 262 in the dispatch request screen 251 in FIG. 8, that is, a map of the area around the current location of the user terminal 11, the location of the virtual stop, the travel time (walking time) and route from the user's current location to the virtual stop, the location of the taxi 12 with a status of vacant that exists around the user's current location, and the driving route of the taxi 12 that passes through the virtual stop. In step S208, the vehicle dispatch integrated management device 14 transmits the virtual stop dispatch information created in step S207 to the user terminal 11. In step S209, the vehicle dispatch integrated management device 14 transmits the virtual stop dispatch information created in step S207 to the driver terminal 33. In addition, the virtual stop dispatch information may be transmitted and displayed not only to the optimal vehicle detected (determined) in step S206, but also to the driver terminal 33 of a vehicle that passes the virtual stop within a certain time or a vehicle that exists within a certain distance from the virtual stop. In step S210, the user terminal 11 displays the virtual stop dispatch information acquired in step S208. In step S211, the driver terminal 33 displays the virtual stop dispatch information acquired in step S208. The processes in steps S206 to S211 are repeated until the vehicle arrives at the virtual stop, and when the vehicle arrives at the virtual stop, the process proceeds to step S212. In addition, when the user is unlikely to be able to board at the virtual stop based on the location of the virtual stop, the travel time (walking time) and route from the user's current location to the virtual stop, the location of the taxi 12 with a status of vacant around the user's current location, etc., or when the time required to board is expected to be longer than a predetermined time, the user application 11 may present another dispatch method to the user.

In step S212, the integrated vehicle dispatch management device 14 sends a virtual stop arrival notification to the user terminal 11, indicating that the vehicle has arrived at the virtual stop. In step S213, the integrated vehicle dispatch management device 14 sends a virtual stop arrival notification to the driver terminal 33. In step S214, the user terminal 11 displays the arrival of the vehicle at the virtual stop. In step S215, the driver terminal 33 displays the arrival of the vehicle at the virtual stop. In step S216, the user stops the vehicle passing through the virtual stop by signaling with a hand or the like, as when using a cruising service, and gets in. In step S217, the driver sets the status of the fare meter to the actual vehicle. After the user gets in at step S216, the processing from step S52 onwards in Figure 6 is performed in the same manner. However, since the virtual stop dispatch request information has already been sent from the user terminal 11 to the dispatch integrated management device 14, the passenger terminal 15, and the driver terminal 33, it is also possible to use the virtual stop dispatch request information as the dispatch request information in FIG. 6.

According to the processing for a dispatch request using a virtual stop in FIG. 9, unlike boarding a vehicle using a pick-up service, the dispatch processing does not begin with the user and the taxi 12 already matched, so as with a cruising service, no pick-up fee is incurred, and there is a higher chance of boarding a taxi 12 sooner than with a normal cruising service or waiting service or a pick-up service.

<Functional block diagram of taxi dispatch system 1>
Fig. 10 is a block diagram showing an example of the functional configuration of the taxi dispatch system 1 of Fig. 1. In Fig. 10, the user terminal 11 has a vehicle information acquisition unit 301, a dispatch request basic information setting unit 302, a payment information setting unit 303, a driving mode setting unit 304, an advertisement setting unit 305, and a mirroring setting unit 306. The dispatch integration management device 14 has a dispatch request processing unit 321, an operation information processing unit 322, a payment processing unit 323, a driving mode processing unit 324, an advertisement processing unit 325, and a mirroring processing unit 326. The processes of the dispatch request processing unit 321, the operation information processing unit 322, the payment processing unit 323, the driving mode processing unit 324, the advertisement processing unit 325, and the mirroring processing unit 326 can be mainly performed by the dispatch management unit 104 (see Fig. 1) of the dispatch integration management device 14.

The passenger terminal 15 has a dispatch request information display unit 341, an operation information display unit 342, a payment information display unit 343, a driving mode display unit 344, an advertisement display unit 345, and a mirroring display unit 346. The processing of each of the dispatch request information display unit 341, the operation information display unit 342, the payment information display unit 343, the driving mode display unit 344, the advertisement display unit 345, and the mirroring display unit 346 may be mainly performed by the passenger app 121 of the passenger terminal 15. The driver terminal 33 has a dispatch request information display unit 361, an operation information display unit 362, a payment information display unit 363, and a driving mode display unit 364. The processing of each of the dispatch request information display unit 361, the operation information display unit 362, the payment information display unit 363, and the driving mode display unit 364 may be performed by the driver app 51 of the driver terminal 33.

Function blocks 301 to 306, 321 to 326, 341 to 346, and 361 to 364 shown in the user terminal 11, the vehicle dispatch integrated management device 14, the passenger terminal 15, and the driver terminal 33 in FIG. 10 may be possessed by a device different from that shown in FIG. 10 among the user terminal 11, the vehicle dispatch integrated management device 14, the passenger terminal 15, and the driver terminal 33, or multiple devices may perform the processing of one function block in a distributed manner. As an example, the processing of the vehicle dispatch request basic information setting unit 302, the payment information setting unit 303, the driving mode setting unit 304, the advertisement setting unit 305, and the mirroring setting unit 306 of the user terminal 11 may be performed in a distributed manner by the user terminal 11 and the vehicle dispatch integrated management device 14, respectively. For example, the user application 21 may cause the vehicle dispatch management unit 104 (see FIG. 1) of the vehicle dispatch integrated management device 14 to carry out these processes via an API, thereby causing the user terminal 11 to operate as a device that inputs and outputs various types of information.

<User terminal 11>
In the user terminal 11, the vehicle information acquisition unit 301 acquires vehicle information that identifies the vehicle in which the user boarded from the passenger terminal 15, and supplies it to the vehicle dispatch integration management device 14 (see steps S57 and S58 in FIG. 6). The reason why the user terminal 11 acquires vehicle information is that the vehicle dispatch integration management device 14 identifies the vehicle in which the user boarded by supplying the vehicle information acquired by the user terminal 11 to the vehicle dispatch integration management device 14. This allows the vehicle dispatch integration management device 14 to identify the vehicle in which the user boarded, and the passenger terminal 15 and driver terminal 33 of that vehicle. As described above, the dispatch request includes a dispatch request for pick-up use with a designated pick-up time, a dispatch request for pick-up use without a designated pick-up time, a dispatch request for cruising use, a dispatch request for waiting use, and a dispatch request for virtual stop use. A dispatch request for pick-up use with a designated pick-up time corresponds to a so-called vehicle dispatch reservation, and a dispatch request for pick-up use without a designated pick-up time corresponds to a case where an immediate pick-up is desired. In the case of a dispatch request for pick-up use, the vehicle in which the user boards is specified, so it is not necessarily required for the vehicle information acquisition unit 301 to acquire vehicle information and supply it to the vehicle dispatch integration management device 14. In the case of a dispatch request for cruising use, waiting use, and virtual stop use, the vehicle in which the user boards is not specified, so the vehicle information acquisition unit 301 acquires vehicle information and supplies it to the vehicle dispatch integration management device 14, for example, as information included in the dispatch request information.

In this embodiment, the vehicle dispatch integrated management device 14 is based on the premise that the vehicle, the passenger terminal 15, and the driver terminal 33 are associated in advance. For example, the passenger terminal 15 of the vehicle in which the user is riding may acquire dispatch request information including user information from the user terminal 11 and supply it to the vehicle dispatch integrated management device 14. In this case, the passenger terminal 15 can identify the vehicle in which the user is riding, and the passenger terminal 15 and the driver terminal 33 of the vehicle by supplying information that identifies the vehicle itself (vehicle information) to the vehicle dispatch integrated management device 14 along with the dispatch request information. In addition, the information that the passenger terminal 15 acquires from the user terminal 11 and supplies to the vehicle dispatch integrated management device 14 may not be dispatch request information, but may be only user information or information that identifies the user terminal 11, and the dispatch request information may be supplied from the user terminal 11 to the vehicle dispatch integrated management device 14. Therefore, the vehicle information acquisition unit 301 may be included in the passenger terminal 15 or the driver terminal 33 as a vehicle information acquisition unit that acquires information (vehicle information) for identifying the vehicle in which the user is riding. The vehicle information may be any of information that identifies the vehicle, information that identifies the passenger terminal 15, information that identifies the driver terminal 33, information that identifies the user terminal 11 of the user in the vehicle, or information that identifies the user.

The vehicle information acquired by the vehicle information acquisition unit 301 is not limited to NFC, and may be acquired using short-range wireless communication in the broad sense. For example, the vehicle information may be acquired by connecting the user terminal 11 and the passenger terminal 15 (or the driver terminal 33) via Bluetooth (registered trademark). Similarly, dispatch request information and the like supplied from the user terminal 11 to the vehicle dispatch integrated management device 14 may be supplied to the vehicle dispatch integrated management device 14 via the passenger terminal 15 through short-range wireless communication of any standard between the user terminal 11 and the passenger terminal 15 (or the driver terminal 33).

The dispatch request basic information setting unit 302 sets basic information (basic information) required for a dispatch request, and supplies the set basic information to the dispatch integrated management device 14 as basic information included in the dispatch request information (see steps S3 to S5 in FIG. 5, steps S54 and S56 in FIG. 6, and steps S203 to S205 in FIG. 9). The dispatch request basic information setting unit 302 sets basic information according to the type of dispatch request. The dispatch request basic information set by the dispatch request basic information setting unit 302 includes any one of user information identifying the user, current location, boarding location (pick-up location), desired pick-up time (pick-up time), and destination. In the case of a dispatch request for pick-up use with a specified pick-up time, the basic information includes user information, boarding location, pick-up time, and destination. In the case of a dispatch request for pick-up use without a specified pick-up time, the basic information includes user information, boarding location, and destination. In the case of a dispatch request for cruising use and waiting use, the basic information includes user information and destination. In the case of a vehicle dispatch request using a virtual stop, basic information includes user information, current location (current location of the user terminal 11), and destination.

These basic information may be input and set by the user when making a request for dispatch, or may be selected by the user from multiple candidates registered in advance when making a request for dispatch. In addition, immutable information such as user information does not need to be set by the user for each dispatch request, and may be set automatically, or may be supplied to the dispatch integrated management device 14 at a different time from the other basic information (such as when the user terminal 11 and the dispatch integrated management device 14 are connected). The dispatch request information is information indicating the contents of the dispatch request, and may include various information other than the basic information. These dispatch request information may be supplied to the dispatch integrated management device 14 at different times, rather than simultaneously. In addition, with regard to the boarding location, the current location of the user terminal 11 may be automatically set by the GPS function of the user terminal 11.

The dispatch request basic information setting unit 302 displays a map of the current location of the user terminal 11 on the screen of the user terminal 11, in addition to the setting unit where the user inputs or selects dispatch request information, and displays the location of the taxi 12 traveling within the displayed map range as a dispatch request screen. The dispatch request basic information setting unit 302 acquires map data on the dispatch request screen, for example, from a map site or from the dispatch integrated management device 14. The location and range of the map displayed on the screen of the user terminal 11 can be changed by the user's operation. The dispatch request basic information setting unit 302 acquires vehicle status data of the taxi 12 traveling within the map range from the dispatch integrated management device 14 (vehicle status data management unit 101 in FIG. 1), and reflects information such as the status, current location, and traveling direction included in the vehicle status data in the display of the vehicle on the map on the dispatch request screen. In addition, when setting the boarding location or destination, the user may specify a location on the map on the dispatch request screen, and the address corresponding to the specified location on the map may be automatically set.

In the case of a vehicle dispatch request using a virtual stop, when the user terminal 11 transmits vehicle dispatch request information using the virtual stop to the vehicle dispatch integrated management device 14 (see step S205 in FIG. 9), the vehicle dispatch integrated management device 14 (vehicle dispatch request processing unit 321) calculates the position of the virtual stop, selects the optimal vehicle that can be boarded at the virtual stop, calculates the walking route and travel time from the current location of the user (user terminal 11) to the virtual stop, calculates the driving route and driving time (arrival time) from the virtual stop to the destination, calculates the waiting time until boarding (boarding time for the taxi 12), and transmits vehicle dispatch information (virtual stop vehicle dispatch information) including the results to the user terminal 11 (see steps 206 to S208 in FIG. 9). The vehicle dispatch request basic information setting unit 302 reflects the vehicle dispatch information from the vehicle dispatch integrated management device 14 on the vehicle dispatch request screen. As a result, the position of the virtual stop, etc. are displayed on the map as in the vehicle dispatch request screen 251 shown in FIG. 8.

The payment information setting unit 303 sets the payment method and supplies the set payment method to the dispatch integrated management device 14 as information included in the dispatch request information (see steps S3 to S5 in FIG. 5, steps S54 and S56 in FIG. 6, and steps S203 to S205 in FIG. 9). The payment method set by the payment information setting unit 303 includes the setting of a fare determination method and a payment method. As described above, the fare determination method includes a determination method based on a pre-determined fare and a determination method based on a meter fare based on a fare meter. The pre-determined fare is a fare that is determined in advance based on the travel distance of the taxi 12's travel route on the map from the boarding point to the disembarking point (destination). The meter fare is a fare that is determined by the fare meter according to the actual travel distance of the taxi 12 from the boarding point to the destination. The user selects which fare determination method to use, the pre-determined fare or the meter fare. In addition, when the pre-determined fare is selected, the payment information setting unit 303 may adopt, for example, the following first or second method as a fare setting method. In the first method, the payment information setting unit 303 automatically determines the driving route of the taxi 12 and sets the fare according to the driving distance of the driving route as the pre-determined fare. In the second method, the payment information setting unit 303 presents a plurality of different driving routes of the taxi 12 to the user and sets the fare according to the driving distance of the driving route selected by the user as the pre-determined fare. In both the first and second methods, the calculation of the driving route and fare of the taxi 12 may be performed by any of the user terminal 11, the vehicle dispatch integrated management device 14, the passenger terminal 15, and the driver terminal 33.

The candidate driving routes are driving routes from the boarding location to the destination, and the destination when calculating the driving route is the destination set by the dispatch request basic information setting unit 302. On the other hand, the boarding location when calculating the driving route differs depending on the type of dispatch request, and corresponds to the boarding location set by the dispatch request basic information setting unit 302, the boarding location where the user actually boarded the taxi 12, the boarding location where the user is predicted to board the taxi 12, etc.

For example, in the case of a dispatch request for pick-up use, the driving route of the candidate taxi 12 may be calculated based on the boarding location set by the dispatch request basic information setting unit 302. In the case of a dispatch request for cruising use and waiting use, the driving route of the candidate taxi 12 may be calculated based on the boarding location where the user actually boarded the taxi 12. However, the driving route and fare presented to the user and set before the user boards the taxi 12 may be calculated based on the current location, assuming that the current location of the user terminal 11 is the predicted boarding location. In this case, after the driving route and the pre-determined fare are set, when the current location moves, the driving route and fare may be updated and re-presented to the user, and reset. Alternatively, if there is no significant change in the driving route even when the current location moves, only the fare may be automatically changed according to the change in the driving distance. In addition, even if the driving route and the pre-determined fare are set before the user actually boards the taxi 12, the driving route and fare may be set based on the boarding location when the user actually boards the taxi 12. In addition, in the case of a dispatch request for use of waiting, the driving route of the candidate taxi 12 may be calculated based on the fixed waiting position, assuming that the fixed waiting position is the predicted boarding location. In the case of a dispatch request for use of a virtual stop, the driving route of the candidate taxi 12 may be calculated based on the position of the virtual stop, assuming that the position of the virtual stop is the boarding location. In this case, even if the driving route and the pre-determined fare are set before the user actually boards the taxi 12, the driving route and the fare may be set based on the boarding location when the user actually boards the taxi 12. Note that even if the meter fare is selected as the fare determination method, the payment information setting unit 303 may set the driving route in the same way as in the case of a pre-determined fare.

The payment information setting unit 303 sets the payment method in addition to the fare determination method. As described above, the payment methods include in-vehicle payment and online payment (in-app payment). In-vehicle payment includes not only cash payment, but also a method of paying the fare using a method that is compatible with the taxi 12 the user has boarded. There are generally the following types of cashless electronic payment methods that do not use cash:

・Code payment, smartphone payment, electronic money payment, credit card payment

Code payment is a payment method that uses payment services such as Alipay (registered trademark), LINE Pay (registered trademark), PayPay (registered trademark), and dPay (registered trademark), and transfers payment data using codes such as QR codes (registered trademark). Smartphone payment is a payment method that uses payment services such as Apple Pay (registered trademark) and Google Pay (registered trademark), which unify different types of payment services such as credit cards, electronic money, and telephone bill combined payment registered on a smartphone, and transfers payment data by holding the smartphone over a reader/writer (payment terminal). In smartphone payment, it is also possible to transfer payment data between the smartphone and the payment terminal using codes. Electronic money payment is a payment method that uses electronic money payment cards (electronic money cards) such as Suica (registered trademark), PASMO (registered trademark), QUICPay (registered trademark), iD (registered trademark), nanaco (registered trademark), etc. Electronic money cards include payment cards such as debit cards, prepaid cards, and taxi-specific payment cards. Credit card payment is a payment method that uses credit cards such as VISA (registered trademark), MasterCard (registered trademark), JCB (registered trademark), etc.

Which of these various payment methods can be used depends on the availability of the taxi 12 in which the user is riding, and mainly differs depending on the taxi company to which the taxi 12 belongs. In addition, the passenger terminal 15 may be used as a payment terminal that functions as a reader/writer, or a payment terminal that displays or reads a code.

Online payment is a payment method that is performed only online (on a ride-hailing app such as user app 21) without any transfer of payment data inside the vehicle. When online payment is set as a payment method, the payment information setting unit 303 sets the payment service to be used for online payment to the payment service selected by the user from among the payment services (credit card, electronic money, code payment service, etc.) preregistered in the ride-hailing app of the user terminal 11.

The driving mode setting unit 304 sets information (driving mode information) related to the driving mode (riding environment) and supplies the set driving mode information to the vehicle dispatch integrated management device 14 as information included in the dispatch request information (see steps S3 to S5 in FIG. 5, steps S54 and S56 in FIG. 6, and steps S203 to S205 in FIG. 9). The driving mode set by the driving mode setting unit 304 includes subjects related to the riding environment felt by the user while riding, such as driving speed (traveling speed), air conditioning (in-vehicle temperature, etc.), and conversation frequency. Note that conversation frequency is information related to the driver's behavior while driving, and information other than conversation frequency related to the driver's behavior while driving is also included in the driving mode information.

Specifically, the following information may be set as driving mode information: With regard to the driving speed, a speed desired by the user, such as fast, normal, or slow, may be set. With regard to the air conditioning, a vehicle interior temperature desired by the user, such as a desired temperature (specified temperature), high, normal, or low, may be set. With regard to the frequency of dialogue, a frequency of dialogue with the driver desired by the user, such as high, normal, or low, may be set. In addition, whether or not to play music or radio, and if so, the genre and volume, etc. may be set. Information regarding each target of the driving mode is selected by the user, for example, from among configurable candidates.

The advertisement setting unit 305 sets information relating to advertisements (advertising information) to be provided to the user via the passenger terminal 15, and supplies the set advertising information to the vehicle dispatch integrated management device 14 as information included in the vehicle dispatch request information (see steps S3 to S5 in FIG. 5, steps S54 and S56 in FIG. 6, and steps S203 to S205 in FIG. 9). The advertising information set by the advertisement setting unit 305 is, for example, a genre in which the user is interested. For example, the advertisement setting unit 305 presents a plurality of genres to the user, and sets one or more genres selected by the user from among the plurality of genres as the advertising information.

The mirroring setting unit 306 sets information (mirroring information) that identifies the content or application when the screen or sound of the content or application played on the user terminal 11 is projected on the passenger terminal 15, and supplies the set mirroring information to the dispatch integrated management device 14 as information included in the dispatch request information (see steps S3 to S5 in FIG. 5, steps S54 and S56 in FIG. 6, and steps S203 to S205 in FIG. 9). The mirroring information set by the mirroring setting unit 306 is, for example, information that identifies the content to be mirrored, such as video, music, or e-books, or information that identifies the application to be mirrored, such as a video management application, an online conference application, or a music management application. The mirroring information may also be information that sets whether or not mirroring is permitted for each content and application available on the user terminal 11. When mirroring is started, the user may select either a display on the screen of the user terminal 11 or the passenger terminal 15 indicating whether or not mirroring is permitted.

The vehicle information acquisition unit 301, the dispatch request basic information setting unit 302, the payment information setting unit 303, the driving mode setting unit 304, the advertisement setting unit 305, and the mirroring setting unit 306 in the user terminal 11 supply the vehicle information, basic information, payment information, driving mode information, advertisement information, and mirroring information, respectively, as dispatch request information to the dispatch integrated management device 14. The timing at which the dispatch request information is supplied from the user terminal 11 to the dispatch integrated management device 14 is when the user gets into the taxi 12 and connects the user terminal 11 to the passenger terminal 15 (when getting in) in the case of a dispatch request for cruising, waiting, and virtual stop use, and when the dispatch request is made before getting into the taxi 12 (before getting in) in the case of a dispatch request for pick-up use. However, even in the case of a dispatch request for cruising, waiting, and virtual stop use, information among the dispatch request information that can be set before getting in may be supplied to the dispatch integrated management device 14 before getting in. In addition, any of the settings in the dispatch request information may be changed to settings different from the dispatch request information supplied to the dispatch integrated management device 14 before or at the time of boarding, or may be set or changed at any time without being included in the dispatch request information. For example, driving mode information, advertising information, mirroring information, etc. may not be included in the dispatch request information, and may be set or changed at any time after the user boards the taxi 12.

Furthermore, the dispatch request basic information setting unit 302, the payment information setting unit 303, the driving mode setting unit 304, the advertisement setting unit 305, and the mirroring setting unit 306 may automatically set the default basic information, payment information, driving mode information, advertisement information, and mirroring information, respectively, when the default information, payment information, driving mode information, advertisement information, and mirroring information, which have been registered in advance, to the default information. When there are multiple candidates for the default information, the multiple candidates may be presented to the user, and the user may select from among them. Furthermore, the dispatch request basic information setting unit 302, the payment information setting unit 303, the driving mode setting unit 304, the advertisement setting unit 305, and the mirroring setting unit 306 may present to the user, as default setting contents, the basic information, payment information, driving mode information, advertisement information, and mirroring information, which are predicted to be set by the user for the current location, day of the week, time zone, weather, and other predetermined conditions of the user terminal 11 when the user makes a dispatch request, based on the user's past taxi 12 usage history.

<Vehicle Dispatch Integrated Management Device 14>
The dispatch request processing unit 321 creates dispatch request information to be presented to the user and the driver based on the dispatch request information from the user terminal 11, and supplies it to the passenger terminal 15 and the driver terminal 33 (see step S7 in FIG. 5 and steps S59 to S61 in FIG. 6). The dispatch request information supplied to the passenger terminal 15 and presented to the user is information for confirming that the dispatch request information set in the user terminal 11 has been properly notified to the taxi 12 (and the driver) in which the user has boarded, or that the taxi 12 in which the user has boarded is the taxi 12 that has accepted the dispatch request of the user, after the user boards the taxi 12 and the user terminal 11 acquires vehicle information from the passenger terminal 15 and supplies it to the dispatch integration management device 14, in the case of a dispatch request for cruising, waiting, or virtual stop use. For example, the dispatch request information presented to the user may be only a part of the information, such as the user information, included in the dispatch request information set in the user terminal 11. The dispatch request information presented to the user is displayed on the passenger terminal 15 of the taxi 12 when the user boards the taxi 12. In addition, even in the case of a dispatch request for pick-up use, the dispatch request processing unit 321 may create dispatch request information to be presented to the user and display it on the passenger terminal 15. The dispatch request information may be provided (displayed) to the passenger terminal 15 before the user gets in the car, or may be provided at the time the user gets in the car. The dispatch request information provided to the driver terminal 33 and presented to the driver is mainly information for the driver to decide whether or not to accept the dispatch request from the user terminal 11, regardless of the type of dispatch request. For example, the dispatch request information presented to the driver includes information excluding personal information and confidential information from the dispatch request information set in the user terminal 11, a map of the area around the current location of the taxi 12, a driving route and driving time (arrival time) from the current location of the taxi 12 on the map to the boarding location or destination, a payment method, and other information.

The dispatch request processing unit 321 also provides the driver terminal 33 with a request acceptance screen for confirming whether or not to accept the dispatch request from the user terminal 11, and acquires a request acceptance notice from the driver terminal 33 indicating that the driver has accepted the request (see steps S7 to S10 in FIG. 5 and steps S60 to S64 in FIG. 6). When the dispatch request is accepted, the dispatch request processing unit 321 provides a dispatch confirmation notice indicating this (see step S13 in FIG. 5) or a request acceptance notice indicating this (see S65 and S66 in FIG. 6) to the user terminal 11 and the passenger terminal 15. Note that in the case of a dispatch request for pick-up use, the dispatch confirmation notice does not need to be provided to the passenger terminal 15 because the user is not on board when the dispatch request is accepted.

On the other hand, in the case of a dispatch request using a virtual stop, the dispatch request processing unit 321 performs processing related to the processing (dispatch control) of the dispatch integrated management device 14 in FIG. 9 before the processing (dispatch control) of the dispatch integrated management device 14 in FIG. 6 after the user gets into the taxi 12. The processing of the dispatch request processing unit 321 and related processing in the case of a dispatch request using a virtual stop will be described in detail later.

The operation information processing unit 322 creates operation information for each taxi 12, and supplies the operation information of the taxi 12 to the passenger terminal 15 and driver terminal 33 of each taxi 12. The operation information processing unit 322 also supplies operation information of the taxi 12 heading to the user terminal 11 of the user waiting to be picked up (see steps S18 to S21 in FIG. 5 and steps S71 to S73 in FIG. 6). The operation information is information obtained from the real-time vehicle movement data of the taxi 12, and is information for presenting, for example, the vehicle's current location, driving direction, destination (or pick-up location), driving route and driving time (arrival time) to the destination (or pick-up location), status, and other operating conditions on a map around the current location of the taxi 12 or the user terminal 11. 5 and 6 only show the case where the destination of the dispatch request or the pick-up location is reflected in the operation information, but the operation information is updated sequentially based on the latest vehicle status data and is sequentially supplied to the user terminal 11 waiting to be picked up, the passenger terminal 15 of the taxi 12 after the passenger has boarded, and the driver terminal 33 of the taxi 12 in any situation.

The payment processing unit 323 performs payment processing according to the payment method set by the payment information setting unit 303 of the user terminal 11 (see steps S77 and S84 in FIG. 6). In the payment processing by the payment processing unit 323, the usage fee (including the pick-up fee, etc.) including the fare is determined according to the fare determination method set by the payment information setting unit 303. In addition, the payment information setting unit 303 notifies the payment service (payment server) set as the payment method of the usage information (usage fee, etc.) and requests payment processing, and the payment result is received. A detailed explanation of the payment processing is omitted. In addition, when the taxi 12 arrives at the destination, the payment processing unit 323 calculates the usage fee (including the pick-up fee, etc.) including the fare according to the fare determination method set by the payment information setting unit 303. After calculating the usage fee, the payment processing unit 323 supplies the passenger terminal 15 and the driver terminal 33 with arrival and payment information indicating the arrival at the destination and the usage fee to be paid by the user. When the payment of the usage fee is completed according to the payment method set by the payment information setting unit 303 of the user terminal 11, a payment completion notice indicating this is provided to the passenger terminal 15 and the driver terminal 33. Arrival and payment information and the payment completion notice may be provided to the user terminal 11.

In addition, when the payment information setting unit 303 sets the online payment as the payment method, the payment processing unit 323 may perform some processing before boarding or while boarding before arriving at the destination. This reduces the user's effort when getting off the vehicle and improves convenience. For example, when the payment information setting unit 303 sets the pre-determined fare as the fare determination method, the payment processing unit 323 can determine the usage fee by the fare calculated according to the pre-determined fare method before arriving at the destination. When the usage fee is determined, the payment processing unit 323 connects to the payment server and transmits information on the payment service set as the payment method by the payment information setting unit 303 and payment information such as the usage fee to complete the payment. When the user's consent to the payment is required, the payment processing unit 323 presents the payment fee (usage fee) to the user terminal 11 or the passenger terminal 15, and obtains information consenting to the payment by the user's operation on the user terminal 11 or the passenger terminal 15. This information consenting to the payment may be set in advance by the payment information setting unit 303 as information to be included in the dispatch request information. This reduces the effort required of the user when getting off. On the other hand, when the meter fare is set as the fare determination method by the payment information setting unit 303, the payment processing unit 323 may obtain information approving payment in advance before the fare is determined before arrival at the destination. In this case, an estimate of the fare calculated in a similar manner to the fare determination method or in another manner is displayed on the user terminal 11 or the passenger terminal 15 and presented to the user, and information approving payment is notified to the payment processing unit 323 by the user's operation on the user terminal 11 or the passenger terminal 15. After arriving at the destination and the fare is determined, the payment processing unit 323 performs payment processing and completes the payment without obtaining the user's further approval for payment. In this case, the effort required of the user when getting off is reduced.

The driving mode processing unit 324 supplies the driving mode information set by the driving mode setting unit 304 of the user terminal 11 to the passenger terminal 15 and the driver terminal 33 (see steps S61 and S62 in FIG. 6). In addition, for driving mode targets related to the riding environment that can be automatically adjusted without the driver, such as air conditioning, the driving mode processing unit 324 may supply a control signal to the taxi 12 in which the user is riding, in which the driving mode processing unit 324 controls the target according to the driving mode information set by the driving mode setting unit 304. In addition, the driving mode information may be supplied to the passenger terminal 15 and the driver terminal 33 as information included in the operation information (see steps S71 to S73 in FIG. 6), and may be changed as appropriate by the user's operation on the user terminal 11 or the passenger terminal 15, and may be notified to the driver.

The advertisement processing unit 325 selects advertisements suitable for the user based on the advertisement information set by the advertisement setting unit 305 of the user terminal 11, and supplies the selected advertisements to the passenger terminal 15 as information included in the operation information (see steps S71 and S72 in FIG. 6). For example, the advertisement processing unit 325 selects, from among multiple types of advertisements prepared in advance, an advertisement in the genre selected by the user by the advertisement setting unit 305 as an advertisement suitable for the user. The advertisement information may be changed as appropriate by the user's operation on the user terminal 11 or passenger terminal 15, and notified to the advertisement processing unit 325.

The mirroring processing unit 326 acquires the screen or audio of the content or application to be mirrored from the user terminal 11 based on the mirroring information set by the mirroring setting unit 306 and supplied from the user terminal 11, and supplies it to the passenger terminal 15 as information included in the operation information (see steps S71 and S72 in FIG. 6). The mirroring information may be changed as appropriate by the user's operation of the user terminal 11 or the passenger terminal 15, and may be notified to the mirroring processing unit 326.

<Passenger Terminal 15>
The dispatch request information display unit 341 generates an image for presenting the dispatch request information from the dispatch request processing unit 321 of the dispatch integrated management device 14 to the passenger, and displays it on the display of the passenger terminal 15. The operation information display unit 342 generates an image for presenting the operation information from the operation information processing unit 322 of the dispatch integrated management device 14 to the passenger, and displays it on the display of the passenger terminal 15. The payment information display unit 343 generates an image for presenting the arrival and payment information from the payment processing unit 323 of the dispatch integrated management device 14 and the payment completion notice to the passenger, and displays it on the display of the passenger terminal 15. The driving mode display unit 344 generates an image for presenting the driving mode information from the driving mode processing unit 324 of the dispatch integrated management device 14 to the passenger, and displays it on the display of the passenger terminal 15. The touch operation of the user on the image portion on which the driving mode information is displayed by the driving mode display unit 344 may be detected by a touch panel, so that the user who is riding can change the driving mode information. When the driving mode information is changed, the change is notified to the driving mode processing unit 324 of the vehicle dispatch integrated management device 14, and the changed driving mode information is processed as being set in the driving mode setting unit 304 of the user terminal 11 (such as supplying the changed driving mode information to the driver terminal 33). The advertisement display unit 345 generates an advertisement from the advertisement processing unit 325 of the vehicle dispatch integrated management device 14 as a video to be presented to the user, and displays it on the display of the passenger terminal 15. The mirroring display unit 346 displays the screen of the content or application from the mirroring processing unit 326 of the vehicle dispatch integrated management device 14 on the display of the passenger terminal 15. The sound of the content or application from the mirroring processing unit 326 is output from a speaker or the like installed in the vehicle.

<Driver Terminal 33>
The dispatch request information display unit 341 generates an image for presenting the dispatch request information from the dispatch request processing unit 321 of the dispatch integrated management device 14 to the driver, and an image for the driver to select whether or not to accept the dispatch request (request acceptance screen), and displays them on the display of the driver terminal 33. The dispatch request information display unit 361 detects a user's touch operation on the image portion where the request acceptance screen is displayed by the touch panel, and when an operation to accept the request is performed, a notification of that effect (request acceptance notification) is supplied from the driver terminal 33 to the dispatch integrated management device 14. The operation information display unit 342 generates an image for presenting the operation information from the operation information processing unit 322 of the dispatch integrated management device 14 to the driver, and displays it on the display of the driver terminal 33. The payment information display unit 343 generates an image for presenting the arrival and payment information from the payment processing unit 323 of the dispatch integrated management device 14 and a payment completion notification to the driver, and displays it on the display of the driver terminal 33. The driving mode display unit 344 generates an image for presenting the driving mode information from the driving mode processing unit 324 of the vehicle dispatch integrated management device 14 to the driver, and displays it on the display of the driver terminal 33. The driver provides an environment desired by the passenger based on the driving mode information displayed on the driver terminal 33.

<Processing of the integrated vehicle dispatch management device 14 in FIG. 10 in the case of a dispatch request using a virtual stop> When the dispatch request processing unit 321 of the integrated vehicle dispatch management device 14 is supplied with dispatch request information using a virtual stop (virtual stop dispatch request information) from the user terminal 11 (see step S205 in FIG. 9), it determines the optimal location of the virtual stop. In determining the optimal location of the virtual stop, the dispatch request processing unit 321 refers to, for example, the current location and destination of the user (user terminal 11) contained in the virtual stop dispatch request information. In addition, vehicle status data from a certain period of time ago, including the latest (real-time) vehicle status data of each taxi 12, is stored in the vehicle status data management unit 101 (see FIG. 1), and the dispatch request processing unit 321 obtains real-time vehicle status data of taxis 12 traveling around the user's current location from the vehicle status data management unit 101. The vehicle status data of each taxi 12 includes various information such as company ID, radio ID, driver ID, tablet ID, status, status time, fare (fare), current location, running speed, direction of travel, boarding location, and destination (drop-off location). The dispatch request processing unit 321 refers to the status, the current location of the taxi 12, running speed, direction of travel (vehicle orientation), and other information included in the real-time vehicle status data. The dispatch request processing unit 321 also refers to the road conditions around the user's current location (one-way streets, presence or absence of bridges, railroad crossings, congestion, no-stop zones for taxis, etc.).

The dispatch request processing unit 321 uses the referenced information to determine the optimal virtual stop position. For example, the dispatch request processing unit 321 calculates the position that best meets the conditions that the virtual stop position should satisfy, and determines that position as the optimal virtual stop position. As the condition, any one or more of the following conditions are used. Note that the conditions used to determine the optimal virtual stop position include at least one condition that the optimal virtual stop position that meets the conditions varies depending on the taxi 12 (boarding vehicle) to be boarded, and the optimal boarding vehicle is determined at the same time as the optimal virtual stop position that best meets the conditions is determined. However, after determining the optimal virtual stop position, the dispatch request processing unit 321 may determine the optimal boarding vehicle based on the optimal virtual stop position, the destination of the dispatch request, real-time vehicle movement data of vehicles existing around the optimal virtual stop position, etc., or it is not necessary to determine the optimal boarding vehicle.

Condition 1. The status of the taxi 12 passing through the optimal virtual stop position is empty. According to condition 1, not only the taxi 12 whose real-time status is empty, but also the position through which the taxi 12 that may possibly become empty passes can be the optimal virtual stop.
Condition 2: The travel distance or travel time required for the taxi 12 to move from the current location to the optimal virtual stop location is short.
Condition 3. The walking distance or walking time required for the user to move from the current location to the optimal virtual stop location is short.
Condition 4: The user's arrival time is earlier than the time when the taxi 12 arrives at the optimal virtual stop position.
Condition 5. The travel distance or travel time required for the taxi 12 to move from the optimal virtual stop position to the destination of the dispatch request is short.
Condition 6. The arrival time at the destination when moving from the optimal virtual stop location to the destination of the vehicle dispatch request is short.
Condition 7: The optimal virtual stop location is close to the planned driving route of taxi 12.
Condition 8. The direction (travel direction) of the taxi 12 passing through the optimal virtual stop position is close to the direction to the destination of the dispatch request. In addition, on a road having lanes with opposing travel directions, the lane side of which the position is located is taken into consideration. A taxi 12 passing on the opposite lane side to a position on a certain lane side is not allowed to pass through that position. In addition, even if the positions are opposite each other on the same road, the positions that are opposite lanes are different positions.
Condition 9. There are no or few one-way streets, bridges, or railroad crossings that impede smooth travel around the optimal virtual stop location.
Condition 10: The roads around the optimal virtual stop location are not congested.
Condition 11: The optimal virtual stop location is not a no-stop zone for taxis 12.
Condition 12: The optimal virtual stop location is a location where the user does not cross a main road (large lane) relative to the user's current location.
Condition 13: The optimal virtual stop position is a position that is statistically likely to be a boarding position. In condition 13, the past vehicle movement data of multiple (all or many) taxis 12 stored in the vehicle movement data management unit 101 is referenced, or the past vehicle movement data of a vehicle that the user has used in the past is referenced, and a location that is statistically likely to be a boarding position is analyzed.

The dispatch request processing unit 321 determines the optimal virtual stop position and the boarding vehicle that meets any one or more of the above conditions 1 to 13. Note that conditions 1 to 13 for determining the optimal virtual stop position are merely examples, and other conditions may be used. The dispatch request processing unit 321 may also assign a priority (weight) to each of the multiple conditions used to determine the optimal virtual stop position, evaluate the overall suitability to the multiple conditions, and determine the position with the highest overall suitability as the optimal virtual stop position and the boarding vehicle.

When the dispatch request processing unit 321 determines the location of the optimal virtual stop (hereinafter simply referred to as the virtual stop) and the optimal boarding vehicle (hereinafter simply referred to as the boarding vehicle), it creates dispatch information including these pieces of information and the current location of the user (user terminal 11) (see step S207 in FIG. 9). The dispatch request processing unit 321 calculates (estimates) the walking route and walking time from the current location of the user (user terminal 11) to the virtual stop, the driving route and driving time (arrival time) from the virtual stop to the destination of the dispatch request, and the waiting time until boarding (boarding time for the taxi 12), as the dispatch information. The dispatch information may include any information that can be supplied to the user terminal 11, such as the usage fee calculated by the payment processing unit 323. In addition, the information regarding the time calculated as the dispatch information may be information that specifies each of the time when the user is predicted to arrive at the virtual stop, the time when the user is predicted to board at the virtual stop (or the time when the taxi 12 arrives at the virtual stop), and the time when the taxi 12 arrives at the destination of the dispatch request. The walking time from the user's current location to the virtual stop may be the time when the user is predicted to arrive at the virtual stop, taking into account the current time. The driving time from the virtual stop to the destination of the dispatch request may be the time when the user arrives at the destination of the dispatch request. The waiting time before boarding may be the time when the user is predicted to board at the virtual stop, taking into account the current time (or the time when the taxi 12 arrives at the virtual stop). The waiting time before boarding may not be the elapsed time from the current time to boarding, but may be the elapsed time from the user's arrival at the virtual stop to boarding. The method of expressing information about time is not limited to a specific method. In addition, the dispatch request processing unit 321 creates detailed information about the boarding vehicle as dispatch information. The detailed information includes information such as the face photo and name of the driver of the boarding vehicle, the taxi company, the vehicle model, and the driver rating (route knowledge, cleanliness level, driving skill, customer service attitude, etc.) (see the balloon of the taxi mark 274A in FIG. 8).

The dispatch request processing unit 321 supplies the created dispatch information to the user terminal 11 and the driver terminal 33 (see steps S208 and S209 in FIG. 9). The dispatch information supplied to the user terminal 11 and the driver terminal 33 does not have to be the same, and may be limited to the information displayed on each terminal. The dispatch request basic information setting unit 302 of the user terminal 11 that has acquired the dispatch information reflects the acquired dispatch information on the dispatch request screen, such as the dispatch request screen 251 in FIG. 8 (see step S210 in FIG. 9). The dispatch request basic information setting unit 302 of the user terminal 11 acquires real-time vehicle status data of the taxis 12 present within the map range of the dispatch request screen 251 from the dispatch integrated management device 14, in addition to the dispatch information, and the map on the dispatch request screen also displays information such as the position of the taxi 12 other than the vehicle being boarded (see taxi marks 274B and 274C in FIG. 8). The taxis 12 displayed on the map may be limited to vehicles whose status is vacant and vehicles whose status will be vacant soon, or may be limited to only vehicles whose status is vacant. The dispatch information is supplied to the driver terminal 33 of vehicles that are within a certain distance including the closest vehicle to the virtual stop, or vehicles that pass the position of the virtual stop or its vicinity (within a certain distance) within a certain time (vehicles that can arrive at the position of the virtual stop within a certain time). The vehicle that can arrive at the position of the virtual stop within a certain time may be a vehicle that takes into consideration the road conditions. The driver terminal 33 that has acquired the dispatch information displays the position of the virtual stop, the current location of the user, the usage fee (including an estimated fee), and the like on a map around the current location of the vehicle. The screen of the driver terminal 33 may display information similar to that of the dispatch request screen of the user terminal 11, may display only the position of the virtual stop, or may display information different from that of the dispatch request screen of the user terminal 11.

(Examples of various forms for requesting a vehicle using a virtual stop)
(Example 1)
When an operation to change the position of the presented virtual stop is performed by the user or the driver on the user terminal 11 or the driver terminal 33 on which the dispatch information for the virtual stop is displayed, the dispatch request processing unit 321 acquires the changed position of the virtual stop. The dispatch request processing unit 321 may create dispatch information again based on the changed position of the virtual stop and provide it to the user terminal 11 and the driver terminal 33. In this way, when the initially presented virtual stop is not an appropriate location, the user or the driver can correct it to an appropriate location, and the accuracy of the determination of the virtual stop and the convenience of the user and the taxi 12 can be improved from the next time onwards.

(Example 2)
The dispatch request processing unit 321 may determine the positions (and boarding vehicles) of multiple virtual stops instead of determining only one position as the optimal virtual stop position. As a method of this, the dispatch request processing unit 321 can, for example, determine multiple positions as the positions of the virtual stops by giving priority to positions that have a high degree of conformity with the above conditions that the positions of the virtual stops should satisfy. As another method, the dispatch request processing unit 321 can determine multiple positions that are statistically likely to be boarding positions as the positions of the virtual stops using past vehicle movement data. In addition, when the dispatch request processing unit 321 determines the positions of multiple virtual stops, it can determine the optimal boarding vehicle for each of them. The optimal boarding vehicle for each virtual stop position can be determined for each virtual stop position in the same manner as when the position of one virtual stop is determined. Even when the positions of multiple virtual stops are determined, the dispatch request processing unit 321 creates dispatch information for each virtual stop similar to the case of determining the position of one virtual stop, and supplies it to the user terminal 11 and the driver terminal 33. The vehicle dispatch request basic information setting unit 302 of the user terminal 11 that has acquired the vehicle dispatch information for the multiple virtual stops reflects (displays) the vehicle dispatch information for the multiple virtual stops (waiting time until boarding, etc.) on the vehicle dispatch request screen in the same manner as when vehicle dispatch information for one virtual stop has been acquired. However, in order to prevent the display on the map of the vehicle dispatch request screen from becoming cluttered, only the positions of the multiple virtual stops (virtual stop marks) may be displayed on the map, and detailed information included in the vehicle dispatch information may be switched and displayed only for the virtual stop designated by the user. The driver terminal 33 that has acquired the vehicle dispatch information for the multiple virtual stops displays the positions of the multiple virtual stops on a map around the current location of the vehicle.

(Example 3)
The dispatch request processing unit 321 may create dispatch information for when a vehicle is used for picking up a vehicle and dispatch information for when a vehicle is used for waiting to be picked up in cooperation with dispatch information for the virtual stop (dispatch information when a virtual stop is used), and supply the information to the user terminal 11. The dispatch request processing unit 321 may supply only two of the dispatch information for when a virtual stop is used, the dispatch information for when a vehicle is used for picking up a vehicle, and the dispatch information for when a vehicle is used for waiting to be picked up to the user terminal 11. The dispatch information for when a vehicle is used for picking up a vehicle may be information that is supplied from the dispatch integration management device 14 to the user terminal 11 and displayed on the dispatch request screen when the dispatch request basic information setting unit 302 of the user terminal 11 sets basic information on the dispatch request screen for when a vehicle is used for picking up a vehicle of the user terminal 11 and before a dispatch request operation for when a vehicle is used for picking up a vehicle (see step S4 in FIG. 5) is performed. Alternatively, the information may be displayed on the dispatch request screen as information attached to the dispatch confirmation notice (see step S13 in FIG. 5 ) that is supplied to the user terminal 11 from the dispatch integration management device 14 after the dispatch request operation for the pick-up service is performed on the dispatch request screen for the pick-up service of the user terminal 11 when the dispatch request is accepted. The dispatch information for the pick-up service that is supplied to the user terminal 11 in cooperation with the dispatch information for the virtual stop includes information such as the driving route and driving time (arrival time) of the taxi 12 from the current location (boarding location) to the destination of the dispatch request, the waiting time until boarding (boarding time for the taxi 12), and the usage fee, as in the case where a dispatch request for the pick-up service is made with the current location of the user (user terminal 11) as the boarding location (pick-up location). Note that the boarding location (pick-up location) may be the position of the virtual stop, or may be specified by the user. In that case, the dispatch information for the pick-up service may include information on the user's walking route and travel time from the current location of the user (user terminal 11) to the boarding location (pick-up location). The dispatch information when waiting for pickup can be information supplied from the integrated dispatch management device 14 to the user terminal 11 and displayed on the dispatch request screen when the dispatch request basic information setting unit 302 of the user terminal 11 is setting basic information on the dispatch request screen for waiting for pickup on the user terminal 11 and before the user terminal 11 is held over the passenger terminal 15 (see step S55 in Figure 6).

The dispatch information when waiting to be picked up that is supplied to the user terminal 11 in conjunction with the dispatch information when a virtual stop is used includes, for each of the waiting locations such as taxi stands that exist around the current location of the user (user terminal 11), information such as the user's walking route and travel time from the current location of the user (user terminal 11) to the waiting location, the taxi's driving route and driving time (arrival time) from the waiting location to the destination of the dispatch request, the waiting time until boarding (boarding time for the taxi 12), and the usage fee. The dispatch request basic information setting unit 302 of the user terminal 11 that has acquired the dispatch information when a pick-up is used and the dispatch information when waiting to be picked up in conjunction with the dispatch information for the virtual stop (dispatch information when a virtual stop is used) switches between a dispatch request screen that reflects the dispatch information when a virtual stop is used, a dispatch request screen that reflects the dispatch information when a pick-up is used, and a dispatch request screen that reflects the dispatch information when waiting to be picked up, or displays them integrated into one dispatch request screen.

For example, as a first specific example, when making a dispatch request using any type of dispatch request method, the dispatch request basic information setting unit 302 of the user terminal 11 acquires dispatch information when using a pick-up service, dispatch information when using a waiting service, and dispatch information when using a virtual stop from the dispatch integrated management device 14. The dispatch request basic information setting unit 302 compares the waiting time (boarding time) until boarding included in each of the dispatch information when using a virtual stop, the dispatch information when using a pick-up service, and the dispatch information when using a waiting service, and assigns higher priority to the dispatch information for each dispatch request method in order of the shortest waiting time, i.e., the earliest boarding time. Note that the priority may be assigned in order of the lowest usage fee or the earliest arrival time at the destination of the dispatch request, rather than in order of the shortest waiting time. The dispatch request basic information setting unit 302 first displays a dispatch request screen reflecting the dispatch information of the dispatch request method with the highest priority, and switches and displays the dispatch request screen reflecting the dispatch information of different dispatch request methods in order of priority according to the user's operation. The user selects one of the dispatch request methods based on the dispatch information on the dispatch request screen, and performs operations such as inputting the dispatch request information required to request a dispatch using the selected dispatch request method on the dispatch request screen that reflects the dispatch information for that dispatch request method.

As a second specific example, when making a vehicle dispatch request using any type of vehicle dispatch request method, the vehicle dispatch request basic information setting unit 302 of the user terminal 11 acquires vehicle dispatch information when using a pick-up service, vehicle dispatch information when using a waiting service, and vehicle dispatch information when using a virtual stop from the vehicle dispatch integrated management device 14. The vehicle dispatch request basic information setting unit 302 displays information on the waiting time (boarding time) until boarding included in each of the vehicle dispatch information when using a virtual stop, vehicle dispatch information when using a pick-up service, and vehicle dispatch information when using a waiting service in association with the vehicle dispatch request method. Note that instead of waiting time information, information such as the usage fee and arrival time at the destination may be displayed, or multiple types of information may be displayed. When the user selects one vehicle dispatch request method based on that information, the vehicle dispatch request basic information setting unit 302 displays a vehicle dispatch request screen that reflects the vehicle dispatch information of the vehicle dispatch request method selected by the user. The user performs operations such as inputting vehicle dispatch request information necessary for a vehicle dispatch request using the selected vehicle dispatch request method on the vehicle dispatch request screen.

As a third specific example, when making a dispatch request using any type of dispatch request method, the dispatch request basic information setting unit 302 of the user terminal 11 acquires dispatch information when using a pick-up service, dispatch information when using a waiting service, and dispatch information when using a virtual stop from the dispatch integrated management device 14. The dispatch request basic information setting unit 302 displays a dispatch request screen that reflects the dispatch information of the dispatch request method that is the default that has been set in advance. However, the dispatch request screen compares the waiting time (boarding time) until boarding included in each of the dispatch information when using a virtual stop, the dispatch information when using a pick-up service, and the dispatch information when using a waiting service, and if there is a dispatch request method that allows boarding a certain amount of time or more (for example, 5 minutes or more) earlier than the default dispatch request method, the user is notified of this. When the user performs an operation to switch to the dispatch request screen of the notified dispatch request method, the dispatch request screen is switched to one that reflects the dispatch information of the dispatch request method. In addition, if there is a vehicle dispatch request method that offers a usage fee that is more than a certain amount cheaper than the waiting time, or a vehicle dispatch request method that offers an arrival time at the destination of the vehicle dispatch request that is more than a certain amount earlier, the user may be notified of this.

<Program>
The series of processes in the above-mentioned user terminal 11, vehicle dispatch management device 13, vehicle dispatch integrated management device 14, passenger terminal 15, or driver terminal 33 can be executed by hardware or software. When the series of processes are executed by software, the programs constituting the software are installed in a computer. Here, the computer includes a computer built into dedicated hardware, and a general-purpose personal computer, for example, capable of executing various functions by installing various programs.

FIG. 11 is a block diagram showing an example of the hardware configuration of a computer that executes the above-mentioned series of processes using a program.

In a computer, a CPU (Central Processing Unit) 501, a ROM (Read Only Memory) 502, and a RAM (Random Access Memory) 503 are interconnected by a bus 504.

Further connected to the bus 504 is an input/output interface 505. Connected to the input/output interface 505 are an input unit 506, an output unit 507, a storage unit 508, a communication unit 509, and a drive 510.

The input unit 506 includes a keyboard, mouse, microphone, etc. The output unit 507 includes a display, speaker, etc. The storage unit 508 includes a hard disk, non-volatile memory, etc. The communication unit 509 includes a network interface, etc. The drive 510 drives removable media 511 such as a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory.

In a computer configured as described above, the CPU 501 loads a program stored in the storage unit 508, for example, into the RAM 503 via the input/output interface 505 and the bus 504, and executes the program, thereby performing the above-mentioned series of processes.

The program executed by the computer (CPU 501) can be provided by being recorded on removable media 511 such as package media, for example. The program can also be provided via a wired or wireless transmission medium such as a local area network, the Internet, or digital satellite broadcasting.

In a computer, a program can be installed in the storage unit 508 via the input/output interface 505 by inserting the removable medium 511 into the drive 510. The program can also be received by the communication unit 509 via a wired or wireless transmission medium and installed in the storage unit 508. Alternatively, the program can be pre-installed in the ROM 502 or storage unit 508.

The program executed by the computer may be a program in which processing is performed chronologically in the order described in this specification, or a program in which processing is performed in parallel or at the required timing, such as when called.

The present technology can also be configured as follows.
(1)
The system includes a plurality of vehicles, a vehicle dispatch management device that manages dispatch of the vehicles, and a first terminal that sets the contents of a dispatch request as dispatch request information,
An information processing system having a processing unit that determines a virtual waiting position based on a current location of the first terminal and dynamic state data of the vehicle.
(2)
The information processing system described in (1), wherein the processing unit determines the virtual waiting position based on any one of the vehicle's position, driving speed, direction of movement, and meter status as the dynamic data of the vehicle.
(3)
The information processing system according to (1) or (2), wherein the processing unit supplies the virtual waiting position to the first terminal.
(4)
The information processing system according to (3), wherein the first terminal displays the virtual waiting position acquired from the processing unit.
(5)
The information processing system described in (3) or (4), wherein the processing unit calculates information regarding at least one of the time required to travel from the current location of the first terminal to the virtual waiting position, the time required to board the vehicle, and the time required to arrive at the destination included in the dispatch request, and supplies the information to the first terminal.
(6)
The information processing system according to (5), wherein the first terminal displays the information related to the time acquired from the processing unit.
(7)
The information processing system according to any one of (1) to (6), wherein the processing unit determines the virtual waiting position using past dynamic data of the plurality of vehicles managed by the vehicle dispatch management device.
(8)
The information processing system according to any one of (1) to (7), wherein the processing unit determines the virtual waiting position taking into consideration road conditions.
(9)
The vehicle includes a second terminal for use by a crew member;
The processing unit provides the virtual waiting position to the second terminal;
The information processing system according to any one of (1) to (8), wherein the second terminal displays the acquired virtual waiting position.
(10)
The information processing system according to (9), wherein the processing unit supplies the current location of the first terminal to the second terminal; and the second terminal displays the obtained current location of the first terminal.
(11)
The information processing system according to (9) or (10), wherein the processing unit supplies the virtual waiting position to the second terminal of the vehicle that is present within a range of a certain condition with respect to the virtual waiting position.
(12)
The vehicle existing within the range of the certain conditions is a vehicle existing within a certain distance of the virtual waiting position or a vehicle that will arrive at the waiting position within a certain time.
(13)
The processing unit calculates information regarding the time required to board a vehicle at the virtual waiting location or the time required to travel to the destination of the vehicle dispatch request, together with information regarding the time required to board a vehicle dispatched by a vehicle dispatch request method of a different type from the vehicle dispatch request method that utilizes the virtual waiting location or the time required to arrive at the destination of the vehicle dispatch request, and supplies the information regarding the calculated times to the first terminal.
(14)
The vehicle dispatch request method of a different type from the vehicle dispatch request method using the virtual waiting includes at least one of a vehicle dispatch request method in which the vehicle is boarded at an actual waiting location and a vehicle dispatch request method in which the vehicle is boarded at a pick-up location using a pick-up car.
(15)
The first terminal displays a message inviting a user to make a vehicle dispatch request using a vehicle dispatch request method different from the vehicle dispatch request method using the virtual waiting position, based on the information regarding the time acquired from the processing unit.
(16)
The first terminal displays information regarding the time obtained from the processing unit, and displays a screen for making the vehicle dispatch request using a vehicle dispatch request method of a different type from the vehicle dispatch request method that uses the virtual waiting location, or displays on the screen for making the vehicle dispatch request using the vehicle dispatch request method that uses the virtual waiting location that a vehicle dispatch request method of a different type from the vehicle dispatch request method that uses the virtual waiting location is more advantageous.The information processing system described in (15).
(17)
An information processing method for an information processing system including a plurality of vehicles, a vehicle dispatch management device that manages the dispatch of the vehicles, and a first terminal that sets the contents of a dispatch request as dispatch request information, the information processing system having a processing unit, the processing unit determining a virtual waiting position based on the current location of the first terminal and dynamic data of the vehicles.
(18)
Computer,
A program for functioning as a processing unit that determines a virtual waiting position suitable for a boarding position when boarding a cruising vehicle, based on the current location of a terminal that sets vehicle dispatch request information indicating the contents of the vehicle dispatch request and the vehicle status data of the vehicle for which dispatch is managed.

1 Taxi dispatch system, 11 User terminal, 12 Taxi, 13 Dispatch management device, 14 Dispatch integrated management device, 15 Passenger terminal, 21 User application, 31 In-vehicle device, 32, 83 Communication unit, 33 Driver terminal, 41 Vehicle status data acquisition unit, 51 Driver application, 81 Vehicle status data management unit, 82 Order information management unit, 101 Vehicle status data management unit, 102 Customer data management unit, 103 Order information management unit, 104 Dispatch management unit, 105 Taxi company communication unit, 106 Application communication unit, 121 Passenger application, 161 Virtual stop display unit, 301 Vehicle information acquisition unit , 302 dispatch request basic information setting unit, 303 payment information setting unit, 304 driving mode setting unit, 305 advertisement setting unit, 306 mirroring setting unit, 321 dispatch request processing unit, 322 operation information processing unit, 323 payment processing unit, 324 driving mode processing unit, 325 advertisement processing unit, 326 mirroring processing unit, 341 dispatch request information display unit, 342 operation information display unit, 343 payment information display unit, 344 driving mode display unit, 345 advertisement display unit, 346 mirroring display unit, 361 dispatch request information display unit, 362 operation information display unit, 363 payment information display unit, 364 driving mode display unit

Claims

The system includes a plurality of vehicles, a vehicle dispatch management device that manages dispatch of the vehicles, and a first terminal that sets the contents of a dispatch request as dispatch request information,
An information processing system having a processing unit that determines a virtual waiting position based on a current location of the first terminal and dynamic state data of the vehicle.
The information processing system according to claim 1 , wherein the processing unit determines the virtual waiting position based on any one of the vehicle's position, driving speed, direction of movement, and meter status as the dynamic data of the vehicle.
The information processing system according to claim 1 , wherein the processing unit supplies the virtual waiting position to the first terminal.
The information processing system according to claim 3 , wherein the first terminal displays the virtual waiting position acquired from the processing unit.
The information processing system according to claim 3, wherein the processing unit calculates information regarding at least one of a time required for the first terminal to travel from a current location of the first terminal to the virtual waiting position, a time required to board the vehicle, and a time required to arrive at a destination included in the dispatch request, and supplies the information to the first terminal.
The information processing system according to claim 5 , wherein the first terminal displays the information relating to the time acquired from the processing unit.
The information processing system according to claim 1 , wherein the processing unit determines the virtual waiting position by using the past dynamic state data of the plurality of vehicles managed by the vehicle dispatch management device.
The information processing system according to claim 1 , wherein the processing unit determines the virtual waiting position in consideration of road conditions.
The vehicle includes a second terminal for use by a crew member;
The processing unit provides the virtual waiting position to the second terminal;
The information processing system according to claim 1 , wherein the second terminal displays the acquired virtual waiting position.
The information processing system according to claim 9 , wherein the processing unit supplies the current location of the first terminal to the second terminal, and the second terminal displays the acquired current location of the first terminal.
The information processing system according to claim 9 , wherein the processing unit supplies the virtual waiting position to the second terminal of the vehicle that is present within a range of a certain condition with respect to the virtual waiting position.
The information processing system according to claim 11 , wherein the vehicle existing within the range of the certain condition is a vehicle existing within a certain distance from the virtual waiting position or a vehicle that will arrive at the waiting position within a certain time.
The information processing system of claim 1, wherein the processing unit calculates information regarding the time required to board a vehicle at the virtual waiting location or the time required to travel to the destination of the vehicle dispatch request, together with information regarding the time required to board a vehicle dispatched using a vehicle dispatch request method of a different type from the vehicle dispatch request method that utilizes the virtual waiting location or the time required to arrive at the destination of the vehicle dispatch request, and supplies the calculated information regarding the times to the first terminal.
The information processing system of claim 13, wherein the vehicle dispatch request method of a different type from the vehicle dispatch request method using the virtual waiting includes at least one of a vehicle dispatch request method in which the vehicle is boarded at an actual waiting location and a vehicle dispatch request method in which a pick-up vehicle is used to board at a pick-up location.
The information processing system according to claim 13, wherein the first terminal displays a display inviting a user to make a vehicle dispatch request using a vehicle dispatch request method different from the vehicle dispatch request method using the virtual waiting position, based on the information regarding the time acquired from the processing unit.
The information processing system described in claim 15, wherein the first terminal displays information regarding the time obtained from the processing unit, displays a screen for making the vehicle dispatch request using a vehicle dispatch request method of a different type from the vehicle dispatch request method that uses the virtual waiting location, or displays on the screen for making the vehicle dispatch request using the vehicle dispatch request method that uses the virtual waiting location that a vehicle dispatch request method of a different type from the vehicle dispatch request method that uses the virtual waiting location is more advantageous.
An information processing method for an information processing system including a plurality of vehicles, a vehicle dispatch management device that manages the dispatch of the vehicles, and a first terminal that sets the contents of a dispatch request as dispatch request information, the information processing system having a processing unit, the processing unit determining a virtual waiting position based on the current location of the first terminal and dynamic data of the vehicles.
Computer,
A program for causing the device to function as a processing unit that determines a virtual waiting position suitable for a boarding position when boarding a cruising vehicle, based on the current location of a terminal that sets vehicle dispatch request information indicating the contents of the vehicle dispatch request and the vehicle status data of the vehicle for which dispatch is managed.