Vehicle dispatch device, vehicle dispatch program, and terminal program

Abstract

To improve transportation efficiency while securing comfort of a user in a vehicle.SOLUTION: A vehicle dispatch device according to an aspect of an embodiment includes a controller configured to receive ride reservation information of a vehicle in which a plurality of users can ride from terminals of the plurality of users and determine dispatch of the vehicle according to the ride reservation information. When the controller receives, from the terminal of the first user, ride reservation information including attribute information of the first user and restriction information indicating a desire to restrict carpool passengers according to the attribute information, the controller determines dispatch of the vehicle to the first user. The controller compares the attribute information of the first user with the attribute information of the second user when the ride reservation information is received from the terminal of the second user after the dispatch of the vehicle to the first user is determined. The controller is configured to permit the second user to board the vehicle when the attribute information of the first user matches the attribute information of the second user.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The disclosed embodiments relate to a vehicle dispatch device, a vehicle dispatch program, and a terminal program. [Background technology]

[0002] In recent years, so-called demand buses, which are reservation-based shared buses that accept advance reservations from multiple users for a single bus, determine a route based on the reservations, and operate buses that allow multiple users to share a ride, have become increasingly common. Demand buses often use vehicles such as wagons and minivans because they have flexibility in their route and can accommodate the needs of small groups of people traveling to multiple destinations. Therefore, when many users share a vehicle, they may need to squeeze their own seats together to accommodate the ride, which can reduce the comfort of the vehicle. Furthermore, having a wide variety of users riding in a vehicle can also be a factor in reducing the comfort of the vehicle.

[0003] In the prior art, in order to improve the comfort of vehicles, a technology has been proposed that enables a vehicle to be operated in a plurality of riding modes, such as a demand bus riding mode and a taxi riding mode (see, for example, Patent Document 1). In the prior art, by operating a vehicle in, for example, a taxi riding mode, a user can occupy the vehicle with a single ride reservation. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-238831 Summary of the Invention [Problem to be solved by the invention]

[0005] However, when a vehicle is occupied as in the conventional technology, other users cannot ride in the vehicle, which reduces the transportation efficiency of the vehicle.

[0006] One aspect of the embodiment has been made in consideration of the above, and aims to provide a vehicle dispatching device, a vehicle dispatching program, and a terminal program that can improve transportation efficiency while ensuring the comfort of users in vehicles. [Means for solving the problem]

[0007] To solve the above problems and achieve the object, a vehicle dispatching device according to one aspect of the embodiment includes a controller that receives, from the terminals of multiple users, ride reservation information for vehicles that the multiple users can ride in, and determines the dispatch of the vehicle in accordance with the ride reservation information. When the controller receives, from the terminal of a first user, ride reservation information that includes attribute information of the first user and restriction information indicating a desire to restrict passengers according to the attribute information, the controller determines the dispatch of the vehicle to the first user. After determining the dispatch of the vehicle for the first user, when the controller receives ride reservation information from the terminal of a second user, the controller compares the attribute information of the first user with the attribute information of the second user. When the attribute information of the first user matches the attribute information of the second user, the controller allows the second user to ride in the vehicle. [Effects of the Invention]

[0008] In one aspect of the embodiment, the vehicle dispatching device allows the second user to board a vehicle when the attribute information of the first user matches the attribute information of the second user. This allows users with the same attributes to share the vehicle, ensuring the comfort of the users in the vehicle. Furthermore, since the second user also boards the vehicle in addition to the first user, the vehicle transportation efficiency can be improved compared to when the first user occupies the vehicle. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram for explaining an outline of a vehicle allocation method performed by a vehicle allocation system including a vehicle allocation device according to an embodiment. [Figure 2] FIG. 2 is a block diagram illustrating an example of the configuration of a vehicle dispatch system according to the embodiment. [Figure 3] FIG. 3 is a block diagram illustrating an example of the configuration of the vehicle dispatching device according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of user information. [Figure 5] FIG. 5 is a diagram showing an example of the boarding reservation information. [Figure 6] FIG. 6 is a diagram illustrating an example of the operating vehicle information. [Figure 7] FIG. 7 is a block diagram illustrating an example of the configuration of a user terminal according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a vehicle allocation determination process executed by the controller. [Figure 9] FIG. 9 is a diagram illustrating an example of the getting on and off place setting process executed by the controller. [Figure 10] FIG. 10 is a diagram showing an example of a display on the display unit of the user terminal. [Figure 11] FIG. 11 is a diagram showing an example of a display on the display unit of the user terminal. [Figure 12] FIG. 12 is a diagram showing a display example on the display unit of the user terminal. [Figure 13] FIG. 13 is a sequence diagram showing the operation procedure of the vehicle dispatch system. [Figure 14] FIG. 14 is a flowchart showing the processing procedure of the vehicle extraction processing executed by the vehicle dispatching device. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, with reference to the accompanying drawings, embodiments of the vehicle dispatching device, vehicle dispatching program, and terminal program disclosed in the present application will be described in detail. Note that the present invention is not limited to the embodiments described below. Also, in the following, "predetermined" can be read as "predetermined."

[0011] First, an overview of a vehicle dispatch method performed by a vehicle dispatch system including a vehicle dispatch device according to an embodiment will be described below with reference to FIG. 1. FIG. 1 is a diagram for explaining an overview of a vehicle dispatch method performed by a vehicle dispatch system including a vehicle dispatch device according to an embodiment. The vehicle dispatch system 1 accepts boarding reservation information from multiple users U, determines a travel route for the vehicle 100 according to the boarding reservation information, and dispatches the vehicle 100. The travel route includes stopping locations (boarding locations and disembarking locations) and stopping times (boarding times and disembarking times) of the vehicle 100. Furthermore, the stopping locations are, for example, bus stops whose locations are predetermined, but are not limited thereto and may be any locations designated by the user U.

[0012] As shown in FIG. 1, the vehicle dispatch system 1 includes a vehicle dispatch device 10, a user terminal 50, and a vehicle 100. The vehicle dispatch device 10 is an information processing device that receives reservation information for the vehicle 100 from the user terminal 50 of each of a plurality of users U and executes various processes, such as determining the dispatch of the vehicle 100 in accordance with the reservation information. The vehicle dispatch device 10 is realized, for example, by a server device. The vehicle dispatch device 10 may be configured as a cloud server that provides cloud services via a communication network such as the Internet or a mobile phone network, or may be configured to perform distributed processing using a plurality of servers. The vehicle dispatch device 10 also has a communication function for communicating with the user terminal 50, the on-board device 110 of the vehicle 100, and the like via the communication network.

