Dispatch device, dispatch method, program, terminal device, and dispatch system

Abstract

To set an appropriate vehicle allocation place according to a situation.SOLUTION: A vehicle allocation device according to an embodiment executes vehicle allocation processing of a taxi and comprises a controller. The controller selects a vehicle allocation candidate point as a candidate of the vehicle allocation point on the basis of vehicle allocation desired position information included in a vehicle allocation request of a user, and executes the vehicle allocation processing on the basis of the vehicle allocation candidate point selected by the user.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The disclosed embodiments relate to a vehicle allocation device, a terminal device, and a vehicle allocation system.

Background Art

[0002] Conventionally, a vehicle allocation service that selects and dispatches a taxi that best meets a user's request through a vehicle allocation application or the like used by the user is known.

[0003] Furthermore, in such vehicle allocation services, in order to prevent the waiting time until a taxi arrives from becoming longer than a user expects, a technology has also been proposed that predicts the waiting time of taxis that are candidates for allocation, and only allocates taxis whose waiting time does not exceed a predetermined range (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problem to be Solved by the Invention

[0005] However, the prior art has room for further improvement in setting an appropriate vehicle allocation location according to the situation.

[0006] For example, at large-scale event venues and the like, when making a taxi reservation, it is practically difficult for a user to find a vehicle allocation location that avoids congestion and takes into account traffic regulations and the like by themselves.

[0007] As a result, there were problems with desirable ride-hailing not being achieved, such as users mistakenly specifying locations that were difficult to access or locations subject to traffic restrictions. Furthermore, if many users' ride-hailing reservations happened to concentrate on a single location, there was a risk of traffic congestion in that area.

[0008] One embodiment, made in view of the above, aims to provide a dispatch device, terminal device, and dispatch system that can set an appropriate dispatch location according to the situation. [Means for solving the problem]

[0009] A dispatch device according to one embodiment is a dispatch device that performs taxi dispatch processing and includes a controller. The controller receives the user's dispatch request, which includes the desired location information of the dispatch destination. And information on special offers at each store location Based on this, candidate dispatch locations are selected, and the dispatch location selected by the user is determined as the dispatch location, and the dispatch process is executed. [Effects of the Invention]

[0010] According to one embodiment, an appropriate vehicle dispatch location can be set depending on the situation. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a schematic diagram illustrating the vehicle dispatch method according to an embodiment. [Figure 2] Figure 2 shows an example of the configuration of a dispatch system according to an embodiment. [Figure 3] Figure 3 shows an example of the configuration of a user terminal according to the embodiment. [Figure 4] Figure 4 is a block diagram showing an example configuration of a dispatching system according to an embodiment. [Figure 5] Figure 5 shows an example of a facility information database. [Figure 6]Fig. 6 is a diagram illustrating an example of a traffic congestion information database. [Figure 7] Fig. 7 is a diagram illustrating an example of a vehicle information database. [Figure 8] Fig. 8 is a diagram illustrating an example of a surrounding information database. [Figure 9] Fig. 9 is an explanatory diagram of the number of vehicles available for waiting for boarding included in surrounding information. [Figure 10] Fig. 10 is a diagram illustrating an example of a reception information data table. [Figure 11] Fig. 11 is a diagram showing a situation in the description using Figs. 12 to 16. [Figure 12] Fig. 12 is a first diagram illustrating an example of an application screen when a vehicle dispatch is requested. [Figure 13] Fig. 13 is a second diagram illustrating an example of an application screen when a vehicle dispatch is requested. [Figure 14] Fig. 14 is a third diagram illustrating an example of an application screen when a vehicle dispatch is requested. [Figure 15] Fig. 15 is a fourth diagram illustrating an example of an application screen when a vehicle dispatch is requested. [Figure 16] Fig. 16 is a diagram illustrating an example of notification of vehicle dispatch information to a taxi. [Figure 17] Fig. 17 is a flowchart showing a processing procedure executed by the vehicle dispatch device according to the embodiment. MODE FOR CARRYING OUT THE INVENTION

[0012] Hereinafter, embodiments of the vehicle dispatch device, terminal device, and vehicle dispatch system disclosed in the present application will be described in detail with reference to the accompanying drawings. It should be noted that the present invention is not limited by the embodiments described below.

[0013] First, an outline of the vehicle dispatch method according to the embodiment will be described with reference to Fig. 1. Fig. 1 is a schematic explanatory diagram of the vehicle dispatch method according to the embodiment.

[0014] As already mentioned, for example, at large event venues, it is virtually impossible for users to find a taxi dispatch location that avoids congestion and takes traffic regulations into consideration when making a reservation.

[0015] As a result, there were problems with desirable ride-hailing not being achieved, such as users mistakenly specifying locations that were difficult to access or locations subject to traffic restrictions. Furthermore, if many users' ride-hailing reservations happened to concentrate on a single location, there was a risk of traffic congestion in that area.

[0016] Therefore, in the dispatch method according to this embodiment, a dispatch request is obtained from the user terminal 10 used by user U, a suitable candidate dispatch location is selected based on the location information of user U included in the dispatch request, and the dispatch process is executed based on the desired dispatch location selected by user U from among these candidates.

[0017] Specifically, as shown in Figure 1, in the dispatch method according to this embodiment, user U first uses their user terminal 10 to specify the destination and the number of passengers, etc., via a taxi dispatch application. In this embodiment, user U is assumed to be at or near an event facility 1000 such as a stadium where an event is being held.

[0018] Then, when user U performs the operation to send a dispatch request, user terminal 10 sends the dispatch request, including the destination, number of passengers, and user U's current location, to the dispatch device 100 (step S1). The location where the dispatch should be made should be the location requested by user U, but the current location accounts for the majority of requested locations, and the current location detection function of user terminal 10 can also be used, so the explanation will continue using the current location as a representative of the requested locations. If the requested location is other than the current location, user U will set the requested location through an input operation, and each process will be carried out based on that location.

[0019] When the dispatch device 100 receives a dispatch request from the user terminal 10, it selects an appropriate dispatch candidate location based on the current location of user U included in the dispatch request (step S2). An appropriate dispatch location is, for example, the nearest location to user U and a location where there is not a concentration of dispatch reservations.

[0020] The dispatching system 100 constantly collects pedestrian flow information, store information, etc. from the pedestrian flow control system 200, and traffic information, etc. from the traffic information provision system 300. Pedestrian flow information includes the flow of people and congestion levels at the event facility 1000 and its surroundings. Store information includes congestion levels at each store in the event facility 1000 and its surroundings. Traffic information includes congestion information, etc.

[0021] The dispatching system 100 selects an appropriate dispatch location while taking into account this pedestrian flow information, store information, traffic information, etc.

[0022] The dispatch device 100 then notifies the user terminal 10 of the selected candidate dispatch locations (step S3). The user terminal 10 presents the notified candidate dispatch locations to the user U and allows the user U to select their desired dispatch location from among the candidate locations.

[0023] Then, when user U performs the operation to select a desired pick-up location, user terminal 10 transmits the selected desired pick-up location to the dispatch device 100 (step S4). The dispatch device 100 receives this and performs the dispatch process based on the desired pick-up location selected by user U (step S5).

[0024] In this dispatch process, the dispatch device 100 transmits a dispatch request, including the desired pick-up location selected by the user U, to the onboard device 30 of each available taxi T (step S6). The onboard device 30 of each taxi T that receives the dispatch request then transmits to the dispatch device 100 a response indicating whether or not it accepts the dispatch request, and if it accepts, the estimated time of arrival at the desired pick-up location (step S7).

[0025] The dispatch device 100 then determines the dispatch details based on the acquired estimated arrival time, generates dispatch information including the determined dispatch details, and notifies the user terminal 10 and the in-vehicle device 30 (step S8).

[0026] As described above, in the dispatch method according to this embodiment, a dispatch request is obtained from the user terminal 10 used by user U, a suitable candidate dispatch location is selected based on the location information of user U included in the dispatch request, and the dispatch process is executed based on the desired dispatch location selected by user U from among these candidates.

[0027] Therefore, according to the dispatch method of this embodiment, it is possible to set an appropriate dispatch location depending on the situation.

[0028] Specific screen examples from the dispatch request in step S1 to the notification of dispatch information in step S8 will be described later using Figures 12 to 16. Below, a more detailed explanation will be given of a configuration example of the dispatch system 1 to which the dispatch method according to the embodiment is applied.

[0029] Figure 2 shows an example configuration of the dispatch system 1 according to the embodiment. As shown in Figure 2, the dispatch system 1 includes one or more user terminals 10, one or more in-vehicle devices 30, a dispatch device 100, a pedestrian flow control system 200, and a traffic information provision system 300. The pedestrian flow control system 200 includes a pedestrian flow control device 201, one or more store devices 202, and an event management device 203.

[0030] Furthermore, as shown in Figure 2, the user terminal 10, the in-vehicle device 30, the dispatch device 100, the pedestrian flow control system 200 (pedestrian flow control device 201, store device 202, event management device 203), and the traffic information provision system 300 are interconnected by a network N, such as the internet or a mobile phone network, and are configured to send and receive data to and from each other via the network N.

[0031] User terminal 10 is a terminal device carried and used by user U. User terminal 10 has a platform on which the application related to the dispatch system 1 runs. User terminal 10 is, for example, a mobile phone such as a smartphone, or a tablet device. User terminal 10 may also be a PC (Personal Computer), a PDA (Personal Digital Assistant), or a wearable device such as a wristwatch or glasses.

[0032] Figure 3 shows an example configuration of the user terminal 10. Specifically, as shown in Figure 3, the user terminal 10 comprises a terminal communication unit 10a, a terminal storage unit 10b, a terminal display unit 10c, a terminal operation unit 10d, and a terminal control unit 10e.

[0033] The terminal communication unit 10a is implemented, for example, by a network adapter. The terminal communication unit 10a is wirelessly connected to the network N described above and transmits and receives information with the dispatch device 100 and other various information provision devices and systems via the network N.

[0034] The terminal storage unit 10b is implemented by, for example, semiconductor memory elements such as RAM (Random Access Memory) and flash memory, or storage devices such as hard disks and optical discs. The terminal storage unit 10b stores programs for realizing various operations of the user terminal 10, various data used during program execution, and various data such as dispatch information acquired from external sources.

[0035] The terminal display unit 10c is implemented by, for example, a liquid crystal display or an organic electro-luminescence (EL) display. The terminal display unit 10c displays various information such as dispatch information. The terminal operation unit 10d is implemented by, for example, a touch switch film installed on the surface side of the terminal display unit 10c or a hard switch installed on the chassis of the user terminal 10. The terminal operation unit 10d outputs a signal corresponding to the operation performed by the user U.

[0036] The terminal control unit 10e is a so-called controller, and is realized, for example, by a CPU (Central Processing Unit) or MPU (Micro Processing Unit) executing various programs (not shown) stored in the memory unit 102 using RAM as the working area. Alternatively, the terminal control unit 10e can be realized by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array). The terminal control unit 10e controls the terminal communication unit 10a, the terminal memory unit 10b, the terminal display unit 10c, and the terminal operation unit 10d, and also transmits and receives various information with them, thereby realizing or executing the information processing functions and operations of the user terminal 10.

