Vehicle dispatch support device, vehicle dispatch support method, and vehicle dispatch support system

Abstract

To provide a vehicle allocation support device, a vehicle allocation support method, and a vehicle allocation support system that, even when the number of people getting on a vehicle and the amount of luggage cannot be determined to be reliable at the time of reservation, reduce the possibility that a plurality of users become unable to use a shared vehicle.SOLUTION: A server device allocates a shared vehicle in which an available space is unused to a first user who has transmitted vehicle allocation request data including a desired space information that cannot be determined to be reliable (S3), when the first user uses the shared vehicle, detects the size of the unused space of the available space (S7), and when determining that the size of a space included in reliable space information is equal to or less than the detected size of the unused space, allocates the shared vehicle being used by the first user to a second user who has transmitted vehicle allocation request data including the reliable space information (S13).SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a vehicle dispatch support device, a vehicle dispatch support method, and a vehicle dispatch support system. [Background technology]

[0002] Patent document 1 describes a technology for allocating a vehicle to multiple users as a shared vehicle for joint use by multiple users that can meet the conditions of the number of passengers or amount of luggage entered by the users when making a reservation. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-220090 Summary of the Invention [Problem to be solved by the invention]

[0004] With the technology described in Patent Document 1, if it is impossible to determine at the time of reservation whether the number of passengers and the amount of luggage are certain, it may be impossible to use a shared vehicle. The present invention aims to reduce the possibility that multiple users will be unable to use a shared vehicle even if it is impossible to determine the number of passengers and amount of luggage at the time of reservation. [Means for solving the problem]

[0005] According to one aspect of the present invention, vehicle allocation request data including desired space information, which is information including the size of the space desired to be used relative to the available space in a shared vehicle, is received from each of multiple users, and it is determined whether the received vehicle allocation request data is vehicle allocation request data including desired space information that can be determined to be reliable. Furthermore, a shared vehicle with unused available space is allocated to a first user among the multiple users who sent the vehicle allocation request data including desired space information that cannot be determined to be reliable, and the size of the unused space in the available space is detected when the first user is using the allocated shared vehicle. Then, it is determined whether the vehicle allocation request data received while the first user is using the allocated shared vehicle is vehicle allocation request data including desired space information that can be determined to be reliable, and if it is determined that the vehicle allocation request data received while the first user is using the allocated shared vehicle is vehicle allocation request data including reliable space information, which is desired space information that can be determined to be reliable, it is determined whether the size of the space included in the reliable space information is equal to or smaller than the size of the detected unused space. Furthermore, if it is determined that the size of the space included in the guaranteed space information is equal to or less than the size of the detected unused space, a shared vehicle used by the first user is dispatched to the second user who sent the dispatch request data including the guaranteed space information. [Effects of the Invention]

[0006] According to the present invention, a shared vehicle with unused available space is allocated to a first user who transmits vehicle allocation request data including desired space information that cannot be determined with certainty. Then, after the size of the available space is determined, the allocated shared vehicle is allocated to a second user, thereby avoiding failure of the vehicle allocation plan and suppressing a decrease in vehicle allocation efficiency. This makes it possible to reduce the possibility that multiple users will be unable to use a shared vehicle, even if it is impossible to determine with certainty at the time of reservation the number of passengers and amount of luggage. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a schematic configuration diagram of an example of a vehicle dispatch support system according to an embodiment; [Figure 2] 2 is an explanatory diagram illustrating an example of a functional configuration of the server device of FIG. 1; [Figure 3] 10 is a flowchart showing an example of an operation when using a vehicle dispatch service. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the description of the drawings, identical or similar parts are designated by identical or similar reference numerals, and redundant explanations will be omitted. Each drawing is a schematic diagram and may differ from the actual product. The embodiments shown below exemplify devices and methods for embodying the technical concept of the present invention, and the technical concept of the present invention is not limited to the devices and methods exemplified in the following embodiments. The technical concept of the present invention can be modified in various ways within the technical scope described in the claims.

[0009] (composition) 1 is a schematic diagram of an example of a vehicle dispatch support system according to an embodiment. The vehicle dispatch support system 1 is a system that provides a vehicle dispatch service that dispatches a vehicle 3 used for a user's transportation. In this specification, the vehicle 3 provided for the vehicle dispatch service by the vehicle dispatch support system 1 is referred to as a "service vehicle." The vehicle dispatch support system 1 includes at least a server device 2 and a service vehicle 3. The first user terminal 4 is a terminal device used by one of the users (hereinafter referred to as the "first user") who uses the vehicle dispatch service provided by the vehicle dispatch support system 1. The second user terminal 5 is a terminal device used by a user (hereinafter referred to as the "second user") who is different from the first user. The first user terminal 4 and the second user terminal 5 may be, for example, a portable information terminal that can be carried by the user or a small computer that is easy to carry.

[0010] When reserving a vehicle dispatch service, the first user accesses the server device 2 using the first user terminal 4. Before reserving a vehicle dispatch service, the first user may install dedicated application software for using the vehicle dispatch support system 1 in the first user terminal 4 in advance and make the reservation using the dedicated application software. In the following description, "application software" will be simply referred to as "software." Alternatively, the first user may use the browser function of the first user terminal 4 to reserve a vehicle dispatch service on a website that accepts reservations for vehicle dispatch services over the Internet. When reserving a vehicle dispatch service, the second user accesses the server device 2 using the second user terminal 5. Before reserving a vehicle dispatch service, the second user may install dedicated software for using the vehicle dispatch support system 1 in the second user terminal 5 in advance and make the reservation using the dedicated software. Alternatively, the second user may use the browser function of the second user terminal 5 to reserve a vehicle dispatch service on a website that accepts reservations for vehicle dispatch services over the Internet.

