Vehicle dispatch system

Abstract

To control the limitation of opportunities to offer carpooling.SOLUTION: A dispatching system is a system for dispatching vehicles to transport users, and is provided with a plurality of vehicles and a server capable of communicating with the plurality of vehicles. The server dispatches the vehicles to transport a user B and a user A when there is an overlap section between a route to user B's destination and a route to user A's destination (steps S111 to S113, and step S115) and to a junction where the overlap section ends (step S114 and step S115).SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to a vehicle dispatch system, and more particularly to a vehicle dispatch system for dispatching vehicles for transporting users. [Background technology]

[0002] Conventionally, there have been systems that allow a first user to share a ride with another user who has the same destination as the first user, or whose destination is a stopover on the way to the first user's destination (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2009-181530 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the system described in Patent Document 1 has the following problems: When the destination of the other user is not a stopover point of the other user and the routes are the same up to a certain point, matching cannot be performed, and there is a risk that opportunities to provide a ride-sharing service will be limited.

[0005] This disclosure has been made to solve the above-mentioned problems, and its purpose is to provide a ride-hailing system that can reduce limitations on opportunities to offer ride-sharing. [Means for solving the problem]

[0006] A vehicle dispatch system according to the present disclosure is a vehicle dispatch system for dispatching vehicles for transporting users, comprising a plurality of vehicles and a server capable of communicating with the plurality of vehicles. When there is an overlapping section between a route to a first destination of a first user and a route to a second destination of a second user, the server dispatches a first vehicle to transport the first user and the second user, and dispatches a second vehicle to a branch point where the overlapping section ends.

[0007] According to this configuration, if there is an overlapping section between the route to the first destination of the first user and the route to the second destination of the second user, a ride-sharing can be provided. In addition, after the overlapping section ends, when the first user is transported to the first destination by the first vehicle, the second user can be transported to the second destination by the second vehicle, and when the second user is transported to the second destination by the second vehicle, the first user can be transported to the first destination by the second vehicle. As a result, a vehicle dispatch system capable of suppressing restrictions on opportunities to provide a ride-sharing can be provided. [Brief description of the drawings]

[0008] [Figure 1] 1 is a diagram showing a configuration of a vehicle dispatch system 1 according to this embodiment. [Diagram 2] 4 is a flowchart showing a process for dispatching a vehicle in this embodiment. [Diagram 3] FIG. 2 is a diagram for explaining a ride-sharing arrangement in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference characters and their description will not be repeated.

[0010] Fig. 1 is a diagram showing the configuration of a vehicle dispatch system 1 according to this embodiment. Referring to Fig. 1, the vehicle dispatch system 1 includes a plurality of vehicles 10, a server 100, and a mobile terminal 800 carried by a user who desires transportation by the vehicles 10. The vehicles 10, the server 100, and the mobile terminal 800 are capable of communicating with each other via a communication network 900.

[0011] The vehicle 10 includes a battery 11, an ECU (Electronic Control Unit) 12, a drive unit 13, a DCM (Data Communication Module) 14, an HMI (Human Machine Interface) 15, and a navigation device 17. The battery 11 stores power used for driving the vehicle 10. The battery 11 is, for example, a lithium ion battery. However, the battery 11 is not limited to this, and may be other types of batteries, for example, a nickel-metal hydride battery or an all-solid-state battery.

[0012] The ECU 12 includes a CPU (Central Processing Unit) and a memory. The memory includes a RAM (Random Access Memory) and a ROM (Read Only Memory) and stores programs and data used by the CPU. The CPU executes predetermined processing defined by a program according to the programs and data stored in the memory and data input from the outside, and stores data resulting from the execution in the memory or outputs it to the outside.

[0013] The navigation device 17 includes a GPS (Global Positioning System). The GPS detects position information of the vehicle 10. The navigation device 17 transfers the position information detected by the GPS to the CPU.