[0037] Returning to the explanation of Figure 2, the in-vehicle device 30 is installed in the taxi T and consists of, for example, a computer with communication capabilities. The in-vehicle device 30 operates as a terminal device on the taxi T side related to the dispatch system 1 and performs various information processing related to the dispatch system 1.

[0038] The dispatching device 100 is implemented, for example, as a cloud server, and continuously collects various information related to the dispatching system 1 from the in-vehicle device 30, the pedestrian flow control system 200, and the traffic information provision system 300 via the network N. Furthermore, when the dispatching device 100 receives the aforementioned dispatch request from user U, it executes each of the processes described in steps S1 to S8 based on the various information it has collected.

[0039] The pedestrian flow control system 200 is a system designed to alleviate congestion that occurs during events, etc. For example, depending on the congestion level around the event venue, it provides congestion information to users U around the event venue, distributes coupons that can be used at facilities around the event venue, provides various information such as congestion at facilities around the event venue, and controls pedestrian flow around the event venue.

[0040] Specifically, the pedestrian flow control device 201 collects images from cameras installed around the event venue and location information of users U around the event venue from user terminals 10 to understand the congestion situation around the event venue. The pedestrian flow control device 201 also obtains information such as the number of event participants and the start and end times of the event from the event management device 203. In addition, the pedestrian flow control device 201 obtains information on coupons issued by each store and congestion status from each store's device 202. Furthermore, the pedestrian flow control device 201 obtains information such as traffic congestion on roads around the event venue and the operation and congestion status of public transportation near the event venue from the traffic information provision system 300. Based on this information, the pedestrian flow control device 201 understands the current congestion situation, predicts future congestion situations, and provides information on suitable routes to avoid congestion and distributes coupons to each user terminal 10 according to the congestion situation around the event venue and the coupons issued and congestion status of nearby stores (facilities), thereby controlling pedestrian flow and mitigating congestion. The store device 202 is installed in each store within the event facility 1000 and its surrounding area, and consists of a tablet terminal, PC, etc. The store device 202 provides the aforementioned congestion information, coupon information, and other store information to the pedestrian flow control device 201, etc., through operation by store staff, etc.

[0041] The traffic information provision system 300 is a system that provides traffic information operated by public interest corporations, general businesses, etc., to the pedestrian flow control device 201, etc., and is composed of server equipment, etc. The traffic information includes congestion information, information on the operation and congestion status of public transportation, etc.

[0042] It should be noted that the configuration example of the dispatch system 1 shown in Figure 2 is merely an example, and it is not necessarily required to be configured as shown. For example, the specific form of distribution and integration of the dispatch device 100, the pedestrian flow control system 200, and the traffic information provision system 300 is not limited to that shown, and all or part of them can be appropriately distributed and integrated according to various loads, usage conditions, operating entities (businesses), etc.

[0043] Next, the configuration of the dispatching system 100 according to the embodiment will be described. Figure 4 is a block diagram showing an example of the configuration of the dispatching system 100 according to the embodiment. Note that Figure 4 shows only the components necessary to explain the features of the embodiment, and descriptions of general components are omitted.

[0044] In other words, each component shown in Figure 4 is a functional concept and does not necessarily need to be physically configured as shown. For example, the specific forms of distribution and integration of each block are not limited to those shown, and it is possible to configure all or part of them by functionally or physically distributing and integrating them in any unit according to various loads and usage conditions. Also, in the explanation using Figure 4, explanations of components that have already been explained may be simplified or omitted.

[0045] As shown in Figure 4, the dispatch device 100 according to this embodiment includes a communication unit 101, a storage unit 102, and a control unit 103.

[0046] The communication unit 101 is implemented, for example, by a network adapter. The communication unit 101 is connected to the aforementioned network N by wire or wireless, and transmits and receives information between the user terminal 10, the in-vehicle device 30, the pedestrian flow control system 200, and the traffic information provision system 300 via the network N.

