Vehicle allocation management device and vehicle allocation management method

The vehicle dispatch management system optimizes vehicle allocation by temporarily suspending luggage-only plans, allowing for combined passenger and cargo dispatch, enhancing efficiency in on-demand services.

JP7782708B2Active Publication Date: 2025-12-09NISSAN MOTOR CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2024544083
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2022-08-31
Filing Date
2023-08-09
Publication Date
2025-12-09
Estimated Expiration
2043-08-09

AI Technical Summary

Technical Problem

Existing on-demand passenger and freight mixed loading systems face inefficiencies in vehicle dispatch and loading due to immediate dispatch of vehicles for luggage requests, leading to passengers having to wait for the next available vehicle.

Method used

A vehicle dispatch management system that temporarily suspends vehicle dispatch plans for luggage requests when no other requests are present, allowing for the creation of combined passenger and cargo plans based on subsequent passenger requests, optimizing vehicle allocation and dispatch.

Benefits of technology

Improves vehicle dispatch and loading efficiency by enabling flexible operation of vehicles capable of carrying both passengers and cargo, ensuring timely and efficient service delivery.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007782708000001
    Figure 0007782708000001
  • Figure 0007782708000002
    Figure 0007782708000002
  • Figure 0007782708000003
    Figure 0007782708000003
Patent Text Reader

Abstract

The present invention is a vehicle dispatch management device that manages an on-demand vehicle dispatch in which a plurality of vehicles that are capable of carrying both passengers and baggage at the same time are used. The device comprises: a vehicle dispatch request acquisition unit that acquires a vehicle dispatch request from a user for either of a passenger vehicle and baggage delivery; a vehicle dispatch plan creation unit that creates a vehicle dispatch plan for one vehicle that is selected from among the plurality of vehicles in response to the acquired vehicle dispatch request; and a vehicle dispatch instruction unit that transmits a vehicle dispatch instruction based on the vehicle dispatch plan to the one vehicle, wherein, when there are no other vehicle dispatch requests at the time when the vehicle dispatch plan creation unit creates the vehicle dispatch plan for the one vehicle in response to a vehicle dispatch request for the baggage delivery, the vehicle dispatch plan creation unit temporarily suspends creation of the vehicle dispatch plan.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a vehicle allocation management technology, and more particularly to a vehicle allocation management device and a vehicle allocation management method for managing on-demand allocation of vehicles capable of carrying both passengers and cargo (luggage). Regarding. [Background technology]

[0002] Mobility services are known as services that provide smooth transportation of passengers and / or luggage by vehicle. In recent years, against the backdrop of a decrease in transportation demand due to population decline and labor shortages, mobility services that simultaneously transport passengers and luggage in a single vehicle have been proposed.

[0003] For example, Patent Document 1 below discloses an on-demand passenger and freight mixed loading system that determines the route of a running vehicle carrying passengers and luggage on the basis of passenger movement requests and luggage movement requests. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6673037 Summary of the Invention [Problem to be solved by the invention]

[0005] In the on-demand passenger and freight mixed loading system disclosed in Patent Document 1, if a vehicle is available in service in response to a request for movement from a vehicle user such as a passenger or a parcel delivery company, the vehicle is immediately dispatched to the user. Therefore, for example, after a vehicle has been dispatched in response to a request for movement of luggage (dispatch request) by a parcel delivery company, even if there is a request for movement from passengers, the passengers will not be loaded onto the vehicle together with their luggage, resulting in a decrease in vehicle dispatch efficiency and / or loading efficiency, and passengers having to wait until the next vehicle becomes available for dispatch.

[0006] Therefore, the present invention has been made in consideration of the above problems, and aims to improve the vehicle dispatch efficiency and / or loading efficiency in an on-demand vehicle dispatch service for vehicles capable of carrying both passengers and cargo (or passengers and cargo). [Means for solving the problem]

[0007] The present invention, which aims to solve the above problems, comprises the following invention-specific matters and technical features.

[0008] According to one aspect, the present invention provides a vehicle dispatch management device that manages on-demand vehicle dispatch using a plurality of vehicles capable of carrying both passengers and luggage. The vehicle dispatch management device includes a vehicle dispatch request acquisition unit that acquires a vehicle dispatch request for either a ride or luggage delivery from a user, a vehicle dispatch plan creation unit that creates a vehicle dispatch plan for one vehicle selected from the plurality of vehicles in response to the acquired vehicle dispatch request, and a vehicle dispatch instruction unit that transmits a vehicle dispatch instruction based on the vehicle dispatch plan to the one vehicle. Furthermore, when the vehicle dispatch plan creation unit creates the vehicle dispatch plan for the one vehicle in response to the luggage delivery dispatch request, if there are no other vehicle dispatch requests, the vehicle dispatch plan creation unit temporarily suspends creation of the vehicle dispatch plan.

[0009] According to another aspect, the present invention provides a vehicle dispatch management method using a vehicle dispatch management device that manages on-demand vehicle dispatch using multiple vehicles capable of carrying both passengers and luggage. The method includes: acquiring a vehicle dispatch request for either a ride or luggage delivery from a user's terminal device; creating a vehicle dispatch plan for one vehicle selected from the multiple vehicles in response to the acquired vehicle dispatch request; and transmitting a dispatch instruction based on the confirmed vehicle dispatch plan to the one vehicle. Creating the vehicle dispatch plan also includes temporarily suspending creation of the vehicle dispatch plan if there are no other vehicle dispatch requests at the time the vehicle dispatch plan is created in response to the luggage delivery dispatch request. [Effects of the Invention]

[0010] According to the present invention, it is possible to improve the vehicle dispatch efficiency and / or loading efficiency in an on-demand vehicle dispatch service for vehicles capable of carrying both passengers and cargo.

[0011] 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 intended to be limiting, and other effects may also be present. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating an example of a vehicle dispatch management system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram showing an example of a functional configuration model of a vehicle dispatch control device according to one embodiment of the present invention. [Figure 3] FIG. 3 is a diagram for explaining derivation of a route pattern in the vehicle dispatch management system according to one embodiment of the present invention. [Figure 4] FIG. 4 is a diagram for explaining various delay limit times in a vehicle dispatch plan by a vehicle dispatch management device according to one embodiment of the present invention. [Figure 5] FIG. 5 is a sequence chart for explaining an outline of a vehicle dispatch service in a vehicle dispatch management system according to one embodiment of the present invention. [Figure 6A] FIG. 6A is a flowchart illustrating an example of a vehicle dispatch management process performed by the vehicle dispatch management device according to one embodiment of the present invention. [Figure 6B] FIG. 6B is a flowchart illustrating an example of a vehicle dispatch management process performed by the vehicle dispatch management device according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the embodiments described below are merely examples, and are not intended to exclude various modifications or applications of techniques not explicitly described below. The present invention can be implemented in various modifications (e.g., combinations of the embodiments) without departing from the spirit of the present invention. Furthermore, in the following description of the drawings, identical or similar parts are denoted by identical or similar reference numerals. The drawings are schematic and do not necessarily correspond to actual dimensions, ratios, etc. Parts in the drawings may have different dimensional relationships or ratios.