[0014] The drive unit 13 includes a motor generator and an inverter that drives the motor generator using power from the battery 11 and charges the battery 11 with regenerative power from the motor generator. The drive unit 13 may further include an engine that runs on fuel to drive the motor generator or the vehicle 10. In other words, the vehicle 10 may be an electric vehicle (BEV: Battery Electric Vehicle) that is equipped with a motor generator but does not have an engine. The vehicle 10 may be a hybrid electric vehicle (HEV: Hybrid Electric Vehicle) or a plug-in hybrid electric vehicle (PHEV: Plug-in Hybrid Electric Vehicle) that is equipped with a motor generator and an engine. The vehicle 10 may be a fuel cell electric vehicle (FCEV: Fuel Cell Electric Vehicle).

[0015] The DCM 14 is a module for communicating with external devices via a communication network 900, transmitting data from the ECU 12 to the external devices and transferring data from the external devices to the ECU 12.

[0016] The HMI 15 is provided near the driver's seat of the vehicle 10, receives information input by the user and outputs it to the ECU 12, and displays or audibly notifies the user of information from the ECU 12, and is configured to include, for example, a touch panel display.

[0017] The server 100 includes a CPU 110, a memory 120, a communication unit 130, and a large-capacity storage device 140. The server 100 manages the dispatch status of the vehicle 10. The memory 120 includes a random access memory (RAM) and a read-only memory (ROM). The communication unit 130 is capable of communicating with an external device via a communication network 900, and transmits data from the CPU 110 to the external device and transfers data from the external device to the CPU 110. The large-capacity storage device 140 is composed of a hard disk drive (HDD) or a solid state drive (SSD), and stores programs and data used by the CPU 110. The CPU 110 executes a predetermined process defined by a program according to the programs and data stored in the memory 120 or the large-capacity storage device 140 and data input from the external device to the communication unit 130, and stores data resulting from the execution in the memory 120 or the large-capacity storage device 140 or outputs the data from the communication unit 130 to the external device.

[0018] The mobile terminal 800 includes a CPU 810, a memory 820, a communication unit 830, an input unit 840, and an output unit 850. The functions of the memory 820 and the communication unit 830 of the mobile terminal 800 are the same as those of the memory 120 and the communication unit 130 of the server 100 described above, respectively. The input unit 840 is composed of a touch panel, an operation button, and a microphone, and transfers data input from the touch panel, the operation button, or the microphone to the CPU 810. The output unit 850 is composed of a display and a speaker, and outputs data from the CPU 810 from the display or the speaker. The CPU 810 executes a predetermined process defined by a program according to the program and data stored in the memory 820, data input from an external device to the communication unit 830, and data input from the input unit 840, and stores data resulting from the execution in the memory 820, outputs the data from the communication unit 830 to an external device, or outputs the data from the output unit 850.

[0019] Conventionally, there have been systems that allow a user to share a ride with another user who has a common destination with the first user, or a user whose destination is a stopover point on the first user's route. Such systems have the following problems. When the destination of the other user is not a stopover point of the first user, and the routes are the same up to a certain point, matching may not be possible, limiting the opportunities to provide a rideshare.

[0020] Therefore, when there is an overlapping section between the route to the first destination of the first user and the route to the second destination of the second user, the server 100 dispatches a first vehicle 10 to transport the first user and the second user, and dispatches a second vehicle 10 to the junction where the overlapping section ends.

[0021] Fig. 2 is a flowchart showing the process for dispatching a vehicle in this embodiment. Referring to Fig. 2, a vehicle dispatch application, which is an application program for receiving a vehicle dispatch service in the vehicle dispatch system 1, is pre-installed in the memory 820 of the mobile terminal 800. The vehicle dispatch application is executed by the CPU 810 of the mobile terminal 800. The vehicle dispatch process is called from a higher-level process by the CPU 110 of the server 100 at predetermined intervals and executed. The navigation process is called from a higher-level process by the ECU 12 of the vehicle 10 at predetermined intervals and executed in cooperation with the navigation device 17.