[0013] The user terminal 50 is a terminal device carried by a user U who makes a ride reservation. The user terminal 50 is, for example, a smartphone, a notebook PC (Personal Computer), a desktop PC, a tablet terminal, etc. The user terminal 50 has a communication function for communicating with the vehicle dispatch device 10 and the like via a communication network.

[0014] In the example of FIG. 1, there are multiple users U, specifically, the users U are a "first user U1" and a "second user U2." The first user U1 possesses a "first user terminal 50a," and the second user U2 possesses a "second user terminal 50b." In the following, when there is no need to particularly distinguish between the first and second users U1 and U2, they will be referred to as users U, and when there is no need to particularly distinguish between the first and second user terminals 50a and 50b, they will be referred to as user terminals 50.

[0015] The vehicle 100 is a reservation-based shared bus that multiple users U can ride in together, or in other words, a demand bus. There are multiple vehicles 100, but this is not limited to this and there may be only one vehicle. Note that the vehicle 100 is not limited to a bus and may be, for example, a wagon type, a minivan type, or other vehicle, as long as it can accommodate multiple users U.

[0016] The vehicle 100 is equipped with an on-board device 110. The on-board device 110 has a communication function for communicating with the vehicle dispatch device 10 and the like via a communication network. When the driver manually drives the vehicle, the on-board device 110 receives operation schedule information including the driving route from the vehicle dispatch device 10 and notifies (for example, displays) the information to the driver. Furthermore, when the vehicle 100 is an autonomous vehicle without a driver (or the driver only responds to emergencies), the vehicle 100 travels autonomously according to the operation schedule information received from the vehicle dispatch device 10.

[0017] The vehicle dispatch device 10 of the vehicle dispatch system 1 according to this embodiment is configured to ensure the comfort of the user U in the vehicle 100 while improving transportation efficiency.

[0018] 1, the vehicle dispatching device 10 acquires operation status information indicating the operation status of the vehicle 100 from the in-vehicle device 110 (step S1). The operation status information includes, but is not limited to, location information of the vehicle 100, usage status including boarding and disembarking of the user U, and vacant seat information. Note that the vehicle dispatching device 10 repeatedly acquires the operation status information at regular or irregular intervals to grasp the latest operation status and manage the vehicle 100.

[0019] Next, the vehicle dispatching device 10 accepts ride reservation information from the first user terminal 50a of the first user U1 (step S2). Here, it is assumed that the first user U1 wishes (or allows) a user U who has the same attributes as the first user U1 to ride with them while riding in the vehicle 100. Conversely, it is assumed that the first user U1 does not wish (or allows) a user U who has different attributes from the first user U1 to ride with them while riding in the vehicle 100. In other words, the first user U1 wishes to limit the number of passengers in the vehicle 100. Therefore, in step S2, the vehicle dispatching device 10 accepts ride reservation information from the first user terminal 50a, the ride reservation information including the attribute information of the first user U1 and restriction information indicating a desire to limit the number of passengers according to the attribute information. The attribute information may be, for example, the gender and age group of the user U, which will be described later. The attribute information of the first user U1 may be registered in advance in the vehicle dispatching device 10. As an example, the attribute information of the first user U1 includes the gender being female, and the restriction information includes a desire to limit passengers to users U with the same attributes as the first user U1 himself, i.e., female users.

[0020] Next, the vehicle dispatching device 10 executes a vehicle extraction process to extract, from the plurality of vehicles 100, a vehicle 100 corresponding to the boarding reservation information received from the first user terminal 50a (step S3). Specifically, the vehicle dispatching device 10 extracts, from the plurality of vehicles 100, a vehicle 100 that can arrive at the boarding location specified by the first user U1 by the specified boarding time, based on the boarding reservation information and the operation status information. Then, the vehicle dispatching device 10 determines the dispatch of the extracted vehicle 100, and notifies the first user terminal 50a that the dispatch of the vehicle 100 has been determined (step S4).

[0021] Next, after deciding to dispatch the vehicle 100 to the first user U1, the vehicle dispatching device 10 accepts ride reservation information from the second user terminal 50b of the second user U2 (step S5). The ride reservation information includes attribute information of the second user U2, but is not limited to this, and the attribute information of the second user U2 may be registered in advance in the vehicle dispatching device 10.

[0022] Next, the vehicle allocation device 10 compares the attribute information of the first user U1 with the attribute information of the second user U2 (step S6). In other words, the vehicle allocation device 10 determines whether the attribute information of the first user U1 matches the attribute information of the second user U2. Here, the vehicle allocation device 10 determines whether the gender of the second user U2 in the attribute information of the second user U2 matches the gender of the first user U1 (i.e., female) in the attribute information of the first user U1.

[0023] If the attribute information of the first user U1 matches the attribute information of the second user U2, the vehicle dispatching device 10 allows the second user U2 to board the vehicle 100. Specifically, if the gender in the attribute information of the second user U2 is female and matches the gender (female) in the attribute information of the first user U1, the vehicle dispatching device 10 allows the second user U2 to board the vehicle 100. Therefore, the vehicle dispatching device 10 notifies the second user terminal 50b that the dispatch of the vehicle 100 has been decided (step S7).

[0024] Although not shown in the figures, if the attribute information of the first user U1 and the attribute information of the second user U2 do not match, the vehicle dispatching device 10 does not permit the second user U2 to board the vehicle 100. In such a case, the vehicle dispatching device 10 extracts and dispatches another vehicle 100 that can arrive at the boarding location specified by the second user U2 by the specified boarding time, based on the boarding reservation information and operation status information received from the second user terminal 50b.

[0025] The vehicle dispatching device 10 generates operation schedule information including an operation route in which the first user U1 and the second user U2 will be passengers, and notifies the in-vehicle device 110 (step S8). As a result, the vehicle 100 travels along an operation route in which the first user U1 and the second user U2 will be passengers, based on the notified operation schedule information.

[0026] As described above, the vehicle dispatching device 10 according to the present embodiment allows the second user U2 to board the vehicle 100 when the attribute information of the first user U1 matches the attribute information of the second user U2. In other words, the vehicle dispatching device 10 limits the users U who may ride in the vehicle 100 in which the first user U1 is riding, based on the attribute information. This allows users U (here, the first and second users U1 and U2) with the same attributes to ride in the vehicle 100, thereby ensuring the comfort of the user U (e.g., the first user U1) in the vehicle 100. In other words, the first user U1 may feel stressed when riding in the same vehicle as a user U with attributes different from himself / herself. However, by configuring the vehicle dispatching device 10 as described above, the stress felt by the first user U1 during the ride can be reduced, thereby ensuring the comfort of the user U (the first user U1) in the vehicle 100. Furthermore, since the vehicle 100 is occupied by the first user U1 as well as the second user U2, the transportation efficiency of the vehicle 100 can be improved compared to when the first user U1 occupies the vehicle 100.