[0047] The storage unit 102 is implemented by, for example, a semiconductor memory element such as RAM or flash memory, or a storage device such as a hard disk or optical disc. In the example shown in Figure 4, the storage unit 102 stores the collected information DB (Data Base) 102a and the received information data table 102b.

[0048] The collected information DB102a is a database of various information collected by the collection unit 103a, which will be described later. The collected information DB102a includes facility information DB102a1, traffic congestion information DB102a2, vehicle information DB102a3, and surrounding area information DB102a4, all relating to the dispatch management area, for example, the event (venue) area in this embodiment. The reception information data table 102b is a data table of dispatch information, including information on dispatch requests received from user U and the determined dispatch details.

[0049] Here, we will explain examples of the facility information DB102a1, traffic congestion information DB102a2, vehicle information DB102a3, surrounding area information DB102a4, and reception information data table 102b, which are included in the collected information DB102a.

[0050] As shown in Figure 5, the facility information DB 102a1 is a database of information about various facilities (event venues, etc.) obtained (provided) from the pedestrian flow control system 200. It stores data for the following data items: "Facility ID" which indicates the identification code of the facility; "Facility Name" which indicates the name of the facility; "Facility Location" which indicates the location of the facility; "Related Area" which indicates the area affected when an event is held at the facility; "Ongoing Event" which indicates an event currently being held at the facility (including the preparation period, etc.); "Start Time" and "End Time" which indicate the start and end times of the event; "Number of Attendees" which indicates the number of attendees at the event; "Congestion Level" and "Congestion Level 15 Minutes Later" which indicate the current congestion level and predicted congestion level in and around the facility at 15 minutes later; and "Facility Data Time" which indicates the time when this data was acquired. The facility ID also functions as an identification code for the data record, and the data record identified by the facility ID stores information about the facility identified by that facility ID.

[0051] These data are registered in the pedestrian flow control system 200 by the administrator of the pedestrian flow control system 200, based on various event information provided by the event organizer, through methods such as inputting data via terminal operation. This data is then provided by the pedestrian flow control system 200 and registered in the facility information DB 102a1. In addition, the "number of attendees," "congestion level," and "congestion level after 15 minutes" are estimated by the pedestrian flow control system 200 by analyzing location data of each user U obtained from the user terminal 10, analysis data of images captured by cameras installed near the event venue, and entry / exit data from automatic gates installed at the event venue. This data is then provided by the pedestrian flow control system 200 and registered in the facility information DB 102a1. Furthermore, regarding the "congestion level," congestion level data for each area, obtained by dividing the area around the event venue into smaller areas, is also provided by the pedestrian flow control system 200 and registered in the facility information DB 102a1.

[0052] Furthermore, as shown in Figure 6, the traffic congestion information DB102a2 is a database of traffic congestion information obtained (provided) from the traffic information provision system 300, and stores data for each of the following data items: "Traffic Congestion ID" which indicates the identification code of congestion, "Congestion Area" which indicates the road section where congestion is occurring, "Cause" which indicates the cause of congestion, "Congestion Severity" and "Predicted Congestion Severity 15 Minutes Later" which indicate the current congestion (Traffic Congestion Data Time) and the predicted degree of congestion 15 minutes later, and "Traffic Congestion Data Time" which indicates the time of acquisition of this data. The Traffic Congestion ID also functions as an identification code for the data record, and the data record identified by the Traffic Congestion ID stores the information related to the congestion identified by the facility ID.

[0053] This data is generated by the traffic information provision system 300 by analyzing data from various sensors, such as cameras, installed at various points along the road, and by analyzing vehicle driving data provided by each vehicle. This data is then provided by the traffic information provision system 300 and registered in the congestion information DB 102a2.

[0054] Furthermore, as shown in Figure 7, the vehicle information DB 102a3 is a database of information about each taxi T, and stores data for the following data items: "Vehicle ID" which indicates the vehicle identification code, "Displayed Vehicle Number" which indicates the vehicle number displayed on the vehicle for guidance, "Current Vehicle Location" which indicates the vehicle's current location, "Vehicle Status" which indicates the vehicle's current status (operating status of the taxi T, e.g., occupied, vacant, etc.), and "Reservation ID" which indicates the identification number of the dispatch reservation. The vehicle ID also functions as an identification code for the data record, and the data record identified by the vehicle ID stores the information about the vehicle identified by that vehicle ID. In addition, the "Reservation ID" uses the dispatch reservation identification code used for the "Reception ID" in the reception information data table 102b in Figure 10, which will be described later, and the same data record is linked to both the "Reservation ID" and the "Reception ID".

[0055] The "Vehicle ID" and "Displayed Vehicle Number" are registered in the Vehicle Information DB 102a3 by methods such as input by the administrator or operator of the dispatch device 100 via terminal operation. In addition, the "Current Vehicle Location" and "Vehicle Status" are registered in the Vehicle Information DB 102a3 based on location information and vehicle availability information transmitted from the onboard device 30. The "Reservation ID" is registered in the Vehicle Information DB 102a3 based on the dispatch processing result by the dispatch device 100 (dispatch information corresponding to automatic dispatch by the dispatch device 100 or manual dispatch by an operator, and is the data registered in the "Reception ID" in the reception information data table 102b in Figure 10 described later).

[0056] Furthermore, as shown in Figure 8, the surrounding information DB 102a4 contains information about each area surrounding each event facility 1000. For example, it stores various data about each area formed by dividing the area surrounding the event facility 1000 with multiple lines extending east-west and north-south. The surrounding information DB102a4 stores data for each of the following data items: "Surrounding Information ID" which indicates the identification code of the surrounding information; "Target Facility ID" which indicates the identification number of the target facility; "Reference Location" which indicates the reference location of the area (e.g., the centroid); "Area Congestion Level" which indicates the degree of congestion in the area; "Taxi Dispatch Availability" and "Taxi Dispatch Location" which indicate whether or not taxi T can be dispatched in the area and where it can be dispatched; "Number of Available Taxis for Waiting" which indicates the maximum number of taxis that can wait in the area suitable for taxi T to wait for passengers; "Partner Stores" which indicates various data (store name, store type, etc.) about stores that have partnered with the area for pedestrian flow control (taxi waiting); "Coupons" which indicates various data (coupon details, coupon recognition data (coupon recognition data output from the user terminal 10 when using a coupon (e.g., a two-dimensional code))) about coupons (benefits) issued by partner stores in the area; and "Store Status" which indicates the congestion level of partner stores in the area. Furthermore, the peripheral information ID also functions as an identification code for data records, and the data record identified by the peripheral information ID will store information related to that peripheral information ID.

[0057] The "surrounding information ID," "target facility ID," "reference location," "taxi dispatch availability," "taxi dispatch location," and "number of taxis available for pickup" are registered in the surrounding information DB 102a4 by methods such as input by the administrator or operator of the dispatch device 100 via terminal operation. In addition, "partner stores," "coupons," and "store status" are registered in the surrounding information DB 102a4 by methods such as input by the administrator or operator of the dispatch device 100 via terminal operation, or by methods such as input by the administrator or operator of the store device 202 via terminal operation. Finally, the "area congestion level" is provided by the pedestrian flow control system 200 and registered in the surrounding information DB 102a4.