[0014] FIG. 1 is a diagram illustrating an example of a vehicle dispatch management system according to an embodiment of the present disclosure. 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 communicatively connected to each other via a communication network N. The vehicle dispatch management system 1 of the present disclosure provides, for example, an on-demand vehicle dispatch service using multiple vehicles V for a certain area. An "on-demand vehicle dispatch service" refers to a service that immediately responds to a vehicle dispatch request from a user and allocates (dispatches) a specific vehicle to the user. In other words, in an on-demand vehicle dispatch service, there is no user-specified vehicle dispatch reservation time. Furthermore, "immediate response" is a concept that not only means dispatching a vehicle immediately in response to a user's vehicle dispatch request, but also includes a certain degree of time that the user would normally tolerate. The vehicle dispatch management system 1 of the present disclosure is based on this "on-demand vehicle dispatch service," and realizes an efficient vehicle dispatch service by adjusting the timing of vehicle dispatch for specific vehicle dispatch requests under predetermined conditions.

[0015] The vehicle dispatch management device 10 is a computing device that comprehensively manages a vehicle dispatch service using multiple vehicles V in a target area. 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 manage data necessary to realize the vehicle dispatch service. The databases 12 include, for example, an operation record database 12a, a cargo information database 12b, a user information database 12c, a map database 12d, a vehicle information database 12e, and a vehicle dispatch plan database 12f (see FIG. 2). In this example, the databases 12 are configured as part of the vehicle dispatch management device 10, but are not limited to this, and all or 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 receives a request for allocation of a vehicle V from a user who desires allocation, creates and confirms a vehicle allocation plan for one vehicle V selectively allocated in response to the vehicle allocation request, and issues a vehicle allocation instruction to the one vehicle V in accordance with the confirmed vehicle allocation plan. The vehicle allocation plan is confirmed, for example, with the user's consent.

[0018] In the present disclosure, types of vehicle dispatch requests include a vehicle dispatch request for a ride from a user who is a passenger (hereinafter referred to as a "ride dispatch request") and a vehicle dispatch request for baggage delivery from a user who is a shipper (baggage delivery business or general user) (hereinafter referred to as a "baggage delivery dispatch request"). In other words, general users who are not baggage delivery business operators can also make a baggage delivery dispatch request to have their baggage delivered. The vehicle dispatch request includes information such as the user name, the type of vehicle dispatch request, departure and arrival points (boarding and disembarking points for passengers, loading and disembarking points for baggage), and transportation details (number of passengers, number, size, and type of baggage for baggage).

[0019] The vehicle dispatch plan includes a route that defines a route from a waiting location (a starting waiting location) for the vehicle V to a waiting location (which may not necessarily be the same as the initial waiting location) that is a terminal location, passing through several points (origin and destinations) along the way for boarding and alighting and / or loading and unloading of luggage. The vehicle dispatch management device 10 temporarily suspends a specific vehicle dispatch plan in accordance with a predetermined suspension condition. An example of a predetermined suspension condition is when no other vehicle dispatch requests have been received at the time a vehicle dispatch plan for a luggage delivery dispatch request is created. Then, the vehicle dispatch management device 10 releases the suspension of the vehicle dispatch plan in accordance with a predetermined release condition, and re-creates a vehicle dispatch plan based on the luggage delivery dispatch request and the passenger dispatch request so as to achieve a so-called mixed cargo and passenger load, proposes it to the user, and confirms it. An example of a predetermined release condition is when a new passenger dispatch request is subsequently received.

[0020] The vehicle V is a vehicle registered in the vehicle information database 12e and available for use by a user. The vehicle V may be any type of vehicle (e.g., sedan, minivan, SUV, etc.), but must be capable of carrying both passengers and freight. The vehicle V may be an electric vehicle (EV) powered by an on-board battery. The vehicle V may also be a self-driving vehicle capable of fully autonomous driving, regardless of the level of automation. The vehicle V is equipped with a control device 300 that controls the vehicle V itself or its onboard equipment (e.g., a navigation device) in accordance with instructions from the vehicle dispatch management device 10 (see FIG. 2). The control device 300 acquires location information of the vehicle V via, for example, a GPS system and transmits it to the vehicle dispatch management device 10. The control device 300 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 300 includes, for example, a navigation function that presents a driving route according to a vehicle dispatch plan, and, in the case of a fully autonomous vehicle, an autonomous driving control function that controls the vehicle V along the driving route.

[0021] The terminal device 20 is a computing device that allows a user, such as a passenger seeking a ride or a parcel delivery company, to make a vehicle dispatch request by operating a user interface. The terminal device 20 is, for example, a smartphone, a pad computer, a laptop personal computer, a desktop computer, or the like, but is not limited to these. The terminal device 20 implements, for example, a vehicle dispatch management client program (a so-called vehicle dispatch app). The terminal device 20 executes the vehicle dispatch app under the control of a processor, thereby enabling the user to use the vehicle dispatch service of the vehicle dispatch management device 10. For example, a 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, in response, accept the vehicle dispatch plan created by the vehicle dispatch management device 10 to make a ride reservation for a vehicle V or a parcel delivery reservation.

[0022] In this way, the vehicle dispatch management system 1 of the present disclosure temporarily puts a dispatch plan based on a dispatch request for package delivery on hold in accordance with predetermined hold conditions, thereby enabling efficient operation of the vehicle V. In particular, the temporarily put on hold dispatch plan is recreated in conjunction with a subsequent new dispatch request, thereby improving the dispatch efficiency and / or loading rate of the vehicle V. Furthermore, the created dispatch plan is proposed to the user, and if the user accepts it, the dispatch plan is finalized, allowing for flexible operation of the vehicle V in response to various dispatch requests and improving dispatch efficiency.

[0023] FIG. 2 is a block diagram illustrating 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 is configured as a functional configuration model including functional components such as a front-end processing unit 110, a demand information acquisition unit 120, a vehicle dispatch request acquisition unit 130, a departure / arrival location determination unit 140, a vehicle dispatch plan creation unit 150, a driving route planning unit 160, and a vehicle communication interface unit 170. As described above, the vehicle dispatch management device 10 also includes various databases 12. This 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 merely an example, and all or part of the functions of a certain functional component may be realized by other functional components. For ease of explanation, the figure also illustrates the configuration of a terminal device 20 serving as a terminal device for a parcel delivery company and a general user, and a portion of the configuration of a control device 300 in a vehicle V.

[0024] The operation history database 12a stores, for example, information (operation history information) relating to past operation history for each vehicle V. The operation history information includes, for example, various specification information such as operation times (operation start times and end times), operation routes, and travel distances for each vehicle V. The operation history information may indicate the demand history for the vehicle V in a certain time period and / or in a certain area based on the operation times for each vehicle V.

[0025] The package information database 12b stores information related to package delivery (package information). The package information includes, for example, the name of the package delivery company, business attributes, delivery base, package ID, package delivery status, customer information, and the like.