[0027] Fig. 2 is a block diagram showing an example of the configuration of a vehicle dispatching system 1 according to an embodiment. Note that the block diagrams such as Fig. 2 show only components necessary for explaining the features of the embodiment, and general components are omitted.

[0028] The vehicle allocation system 1 includes the vehicle allocation device 10, the user terminal 50, and the in-vehicle device 110. The vehicle allocation device 10, the user terminal 50, and the in-vehicle device 110 are connected via a communication network N so as to be able to communicate with each other.

[0029] Next, a configuration example of the vehicle dispatching device 10 according to the embodiment will be described with reference to Fig. 3. Fig. 3 is a block diagram showing a configuration example of the vehicle dispatching device 10 according to the embodiment.

[0030] 3, the vehicle dispatching device 10 includes a communication unit 11, a controller (control unit) 20, and a storage unit 30. The communication unit 11 is an interface for communicating data between the user terminal 50 and the in-vehicle device 110. The communication unit 11 is, for example, a network interface card (NIC).

[0031] The controller 20 includes a microcomputer having a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), etc., and various other circuits. The controller 20 controls the overall operation of the vehicle dispatching device 10 by having the CPU execute a program (such as a vehicle dispatching program) stored in the ROM using the RAM as a working area. Note that the controller 20 may be partially or entirely configured with hardware such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

[0032] The storage unit 30 is, for example, a RAM or a data flash. The storage unit 30 can store user information 31, ride reservation information 32, operating vehicle information 33, information on various programs, etc. The vehicle dispatching device 10 may acquire the above-mentioned programs and various information via other computers or portable recording media connected via a wired or wireless network.

[0033] 4 is a diagram showing an example of the user information 31. The user information 31 is information about a user U registered in the vehicle dispatch system 1. The user information 31 is generated when a new user ID, which will be described later, is issued at any time, such as when the user U newly registers with the vehicle dispatch device 10 via the user terminal 50, or when the user terminal 50 transmits ride reservation information.

[0034] As shown in FIG. 4, the user information 31 has items such as "user ID," "name," "attribute information," and "reservation ID." "User ID" is identification information that identifies user U. "Name" is information that indicates the name of user U. In the example shown in FIG. 4, for convenience, "name" is written abstractly as "B01," but it is assumed that specific information is stored in "B01." Below, other information may also be written abstractly.

[0035] "Attribute information" is attribute information that indicates attributes possessed by user U. The attribute information includes, for example, the user U's gender, family structure, organizations to which the user U belongs (e.g., a company, school, club, etc.), facilities used (e.g., a shopping mall, hospital, etc.), age group (age), and smoking habit information such as whether the user is a smoker or non-smoker. Note that, although specific examples of attribute information have been given above, these are merely examples and are not limited to these. Furthermore, the attribute information may include all or part of the above-mentioned gender, family structure, etc. of user U. Furthermore, the above-mentioned attribute information is information input by user U to user terminal 50, but is not limited to this.

[0036] The "reservation ID" is identification information for identifying a ride reservation made by the user U. The reservation ID corresponds to the reservation ID of the ride reservation information 32, which will be described later.

[0037] In the example shown in FIG. 4, the user information identified by the user ID "A01" indicates that the name is "B01", the attribute information is "C01", and the reservation ID is "D01".

[0038] 5 is a diagram showing an example of the boarding reservation information 32. The boarding reservation information 32 is information relating to a boarding reservation made by a user. The boarding reservation information 32 is generated when a boarding reservation is confirmed and a new reservation ID, which will be described later, is issued.

[0039] As shown in Fig. 5, the boarding reservation information 32 has items such as "reservation ID," "user ID," and "reservation details." The "reservation ID" is identification information that identifies the boarding reservation. The "user ID" is identification information that identifies the user who made the boarding reservation, and corresponds to the user ID in the user information 31 described above.

[0040] "Reservation details" is the details of a ride reservation, and includes items such as boarding location, boarding time, disembarking location, disembarking time, and restriction information. The boarding location is information about the location where user U will board, and the boarding time is information about the time when user U will board. The disembarking location is information about the location where user U will disembark, and the disembarking time is information about the time when user U will disembark. The disembarking time is the approximate scheduled time when the ride dispatch device 10 will disembark at the disembarkation location when it accepts ride reservation information and decides to dispatch a ride, and is calculated, for example, based on the boarding location, boarding time, and disembarkation location.

[0041] The restriction information is information indicating whether or not restriction information is included in the ride reservation. Specifically, the restriction information is information indicating whether or not the ride reservation information includes attribute information of user U and restriction information indicating a desire to restrict fellow passengers according to the attribute information. If restriction information is included in the ride reservation information, information on the content of the restriction (for example, restricting fellow passengers to users U of the same gender) is also registered.

[0042] In the example shown in Figure 5, the boarding reservation information identified by the reservation ID "D01" indicates that the user ID is "A01", the boarding location in the reservation details is "F01", the boarding time is "10:00", the disembarking location is "F03", the disembarking time is "10:30", and the restriction information is "Yes".

[0043] Fig. 6 is a diagram showing an example of the operating vehicle information 33. The operating vehicle information 33 is information related to the vehicle 100. As shown in Fig. 6, the operating vehicle information 33 has items such as "vehicle ID," "operation status," and "reservation ID."

[0044] "Vehicle ID" is identification information that identifies vehicle 100. "Operation status" is information that indicates the current operation status of vehicle 100. "Operation status" includes, for example, location information of vehicle 100, usage status including boarding and disembarking of user U, and vacant seat information. "Reservation ID" is identification information that identifies a boarding reservation to board vehicle 100, and corresponds to the reservation ID in the boarding reservation information 32 described above.

[0045] In the example shown in FIG. 6, the operating vehicle information identified by the vehicle ID "G01" indicates that the operating status is "H01" and the reservation IDs are "D01, D02, D03, . . . ".

[0046] Returning to the explanation of Fig. 3, the controller 20 executes various processes such as a process of determining the dispatch of the vehicle 100 in accordance with the boarding reservation information, a process of comparing attribute information between users who have received boarding reservation information, and a process of permitting boarding in the vehicle 100 when the attribute information matches. These various processes will be described later with reference to Fig. 8 and subsequent figures.