[0058] "Taxi dispatch location" refers to the location of each point in the aforementioned area set up around event facility 1000 that could be a suitable dispatch location. These points are selected in advance for reasons such as having a wide shoulder, no obstacles such as fences between the road and the sidewalk, and not being near intersections or bus stops, making them suitable locations for dispatch. "Taxi dispatch availability" is a flag indicating whether or not a suitable dispatch location exists in the area.

[0059] The "taxi dispatch locations" (areas where taxis are stationed) can, of course, include stores with parking lots. In the case of stores, if they have already made arrangements to allow the use of their parking lots as taxi dispatch locations, those parking lots can be designated as "taxi dispatch locations."

[0060] "Number of taxis available for pickup" refers to the number of taxis T available for pickup by user U at each taxi dispatch location.

[0061] Let's explain this "number of taxis available for pickup" in detail. As shown in Figure 9, let's assume that a taxi dispatch point A1 is set up in the middle of a certain road. We will consider an area R1 along the road centered on this point A1.

[0062] If a taxi reservation is already registered with location A1 as the pick-up location, based on a ride request from user U who is near location A1, then setting the same location A1 as the pick-up location for another ride request from user U who is also near location A1 may cause problems for taxi T to stop at the pick-up location and for user U to board taxi T. This problem is particularly likely to occur if the pick-up location is the same for many ride requests from user U.

[0063] Therefore, in this embodiment, a "number of vehicles that can wait for a ride" is set to limit the maximum number of vehicles that can be dispatched to the same dispatch location. The maximum number of vehicles that can be dispatched should be determined based on the number of vehicles that can park without obstruction at the dispatch location, for example, the area of ​​the parking space, the width of the road, and any fences installed on the road (obstacles that would hinder the stopping of taxis T or the boarding of taxis T).

[0064] Furthermore, when setting the same dispatch location for multiple user U's dispatch requests, it is also effective to slightly distribute the dispatch locations. Specifically, as shown in Figure 9, in area R1, for example, location A1 (the location registered in "Taxi Dispatch Location" in surrounding information DB102a4) is used as the center point, and locations A1 are distributed at regular intervals (here, n meters that do not hinder the parking of taxis T in a line). In this case, each distributed location can be represented by assigning a number to the dispatch location A1, such as A1-0, A1-1, A1-2, and so on.

[0065] If the dispatch location determined based on user U's dispatch request overlaps with a dispatch location determined based on another dispatch request, these dispersed locations are determined as detailed dispatch locations and guided to user U.

[0066] Furthermore, the "number of taxis available for pickup" corresponds to the maximum number of pickup locations that can be appropriately set in area R, which is within a suitable range from point A1 (a range that does not cause problems as a change in pickup location), when distributing the pickup locations. In other words, the "number of taxis available for pickup" corresponds to the maximum number of pickup locations when appropriate distribution locations are set, avoiding intersections and bus stops, which are unsuitable locations for taxis T to stop.

[0067] Furthermore, as shown in Figure 10, the reception information data table 102b is a table of information regarding received dispatch requests, and stores data for each of the following data items: "Reception ID," which is the identification code for the dispatch request; "User Name," which indicates the name of the user U who made the dispatch request (information for confirming the user U who made the dispatch request); "User Access Information," which indicates information for communicating with the user U who made the dispatch request (for example, an email address); "User Location," which indicates the location of the user U who made the dispatch request; "Destination," which indicates the destination in the dispatch request; "Number of Passengers," which indicates the number of passengers in the dispatch request; "Dispatch Vehicle ID," which indicates the vehicle to be dispatched; "Dispatch Area ID," which indicates the area (location) to be dispatched; "Scheduled Boarding Time," which indicates the scheduled boarding time of the dispatched vehicle; "Dispatch Status," which indicates the dispatch status of the vehicle to be dispatched (before boarding, boarding completed, disembarking (arrival at destination) completed); and "Reception Time," which indicates the time the dispatch request was received. Furthermore, the reception ID also functions as an identification code for the data record. The data record identified by the reception ID will store all the information related to the reception (dispatch) information identified by that reception ID.

[0068] Furthermore, the "Dispatch Vehicle ID" uses the vehicle identification code used for the "Vehicle ID" in the vehicle information DB102a3 shown in Figure 7, and the same data record will be linked for both the "Dispatch Vehicle ID" and the "Vehicle ID". Similarly, the "Dispatch Area ID" uses the identification code for the surrounding information used for the "Surrounding Information ID" in the surrounding information DB102a4 shown in Figure 8, and the same data record will be linked for both the "Surrounding Information ID" and the "Dispatch Area ID".

[0069] The data for "User Name," "User Access Information," "User Location at Time of Request," "Destination," "Number of Passengers," "Scheduled Boarding Time," and "Request Time" are generated when User U inputs information into User Terminal 10 when requesting a taxi T, and also by the GPS receiver and timing device built into User Terminal 10. This data is then transmitted from User Terminal 10 to the dispatch device 100. The data for "Dispatched Vehicle ID," "Vehicle ID," and "Scheduled Boarding Time" are generated by the dispatch processing unit 103e when determining the dispatch details (the "Scheduled Boarding Time" is updated as needed depending on the status of taxi T). The data for "Dispatch Status" is generated by the in-vehicle device 30 based on the status of the taxi T's fare meter and the results of the analysis of images captured by the in-vehicle camera, and the collection unit 103a collects (receives) this data from the in-vehicle device 30.

[0070] Regarding the data registration process for the reception information data table 102b, the above explanation is an example where user U requests a taxi using the taxi dispatch app on user terminal 10. However, in the case of a taxi dispatch request made by voice over the phone, the operator of the dispatch device 100 will input the following data into the reception information data table 102b: "user name", "user access information", "user location at time of reception", "destination", "number of passengers", "scheduled time of boarding", and "reception time".

[0071] Returning to the explanation of Figure 4, the control unit 103 is a so-called controller, and is realized, for example, by a CPU or MPU executing various programs (not shown) stored in the memory unit 102 using RAM as the working area. Alternatively, the control unit 103 can be realized by an integrated circuit such as an ASIC or FPGA.

[0072] The control unit 103 includes a collection unit 103a, an acquisition unit 103b, a selection unit 103c, a notification unit 103d, and a vehicle dispatch processing unit 103e, and realizes or executes the information processing functions and operations described below.

[0073] The collection unit 103a continuously collects various types of information contained in the aforementioned collection information DB 102a via the communication unit 101 and stores them in the storage unit 102. For data that changes over time, the data stored in the storage unit 102 is updated with the new data collected by the collection unit 103a.

[0074] Specifically, the collection unit 103a obtains data from the event management device 203, including "facility name," "currently held event," "related area," "currently held event," "start time," "end time," "number of visitors," and "facility data time," and stores it in the facility information DB 102a1 with the "facility ID" data attached. In addition, the collection unit 103a obtains data from the pedestrian flow control device 201, including data identifying the facility (for example, data of the same type as the "facility ID"), "congestion level," "congestion level 15 minutes later," and "facility data time," and stores it in the corresponding data record in the facility information DB 102a1. The "facility data time" stored is the latest time the corresponding record in the facility information DB 102a1 was updated, i.e., the latest data update time.

[0075] Furthermore, the collection unit 103a continuously obtains data such as "congested area," "cause," "congestion degree," "predicted congestion degree 15 minutes later," and "congestion data time" from the traffic information provision system 300, assigns "congestion ID" data to it, stores it in the congestion information DB 102a2, and updates it with the latest data.

[0076] Furthermore, the collection unit 103a acquires data from the traffic information provision system 300 if either the "congestion level" or the "predicted congestion level 15 minutes later" indicates the occurrence of congestion, and stores it in the congestion information DB 102a2. If both the "congestion level" and the "predicted congestion level 15 minutes later" indicate the absence of congestion, the corresponding data record is deleted.