[0026] The user information database 12c stores user information about users who use the ride-hailing service. The user information includes, for example, a user ID and password, personal attributes, and information about service usage. The user information is registered in the user information database 12c under the control of the ride-hailing management device 10, for example, when the user inputs predetermined information when the ride-hailing app is first launched. In addition, in the present disclosure, the user information may include the user's own specific behavioral history. The specific behavioral history may include, for example, the user's purchase history in the area covered by the ride-hailing service. Such behavioral history may be used by the demand information acquisition unit 120 to predict, for example, whether the user is likely to request a ride-hailing service shortly after making a purchase.

[0027] The map database 12d stores map data for at least the area covered by the vehicle dispatch service. The map data includes, for example, information on addresses, place names, roads, and facility names. The map data may also include information necessary for route search and environmental information such as road congestion conditions. The map data may be known data, or may be, for example, an external map database connectable via an API.

[0028] The vehicle information database 12e stores information (vehicle information) about the vehicle V available 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 occupants / maximum load capacity, etc.), current vehicle dispatch plan, current location, and current status (service status, remaining battery capacity, number of occupants, load capacity, etc.). The current location of the vehicle V is updated as needed based on location information transmitted from the vehicle V, as will be described later.

[0029] The vehicle dispatch plan database 12f stores a vehicle dispatch plan for each vehicle V based on a dispatch request. The vehicle dispatch plan includes a route from a waiting location as a starting point to a waiting location as a final point via several points. Each vehicle dispatch plan is also associated with status information, such as whether it is in a temporarily suspended state or a confirmed state.

[0030] The front-end processing unit 110 performs various processes with the user's terminal device 20. As one example, the front-end processing unit 110 refers to the user information database 12c and performs login authentication processing in response to a login request from a vehicle dispatching app on the user's terminal device 20. As another example, the front-end processing unit 110 accepts a vehicle dispatch request from the vehicle dispatching app on the user's terminal device 20, passes the request to the vehicle dispatch request acquisition unit 130, and interacts with the terminal device 20 to receive the user's approval or disapproval of the vehicle dispatch plan created by the vehicle dispatch plan creation unit 150 in response to the request. As yet another example, the front-end processing unit 110 acquires a user's behavior history transmitted from the user's terminal device 20 and stores the history in the user information database 12c. The user's behavior history can be used to predict future demand.

[0031] The demand information acquisition unit 120 acquires, at a predetermined timing, demand information indicating the current and / or future demand of the vehicle V. The demand information acquisition unit 120 includes, for example, a current demand calculation unit 121 that calculates the current demand of the vehicle V, and a demand prediction unit 122 that predicts the future demand. In the present disclosure, by using the demand information acquired by the demand information acquisition unit 120, it becomes possible to optimize the vehicle dispatch plan.

[0032] The current demand calculation unit 121 refers to the vehicle dispatch plan database 12f, calculates the current demand based on the number of waiting vehicles V (number of waiting vehicles) that are not currently assigned to any vehicle dispatch plan, and outputs this as demand information.

[0033] The demand forecasting unit 122, for example, refers to the operation performance database 12a, predicts future demand for vehicles V based on past operation performance information, etc., and outputs this as demand information. As an example, the future demand may be the number of vehicles V that are expected to be in demand at a specific time or time period, such as 10 minutes, 20 minutes, 30 minutes, or 1 hour after a reference time (e.g., the current time). As another example, the future demand may take into account the number of vehicles V predicted based on the user's behavioral history. That is, if a user without transportation goes shopping at a shopping mall or the like in the target area, the user may request a ride. Therefore, the demand forecasting unit 122 counts this as the number of vehicles V that are expected to be in demand based on such behavioral history. As yet another example, the demand forecasting unit 122 may predict future demand by taking into account, in addition to operation performance information, for example, temporal and seasonal factors and environmental factors such as the holding of an event. The demand forecasting unit 122 may include a demand forecasting model that has been subjected to machine learning according to a predetermined machine learning algorithm, with, for example, operation record information or the like as explanatory variables and predicted demand as a target variable. In this way, the demand forecasting unit 122 can create an optimal vehicle plan by predicting future demand, thereby enabling efficient operation of the vehicle V.

[0034] The vehicle allocation request acquisition unit 130 receives and acquires a vehicle allocation request from a user via the front-end processing unit 110. The time when the vehicle allocation request acquisition unit 130 receives the vehicle allocation request is the start time of counting the holding limit time, which will be described later. As described above, in the present disclosure, vehicle allocation requests from users are classified into a vehicle allocation request for a ride and a vehicle allocation request for baggage delivery. The vehicle allocation request acquisition unit 130 passes the acquired vehicle allocation request to each of the departure / arrival point determination unit 140 and the vehicle allocation plan creation unit 150.

[0035] The departure and arrival point determination unit 140 refers to the map database 12d based on the dispatch request and determines departure and arrival points shown on the map where the user can actually get on and off. That is, the departure and arrival point determination unit 140 refers to the map database 12d for the departure and arrival points indicated in the dispatch request and generates departure and arrival point information indicating geographical positions on the travel route where the user can actually get on and off or where luggage can be loaded and unloaded. The departure and arrival point determination unit 140 passes the generated departure and arrival point information to the dispatch plan creation unit 150.

[0036] The vehicle allocation plan creation unit 150 creates and confirms a vehicle allocation plan for one vehicle V selected from multiple candidate vehicles (candidate vehicles) V based on the allocation request and the departure and arrival point information, and issues a vehicle allocation instruction to the one vehicle V in accordance with the confirmed vehicle allocation plan. In the present disclosure, when creating a vehicle allocation plan for a vehicle allocation request for baggage delivery, if no other vehicle allocation requests have been accepted, the vehicle allocation plan creation unit 150 temporarily suspends the vehicle allocation plan for the vehicle allocation request for baggage delivery. Then, if the vehicle allocation plan creation unit 150 accepts, for example, a new vehicle allocation request for a passenger while the vehicle allocation plan is suspended, the vehicle allocation plan creation unit 150 releases the suspension of the vehicle allocation plan and updates or regenerates the vehicle allocation plan based on the baggage delivery allocation request and the passenger allocation request so as to achieve a so-called mixed cargo and passenger load, and proposes and confirms the plan to the user. In this way, since the vehicle allocation plan is proposed to the user before being confirmed, the user can determine whether the proposed vehicle allocation plan meets their wishes. The vehicle allocation plan creating unit 150 stores the determined vehicle allocation plan in the vehicle allocation plan database 12f, and notifies the vehicle allocation instruction unit 172 to instruct the vehicle V to allocate the vehicle.