[0047] Next, a configuration example of the user terminal 50 according to the embodiment will be described with reference to Fig. 7. Fig. 7 is a block diagram showing a configuration example of the user terminal 50 according to the embodiment.

[0048] 7, the user terminal 50 includes a communication unit 51, an operation unit 52, a display unit 53, a controller (control unit) 60, and a storage unit 70. The communication unit 51 is an interface for communicating data with the vehicle dispatching device 10. The communication unit 51 is, for example, an NIC.

[0049] The operation unit 52 is an input device that accepts various operations from the user U. Specifically, the operation unit 52 accepts input operations for ride reservation information. The ride reservation information may include the above-mentioned attribute information, restriction information, etc. The operation unit 52 outputs information according to the accepted input operations to the controller 20. Note that, for example, a touch panel display can be used as the operation unit 52, and in such a case, the display unit 53 functions as the operation unit 52.

[0050] The display unit 53 is a display that displays various information, such as a screen for accepting boarding reservation information and a screen showing vacant seat information.

[0051] The controller 60 includes a microcomputer having a CPU, ROM, RAM, etc., and various circuits. The controller 60 controls the overall operation of the user terminal 50 by having the CPU execute a program (such as a terminal program) stored in the ROM using the RAM as a work area. Note that the controller 60 may be partially or entirely configured using hardware such as an ASIC or FPGA.

[0052] The controller 60 transmits the ride reservation information input from the operation unit 52 to the vehicle dispatching device 10 via the communication unit 51. In detail, the controller 60 accepts input of a ride reservation including attribute information of the user U and restriction information indicating a desire to restrict fellow passengers according to the attribute information, and transmits the ride reservation information indicating the accepted ride reservation to the vehicle dispatching device 10. In addition, when the controller 60 receives various information from the vehicle dispatching device 10, such as vacant seat information, notification of reservation details, and notification of reservation confirmation, the controller 60 causes the display unit 53 to display such various information.

[0053] The storage unit 70 is, for example, a RAM or a data flash. The storage unit 70 can store information about various programs, etc. The user terminal 50 may also acquire the above-mentioned programs and various information via another computer or portable recording medium connected via a wired or wireless network.

[0054] Next, a detailed description will be given of the processing executed by the controller 20 of the vehicle dispatching device 10 shown in Fig. 3. The controller 20 acquires operation status information indicating the operation status of the vehicle 100 from the in-vehicle device 110 (see Fig. 2). The controller 20 stores the acquired operation status information in the storage unit 30 as operating vehicle information 33.

[0055] When the controller 20 receives the name, attribute information, etc. of the user U from the user terminal 50, the controller 20 stores the received name, attribute information, etc. of the user U in the storage unit 30 as user information 31.

[0056] The controller 20 receives ride reservation information from the user terminal 50. The controller 20 determines the allocation of the vehicle 100 in accordance with the received ride reservation information. Here, an example of the vehicle allocation determination process executed by the controller 20 will be described with reference to Fig. 8. Fig. 8 is a diagram showing an example of the vehicle allocation determination process executed by the controller 20.

[0057] In the example of FIG. 8, a first user U1, a second user U2, and a third user U3 make a reservation for a ride on the vehicle 100. Note that the first user U1 in FIG. 8 is a user identified by the user ID "A01" in FIGS. 4 and 5, and the second user U2 is a user identified by the user ID "A02." The third user U3 is a user identified by the user ID "A03." The first user U1 and the second user U2 have matching attributes. The first and second users U1, U2, and the third user U3 do not have matching attributes; in other words, they have different attributes. As an example, the attribute information of the first and second users U1, U2 includes the gender being female, and the attribute information of the third user U3 includes the gender being male. The ride reservation information of the first and second users U1, U2 both includes restriction information indicating that passengers are limited to users with the same attributes as themselves, i.e., female users U. The boarding reservation information of the first user U1 includes information to board at stop F01 and disembark at stop F03. The boarding reservation information of the second user U2 includes information to board at stop F02, which is between stop F01 and stop F03, and disembark at stop F04 after passing stop F03. The boarding reservation information of the third user U3 will be described later.

[0058] When the controller 20 receives ride reservation information from the user terminal 50 (first user terminal 50a) of the first user U1, the controller 20 sets a travel route for the vehicle 100 such that the first user U1 boards at stop F01 and disembarks at stop F03 in accordance with the ride reservation information. Then, the controller 20 determines the dispatch of the vehicle 100 to the first user U1 along the set travel route.

[0059] After determining the allocation of the vehicle 100 for the first user U1, the controller 20 receives ride reservation information from the user terminal 50 (second user terminal 50b) of the second user U2. Because the ride reservation information of the first user U1 and the ride reservation information of the second user U2 include restriction information, the controller 20 compares the attribute information of the first user U1 with the attribute information of the second user U2. Because the first and second users U1 and U2 are both female, the attribute information of the first user U1 matches the attribute information of the second user U2. Therefore, the controller 20 permits the second user U2 to ride in the vehicle 100. Specifically, in addition to the travel route set for the first user U1, the controller 20 sets a travel route for the vehicle 100 such that the second user U2 boards the vehicle at stop F02 and disembarks at stop F04. Then, the controller 20 determines the allocation of the vehicle 100 for the second user U2 along the set travel route.

[0060] After deciding to dispatch the vehicle 100 to the first and second users U1 and U2, the controller 20 receives ride reservation information from the user terminal 50 of the third user U3. Here, a case will be described in which the ride reservation information of the third user U3 includes information for boarding at one of stops F01, F02, and F03 and disembarking at stop F05. At least one of the first and second users U1 and U2 is riding in the vehicle 100 in the section from stop F01 to stop F04. Because the ride reservation information of the first and second users U1 and U2 both includes restriction information, the controller 20 compares the attribute information of the first and second users U1 and U2 with the attribute information of the third user U3 and determines whether the third user U3 is allowed to ride in the vehicle 100. In this example, the first and second users U1 and U2 are female, and the third user U3 is male, so the attribute information of the first and second users U1 and U2 does not match the attribute information of the third user U3. Therefore, the controller 20 does not permit the third user U3 to board (does not allow boarding) in the section from stop F01 to stop F04 where at least one of the first and second users U1 and U2 is boarding. Therefore, the controller 20 decides to dispatch a vehicle 100 other than the vehicle 100 boarded by the first and second users U1 and U2 to the third user U3.