[0077] Furthermore, the collection unit 103a continuously obtains data such as "Vehicle ID," "Current Vehicle Location," and "Vehicle Status" from the in-vehicle device 30, stores the "Vehicle ID" in the same data record in the vehicle information DB 102a3, and updates it with the latest data. The "Vehicle ID" and "Displayed Vehicle Number" are registered in the vehicle information DB 102a3 in advance for the managed vehicles by methods such as input by the dispatching device 100 administrator, operator, etc., via terminal operation. In addition, regarding the "Reservation ID" in the vehicle information DB 102a3, when the dispatch reservation is completed, the data of the "Reception ID" in the corresponding data record in the reception information data table 102b is stored by the dispatching processing unit 103e, which will be described later.

[0078] Furthermore, the collection unit 103a generates and stores data such as the "target facility ID," "reference location," "taxi dispatch availability," "taxi dispatch location," and "number of taxis waiting to be picked up," which are set by input operations in the dispatch device 100, in the surrounding information DB 102a4, adding the "surrounding information ID." In addition, the collection unit 103a obtains data on the location of stores, coupons, and store (congestion) status from the store device 202 as needed, and stores the "partner store," "coupon," and "store status" in the corresponding data record in the surrounding information DB 102a4 (determined by the "reference location" data and the store location), and updates it with the latest data.

[0079] In the above example, the data collection unit 103a collected various data from the pedestrian flow control device 201, the store equipment 202, and the event management device 203. However, if the pedestrian flow control device 201, as part of the pedestrian flow control system 200, is collecting this data for pedestrian flow control operations, it is more efficient to collect this data from the pedestrian flow control device 201.

[0080] The acquisition unit 103b acquires a dispatch request from the user terminal 10 via the communication unit 101 and notifies the selection unit 103c. The acquisition unit 103b also acquires the desired dispatch location selected by user U from the user terminal 10 via the communication unit 101 and notifies the dispatch processing unit 103e.

[0081] Specifically, the acquisition unit 103b generates and stores data records in the reception information data table 102b with the "reception ID" data attached, based on the data included in the dispatch request acquired from the user terminal 10, including the "user name," "user access information," "user location at reception," "destination," "number of passengers," "scheduled boarding time," and "reception time."

[0082] The selection unit 103c selects an appropriate dispatch candidate location based on dispatch information such as the current location of user U included in the dispatch request acquired by the acquisition unit 103b, and various information included in the collected information DB 102a. The selection unit 103c also notifies the notification unit 103d of the selected dispatch candidate location to the user terminal 10.

[0083] Specifically, for example, the selection unit 103c selects candidate dispatch locations by sequentially executing the following processes (steps A, B, C).

[0084] (Step A) Based on the "Reference Location" data in the surrounding information DB 102a4, an area (identified by the "Surrounding Information ID" data) within a predetermined range (within a predetermined distance, within a predetermined travel time, etc.) from the current location of user U stored in the "User Location" field of the reception information data table 102b (or the location if a planned location for the scheduled boarding time, etc., is specified) is extracted.

[0085] (Step B) Based on the "area congestion level," "taxi dispatch availability," and "number of taxis waiting for pickup" data in the extracted area data records (identified by the "surrounding information ID" data) in the surrounding information DB102a4, and the number of taxis waiting for pickup in the relevant area which can be determined by searching the "dispatch area ID" data in the reception information data table 102b, a candidate dispatch location (identified by the "surrounding information ID" data) to be provided to user U is selected. In addition, information such as the congestion level of the route from user U's current location to the candidate dispatch location may be added as information for the determination.

[0086] (Step C) From the data record of the determined candidate dispatch location (identified by the "surrounding information ID" data) in the surrounding information DB102a4, the following data is extracted to be provided to user U: "reference location", "area congestion level", "partner store", "coupon", and "store status". In addition, data such as the distance traveled from user U's current location to the candidate dispatch location, travel time, and route congestion level may also be provided to user U.

[0087] The notification unit 103d notifies the user terminal 10 (using the "User Access Information" data in the reception information data table 102b) of various data regarding the candidate dispatch locations selected by the selection unit 103c via the communication unit 101. The data may also be processed as appropriate before notification, such as by creating an image displaying location, distance, and other data on a map.

[0088] Furthermore, the notification unit 103d notifies the user terminal 10 and the in-vehicle device 30 of the dispatch information determined by the dispatch processing unit 103e, which will be described later, via the communication unit 101.

[0089] The dispatch processing unit 103e executes the dispatch process based on the desired dispatch location selected by user U from the candidate dispatch locations, which is acquired by the acquisition unit 103b. When the acquisition unit 103b acquires the user U's desired dispatch location, it stores the "surrounding information ID" data corresponding to the desired dispatch location in the "dispatch area ID" of the corresponding data record in the reception information data table 102b.

[0090] In this dispatch process, the dispatch processing unit 103e transmits a dispatch request, including the desired dispatch location selected by the user U, to the onboard device 30 of each taxi T that is currently available, via the communication unit 101. Specifically, based on the "current vehicle location" and "vehicle status" data in the vehicle information DB 102a3, it selects a taxi T that is located within a predetermined range (within a predetermined distance or time) from the desired dispatch location and is in a state where it can accept a dispatch reservation (for example, available), and transmits a dispatch request (including the desired dispatch location and data such as "user name," "user access information," "destination," "number of passengers," and "scheduled pick-up time" from the reception information data table 102b) to the selected taxi T.

[0091] Furthermore, the dispatch processing unit 103e receives data on the acceptance of a dispatch request from the onboard device 30 of each taxi T that receives such a dispatch request, via the communication unit 101, and estimates the estimated time of arrival at the desired dispatch location. The estimated time of arrival is estimated based on the distance between the "current vehicle location" data of the relevant taxi's data record in the vehicle information DB 102a3 and the desired dispatch location (the "taxi dispatch location" data in the surrounding information DB 102a4, which is linked to the "dispatch area ID" of the relevant reception data record in the reception information data table 102b), and also takes into account various traffic congestion data from the traffic congestion information DB 102a2 (in particular, traffic congestion information on the route from the taxi T's current location to the desired dispatch location). The estimated time of arrival may also be transmitted from the onboard device 30 of each taxi T (estimated time of arrival manually set by the taxi driver or estimated by the navigation device).

[0092] The dispatch processing unit 103e then determines which taxi T to dispatch based on the estimated arrival time, and stores the "Vehicle ID" data of the dispatched taxi T and its estimated arrival time in the "Dispatched Vehicle ID" and "Scheduled Boarding Time" fields of the corresponding dispatch reception data record in the reception information data table 102b. Preferably, the dispatch processing unit 103e determines the taxi T with the earliest estimated arrival time as the dispatched vehicle, and stores the user U's desired boarding time and the later of the estimated arrival time in the "Scheduled Boarding Time" field. In this case, the dispatch processing unit 103e stores the "Reservation ID" data of the corresponding data record in the reception information data table 102b in the "Reservation ID" field of the relevant taxi data record in the vehicle information DB 102a3, and also stores data indicating the dispatch reservation in the "Vehicle Status" field.

[0093] The dispatch processing unit 103e then retrieves the following data from the relevant data record in the reception information data table 102b: "reception ID," "user name," "user access information," "destination," "number of passengers," "dispatch area ID," and "scheduled pick-up time." It also retrieves the corresponding "taxi dispatch location" data from the surrounding information DB 102a4 based on the "dispatch area ID," and then notifies the notification unit 103d of these retrieved data to the in-vehicle device 30.

