Vehicle allocation management device and vehicle allocation management method
Patent Information
- Application Number
- JP2023142073
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-09-01
- Publication Date
- 2025-03-13
AI Technical Summary
【0009】 本発明によれば、現在の車両の供給量と将来の車両の需要量とを考慮して乗合可能な車両の台数を調整するので、現在及び将来のユーザに対して車両の効率的な配車が可能になる。
Smart Images

Figure 2025035187000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a vehicle allocation management device and a vehicle allocation management method. [Background technology]
[0002] Mobility services are services that provide smooth transportation of passengers and / or luggage by vehicles. Mobility services require efficient vehicle allocation in order to increase the utilization rate of each vehicle and improve user convenience.
[0003] For example, the following Patent Document 1 discloses a technology in a ride-sharing system in which multiple transport objects with different destinations ride together in a vehicle, in which vacant vehicles are allocated so that there are a predetermined number or more vacant vehicles among the multiple vehicles that can carry the transport objects around the driving position of an operating vehicle that carries the transport objects. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2020-135314 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, the technology described in Patent Document 1 above allocates vehicles simply based on the current supply of vehicles, without any consideration of future vehicle demand, and therefore may allocate all of the vehicles present in the vicinity of the boarding location indicated in the user's allocation request, resulting in the problem that vehicles cannot be allocated quickly in response to subsequent allocation requests.
[0006] Therefore, the present invention aims to provide a vehicle dispatch management device and a vehicle dispatch management method that adjusts the number of vehicles available for sharing, taking into account the relationship between the current supply of vehicles and the future demand for vehicles, thereby enabling efficient dispatch of vehicles. [Means for solving the problem]
[0007] The present invention, which aims to solve the above problems, includes the following invention-specific matters and technical features.
[0008] The present invention according to one aspect is a vehicle dispatch management device that manages the dispatch of vehicles in a target area of a vehicle dispatch service based on a dispatch request. The vehicle dispatch management device includes a vehicle information acquisition unit that acquires predetermined vehicle information from the vehicles, a vehicle supply amount calculation unit that calculates a vehicle supply amount, which is a supply amount of vehicles that can be dispatched from among the plurality of vehicles, based on the predetermined vehicle information, a vehicle demand amount calculation unit that calculates a predicted vehicle demand amount, which is a demand amount of the vehicles in a predetermined time period in the future, a shared vehicle supply amount adjustment unit that adjusts a shared vehicle supply amount, which is a supply amount of vehicles that can be shared between users, based on a relationship between the vehicle supply amount and the predicted vehicle demand amount, and a vehicle allocation unit that allocates the vehicles to the users who have made the dispatch request according to a predetermined vehicle allocation judgment criterion. The shared vehicle supply amount adjustment unit adjusts the shared vehicle supply amount by changing the predetermined vehicle allocation judgment criterion. Effect of the Invention
[0009] According to the present invention, the number of vehicles available for sharing is adjusted taking into account the current supply of vehicles and the future demand for vehicles, thereby enabling efficient allocation of vehicles to current and future users.
[0010] Other technical features, objects, and operational effects or advantages of the present invention will become apparent from the following embodiments described with reference to the accompanying drawings. The effects described in this specification are merely examples and are not limited thereto, and other effects may also be present. [Brief description of the drawings]
[0011] [Figure 1] FIG. 1 is a diagram showing an example of a schematic configuration of a vehicle dispatch management system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram for explaining the allocation of vehicles in a target area of a vehicle dispatch service. [Diagram 3] FIG. 3 is a block diagram showing an example of a functional configuration model of a vehicle dispatch control device according to an embodiment of the present invention. [Figure 4] FIG. 4 is a block diagram showing details of the vehicle dispatch plan formulation unit in the vehicle dispatch management device according to one embodiment of the present invention. [Diagram 5] FIG. 5 is a flowchart for explaining an example of a shared vehicle management process by the vehicle dispatch management device according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. However, the embodiment described below is merely an example, and there is no intention to exclude various modifications and application of techniques not specified below. The present invention can be implemented by various modifications (for example, combining the respective embodiments) within the scope of the gist of the present invention. In addition, in the following description of the drawings, the same or similar parts are represented by the same or similar reference numerals. The drawings are schematic and do not necessarily correspond to actual dimensions, ratios, etc. The drawings may also include parts with different dimensional relationships and ratios.
[0013] 1 is a diagram showing an example of a schematic configuration of a vehicle dispatch management system according to an embodiment of the present invention. As shown in the figure, the vehicle dispatch management system 1 includes a vehicle dispatch management device 10, a terminal device 20, and a vehicle V, which are connected to each other so as to be able to communicate with each other via a communication network N. In addition, the vehicle dispatch management system 1 can be connected via the communication network N to a road traffic information management system 30 that provides various types of traffic information in real time.
[0014] The vehicle dispatch management system 1 of the present disclosure provides a vehicle dispatch service using a plurality of vehicles V, for example, for a certain area. The vehicle dispatch service may be either an "on-demand" system or a "reservation" system. Furthermore, the vehicles V may be either a manned vehicle or an unmanned vehicle.
[0015] The vehicle dispatch management device 10 is a computing device that comprehensively manages a vehicle dispatch service by a plurality of vehicles V in a target area of the vehicle dispatch service. The vehicle dispatch management device 10 implements, for example, a vehicle dispatch management server program and executes the vehicle dispatch management server program under the control of a processor, thereby realizing the vehicle dispatch service of the present disclosure.
[0016] The vehicle dispatch management device 10 includes various databases 12 that accumulate and manage data necessary to realize such a vehicle dispatch service. The databases 12 may include, for example, a user information database 12a, a road map information database 12b, a vehicle information database 12c, a vehicle dispatch plan database 12d, and an operation record information database 12e (see FIG. 3). The databases 12 may be configured as a part of the vehicle dispatch management device 10, or all or a part of the databases 12 may be configured separately from the vehicle dispatch management device 10.
[0017] In general, the vehicle allocation management device 10 accepts a vehicle allocation request from a user who wishes to allocate a vehicle V to a destination, extracts a vehicle V to be allocated to the user from among a plurality of vehicles V based on the vehicle allocation request, creates a vehicle allocation plan, and proposes the created vehicle allocation plan to the user. The vehicle allocation management device 10 finalizes the proposed vehicle allocation plan based on the user's consent to the proposed vehicle allocation plan, and issues a vehicle allocation instruction to the vehicle V according to the finalized vehicle allocation plan.
[0018] The dispatch plan includes a driving route that defines a route from a location where the vehicle V is waiting (a starting waiting location), passing through several points (boarding and disembarking points) along the way where the user gets on and off, to a final waiting location (not necessarily the same as the initial waiting location). If the vehicle V is waiting, the dispatch plan is newly created based on a new dispatch request, and if the vehicle V is in operation, the dispatch plan can be updated based on a new dispatch request.
[0019] The vehicle V is a vehicle registered in the vehicle information database 12c that is provided for use by a user. The vehicle V may be of any type (e.g., a sedan, a minivan, an SUV, etc.). The vehicle V may be an electric vehicle (EV) powered by an on-board battery. The vehicle V may also be a conventional manned vehicle. Alternatively, the vehicle V may be an unmanned vehicle capable of autonomous driving using an automated driving system, and the so-called level of automated driving may not be an issue.
[0020] The vehicle V is equipped with a control device CTL that controls the vehicle V itself or its on-board equipment according to instructions from the vehicle dispatch management device 10. Although not shown, the control device CTL is configured to include a processor, a memory, etc. The control device CTL, for example, acquires geographical position information (hereinafter referred to as "position information") of the vehicle V via a GPS system and controls the transmission of this information to the vehicle dispatch management device 10, and also receives dispatch instructions from the vehicle dispatch management device 10 and controls the operation of various devices or equipment of the vehicle V. The control device CTL also controls, for example, the current boarding status of the vehicle V to be transmitted to the vehicle dispatch management device 10.
[0021] The terminal device 20 is, for example, a computing device for a user who wishes to ride to make a vehicle dispatch request by operating a user interface. The terminal device 20 is, for example, a smartphone, a pad computer, a notebook personal computer, a desktop computer, etc., but is not limited to these. The terminal device 20 implements, for example, a vehicle dispatch management client program (so-called a vehicle dispatch application). The terminal device 20 executes the vehicle dispatch application under the control of the processor, thereby enabling the user to use the vehicle dispatch service of the vehicle dispatch management device 10. For example, the user can make a vehicle dispatch request from a vehicle dispatch request screen (not shown) on the user interface of the terminal device 20, and accept the vehicle dispatch plan created by the vehicle dispatch management device 10 in response to the request, thereby making a reservation for a ride in the vehicle V.
[0022] The road traffic information management system 30 is an information and communication system that provides road traffic information in real time. For example, the road traffic information management system 30 collects road traffic data from vehicle sensors and cameras installed on roads, and also collects driving data from a control device CTL mounted on the vehicle V, and manages road traffic information that is integrated, processed, and edited from the data. The edited road traffic information may include, for example, information on road closures and detour routes, and the time required between points via a specific route. The road traffic information management system 30 appropriately provides the road traffic information to the vehicle dispatch management device 10 and the vehicle V.
[0023] In the vehicle dispatch management system 1 as described above, the vehicle dispatch management device 10 acquires predetermined vehicle information from each vehicle in the target area of the vehicle dispatch service, calculates the supply amount (vehicle supply amount) of vehicles V that can be dispatched at the present time, calculates the demand amount (predicted vehicle demand amount) of vehicles V in a predetermined time period in the future, and increases the supply amount of vehicles V that can be shared between users when it is determined that the predicted vehicle demand amount is large compared to the vehicle supply amount. The supply amount of vehicles V that can be shared is adjusted, for example, by changing a predetermined vehicle allocation judgment criterion. This makes it possible to avoid the inconvenience of dispatching all vehicles V that are near the boarding location indicated by the user's dispatch request, which causes a delay in dispatching vehicles V in response to a dispatch request that will occur in the future.
[0024] For example, as shown in Fig. 2(a), at a certain time, vehicles V1 and V2 are waiting at a waiting place P1, and vehicle V3 is waiting at a waiting place P2. Note that in the figure, the lattice points indicate boarding points or disembarking points where users can get on and off.
[0025] Assume now that the vehicle dispatch management device 10 has received a vehicle dispatch request from a user U1 who wishes to ride from a boarding location O1 to a disembarking location D1, and has also received a vehicle dispatch request from a user U2 who wishes to ride from a boarding location O2 to a disembarking location D2. Assume, on the other hand, that the vehicle dispatch management device 10 has predicted a vehicle dispatch request (i.e., vehicle demand) from a user U3 who wishes to ride from a boarding location O3 to a disembarking location D3 in a time slot five minutes from now.
[0026] In such a situation, according to the conventional vehicle dispatch method, as shown in Fig. 2(b), the currently most suitable vehicle V is assigned each time a vehicle dispatch request is received from a user, so that the vehicle V1 waiting at the waiting place P1 near the boarding place O1 is assigned to the user U1, while the vehicle V1 is assigned to the user U2, while the vehicle V2 waiting at the waiting place P1 near the boarding place O2 is assigned to the user U2. Therefore, even if a demand for one vehicle V is expected in five minutes, there is no vehicle V available at the waiting place P1 near the boarding place O3, and by dispatching the vehicle V3 waiting at the waiting place P2, the waiting time of the potential user U3 increases significantly, and therefore the average waiting time of users when viewed in the entire vehicle dispatch service increases.
[0027] In response to this, the vehicle dispatch management device 10 of the present disclosure accepts the dispatch requests of users U1 and U2, respectively, while considering the dispatch request of potential user U3 in a future time period (five minutes from now in this example), and assigns an optimal vehicle V to each user U. That is, as shown in FIG. 2(c), the vehicle dispatch management device 10 adjusts the supply of vehicles V available for sharing by changing a predetermined vehicle dispatch allocation judgment criterion, thereby assigning vehicle V1 to the shared ride of users U1 and U2, and securing vehicle V for future potential user U3. This makes it possible to reduce the average waiting time for users when viewed throughout the entire vehicle dispatch service.
[0028] FIG. 3 is a block diagram showing an example of a functional configuration model of a vehicle dispatch management device according to an embodiment of the present invention. As shown in the figure, the vehicle dispatch management device 10 can be configured as a functional configuration model including functional components such as a front-end processing unit 110, a vehicle dispatch plan formulation unit 120, and a vehicle communication unit 130. In addition, as described above, the vehicle dispatch management device 10 includes various databases 12. Such a functional model is realized by the vehicle dispatch management device 10 executing a vehicle dispatch management server program under the control of a processor, thereby cooperating with various hardware resources. The functional configuration model shown here is an example, and all or part of the functions of a certain functional component may be realized by other functional components. In addition, in the figure, for convenience of explanation, a user's terminal device 20 and a control device CTL in a vehicle V are also shown.
[0029] The user information database 12a stores information about users who use the vehicle dispatch service (hereinafter referred to as "user information"). The user information includes, for example, a user ID and password, personal attributes (gender, age, need for assistance, etc.), and information about the service usage status. The user information is registered in the user information database 12a under the control of the vehicle dispatch management device 10 by the user inputting predetermined information, for example, when the vehicle dispatch app is first started.
[0030] The road map information database 12b stores map information for the target area of the vehicle dispatch service. The map information includes map data related to addresses, place names, roads, facilities, etc. The map information may also include information necessary for searching for a driving route, such as road information, feature information, and environmental information.
[0031] The vehicle information database 12c stores information (vehicle information) about the vehicle V that is provided for use by the user. The vehicle information includes, for example, information about the vehicle ID, vehicle attributes (vehicle registration number, vehicle model, maximum number of passengers / maximum load capacity, number of transportation spaces, manned or unmanned driving type, etc.), vehicle performance, other specifications, current vehicle dispatch plan, current location, and current status (service status, remaining battery capacity (driving range), number of passengers, and usage status of transportation spaces, etc.). The vehicle information acquired from the vehicle V via the vehicle communication unit 130 may be updated at any time.
[0032] The vehicle allocation plan database 12d stores a vehicle allocation plan for each vehicle V created by the vehicle allocation plan formulation unit 120 based on a vehicle allocation request. As described above, the vehicle allocation plan includes a driving route from a waiting location serving as a starting point to a waiting location serving as an end point via several starting and ending points, an expected arrival time at each intermediate point, and the like.
[0033] The operation performance information database 12e stores information (operation performance information) on past operation performance, for example, for each vehicle V. The operation performance information includes various types of specification information, such as operation time (operation start time and end time), travel route, and travel distance, for each vehicle V. The operation performance information is used to calculate a predicted vehicle demand, which is the demand for the vehicle V at a predetermined time in the future.
[0034] The front-end processing unit 110 performs various processes with the user's terminal device 20. As an example, the front-end processing unit 110 refers to the user information database 12a in response to a login request from a vehicle dispatch application on the user's terminal device 20, and performs a login authentication process. The front-end processing unit 110 also communicates with the terminal device 20 in order to respond to a vehicle dispatch request from the vehicle dispatch application on the user's terminal device 20. More specifically, the front-end processing unit 110 receives a vehicle dispatch request, transfers it to the vehicle dispatch request acceptance unit 121, and in response thereto, transmits a vehicle dispatch plan created by the vehicle dispatch plan formulation unit 120 to the terminal device 20, and causes the vehicle dispatch plan (candidate vehicles) to be displayed on the user interface of the terminal device 20. The front-end processing unit 110 receives a notification of acceptance or rejection by the user transmitted from the terminal device 20 in response thereto, and transfers it to the vehicle dispatch plan formulation unit 120.
[0035] The vehicle allocation plan formulation unit 120 creates and / or updates a vehicle allocation plan for candidate vehicles V among the vehicles V that can operate in the target area based on the vehicle allocation request delivered from the front-end processing unit 110. The vehicle allocation plan formulation unit 120 proposes the created or updated vehicle allocation plan to the user via the front-end processing unit 110. When the vehicle allocation plan formulation unit 120 receives approval from the user for the proposed vehicle allocation plan, it finalizes the approved vehicle allocation plan, stores the finalized vehicle allocation plan in the vehicle allocation plan database 12d, and issues an allocation instruction to the vehicles V of the vehicle allocation plan. As described below, the vehicle allocation plan formulation unit 120 adjusts the shared vehicle supply amount, which is the supply amount of vehicles V that can be shared between users, by changing a predetermined vehicle allocation judgment criterion based on the relationship between the current vehicle supply amount and the future predicted vehicle demand amount.
[0036] The vehicle communication unit 130 exchanges various information with the vehicle V via the communication network N. For example, the vehicle communication unit 130 transmits a vehicle information transmission request to the vehicle V, and receives vehicle information transmitted by the vehicle V in response to the request. The vehicle information includes, for example, position information of the vehicle V. In addition, the vehicle communication unit 130 transmits driving instructions to the vehicle V according to the determined vehicle dispatch plan.
[0037] 4 is a block diagram showing details of a vehicle dispatch plan formulation unit in a vehicle dispatch management device according to an embodiment of the present invention. As shown in the figure, the vehicle dispatch plan formulation unit 120 includes, for example, a vehicle dispatch request acceptance unit 121, a vehicle information acquisition unit 122, a vehicle supply amount calculation unit 123, a vehicle demand amount calculation unit 124, a bus supply amount adjustment unit 125, a vehicle allocation unit 126, a vehicle placement adjustment unit 127, and a vehicle dispatch instruction unit 128.
[0038] The dispatch request reception unit 121 acquires and accepts a dispatch request from a user via the front-end processing unit 110. The time when the dispatch request reception unit 121 accepts the dispatch request is the start time of counting various limit allowable times of the user (e.g., limit allowable waiting time for boarding, limit allowable waiting time for departure, limit allowable time for arrival at the destination, etc.). Various limit allowable times are examples of vehicle allocation criteria. For example, the limit allowable waiting time for boarding is one of the conditions for whether or not a ride-sharing between users is established. For example, if the waiting time of one user exceeds the limit allowable waiting time for departure when considering the ride-sharing of the other user, the ride-sharing is not established. The dispatch request reception unit 121 passes the accepted dispatch request to the vehicle allocation unit 126.
[0039] The vehicle information acquisition unit 122 communicates with the control device CTL of the vehicle V via the vehicle communication unit 130 and acquires vehicle information including location information, boarding information, status information, and the like of the vehicle V. The boarding information includes, for example, the number of passengers relative to the capacity, and the like. The status information includes, for example, the cruising distance based on the remaining battery power, and the like. The vehicle information acquisition unit 122 updates the vehicle information database 12c based on the acquired vehicle information.
[0040] The vehicle supply amount calculation unit 123 calculates a vehicle supply amount, which is the supply amount of vehicles available for dispatch at the present time (i.e., the vehicle supply amount in the current time period), based on the acquired vehicle information. The vehicle supply amount calculation unit 123 may calculate the vehicle supply amount for each sub-area in the target area of the vehicle dispatch service. For example, the vehicle supply amount calculation unit 123 calculates the vehicle supply amount excluding vehicles V undergoing maintenance such as battery charging. In addition, the vehicle supply amount calculation unit 123 may calculate a predicted vehicle supply amount, which is the supply amount of vehicles available for dispatch in a specified time period in the future.
[0041] The vehicle demand amount calculation unit 124 calculates the demand for vehicles V in a predetermined time period in the future. The vehicle demand amount calculation unit 124 may calculate the vehicle demand amount for each sub-area. For example, the vehicle demand amount calculation unit 124 calculates the current vehicle demand amount based on the received vehicle dispatch request. In addition, the vehicle demand amount calculation unit 124 calculates a predicted vehicle demand amount, which is the demand amount for vehicles V in a predetermined time period in the future, based on the operation performance information database 12e.
[0042] The vehicle demand calculation unit 124 may create predicted demand information by considering, for example, traffic conditions and environmental information in the target area in addition to the operation record information. The environmental information may include, for example, event holding information. The predicted vehicle demand includes the predicted occurrence time, departure point, destination, waiting place around the departure point, initial travel time, planned travel distance, end time, and waiting place around the destination in a predetermined unit time (for example, every 10 minutes from the reference time until 30 minutes ahead), etc. The vehicle demand calculation unit 124 may include, for example, a demand prediction model in which machine learning is performed according to a predetermined machine learning algorithm with the operation record information as an explanatory variable and the predicted vehicle demand as an objective variable.
[0043] The shared vehicle supply amount adjustment unit 125 adjusts the shared vehicle supply amount, which is the supply amount of vehicles V that can be shared between users, by changing a predetermined vehicle allocation judgment criterion based on the relationship between the vehicle supply amount in the current time period and the predicted vehicle demand amount in the future time period. Typically, the shared vehicle supply amount adjustment unit 125 adjusts the shared vehicle supply amount for each sub-area in the target region based on the relationship between the vehicle supply amount and the predicted vehicle demand amount. For example, the shared vehicle supply amount adjustment unit 125 increases the shared vehicle supply amount as the predicted vehicle demand amount is greater relative to the vehicle supply amount. This makes it possible to secure vehicles V for future vehicle demand, and to reduce the average waiting time of all users in the target area of the vehicle dispatch service.
[0044] In this case, the shared vehicle supply adjustment unit 125 adjusts the shared vehicle supply amount by dispatching vehicles V other than the vehicle V already in the user as a shared vehicle V by dispatching vehicles in response to the dispatch request. As a result, the vehicle V already in the user's vehicle is not eligible for sharing with other users, so that it is possible to prevent an excessive decrease in the level of dispatch service (LOS) for users who are in the vehicle.
[0045] In addition, the shared vehicle supply adjustment unit 125 records and holds the relationship between the vehicle supply volume and the predicted vehicle demand volume over time. This allows the shared vehicle supply adjustment unit 125 to evaluate the change over time in the supply and demand balance of the vehicle V. For example, the shared vehicle supply adjustment unit 125 monitors whether the predicted vehicle demand volume is high compared to the vehicle supply volume continues for a certain period of time, and increases the shared vehicle supply volume when it determines that such a state has continued for a certain period of time. This makes it possible to reduce the average waiting time of all users in the target area of the vehicle dispatch service by reserving the vehicle V in preparation for the future when a high demand for vehicles is expected to continue in the future.
[0046] In addition, the shared vehicle supply amount adjustment unit 125 adjusts the shared vehicle supply amount by preferentially using the waiting time of the user as a predetermined vehicle allocation judgment criterion. For example, the shared vehicle supply amount adjustment unit 125 adjusts the shared vehicle supply amount based on the waiting time of the user. Alternatively, the shared vehicle supply amount adjustment unit 125 adjusts the shared vehicle supply amount by preferentially using the time it takes for the user to travel to the boarding location (non-rental time) as a predetermined vehicle allocation judgment criterion. For example, the shared vehicle supply amount adjustment unit 125 may adjust the shared vehicle supply amount based on the non-rental time for the user. In addition, when the shared vehicle supply amount adjustment unit 125 determines that the predicted vehicle demand amount is high compared to the vehicle supply amount, it may change the vehicle allocation judgment criterion from the user's waiting time priority to the non-rental time priority. This promotes sharing between users, and makes it possible to secure vehicles V for future vehicle demand.
[0047] In addition, the shared vehicle supply adjustment unit 125 may relax the predetermined vehicle allocation judgment criteria when it is determined that the predicted vehicle demand is large relative to the vehicle supply. As an example, the shared vehicle supply adjustment unit 125 extends the maximum allowable waiting time for users from 5 minutes to 10 minutes, for example. As a result, the waiting time of some users will increase within a range that does not exceed the maximum allowable waiting time for users, but by allocating a vehicle V that can be shared to the user, sharing between users will be promoted, and it becomes possible to secure a vehicle V for future vehicle demand.
[0048] In addition, when the shared vehicle supply adjustment unit 125 determines that the predicted vehicle demand is high relative to the vehicle supply, it may limit the supply of vehicles V available for dispatch indicated by a predetermined vehicle allocation judgment criterion. In other words, by limiting the supply of vehicles V available for dispatch according to a predetermined vehicle allocation judgment criterion, the dispatch of vehicles V available for dispatch is relatively increased, which promotes sharing between users.
[0049] In addition, the shared vehicle supply amount adjustment unit 125 adjusts the shared vehicle supply amount to increase within a range of a predetermined upper limit value. This makes it possible to prevent an excessive increase in the supply amount of shared vehicles V. In other words, the shared vehicle supply amount adjustment unit 125 may set a predetermined upper limit value based on the waiting time at the boarding location of the user who made the dispatch request for a shared vehicle V in the first sub-area in which the user is located, and the waiting time at the boarding location of the user for a shared vehicle V in a second sub-area other than the first sub-area. This prevents vehicles from being excessively dispatched from areas other than the area in which the user is located due to the occurrence of a shared ride.
[0050] The vehicle allocation unit 126 allocates a vehicle V to a user who has made a vehicle dispatch request according to a predetermined vehicle allocation criterion. Typically, the vehicle allocation unit 126 allocates to the user an optimal vehicle V that can be shared and is selected according to the predetermined vehicle allocation criterion. For example, the vehicle allocation unit 126 allocates a vehicle that can be shared, for which the predetermined vehicle allocation criterion exceeds a predetermined suitability, to a combination of users who are the subject of a ride-sharing. The predetermined suitability is a value that is scored based on various conditions, such as the user's waiting time and non-rental time. This makes it possible to reduce the average waiting time for all users in the target area of the ride-dispatch service.
[0051] The vehicle allocation unit 126 creates a vehicle allocation plan for the vehicle V allocated to the user. The vehicle allocation plan includes a driving route that defines a location where the vehicle V waits (a starting point of waiting location) via several points (boarding and disembarking points) along the way where users get on and off, to a final waiting location (not necessarily the same as the initial waiting location). For example, the vehicle allocation unit 126 creates a vehicle allocation plan for a vehicle V shared between users so that the vehicle V runs through the boarding and disembarking points of each user.
[0052] The vehicle allocation unit 126 may propose the created vehicle allocation plan to the user and accept or reject the plan from the user. When the vehicle allocation unit 126 accepts the user's acceptance of the proposed vehicle allocation plan, the vehicle allocation unit 126 finalizes the approved vehicle allocation plan, stores the finalized vehicle allocation plan in the vehicle allocation plan database 12d, and notifies the vehicle allocation instruction unit 128 to instruct the vehicle V of the vehicle allocation plan to be dispatched.
[0053] Furthermore, when the vehicle allocation unit 126 determines that there is a shortage of vehicles V available for sharing in a sub-area (first sub-area) in the target area of the vehicle dispatch service by referring to the vehicle information database 12c, it allocates vehicles V available for sharing in another sub-area (second sub-area) where the vehicle supply is greater than the predicted vehicle demand. This allows the vehicles V available for sharing in the entire target area to be efficiently operated, and promotes sharing between users.
[0054] Furthermore, when the vehicle allocation unit 126 determines that the vehicle demand in the first sub-area cannot be met even if a ride-shareable vehicle V from the second sub-area as described above is allocated, the vehicle allocation unit 126 may allocate a ride-shareable vehicle V in a predetermined standby state in the first sub-area. The predetermined standby state may include, for example, a state in which the on-board battery is being charged or other maintenance is being performed. In other words, even if the vehicle V is not fully charged due to charging of the on-board battery, it may be possible to allocate it depending on the mileage based on the dispatch request, and the vehicle allocation unit 126 can efficiently operate the vehicle V by allocating such a vehicle V when the vehicle demand is high.
[0055] The vehicle placement adjustment unit 127 adjusts the placement of the vehicles V between the sub-areas in the target area. That is, when the vehicle placement adjustment unit 127 determines that the difference between the predicted vehicle demand and the vehicle supply in the first sub-area is equal to or greater than a predetermined value, the vehicle placement adjustment unit 127 adjusts the placement of vehicles available for sharing in a second sub-area other than the first sub-area to the first sub-area. For example, the vehicle placement adjustment unit 127 increases the supply of vehicles available for sharing to be relocated as the difference between the predicted vehicle demand and the vehicle supply becomes larger. This ensures that vehicles V available for sharing are available in the sub-areas where the predicted demand is expected, and the vehicles V available for sharing in the entire target area can be efficiently operated, thereby promoting sharing between users.
[0056] The vehicle dispatch instruction unit 128 transmits driving instructions to the vehicle V according to the vehicle dispatch plan in response to the notification from the vehicle allocation unit 126. The control device CTL of the vehicle V that receives the driving instructions uses a navigation function to display, for example, a driving route according to the vehicle dispatch plan and a predicted arrival time at each point on a user interface (not shown) of the vehicle V. Alternatively, the control device CTL determines a detailed actual driving route according to the driving route in the vehicle dispatch plan, and performs control so that the vehicle autonomously drives along the actual driving route.
[0057] 5 is a flow chart for explaining an example of a shared vehicle management process by the vehicle dispatch management device according to one embodiment of the present invention. This process is realized by the vehicle dispatch management device 10 executing a vehicle dispatch management server program under the control of a processor, thereby cooperating with various hardware resources. The vehicle dispatch management device 10 executes this process at a predetermined timing, for example, regularly or irregularly.
[0058] As shown in the figure, the vehicle dispatch management device 10 acquires predetermined vehicle information from each vehicle V in the target area (S501). The predetermined vehicle information includes, for example, the current position information, boarding information, and operation information of the vehicle V.
[0059] Next, the vehicle allocation management device 10 calculates the current vehicle supply amount for each sub-area in the target area of the vehicle allocation service based on the acquired predetermined vehicle information (S502). Next, the vehicle allocation management device 10 refers to the operation performance information stored in the operation performance information database 12e and calculates the predicted vehicle demand amount for each sub-area in a predetermined time period in the future (S503). In this case, the vehicle allocation management device 10 can create predicted demand information by taking into account, for example, traffic conditions and environmental information in the target area in addition to the operation performance information. In addition, although not shown, the vehicle allocation management device 10 records and holds the calculated vehicle supply amount and predicted vehicle demand amount.
[0060] Next, the vehicle allocation management device 10 compares the vehicle supply volume with the predicted vehicle demand volume for each sub-area (S504) and determines whether the predicted vehicle demand volume is greater than the vehicle supply volume (S505). In this case, the vehicle allocation management device 10 may determine whether a state in which the vehicle supply volume is smaller than the predicted vehicle demand volume continues for a certain period of time. When the vehicle allocation management device 10 determines that the vehicle supply volume is not greater than the predicted vehicle demand volume (No in S505), the vehicle allocation management device 10 temporarily ends the process. In other words, the vehicle allocation management device 10 does not adjust the supply volume of vehicles V that can be shared at the current timing.
[0061] On the other hand, when the vehicle dispatch management device 10 determines that the predicted vehicle demand is high relative to the vehicle supply (Yes in S505), the vehicle dispatch management device 10 adjusts the supply of vehicles available for sharing in the sub-area by changing a predetermined vehicle allocation judgment criterion (S506). Typically, the shared vehicle supply adjustment unit 125 increases the shared vehicle supply as the predicted vehicle demand is high relative to the vehicle supply. In this case, the vehicle V already in use by the user is excluded from the vehicles V available for sharing.
[0062] For example, the vehicle allocation management device 10 changes the predetermined vehicle allocation judgment criteria from prioritizing user waiting time to prioritizing non-rented time in order to increase the supply of vehicles V that can be shared. Alternatively, the vehicle allocation management device 10 may relax the predetermined vehicle allocation judgment criteria (e.g., user waiting time, maximum allowable waiting time for boarding, non-rented time, etc.). Alternatively, the vehicle allocation management device 10 may limit the supply of vehicles V that can be shared, as indicated by the predetermined vehicle allocation judgment criteria, so that sharing of vehicles V that can be shared is relatively promoted.
[0063] In addition, the vehicle dispatch management device 10 may limit the supply of vehicles V available for sharing to a predetermined upper limit value to prevent the waiting time of a user from being shorter than the waiting time of the user when a vehicle V is dispatched from an area other than the area where the user is located due to the occurrence of sharing.
[0064] As described above, according to this embodiment, when a high demand for vehicles is expected in the future, the vehicle dispatch management device 10 increases the supply of vehicles V that can be shared at present to promote sharing between users, so that it is possible to secure vehicles V that can be dispatched in preparation for the future, and also to reduce the average waiting time of all users in the target area of the vehicle dispatch service. In particular, in this embodiment, the vehicle dispatch management device 10 adjusts the supply of vehicles V that can be shared by changing a predetermined vehicle allocation judgment criterion, so that it is possible to reduce the average waiting time of all users in the target area of the vehicle dispatch service without excessively lowering the level of the vehicle dispatch service.
[0065] The above-described embodiments are merely examples for explaining the present invention, and are not intended to limit the present invention to these embodiments. The present invention can be embodied in various forms without departing from the spirit of the present invention.
[0066] In addition, in the methods disclosed herein, steps, operations, or functions may be performed in parallel or in a different order, unless the results are inconsistent. The steps, operations, and functions described are provided merely as examples, and some of the steps, operations, and functions may be omitted or combined into one, or other steps, operations, or functions may be added, without departing from the spirit of the invention.
[0067] In addition, although various embodiments are disclosed in this specification, specific features (technical matters) in one embodiment can be added to or replaced with specific features in other embodiments, with appropriate modifications, and such forms are also included in the spirit of the present invention. [Explanation of symbols]
[0068] 1. Vehicle dispatch management system 10...Vehicle allocation management device 110...Front-end processing unit 120… Vehicle Allocation Planning Department 121…Vehicle dispatch request reception department 122…Vehicle information acquisition unit 123...Vehicle supply calculation unit 124...Vehicle demand calculation unit 125…Public Vehicle Supply Adjustment Department 126…Vehicle Allocation Department 127…Vehicle Layout Adjustment Section 128…Dispatch Instructions Department 130…Vehicle communication unit 12. Database 12a…User information database 12b…Road map information database 12c…Vehicle information database 12d…Vehicle allocation plan database 12e…Operational performance information database 20...Terminal device 30...Road Traffic Information Management System N: Communication network V…Vehicle CTL: Control device
Claims
1. A vehicle dispatch management device that manages vehicle dispatch in a target area of a vehicle dispatch service based on a vehicle dispatch request, a vehicle information acquisition unit that acquires predetermined vehicle information from the vehicle; a vehicle supply amount calculation unit that calculates a vehicle supply amount, which is a supply amount of vehicles that can be dispatched among the plurality of vehicles, based on the predetermined vehicle information; a vehicle demand amount calculation unit that calculates a predicted vehicle demand amount, which is a demand amount for the vehicle in a predetermined time period in the future; a shared vehicle supply amount adjustment unit that adjusts a shared vehicle supply amount, which is a supply amount of vehicles that can be shared between users, based on a relationship between the vehicle supply amount and the predicted vehicle demand amount; a vehicle allocation unit that allocates the vehicle to the user who has made the vehicle dispatch request in accordance with a predetermined vehicle allocation judgment criterion; The passenger vehicle supply amount adjustment unit adjusts the passenger vehicle supply amount by changing the predetermined vehicle allocation judgment criterion. Vehicle dispatch management device.
2. The passenger vehicle supply amount adjustment unit increases the passenger vehicle supply amount as the predicted vehicle demand amount is greater than the vehicle supply amount. The vehicle dispatch management device according to claim 1.
3. The passenger vehicle supply amount adjustment unit adjusts the passenger vehicle supply amount based on a relationship between the vehicle supply amount and the predicted vehicle demand amount for each sub-area in the target area. The vehicle dispatch management device according to claim 2.
4. The shared vehicle supply amount adjustment unit adjusts the shared vehicle supply amount based on the waiting time at the boarding location of the user based on the dispatch request as the predetermined vehicle allocation judgment criterion. The vehicle dispatch management device according to claim 2.
5. When the passenger vehicle supply amount adjustment unit determines that the predicted vehicle demand amount is large relative to the vehicle supply amount, the passenger vehicle supply amount adjustment unit adjusts the passenger vehicle supply amount using the non-rental time during which the vehicle travels to the boarding point as the predetermined judgment criterion. The vehicle dispatch management device according to claim 4.
6. The passenger vehicle supply amount adjustment unit relaxes the predetermined vehicle allocation judgment criterion when it determines that the predicted vehicle demand amount is large relative to the vehicle supply amount. The vehicle dispatch management device according to claim 4.
7. the passenger vehicle supply amount adjustment unit, when determining that the predicted vehicle demand amount is large relative to the vehicle supply amount, limits the supply amount of the dispatchable vehicles indicated by the predetermined vehicle allocation judgment criterion. The vehicle dispatch management device according to claim 4.
8. The shared vehicle supply amount adjustment unit adjusts the shared vehicle supply amount by setting vehicles other than the vehicles in which other users are already riding by the dispatch among the plurality of vehicles as vehicles available for sharing. The vehicle dispatch management device according to claim 2.
9. The passenger vehicle supply adjustment unit increases the passenger vehicle supply when it determines that a state in which the predicted vehicle demand is large relative to the vehicle supply has continued for a certain period of time. The vehicle dispatch management device according to claim 2.
10. The passenger vehicle supply amount adjustment unit increases the passenger vehicle supply amount within the range of the predetermined upper limit value. The vehicle dispatch management device according to claim 3.
11. The shared vehicle supply amount adjustment unit sets the predetermined upper limit value based on a waiting time at the boarding location of the user for the shared vehicle in the first sub-area where the user is located and a waiting time at the boarding location of the user for the shared vehicle in the second sub-area. The vehicle dispatch management device according to claim 10.
12. the vehicle allocation unit, when there is a shortage of the vehicles available for sharing in the first sub-area, allocates the vehicles available for sharing in the second sub-area in which the vehicle supply amount is greater than the predicted vehicle demand amount. The vehicle dispatch management device according to claim 11.
13. the vehicle allocation unit allocates the available vehicles in the first sub-area that are in a predetermined waiting state when the available vehicles in the second sub-area are insufficient. The vehicle dispatch management device according to claim 12.
14. the vehicle allocation unit allocates the available vehicles for sharing to a combination of the users to which the predetermined vehicle allocation judgment criterion exceeds a predetermined suitability. The vehicle dispatch management device according to claim 2.
15. a vehicle allocation adjustment unit that adjusts the allocation of the vehicles available for sharing in the second sub-area to the first sub-area when it is determined that the difference between the predicted vehicle demand and the vehicle supply in the first sub-area is equal to or greater than a predetermined value; The vehicle dispatch management device according to claim 3.
16. The vehicle allocation adjustment unit increases the supply of the vehicles available for sharing that are rearranged as the difference between the predicted vehicle demand and the vehicle supply increases. The vehicle dispatch management device according to claim 15.
17. A vehicle dispatch management method using a vehicle dispatch management device that manages vehicle dispatch in a vehicle dispatch service target area based on a vehicle dispatch request, comprising: acquiring predetermined vehicle information from the vehicle; Calculating a vehicle supply amount, which is a supply amount of vehicles that can be dispatched among the plurality of vehicles, based on the predetermined vehicle information; Calculating a predicted vehicle demand amount, which is a demand amount for the vehicle in a predetermined time period in the future; adjusting a shared vehicle supply amount, which is a supply amount of vehicles available for users to share, based on a relationship between the vehicle supply amount and the predicted vehicle demand amount; and allocating the vehicle to the user who has made the vehicle dispatch request in accordance with a predetermined vehicle allocation criterion; The adjustment of the passenger vehicle supply amount adjusts the passenger vehicle supply amount by changing the predetermined vehicle allocation judgment criterion. Vehicle allocation management methods.
Citation Information
Patent Citations
Vehicle allocation device, and vehicle allocation method
JP2020135314A