[0022] First, in the vehicle dispatch application of the mobile terminal 800, the CPU 810 of the mobile terminal 800 determines whether or not a vehicle dispatch request from user B has been accepted by the input unit 840 (step S811). If it is determined that the vehicle dispatch request has been accepted (YES in step S811), the CPU 810 controls the communication unit 830 to accept input of the departure point, destination, departure time, and desired arrival time desired by user B at the input unit 840 and transmit them to the server 100 via the communication network 900 (step S812). If it is determined that the vehicle dispatch request has not been accepted (NO in step S811) or after step S812, the CPU 810 returns the processing to be executed to the upper processing of the vehicle dispatch application.

[0023] In the server 100, the CPU 110 judges whether the starting point, the destination, the departure time, and the desired arrival time are received by the communication unit 130 from the mobile terminal 800 of the user B (step S111). When it is judged that the starting point and the like are received (YES in step S111), the CPU 110 searches for a vehicle 10A that is scheduled to pass near the received starting point at the received departure time (step S112). When the vehicle 10A is already in a shared ride with another user A, the CPU 110 searches for a vehicle 10A that is capable of making a detour to the received starting point and has at least a partial overlap of routes to the destination P2 of the user B and the other user A. Note that it is judged that a detour is possible, for example, when there is permission from the user A already in the vehicle, and the delay in the expected arrival time of the user A at the destination P2 is within a predetermined time (for example, 5 minutes).

[0024] FIG. 3 is a diagram for explaining carpooling in this embodiment. Referring to FIG. 3, vehicle 10A is scheduled to carry user A from departure point P1 and arrive at destination P2 via routes R1, R2, and R3. In this case, a request for dispatch is received from user B, and a vehicle 10A scheduled to pass near user B's departure point P4 is searched for. This vehicle 10A is already in a carpooling state with other user A, but it is possible for user A to make a detour to user B's departure point P4, and the routes to branch point P5 on the way are partially overlapped between user A and user B. Therefore, vehicle 10A is searched for as a vehicle 10 that can transport user B.

[0025] 2, when the server 100 determines that the departure place and the like have not been received (NO in step S111), or after step S112, the CPU 110 determines whether the searched vehicle 10A can transport the user B to the destination P6 (step S113). Note that transportation to the destination P6 is determined to be possible when permission is given by the user A already in the vehicle, and the delay in the scheduled arrival time of the user A at the destination P2 is within a predetermined time (for example, 5 minutes).

[0026] If it is determined that the vehicle 10B is not capable of transporting the user B to the destination P6 (NO in step S113), the CPU 110 searches for a vehicle 10B that can be transferred to at the branch point (step S114). If the vehicle 10B is already in a shared ride with another user, a vehicle 10B that can make a detour to the branch point P5 and has at least a partial overlap in routes to the destinations of the user B and the other user is searched for. Note that a detour is determined to be possible, for example, when there is permission from the other user already in the vehicle and the delay in the expected arrival time at the destination of the other user is within a predetermined time (for example, 5 minutes). If the CPU 110 determines in step S113 that the vehicle 10B is not capable of transporting the user B to the destination P6, it repeats the process of step S114.

[0027] If it is determined that the vehicle 10 can transport the user to the destination P6 (YES in step S113), the CPU 110 controls the communication unit 130 to transmit the section for which each of the determined vehicles 10A, 10B is responsible for transporting the user and the scheduled time of transportation to each of the determined vehicles 10A, 10B via the communication network 900 (step S115). If it is determined that the departure point, etc. has not been received from the user (NO in step S111) or after step S115, the CPU 110 returns the process to be executed to the upper process.

[0028] In the vehicles 10A and 10B, the CPU of the ECU 12 determines whether or not the transportation section and the scheduled transportation time have been received by the DCM 14 (step S211). If it is determined that the transportation section and the scheduled transportation time have been received (YES in step S211), the CPU of the ECU 12 stores the received transportation section and the scheduled transportation time in the memory of the ECU 12 (step S212).