[0094] Furthermore, the dispatch processing unit 103e retrieves the "reception ID," "destination," "number of passengers," "dispatch area ID," and "scheduled pick-up time" data from the relevant data record in the reception information data table 102b. Based on the "dispatch area ID," it also retrieves the corresponding "taxi dispatch location," "partner stores," "coupons," and "store status" data from the surrounding information DB 102a4. The unit then notifies the user terminal 10 of the user U who made the dispatch request of the retrieved data via the notification unit 103d.

[0095] Subsequently, the collection unit 103a updates the "vehicle status" data of the corresponding taxi's data record in the vehicle information DB 102a3 based on the vehicle status data of taxi T acquired from the in-vehicle device 30, so that the dispatching operator of the dispatching device 100 can determine whether the dispatch has been completed (whether user U has boarded taxi T).

[0096] Next, in order to make the details of the dispatch process according to this embodiment easier to understand, we will explain it in detail using examples of the app screen when a dispatch request is made. Figure 11 is a diagram showing the situation in the explanation using Figures 12 to 16. Figures 12 to 15 are diagrams (1) to (4) showing examples of the app screen when a dispatch request is made. Figure 16 is a diagram showing an example of dispatch information notification to taxi T.

[0097] Figure 11 is a schematic diagram showing an overview of event facility 1000 and its surroundings. As shown in Figure 11, there are locations A1, A2, A3, and A11 around event facility 1000, which are registered in the "Taxi Dispatch Location" section of the surrounding information DB 102a4. Location A11 is the location where a store (Store A) is located nearby.

[0098] Furthermore, assume that there are three sets of users U01, U02, and U03 who are requesting rides around event facility 1000. Circles CU01, CU02, and CU03 indicate the range (the area within the circle) of potential pick-up locations for each of the pick-up requests from users U01, U02, and U03. The radius of these circles CU01, CU02, and CU03 represents the maximum distance rMAX from the user's location to a potential pick-up location.

[0099] Now, let's consider the case where user U01 makes a taxi dispatch request. As shown in Figure 12, user U01 launches the taxi dispatch application on their user terminal 10. As shown in Figure 12, the taxi dispatch application displays input fields for the destination and the number of passengers on the screen of the user terminal 10. The user terminal 10 has a touch panel screen, and input operations can be performed by touching the buttons and keyboard displayed on the screen, according to the displayed image and touch position.

[0100] When user U01 enters information into each of the above fields and touches the "Request" button, user terminal 10 transmits a dispatch request to dispatch device 100 that includes the entered information for each field, as well as user access information such as user U01's current location (based on the functions of user terminal 10, such as GPS) and stored information, name, and email address.

[0101] When the dispatch device 100 receives a dispatch request from user U01's user terminal 10, it selects an appropriate dispatch candidate location based on user U01's current location included in the request, and notifies the user terminal 10 of the selected dispatch candidate location, along with various related information.

[0102] In the situation shown in Figure 11, the dispatching device 100 first extracts points A1, A11, and A2, which are within a predetermined distance (CU01) from the user U01's current location, as candidate dispatch locations. Then, the dispatching device 100 further narrows down the candidate dispatch locations and determines their suitability order (guidance priority) based on various conditions for suitability as a dispatch location, such as the congestion level of each location, the congestion level of the route to each location, the presence and congestion level of shops etc. at each location, and the dispatch status at each dispatch location (whether or not the number of waiting vehicles has been reached). In the situation shown in Figure 11, since the area around point A2 and the route to point A2 are congested, the dispatching device 100 selects points A1 and A11 as candidate dispatch locations (excluding point A2) and notifies the user terminal 10 of various data regarding these selected candidate dispatch locations.

[0103] Although not shown in the diagram, it is also an effective method to configure the system so that user U can set various conditions for the dispatch location (for example, a location with a roof), and for the dispatch device 100 to exclude candidate dispatch locations that do not meet the set conditions.

[0104] When the user terminal 10 receives various data regarding the candidate dispatch locations selected by the dispatch device 100, it displays a list of each candidate dispatch location, as shown in Figure 13, allowing the user to select one. The user terminal 10 displays the list in the order of priority of the candidate dispatch locations included in the various data regarding the candidate dispatch locations, with higher priority locations displayed higher up in the list (in Figure 13, shorter distances are displayed higher up in the list due to higher priority). The user terminal 10 also displays various data regarding the candidate dispatch locations as appropriate. For example, as shown in Figure 13, the user terminal 10 displays candidate dispatch locations on a map near the event facility 1000 (stadium), distance comparison information to each candidate dispatch location, and store information (coupon information) near each candidate dispatch location. In addition, the user terminal 10 may also display, for example, the level of congestion near the candidate dispatch locations and store information, and various display formats are possible, such as various list formats and icon displays.

[0105] For example, as shown in Figure 14, the user U may touch each point (candidate dispatch location) on the map screen displayed on the user terminal 10 to display detailed information for each location. Specifically, by touching the candidate dispatch location A11 on the map screen, the user terminal 10 displays information about stores near the candidate dispatch location, such as the store name and information about the availability and content of any coupons offered by the store.

[0106] Then, when user U01 selects a desired pick-up location from the list of candidate pick-up locations and touches the "Select" button, user terminal 10 transmits the desired pick-up location selected by user U01 to the pick-up device 100.

[0107] As shown in Figure 13, by displaying the list of candidate pick-up locations in order that location A1, which is closer to user U01, is ranked higher, user U can more easily select a pick-up location that requires less travel and physical exertion. Furthermore, by displaying various information about the candidate pick-up locations, user U can use this information to select an appropriate pick-up location, for example, by choosing a location near a favorite store where coupons can be used.

[0108] In addition, other useful information regarding potential pickup locations includes fare discounts based on the distance to the pickup location and routes to each potential pickup location.

[0109] This makes it easier for user U to select an appropriate pickup location based on information related to each potential pickup location, such as the degree of pedestrian congestion and road traffic congestion.

[0110] The dispatch device 100 then acquires the desired (selected) pick-up location transmitted from the user terminal 10 and performs the pick-up process based on the desired pick-up location. Furthermore, based on the results of the pick-up process, the dispatch device 100 notifies the user terminal 10 of user U01 and the in-vehicle device 30 of the taxi T that received the pick-up request from user U01 of the determined pick-up information, along with various related information.

[0111] At this time, as shown in Figure 15, the user terminal 10 of user U01 displays the scheduled dispatch time and the vehicle identification number of taxi T included in the determined dispatch information. In addition, the user terminal 10 of user U01 displays the route from user U01's current location to point A1 on the displayed map. It is also effective to display various information related to the determined dispatch location on the user terminal 10, such as the location of stores near the dispatch location (displayed on the map) and store information (store overview, congestion status, coupon information, etc.).

[0112] On the other hand, as shown in Figure 16, the display unit 31 of the in-vehicle device 30 of taxi T, which has received a dispatch request from user U01, displays a map screen showing the dispatch location (point A1) and user U01's current location, along with user information such as user U01's name. In addition, the in-vehicle device 30 displays the real-time estimated arrival time of taxi T, the error from the scheduled boarding time (original estimated arrival time), and precautions in case of congestion (for example, obtaining information related to the route from the traffic information provision system 300 to the dispatch location).

[0113] In order to display this information, various types of information, particularly location data that changes over time, are continuously exchanged (at predetermined time intervals) between the user terminal 10 of user U01 and the dispatching system 100, and between the in-vehicle device 30 and the dispatching system 100.