[0061] On the other hand, a case will be described in which the boarding reservation information of the third user U3 includes boarding at, for example, stop F04. Since the second user U2 disembarks at stop F04, the restriction on fellow passengers in the vehicle 100 is lifted. Therefore, the controller 20 permits the third user U3 to board the vehicle 100; in other words, it can set stop F04 as the boarding location. Specifically, in addition to the operating routes set for the first and second users U1 and U2, the controller 20 sets an operating route for the vehicle 100 such that the third user U3 boards at stop F04 and disembarks at stop F05. Then, the controller 20 determines the allocation of the vehicle 100 for the third user U3 along the set operating route.

[0062] This allows the controller 20 to reduce the stress felt by the first and second users U1 and U2 when a user U of the opposite sex (here, the third user U3) is riding with them, thereby ensuring the comfort of the first and second users U1 and U2 in the vehicle 100.

[0063] When the dispatch of the vehicle 100 to each user U is determined and the boarding reservation is confirmed, the controller 20 stores the details of the confirmed boarding reservation in the storage unit 30 as boarding reservation information 32. Note that the boarding reservation information 32 in Fig. 5 shows an example in which a first user U1 boards at stop F01 and disembarks at stop F03, a second user U2 boards at stop F02 and disembarks at stop F04, and a third user U3 boards at stop F04 and disembarks at stop F05.

[0064] In the above example, the attribute information of the user U includes gender, and passengers in the vehicle 100 are restricted based on gender; however, this is not limiting. For example, the attribute information of the user U may include family structure, and the controller 20 may restrict passengers in the vehicle 100 based on the family structure. Specifically, if the first user U1 and the second user U2 are family (or relatives), the controller 20 permits the first user U1 and the second user U2, whose attribute information matches, to ride in the vehicle 100. On the other hand, if the third user U3 is not a family (or relative) of the first and second users U1 and U2, the controller 20 does not permit the third user U3, whose attribute information does not match, to ride in the vehicle 100 in which at least one of the first and second users U1 and U2 is riding. This allows the controller 20 to reduce the stress felt by the first and second users U1 and U2 when a user U other than a family member (here, the third user U3) is riding with them, thereby ensuring the comfort of the first and second users U1 and U2 in the vehicle 100.

[0065] Furthermore, the attribute information of the user U may include an organization (e.g., a company, a school, a club, etc.) to which the user U belongs, and the controller 20 may limit passengers in the vehicle 100 depending on the organization. Specifically, if the first user U1 and the second user U2 belong to the same organization, the controller 20 permits the first user U1 and the second user U2, whose attribute information matches, to ride in the vehicle 100. On the other hand, if the third user U3 does not belong to the organization of the first and second users U1 and U2, the controller 20 does not permit the third user U3, whose attribute information does not match, to ride in the vehicle 100 in which at least one of the first and second users U1 and U2 is riding. In this way, the controller 20 can reduce the stress felt by the first and second users U1 and U2 when a user U (third user U3) who does not belong to the same organization rides in the vehicle 100, thereby ensuring the comfort of the first and second users U1 and U2 in the vehicle 100.

[0066] Furthermore, the attribute information of the user U may include facilities used by the user U (e.g., shopping malls, hospitals, etc.), and the controller 20 may limit passengers in the vehicle 100 depending on the facilities. Specifically, when a first user U1 and a second user U2 use the same facility, the controller 20 permits the first user U1 and the second user U2, whose attribute information matches, to ride in the vehicle 100. On the other hand, when a third user U3 does not use the facilities used by the first and second users U1 and U2, the controller 20 does not permit the third user U3, whose attribute information does not match, to ride in the vehicle 100 in which at least one of the first and second users U1 and U2 is riding. In this way, the controller 20 can reduce the stress felt by the first and second users U1 and U2 when a user U (third user U3) who does not use the same facility rides in the vehicle 100, thereby ensuring the comfort of the first and second users U1 and U2 in the vehicle 100.

[0067] Furthermore, the attribute information of the user U may include the age group of the user U, and the controller 20 may limit passengers in the vehicle 100 according to the age group. Specifically, if the first user U1 and the second user U2 are in the same age group, the controller 20 permits the first user U1 and the second user U2, whose attribute information matches, to ride in the vehicle 100. On the other hand, if the third user U3 is in a different age group from the first and second users U1 and U2, the controller 20 does not permit the third user U3, whose attribute information does not match, to ride in the vehicle 100 in which at least one of the first and second users U1 and U2 is riding. In this way, the controller 20 can reduce the stress felt by the first and second users U1 and U2 when a user U (third user U3) of a different age group rides in the vehicle 100, thereby ensuring the comfort of the first and second users U1 and U2 in the vehicle 100.

[0068] Furthermore, the attribute information of the user U may include smoking habit information, such as whether the user is a smoker or a non-smoker, and the controller 20 may restrict passengers in the vehicle 100 according to the smoking habit information. Specifically, if the first user U1 and the second user U2 are non-smokers, the controller 20 permits the first user U1 and the second user U2, whose attribute information matches, to ride in the vehicle 100. On the other hand, if the third user U3 has smoking habit information (here, a smoker) that differs from the smoking habit information of the first and second users U1 and U2, the controller 20 does not permit the third user U3, whose attribute information does not match, to ride in the vehicle 100 in which at least one of the first and second users U1 and U2 is riding. In this way, the controller 20 can reduce stress felt by the first and second users U1 and U2, who are non-smokers, when the user U (third user U3), who is a smoker, rides in the vehicle 100, thereby ensuring the comfort of the first and second users U1 and U2.

[0069] Furthermore, the controller 20 may set a location related to the attribute information of the user U as a boarding and alighting location (stopping location) for the vehicle 100. In other words, the controller 20 may set a location related to a predetermined attribute as a boarding and alighting location for the vehicle 100 only for users U having the attribute. When the controller 20 sets a location related to the attribute information as a boarding and alighting location, the controller 20 does not allow the location (stopping location) to be set as a boarding and alighting location for other users U who do not have the attribute information. Here, an example of a boarding and alighting location setting process executed by the controller 20 will be described with reference to FIG. 9. FIG. 9 is a diagram showing an example of a boarding and alighting location setting process executed by the controller 20.