[0037] More specifically, the vehicle allocation plan creation unit 150 first requests the driving route planning unit 160 to derive a route pattern in accordance with the acquired vehicle allocation request. The route pattern indicates a route that passes through all of the determined origins and destinations (waypoints) when a new origin and destination is added to a route that passes through all of the determined origins and destinations. The route pattern may include a route pattern based on a vehicle allocation plan for a mixed cargo and passenger load based on a vehicle allocation request for a passenger ride and a vehicle allocation request for a baggage delivery. In response to the request for deriving a route pattern, the driving route planning unit 160 refers to the map database 12d and the vehicle information database 12e to extract one or more vehicles V that can meet the vehicle allocation request as candidate vehicles v, derive a route pattern for each of the extracted candidate vehicles v according to the origin and destination information, and transfers the derived route pattern to the vehicle allocation plan creation unit 150.

[0038] For example, as shown in FIG. 3, candidate vehicles v(1) to v(3) are extracted from the geographical relationship between the boarding location Req_PU and the disembarking location Req_DO based on the dispatch request. Candidate vehicle v(1) is a vehicle for which a route passing through points P(0) to P(1) to P(2) has already been set. Candidate vehicle v(2) is a vehicle waiting at waiting location S. Candidate vehicle v(3) is a vehicle for which a route passing through points P(0) to P(1) has already been set. Looking at candidate vehicle v(1), there are a total of six patterns (route patterns) in which the boarding location Req_PU and the disembarking location Req_DO are added to points P(0) to P(2). Similarly, the route patterns for candidate vehicles v(2) and v(3) are one pattern and three patterns, respectively.

[0039] Returning to FIG. 2, the vehicle allocation plan creation unit 150 next attempts to create a vehicle allocation plan based on each route pattern of the candidate vehicle v derived by the travel route planning unit 160. The vehicle allocation plan includes a travel route that adds a waiting location as a starting point and a waiting location as an end point to the route pattern. The vehicle allocation plan creation unit 150 narrows down the vehicle allocation plans by deleting or excluding any vehicle allocation plans that meet predetermined exclusion conditions from the created vehicle allocation plans. Examples of the predetermined exclusion conditions include, but are not limited to, the following (i) to (iv). (i) Passenger and / or luggage capacity requirements If the number of passengers and / or the amount of luggage loaded by a new trip request exceeds the specified number of passengers and / or the specified amount of luggage loaded, the trip plan is rejected. (ii) Conditions regarding the time limit for delay when boarding or loading If the boarding time and / or luggage loading time of the relevant user (user who has confirmed the reservation of vehicle V) exceeds the delay limit time due to the new dispatch request, the dispatch plan is excluded. (iii) Conditions regarding the time limit for delay when disembarking or unloading If the drop-off time of the associated user and / or the drop-off time of the luggage exceeds the delay limit time due to the new dispatch request, the dispatch plan is excluded. (iv) Conditions regarding the delivery delay limit time for the user who made a new delivery request and / or the luggage If the boarding time and / or luggage loading time of a user who has made a new vehicle dispatch request exceeds the vehicle dispatch delay limit time, the vehicle dispatch plan is excluded.

[0040] Here, the various delay limit times in the vehicle dispatch plan will be explained. Fig. 4 is a diagram for explaining various delay limit times in the vehicle dispatch plan by the vehicle dispatch management device according to one embodiment of the present invention.

[0041] As shown in the figure, the scheduled travel time T_Tra according to the dispatch plan of a certain vehicle V based on a dispatch request refers to the time from the dispatch request acceptance time T_Req to the scheduled disembarkation time (scheduled loading / unloading time) T_DO. The dispatch delay limit time refers to the time from the dispatch request acceptance time T_Req to the scheduled boarding time (scheduled loading / unloading time) T_PU. The boarding delay limit time (loading delay limit time) refers to the time from the scheduled boarding time T_PU to the boarding limit time TL_PU. The disembarking delay limit time (loading / unloading delay limit time) refers to the time from the scheduled departure time T_Dep to the disembarking limit time (loading / unloading delay limit time) TL_DO, and is set to, for example, 1.2 times the time it would take if vehicle V were to travel directly from the boarding point (loading point) to the disembarking point (loading / unloading point). In the figure, the hold limit time is the time allowed for temporary suspension of the dispatch plan, and is measured from the dispatch request acceptance time. The hold limit time is an example of a predetermined release condition.

[0042] As one example, when the vehicle dispatch plan creation unit 150 determines that the addition of a boarding location Req_PU to a vehicle dispatch plan based on a certain route pattern will cause the boarding time of a related user to exceed the boarding delay limit time, the vehicle dispatch plan creation unit 150 excludes the vehicle dispatch plan (exclusion condition (ii)). As another example, when the vehicle dispatch plan creation unit 150 determines that the addition of a boarding location Req_PU and a disembarking location Req_DO to a vehicle dispatch plan based on a certain route pattern will cause the disembarking time of a related user to exceed the delay limit time, the vehicle dispatch plan creation unit 150 excludes the vehicle dispatch plan (exclusion condition (iii)).

[0043] Returning to FIG. 2 , the vehicle allocation plan creation unit 150 then calculates evaluation values ​​for the narrowed-down vehicle allocation plans according to a predetermined evaluation function and selects an optimal vehicle allocation plan according to the calculated evaluation value. The predetermined evaluation function is a function defined such that, for a vehicle allocation request for boarding, the shorter the ride time from the boarding time to the disembarking time, the higher the evaluation value; and, for a vehicle allocation request for baggage delivery, the lower the travel cost based on the travel distance, the higher the evaluation value. In this case, the vehicle allocation plan creation unit 150 selects the vehicle allocation plan with the highest evaluation value. The selected vehicle allocation plan is a provisional (tentative) vehicle allocation plan. A provisional vehicle allocation plan is an unconfirmed vehicle allocation plan that may still be modified or canceled. In the case of a vehicle allocation plan for mixed cargo and passenger transport, the vehicle allocation plan creation unit 150 selects the vehicle allocation plan with the highest evaluation value according to the evaluation function. In this way, by using the evaluation function, the optimal vehicle allocation plan can be selected from multiple vehicle allocation plans. In particular, in the present disclosure, different evaluation functions are used for vehicle dispatch requests for rides and vehicle dispatch requests for baggage delivery, so that a vehicle dispatch plan that is more suited to the transportation content can be selected.

[0044] In the present disclosure, when the vehicle dispatch plan creation unit 150 determines that the vehicle dispatch plan has been created based only on a dispatch request for baggage delivery, the vehicle dispatch plan creation unit 150 may temporarily suspend the creation of the vehicle dispatch plan. The vehicle dispatch management device 10 temporarily stores the suspended vehicle dispatch plan in the vehicle dispatch plan database 12f. Then, if the vehicle dispatch plan creation unit 150 receives, for example, a new dispatch request while the vehicle dispatch plan is suspended, the vehicle dispatch plan creation unit 150 releases the suspension of the vehicle dispatch plan, derives a new route pattern based on the baggage delivery dispatch request and the passenger dispatch request, and re-creates and confirms the vehicle dispatch plan so as to carry so-called mixed cargo and passenger loads.