[0114] Next, we will explain examples of other situations for user U who requests a ride. First, we will explain the example of user U02's situation in Figure 11. When user U02 requests a ride by operating the user terminal 10, ride information such as user U02's current location is transmitted to the ride dispatch device 100. The ride dispatch device 100 receives the ride request, selects an appropriate candidate pick-up location based on the pick-up information included in the request, and notifies user U02's user terminal 10 of the selected candidate pick-up location, along with various related information.

[0115] In this situation, the dispatching system 100 first extracts points A1, A11, and A2, which are within a predetermined distance (CU02) from the user U02's current location, as candidate dispatch locations. Then, the dispatching system 100 further excludes point A2, the closest candidate dispatch location to the user U02's current location, because the area around point A2 and the route to point A2 are congested. In other words, in this example, point A2, which would normally be a dispatch location using the dispatching method, is excluded from the candidate dispatch locations because it is determined to be an unsuitable location based on the circumstances surrounding point A2.

[0116] Subsequently, a display screen showing locations A1 and A11 as candidate locations for vehicle dispatch will appear on user U02's user terminal 10, and from there, each vehicle dispatch operation and process will be carried out in the same manner as in the example situation described above.

[0117] Next, an example of the situation of user U03 in Figure 11 will be described. When user U02 operates user terminal 10 to request a ride, ride information such as user U03's current location is transmitted to the ride dispatch device 100. The ride dispatch device 100 receives the ride request, selects an appropriate candidate pick-up location based on the ride information included in the request, and notifies user U03's user terminal 10 of the selected candidate pick-up location, along with various related information.

[0118] In this situation, the dispatching device 100 first extracts points A11 and A3, which are within a predetermined distance (CU03) from the user U03's current location, as candidate dispatch locations. The dispatching device 100 then determines that there is no congestion near points A11 and A3, or along the routes to those points, and therefore designates points A11 and A3 as candidate dispatch locations (without excluding them).

[0119] Subsequently, user U03's user terminal 10 displays a screen showing locations A11 and A3 as potential dispatch locations. However, since store A is located near location A11, the display screen also shows information related to store A (such as the existence of store A, its congestion status, and any coupons issued) as information related to location A11. User U03 then selects a dispatch location, taking into account the information related to store A as well as the information related to location A11. From this point onward, each dispatch operation and process proceeds in the same manner as in the example described above.

[0120] Therefore, in this situation, instead of selecting point A3 (the nearest point) which would normally be the pickup point using the standard dispatch method, user U03 might choose point A11 as the pickup point for using store A. In other words, user U03 can select the appropriate pickup point depending on various circumstances regarding the pickup point.

[0121] Next, the processing procedure executed by the dispatch device 100 (control unit 103) according to the embodiment will be explained using Figure 17. Figure 17 is a flowchart showing the processing procedure executed by the dispatch device 100 according to the embodiment, and this process is repeatedly executed while the dispatch device 100 is operating.

[0122] As shown in Figure 17, first, in step S101, the control unit 103 collects various information such as information about the event facility 1000, stores it in each database of the collected information DB 102a, and then moves on to step S102. In step S102, the control unit 103 determines whether a new dispatch request has been received. If a dispatch request has been received (step S102, Yes), it moves on to step S103; if no dispatch request has been received (step S102, No), it moves on to step S105.

[0123] Then, in step S103, the control unit 103 obtains information regarding the dispatch request from user U, stores it in the reception information data table 102b, and proceeds to step S104.

[0124] In step S104, the control unit 103 selects an appropriate dispatch candidate location based on the contents of the dispatch request (contents stored in the reception information data table 102b: such as the current location of user U) and considering various data stored in the collected information DB 102a. It then transmits information regarding the selected dispatch candidate location to the user terminal 10 of user U, who made the dispatch request, and proceeds to step S105.

[0125] In step S105, the control unit 103 determines whether it has received information on the dispatch location selection result based on candidate dispatch locations from the user terminal 10 of user U, who is the source of the dispatch request. If it has received the information (step S105, Yes), it proceeds to step S106; otherwise, it terminates the process (step S105, No). If the dispatch location selection result has not been received, the control unit 103 terminates the process in step S105 (similar to not having received the dispatch location selection result information).

[0126] In step S106, the control unit 103 performs dispatch processing based on the dispatch location selection information of user U, who is the dispatch requester, and proceeds to step S107. In step S107, the control unit 103 transmits various dispatch information based on the dispatch processing results in step S106 to the user terminal 10 of user U, who is the dispatch requester, and to the in-vehicle device 30 of the taxi T whose dispatch has been decided, and then terminates the process.

[0127] As described above, the dispatch device 100 according to the embodiment is a dispatch device that performs dispatch processing for taxi T and includes a control unit 103 (corresponding to an example of a "controller"). The control unit 103 selects candidate dispatch locations, which are candidates for the dispatch location, based on the dispatch location information of user U included in the dispatch request of user U, and determines the candidate dispatch location selected by user U as the dispatch location and executes the dispatch processing.

[0128] Therefore, according to the dispatch device 100 of this embodiment, it is possible to set an appropriate dispatch location according to the situation.

[0129] Furthermore, the control unit 103 selects candidate dispatch locations according to the pedestrian flow conditions in the area indicated by the requested dispatch location information.

[0130] Therefore, according to the dispatch device 100 of this embodiment, it is possible to select an appropriate dispatch candidate location in accordance with the pedestrian flow conditions in the area where a dispatch candidate location may be set.

[0131] Furthermore, the control unit 103 selects the above-mentioned dispatch candidate locations according to the store information at each location.

[0132] Therefore, according to the dispatch device 100 of this embodiment, an appropriate dispatch candidate location is selected according to the presence or absence and congestion level of each store around the location where a dispatch candidate location may be set, and the user U can select an appropriate dispatch location accordingly.

[0133] Furthermore, the control unit 103 selects the candidate dispatch location according to the special offer information in the store information.

[0134] Therefore, according to the dispatch device 100 of this embodiment, an appropriate dispatch candidate location is selected, taking into account coupons issued by each store around the location where a dispatch candidate location may be set, and the user U can select an appropriate dispatch location accordingly.

[0135] Furthermore, the control unit 103 changes the above-mentioned benefit information based on the distance from the desired vehicle dispatch location information to the store's location.

[0136] Therefore, according to the dispatch device 100 of this embodiment, it is possible to provide user U with appropriate benefits at stores near the candidate dispatch location, depending on the distance traveled by user U to the candidate dispatch location, and user U can select an appropriate dispatch location accordingly.

[0137] Furthermore, the control unit 103 selects the candidate dispatch locations according to the traffic congestion along the route to each point for taxi T.

[0138] Therefore, according to the dispatch device 100 of this embodiment, it is possible to select a candidate dispatch location that is suitable for the movement of taxi T, in accordance with the traffic congestion situation.

[0139] Furthermore, the above requested vehicle dispatch location information is the current location information of user U.

[0140] Therefore, according to the dispatch device 100 of this embodiment, an appropriate dispatch candidate location is selected according to the current location of user U, who is estimated to have the highest demand. As a result, user U can skip the operation of specifying their desired dispatch location and can select an appropriate dispatch location with simple operation.

[0141] Furthermore, if the dispatch location determined above overlaps with another dispatch location determined by the control unit 103, the control unit 103 will distribute the dispatch locations.