[0070] In the example of FIG. 9, a first user U1, a second user U2, and a third user U3 make a reservation for a ride on the vehicle 100. The first user U1 and the second user U2 have the same attributes. The first and second users U1, U2, and the third user U3 do not have the same attributes; in other words, they have different attributes. As an example, the attribute information of the first and second users U1, U2 includes information about the organization to which the first and second users U1, U2 belong (e.g., Company A), while the attribute information of the third user U3 does not include information about the organization. Furthermore, the ride reservation information of the first and second users U1, U2 both includes restriction information indicating that passengers are limited to users U who have the same attributes as the first and second users U1, U2, i.e., belong to the same organization. Furthermore, the stop F14 is a location related to the attribute information of the first and second users U1, U2, and here is a stop near the organization (Company A) to which the first and second users U1, U2 belong (Company A) or within the premises of the organization (Company A). The controller 20 allows the first and second users U1 and U2 to set this stop F14 as a boarding / alighting location. For example, based on the location information of company A to which the first and second users U1 and U2 belong, the controller 20 allows the first and second users U1 and U2 to set stop F14 within a predetermined range therearound as a boarding / alighting location (opens it as a boarding / alighting location). On the other hand, the controller 20 prevents the third user U3, who does not have the attribute information of company A, from setting stop F14 as a boarding / alighting location; in other words, the controller 20 does not open stop F14 as a boarding / alighting location.

[0071] More specifically, the ride reservation information of the first user U1 includes information to board at stop F11 and disembark at stop F14, which is related to the user's attributes. The ride reservation information of the second user U2 includes information to board at stop F12 and disembark at stop F14, which is related to the user's attributes. The ride reservation information of the third user U3 will be described later.

[0072] When the controller 20 receives ride reservation information from the user terminal 50 (first user terminal 50a) of the first user U1, the controller 20 sets a travel route for the vehicle 100 in accordance with the ride reservation information so that the first user U1 gets on at stop F11 and gets off at stop F14. Then, the controller 20 determines the dispatch of the vehicle 100 to the first user U1 along the set travel route.

[0073] After deciding to dispatch the vehicle 100 to the first user U1, the controller 20 receives ride reservation information from the user terminal 50 (second user terminal 50b) of the second user U2. Because the ride reservation information of the first user U1 and the ride reservation information of the second user U2 include restriction information, the controller 20 compares the attribute information of the first user U1 with the attribute information of the second user U2. Because the first and second users U1 and U2 belong to the same organization (company A), the attribute information of the first user U1 matches the attribute information of the second user U2. Therefore, the controller 20 permits the second user U2 to ride the vehicle 100. Specifically, in addition to the travel route set for the first user U1, the controller 20 sets a travel route for the vehicle 100 such that the second user U2 boards the vehicle at stop F12 and disembarks at stop F14. Then, the controller 20 determines the allocation of the vehicle 100 for the second user U2 along the set travel route.

[0074] After determining the allocation of the vehicle 100 to the first and second users U1 and U2, the controller 20 receives ride reservation information from the user terminal 50 of the third user U3. Here, a case will be described in which the ride reservation information of the third user U3 includes information for boarding at one of stops F11, F12, and F13 and disembarking at stop F15. At least one of the first and second users U1 and U2 is riding in the vehicle 100 in the section from stop F11 to stop F14. Because the ride reservation information of the first and second users U1 and U2 both includes restriction information, the controller 20 compares the attribute information of the first and second users U1 and U2 with the attribute information of the third user U3 and determines whether the third user U3 is allowed to ride in the vehicle 100. In this example, the first and second users U1 and U2 belong to the same organization (company A), and the third user U3 does not belong to that organization. Therefore, the attribute information of the first and second users U1 and U2 does not match the attribute information of the third user U3. Therefore, the controller 20 does not permit the third user U3 to board (does not permit boarding) in the section from stop F11 to stop F14 where at least one of the first and second users U1 and U2 is boarding. Furthermore, the controller 20 does not permit stop F14, which is related to the attribute information of the first and second users U1 and U2, to be set as a boarding / alighting location for the third user U3, who does not have that attribute information. Therefore, the controller 20 determines to dispatch a vehicle 100 other than the vehicle 100 boarded by the first and second users U1 and U2, to the third user U3.

[0075] On the other hand, a case will be described in which the boarding reservation information of the third user U3 includes boarding at, for example, stop F15. Because the first and second users U1 and U2 have already disembarked at stop F15, the restriction on fellow passengers in the vehicle 100 is lifted. Therefore, the controller 20 permits the third user U3 to board the vehicle 100; in other words, it can set stop F15 as the boarding location. Specifically, the controller 20 sets a travel route for the vehicle 100 such that the third user U3 boards at stop F15, in addition to the travel routes set for the first and second users U1 and U2. Then, the controller 20 determines the dispatch of the vehicle 100 for the third user U3 along the set travel route.

[0076] In this way, the controller 20 sets a location (stop location F14) related to the attribute information of the user U (for example, information about an organization to which the user U belongs) as a boarding and disembarking location for the vehicle 100. This allows the vehicle 100 to be used like a shuttle bus. More specifically, the vehicle 100 can be used like a shuttle bus that transports the user U to a location related to the attribute information of the user U, or transports the user U from a location related to the attribute information of the user U.

[0077] Next, examples of displays on the display unit 53 of the user terminal 50 will be described with reference to Figs. 10 to 12. Figs. 10 to 12 are diagrams showing examples of displays on the display unit 53 of the user terminal 50. Fig. 10 shows the display unit 53 transitioning from a boarding reservation information input screen to a screen showing vacant seat information. Fig. 11 shows the display unit 53 transitioning from a boarding reservation information input screen to a screen requesting approval of the reservation details. Fig. 12 shows the display unit 53 displaying a boarding reservation information input screen, which is a screen for setting a location related to the attributes of the user U (here, the organization to which the user U belongs) as a boarding and disembarking location for the vehicle 100.

[0078] As shown on the left side of FIG. 10, when accepting a ride reservation from user U, the controller 60 (see FIG. 7) of the user terminal 50 displays an input screen for accepting input of ride reservation information on the display unit 53. On the input screen, the boarding location is entered in input field 54a, the desired boarding time is entered in input field 54b, and the disembarking location is entered in input field 54c. The input screen also accepts restriction information indicating a desire to restrict fellow passengers according to the user U's attribute information. For example, the input screen displays passenger condition settings such as "female only," "non-smoking," and "affiliation (XX company)," and if the corresponding input field (checkbox) 54d is checked by the user U, the passenger restriction (restriction information) is accepted. FIG. 10 illustrates an example in which the attribute information of user U includes the gender being female, and the user U accepts restriction information indicating that the user U wishes to restrict fellow passengers to female users U with the same attribute as the user U.

[0079] The input screen displays a seat availability check button 54e and a reservation request button 54f. When the seat availability check button 54e is pressed by the user U, the user terminal 50 transmits the input ride reservation information to the vehicle dispatch device 10. The vehicle dispatch device 10 extracts a vehicle 100 corresponding to the ride reservation information transmitted from the user terminal 50, and transmits vacant seat information of the extracted vehicle 100 to the user terminal 50. The user terminal 50 displays the vacant seat information transmitted from the vehicle dispatch device 10 on the display unit 53. Specifically, as shown on the right side of FIG. 10 , the controller 60 of the user terminal 50 displays the vacant seat information in a display field 54g.