[0045] Furthermore, the vehicle allocation plan creation unit 150 may temporarily suspend the creation of a vehicle allocation plan based on a vehicle allocation request for parcel delivery, and then release the suspension, in accordance with suspension conditions and release conditions that depend on demand. As an example, the vehicle allocation plan creation unit 150 temporarily suspends the creation of the vehicle allocation plan when the future demand volume predicted by the demand forecasting unit 122 exceeds a first upper limit value. In other words, when a certain degree of future demand for vehicles V is expected, the vehicle allocation plan creation unit 150 temporarily suspends the creation of a vehicle allocation plan in preparation for future vehicle allocation requests. This makes it possible to avoid delivering individual parcels as much as possible, and enables efficient operation of vehicles V taking future demand volume into consideration.

[0046] As another example, the vehicle allocation plan creation unit 150 temporarily suspends the creation of a vehicle allocation plan when the ratio of the future demand volume predicted by the demand prediction unit 122 to the current demand volume calculated by the current demand calculation unit 121 exceeds a predetermined rate of change. In other words, when an increasing trend in future demand for vehicle V is expected, the vehicle allocation plan creation unit 150 temporarily suspends the creation of a vehicle allocation plan in preparation for future vehicle allocation requests. This makes it possible to avoid delivery of individual packages as much as possible, and enables efficient operation of vehicle V in response to a sudden increase in future demand volume.

[0047] As another example, when the current demand calculated by the current demand calculation unit 121 exceeds the second upper limit, the vehicle allocation plan creation unit 150 does not put the vehicle allocation plan on hold or releases the hold on the vehicle allocation plan. In other words, when the current demand is high, the vehicle allocation plan creation unit 150 releases the hold on the vehicle allocation plan to prevent demand from being missed. This makes it possible to maintain a high utilization rate of the vehicle V and to operate the vehicle V efficiently.

[0048] As yet another example, the vehicle allocation plan creation unit 150 may finalize the creation of a vehicle allocation plan without suspending it if the number of parcels indicated in the parcel delivery dispatch request is equal to or greater than a predetermined limit for the number of parcels to be held. In this case, the vehicle allocation plan creation unit 150 may also decrease the value of the predetermined limit for the number of parcels to be held if the ratio of the future demand volume predicted by the demand forecasting unit 122 to the current demand volume calculated by the current demand calculation unit 121 exceeds a predetermined rate of change. In this way, since it is determined whether the number of parcels indicated in the parcel delivery dispatch request is equal to or greater than the predetermined limit for the number of parcels to be held, it is possible to create a vehicle allocation plan that takes into account the loading rate of the vehicle V. Furthermore, if future demand for the vehicle V is expected to increase, it is possible to deliver as many of the held parcels as possible to prepare for future demand.

[0049] The vehicle dispatch plan creation unit 150 may arbitrarily set a holding time limit for a vehicle dispatch request for parcel delivery. As an example, the vehicle dispatch plan creation unit 150 may set the holding time limit according to attribute information of a user who has made a vehicle dispatch request for parcel delivery. More specifically, if the user who has made the vehicle dispatch request for parcel delivery is a general user, the holding time limit is set to a relatively short first holding time limit, whereas if the user is a parcel delivery company, the holding time limit is set to a second first holding time limit that is longer than the first holding time limit. In other words, by setting a shorter holding time limit for a one-off vehicle dispatch request for parcel delivery made by a general user, while allowing parcel delivery companies to hold the vehicle dispatch plan to a certain extent, general users' satisfaction with the vehicle dispatch service can be improved, and further activation of the vehicle dispatch service can be expected.

[0050] As another example, the vehicle dispatch plan creation unit 150 may set the holding time limit according to the luggage attribute information indicated in the luggage delivery request. More specifically, if the luggage is a refrigerated item or a perishable food item, etc., and there is a risk that a delay or postponement of the delivery date will reduce the value of the luggage, the holding time limit is set as a relatively short first holding time limit. In other words, by setting a shorter holding time limit for luggage delivery requests for perishable food items, etc., it becomes possible to accommodate delivery services for luggage that must be delivered quickly within a short period of time.

[0051] As yet another example, the vehicle dispatch plan creation unit 150 may set a holding limit time according to loading location information indicated in a vehicle dispatch request for parcel delivery. More specifically, if the loading location of the parcel is the home of a general user, the holding limit time is set to a first holding limit time, whereas if the loading location of the parcel is the business premises of a parcel delivery company, the holding limit time is set to a second holding limit time that is longer than the first holding limit time. In other words, by setting a shorter holding limit time for a one-off parcel delivery vehicle request from a general user, while allowing the parcel delivery company to postpone the vehicle dispatch plan to a certain extent, general users' satisfaction with the vehicle dispatch service can be improved, and further activity of the vehicle dispatch service can be expected.

[0052] The vehicle communication interface unit 170 exchanges various types of information with the vehicle V via the communication network N. For example, the vehicle communication interface unit 170 includes a vehicle information acquisition unit 171 that acquires vehicle information including location information of the vehicle V, and a vehicle allocation instruction unit 172 that instructs the vehicle V to move according to a vehicle allocation plan.

[0053] The vehicle information acquisition unit 171 communicates with the communication unit 310 of the control device 300 and acquires the location information acquired by the location information acquisition unit 320. Furthermore, the vehicle allocation instruction unit 172 refers to the vehicle allocation plan database 12f in accordance with instructions from the vehicle allocation plan creation unit 150, identifies a corresponding vehicle allocation plan, and transmits driving instructions to the vehicle V in accordance with the identified vehicle allocation plan. The control device 300 of the vehicle V that has received the driving instructions uses a navigation function to display a driving route in accordance with the vehicle allocation plan on, for example, a user interface (indicated as "UI" in the figure) 330.

[0054] FIG. 5 is a sequence chart for explaining an outline of a vehicle dispatch service in a vehicle dispatch management system according to one embodiment of the present invention.

[0055] First, the vehicle V transmits its own location information acquired from the GPS system to the vehicle dispatch management device 10 at a predetermined timing (S501). The vehicle V acquires and transmits the location information periodically or in response to a transmission request from the vehicle dispatch management device 10. As a result, the vehicle dispatch management device 10 acquires the location information transmitted from the vehicle V (S502).

[0056] Meanwhile, a user who wishes to use a vehicle dispatch service executes a vehicle dispatch app implemented in the terminal device 20 and inputs the necessary information for the vehicle dispatch request on a vehicle dispatch request screen displayed on the user interface, and the terminal device 20 then transmits the vehicle dispatch request to the vehicle dispatch management device 10 (S503). For example, a user who wishes to board a vehicle inputs the boarding and disembarking locations, the number of passengers, etc. A user who wishes to have luggage delivered inputs the loading and disembarking locations, the number, size, and type of luggage, etc. The boarding and disembarking locations (loading and disembarking locations) can be selected, for example, from a geographical map displayed by the vehicle dispatch app. The boarding location (loading location) may also be the current location obtained, for example, by a GPS function installed in the user's smartphone.