[0142] Therefore, according to the dispatch device 100 of this embodiment, it is possible to prevent confusion when taxis T are parked or when users board taxis, which can occur when taxi T reservations are concentrated at the same dispatch location.

[0143] Furthermore, the user terminal 10 according to the embodiment is a terminal device used by user U and includes a terminal control unit 10e (corresponding to an example of a "terminal controller"). The terminal control unit 10e transmits a dispatch request including desired dispatch location information to the dispatch device 100 based on the dispatch request operation of user U, receives and displays dispatch candidate location information transmitted from the dispatch device 100 in response to the dispatch request, allows user U to select from the displayed dispatch candidate location information and transmit selected dispatch candidate location information to the dispatch device 100, and receives and displays dispatch information transmitted from the dispatch device 100 in response to the transmission of the selected dispatch candidate location information.

[0144] Therefore, according to the user terminal 10 of this embodiment, user U can set an appropriate dispatch location according to the situation and easily confirm the information of said dispatch location.

[0145] Furthermore, the dispatch system 1 according to the embodiment includes a dispatch device 100, a user terminal 10 used by user U (corresponding to an example of a "user terminal device"), and an in-vehicle device 30 installed in a taxi T. The dispatch device 100 selects candidate dispatch locations, which are candidates for the dispatch location, based on the desired dispatch location information included in the dispatch request from the user terminal 10, transmits candidate dispatch location information, which is information about the candidate dispatch location, to the user terminal 10, receives selected candidate dispatch location information selected by user U from the candidate dispatch locations from the user terminal 10, transmits dispatch request information to the selected candidate dispatch location based on the selected candidate dispatch location information to the in-vehicle device 30, receives acceptance / rejection information from the in-vehicle device 30 indicating whether the dispatch request information can be accepted, and if the acceptance / rejection information indicates acceptance, generates dispatch information related to the dispatch and transmits it to the user terminal 10 and the in-vehicle device 30. The user terminal 10 transmits a dispatch request including the desired dispatch location information to the dispatch device 100 based on the dispatch request operation of user U, receives and displays the dispatch candidate location information transmitted from the dispatch device 100 in response to the dispatch request, transmits the selected dispatch candidate location information related to the dispatch candidate location selected by user U from the displayed dispatch candidate location information to the dispatch device 100, and receives and displays the dispatch information transmitted from the dispatch device 100. The in-vehicle device 30 receives and displays the dispatch request information transmitted from the dispatch device 100, generates acceptance / rejection information for the dispatch request information based on the operation input and transmits it to the dispatch device 100, and receives and displays the dispatch information transmitted from the dispatch device 100.

[0146] Therefore, according to the dispatch system 1 of this embodiment, it is possible to provide taxi users with a service that sets an appropriate dispatch location according to the situation.

[0147] Further effects and modifications can be readily derived by those skilled in the art. Therefore, broader aspects of the present invention are not limited to the specific details and representative embodiments expressed and described above. Accordingly, various modifications are possible without departing from the spirit or scope of the overall concept of the invention as defined by the appended claims and their equivalents. [Explanation of Symbols]

[0148] 1. Dispatch System 10 User terminals 10a Terminal Communication Unit 10b Terminal storage unit 10c Terminal Display Unit 10d Terminal operation unit 10e Terminal Control Unit 30 Onboard equipment 100 Dispatch system 101 Communications Department 102 Storage section 102a Collection Information Database 102a1 Facility Information Database 102a2 Traffic Information Database 102a3 Vehicle Information Database 102a4 Surrounding Information Database 102b Reception Information Data Table 103 Control Unit 103a Collection Department 103b Acquisition Department 103c Selection Department 103d Notification Department 103e Dispatch Processing Unit 200-person flow control system 201 People flow control device 202 Store Equipment 203 Event Management Device 300 Traffic Information Provision System 1000 event facilities T Taxi U User

Claims

1. A dispatch system for performing taxi dispatch processing, comprising a controller, The aforementioned controller, Based on the user's requested pick-up location information and the special offer information of stores at each location, the system selects candidate pick-up locations. The dispatch process is executed by determining the dispatch location to be the candidate dispatch location selected by the user. Vehicle dispatch system.

2. The aforementioned controller, The candidate dispatch location is selected according to the pedestrian flow conditions in the area indicated by the aforementioned desired dispatch location information. The dispatch device according to claim 1.

3. The aforementioned controller, The aforementioned reward information is changed based on the distance from the desired vehicle dispatch location to the store's location. The dispatch device according to claim 1.

4. The aforementioned controller, The candidate dispatch locations are selected according to the traffic congestion along the taxi's route to each point. The dispatching device according to claim 1, 2, or 3.

5. The aforementioned requested vehicle dispatch location information is the user's current location information. The dispatching device according to claim 1, 2, or 3.

6. The aforementioned controller, If the aforementioned dispatch location overlaps with another dispatch location that has been determined, the dispatch locations will be distributed. The dispatching device according to claim 1, 2, or 3.

7. A dispatch method performed by a controller of a dispatch device that performs taxi dispatch processing, Based on the user's requested pick-up location information and the special offer information of stores at each location, the system selects candidate pick-up locations. The dispatch process is executed by determining the dispatch location to be the candidate dispatch location selected by the user. How to arrange a vehicle.

8. A program that causes a computer to perform taxi dispatch processing, Based on the user's requested pick-up location information and the special offer information of stores at each location, the system selects candidate pick-up locations. The dispatch process is executed by determining the dispatch location to be the candidate dispatch location selected by the user. A program that causes the aforementioned computer to perform a process.

9. A terminal device used by a user, which includes a terminal controller, The aforementioned terminal controller is Based on the user's dispatch request operation, a dispatch request including the desired dispatch location information is transmitted to the dispatch system. In response to a dispatch request, the dispatch device receives and displays dispatch candidate location information selected according to the store information and special offers at each location. The user selects a candidate dispatch location from the displayed candidate dispatch location information and transmits the selected candidate dispatch location information to the dispatch device. In response to the transmission of the selected candidate dispatch location information, the dispatch device receives and displays the dispatch information transmitted from the dispatch device. Terminal device.

10. It comprises a dispatching system, a user terminal device used by the user, and an in-vehicle device installed in the taxi. The aforementioned dispatching device is Based on the desired pick-up location information included in the pick-up request from the user terminal device and the special offer information of the store at each location, candidate pick-up locations are selected, and the information of these candidate pick-up locations is transmitted to the user terminal device. The system receives information on selected dispatch candidate locations chosen by the user from the aforementioned dispatch candidate locations from the user terminal device. The vehicle transmits dispatch request information to the selected dispatch candidate location based on the selected dispatch candidate location information to the in-vehicle device. The in-vehicle device receives acceptance / rejection information indicating whether or not the dispatch request information can be accepted, If the acceptance status information indicates acceptance, dispatch information for vehicle dispatch is generated and transmitted to the user terminal device and the in-vehicle device. The user terminal device is Based on the user's dispatch request operation, the dispatch device transmits a dispatch request including the desired dispatch location information. The dispatch device receives and displays the dispatch candidate location information selected according to the reward information transmitted in response to the dispatch request. The dispatch device receives the selected dispatch candidate location information for the dispatch candidate location selected by the user from the displayed dispatch candidate location information. The dispatching device receives and displays the dispatching information transmitted from the dispatching device. The in-vehicle device is The dispatch request information transmitted from the dispatch device is received and displayed. Based on the operation input, the system generates the acceptance / rejection information for the dispatch request information and transmits it to the dispatch device. The dispatching device receives and displays the dispatching information transmitted from the dispatching device. Ride-hailing system.

Images