[0080] In this way, when the vehicle dispatching device 10 receives ride reservation information including attribute information and restriction information of the user U from the user terminal 50, the vehicle dispatching device 10 provides vacant seat information indicating the vacant seat status of the vehicle 100 corresponding to the ride reservation information to the user terminal 50. This allows the user U to easily know the vacant seat status of the vehicle 100 in which the user U wishes to ride, thereby improving convenience.

[0081] As shown on the left side of FIG. 11 , when the user U presses the reservation request button 54f on the input screen, the user terminal 50 transmits the input ride reservation information to the vehicle dispatching device 10. The vehicle dispatching device 10 extracts a vehicle 100 corresponding to the ride reservation information transmitted from the user terminal 50 and transmits information about the extracted vehicle 100 to the user terminal 50. The user terminal 50 displays the information about the vehicle 100 transmitted from the vehicle dispatching device 10 on the display unit 53 and requests approval of the reservation details. Specifically, as shown on the right side of FIG. 11 , the controller 60 of the user terminal 50 displays the information about the vehicle 100 in the display field 54h. Furthermore, a reservation approval button 54i and a cancel button 54k are displayed on the approval screen requesting approval of the reservation details. When the reservation approval button 54i is pressed by the user U, the user terminal 50 transmits approval information indicating that the reservation has been approved to the vehicle dispatching device 10. When approval information is sent from the user terminal 50, the vehicle dispatching device 10 generates operation schedule information including the operation route of the vehicle 100 according to the reservation details, determines the dispatch of the vehicle 100, and notifies the user terminal 50 that the reservation details have been confirmed. Note that when the user U presses the cancel button 54k, the reservation details are canceled.

[0082] As shown in FIG. 12, when the user U checks the input field (check box) 54d corresponding to "Affiliation (XX company)" in the passenger condition setting on the input screen, passenger restrictions (restriction information) are accepted. Also, on the input screen, in the input field 54a for boarding location and the input field 54c for disembarking location, it becomes possible to set a location related to the attribute information of the user U as the boarding and disembarking location of the vehicle 100. FIG. 12 shows an example in which the XX company to which the user U belongs is set as the disembarking location (see input field 54c).

[0083] Next, the operation procedure of the vehicle allocation system 1 will be described with reference to Fig. 13. Fig. 13 is a sequence diagram showing the operation procedure of the vehicle allocation system 1.

[0084] 13, the vehicle dispatching device 10 acquires operation status information indicating the operation status of the vehicle 100 from the in-vehicle device 110 (step S101). The vehicle dispatching device 10 repeatedly acquires the operation status information at any timing. The vehicle dispatching device 10 stores the acquired operation status information in the storage unit 30 as operating vehicle information 33.

[0085] The user terminal 50 registers the name, attribute information, etc. of the user U as user information in the vehicle dispatching device 10 (step S102). The vehicle dispatching device 10 executes a registration process to store the information received from the user terminal 50 in the storage unit 30 as user information 31 (step S103). In this registration process, a process is also performed to enable a location related to the attribute information of the user U to be set as a boarding and disembarking location for the vehicle 100 for each user U.

[0086] Next, the user U makes a reservation for a ride in the vehicle 100. Here, if the user U wants to check the availability of seats in the vehicle 100 that he / she wishes to ride in, the user terminal 50 transmits ride reservation information to the vehicle dispatch device 10 in response to a user operation, and requests the vehicle dispatch device 10 for available seat information (step S104).

[0087] The vehicle dispatching device 10 executes a vehicle extraction process to extract, from the plurality of vehicles 100, a vehicle 100 corresponding to the boarding reservation information received from the user terminal 50 (step S105). Note that detailed processing procedures of the vehicle extraction process in step S105 and step S108, which will be described later, will be described later with reference to FIG. 14.

[0088] Next, the vehicle dispatching device 10 notifies (transmits) the vacant seat information of the extracted vehicle 100 to the user terminal 50 (step S106). As a result, the vacant seat information is displayed on the display unit 53 of the user terminal 50 (see FIG. 10).

[0089] Next, if the user U who has checked the vacant seat information wishes to make a reservation for the vehicle 100, the user terminal 50 requests the vehicle dispatch device 10 to make a reservation for the vehicle 100 in response to a user operation (step S107). At this time, the user terminal 50 transmits (retransmits) the reservation information.

[0090] The vehicle dispatching device 10 executes a vehicle extraction process to extract a vehicle 100 corresponding to the boarding reservation information received from the user terminal 50 (step S108). Then, the vehicle dispatching device 10 notifies (transmits) the information of the extracted vehicle 100 to the user terminal 50, and requests approval of the reservation contents from the user terminal 50 (step S109). As a result, information on the vehicle 100 and the like are displayed on the user terminal 50 (see FIG. 11).

[0091] Next, if the user U approves the reservation details, the user terminal 50 transmits approval information indicating that the reservation has been approved in response to a user operation to the vehicle dispatching device 10 (step S110). When the approval information is transmitted from the user terminal 50, the vehicle dispatching device 10 generates (or updates) operation schedule information including an operation route of the vehicle 100 in accordance with the reservation details (step S111).

[0092] Next, the vehicle dispatching device 10 notifies the user terminal 50 that the reservation details have been confirmed (step S112). The vehicle dispatching device 10 also notifies (transmits) the operation schedule information generated in step S111 to the in-vehicle device 110 (step S113). As a result, the vehicle 100 travels along the operation route based on the notified operation schedule information. When the vehicle 100 travels along the operation route, the vehicle dispatching device 10 acquires the boarding and alighting status of the user U from the in-vehicle device 110 (step S114).

[0093] The vehicle dispatching device 10 manages the operation of the vehicle 100 according to the boarding and disembarking status of the user U and the operating status of the vehicle 100 (step S115). For example, when a user U who wishes to limit the number of fellow passengers gets into the vehicle 100, the vehicle dispatching device 10 manages the vehicle 100 as a vehicle with restricted fellow passengers. When a user U who wishes to limit the number of fellow passengers gets out of the vehicle 100, the vehicle dispatching device 10 manages the vehicle 100 as a vehicle with no passenger restrictions.

[0094] Next, the vehicle extraction process in the above-mentioned steps S105 and S108 will be described with reference to Fig. 14. Fig. 14 is a flowchart showing the processing procedure of the vehicle extraction process executed by the vehicle dispatching device 10.