[0011] <First user terminal> The first user terminal 4 accepts an input operation by the first user regarding a reservation for a vehicle dispatch service. The first user terminal 4 generates first vehicle dispatch request data for applying for a reservation for a vehicle dispatch service based on the information input by the first user, and transmits the first vehicle dispatch request data to the server device 2. The first vehicle dispatch request data includes information on the boarding location (desired boarding location) where the first user wishes to board the service vehicle 3 and the disembarking location (desired disembarking location) where the first user wishes to disembark from the service vehicle 3. In addition, the first vehicle dispatch request data includes information on the date and time (desired boarding date and time) where the first user wishes to board the service vehicle 3 and the date and time (desired disembarking date and time) where the first user wishes to disembark from the service vehicle 3. The first vehicle dispatch request data may also include, for example, information about the first user (for example, the first user's attributes and identification information). The first user's attributes include, for example, the first user's gender, age, health condition, family composition, etc.

[0012] Furthermore, the first vehicle dispatch request data includes desired space information. The desired space information is information including the size of the space that the first user desires to use relative to the available space of the shared vehicle (service vehicle 3). In addition, the desired space information includes information on the number of people (including the first user himself) who will be traveling using the available space of the service vehicle 3, and information on the amount of luggage (size of luggage, number of luggage) that will be traveling using the available space of the service vehicle 3. The desired space information is input using the controls provided on the HMI, for example, after inputting the desired boarding location, desired disembarking location, desired boarding date and time, and desired disembarking date and time. The first vehicle dispatch request data also includes whether or not the user wishes to share a ride (sharing the transportation of passengers and luggage with other users).

[0013] The first user terminal 4 includes a positioning device 40, a communication device 41, a human-machine interface (HMI) 42, and a controller 43. The positioning device 40 measures the current position of the first user terminal 4 (i.e., the current position of the first user). The positioning device 40 may include, for example, a Global Navigation System (GNSS) receiver. The GNSS receiver may be, for example, a Global Positioning System (GPS) receiver. The positioning device 40 may also include an inertial navigation system. The positioning device 50 outputs current position information of the first user terminal 4 to the controller 34. The communication device 41 provides a communication function between the first user terminal 4 and an external device. The communication method used by the communication device 41 may be, for example, wireless communication via a public mobile communication network, satellite communication, etc. The first user terminal 4 transmits and receives data to and from the server device 2 via the communication device 41. The HMI 42 is an interface device that exchanges information between the first user terminal 4 and the first user. The HMI 42 includes a display device that can be seen by the first user, and a speaker or buzzer that outputs alarm sounds, notification sounds, and audio information. The HMI 42 also includes controls and a voice input device that accept operation inputs from the first user to the first user terminal 4. The controls may be buttons, switches, levers, dials, keyboards, touch panels, etc.

[0014] The controller 43 is an electronic control unit (ECU) that controls the operation of the first user terminal 4. The controller 43 includes a processor 44 and peripheral components such as a storage device 45. The processor 44 may be, for example, a central processing unit (CPU) or a micro-processing unit (MPU). The storage device 45 may include non-transitory tangible storage media such as registers, cache memory, and memories such as read-only memory (ROM) and random access memory (RAM) used as main storage devices. The functions of the first user terminal 4 described below are realized by, for example, the processor 44 executing a computer program stored in the storage device 45.

[0015] <Second user terminal> The second user terminal 5 accepts input operations by the second user regarding reservations for the vehicle dispatch service. Based on the information input by the second user, the second user terminal 5 generates second vehicle dispatch request data for applying for a reservation for the vehicle dispatch service and transmits the second vehicle dispatch request data to the server device 2. The second vehicle dispatch request data includes information on the boarding location (desired boarding location) where the second user wishes to board the service vehicle 3 and the disembarking location (desired disembarking location) where the second user wishes to disembark from the service vehicle 3. In addition, the second vehicle dispatch request data includes information on the date and time (desired boarding date and time) where the second user wishes to board the service vehicle 3 and the date and time (desired disembarking date and time) where the second user wishes to disembark from the service vehicle 3. The second vehicle dispatch request data may also include, for example, information about the second user (for example, attributes and identification information of the second user). The attributes of the second user include, for example, the second user's gender, age, health condition, family composition, etc.

[0016] Furthermore, the second vehicle dispatch request data includes desired space information. The desired space information is information including the size of the space that the second user desires to use, relative to the available space of the shared vehicle (service vehicle 3). In addition, the desired space information includes information on the number of people (including the second user himself) who will be traveling using the available space of the service vehicle 3, and information on the amount of luggage (size of luggage, number of luggage) that will be traveling using the available space of the service vehicle 3. The second dispatch request data also includes whether or not the user wishes to share a ride.

[0017] The second user terminal 5 includes a positioning device 50 , a communication device 51 , an HMI 52 , and a controller 53 . The positioning device 50 measures the current position of the second user terminal 5 (i.e., the current position of the second user). The positioning device 50 may include, for example, a Global Navigation System (GNSS) receiver. The GNSS receiver may be, for example, a Global Positioning System (GPS) receiver. The positioning device 50 may also include an inertial navigation system. The positioning device 50 outputs current position information of the second user terminal 5 to the controller 34.

[0018] The communication device 51 provides a communication function between the second user terminal 5 and an external device. The communication method used by the communication device 51 may be, for example, wireless communication via a public mobile communication network, satellite communication, etc. The second user terminal 5 transmits and receives data to and from the server device 2 via the communication device 51. The HMI 52 is an interface device that exchanges information between the second user terminal 5 and the second user. The HMI 52 includes a display device that can be seen by the second user, and a speaker or buzzer that outputs alarm sounds, notification sounds, and audio information. The HMI 52 also includes controls and a voice input device that accept operational inputs to the second user terminal 5 by the second user. The controls may be buttons, switches, levers, dials, keyboards, touch panels, etc.

[0019] The controller 53 is an electronic control unit that controls the operation of the second user terminal 5. The controller 53 includes a processor 54 and peripheral components such as a memory device 55. The processor 54 may be, for example, a CPU or an MPU. The memory device 55 may include non-transitory tangible storage media such as registers, cache memory, and memories such as ROM and RAM used as main memory devices. The functions of the second user terminal 5 described below are realized by, for example, the processor 54 executing a computer program stored in the storage device 55.

[0020] <Server device> The server device 2 receives the first vehicle allocation request data from the first user terminal 4 and receives the second vehicle allocation request data from the second user terminal 5. Then, the server device 2 performs processing according to the first vehicle allocation request data and the second vehicle allocation request data. The server device 2 includes a processor 20, a storage device 21, a communication device 22, a registrant database (registrant DB) 23, a map database (map DB) 24, and a reservation database (reservation DB) 25. The processor 20 may be, for example, a CPU or an MPU. The storage device 21 may include a non-transitory tangible storage medium such as a register, a cache memory, or a memory such as a ROM or RAM used as a main storage device. The functions of the server device 2 described below are realized, for example, by the processor 20 executing a computer program stored in the storage device 21.

[0021] The communication device 22 provides a communication function between the server device 2 and an external device. The communication method used by the communication device 22 may be, for example, wired communication or wireless communication via a public mobile communication network, satellite communication, road-to-vehicle communication with the service vehicle 3, or the like. The server device 2 transmits and receives data to and from the service vehicle 3, the first user terminal 4, and the second user terminal 5 via the communication device 22.

[0022] The registrant DB23 is a database for registering users of the vehicle dispatch support system 1. In the following description, a person registered in the registrant DB23 will be referred to as a "registrant." For example, a user of a vehicle dispatch service is registered in the registrant DB23 as a person who uses the vehicle dispatch support system 1.

[0023] The map DB 24 stores map information of an area where the vehicle dispatch support system 1 provides a vehicle dispatch service. The map information may be, for example, map data for navigation (hereinafter simply referred to as a "navigation map"). The server device 2 calculates a driving route from the desired boarding location included in the vehicle dispatch request data to the desired disembarking location based on the map information stored in the map DB 24 in response to the vehicle dispatch request data received from the first user terminal 4 and the second user terminal 5. The server device 2 also predicts the disembarking date and time when the service vehicle 3 will depart at the desired boarding date and time included in the reservation information, travel along the driving route, and arrive at the desired disembarking location. The server device 2 stores the desired boarding location, desired boarding date and time, and desired disembarking location included in the dispatch request data, as well as the travel route and disembarking date and time calculated by the server device 2, in the reservation DB 25 as a travel plan for the service vehicle 3. In addition, the server device 2 transmits to the service vehicle 3 a travel plan including the desired boarding location, desired boarding date and time, desired disembarking location, disembarking date and time, and travel route.

[0024] <Service vehicle> The service vehicle 3 is a vehicle that operates in response to user requests (a so-called demand-based transportation vehicle), and may be, for example, a shared taxi or a robot taxi. The service vehicle 3 is an autonomously driven vehicle that automatically drives the service vehicle 3 by the controller 34 according to a driving plan transmitted from the server device 2 without the involvement of a driver (human). In the embodiment, the configuration of the service vehicle 3 will be described in the case where the available space includes a boarding space for the users themselves (the first user themselves, the second user themselves) and a loading space for loading luggage. When the service vehicle 3 receives the travel plan from the server device 2, it drives to the boarding location so as to arrive by the desired boarding date and time included in the travel plan. Also, when the user gets on the service vehicle 3 at the boarding location, it drives to the disembarking location along the travel route included in the travel plan. The service vehicle 3 includes a sensor 30, a positioning device 31, a map database (map DB) 32, a communication device 33, a controller , and an actuator . The sensors 30 include an object sensor that detects objects around the service vehicle 3, and a vehicle sensor that detects various information obtained from the service vehicle 3 (vehicle state). The object sensor detects the surrounding environment of the service vehicle 3, such as the relative position of the service vehicle 3 and an object present around the service vehicle 3, the distance between the service vehicle 3 and the object, and the direction in which the object is present. The object sensor may include, for example, a camera that captures the surrounding environment of the service vehicle 3. Furthermore, for example, the object sensor may include a distance measuring device such as a laser range finder (LRF), radar, or a laser radar of LiDAR (Light Detection and Ranging). The object sensor outputs surrounding environment information, which is information on the detected surrounding environment of the service vehicle 3, to the controller 34. The vehicle sensors may include, for example, a vehicle speed sensor that detects the traveling speed (vehicle speed) of the service vehicle 3, a wheel speed sensor that detects the rotational speed of each tire equipped on the service vehicle 3, a three-axis acceleration sensor (G sensor) that detects the acceleration (including deceleration) in three axial directions of the service vehicle 3, a steering angle sensor that detects the steering angle (including the turning angle), a gyro sensor that detects the angular velocity generated in the service vehicle 3, and a yaw rate sensor that detects the yaw rate. Furthermore, the vehicle sensors may include a seat belt sensor that detects whether a seat belt is fastened or unfastened, and a door sensor that detects whether a door is opened or closed. The vehicle sensors output vehicle state information to the controller 34.

[0025] The positioning device 31 measures the current position and attitude of the service vehicle 3. The positioning device 31 may include, for example, a Global Navigation System (GNSS) receiver. The GNSS receiver may be, for example, a Global Positioning System (GPS) receiver. The positioning device 31 may also include an inertial navigation system. The positioning device 31 outputs current position information of the measured current position to the controller 34. The map DB 32 stores map information. The map information may include map data for navigation (hereinafter simply referred to as a "navigation map") and high-precision map data suitable as a map for automated driving (hereinafter simply referred to as a "high-precision map"). The communication device 33 provides a communication function between the service vehicle 3 and an external device. The communication method used by the communication device 33 may be, for example, wireless communication via a public mobile communication network, satellite communication, road-to-vehicle communication, or the like. The service vehicle 3 transmits and receives data to and from the server device 2 via the communication device 33 .

[0026] The controller 34 is an electronic control unit that controls the service vehicle 3. For example, the controller 34 controls the autonomous driving of the service vehicle 3. The controller 34 includes a processor 36 and peripheral components such as a storage device 37. The processor 36 may be, for example, a CPU or an MPU. The storage device 37 may include non-transitory tangible storage media such as registers, cache memory, and memories such as ROM and RAM used as main storage devices. The functions of the controller 34 are realized, for example, by the processor 36 executing a computer program stored in the storage device 37. The controller 34 executes autonomous driving control to drive the service vehicle 3 according to the driving plan based on the surrounding environment information and vehicle state information from the sensor 30, the positioning results of the positioning device 31, and the map information in the map DB 32. For example, the controller 34 calculates a target driving trajectory for the service vehicle 3 based on the current position and attitude of the service vehicle 3, the driving route included in the driving plan, map information, and the surrounding environment of the service vehicle 3. In addition, the controller 34 generates, for example, a route space map that represents the route around the service vehicle 3 and the presence or absence of objects, and a risk map that quantifies the degree of risk during driving, and generates a target driving trajectory based on the motion characteristics of the service vehicle 3, the vehicle state information, the route space map, and the risk map. Then, the controller 34 drives the actuator 35 so that the service vehicle 3 drives along the generated target driving trajectory. The actuator 35 operates the steering device, drive device and braking device of the service vehicle 3 in response to control signals from the controller 34 to generate vehicle behavior of the service vehicle 3, thereby automatically driving the service vehicle 3. The actuator 35 includes a steering actuator, an accelerator opening actuator and a brake control actuator.

[0027] <Server device functional configuration> The following describes the functional configuration of the server device 2. Figure 2 is an explanatory diagram showing an example of a block diagram showing the functional configuration of the server device 2. The server device 2 includes a request data acquisition unit 60, a desired space information determination unit 61, a vehicle allocation plan determination unit 62, a driving plan setting unit 63, an unused space detection unit 64, an unused space determination unit 65, and a vehicle allocation plan correction unit 66. In addition, the server device 2 includes a driving plan correction unit 67 and a ride-sharing vehicle allocation unit 68.

[0028] When the request data acquisition unit 60 receives the first vehicle dispatch request data from the first user terminal 4, it registers the information contained in the first vehicle dispatch request data (desired boarding location, desired disembarking location, desired boarding date and time, desired space information) in the reservation DB 25. In addition, when the request data acquisition unit 60 receives second dispatch request data from the second user terminal 5, it registers the information contained in the second dispatch request data (desired boarding location, desired disembarking location, desired boarding date and time, and desired space information) in the reservation DB 25.

[0029] The desired space information determination unit 61 determines whether or not the vehicle allocation request data (first vehicle allocation request data, second vehicle allocation request data) is vehicle allocation request data that includes desired space information that can be determined to be reliable. Specifically, the request data acquisition unit 60 uses the following judgment conditions I to III to determine whether the dispatch request data acquired includes desired space information that can be determined to be reliable. Judgment condition I: If the dispatch request data does not contain information indicating the user and luggage who will be traveling using the available space, it is judged that the dispatch request data contains desired space information that cannot be determined to be reliable. Judgment condition II: If the dispatch request data contains information indicating users and luggage who will be using the available space, and there is a possibility that the number of users and amount of luggage who will be using the available space may fluctuate, the dispatch request data is judged to contain desired space information that cannot be determined to be reliable. Judgment condition III: If the dispatch request data contains information indicating users and luggage who will be traveling using the available space, and there is no possibility that the number of users traveling using the available space or the amount of luggage will change, the dispatch request data is judged to contain reliable space information. The guaranteed space information is desired space information that can be determined to be guaranteed. In addition, the following explanation will be written under the assumption that the first dispatch request data is dispatch request data that includes desired space information that cannot be determined to be certain, and the second dispatch request data is dispatch request data that includes certain space information.

[0030] When using the judgment conditions II and III, for example, if the probability that the number of users moving using the available space and the amount of luggage will change exceeds a preset threshold probability, it is judged that there is a possibility that the number of users moving using the available space and the amount of luggage will change. Note that the probability that the number of users moving using the available space and the amount of luggage will change is predicted, for example, from a database based on past usage history.

[0031] Below, with reference to Table 1, we will explain an example of a method for calculating the probability that the number of users moving using available space will increase, as a method for predicting the probability that the number of users moving using available space will change. [Table 1]

[0032] For example, as shown in Table 1 as "Case 1," if the desired boarding location is a cultural center (for extracurricular activities), the desired disembarking location is a restaurant, the desired boarding date and time is a holiday afternoon, the number of users traveling using the available space is two, and the user has low reservation accuracy based on past usage history, it is estimated that inviting unexpected friends will increase the number of users traveling using the available space, and therefore it is calculated that there is a high probability that the number of users traveling using the available space will increase.

[0033] Below, with reference to Table 2, we will explain an example of a method for calculating the probability that the amount of luggage being moved using available space will increase, as a method for predicting the probability that the amount of luggage being moved using available space will change. [Table 2]

[0034] For example, as shown in "Case 1" in Table 2, in the case of a user whose desired boarding location is a shopping center, whose desired disembarking location is home, whose desired boarding date and time is a daytime holiday, whose luggage to be moved using the available space is a small single piece, and whose reservation accuracy based on past usage history is low, it is estimated that unplanned shopping will increase the amount of luggage to be moved using the available space, and therefore it is calculated that there is a high probability that the amount of luggage to be moved using the available space will increase.

[0035] In addition, the probability that the number of users moving using the available space will increase, or the probability that the amount of luggage moving using the available space will increase, may be calculated using a formula that uses, for example, the type of influencing factor, weights estimated from registered data, influencing factors, error terms, etc.

[0036] The vehicle allocation plan determination unit 62 determines a vehicle allocation plan for allocating the service vehicles 3 by determining the service vehicles 3 to be provided to the user based on the desired boarding location included in the vehicle allocation request data and the current location of the service vehicles 3. For example, the vehicle allocation plan determination unit 62 determines the vehicle allocation plan by selecting multiple service vehicles 3 that are not currently being used by other users and that can arrive at the desired boarding location by the desired boarding date and time. Furthermore, the vehicle allocation plan determination unit 62 stores identification information of the selected service vehicles 3 in the reservation DB 25. Note that if it is not possible to select multiple service vehicles 3, the vehicle allocation plan may be determined by selecting one service vehicle 3, such as the service vehicle 3 located closest to the desired boarding location. In addition, the vehicle allocation plan determination unit 62 determines a vehicle allocation plan according to the vehicle allocation request data that the desired space information determination unit 61 has determined to include desired space information that can be determined to be reliable. Specifically, a shared vehicle (service vehicle 3) with unused available space is dispatched to a user (first user) among multiple users who has sent vehicle dispatch request data including desired space information that cannot be determined to be reliable. A shared vehicle (service vehicle 3) with unused available space is a vehicle in which there are no passengers in the boarding space and no luggage in the loading space.

[0037] The trip plan setting unit 63 sets a trip route from the desired boarding location to the desired disembarking location included in the first vehicle dispatch request data based on map information stored in the map DB 24. The trip plan setting unit 63 also predicts a disembarking date and time when the service vehicle 3 will depart at the desired boarding date and time included in the first vehicle dispatch request data, travel along the travel route, and arrive at the desired disembarking location. The trip plan setting unit 63 stores the calculated travel route and disembarking date and time in the reservation DB 25. As a result, the desired boarding location, desired boarding date and time, and desired disembarking location included in the first vehicle dispatch request data, and the disembarking date and time and travel route set by the trip plan setting unit 63 are stored in the reservation DB 25 as a trip plan for the vehicle dispatch service to be provided to the first user. Furthermore, the driving plan setting unit 63 transmits driving plan information regarding the driving plan to the service vehicle 3 selected by the vehicle allocation plan determination unit 62 (i.e., the service vehicle 3 provided for the first user) and the first user terminal 4.

[0038] The unused space detection unit 64 detects the size of unused space among the available spaces when the first user is using the allocated shared vehicle (service vehicle 3). The size of the unused space is detected using, for example, a camera capable of capturing an image of the interior of the service vehicle 3, a pressure sensor disposed on the seat of the service vehicle 3, or the like.

[0039] When the desired space information determination unit 61 determines that the dispatch request data received while the first user is using the dispatched shared vehicle (service vehicle 3) is dispatch request data including guaranteed space information, the unused space determination unit 65 determines whether the size of the space included in the guaranteed space information is less than or equal to the size of the unused space detected by the unused space detection unit 64. For example, if the size of the unused space detected by the unused space detection unit 64 is a boarding space that can accommodate three users, and the confirmed space information indicates that the number of people traveling using the available space is two, it is determined that the size of the space included in the confirmed space information is less than or equal to the size of the unused space detected by the unused space detection unit 64.

[0040] When the unused space determination unit 65 determines that the size of the space included in the guaranteed space information is equal to or less than the size of the unused space detected by the unused space detection unit 64, the vehicle allocation plan correction unit 66 corrects the vehicle allocation plan determined by the vehicle allocation plan determination unit 62. Specifically, the dispatch plan determined by the dispatch plan determination unit 62 is corrected so as to dispatch a service vehicle 3 to the second user based on the desired boarding location included in the second dispatch request data and the current location of the service vehicle 3 used by the first user.

[0041] The driving plan correction unit 67 corrects the driving plan set by the driving plan setting unit 63 based on the dispatch plan corrected by the dispatch plan correction unit 66, the current position of the service vehicle 3 used by the first user, and the driving plan set by the driving plan setting unit 63. Specifically, a travel route is set for the service vehicle 3 used by the first user to travel to the desired boarding location included in the second dispatch request data. Furthermore, a travel route is set to travel to the desired drop-off location closest to the desired boarding location included in the second dispatch request data, out of the desired drop-off locations included in the first dispatch request data and the second dispatch request data, and then to arrive at the remaining desired drop-off location.

[0042] The ride-pooling vehicle dispatch unit 68 transmits a driving plan for arriving at the desired boarding location included in the second vehicle dispatch request data by the desired boarding date and time included in the second vehicle dispatch request data, based on the map information stored in the map DB 24, to the service vehicle 3 whose dispatch plan has been corrected by the dispatch plan correction unit 66. In addition, the ride-pooling vehicle dispatch unit 68 transmits the driving route set by the driving plan correction unit 67 to the service vehicle 3 whose dispatch plan has been corrected by the dispatch plan correction unit 66.

[0043] (operation) FIG. 3 is a flowchart showing an example of an operation when using a vehicle dispatch service. In step S1, the request data acquisition unit 60 acquires first vehicle allocation request data received from the first user terminal 4 and second vehicle allocation request data received from the second user terminal 4. In step S2, the vehicle allocation plan determination unit 62 determines whether or not there is a service vehicle 3 that is capable of accepting the first vehicle allocation request data (first request) acquired in step S1 and has unused available space. If there is a service vehicle 3 that is capable of accepting the first request and has unused available space (step S2: Y), the process proceeds to step S3. If there is no service vehicle 3 that is capable of accepting the first request and has unused available space (step S2: N), the process proceeds to step S4. In step S3, the vehicle allocation plan determination unit 62 sets the service vehicle 3 with unused available space as the vehicle to be allocated to the first user, thereby matching the first user with the service vehicle 3 with unused available space. In step S4, the vehicle allocation plan determination unit 62 sends a message to the first user terminal 4 indicating that it is impossible to allocate the service vehicle 3. In step S5, the driving plan setting unit 63 sets driving plan information and transmits the set driving plan information to the service vehicle 3 set in step S3. The service vehicle 3 that receives the driving plan information moves to the desired boarding location included in the first vehicle dispatch request data. Then, the first user boards the service vehicle 3 that has moved to the desired boarding location included in the first vehicle dispatch request data. In step S6, the unused space detection unit 64 detects the size of unused space among the available space for the service vehicle 3 in which the first user is riding. As a result, in step S6, the size of unused space among the available space for the service vehicle 3 in which the first user is riding is determined. In step S7, the unused space determination unit 65 determines whether or not there is available space by determining whether or not the size of the space included in the guaranteed space information is equal to or less than the size of the unused space determined in step S6. If there is available space (step S7: Y), the process proceeds to step S8. If there is no available space (step S7: N), the process proceeds to step S9. In step S8, the vehicle allocation plan correction unit 66 sets the service vehicle 3 determined in step S7 to have the space size included in the guaranteed space information equal to or less than the unused space size confirmed in step S6 as a candidate service vehicle 3 to be allocated to the second user. In step S9, the vehicle allocation plan determination unit 62 sets the service vehicle 3 with unused usable space as a vehicle to be allocated to the second user, thereby matching the second user with the service vehicle 3 with unused usable space. In step S10, the vehicle allocation plan correction unit 66 acquires the operation plan of the service vehicle 3 (shareable vehicle) set in step S8 by acquiring the operation plan of the service vehicle 3 set in step S8 from the operation plan stored in the reservation DB 25. Furthermore, the vehicle allocation plan correction unit 66 corrects the vehicle allocation plan so as to allocate the service vehicle 3 to the second user based on the operation plan of the service vehicle 3 set in step S8 and the current position. In step S11, the driving plan correction unit 67 sets candidate driving routes for the shareable vehicle based on the vehicle allocation plan corrected in step S10, the current position of the shareable vehicle (shareable vehicle), and the driving plan set by the driving plan setting unit 63. In step S12, the ride-pooling vehicle dispatch unit 68 determines whether or not a service vehicle 3 capable of accepting the second dispatch request data (second request) acquired in step S1 is present among the shareable vehicles for which the candidate driving route was set in step S11. If a service vehicle 3 capable of accepting the second request is present among the shareable vehicles (step S12: Y), the process proceeds to step S13. If a service vehicle 3 capable of accepting the second request is not present among the shareable vehicles (step S12: N), the process proceeds to step S14. In step S13, the ride-pooling vehicle dispatch unit 68 matches the service vehicle 3 capable of accepting the second request with the second user as a vehicle shared by the first user and the second user (shared vehicle). In step S14, the ride-sharing vehicle dispatch unit 68 determines whether there is a service vehicle 3 that is capable of accepting the second request and has unused available space. If there is a service vehicle 3 that is capable of accepting the second request and has unused available space (step S14: Y), the process proceeds to step S9. If there is not a service vehicle 3 that is capable of accepting the second request and has unused available space (step S14: N), the process proceeds to step S15. In step S15, the vehicle dispatch plan correction unit 66 sends a message to the second user terminal 4 that it is impossible to dispatch a service vehicle 3.

[0044] (Effects of the embodiment) (1) A vehicle dispatch support device and a vehicle dispatch support method provide a vehicle dispatch service in which a shared vehicle is dispatched to be jointly used by multiple users for the transportation of at least one of the users themselves and their luggage. The vehicle dispatch support system 1 receives vehicle dispatch request data including desired space information from each of the multiple users. Furthermore, it determines whether the received vehicle dispatch request data is vehicle dispatch request data including desired space information that can be determined to be reliable. Furthermore, it dispatches a shared vehicle with unused available space to a first user among the multiple users who transmitted vehicle dispatch request data including desired space information that cannot be determined to be reliable. Furthermore, when the first user uses the dispatched shared vehicle, it detects the size of unused space among the available space. Then, it determines whether the vehicle dispatch request data received when the first user is using the dispatched shared vehicle is vehicle dispatch request data including desired space information that can be determined to be reliable. Furthermore, when it is determined that the vehicle dispatch request data received when the first user is using the dispatched shared vehicle is vehicle dispatch request data including reliable space information, which is desired space information that can be determined to be reliable, it determines whether the size of the space included in the reliable space information is equal to or smaller than the size of the detected unused space. Then, when it is determined that the size of the space included in the guaranteed space information is equal to or less than the size of the detected unused space, the shared vehicle used by the first user is dispatched to the second user who sent the dispatch request data including the guaranteed space information. As a result, a shared vehicle with unused available space is allocated to a first user who transmits vehicle allocation request data including desired space information that cannot be determined to be reliable. Then, after the size of the available space is determined, the shared vehicle allocated to the first user is allocated to the second user, thereby avoiding failure of the vehicle allocation plan and suppressing a decrease in vehicle allocation efficiency. Therefore, even if it is impossible to determine the number of passengers or amount of luggage at the time of reservation, it is possible to reduce the possibility that multiple users will not be able to use the shared vehicle.

[0045] (2) If the dispatch request data does not contain information indicating the user and luggage moving using the available space, it is determined that the dispatch request data contains desired space information that cannot be determined to be reliable. This allows a shared vehicle with unused available space to be dispatched to a user who has not entered user information or luggage information as dispatch request data, thereby avoiding failure of the dispatch plan and suppressing a decrease in dispatch efficiency.

[0046] (3) If the dispatch request data contains information indicating users and luggage who will be using the available space, and there is a possibility that the number of users and the amount of luggage who will be using the available space may fluctuate, the dispatch request data is determined to contain desired space information that cannot be determined to be reliable. This allows for user information and luggage information to be input as dispatch request data, but by dispatching a shared vehicle with unused available space to users whose number of users or amount of luggage may fluctuate, failure of the dispatch plan can be avoided and a decrease in dispatch efficiency can be suppressed.

[0047] (4) If the dispatch request data contains information indicating users and luggage traveling using the available space, and there is no possibility that the number of users traveling using the available space or the amount of luggage will change, the dispatch request data is determined to contain reliable space information. This allows user information and luggage information to be entered as vehicle dispatch request data, and by dispatching a shared vehicle with a fixed amount of available space to a second user for a user whose number of users or amount of luggage is not likely to fluctuate, failure of the vehicle dispatch plan can be avoided and a decrease in vehicle dispatch efficiency can be suppressed.

[0048] (5) If the probability that the number of users and the amount of luggage moving using the available space will fluctuate, as predicted from a database based on past usage history, exceeds a predetermined threshold probability, it is determined that there is a possibility that the number of users and the amount of luggage moving using the available space will fluctuate. This allows shared vehicles with unused available space to be dispatched to users whose number of users or amount of luggage is expected to fluctuate, thereby avoiding failure of the vehicle dispatch plan and suppressing a decrease in vehicle dispatch efficiency.

[0049] (6) The desired space information includes information on the number of people who will be moving using the available space and information on the amount of luggage that will be moved using the available space. This makes it possible to improve the accuracy of determining whether the size of the space included in the guaranteed space information is equal to or less than the size of the detected unused space.

[0050] (7) The available space includes the passenger space for the user to board the vehicle and the loading space for luggage. This makes it possible to avoid failure of dispatch plans and prevent a decline in dispatch efficiency in dispatch services that use shared vehicles capable of carrying both passengers and cargo.

[0051] (Modification of the embodiment) (1) In the embodiment, the service vehicle 3 is configured such that the available space includes a boarding space for the users (the first user and the second user) to board and a loading space for loading luggage, but the configuration of the service vehicle 3 is not limited to this. In other words, the service vehicle 3 may be configured such that the available space is only one of the boarding space and the loading space. In this case, in a vehicle dispatch service that uses shared vehicles to transport only personnel or only cargo, it is possible to avoid failure of the vehicle dispatch plan and prevent a decrease in vehicle dispatch efficiency. [Explanation of symbols]

[0052] 1...Vehicle dispatch support system, 2...Server device, 3...Service vehicle, 4...First user terminal, 5...Second user terminal, 20, 36, 44, 54...Processor, 21, 37, 45, 55...Storage device, 22, 33, 41, 51...Communication device, 23...Registrant database, 24, 32...Map database, 25...Reservation database, 30...Sensor, 31, 40, 50...Positioning device, 34, 43, 53...Controller, 35...Actuator, 42, 52...Human-machine interface, 60...Request data acquisition unit, 61...Desired space information determination unit, 62...Vehicle dispatch plan determination unit, 63...Drive plan setting unit, 64...Unused space detection unit, 65...Unused space determination unit, 66...Vehicle dispatch plan correction unit, 67...Drive plan correction unit, 68...Ride-share vehicle dispatch unit

Claims

1. A vehicle dispatch support device that provides a vehicle dispatch service for dispatching a shared vehicle that is used jointly by a plurality of users for transportation of at least one of the users themselves and their luggage, receiving, from each of the plurality of users, vehicle dispatch request data including desired space information, which is information including the size of the space the user wishes to use relative to the available space of the shared vehicle; A process of determining whether the received vehicle dispatch request data is vehicle dispatch request data including the desired space information that can be determined to be reliable; A process of allocating a shared vehicle with an unused available space to a first user who has transmitted vehicle allocation request data including the desired space information that cannot be determined to be reliable among the plurality of users; a process of detecting a size of an unused space among the available spaces when the first user is using the allocated shared vehicle; A process of determining whether or not vehicle allocation request data received while the first user is using the allocated shared vehicle is vehicle allocation request data that includes the desired space information that can be determined to be reliable; When it is determined that the vehicle dispatch request data received while the first user is using the dispatched shared vehicle is vehicle dispatch request data that includes reliable space information, which is desired space information that can be determined to be reliable, a process of determining whether the size of the space included in the reliable space information is equal to or smaller than the size of the detected unused space; When it is determined that the size of the space included in the assured space information is equal to or smaller than the detected size of the unused space, a process of dispatching a shared vehicle used by the first user to a second user who transmitted vehicle dispatch request data including the assured space information; A vehicle dispatch assistance device comprising a computer that executes the above.

2. The vehicle dispatch support device of claim 1, wherein if the vehicle dispatch request data does not contain information indicating the user and luggage moving using the available space, it is determined that the vehicle dispatch request data includes desired space information that cannot be determined to be certain.

3. A vehicle dispatch support device as described in claim 1 or claim 2, which determines that the vehicle dispatch request data includes desired space information that cannot be determined to be certain when information indicating users and luggage moving using the available space is present in the vehicle dispatch request data and there is a possibility that the number of users moving using the available space and the amount of luggage may change.

4. A vehicle dispatch support device as described in any one of claims 1 to 3, which determines that the vehicle dispatch request data includes the guaranteed space information when information indicating users and luggage traveling using the available space is present in the vehicle dispatch request data and there is no possibility that the number of users traveling using the available space or the amount of luggage will change.

5. A vehicle dispatch support device as described in claim 3 or claim 4, which determines that there is a possibility that the number of users and amount of luggage moving using the available space will change if the probability that the number of users and amount of luggage moving using the available space will change, predicted from a database based on past usage history, exceeds a predetermined threshold probability.

6. The vehicle dispatch support device according to any one of claims 1 to 5, wherein the desired space information includes information on the number of people moving using the available space and information on the amount of luggage moving using the available space.

7. The vehicle dispatch assistance device according to claim 1 , wherein the available space includes a boarding space for the user to board and a loading space for loading the luggage.

8. The vehicle dispatch assistance device according to claim 1 , wherein the available space is only one of a boarding space for the user to board and a loading space for loading the luggage.

9. A vehicle dispatch support method for providing a vehicle dispatch service in which a shared vehicle is dispatched to be used jointly by a plurality of users for transportation of at least one of the users themselves and their luggage, the method comprising: Transmitting vehicle allocation request data received from each of the plurality of users, the vehicle allocation request data including desired space information, which is information including the size of the space desired to be used relative to the available space of the shared vehicle, to a server device; The server device: determining whether the received vehicle dispatch request data is vehicle dispatch request data including the desired space information that can be determined to be reliable; Distributing a shared vehicle with an unused available space to a first user who has transmitted vehicle allocation request data including the desired space information that cannot be determined to be reliable among the plurality of users; When the first user is using the allocated shared vehicle, a size of an unused space among the available spaces is detected; determining whether or not vehicle allocation request data received while the first user is using the allocated shared vehicle is vehicle allocation request data including the desired space information that can be determined to be reliable; When it is determined that the vehicle dispatch request data received while the first user is using the dispatched shared vehicle is vehicle dispatch request data that includes reliable space information, which is desired space information that can be determined to be reliable, it is determined whether the size of the space included in the reliable space information is equal to or smaller than the size of the detected unused space; A vehicle dispatch support method that, when it is determined that the size of the space included in the guaranteed space information is less than or equal to the size of the detected unused space, dispatches a shared vehicle used by the first user to a second user who sent vehicle dispatch request data including the guaranteed space information.

10. A vehicle dispatch support system that provides a vehicle dispatch service that dispatches a shared vehicle that is used jointly by multiple users for transportation of at least one of the users themselves and their luggage, a server device that receives vehicle dispatch request data including desired space information, which is information including the size of the space that the user wishes to use relative to the available space of the shared vehicle, received from each of the plurality of users; The server device determining whether the received vehicle dispatch request data is vehicle dispatch request data including the desired space information that can be determined to be reliable; Distributing a shared vehicle with an unused available space to a first user who has transmitted vehicle allocation request data including the desired space information that cannot be determined to be reliable among the plurality of users; When the first user is using the allocated shared vehicle, a size of an unused space among the available spaces is detected; determining whether or not vehicle allocation request data received while the first user is using the allocated shared vehicle is vehicle allocation request data including the desired space information that can be determined to be reliable; When it is determined that the vehicle dispatch request data received while the first user is using the dispatched shared vehicle is vehicle dispatch request data that includes reliable space information, which is desired space information that can be determined to be reliable, it is determined whether the size of the space included in the reliable space information is equal to or smaller than the size of the detected unused space; When it is determined that the size of the space included in the guaranteed space information is less than or equal to the size of the detected unused space, the vehicle dispatch support system dispatches a shared vehicle used by the first user to a second user who sent vehicle dispatch request data including the guaranteed space information.

Images