[0057] When the vehicle dispatch management device 10 receives a vehicle dispatch request from the terminal device 20 (S504), it creates a vehicle dispatch plan for vehicle V based on the received vehicle dispatch request, and transmits the contents of the created vehicle dispatch plan to the terminal device 20 to propose it to the user (S505). Note that when the received vehicle dispatch request is a vehicle dispatch request for baggage delivery, if no other vehicle dispatch requests have been received at the time the vehicle dispatch management device 10 creates a vehicle dispatch plan based on the vehicle dispatch request for baggage delivery, the vehicle dispatch management device 10 temporarily suspends the creation of the vehicle dispatch plan for vehicle V based on the vehicle dispatch request for baggage delivery, and releases the suspension under predetermined conditions, and updates or re-creates the vehicle dispatch plan as necessary.

[0058] When the terminal device 20 receives the contents of the vehicle allocation plan, it displays it on the user interface as a vehicle allocation plan proposal screen and prompts the user to accept or reject (accept or reject) the proposed vehicle allocation plan (S506). When the user inputs acceptance or rejection on the vehicle allocation plan proposal screen, the terminal device 20 receives this and transmits an acceptance or rejection notice to the vehicle allocation management device 10 (S507), and the vehicle allocation management device 10 receives the acceptance or rejection notice transmitted from the terminal device 20 (S508). For example, if the acceptance or rejection notice indicates acceptance of the vehicle allocation plan, the vehicle allocation management device 10 confirms the vehicle allocation plan for vehicle V in accordance with the vehicle allocation plan, transmits a confirmation notice of the vehicle allocation reservation to the terminal device 20, and transmits a vehicle allocation instruction in accordance with the vehicle allocation plan to vehicle V (S509).

[0059] When the terminal device 20 receives the notification of confirmation of the vehicle dispatch reservation, it displays this on the user interface to notify the user that the vehicle dispatch reservation has been confirmed (S510). Meanwhile, when the vehicle V receives the dispatch instruction, it displays, for example, on a navigation screen, a driving route according to the dispatch plan indicated in the dispatch instruction to navigate the driver (S511). This enables the driver to operate the vehicle V on an on-demand basis in response to the user's dispatch request.

[0060] 6A and 6B are flowcharts illustrating an example of a vehicle dispatch management process performed by a vehicle dispatch management device according to an embodiment of the present invention. This process is realized by the vehicle dispatch management device executing a vehicle dispatch management server program under the control of a processor, in cooperation with various hardware resources.

[0061] As shown in FIG. 1A, the vehicle dispatch management device 10 waits until a new vehicle dispatch request is received from a user (S601). Meanwhile, for example, a user who wishes to ride or have luggage delivered operates a vehicle dispatch app on the user interface of the terminal device 20 to input a vehicle dispatch request. When a vehicle dispatch request is received from the user (Yes in S601), the vehicle dispatch management device 10 refers to the map database 12d based on the vehicle dispatch request and determines the departure and arrival points (S602).

[0062] Next, the vehicle dispatch management device 10 extracts one or more candidate vehicles v according to the departure and arrival points (S603). For example, the vehicle dispatch management device 10 extracts a vehicle V that is waiting or moving near the departure point as a candidate vehicle v.

[0063] Next, the vehicle dispatch management device 10 derives a route pattern for each extracted candidate vehicle v by referring to the map database 12d (S604). As described above, the route pattern indicates a route that passes through all of the determined departure and arrival points (waypoints) when a new departure and arrival point is added to a route that passes through all of the determined departure and arrival points. Next, the vehicle dispatch management device 10 creates a vehicle dispatch plan based on the derived route pattern (S605). The vehicle dispatch plan includes a driving route that adds a waiting location that serves as a starting point and a waiting location that serves as an end point to the route pattern.

[0064] Next, the vehicle dispatch management device 10 narrows down the vehicle dispatch plans by excluding any vehicle dispatch plans that do not meet predetermined exclusion conditions from the created vehicle dispatch plans (S606). For example, if the ride time of a user who has made a new vehicle dispatch request exceeds the vehicle dispatch delay limit time, the vehicle dispatch management device 10 excludes the vehicle dispatch plan.

[0065] Next, the vehicle dispatch management device 10 calculates an evaluation value for the narrowed-down vehicle dispatch plans according to a predetermined evaluation function, and selects one vehicle dispatch plan with the largest calculated evaluation value (S607). If there are vehicle dispatch plans for mixed cargo and passenger transport, the vehicle dispatch plan creation unit 150 selects the one with the largest evaluation value according to the evaluation function from among them.

[0066] The vehicle dispatch management device 10 then refers to the vehicle dispatch plan database 12f and determines whether or not there is a vehicle dispatch plan that is temporarily on hold (S608). In the present disclosure, a held vehicle dispatch plan is a vehicle dispatch plan based on a vehicle dispatch request for a single parcel delivery. If the vehicle dispatch management device 10 determines that there is no vehicle dispatch plan that is temporarily on hold (No in S608), the vehicle dispatch management device 10 then determines whether or not the current vehicle dispatch request is a parcel dispatch request (S609). On the other hand, if the vehicle dispatch management device 10 determines that there is a vehicle dispatch plan that is temporarily on hold (Yes in S608), as will be described later, the vehicle dispatch management device 10 updates or re-creates the vehicle dispatch plan based on the vehicle dispatch plan based on the current vehicle dispatch request and the held vehicle dispatch plan (S620).

[0067] When the vehicle dispatch management device 10 determines that the current vehicle dispatch request is not a cargo dispatch request (No in S609), the vehicle dispatch management device 10 subsequently determines whether the vehicle dispatch plan is a mixed cargo and passenger load (S610). In other words, when the vehicle dispatch plan is re-created (S620), there is a possibility that it is a mixed cargo and passenger load.

[0068] When the vehicle dispatch management device 10 determines that the current vehicle dispatch plan is a mixed cargo and passenger load (Yes in S610), the vehicle dispatch management device 10 proposes the contents of the vehicle dispatch plan to the user (S612 in FIG. 6B). That is, the vehicle dispatch management device 10 transmits the contents of the created current vehicle dispatch plan to the terminal device 20, and in response, the terminal device 20 displays the contents on the user interface and prompts the user to accept or reject the vehicle dispatch plan.

[0069] On the other hand, if the vehicle dispatch management device 10 determines that the current vehicle dispatch request is a request for dispatching luggage (Yes in S609), the vehicle dispatch management device 10 further determines whether the number of luggage pieces indicated in the vehicle dispatch request is equal to or greater than a predetermined limit for the number of luggage pieces that can be held (S611). If the vehicle dispatch management device 10 determines that the number of luggage pieces indicated in the vehicle dispatch request is equal to or greater than the predetermined limit for the number of luggage pieces that can be held (Yes in S611), the vehicle dispatch management device 10 proposes the contents of the vehicle dispatch plan to the user (S612). In this way, since it is determined whether the number of luggage pieces indicated in the luggage delivery dispatch request is equal to or greater than the predetermined limit for the number of luggage pieces, a vehicle dispatch plan that takes into account the loading rate of the vehicle V becomes possible. Note that if the size of each luggage piece is small, even if there is a large number of pieces, the capacity (volume) is small, and the loading rate remains low even when the luggage pieces are loaded onto the vehicle V. Therefore, the vehicle dispatch management device 10 may determine whether the luggage is equal to or larger than a predetermined size, instead of or in addition to the determination based on the number of luggage indicated in the vehicle dispatch request.