[0029] If it is determined that the transportation section etc. have not been received (NO in step S211), or after step S212, the CPU of the ECU 12 determines whether it is time to start moving to the departure point or the branch point (step S221). If it is determined that the movement start time has arrived (YES in step S221), the CPU of the ECU 12 controls the navigation device 17 to start navigation of the movement to the departure point or the branch point and the travel of the transportation section (step S222). The CPU of the ECU 12 controls the navigation device 17 to make a temporary stop at the departure point, the branch point, and the destination to allow the user to get on and off. If it is determined that the movement start time has not arrived (NO in step S221), or after step S222, the CPU of the ECU 12 returns the processing to be executed to the upper processing.

[0030] 3, when dispatch of vehicle 10A to user B's departure point P4 is decided, vehicle 10A, which was scheduled to proceed from route R1 to route R2, changes to route R4 at route change point P3. Vehicle 10A picks up user B at departure point P4, proceeds to branch point P5 via route R5, and drops off user B. Vehicle 10A then proceeds to destination P2 via route R3, and drops off user A at destination P2.

[0031] When the dispatch of vehicle 10B to branch point P5 is determined, vehicle 10B starts moving so as to arrive at branch point P5 at the scheduled arrival time of vehicle 10A. Vehicle 10B picks up user B at branch point P5, proceeds to destination P6 via route R6, and drops off user B at destination P6.

[0032] [Variations] (1) In the above-described embodiment, the vehicle 10A, 10B is driven by a driver based on instructions from the navigation device 17. However, this is not limited thereto, and an automatic driving system may drive the vehicle 10A, 10B based on instructions from the navigation device 17.

[0033] (2) In the above-described embodiment, the departure time shown in step S812 in FIG. 2 may be the time at which a vehicle can arrive immediately if dispatched at the current time, or it may be the reserved departure time several hours or days later.

[0034] (3) The above-described embodiment can be understood as a disclosure of the vehicle dispatch system 1, the server 100, the vehicle 10, and the mobile terminal 800, or a disclosure of a vehicle dispatch-related method or program executed by these.

[0035] [summary] (1) As shown in Fig. 1 to Fig. 3, the vehicle dispatch system 1 is a system for dispatching vehicles 10 for transporting users, and includes a plurality of vehicles 10 and a server 100 capable of communicating with the plurality of vehicles 10. As shown in Fig. 2 and Fig. 3, when there is an overlapping section (e.g., routes R4 and R5) between a route to a destination of user B (e.g., destination P6) and a route to a destination of user A (e.g., destination P2), the server 100 dispatches a vehicle 10A to transport user B and user A (e.g., steps S111 to S113, step S115), and dispatches a vehicle 10B to a branch point (e.g., branch point P5) where the overlapping section ends (e.g., steps S114, step S115).

[0036] As a result, if there is an overlapping section between the route to the destination of user B and the route to the destination of user A, a ride-sharing can be offered. Furthermore, after the overlapping section ends, when user B is transported to the destination (e.g., destination P6) by vehicle 10B, user A can be transported to the destination (e.g., destination P2) by vehicle 10A, and when user A is transported to the destination (e.g., destination P2) by vehicle 10B, user B can be transported to the destination (e.g., destination P6) by vehicle 10A. As a result, it is possible to suppress limitations on opportunities to offer ride-sharing.

[0037] The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the disclosure is defined by the claims, not by the description of the embodiments described above, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0038] 1 Vehicle dispatch system, 10, 10A, 10B Vehicle, 11 Battery, 12 ECU, 13 Drive unit, 14 DCM, 15 HMI, 17 Navigation device, 100 Server, 110 CPU, 120 Memory, 130 Communication unit, 140 Mass storage device, 800 Mobile terminal, 810 CPU, 820 Memory, 830 Communication unit, 840 Input unit, 850 Output unit, 900 Communication network.

Claims

[Claim 1] A vehicle dispatch system for dispatching a vehicle for transporting a user, comprising: Multiple vehicles and A server capable of communicating with the plurality of vehicles, The server, dispatching a first vehicle to transport the first user and the second user when there is an overlap between a route to a first destination of a first user and a route to a second destination of a second user; A vehicle dispatching system that dispatches a second vehicle to a branch point where the overlapping section ends.

Images