[0095] 14, the controller 20 of the vehicle dispatching device 10 acquires operation status information indicating the operation status of the vehicle 100 from the in-vehicle device 110 (step S201). Next, the controller 20 selects, from the plurality of vehicles 100, a vehicle 100 that is located near the boarding location in the boarding reservation information (step S202). Note that when the controller 20 executes step S202 for the first time, it selects the vehicle 100 that is closest to the boarding location, and when the controller 20 executes step S202 for the second time or later, it selects the vehicle 100 in order of proximity to the boarding location.

[0096] Next, the controller 20 determines whether the selected vehicle 100 is in a state where fellow passengers are restricted (step S203). That is, the controller 20 determines whether the selected vehicle 100 is in a state where a user U who desires to restrict fellow passengers is riding in the vehicle or is scheduled to ride in the vehicle.

[0097] If the controller 20 determines that the vehicle 100 is in a passenger restricted state (step S203, Yes), it determines whether the attribute information of the user U riding in the vehicle 100 matches the attribute information of the user U who accepted the boarding reservation information (step S204).

[0098] If it is determined that the attribute information matches (step S204, Yes), the controller 20 determines whether there are vacant seats when the selected vehicle 100 arrives at the boarding location in the boarding reservation information (step S205). If it is determined that there are vacant seats in the vehicle 100 (step S205, Yes), the controller 20 extracts the selected vehicle 100 as a dispatchable vehicle (step S206).

[0099] On the other hand, if it is determined that the vehicle 100 is not in a passenger restricted state (step S203, No), the controller 20 determines whether the vehicle 100 can arrive at the boarding location in the boarding reservation information by the desired boarding time (step S207).If it is determined that the vehicle 100 can arrive at the boarding location by the desired boarding time (step S207, Yes), the controller 20 proceeds to step S206 and extracts the selected vehicle 100 as a dispatchable vehicle.

[0100] If the controller 20 determines that the vehicle 100 cannot arrive at the boarding location by the desired boarding time (step S207, No), the controller 20 returns to step S202 and selects the vehicle 100 again. If the controller 20 determines that the attribute information does not match (step S204, No) or that there are no vacant seats in the vehicle 100 (step S205, No), the controller 20 returns to step S202 and selects the vehicle 100 again.

[0101] As described above, the vehicle dispatching device 10 according to the embodiment includes a controller 20 that receives, from the user terminals 50 of the multiple users U, ride reservation information for a vehicle 100 that can accommodate multiple users U and determines the dispatch of the vehicle 100 based on the ride reservation information. When the controller 20 receives, from the first user terminal 50a, ride reservation information including attribute information of the first user U1 and restriction information indicating a desire to restrict the number of passengers based on the attribute information, the controller 20 determines the dispatch of the vehicle 100 to the first user U1. After determining the dispatch of the vehicle 100 for the first user U1, when the controller 20 receives ride reservation information from the second user terminal 50b, the controller 20 compares the attribute information of the first user U1 with the attribute information of the second user U2. When the attribute information of the first user U1 matches the attribute information of the second user U2, the controller 20 allows the second user U2 to board the vehicle.

[0102] In this way, the vehicle dispatching device 10 allows the second user U2 to board the vehicle when the attribute information of the first user U1 matches the attribute information of the second user U2. This allows users U with the same attributes to share the vehicle 100, ensuring the comfort of the users in the vehicle 100. Furthermore, since the second user U2 also boards the vehicle 100 in addition to the first user U1, the transportation efficiency of the vehicle 100 can be improved compared to when the first user U1 occupies the vehicle 100.

[0103] The attribute information also includes at least one of the gender, family structure, and age group of the user U. This allows the vehicle 100 to be shared with other users U of, for example, the same gender, the same family structure, and / or the same age group, thereby ensuring the comfort of the users in the vehicle 100.

[0104] Further advantages and modifications will readily occur to those skilled in the art. Therefore, the invention in its broader aspects is not limited to the specific details and representative embodiments shown and described above. Accordingly, various modifications may be made without departing from the spirit or scope of the general inventive concept as defined by the appended claims and their equivalents. [Explanation of symbols]

[0105] 10. Vehicle dispatching device 20 Controller 50 User Terminals 50a First user terminal 50b Second user terminal 100 vehicles

Claims

1. A vehicle dispatching device including a controller that receives, from terminals of a plurality of users, ride reservation information for vehicles that the plurality of users can ride in, and determines the dispatch of the vehicles in accordance with the ride reservation information, The controller When receiving ride reservation information from a terminal of a first user, the ride reservation information including attribute information of the first user and restriction information indicating a desire to restrict fellow passengers according to the attribute information, a decision is made to dispatch the vehicle to the first user; After deciding to dispatch the vehicle to the first user, when ride reservation information is received from a terminal of a second user, comparing attribute information of the first user with attribute information of the second user; If the attribute information of the first user and the attribute information of the second user match, permit the second user to get into the vehicle. Dispatch device.

2. The controller setting a location related to the attribute information as a boarding and disembarking location for the vehicle; The vehicle dispatching device according to claim 1 .

3. The attribute information includes information about an organization to which the user belongs, The controller setting a location associated with the organization as a boarding and disembarking location for the vehicle; The vehicle dispatching device according to claim 2.

4. The attribute information includes at least one of the user's gender, family structure, and age group. The vehicle dispatching device according to claim 1 .

5. The controller When receiving ride reservation information including the attribute information of the first user and the restriction information from the terminal of the first user, providing vacant seat information indicating the vacant seat status of the vehicle corresponding to the ride reservation information to the terminal of the first user. The vehicle dispatching device according to claim 1 .

6. Accepting ride reservation information for vehicles available for ride by the plurality of users from the terminals of the respective users, and determining dispatch of the vehicles in accordance with the ride reservation information; When receiving ride reservation information from a terminal of a first user, the ride reservation information including attribute information of the first user and restriction information indicating a desire to restrict fellow passengers according to the attribute information, determining to dispatch the vehicle to the first user; After deciding to dispatch the vehicle to the first user, when boarding reservation information is received from a terminal of a second user, comparing attribute information of the first user with attribute information of the second user; permitting the second user to board the vehicle when the attribute information of the first user matches the attribute information of the second user; A dispatch program that causes a computer to execute the above.

7. A terminal program executed by a computer of a terminal capable of communicating with the vehicle dispatching device according to any one of claims 1 to 5, Accepting input of a ride reservation including user attribute information and restriction information indicating a desire to restrict fellow passengers according to the attribute information, and transmitting ride reservation information indicating the accepted ride reservation to the vehicle dispatching device. A terminal program that causes the computer to execute the above.

Images