[0070] The vehicle dispatch management device 10 determines whether or not consent has been received from the user for the proposed vehicle dispatch plan (S613). If consent has been received from the user for the proposed vehicle dispatch plan (Yes in S613), the vehicle dispatch management device 10 confirms the current vehicle dispatch plan (S614). The vehicle dispatch management device 10 stores the confirmed vehicle dispatch plan in the vehicle dispatch plan database 12f. Subsequently, the vehicle dispatch management device 10 transmits a notification of confirmation of the vehicle dispatch reservation to the terminal device 20, and transmits a dispatch instruction based on the vehicle dispatch plan to the vehicle V (S615).

[0071] On the other hand, if the vehicle dispatch management device 10 receives a non-acceptance (rejection) from the user in response to the proposed vehicle dispatch plan (No in S613), it cancels the current vehicle dispatch plan based on the user's vehicle dispatch request (S616). In this case, the vehicle dispatch management device 10 returns the temporarily held vehicle dispatch plan that was used to recreate the vehicle dispatch plan to the original held vehicle dispatch plan. If the user desires a different vehicle dispatch service, the user will make a new vehicle dispatch request.

[0072] On the other hand, if the vehicle dispatch management device 10 determines that the number of pieces of luggage in the dispatch request is not equal to or greater than the predetermined limit number of reserved luggage (No in S611), or if it determines that the current dispatch plan is not a mixed cargo / passenger load (No in S610), the vehicle dispatch management device 10 determines whether the elapsed time since the pending dispatch plan exceeded the limit time (S617 in FIG. 6B). This is to prevent further delays in luggage delivery if the current dispatch plan exceeds the limit time since the dispatch request for luggage delivery was accepted.

[0073] When the vehicle dispatch management device 10 determines that the elapsed time of the hold of the reserved vehicle dispatch plan has exceeded the hold limit time (Yes in S617), it proposes the content of the current vehicle dispatch plan to the user (S612), as described above. In other words, when the vehicle dispatch management device 10 determines that the elapsed time of the hold of the vehicle dispatch plan recreated based on the reserved vehicle dispatch plan has exceeded the hold limit time, it releases the hold of the vehicle dispatch plan. In this way, when the elapsed time of the hold of the reserved vehicle dispatch plan has exceeded the hold limit time, the hold of the vehicle dispatch plan is released, so that it is possible to prevent the user's waiting time for a vehicle dispatch request from being longer than necessary.

[0074] On the other hand, if the vehicle dispatch management device 10 determines that the elapsed hold time of the vehicle dispatch plan does not exceed the hold limit time (No in S617), the vehicle dispatch management device 10 then determines whether the vehicle dispatch plan satisfies a hold condition that depends on demand (S618). As an example, the vehicle dispatch management device 10 determines that the vehicle dispatch plan satisfies the hold condition when the predicted future demand amount exceeds a first upper limit value (Yes in S618). As another example, the vehicle dispatch management device 10 determines that the vehicle dispatch plan does not satisfy the hold condition when the current demand amount is below a predetermined lower limit value (No in S618).

[0075] When the vehicle dispatch management device 10 determines that the vehicle dispatch plan does not satisfy the suspension condition (No in S618), the vehicle dispatch management device 10 proposes the contents of the current vehicle dispatch plan to the user (S612), as described above. On the other hand, when the vehicle dispatch management device 10 determines that the vehicle dispatch plan satisfies the suspension condition (Yes in S618), it decides to suspend the current vehicle dispatch plan (S619). The vehicle dispatch management device 10 stores the vehicle dispatch plan for which suspension has been decided in the vehicle dispatch plan database 12f. The suspended vehicle dispatch plan is referred to when the next vehicle dispatch request is made.

[0076] Returning to FIG. 6A, when the vehicle dispatch management device 10 determines that there is a pending vehicle dispatch plan (Yes in S608), the vehicle dispatch management device 10 recreates the vehicle dispatch plan based on the current vehicle dispatch plan and the pending vehicle dispatch plan (S620). For example, when there is a request for dispatching a new passenger, the vehicle dispatch management device 10 recreates the vehicle dispatch plan so that both passengers and freight are loaded. This increases the loading rate of the vehicle V, enabling efficient operation.

[0077] That is, the vehicle allocation plan re-creation process is performed by the vehicle allocation management device 10 executing the processes corresponding to the processes from S603 to S607 based on the vehicle allocation plan based on the current vehicle allocation request and the pending vehicle allocation plan.

[0078] More specifically, the vehicle dispatch management device 10 extracts candidate vehicles v based on the departure and arrival points indicated in the vehicle dispatch plan based on the current vehicle dispatch request and the departure and arrival points indicated in the pending vehicle dispatch plan (processing corresponding to S603). Subsequently, the vehicle dispatch management device 10 derives a route pattern for each extracted candidate vehicle v (processing corresponding to S604). Next, the vehicle dispatch management device 10 regenerates a vehicle dispatch plan based on the derived route pattern (processing corresponding to S605). Subsequently, the vehicle dispatch management device 10 excludes, from the regenerated vehicle dispatch plans, vehicle dispatch plans that do not meet predetermined exclusion conditions, thereby narrowing down the operation routes (processing corresponding to S606). Then, the vehicle dispatch management device 10 calculates evaluation values ​​for the narrowed-down vehicle dispatch plans according to a predetermined evaluation function, and selects the vehicle dispatch plan with the largest calculated evaluation value (processing corresponding to S607).

[0079] When the vehicle allocation management device 10 selects one vehicle allocation plan, it determines whether or not the current vehicle allocation request is a cargo allocation request (S609), as described above, and similarly performs the subsequent processes.

[0080] In the above example, the vehicle dispatch management device 10 determines whether or not there is a vehicle dispatch plan on hold (S608) in response to acquisition of a vehicle dispatch request from a user (S601), but this is not limited to this. Although not shown, even when no vehicle dispatch request is acquired, the vehicle dispatch management device 10 may determine whether or not the elapsed time of the hold of the vehicle dispatch plan has exceeded the hold limit time, and if it determines that the hold elapsed time has exceeded the hold limit time, may release the hold of the vehicle dispatch plan and propose it to the user.

[0081] As described above, according to this embodiment, a vehicle dispatch plan based on a package delivery dispatch request is temporarily suspended under predetermined conditions, thereby enabling efficient operation of vehicle V. In particular, the temporarily suspended vehicle dispatch plan is recreated together with a vehicle dispatch plan based on a subsequent dispatch request, thereby improving the dispatch efficiency and / or loading rate of vehicle V. Furthermore, the created vehicle dispatch plan is proposed to the user, and if the user accepts it, the vehicle dispatch plan is finalized, allowing vehicle V to be flexibly operated in response to various dispatch requests, thereby improving the dispatch efficiency and / or loading rate.

[0082] 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.

[0083] For example, 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.

[0084] Furthermore, although various embodiments are disclosed in this specification, specific features (technical matters) in one embodiment can be added to or substituted for specific features in other embodiments, with appropriate modifications, and such forms are also included in the spirit of the present invention. [Explanation of symbols]

[0085] 1...Vehicle dispatch management system 10...Vehicle dispatch management device 110...Front-end processing unit 120…Demand information acquisition department 121…Current demand calculation department 122...Demand Forecasting Department 130... Vehicle dispatch request acquisition unit 140...Departure and Arrival Location Determination Department 150... Vehicle Allocation Planning Department 160...Route Planning Department 170...Vehicle communication interface unit 171...Vehicle information acquisition unit 172...Dispatch Instruction Department 12...Database 12a...Operational performance database 12b...Baggage information database 12c...User information database 12d…Map database 12e...Vehicle information database 12F: Vehicle dispatch plan database 20...Terminal device N: Communication network V...Vehicle 300...Control device 310…Communications Department 320...Location information acquisition unit 330...User interface section

Claims

1. A vehicle dispatch management device that manages on-demand vehicle dispatch using a plurality of vehicles that can carry both passengers and luggage, a vehicle dispatch request acquisition unit that acquires a vehicle dispatch request from a user for either a ride or a baggage delivery; a vehicle allocation plan creation unit that creates a vehicle allocation plan for one vehicle selected from the plurality of vehicles based on the acquired vehicle allocation request; a vehicle allocation instruction unit that transmits a vehicle allocation instruction based on the vehicle allocation plan to the one vehicle; the vehicle allocation plan creation unit temporarily suspends creation of the vehicle allocation plan if there are no other vehicle allocation requests at the time of creating the vehicle allocation plan for the one vehicle in response to the vehicle allocation request for the package delivery; When a predetermined holding time limit has elapsed since the time when the request for dispatching the luggage delivery vehicle was accepted, the holding is released. Vehicle dispatch management device.

2. the vehicle allocation plan creation unit proposes the created vehicle allocation plan to the user, and when the user agrees to the proposal, finalizes the vehicle allocation plan. The vehicle dispatch control device according to claim 1 .

3. a demand information acquisition unit that acquires demand information indicating current and future demand amounts for the plurality of vehicles; The vehicle dispatch control device according to claim 1 .

4. the vehicle allocation plan creation unit temporarily suspends creation of the vehicle allocation plan when the future demand amount indicated by the demand information exceeds a first upper limit value; The vehicle allocation management device according to claim 3.

5. the vehicle allocation plan creation unit temporarily suspends creation of the vehicle allocation plan when a ratio of the future demand amount to the current demand amount indicated by the demand information exceeds a predetermined rate of change. The vehicle allocation management device according to claim 3.

6. the vehicle allocation plan creation unit finalizes the vehicle allocation plan when a current demand amount indicated by the demand information exceeds a second upper limit value. The vehicle allocation management device according to claim 3.

7. the vehicle allocation plan creation unit finalizes the vehicle allocation plan when the number of parcels indicated in the parcel delivery vehicle allocation request is equal to or greater than a predetermined limit number of parcels to be held; The vehicle dispatch control device according to claim 1 .

8. a demand information acquisition unit that acquires demand information indicating current and future demand amounts for the plurality of vehicles; the vehicle dispatch plan creation unit reduces the value of the predetermined limit number of reserved baggage when a ratio of the future demand amount to the current demand amount indicated by the demand information exceeds a predetermined rate of change. The vehicle allocation management device according to claim 7.

9. the vehicle allocation plan creation unit recreates a vehicle allocation plan based on the vehicle allocation request corresponding to the temporarily held vehicle allocation plan and the other vehicle allocation requests when there is a vehicle allocation plan that is temporarily held; The vehicle dispatch control device according to claim 1 .

10. the vehicle dispatch plan creation unit sets the predetermined holding limit time in accordance with attribute information of a user who has made the vehicle dispatch request for the luggage delivery. The vehicle dispatch control device according to claim 1 .

11. the vehicle dispatch plan creation unit sets the predetermined holding limit time in accordance with baggage attribute information indicated in the baggage delivery vehicle dispatch request. The vehicle dispatch control device according to claim 1 .

12. the vehicle dispatch plan creation unit sets the predetermined holding limit time in accordance with loading location information indicated in the vehicle dispatch request for the luggage delivery. The vehicle dispatch control device according to claim 1 .

13. the demand information acquisition unit includes a demand forecasting unit that forecasts the future demand amount, the demand forecasting unit calculates the future demand amount based on the number of waiting vehicles that are subject to the vehicle allocation plan among the plurality of vehicles; The vehicle allocation management device according to claim 3.

14. the demand forecasting unit calculates the future demand amount based on operation performance information regarding past operation performance of the plurality of vehicles; The vehicle dispatch management device according to claim 13.

15. the demand forecasting unit calculates the future demand amount based on a behavior history of the user who has made the ride dispatch request; The vehicle dispatch control device according to claim 13 or 14.

16. the vehicle allocation plan creation unit extracts a plurality of candidate vehicles from among the plurality of vehicles in response to the vehicle allocation request, creates a plurality of vehicle allocation plans based on a plurality of route patterns for each of the plurality of candidate vehicles, and selects one of the vehicle allocation plans in accordance with a predetermined evaluation function; The vehicle dispatch control device according to claim 1 .

17. A vehicle allocation management method using a vehicle allocation management device that manages on-demand vehicle allocation using a plurality of vehicles that can carry both passengers and luggage, comprising: Acquiring a vehicle dispatch request for either a ride or a baggage delivery from a user's terminal device; creating a vehicle allocation plan for one vehicle selected from the plurality of vehicles in response to the acquired vehicle allocation request; transmitting a dispatch instruction based on the determined dispatch plan to the one vehicle; creating the vehicle allocation plan includes temporarily suspending the creation of the vehicle allocation plan if there are no other vehicle allocation requests at the time of creating the vehicle allocation plan for the one vehicle in response to the vehicle allocation request for the package delivery; and releasing the hold when a predetermined hold limit time has elapsed since the time when the request for dispatching the luggage delivery vehicle was accepted. Vehicle allocation management method.

Citation Information

Patent Citations

  • Vehicle dispatching planning device and vehicle dispatching planning method

    JP2009146004A

  • Vehicle allocation management device and vehicle allocation management method

    JP2022003458A

  • Smart Signs for Autonomous Vehicles

    JP2022504037A

  • On-demand passenger and freight mixed transport system and on-board equipment

    JP6673037B2

  • Mixed freight / passenger loading system, vehicle dispatch device for mixed freight / passenger loading system, and vehicle dispatch method for mixed freight / passenger loading system

    WO2022162842A1