WO2024048231A1 - Vehicle dispatch management device and vehicle dispatch management method - Google Patents
Vehicle dispatch management device and vehicle dispatch management method Download PDFInfo
- Publication number
- WO2024048231A1 WO2024048231A1 PCT/JP2023/029096 JP2023029096W WO2024048231A1 WO 2024048231 A1 WO2024048231 A1 WO 2024048231A1 JP 2023029096 W JP2023029096 W JP 2023029096W WO 2024048231 A1 WO2024048231 A1 WO 2024048231A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- vehicle
- vehicle allocation
- plan
- dispatch
- management device
- Prior art date
Links
- 238000007726 management method Methods 0.000 title claims abstract description 146
- 238000012384 transportation and delivery Methods 0.000 claims abstract description 68
- 230000004044 response Effects 0.000 claims abstract description 28
- 238000011156 evaluation Methods 0.000 claims description 21
- 239000000725 suspension Substances 0.000 claims description 12
- 238000000034 method Methods 0.000 claims description 10
- 239000000284 extract Substances 0.000 claims description 5
- 230000008859 change Effects 0.000 claims description 4
- 238000012545 processing Methods 0.000 description 18
- 230000006870 function Effects 0.000 description 17
- 238000004891 communication Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 7
- 238000004364 calculation method Methods 0.000 description 6
- 230000007717 exclusion Effects 0.000 description 6
- 230000006399 behavior Effects 0.000 description 5
- 238000013439 planning Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 238000012790 confirmation Methods 0.000 description 3
- 238000007596 consolidation process Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000007423 decrease Effects 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 238000009795 derivation Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000007613 environmental effect Effects 0.000 description 2
- 235000013305 food Nutrition 0.000 description 2
- 238000010801 machine learning Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000002360 preparation method Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000000670 limiting effect Effects 0.000 description 1
- 230000001151 other effect Effects 0.000 description 1
- 238000005057 refrigeration Methods 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
- 230000001932 seasonal effect Effects 0.000 description 1
- 230000008685 targeting Effects 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
Images
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B65—CONVEYING; PACKING; STORING; HANDLING THIN OR FILAMENTARY MATERIAL
- B65G—TRANSPORT OR STORAGE DEVICES, e.g. CONVEYORS FOR LOADING OR TIPPING, SHOP CONVEYOR SYSTEMS OR PNEUMATIC TUBE CONVEYORS
- B65G61/00—Use of pick-up or transfer devices or of manipulators for stacking or de-stacking articles not otherwise provided for
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/123—Traffic control systems for road vehicles indicating the position of vehicles, e.g. scheduled vehicles; Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, trams
Definitions
- the present invention relates to vehicle dispatch management technology, and in particular to a vehicle dispatch management device and a vehicle dispatch management method for managing on-demand dispatch of vehicles that can carry both passengers and cargo (baggage). Regarding.
- Mobility services are known as services that provide smooth transportation of passengers and/or luggage by vehicle.
- mobility services have been proposed that transport passengers and luggage simultaneously in a single vehicle.
- Patent Document 1 listed below discloses an on-demand passenger cargo consolidation system that determines the route of an operating vehicle carrying passengers and luggage together based on passenger movement requests and baggage movement requests.
- the present invention has been made in view of the above-mentioned problems, and is an object of the present invention to improve vehicle dispatch efficiency and/or loading efficiency in an on-demand dispatch service for vehicles capable of passenger/cargo consolidation (consolidated cargo/passenger loading).
- the purpose is to improve vehicle dispatch efficiency and/or loading efficiency in an on-demand dispatch service for vehicles capable of passenger/cargo consolidation (consolidated cargo/passenger loading).
- the present invention for solving the above problems is constituted by including the following invention specific matters or technical features.
- the present invention is a vehicle allocation management device that manages on-demand vehicle allocation using a plurality of vehicles that can carry passengers and luggage together.
- the vehicle dispatch management device includes a vehicle dispatch request acquisition unit that acquires a vehicle dispatch request for either boarding or baggage delivery by a user, and one vehicle that is selected from the plurality of vehicles in response to the obtained vehicle dispatch request. and a vehicle allocation instruction section that transmits a vehicle allocation instruction based on the vehicle allocation plan to the one vehicle. Further, at the time when the vehicle dispatch plan creation unit creates the vehicle dispatch plan for the one vehicle in response to the vehicle dispatch request for package delivery, if there is no other vehicle dispatch request, the vehicle dispatch plan creation unit may not create the vehicle dispatch plan. temporarily put on hold.
- the present invention according to another aspect is 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 passengers and luggage together.
- the method includes acquiring a vehicle dispatch request for either a ride or a package delivery from a user's terminal device, and dispatching a vehicle to one vehicle selected from the plurality of vehicles in response to the acquired vehicle dispatch request.
- the method includes creating a plan, and transmitting a vehicle allocation instruction based on the confirmed vehicle allocation plan to the one vehicle. Further, creating the vehicle allocation plan means that at the time when the vehicle allocation plan for the one vehicle is created in response to the vehicle allocation request for package delivery, if there is no other vehicle allocation request, the vehicle allocation plan is Including temporarily suspending creation.
- FIG. 1 is a diagram illustrating an example of a vehicle allocation management system according to an embodiment of the present invention.
- FIG. 2 is a block diagram showing an example of a functional configuration model of a vehicle allocation management device according to an embodiment of the present invention.
- FIG. 3 is a diagram for explaining derivation of a route pattern in the vehicle allocation management system according to an embodiment of the present invention.
- FIG. 4 is a diagram for explaining various delay limit times in a vehicle allocation plan by a vehicle allocation management device according to an embodiment of the present invention.
- FIG. 5 is a sequence chart for explaining an overview of a vehicle dispatch service in a vehicle dispatch management system according to an embodiment of the present invention.
- FIG. 1 is a diagram illustrating an example of a vehicle allocation management system according to an embodiment of the present invention.
- FIG. 2 is a block diagram showing an example of a functional configuration model of a vehicle allocation management device according to an embodiment of the present invention.
- FIG. 3 is a diagram for explaining derivation of a route pattern in the
- FIG. 6A is a flowchart for explaining an example of vehicle allocation management processing by the vehicle allocation management device according to an embodiment of the present invention.
- FIG. 6B is a flowchart for explaining an example of vehicle allocation management processing by the vehicle allocation management device according to an embodiment of the present invention.
- FIG. 1 is a diagram illustrating an example of a vehicle allocation management system according to an embodiment of the present invention.
- the vehicle allocation management system 1 includes a vehicle allocation management device 10, a terminal device 20, and a vehicle V, which are connected to each other via a communication network N so that they can communicate with each other.
- the vehicle dispatch management system 1 of the present disclosure provides, for example, an on-demand vehicle dispatch service using a plurality of vehicles V, targeting a certain area.
- "On-demand vehicle dispatch service” refers to a service that allocates (dispatch) a predetermined vehicle to a user in immediate response to a vehicle dispatch request from the user. In other words, in an on-demand vehicle dispatch service, there is no vehicle dispatch reservation time specified by the user.
- immediate response is a concept that includes not only dispatching a vehicle without delay in response to a vehicle dispatch request from a user, but also including a certain amount of time that the user can usually tolerate.
- the vehicle dispatch management system 1 of the present disclosure is based on the premise of such an "on-demand vehicle dispatch service" and provides efficient delivery by adjusting the timing of dispatch for a specific vehicle dispatch request under predetermined conditions. Realize ride-hailing services.
- the vehicle dispatch management device 10 is a computing device that centrally manages vehicle dispatch services by a plurality of vehicles V in a target area.
- the vehicle dispatch management device 10 implements the vehicle dispatch service of the present disclosure by implementing, for example, a vehicle dispatch management server program and executing the vehicle dispatch management server program under the control of a processor.
- the vehicle dispatch management device 10 includes various databases 12 that manage data necessary to realize such a vehicle dispatch service.
- the database 12 includes, for example, an operation record database 12a, a baggage 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).
- the database 12 is configured as a part of the vehicle allocation management device 10, but the database 12 is not limited to this, and all or part of it may be configured separately from the vehicle allocation management device 10.
- the vehicle dispatch management device 10 receives a dispatch request for a vehicle V from a user who wishes to dispatch a vehicle, and creates and finalizes a dispatch plan for one vehicle V selectively allocated in response to the dispatch request. Then, a vehicle allocation instruction is given to one vehicle V in accordance with the confirmed vehicle allocation plan. The vehicle allocation plan is confirmed, for example, after receiving the user's consent.
- vehicle dispatch requests include a vehicle dispatch request for a ride from a user who is a passenger (hereinafter referred to as a "vehicle dispatch request"), and a vehicle dispatch request from a user who is a shipper (package delivery company or general user).
- vehicle dispatch request There is a vehicle allocation request for package delivery (hereinafter referred to as “vehicle allocation request for package delivery”).
- vehicle allocation request for package delivery a vehicle allocation request for package delivery
- a general user who is not a package delivery company can also request a package delivery vehicle in order to have his or her package delivered.
- a vehicle dispatch request includes, for example, the user name, the type of vehicle dispatch request, the departure/arrival location (boarding and disembarking locations for passengers, loading and unloading locations for cargo), transportation details (number of passengers and cargo). If so, it includes information on the number, size, type of luggage, etc.
- the vehicle allocation plan starts from the place where the vehicle V waits (the starting point), passes through several points along the way (departure/arrival points) for boarding and alighting and/or loading/unloading cargo, and then goes to the final point (the waiting point). (This may not be the same as the initial waiting location.)
- the vehicle allocation management device 10 temporarily suspends a specific vehicle allocation plan according to predetermined suspension conditions.
- the predetermined suspension condition is, for example, a case where no other vehicle allocation request is received at the time of creating a vehicle allocation plan for a vehicle allocation request for package delivery.
- the vehicle allocation management device 10 releases the suspension of the vehicle allocation plan according to predetermined release conditions, and adjusts the vehicle allocation plan so that it is a so-called mixed freight and passenger loading based on the vehicle allocation request for baggage delivery and the vehicle allocation request for boarding. Recreate it, propose it to the user, and confirm.
- the predetermined cancellation condition is, for example, when a request for dispatching a new ride is subsequently received.
- Vehicle V is a vehicle registered in the vehicle information database 12e that is available for use by the user.
- the type of vehicle V (for example, sedan, minivan, SUV, etc.) does not matter, but it is assumed that it is at least a type that can carry cargo and passengers together.
- the vehicle V may be an electric vehicle (EV) powered by an on-board battery. Further, the vehicle V may be a self-driving car capable of completely autonomous driving, and the so-called self-driving level does not matter.
- the vehicle V includes a control device 300 that controls the vehicle V itself or its onboard equipment (for example, a navigation device) according to instructions from the vehicle allocation management device 10 (see FIG. 2).
- the control device 300 acquires position information of the vehicle V via a GPS system, transmits this to the vehicle dispatch management device 10, receives a dispatch instruction from the vehicle dispatch management device 10, and controls various devices of the vehicle V or Control the operation of the device.
- the control device 300 includes, for example, a navigation function that presents an operating route according to a vehicle allocation plan, and an autonomous driving control function that follows the operating route of the vehicle V in the case of a fully autonomous vehicle.
- the terminal device 20 is a computing device that allows a user, such as a ride applicant or a luggage delivery company, to request a ride 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 vehicle dispatch application).
- vehicle dispatch application enables the user to use the vehicle dispatch service of the vehicle dispatch management device 10 by executing a vehicle dispatch application under the control of the processor.
- the user makes a vehicle dispatch request from a vehicle dispatch request screen (not shown) on the user interface of the terminal device 20, and in response, accepts the vehicle dispatch plan created by the vehicle dispatch management device 10. You can make reservations for rides or baggage delivery.
- the vehicle allocation plan based on the vehicle allocation request for package delivery is temporarily suspended according to the predetermined suspension conditions, so that the vehicles V can be efficiently operated.
- the temporarily suspended vehicle allocation plan is re-created together with subsequent new vehicle allocation requests, so that the vehicle V allocation efficiency and/or loading rate can be improved.
- the created vehicle allocation plan is proposed to the user, and if the user accepts the proposal, the vehicle allocation plan is finalized, so vehicles V can be operated flexibly in response to various vehicle allocation requests. , vehicle dispatch efficiency can be improved.
- FIG. 2 is a block diagram showing an example of a functional configuration model of a vehicle allocation management device according to an embodiment of the present invention.
- the vehicle allocation management device 10 includes, for example, a front end processing unit 110, a demand information acquisition unit 120, a vehicle allocation request acquisition unit 130, a departure/arrival point determination unit 140, a vehicle allocation plan creation unit 150, It is configured as a functional configuration model including functional components such as a travel route planning section 160 and a vehicle communication interface section 170. Further, the vehicle allocation management device 10 includes various databases 12, as described above. 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.
- the terminal device 20 as a terminal device for package delivery companies and general users, and a part of the configuration of the control device 300 in the vehicle V are also shown.
- the operation record database 12a stores, for example, information regarding the past operation record of each vehicle V (operation record information).
- the operation record information includes various specification information such as operation time (operation start time and end time), operation route, and mileage for each vehicle V, for example.
- the operation record information may indicate the demand record of the vehicle V in a certain time zone and/or a certain area based on the operation time of each vehicle V.
- the package information database 12b stores information regarding package delivery (package information).
- the package information includes, for example, information regarding the package delivery company name, business attributes, delivery base, package ID, package delivery status, customer information, and the like.
- the user information database 12c stores user information regarding users who use the dispatch service.
- the user information includes, for example, a user ID and password, personal attributes, and information regarding service usage status.
- the user information is registered in the user information database 12c under the control of the vehicle dispatch management device 10, for example, when the user inputs predetermined information when the vehicle dispatch application is first activated.
- the user information may include the user's own specific behavior history.
- the specific behavior history includes, for example, the user's purchase history in the target area of the ride-hailing service. Such behavior history can be used by the demand information acquisition unit 120, for example, to predict whether there is a possibility that the user will request a ride soon after making a purchase.
- the map database 12d stores at least map data in the target area of the dispatch service.
- the map data includes, for example, information regarding addresses, place names, roads, facility names, and the like. Additionally, the map data may include information necessary for route search and environmental information such as road congestion conditions.
- Map data can be used, and for example, it may be an external map database that can be connected via an API.
- the vehicle information database 12e stores information (vehicle information) regarding the vehicle V provided for use by the user.
- Vehicle information includes, for example, vehicle ID, vehicle attributes (vehicle registration number, vehicle type, maximum number of passengers/maximum loading capacity, etc.), current dispatch plan, current location, and current status (service status, remaining battery capacity, number of passengers, etc.). , cargo loading capacity, etc.).
- vehicle ID vehicle ID
- vehicle attributes vehicle registration number, vehicle type, maximum number of passengers/maximum loading capacity, etc.
- current dispatch plan current location
- current status service status, remaining battery capacity, number of passengers, etc.
- cargo loading capacity etc.
- the vehicle allocation plan database 12f stores a vehicle allocation plan for each vehicle V based on the vehicle allocation request.
- the vehicle allocation plan includes an operation route from a waiting location as a starting point to a waiting location as an end point via several points. Furthermore, each vehicle allocation plan is associated with status information such as whether it is temporarily on hold or confirmed.
- the front end processing unit 110 performs various processes with the user's terminal device 20.
- the front-end processing unit 110 refers to the user information database 12c and performs login authentication processing in accordance with a login request from a vehicle dispatch application on the user's terminal device 20.
- the front-end processing unit 110 receives a vehicle dispatch request from a vehicle dispatch application on the user's terminal device 20, passes it to the vehicle dispatch request acquisition unit 130, and in response, the front end processing unit 110 receives a vehicle dispatch request from a vehicle dispatch application on the user's terminal device 20, passes it to the vehicle dispatch request acquisition unit 130, and in response, the vehicle dispatch plan creation unit 150 It interacts with the terminal device 20 in order to receive the user's approval or disapproval of the created vehicle allocation plan.
- the front end processing unit 110 acquires the user's action history transmitted from the user's terminal device 20 and stores it in the user information database 12c. A user's behavior history can be used to predict future demand.
- the demand information acquisition unit 120 acquires demand information indicating the current and/or future demand amount of the vehicle V at a predetermined timing.
- the demand information acquisition unit 120 includes, for example, a current demand calculation unit 121 that calculates the current demand for the vehicle V, and a demand prediction unit 122 that predicts the future demand.
- a current demand calculation unit 121 that calculates the current demand for the vehicle V
- a demand prediction unit 122 that predicts the future demand.
- the current demand calculation unit 121 refers to the vehicle allocation plan database 12f, calculates the current demand amount based on the number of waiting vehicles V to which no vehicle allocation plan is assigned at the present time (the number of waiting vehicles), and is output as demand information.
- the demand forecasting unit 122 refers to the operation record database 12a, predicts the future demand for the vehicle V based on past operation record information, and outputs this as demand information.
- future demand may be based on vehicles that are expected to be in demand at specific times or time periods such as 10 minutes, 20 minutes, 30 minutes, and 1 hour after a reference time (for example, the current time).
- the number of units may be V.
- the predicted number of vehicles V based on the user's behavior history is taken into consideration. In other words, when a user who does not have a means of transportation goes shopping at a shopping mall or the like within the target area, there is a possibility that the user requests a ride. is counted as the expected number of vehicles V.
- the demand forecasting unit 122 may predict the future demand amount by considering environmental factors such as temporal/seasonal factors and event holdings in addition to operation performance information.
- the demand forecasting unit 122 may include a demand forecasting model subjected to machine learning according to a predetermined machine learning algorithm, using, for example, operating performance information as an explanatory variable and a predicted demand amount as an objective variable. In this way, the demand forecasting unit 122 can create an optimal vehicle plan by predicting future demand, and the vehicles V can be operated efficiently.
- the vehicle allocation request acquisition unit 130 receives and acquires a vehicle allocation request from the user via the front end processing unit 110.
- the time when the vehicle dispatch request acquisition unit 130 receives the vehicle dispatch request becomes the time at which the holding limit time, which will be described later, starts to be counted.
- the types of vehicle allocation requests made by the user include vehicle allocation requests for rides and vehicle allocation requests for package delivery.
- the vehicle allocation request acquisition unit 130 delivers the acquired vehicle allocation request to the departure/arrival point determination unit 140 and the vehicle allocation plan creation unit 150, respectively.
- the departure and arrival point determining unit 140 refers to the map database 12d and determines the departure and arrival points shown on the map where the user can actually get on and off the vehicle. That is, the departure/arrival point determining unit 140 refers to the map database 12d for the departure/arrival point indicated in the dispatch request, and indicates a geographical position on the service route where the user can actually get on and off or load/unload luggage. Generate departure and destination information. The departure and arrival point determining unit 140 delivers the generated departure and arrival point information to the vehicle allocation plan creation unit 150.
- the vehicle allocation plan creation unit 150 creates and finalizes a vehicle allocation plan for one vehicle V selected from a plurality of candidate vehicles (candidate vehicles) V, based on the vehicle allocation request and departure/arrival point information. A vehicle allocation instruction is given to one vehicle V according to the vehicle allocation plan.
- the vehicle allocation plan creation unit 150 if the vehicle allocation plan creation unit 150 has not received any other vehicle allocation requests at the time of creating the vehicle allocation plan for the package delivery vehicle allocation request, the vehicle allocation plan creation unit 150 temporarily suspends the vehicle allocation plan for the package delivery vehicle allocation request. . If, for example, a new vehicle dispatch request is received while the vehicle dispatch plan is on hold, the vehicle dispatch plan creation unit 150 releases the suspension of the vehicle dispatch plan, and dispatches the dispatch request for baggage delivery and the dispatch of a ride.
- the vehicle allocation plan is updated or re-created so that it becomes a so-called mixed cargo/passenger loading, and this is proposed to the user and confirmed. In this way, since the vehicle allocation plan is proposed to the user before it is finalized, the user can determine whether the proposed vehicle allocation plan meets his or her wishes.
- the vehicle allocation plan creation unit 150 stores the confirmed 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.
- 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 the departure and arrival points when a new departure and arrival point is added to the route that passes through the determined departure and arrival points (stopover points).
- the route pattern may include a route pattern based on a freight and passenger mixed vehicle dispatch plan based on a vehicle dispatch request for boarding and a vehicle dispatch request for package delivery.
- the driving route planning unit 160 refers to the map database 12d and the vehicle information database 12e and extracts one or more vehicles V that can match the vehicle allocation request as candidate vehicles v. For each of the extracted candidate vehicles v, a route pattern is derived according to the departure and arrival point information, and the derived route pattern is delivered to the vehicle allocation plan creation section 150.
- candidate vehicles v(1) to v(3) are extracted from the geographical relationship between the pick-up location Req_PU and the drop-off location Req_DO based on the vehicle allocation 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.
- route patterns of candidate vehicles v(2) and V(3) are one pattern and three patterns, respectively.
- 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 an operation route in which a waiting location serving as a starting point and a waiting location serving as an ending point are added to the route pattern.
- the vehicle allocation plan creation unit 150 narrows down the vehicle allocation plans by deleting or excluding vehicle allocation plans that meet predetermined exclusion conditions from among the created vehicle allocation plans. Examples of the predetermined exclusion conditions include (i) to (iv) below, but are not limited to these.
- FIG. 4 is a diagram for explaining various delay limit times in a vehicle allocation plan by a vehicle allocation management device according to an embodiment of the present invention.
- the scheduled operating time T_Tra according to the dispatch plan of a certain vehicle V based on the dispatch request is the time from the dispatch request reception time T_Req to the scheduled disembarkation time (scheduled loading/unloading time) T_DO.
- the vehicle allocation delay limit time refers to the time from the vehicle allocation request reception time T_Req to the scheduled boarding time (scheduled loading time) T_PU.
- the boarding delay limit time refers to the time from the scheduled boarding time T_PU to the boarding limit time TL_PU.
- the deboarding delay limit time refers to the time from the scheduled departure time T_Dep to the deboarding limit time (loading/unloading delay limit time) TL_DO, for example, from the boarding place (loading place) to the unloading place (loading/unloading place).
- the time is set to be 1.2 times the time it would take if the vehicle V went straight to the destination.
- the holding limit time is a time that allows temporary holding of the vehicle allocation plan, and is measured from the time when the vehicle allocation request is received.
- the hold limit time is an example of a predetermined release condition.
- the vehicle dispatch plan creation unit 150 excludes the vehicle dispatch plan ( Exclusion condition (ii)).
- the vehicle dispatch plan creation unit 150 determines that the alighting time of the related user will exceed the delay limit time due to the addition of pick-up point Req_PU and drop-off point Req_DO in a vehicle dispatch plan based on a certain route pattern, the vehicle dispatch plan creation unit 150 Exclude the plan (exclusion condition (iii)).
- the vehicle allocation plan creation unit 150 next calculates evaluation values for the narrowed-down vehicle allocation plans according to a predetermined evaluation function, and selects the optimal vehicle allocation plan according to the calculated evaluation values. For example, if the predetermined evaluation function is a request for dispatch of a ride, the shorter the riding time from the boarding time to the time of disembarkation, the higher the evaluation value, and if it is a request for dispatch of a package delivery, the evaluation value is based on the travel cost based on the distance traveled. This is a function defined such that the smaller the value, 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.
- a predetermined evaluation function is a request for dispatch of a ride
- the shorter the riding time from the boarding time to the time of disembarkation the higher the evaluation value
- the evaluation value is based on the travel cost based on the distance traveled. This is a function defined such that the smaller the value, the higher the evaluation value. In this
- the selected vehicle allocation plan is a provisional (temporary) vehicle allocation plan.
- a tentative vehicle allocation plan is a vehicle allocation plan that has not yet been finalized and is subject to modification or cancellation.
- the vehicle allocation plan creation unit 150 selects the one with the highest evaluation value based on the evaluation function. In this way, by using the evaluation function, it is possible to select the optimal vehicle allocation plan from among a plurality of vehicle allocation plans.
- different evaluation functions are used for requests for vehicle allocation for boarding and requests for vehicle allocation for package delivery, so it is possible to select a vehicle allocation plan that is more in line with the content of transportation.
- the vehicle allocation plan creation unit 150 may temporarily suspend the creation of the vehicle allocation plan.
- the vehicle allocation management device 10 temporarily stores the suspended vehicle allocation plan in the vehicle allocation plan database 12f. If, for example, a new vehicle dispatch request is received while the vehicle dispatch plan is on hold, the vehicle dispatch plan creation unit 150 cancels the suspension of the vehicle dispatch plan and creates a new vehicle dispatch request based on the package delivery vehicle dispatch request and the ride dispatch request.
- a new route pattern is derived, a vehicle allocation plan is re-created so that it will be a so-called mixed cargo/passenger load, and this is finalized.
- the vehicle allocation plan creation unit 150 can temporarily suspend the creation of a vehicle allocation plan based on a vehicle allocation request for package delivery and release the suspension, according to demand-dependent suspension conditions and release conditions. As an example, if the future demand predicted by the demand forecasting unit 122 exceeds the first upper limit, the vehicle allocation plan creation unit 150 temporarily suspends creation of the vehicle allocation plan. That is, when a certain amount of future demand for vehicles V is expected, the vehicle allocation plan creation unit 150 temporarily suspends the creation of the vehicle allocation plan in preparation for future vehicle allocation requests. As a result, it is possible to avoid delivering individual packages as much as possible, and it is possible to efficiently operate the vehicle V in consideration of future demand.
- the vehicle allocation plan creation section 150 Creation of the vehicle allocation plan is temporarily suspended.
- the vehicle allocation plan creation unit 150 temporarily suspends the creation of the vehicle allocation plan in preparation for future vehicle allocation requests.
- the vehicle allocation plan creation unit 150 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 suspend the vehicle allocation plan or suspends the vehicle allocation plan. unlock. That is, when the current demand is high, the vehicle allocation plan creation unit 150 releases the suspension of the vehicle allocation plan in order to prevent demand from being missed. Thereby, a high operating rate of the vehicle V can be maintained, and the vehicle V can be operated efficiently.
- the vehicle allocation plan creation unit 150 may finalize the vehicle allocation plan without suspending the creation of the vehicle allocation plan if the number of packages indicated by the vehicle allocation request for package delivery is equal to or greater than a predetermined limit number of pending packages. .
- the vehicle allocation plan creation unit 150 determines that when the ratio of the future demand amount predicted by the demand forecasting unit 122 to the current demand amount calculated by the current demand calculation unit 121 exceeds a predetermined rate of change. , the predetermined limit number of held baggage may be changed to a smaller value.
- the vehicle allocation plan creation unit 150 can arbitrarily set a hold limit time for a vehicle allocation request for package delivery.
- the vehicle allocation plan creation unit 150 may set a holding limit time according to attribute information of a user who has made a request for vehicle allocation for package delivery. More specifically, if the user who requested a vehicle for parcel delivery is a general user, the holding limit time is set as a relatively short first holding limit time, whereas if the user is a parcel delivery company. In this case, the hold limit time is set as a second first hold limit time that is longer than the first hold limit time.
- the vehicle allocation plan creation unit 150 may set the holding limit time according to the package attribute information indicated by the vehicle allocation request for package delivery. More specifically, if the package is a product that requires refrigeration or perishable food, and if there is a risk that delaying or delaying the delivery time will reduce the value of the package, the holding time limit is relatively short. Set as the hold limit time. In other words, by setting a shorter holding limit time for requests for delivery of parcels such as perishable foods, it becomes possible to support delivery services for parcels that must be delivered quickly in a short period of time.
- the vehicle allocation plan creation unit 150 may set the holding limit time according to the loading point information indicated by the vehicle allocation request for package delivery. More specifically, if the loading point of the package is the general user's home, the holding limit time is set as the first holding limit time, whereas if the loading point of the package is the business office of the package delivery company. In this case, the hold limit time is set as a second first hold limit time that is longer than the first hold limit time. In other words, by setting the hold limit time shorter for a one-off package delivery request made by a general user, and by allowing package delivery companies to hold their vehicle dispatch plans to a certain extent, it is possible to improve the satisfaction of general users with the ride dispatch service. It is expected that this will improve ride-hailing services and further revitalize ride-hailing services.
- the vehicle communication interface unit 170 exchanges various information with the vehicle V via the communication network N.
- 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.
- the vehicle information acquisition unit 171 communicates with the communication unit 310 of the control device 300 and acquires the position information etc. acquired by the position information acquisition unit 320.
- the vehicle allocation instruction unit 172 refers to the vehicle allocation plan database 12f in accordance with the instruction from the vehicle allocation plan creation unit 150, identifies a corresponding vehicle allocation plan, and transmits an operation instruction to the vehicle V according to the identified vehicle allocation plan.
- the control device 300 of the vehicle V which has received the operation instruction, uses the navigation function to display a travel route according to the vehicle allocation plan, for example, on a user interface (indicated as "UI" in the figure) 330.
- FIG. 5 is a sequence chart for explaining an overview of a vehicle dispatch service in a vehicle dispatch management system according to an embodiment of the present invention.
- the vehicle V transmits its own position information obtained from the GPS system to the vehicle allocation management device 10 at a predetermined timing (S501). Note that the vehicle V acquires and transmits the position information periodically or in response to a transmission request from the vehicle allocation management device 10. Thereby, the vehicle allocation management device 10 acquires the position information transmitted from the vehicle V (S502).
- a user who wishes to use a ride-hailing service executes a ride-hailing application installed on the terminal device 20 and inputs the necessary information for a ride-hailing request on the ride-hailing request screen displayed on the user interface.
- the terminal device 20 transmits a vehicle allocation request to the vehicle allocation management device 10 (S503).
- a user who wishes to ride a vehicle inputs the boarding location, the alighting location, the number of passengers, etc.
- a user who wishes to have a package delivered inputs the loading and unloading locations, the number, size, type, etc. of the packages.
- the pick-up and drop-off locations may be selected from, for example, a geographic map displayed by the ride-hailing app. Further, the boarding place (loading place) may be the current position obtained by, for example, a GPS function installed in the user's smartphone.
- the vehicle allocation management device 10 When the vehicle allocation management device 10 receives the vehicle allocation request from the terminal device 20 (S504), it creates a vehicle allocation plan for the vehicle V based on the received vehicle allocation request, and in order to propose this to the user, the vehicle allocation management device 10 creates the contents of the created vehicle allocation plan. is transmitted to the terminal device 20 (S505). In addition, when the received vehicle allocation request is a vehicle allocation request for package delivery, the vehicle allocation management device 10 does not receive any other vehicle allocation request at the time of creating a vehicle allocation plan based on the vehicle allocation request for package delivery. , temporarily suspends the creation of a vehicle dispatch plan for vehicle V based on the vehicle dispatch request for said package delivery, releases the suspension under predetermined conditions, and updates or re-creates the vehicle dispatch plan as necessary. .
- the terminal device 20 When the terminal device 20 receives the contents of the vehicle allocation plan, it displays this as a vehicle allocation plan proposal screen on the user interface and prompts the user to accept or reject (accept or reject) the proposed vehicle allocation plan (S506).
- the terminal device 20 transmits a notification of acceptance/disapproval to the vehicle allocation management device 10 (S507), and the vehicle allocation management device 10 receives the notification sent from the terminal device 20.
- a notification of acceptance/rejection is received (S508).
- the vehicle allocation management device 10 finalizes the vehicle allocation plan for the vehicle V according to the vehicle allocation plan, sends a confirmation notification of the vehicle allocation reservation to the terminal device 20, and A vehicle allocation instruction according to the vehicle allocation plan is transmitted to vehicle V (S509).
- the terminal device 20 When the terminal device 20 receives the confirmation notification of the vehicle allocation reservation, it displays this on the user interface to inform the user that the vehicle allocation reservation has been confirmed (S510). On the other hand, upon receiving the vehicle allocation instruction, the vehicle V displays, for example, on the navigation screen an operating route according to the vehicle allocation plan indicated by the vehicle allocation instruction, in order to navigate the driver (S511). This allows the driver to operate the vehicle V in an on-demand manner in response to a user's dispatch request.
- FIGS. 6A and 6B are flowcharts for explaining an example of vehicle allocation management processing by the vehicle allocation management device according to an embodiment of the present invention. Such processing is realized by the vehicle dispatch management device executing the vehicle dispatch management server program under the control of the processor, thereby cooperating with various hardware resources.
- the vehicle allocation management device 10 waits until a new vehicle allocation request is received from the user (S601).
- a user who desires a ride or delivery of luggage operates a ride allocation application on the user interface of the terminal device 20 and inputs a ride allocation request.
- the vehicle allocation management device 10 receives a vehicle allocation request from the user (S601: Yes)
- the vehicle allocation management device 10 refers to the map database 12d and determines departure and arrival points based on the vehicle allocation request (S602).
- the vehicle allocation management device 10 extracts one or more candidate vehicles v according to the departure and arrival points (S603). For example, the vehicle allocation management device 10 extracts a vehicle V that is waiting or moving near the departure point as a candidate vehicle v.
- the vehicle allocation management device 10 derives a route pattern for each extracted candidate vehicle v by referring to the map database 12d (S604).
- the route pattern indicates a route that passes through all the departure and arrival points when a new departure and arrival point is added to the route that passes through the determined departure and arrival points (stopover points).
- the vehicle allocation management device 10 creates a vehicle allocation plan based on the derived route pattern (S605).
- the vehicle allocation plan includes an operation route in which a waiting location serving as a starting point and a waiting location serving as an ending point are added to the route pattern.
- the vehicle allocation management device 10 narrows down the vehicle allocation plans by excluding the vehicle allocation plans that do not meet the predetermined exclusion conditions from among the created vehicle allocation plans (S606). For example, if the boarding time of the user who has made a new vehicle allocation request exceeds the vehicle allocation delay limit time, the vehicle allocation management device 10 excludes the vehicle allocation plan.
- the vehicle allocation management device 10 calculates evaluation values for the narrowed-down vehicle allocation plans according to a predetermined evaluation function, and selects one vehicle allocation plan with the highest calculated evaluation value (S607). If there is a vehicle allocation plan for mixed cargo and passenger loading, the vehicle allocation plan creation unit 150 selects the one with the highest evaluation value based on the evaluation function.
- the vehicle allocation management device 10 then refers to the vehicle allocation plan database 12f and determines whether there is a temporarily suspended vehicle allocation plan (S608).
- a pending dispatch plan in this disclosure, is a dispatch plan based on a dispatch request for a single package delivery.
- the vehicle dispatch management device 10 determines whether the current vehicle dispatch request is a luggage dispatch request. (S609).
- the vehicle dispatch management device 10 determines that there is a temporarily pending vehicle dispatch plan (Yes in S608), as will be described later, the vehicle dispatch management device 10 determines that there is a vehicle dispatch plan based on the current vehicle dispatch request and a pending vehicle dispatch plan.
- the vehicle allocation plan is updated or re-created based on the vehicle allocation plan (S620).
- the vehicle dispatch management device 10 determines whether the vehicle dispatch plan is for mixed freight and passenger loading (S610). ). In other words, when the vehicle allocation plan is re-created (S620), there is a possibility that freight and passengers will be mixed.
- the vehicle allocation management device 10 determines that the current vehicle allocation plan is for mixed cargo and passenger loading (Yes in S610)
- the vehicle allocation management device 10 proposes the contents of the vehicle allocation 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 to inform the user of the vehicle dispatch plan. Ask them to accept or reject the request.
- the vehicle dispatch management device 10 determines that the current vehicle dispatch request is a request for dispatching packages (Yes in S609), the vehicle dispatch management device 10 further determines that the number of packages indicated by the vehicle dispatch request is a predetermined number of held packages. It is determined whether the number is greater than or equal to the limit number (S611). If the vehicle dispatch management device 10 determines that the number of packages indicated by the vehicle dispatch request is equal to or greater than the predetermined limit number of held packages (Yes in S611), the vehicle dispatch management device 10 informs the user of the contents of the vehicle dispatch plan. A proposal is made (S612).
- the vehicle allocation management device 10 may determine whether the package is larger than a predetermined size.
- the vehicle allocation management device 10 determines whether consent has been received from the user for the vehicle allocation plan proposal (S613). When the vehicle allocation management device 10 receives consent from the user for the vehicle allocation plan proposal (S613: Yes), the vehicle allocation management device 10 finalizes the current vehicle allocation plan (S614). The vehicle allocation management device 10 stores the confirmed vehicle allocation plan in the vehicle allocation plan database 12f. Subsequently, the vehicle allocation management device 10 transmits a confirmation notification of the vehicle allocation reservation to the terminal device 20, and also transmits a vehicle allocation instruction based on the vehicle allocation plan to the vehicle V (S615).
- the vehicle allocation management device 10 when the vehicle allocation management device 10 receives a disapproval (rejection) from the user to the vehicle allocation plan proposal (No in S613), the vehicle allocation management device 10 cancels the current vehicle allocation plan based on the user's vehicle allocation request ( S616). In this case, the vehicle allocation management device 10 returns the temporarily suspended vehicle allocation plan used to recreate the vehicle allocation plan to the original pending vehicle allocation plan. If the user desires another vehicle dispatch service, he or she will make a new vehicle dispatch request.
- the vehicle allocation management device 10 determines whether the elapsed hold time of the held vehicle allocation plan exceeds the hold limit time (S617 in FIG. 6B). This is to prevent further delays in package delivery if the current vehicle allocation plan exceeds the hold limit time from the time when the package delivery request for vehicle allocation is received.
- the vehicle dispatch management device 10 determines that the pending elapsed time of the pending vehicle dispatch plan has exceeded the pending limit time (S617: Yes), as described above, the vehicle dispatch management device 10 proposes the contents of the current vehicle dispatch plan to the user (S612). ). In other words, when the vehicle dispatch management device 10 determines that the elapsed time on hold of the vehicle dispatch plan recreated based on the put on hold vehicle dispatch plan has exceeded the hold limit time, the vehicle dispatch management device 10 releases the hold on the vehicle dispatch plan. . In this way, if the elapsed time on hold for a vehicle dispatch plan exceeds the holding limit time, the vehicle dispatch plan is released from hold, so the user's waiting time for a vehicle dispatch request may be longer than necessary. can be prevented.
- the vehicle dispatch management device 10 determines whether the vehicle dispatch plan is on hold under the demand-dependent hold conditions (No in S617). It is determined whether or not the following is satisfied (S618). As an example, the vehicle allocation management device 10 determines that the vehicle allocation plan satisfies the reservation condition when the predicted future demand exceeds the first upper limit value (Yes in S618). As another example, if the current demand is below a predetermined lower limit, the vehicle allocation management device 10 determines that the vehicle allocation plan does not satisfy the reservation condition (No in S618).
- the vehicle allocation management device 10 determines that the vehicle allocation plan does not satisfy the reservation conditions (No in S618), the vehicle allocation management device 10 proposes the contents of the current vehicle allocation plan to the user (S612). On the other hand, if the vehicle allocation management device 10 determines that the vehicle allocation plan satisfies the suspension conditions (S618: Yes), it determines to suspend the current vehicle allocation plan (S619). The vehicle allocation management device 10 stores the vehicle allocation plan that has been decided to be put on hold in the vehicle allocation plan database 12f. The suspended vehicle dispatch plan will be referenced when the next vehicle dispatch request is made.
- the vehicle dispatch management device 10 determines that there is a pending vehicle dispatch plan (Yes in S608), the vehicle dispatch management device 10 creates a vehicle dispatch plan based on the current vehicle dispatch plan and the pending vehicle dispatch plan. is re-created (S620). For example, when a new vehicle allocation request is received, the vehicle allocation management device 10 re-creates a vehicle allocation plan so that freight and passengers are mixed. Thereby, the loading rate of the vehicle V can be increased, and efficient operation becomes possible.
- the vehicle allocation plan re-creation process is performed by the vehicle allocation management device 10 executing 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. .
- the vehicle allocation management device 10 extracts candidate vehicles v based on the departure and arrival points indicated by the vehicle allocation plan based on the current vehicle allocation request and the departure and arrival points indicated by the pending vehicle allocation plan (processing corresponding to S603). . Subsequently, the vehicle allocation management device 10 derives a route pattern for each extracted candidate vehicle v (processing corresponding to S604). Next, the vehicle allocation management device 10 re-creates a vehicle allocation plan based on the derived route pattern (processing corresponding to S605).
- the vehicle allocation management device 10 narrows down the operation route by excluding, from among the re-created vehicle allocation plans, unsatisfactory vehicle allocation plans that meet predetermined exclusion conditions (processing corresponding to S606). Then, the vehicle allocation management device 10 calculates evaluation values for the narrowed-down vehicle allocation plans according to a predetermined evaluation function, and selects one vehicle allocation plan with the largest calculated evaluation value (S607 ).
- the vehicle allocation management device 10 selects one vehicle allocation plan, as described above, it determines whether the current vehicle allocation request is a luggage allocation request (S609), and similarly performs the subsequent processing.
- the vehicle allocation management device 10 determines whether there is a pending vehicle allocation plan (S608) in response to obtaining a vehicle allocation request from the user (S601). Not limited. Although not shown, the vehicle dispatch management device 10 determines whether or not the elapsed time of the pending vehicle dispatch plan has exceeded the limit time for the pending vehicle dispatch plan, even if no vehicle dispatch request has been obtained. If it is determined that the hold limit time has been exceeded, the hold of the vehicle allocation plan may be canceled and a proposal may be made to the user.
- the vehicle allocation plan based on the vehicle allocation request for package delivery is temporarily suspended under predetermined conditions, so that the vehicle V can be efficiently operated.
- the temporarily suspended vehicle allocation plan is re-created together with the vehicle allocation plan based on the subsequent vehicle allocation request, the vehicle allocation efficiency and/or loading rate of the vehicle V is improved.
- the created vehicle allocation plan is proposed to the user, and if the user accepts the proposal, the vehicle allocation plan is finalized, so vehicles V can be operated flexibly in response to various vehicle allocation requests. , vehicle allocation efficiency and/or loading rate can be improved.
- steps, acts, or functions may be performed in parallel or in a different order unless the results are inconsistent.
- the steps, acts, and functions described are provided by way of example only, and some of the steps, acts, and functions may be omitted or combined with each other without departing from the spirit of the invention. It is also possible to add other steps, actions, or functions.
Landscapes
- Engineering & Computer Science (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
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.
Description
本発明は、配車管理技術に関し、特に、乗客と貨物(荷物)とを混載可能な車両のオンデマンド方式による配車を管理する配車管理装置及び配車管理方法に関する。
に関する。 The present invention relates to vehicle dispatch management technology, and in particular to a vehicle dispatch management device and a vehicle dispatch management method for managing on-demand dispatch of vehicles that can carry both passengers and cargo (baggage).
Regarding.
に関する。 The present invention relates to vehicle dispatch management technology, and in particular to a vehicle dispatch management device and a vehicle dispatch management method for managing on-demand dispatch of vehicles that can carry both passengers and cargo (baggage).
Regarding.
モビリティサービスは、車両による乗客及び/又は荷物の輸送をスムーズに提供するサービスとして知られている。近年では、人口減少に伴う輸送需要の減少や労働力不足等を背景に、一つの車両で乗客と荷物とを同時に輸送するモビリティサービスが提案されている。
Mobility services are known as services that provide smooth transportation of passengers and/or luggage by vehicle. In recent years, against the backdrop of declining demand for transportation due to population decline and labor shortages, mobility services have been proposed that transport passengers and luggage simultaneously in a single vehicle.
例えば、下記特許文献1は、乗客の移動要求と荷物の移動要求とに基づいて、乗客と荷物とを混載した運行車両の経路を決定するオンデマンド客貨混載システムを開示している。
For example, Patent Document 1 listed below discloses an on-demand passenger cargo consolidation system that determines the route of an operating vehicle carrying passengers and luggage together based on passenger movement requests and baggage movement requests.
特許文献1に開示されたオンデマンド客貨混載システムでは、乗客や荷物配送業者といった車両の利用者の移動要求に対して、利用可能な運行車両があれば該利用者に直ちに配車が行われる。したがって、例えば、荷物配送事業者による荷物の移動要求(配車要求)に対して車両の配車がなされた後にあっては、乗客の移動要求があっても、乗客は該車両には荷物ともに混載されないために、配車効率及び/又は積載効率が低下し、乗客は、次の配車が可能になるまで待たされるという問題があった。
In the on-demand passenger/freight consolidation system disclosed in Patent Document 1, in response to a movement request from a vehicle user such as a passenger or a luggage delivery company, if there is an available operating vehicle, a vehicle is immediately allocated to the user. Therefore, for example, after a vehicle is dispatched in response to a request to move cargo (vehicle allocation request) by a cargo delivery company, even if there is a request to move a passenger, the passenger and the cargo will not be loaded together in the vehicle. Therefore, there is a problem in that vehicle allocation efficiency and/or loading efficiency decreases, and passengers are forced to wait until the next vehicle becomes available.
そこで、本発明は、上記の問題に鑑みてなされたものであり、客貨混載(貨客混載)が可能な車両のオンデマンド方式の配車サービスにおいて、車両の配車効率及び/又は積載効率を向上させることを目的とする。
The present invention has been made in view of the above-mentioned problems, and is an object of the present invention to improve vehicle dispatch efficiency and/or loading efficiency in an on-demand dispatch service for vehicles capable of passenger/cargo consolidation (consolidated cargo/passenger loading). The purpose is to
上記課題を解決するための本発明は、以下に示す発明特定事項乃至は技術的特徴を含んで構成される。
The present invention for solving the above problems is constituted by including the following invention specific matters or technical features.
ある観点に従う本発明は、乗客と荷物とを混載可能な複数の車両を用いたオンデマンド方式による配車を管理する配車管理装置である。前記配車管理装置は、ユーザによる乗車及び荷物配送のいずれかの配車要求を取得する配車要求取得部と、取得された前記配車要求に応答して前記複数の車両の中から選択される一の車両に対する配車計画を作成する配車計画作成部と、前記配車計画に基づく配車指示を前記一の車両に送信する配車指示部と、を備える。また、前記配車計画作成部は、前記荷物配送の配車要求に応答して前記一の車両に対する前記配車計画を作成する時点で、他の前記配車要求がない場合には、前記配車計画の作成を一時的に保留する。
The present invention according to a certain aspect is a vehicle allocation management device that manages on-demand vehicle allocation using a plurality of vehicles that can carry passengers and luggage together. The vehicle dispatch management device includes a vehicle dispatch request acquisition unit that acquires a vehicle dispatch request for either boarding or baggage delivery by a user, and one vehicle that is selected from the plurality of vehicles in response to the obtained vehicle dispatch request. and a vehicle allocation instruction section that transmits a vehicle allocation instruction based on the vehicle allocation plan to the one vehicle. Further, at the time when the vehicle dispatch plan creation unit creates the vehicle dispatch plan for the one vehicle in response to the vehicle dispatch request for package delivery, if there is no other vehicle dispatch request, the vehicle dispatch plan creation unit may not create the vehicle dispatch plan. temporarily put on hold.
また、別の観点に従う本発明は、乗客と荷物とを混載可能な複数の車両を用いたオンデマンド方式による配車を管理する配車管理装置による配車管理方法である。前記方法は、ユーザの端末装置から乗車及び荷物配送のいずれかの配車要求を取得することと、取得された前記配車要求に応答して前記複数の車両の中から選択される一の車両に対する配車計画を作成することと、確定された前記配車計画に基づく配車指示を前記一の車両に送信することと、を含む。また、前記配車計画を作成することは、前記荷物配送の配車要求に応答して前記一の車両に対する前記配車計画を作成する時点で、他の前記配車要求がない場合には、前記配車計画の作成を一時的に保留することを含む。
The present invention according to another aspect is 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 passengers and luggage together. The method includes acquiring a vehicle dispatch request for either a ride or a package delivery from a user's terminal device, and dispatching a vehicle to one vehicle selected from the plurality of vehicles in response to the acquired vehicle dispatch request. The method includes creating a plan, and transmitting a vehicle allocation instruction based on the confirmed vehicle allocation plan to the one vehicle. Further, creating the vehicle allocation plan means that at the time when the vehicle allocation plan for the one vehicle is created in response to the vehicle allocation request for package delivery, if there is no other vehicle allocation request, the vehicle allocation plan is Including temporarily suspending creation.
本発明によれば、客貨混載が可能な車両のオンデマンド方式の配車サービスにおいて、車両の配車効率及び/又は積載効率を向上させることができる。
According to the present invention, it is possible to improve vehicle dispatch efficiency and/or loading efficiency in an on-demand dispatch service for vehicles capable of mixed passenger and cargo loading.
本発明の他の技術的特徴、目的、及び作用効果乃至は利点は、添付した図面を参照して説明される以下の実施形態により明らかにされる。本明細書に記載された効果はあくまで例示であって限定されるものではなく、また他の効果があっても良い。
Other technical features, objects, effects, and advantages of the present invention will be made clear by the following embodiments described with reference to the accompanying drawings. The effects described in this specification are merely examples and are not limiting, and other effects may also be present.
以下、図面を参照して本発明の実施の形態を説明する。ただし、以下に説明する実施形態は、あくまでも例示であり、以下に明示しない種々の変形や技術の適用を排除する意図はない。本発明は、その趣旨を逸脱しない範囲で種々変形(例えば各実施形態を組み合わせる等)して実施することができる。また、以下の図面の記載において、同一又は類似の部分には同一又は類似の符号を付して表している。図面は模式的なものであり、必ずしも実際の寸法や比率等とは一致しない。図面相互間においても互いの寸法の関係や比率が異なる部分が含まれていることがある。
Embodiments of the present invention will be described below with reference to the drawings. However, the embodiments described below are merely examples, and there is no intention to exclude the application of various modifications and techniques not specified below. The present invention can be implemented in various ways (for example, by combining the embodiments) without departing from the spirit thereof. In addition, in the description of the drawings below, the same or similar parts are denoted by the same or similar symbols. The drawings are schematic and do not necessarily correspond to actual dimensions or proportions. The drawings may also include portions that differ in dimensional relationships and ratios.
図1は、本発明の一実施形態に係る配車管理システムの一例を説明する図である。同図に示すように、配車管理システム1は、配車管理装置10と、端末装置20と、車両Vを含み、これらは通信ネットワークNを介して相互に通信可能に接続される。本開示の配車管理システム1は、例えば、ある地域を対象にした、複数の車両Vを用いたオンデマンド方式による配車サービスを提供する。「オンデマンド方式による配車サービス」とは、ユーザからの配車要求に即時に応答して、該ユーザに所定の車両を割り当てる(配車する)サービスをいう。つまり、オンデマンド方式による配車サービスでは、ユーザが指定する配車予約時刻は存在しない。また、「即時に応答」とは、ユーザからの配車要求に対して間髪入れずに配車するだけでなく、ユーザが通常許容し得るようなある程度の幅をもった時間を含む概念である。本開示の配車管理システム1は、このような「オンデマンド方式による配車サービス」を前提としつつ、所定の条件の下、特定の配車要求についてはその配車のタイミングを調整することにより、効率的な配車サービスを実現する。
FIG. 1 is a diagram illustrating an example of a vehicle allocation management system according to an embodiment of the present invention. As shown in the figure, the vehicle allocation management system 1 includes a vehicle allocation management device 10, a terminal device 20, and a vehicle V, which are connected to each other via a communication network N so that they can communicate with each other. The vehicle dispatch management system 1 of the present disclosure provides, for example, an on-demand vehicle dispatch service using a plurality of vehicles V, targeting a certain area. "On-demand vehicle dispatch service" refers to a service that allocates (dispatch) a predetermined vehicle to a user in immediate response to a vehicle dispatch request from the user. In other words, in an on-demand vehicle dispatch service, there is no vehicle dispatch reservation time specified by the user. Furthermore, "immediate response" is a concept that includes not only dispatching a vehicle without delay in response to a vehicle dispatch request from a user, but also including a certain amount of time that the user can usually tolerate. The vehicle dispatch management system 1 of the present disclosure is based on the premise of such an "on-demand vehicle dispatch service" and provides efficient delivery by adjusting the timing of dispatch for a specific vehicle dispatch request under predetermined conditions. Realize ride-hailing services.
配車管理装置10は、対象地域における複数の車両Vによる配車サービスを統括的に管理するコンピューティングデバイスである。配車管理装置10は、例えば配車管理サーバプログラムを実装し、プロセッサの制御の下、配車管理サーバプログラムを実行することにより、本開示の配車サービスを実現する。
The vehicle dispatch management device 10 is a computing device that centrally manages vehicle dispatch services by a plurality of vehicles V in a target area. The vehicle dispatch management device 10 implements the vehicle dispatch service of the present disclosure by implementing, for example, a vehicle dispatch management server program and executing the vehicle dispatch management server program under the control of a processor.
配車管理装置10は、かかる配車サービスを実現するために必要なデータを管理する各種のデータベース12を含む。データベース12は、例えば、稼働実績データベース12aと、荷物情報データベース12bと、ユーザ情報データベース12cと、地図データベース12dと、車両情報データベース12eと、配車計画データベース12fとを含み構成される(図2参照)。本例では、データベース12は、配車管理装置10の一部として構成されているが、これに限られず、その全部又は一部が配車管理装置10とは別体に構成されても良い。
The vehicle dispatch management device 10 includes various databases 12 that manage data necessary to realize such a vehicle dispatch service. The database 12 includes, for example, an operation record database 12a, a baggage 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 database 12 is configured as a part of the vehicle allocation management device 10, but the database 12 is not limited to this, and all or part of it may be configured separately from the vehicle allocation management device 10.
概略的には、配車管理装置10は、配車を希望するユーザから車両Vの配車要求を受け付けて、該配車要求に対して選択的に割り当てられた一の車両Vに対する配車計画を作成して確定し、確定した配車計画に従った配車指示を一の車両Vに行う。配車計画の確定は、例えば、ユーザの承諾を受けて行われる。
Generally speaking, the vehicle dispatch management device 10 receives a dispatch request for a vehicle V from a user who wishes to dispatch a vehicle, and creates and finalizes a dispatch plan for one vehicle V selectively allocated in response to the dispatch request. Then, a vehicle allocation instruction is given to one vehicle V in accordance with the confirmed vehicle allocation plan. The vehicle allocation plan is confirmed, for example, after receiving the user's consent.
本開示では、配車要求の種別として、乗客であるユーザからの乗車のための配車要求(以下「乗車の配車要求」という。)と、荷主(荷物配送事業者又は一般ユーザ)であるユーザからの荷物配送のための配車要求(以下「荷物配送の配車要求」という。)とがある。つまり、荷物配送事業者でない一般ユーザもまた、自身の荷物を配送してもらうために荷物配送の配車要求を行い得る。配車要求は、例えば、ユーザ名、配車要求の種別、発着地(乗客であれば乗車地及び降車地、荷物であれば荷積地及び荷降地)、運送内容(乗客であれば人数、荷物であれば荷物の個数やサイズ、種類)等に関する情報を含む。
In this disclosure, the 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 "vehicle dispatch request"), and a vehicle dispatch request from a user who is a shipper (package delivery company or general user). There is a vehicle allocation request for package delivery (hereinafter referred to as "vehicle allocation request for package delivery"). In other words, a general user who is not a package delivery company can also request a package delivery vehicle in order to have his or her package delivered. A vehicle dispatch request includes, for example, the user name, the type of vehicle dispatch request, the departure/arrival location (boarding and disembarking locations for passengers, loading and unloading locations for cargo), transportation details (number of passengers and cargo). If so, it includes information on the number, size, type of luggage, etc.
配車計画は、車両Vが待機する場所(起点となる待機場所)から、乗降及び/又は荷物の積降を行う途中のいくつかの地点(発着地)を経由して、終点となる待機場所(最初の待機場所と同じとは限らない。)までを定めた運行ルートを含む。配車管理装置10は、所定の保留条件に従って、特定の配車計画を一時的に保留する。所定の保留条件は、例えば、荷物配送の配車要求に対する配車計画を作成する時点で他の配車要求を受け付けていない場合などである。そして、配車管理装置10は、所定の解除条件に従って、該配車計画の保留を解除して、荷物配送の配車要求と乗車の配車要求とに基づいて、いわゆる貨客混載となるように、配車計画を作成し直して、これをユーザに提案し、確定する。所定の解除条件は、例えばその後に新規の乗車の配車要求を受け付けた場合などである。
The vehicle allocation plan starts from the place where the vehicle V waits (the starting point), passes through several points along the way (departure/arrival points) for boarding and alighting and/or loading/unloading cargo, and then goes to the final point (the waiting point). (This may not be the same as the initial waiting location.) The vehicle allocation management device 10 temporarily suspends a specific vehicle allocation plan according to predetermined suspension conditions. The predetermined suspension condition is, for example, a case where no other vehicle allocation request is received at the time of creating a vehicle allocation plan for a vehicle allocation request for package delivery. Then, the vehicle allocation management device 10 releases the suspension of the vehicle allocation plan according to predetermined release conditions, and adjusts the vehicle allocation plan so that it is a so-called mixed freight and passenger loading based on the vehicle allocation request for baggage delivery and the vehicle allocation request for boarding. Recreate it, propose it to the user, and confirm. The predetermined cancellation condition is, for example, when a request for dispatching a new ride is subsequently received.
車両Vは、ユーザの利用に供される、車両情報データベース12eに登録された車両である。車両Vの車種(例えば、セダン、ミニバン、SUV等)は問わないが、少なくとも貨客混載が可能な車種であるものとする。車両Vは、車載バッテリーを動力源とする電気自動車(EV)であっても良い。また、車両Vは、完全な自律走行可能な自動運転車であっても良く、いわゆる自動運転化レベルを問わない。車両Vは、配車管理装置10による指示に従って車両V自体又はその搭載機器(例えばナビゲーション装置)を制御する制御装置300を備える(図2参照)。制御装置300は、例えば、GPSシステムを介して車両Vの位置情報を取得し、これを配車管理装置10に送信するとともに、配車管理装置10から配車指示を受け付けて、車両Vの各種の機器又は装置の動作を制御する。制御装置300は、例えば、配車計画に従った運行ルートを提示するナビゲーション機能や、完全自動運転車であれば車両Vの運行ルートに沿った自律走行制御機能を含む。
Vehicle V is a vehicle registered in the vehicle information database 12e that is available for use by the user. The type of vehicle V (for example, sedan, minivan, SUV, etc.) does not matter, but it is assumed that it is at least a type that can carry cargo and passengers together. The vehicle V may be an electric vehicle (EV) powered by an on-board battery. Further, the vehicle V may be a self-driving car capable of completely autonomous driving, and the so-called self-driving level does not matter. The vehicle V includes a control device 300 that controls the vehicle V itself or its onboard equipment (for example, a navigation device) according to instructions from the vehicle allocation management device 10 (see FIG. 2). For example, the control device 300 acquires position information of the vehicle V via a GPS system, transmits this to the vehicle dispatch management device 10, receives a dispatch instruction from the vehicle dispatch management device 10, and controls various devices of the vehicle V or Control the operation of the device. The control device 300 includes, for example, a navigation function that presents an operating route according to a vehicle allocation plan, and an autonomous driving control function that follows the operating route of the vehicle V in the case of a fully autonomous vehicle.
端末装置20は、例えば、乗車希望者や荷物配送事業者といったユーザがユーザインターフェースを操作して配車要求を行うためのコンピューティングデバイスである。端末装置20は、例えばスマートフォンやパッドコンピュータ、ノート型パーソナルコンピュータ、デスクトップ型コンピュータ等であるが、これらに限られない。端末装置20は、例えば、配車管理クライアントプログラム(いわゆる配車アプリ)を実装する。端末装置20は、プロセッサの制御の下、配車アプリを実行することにより、ユーザによる配車管理装置10の配車サービスの利用を可能にする。例えば、ユーザは、端末装置20のユーザインターフェース上の配車要求画面(図示せず)から配車要求を行い、これに応答して配車管理装置10が作成した配車計画を承諾することで、車両Vの乗車予約又は荷物配送予約を行い得る。
The terminal device 20 is a computing device that allows a user, such as a ride applicant or a luggage delivery company, to request a ride 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 vehicle dispatch application). The terminal device 20 enables the user to use the vehicle dispatch service of the vehicle dispatch management device 10 by executing a vehicle dispatch application under the control of the processor. For example, the user makes a vehicle dispatch request from a vehicle dispatch request screen (not shown) on the user interface of the terminal device 20, and in response, accepts the vehicle dispatch plan created by the vehicle dispatch management device 10. You can make reservations for rides or baggage delivery.
このように、本開示の配車管理システム1では、荷物配送の配車要求に基づく配車計画を所定の保留条件に従って一時的に保留するので、車両Vの効率的な運用が可能になる。とりわけ、一時的に保留となった配車計画は、その後の新規の配車要求と合わせて再作成されるので、車両Vの配車効率及び/又は積載率が向上するようになる。また、作成された配車計画はユーザに提案され、これに対してユーザが承諾した場合に、配車計画が確定されるので、種々の配車要求に対して車両Vの柔軟な運用を行うことができ、配車効率を向上させることができる。
In this way, in the vehicle allocation management system 1 of the present disclosure, the vehicle allocation plan based on the vehicle allocation request for package delivery is temporarily suspended according to the predetermined suspension conditions, so that the vehicles V can be efficiently operated. In particular, the temporarily suspended vehicle allocation plan is re-created together with subsequent new vehicle allocation requests, so that the vehicle V allocation efficiency and/or loading rate can be improved. In addition, the created vehicle allocation plan is proposed to the user, and if the user accepts the proposal, the vehicle allocation plan is finalized, so vehicles V can be operated flexibly in response to various vehicle allocation requests. , vehicle dispatch efficiency can be improved.
図2は、本発明の一実施形態に係る配車管理装置の機能構成モデルの一例を示すブロックダイアグラム図である。同図に示すように、配車管理装置10は、例えば、フロントエンド処理部110と、需要情報取得部120と、配車要求取得部130と、発着地決定部140と、配車計画作成部150と、走行ルート計画部160と、車両通信インターフェース部170といった機能構成要素を含む機能構成モデルとして構成される。また、配車管理装置10は、上述したように、各種のデータベース12を含む。かかる機能モデルは、配車管理装置10が、プロセッサの制御の下、配車管理サーバプログラムを実行し、これにより、各種のハードウェア資源と協働することにより、実現される。ここに示す機能構成モデルは一例であって、ある機能構成要素における全部又は一部の機能が、他の機能構成要素によって実現されても良い。なお、同図では、説明の便宜上、荷物配送業者用及び一般ユーザ用端末装置としての端末装置20、及び車両Vにおける制御装置300の一部の構成もまた示されている。
FIG. 2 is a block diagram showing an example of a functional configuration model of a vehicle allocation management device according to an embodiment of the present invention. As shown in the figure, the vehicle allocation management device 10 includes, for example, a front end processing unit 110, a demand information acquisition unit 120, a vehicle allocation request acquisition unit 130, a departure/arrival point determination unit 140, a vehicle allocation plan creation unit 150, It is configured as a functional configuration model including functional components such as a travel route planning section 160 and a vehicle communication interface section 170. Further, the vehicle allocation management device 10 includes various databases 12, as described above. 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, the terminal device 20 as a terminal device for package delivery companies and general users, and a part of the configuration of the control device 300 in the vehicle V are also shown.
稼働実績データベース12aは、例えば車両Vごとの過去の稼働実績に関する情報(稼働実績情報)を格納する。稼働実績情報は、例えば、車両Vごとの稼働時刻(運行開始時刻及び終了時刻)、運行ルート、及び走行距離等の各種の諸元情報を含む。稼働実績情報は、車両Vごとの稼働時刻に基づいて、ある時間帯及び/又はある地域における車両Vの需要実績を示し得る。
The operation record database 12a stores, for example, information regarding the past operation record of each vehicle V (operation record information). The operation record information includes various specification information such as operation time (operation start time and end time), operation route, and mileage for each vehicle V, for example. The operation record information may indicate the demand record of the vehicle V in a certain time zone and/or a certain area based on the operation time of each vehicle V.
荷物情報データベース12bは、荷物配送に関する情報(荷物情報)を格納する。荷物情報は、例えば、荷物配送業者名、事業者属性、配送拠点、荷物ID、荷物配送状況及び顧客情報等に関する情報を含む。
The package information database 12b stores information regarding package delivery (package information). The package information includes, for example, information regarding the package delivery company name, business attributes, delivery base, package ID, package delivery status, customer information, and the like.
ユーザ情報データベース12cは、配車サービスを利用するユーザに関するユーザ情報を格納する。ユーザ情報は、例えば、ユーザID及びパスワード、個人属性、並びにサービス利用状況に関する情報を含む。ユーザ情報は、例えば配車アプリの最初の起動時にユーザが所定の情報を入力することにより、配車管理装置10の制御の下、ユーザ情報データベース12cに登録される。また、本開示では、ユーザ情報は、ユーザ自身の特定の行動履歴を含み得る。特定の行動履歴は、例えば、配車サービスの対象地域におけるユーザの購買履歴を含む。このような行動履歴は、需要情報取得部120において例えばユーザが購買後間もなく配車要求をし得る可能性があるか否かを予測するために、利用され得る。
The user information database 12c stores user information regarding users who use the dispatch service. The user information includes, for example, a user ID and password, personal attributes, and information regarding service usage status. The user information is registered in the user information database 12c under the control of the vehicle dispatch management device 10, for example, when the user inputs predetermined information when the vehicle dispatch application is first activated. Further, in the present disclosure, the user information may include the user's own specific behavior history. The specific behavior history includes, for example, the user's purchase history in the target area of the ride-hailing service. Such behavior history can be used by the demand information acquisition unit 120, for example, to predict whether there is a possibility that the user will request a ride soon after making a purchase.
地図データベース12dは、少なくとも配車サービスの対象地域における地図データを格納する。地図データは、例えば、住所、地名、道路、及び施設名等に関する情報を含む。また、地図データは、ルート探索に必要な情報や道路渋滞状況等の環境情報を含み得る。地図データは、既知のものを利用することができ、例えば、APIを介して接続可能な外部の地図データベースであってもよい。
The map database 12d stores at least map data in the target area of the dispatch service. The map data includes, for example, information regarding addresses, place names, roads, facility names, and the like. Additionally, the map data may include information necessary for route search and environmental information such as road congestion conditions. Known map data can be used, and for example, it may be an external map database that can be connected via an API.
車両情報データベース12eは、ユーザの利用に供される車両Vに関する情報(車両情報)を格納する。車両情報は、例えば、車両ID、車両属性(車両登録番号、車種、及び最大乗車人員/最大積載量等)、現在の配車計画、現在位置、及び現在状態(サービス状態、バッテリー残容量、乗車人員、及び荷物積載量等)等に関する情報を含む。車両Vの現在位置は、後述するように、車両Vから送信される位置情報に基づいて随時に更新される。
The vehicle information database 12e stores information (vehicle information) regarding the vehicle V provided for use by the user. Vehicle information includes, for example, vehicle ID, vehicle attributes (vehicle registration number, vehicle type, maximum number of passengers/maximum loading capacity, etc.), current dispatch plan, current location, and current status (service status, remaining battery capacity, number of passengers, etc.). , cargo loading capacity, etc.). The current position of the vehicle V is updated at any time based on position information transmitted from the vehicle V, as described later.
配車計画データベース12fは、配車要求に基づく車両Vごとの配車計画を格納する。配車計画は、起点となる待機場所からいくつかの地点を経由した終点となる待機場所までの運行ルートを含む。また、各配車計画には、一時保留状態であるか、確定状態であるかといったステータス情報が関連付けられている。
The vehicle allocation plan database 12f stores a vehicle allocation plan for each vehicle V based on the vehicle allocation request. The vehicle allocation plan includes an operation route from a waiting location as a starting point to a waiting location as an end point via several points. Furthermore, each vehicle allocation plan is associated with status information such as whether it is temporarily on hold or confirmed.
フロントエンド処理部110は、ユーザの端末装置20との間での各種の処理を行う。一例として、フロントエンド処理部110は、ユーザの端末装置20上の配車アプリからのログイン要求に従って、ユーザ情報データベース12cを参照し、ログイン認証処理を行う。他の例として、フロントエンド処理部110は、ユーザの端末装置20上の配車アプリからの配車要求を受け付けて、これを配車要求取得部130に引き渡し、これに応答して配車計画作成部150により作成された配車計画に対するユーザの諾否を受けるために、端末装置20とやり取りする。更に他の例として、フロントエンド処理部110は、ユーザの端末装置20から送信されるユーザの行動履歴を取得して、これをユーザ情報データベース12cに格納する。ユーザの行動履歴は、将来の需要量の予測のために利用され得る。
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 12c and performs login authentication processing in accordance with a login request from a vehicle dispatch application on the user's terminal device 20. As another example, the front-end processing unit 110 receives a vehicle dispatch request from a vehicle dispatch application on the user's terminal device 20, passes it to the vehicle dispatch request acquisition unit 130, and in response, the front end processing unit 110 receives a vehicle dispatch request from a vehicle dispatch application on the user's terminal device 20, passes it to the vehicle dispatch request acquisition unit 130, and in response, the vehicle dispatch plan creation unit 150 It interacts with the terminal device 20 in order to receive the user's approval or disapproval of the created vehicle allocation plan. As yet another example, the front end processing unit 110 acquires the user's action history transmitted from the user's terminal device 20 and stores it in the user information database 12c. A user's behavior history can be used to predict future demand.
需要情報取得部120は、所定のタイミングで、車両Vの現在及び/又は将来の需要量を示す需要情報を取得する。需要情報取得部120は、例えば、車両Vの現在の需要量を算出する現在需要算出部121と、将来の需要量を予測する需要予測部122とを含む。本開示では、需要情報取得部120が取得する需要情報を用いることにより、配車計画を最適化することができるようになる。
The demand information acquisition unit 120 acquires demand information indicating the current and/or future demand amount of the vehicle V at a predetermined timing. The demand information acquisition unit 120 includes, for example, a current demand calculation unit 121 that calculates the current demand for 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 allocation plan.
現在需要算出部121は、配車計画データベース12fを参照し、現時点においていずれの配車計画も割り当てられていない待機中の車両Vの台数(待機台数)に基づいて、現在の需要量を算出し、これを需要情報として出力する。
The current demand calculation unit 121 refers to the vehicle allocation plan database 12f, calculates the current demand amount based on the number of waiting vehicles V to which no vehicle allocation plan is assigned at the present time (the number of waiting vehicles), and is output as demand information.
需要予測部122は、例えば、稼働実績データベース12aを参照し、過去の稼働実績情報等に基づいて、車両Vの将来の需要量を予測して、これを需要情報として出力する。一例として、将来の需要量は、基準時刻(例えば現在時刻)から10分後、20後、30分後、及び1時間後等といった特定の時刻又はその時間帯において需要が見込まれるであろう車両Vの台数であり得る。他の例として、将来の需要量は、ユーザの行動履歴に基づいて予測される車両Vの台数が考慮される。すなわち、移動手段を持たないユーザが、対象地域内のショッピングモールなどで買い物をした場合、該ユーザが配車要求をする可能性があるため、需要予測部122は、このような行動履歴に従って、需要が見込まれるであろう車両Vの台数としてカウントする。更に他の例として、需要予測部122は、稼働実績情報に加えて、例えば、時間的・季節的要因やイベント開催といった環境的要因を考慮して、将来の需要量を予測しても良い。需要予測部122は、例えば稼働実績情報等を説明変数とし、予測需要量を目的変数として、所定の機械学習アルゴリズムに従って機械学習が施された需要予測モデルを含み得る。このように、需要予測部122は将来の需要量を予測することで、最適な車両計画を作成することができ、車両Vの効率的な運用が可能になる。
For example, the demand forecasting unit 122 refers to the operation record database 12a, predicts the future demand for the vehicle V based on past operation record information, and outputs this as demand information. As an example, future demand may be based on vehicles that are expected to be in demand at specific times or time periods such as 10 minutes, 20 minutes, 30 minutes, and 1 hour after a reference time (for example, the current time). The number of units may be V. As another example, for the future demand amount, the predicted number of vehicles V based on the user's behavior history is taken into consideration. In other words, when a user who does not have a means of transportation goes shopping at a shopping mall or the like within the target area, there is a possibility that the user requests a ride. is counted as the expected number of vehicles V. As yet another example, the demand forecasting unit 122 may predict the future demand amount by considering environmental factors such as temporal/seasonal factors and event holdings in addition to operation performance information. The demand forecasting unit 122 may include a demand forecasting model subjected to machine learning according to a predetermined machine learning algorithm, using, for example, operating performance information as an explanatory variable and a predicted demand amount as an objective variable. In this way, the demand forecasting unit 122 can create an optimal vehicle plan by predicting future demand, and the vehicles V can be operated efficiently.
配車要求取得部130は、フロントエンド処理部110を介して、ユーザからの配車要求を受け付けて取得する。配車要求取得部130が配車要求を受け付けた時刻は、後述する保留限界時間の計時開始時刻となる。上述したように、本開示では、ユーザによる配車要求の種別には、乗車の配車要求と荷物配送の配車要求とがある。配車要求取得部130は、取得した配車要求を発着地決定部140及び配車計画作成部150の各々に引き渡す。
The vehicle allocation request acquisition unit 130 receives and acquires a vehicle allocation request from the user via the front end processing unit 110. The time when the vehicle dispatch request acquisition unit 130 receives the vehicle dispatch request becomes the time at which the holding limit time, which will be described later, starts to be counted. As described above, in the present disclosure, the types of vehicle allocation requests made by the user include vehicle allocation requests for rides and vehicle allocation requests for package delivery. The vehicle allocation request acquisition unit 130 delivers the acquired vehicle allocation request to the departure/arrival point determination unit 140 and the vehicle allocation plan creation unit 150, respectively.
発着地決定部140は、配車要求に基づいて、地図データベース12dを参照し、地図上に示される実際にユーザが乗降等可能な発着地を決定する。すなわち、発着地決定部140は、配車要求において示される発着地に対して、地図データベース12dを参照し、運行ルート上でユーザが実際に乗降可能又は荷物を積み降し可能な地理的位置を示す発着地情報を生成する。発着地決定部140は、生成した発着地情報を配車計画作成部150に引き渡す。
Based on the dispatch request, the departure and arrival point determining unit 140 refers to the map database 12d and determines the departure and arrival points shown on the map where the user can actually get on and off the vehicle. That is, the departure/arrival point determining unit 140 refers to the map database 12d for the departure/arrival point indicated in the dispatch request, and indicates a geographical position on the service route where the user can actually get on and off or load/unload luggage. Generate departure and destination information. The departure and arrival point determining unit 140 delivers the generated departure and arrival point information to the vehicle allocation plan creation unit 150.
配車計画作成部150は、配車要求及び発着地情報に基づいて、複数の候補となる車両(候補車両)Vの中から選択された一の車両Vに対する配車計画を作成して確定し、確定した配車計画に従った配車指示を一の車両Vに行う。本開示では、配車計画作成部150は、荷物配送の配車要求に対する配車計画を作成する時点で、他の配車要求を受け付けていない場合に、荷物配送の配車要求に対する配車計画を一時的に保留する。そして、配車計画作成部150は、該配車計画の保留中に、例えば新規の乗車の配車要求を受け付けた場合には、該配車計画の保留を解除して、荷物配送の配車要求と乗車の配車要求とに基づいて、いわゆる貨客混載となるように、配車計画を更新又は作成し直して、これをユーザに提案し、確定する。このように、配車計画は、確定前に、ユーザに提案されるので、ユーザは、提案された配車計画が自身の希望に沿っているか否かを判断することができる。配車計画作成部150は、確定した配車計画を配車計画データベース12fに格納するとともに、車両Vに配車指示するように配車指示部172に通知する。
The vehicle allocation plan creation unit 150 creates and finalizes a vehicle allocation plan for one vehicle V selected from a plurality of candidate vehicles (candidate vehicles) V, based on the vehicle allocation request and departure/arrival point information. A vehicle allocation instruction is given to one vehicle V according to the vehicle allocation plan. In the present disclosure, if the vehicle allocation plan creation unit 150 has not received any other vehicle allocation requests at the time of creating the vehicle allocation plan for the package delivery vehicle allocation request, the vehicle allocation plan creation unit 150 temporarily suspends the vehicle allocation plan for the package delivery vehicle allocation request. . If, for example, a new vehicle dispatch request is received while the vehicle dispatch plan is on hold, the vehicle dispatch plan creation unit 150 releases the suspension of the vehicle dispatch plan, and dispatches the dispatch request for baggage delivery and the dispatch of a ride. Based on the request, the vehicle allocation plan is updated or re-created so that it becomes a so-called mixed cargo/passenger loading, and this is proposed to the user and confirmed. In this way, since the vehicle allocation plan is proposed to the user before it is finalized, the user can determine whether the proposed vehicle allocation plan meets his or her wishes. The vehicle allocation plan creation unit 150 stores the confirmed 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.
より具体的には、配車計画作成部150は、取得された配車要求に従って、まず、走行ルート計画部160にルートパターンの導出を依頼する。ルートパターンは、決定済みの発着地(経由地)を通る経路に対して新たな発着地を追加した場合に全ての発着地を通るルートを示す。ルートパターンは、乗車の配車要求及び荷物配送の配車要求に基づいた貨客混載の配車計画によるルートパターンを含み得る。走行ルート計画部160は、ルートパターンの導出依頼に応答して、地図データベース12d及び車両情報データベース12eを参照して、配車要求に適合し得る1又はそれ以上の車両Vを候補車両vとして抽出し、抽出された候補車両vの各々について、発着地情報に従ったルートパターンを導出し、導出したルートパターンを配車計画作成部150に引き渡す。
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 the departure and arrival points when a new departure and arrival point is added to the route that passes through the determined departure and arrival points (stopover points). The route pattern may include a route pattern based on a freight and passenger mixed vehicle dispatch plan based on a vehicle dispatch request for boarding and a vehicle dispatch request for package delivery. In response to the route pattern derivation request, the driving route planning unit 160 refers to the map database 12d and the vehicle information database 12e and extracts one or more vehicles V that can match the vehicle allocation request as candidate vehicles v. For each of the extracted candidate vehicles v, a route pattern is derived according to the departure and arrival point information, and the derived route pattern is delivered to the vehicle allocation plan creation section 150.
例えば、図3に示すように、配車要求に基づく乗車地Req_PU及び降車地Req_DOとの地理的関係から、候補車両v(1)~v(3)が抽出されたとする。候補車両v(1)は、地点P(0)~P(1)~P(2)を通るルートが既に設定された車両である。また、候補車両v(2)は、待機場所Sで待機している車両である。また、候補車両v(3)は、地点P(0)~P(1)を通るルートが既に設定された車両である。今、候補車両v(1)についてみると、地点P(0)~P(2)に乗車地Req_PU及び降車地Req_DOが追加されるパターン(ルートパターン)は、全部で6パターンとなる。同様に、候補車両v(2)及びV(3)のルートパターンは、各々、1パターン及び3パターンとなる。
For example, as shown in FIG. 3, assume that candidate vehicles v(1) to v(3) are extracted from the geographical relationship between the pick-up location Req_PU and the drop-off location Req_DO based on the vehicle allocation 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. Further, candidate vehicle v(2) is a vehicle waiting at waiting location S. Further, candidate vehicle v(3) is a vehicle for which a route passing through points P(0) to P(1) has already been set. Now, regarding the candidate vehicle v(1), there are a total of six patterns (route patterns) in which the boarding place Req_PU and the getting off place Req_DO are added to the points P(0) to P(2). Similarly, the route patterns of candidate vehicles v(2) and V(3) are one pattern and three patterns, respectively.
図2に戻り、配車計画作成部150は、次に、走行ルート計画部160により導出された候補車両vの各ルートパターンに基づいて配車計画の作成を試みる。配車計画は、ルートパターンに対して起点となる待機場所及び終点となる待機場所を加えた運行ルートを含む。配車計画作成部150は、作成した配車計画のうち、所定の除外条件に該当する配車計画を削除又は除外して配車計画を絞り込む。所定の除外条件として、以下の(i)~(iv)が例示されるが、これらに限られない。
(i) 乗車人員及び/又は荷物積載量に関する条件
乗車人員及び/又は荷物積載量が、新規の配車要求によって規定の人員及び/又は積載量を超過する場合、該配車計画は除外される。
(ii) 乗車又は積荷時の遅延限界時間に関する条件
関連ユーザ(車両Vの予約が確定しているユーザ)の乗車時間及び/又は荷物の積荷時間が新規の配車要求によって遅延限界時間を超える場合、該配車計画は除外される。
(iii) 降車又は荷降時の遅延限界時間に関する条件
関連ユーザの降車時間及び/又は荷物の荷降時間が新規の配車要求によって遅延限界時間を超える場合、該配車計画は除外される。
(iv) 新規の配車要求を行ったユーザ及び/又は荷物の配車遅延限界時間に関する条件
新規の配車要求を行ったユーザの乗車時間及び/又は荷物の積荷時間が配車遅延限界時間を超える場合、該配車計画は除外される。 Returning to FIG. 2, the vehicle allocationplan 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 an operation route in which a waiting location serving as a starting point and a waiting location serving as an ending point are added to the route pattern. The vehicle allocation plan creation unit 150 narrows down the vehicle allocation plans by deleting or excluding vehicle allocation plans that meet predetermined exclusion conditions from among the created vehicle allocation plans. Examples of the predetermined exclusion conditions include (i) to (iv) below, but are not limited to these.
(i) Conditions regarding the number of passengers and/or cargo capacity If the number of passengers and/or cargo capacity exceeds the specified number of passengers and/or cargo capacity due to a new dispatch request, the dispatch plan will be excluded.
(ii) Conditions regarding the delay limit time when boarding or loading If the boarding time and/or luggage loading time of the related user (user whose reservation for vehicle V has been confirmed) exceeds the delay limit time due to a new vehicle allocation request, The vehicle allocation plan is excluded.
(iii) Conditions regarding the delay limit time when disembarking or unloading If the related user's alighting time and/or the unloading time of luggage exceeds the delay limit time due to a new vehicle allocation request, the vehicle allocation plan is excluded.
(iv) Conditions regarding the limit time for vehicle dispatch delay for the user who has made a new vehicle dispatch request and/or luggage If the boarding time and/or loading time of luggage for the user who has made a new vehicle dispatch request exceeds the vehicle dispatch delay limit time, the applicable Vehicle dispatch plans are excluded.
(i) 乗車人員及び/又は荷物積載量に関する条件
乗車人員及び/又は荷物積載量が、新規の配車要求によって規定の人員及び/又は積載量を超過する場合、該配車計画は除外される。
(ii) 乗車又は積荷時の遅延限界時間に関する条件
関連ユーザ(車両Vの予約が確定しているユーザ)の乗車時間及び/又は荷物の積荷時間が新規の配車要求によって遅延限界時間を超える場合、該配車計画は除外される。
(iii) 降車又は荷降時の遅延限界時間に関する条件
関連ユーザの降車時間及び/又は荷物の荷降時間が新規の配車要求によって遅延限界時間を超える場合、該配車計画は除外される。
(iv) 新規の配車要求を行ったユーザ及び/又は荷物の配車遅延限界時間に関する条件
新規の配車要求を行ったユーザの乗車時間及び/又は荷物の積荷時間が配車遅延限界時間を超える場合、該配車計画は除外される。 Returning to FIG. 2, the vehicle allocation
(i) Conditions regarding the number of passengers and/or cargo capacity If the number of passengers and/or cargo capacity exceeds the specified number of passengers and/or cargo capacity due to a new dispatch request, the dispatch plan will be excluded.
(ii) Conditions regarding the delay limit time when boarding or loading If the boarding time and/or luggage loading time of the related user (user whose reservation for vehicle V has been confirmed) exceeds the delay limit time due to a new vehicle allocation request, The vehicle allocation plan is excluded.
(iii) Conditions regarding the delay limit time when disembarking or unloading If the related user's alighting time and/or the unloading time of luggage exceeds the delay limit time due to a new vehicle allocation request, the vehicle allocation plan is excluded.
(iv) Conditions regarding the limit time for vehicle dispatch delay for the user who has made a new vehicle dispatch request and/or luggage If the boarding time and/or loading time of luggage for the user who has made a new vehicle dispatch request exceeds the vehicle dispatch delay limit time, the applicable Vehicle dispatch plans are excluded.
ここで、配車計画における上述した各種の遅延限界時間について説明する。図4は、本発明の一実施形態に係る配車管理装置による配車計画における各種の遅延限界時間を説明するための図である。
Here, the various delay limit times mentioned above in the vehicle allocation plan will be explained. FIG. 4 is a diagram for explaining various delay limit times in a vehicle allocation plan by a vehicle allocation management device according to an embodiment of the present invention.
同図に示すように、配車要求に基づくある車両Vの配車計画に従う予定運行時間T_Traは、配車要求受付時刻T_Reqから降車予定時刻(積降予定時刻)T_DOまでの時間をいう。また、配車遅延限界時間は、配車要求受付時刻T_Reqから乗車予定時刻(積荷予定時刻)T_PUまでの時間をいう。また、乗車遅延限界時間(積荷遅延限界時間)は、乗車予定時刻T_PUから乗車限界時刻TL_PUまでの時間をいう。また、降車遅延限界時間(積降遅延限界時間)は、出発予定時刻T_Depから降車限界時刻(積降遅延限界時刻)TL_DOまでの時間をいい、例えば乗車地(積荷地)から降車地(積降地)まで車両Vが直行した場合の時間の1.2倍の時間に設定される。なお、図中、保留限界時間は、配車計画の一時的な保留を許容する時間であり、配車要求受付時刻から計時される。保留限界時間は、所定の解除条件の一例である。
As shown in the figure, the scheduled operating time T_Tra according to the dispatch plan of a certain vehicle V based on the dispatch request is the time from the dispatch request reception time T_Req to the scheduled disembarkation time (scheduled loading/unloading time) T_DO. Further, the vehicle allocation delay limit time refers to the time from the vehicle allocation request reception time T_Req to the scheduled boarding time (scheduled loading time) T_PU. Further, 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. In addition, the deboarding delay limit time (loading/unloading delay limit time) refers to the time from the scheduled departure time T_Dep to the deboarding limit time (loading/unloading delay limit time) TL_DO, for example, from the boarding place (loading place) to the unloading place (loading/unloading place). The time is set to be 1.2 times the time it would take if the vehicle V went straight to the destination. In addition, in the figure, the holding limit time is a time that allows temporary holding of the vehicle allocation plan, and is measured from the time when the vehicle allocation request is received. The hold limit time is an example of a predetermined release condition.
一例として、配車計画作成部150は、あるルートパターンに基づく配車計画について、乗車地Req_PUの追加によって、関連ユーザの乗車時刻が乗車遅延限界時間を超えると判断する場合、該配車計画を除外する(除外条件(ii))。他の例として、配車計画作成部150は、あるルートパターンに基づく配車計画について、乗車地Req_PU及び降車地Req_DOの追加によって、関連ユーザの降車時刻が遅延限界時間を超えると判断する場合、該配車計画を除外する(除外条件(iii))。
As an example, when determining that the boarding time of the related user will exceed the boarding delay limit time due to the addition of boarding place Req_PU in a vehicle dispatch plan based on a certain route pattern, 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 alighting time of the related user will exceed the delay limit time due to the addition of pick-up point Req_PU and drop-off point Req_DO in a vehicle dispatch plan based on a certain route pattern, the vehicle dispatch plan creation unit 150 Exclude the plan (exclusion condition (iii)).
図2に再び戻り、配車計画作成部150は、次に、絞り込まれた配車計画について、所定の評価関数に従って評価値を算出し、算出された評価値に従って最適な一の配車計画を選定する。所定の評価関数は、例えば、乗車の配車要求であれば、乗車時刻から降車時刻までの乗車時間が短いほど評価値が高く、また、荷物配送の配車要求であれば、走行距離に基づく移動コストが小さいほど評価値が高くなるように定義された関数である。この場合、配車計画作成部150は、評価値が最大である配車計画を選択する。選定された配車計画は、暫定の(仮の)配車計画である。仮の配車計画とは、まだ修正又はキャンセルされる可能性がある、確定前の配車計画である。配車計画作成部150は、貨客混載の配車計画の場合には、その中で、評価関数による評価値が最大のものを選定する。このように、評価関数を用いることで、複数の配車計画の中から最適な配車計画を選定することができる。とりわけ、本開示では、乗車の配車要求と荷物配送の配車要求とで異なる評価関数を用いるので、運送内容により則した配車計画を選定することができる。
Returning to FIG. 2 again, the vehicle allocation plan creation unit 150 next calculates evaluation values for the narrowed-down vehicle allocation plans according to a predetermined evaluation function, and selects the optimal vehicle allocation plan according to the calculated evaluation values. For example, if the predetermined evaluation function is a request for dispatch of a ride, the shorter the riding time from the boarding time to the time of disembarkation, the higher the evaluation value, and if it is a request for dispatch of a package delivery, the evaluation value is based on the travel cost based on the distance traveled. This is a function defined such that the smaller the value, 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 (temporary) vehicle allocation plan. A tentative vehicle allocation plan is a vehicle allocation plan that has not yet been finalized and is subject to modification or cancellation. In the case of a mixed freight/passenger vehicle allocation plan, the vehicle allocation plan creation unit 150 selects the one with the highest evaluation value based on the evaluation function. In this way, by using the evaluation function, it is possible to select the optimal vehicle allocation plan from among a plurality of vehicle allocation plans. In particular, in the present disclosure, different evaluation functions are used for requests for vehicle allocation for boarding and requests for vehicle allocation for package delivery, so it is possible to select a vehicle allocation plan that is more in line with the content of transportation.
本開示では、配車計画作成部150は、配車計画が荷物配送の配車要求のみに基づいて作成されていると判断する場合、該配車計画の作成を一時的に保留し得る。配車管理装置10は、保留した配車計画を配車計画データベース12fに一旦格納する。そして、配車計画作成部150は、該配車計画の保留中に例えば新たな配車要求を受け付けた場合、該配車計画の保留を解除して、荷物配送の配車要求と乗車の配車要求とに基づいて新たにルートパターンを導出し、いわゆる貨客混載となるように、配車計画を作成し直して、これを確定する。
In the present disclosure, when the vehicle allocation plan creation unit 150 determines that the vehicle allocation plan is created based only on a vehicle allocation request for package delivery, the vehicle allocation plan creation unit 150 may temporarily suspend the creation of the vehicle allocation plan. The vehicle allocation management device 10 temporarily stores the suspended vehicle allocation plan in the vehicle allocation plan database 12f. If, for example, a new vehicle dispatch request is received while the vehicle dispatch plan is on hold, the vehicle dispatch plan creation unit 150 cancels the suspension of the vehicle dispatch plan and creates a new vehicle dispatch request based on the package delivery vehicle dispatch request and the ride dispatch request. A new route pattern is derived, a vehicle allocation plan is re-created so that it will be a so-called mixed cargo/passenger load, and this is finalized.
また、配車計画作成部150は、需要に依存する保留条件及び解除条件に従って、荷物配送の配車要求に基づく配車計画の作成を一時的に保留し、該保留を解除し得る。一例として、配車計画作成部150は、需要予測部122により予測された将来の需要量が第1の上限値を上回る場合に、該配車計画の作成を一時的に保留する。つまり、車両Vの将来の需要がある程度見込まれる場合、配車計画作成部150は、将来の配車要求に備えて、配車計画作成を一時的に保留する。これにより、荷物単体での配送を可能な限り回避することができ、将来の需要量を考慮した効率的な車両Vの運用が可能になる。
In addition, the vehicle allocation plan creation unit 150 can temporarily suspend the creation of a vehicle allocation plan based on a vehicle allocation request for package delivery and release the suspension, according to demand-dependent suspension conditions and release conditions. As an example, if the future demand predicted by the demand forecasting unit 122 exceeds the first upper limit, the vehicle allocation plan creation unit 150 temporarily suspends creation of the vehicle allocation plan. That is, when a certain amount of future demand for vehicles V is expected, the vehicle allocation plan creation unit 150 temporarily suspends the creation of the vehicle allocation plan in preparation for future vehicle allocation requests. As a result, it is possible to avoid delivering individual packages as much as possible, and it is possible to efficiently operate the vehicle V in consideration of future demand.
他の例として、配車計画作成部150は、現在需要算出部121により算出された現在の需要量に対する需要予測部122によって予測された将来の需要量の比が所定の変化率を上回る場合に、該配車計画の作成を一時的に保留する。つまり、車両Vの将来の需要に増加傾向が見込まれる場合、配車計画作成部150は、将来の配車要求に備えて、配車計画の作成を一時的に保留する。これにより、荷物単体での配送を可能な限り回避することができ、将来の需要量の急激な増加に対応した効率的な車両Vの運用が可能になる。
As another example, when the ratio of the future demand amount predicted by the demand forecasting section 122 to the current demand amount calculated by the current demand calculation section 121 exceeds a predetermined rate of change, the vehicle allocation plan creation section 150 Creation of the vehicle allocation plan is temporarily suspended. In other words, when the future demand for vehicles V is expected to increase, the vehicle allocation plan creation unit 150 temporarily suspends the creation of the vehicle allocation plan in preparation for future vehicle allocation requests. As a result, it is possible to avoid delivering individual packages as much as possible, and it is possible to efficiently operate the vehicle V in response to a sudden increase in demand in the future.
また、他の例として、配車計画作成部150は、現在需要算出部121により算出された現在の需要量が第2の上限値を上回る場合に、配車計画を保留しないか又は配車計画の保留を解除する。つまり、現在の需要量が高い場合には、配車計画作成部150は、需要の取りこぼしを防止するために、配車計画の保留を解除する。これにより、車両Vの高い稼働率を維持することができ、車両Vの効率的な運用ができるようになる。
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 suspend the vehicle allocation plan or suspends the vehicle allocation plan. unlock. That is, when the current demand is high, the vehicle allocation plan creation unit 150 releases the suspension of the vehicle allocation plan in order to prevent demand from being missed. Thereby, a high operating rate of the vehicle V can be maintained, and the vehicle V can be operated efficiently.
更に他の例として、配車計画作成部150は、荷物配送の配車要求が示す荷物の個数が所定の保留荷物限界数以上である場合に、配車計画の作成を保留せずに確定させても良い。また、この場合に、配車計画作成部150は、現在需要算出部121により算出された現在の需要量に対する需要予測部122によって予測された将来の需要量の比が所定の変化率を超える場合に、該所定の保留荷物限界数の値を小さくするよう変更しても良い。このように、荷物配送の配車要求が示す荷物の個数が所定の保留荷物限界数上であるか否かが判断されるので、車両Vの積載率を考慮した配車計画が可能になる。また、車両Vの将来の需要に増加傾向が見込まれる場合には、保留している荷物をなるべく配送しておいて、将来の需要に備えることができる。
As still another example, the vehicle allocation plan creation unit 150 may finalize the vehicle allocation plan without suspending the creation of the vehicle allocation plan if the number of packages indicated by the vehicle allocation request for package delivery is equal to or greater than a predetermined limit number of pending packages. . In addition, in this case, the vehicle allocation plan creation unit 150 determines that when the ratio of the future demand amount predicted by the demand forecasting unit 122 to the current demand amount calculated by the current demand calculation unit 121 exceeds a predetermined rate of change. , the predetermined limit number of held baggage may be changed to a smaller value. In this way, it is determined whether or not the number of packages indicated by the vehicle allocation request for package delivery is above the predetermined limit number of held packages, making it possible to plan the vehicle allocation in consideration of the loading rate of the vehicle V. Furthermore, if the future demand for the vehicle V is expected to increase, it is possible to prepare for future demand by delivering as much of the held cargo as possible.
配車計画作成部150は、荷物配送の配車要求に対する保留限界時間を任意に設定し得る。一例として、配車計画作成部150は、荷物配送の配車要求を行ったユーザの属性情報に応じて、保留限界時間を設定し得る。より具体的には、荷物配送の配車要求を行ったユーザが一般ユーザである場合には、保留限界時間は比較的短い第1の保留限界時間として設定される一方、ユーザが荷物配送業者である場合には、保留限界時間は第1の保留限界時間により長い第2の第1の保留限界時間として設定される。つまり、一般ユーザによる単発的な荷物配送の配車要求ほど保留限界時間を短く設定する一方、荷物配送業者には配車計画のある程度の保留を許容してもらうことで、一般ユーザの配車サービスに対する満足度を向上させ、配車サービスの更なる活性化が期待できる。
The vehicle allocation plan creation unit 150 can arbitrarily set a hold limit time for a vehicle allocation request for package delivery. As an example, the vehicle allocation plan creation unit 150 may set a holding limit time according to attribute information of a user who has made a request for vehicle allocation for package delivery. More specifically, if the user who requested a vehicle for parcel delivery is a general user, the holding limit time is set as a relatively short first holding limit time, whereas if the user is a parcel delivery company. In this case, the hold limit time is set as a second first hold limit time that is longer than the first hold limit time. In other words, by setting the hold limit time shorter for a one-off package delivery request made by a general user, and by allowing package delivery companies to hold their vehicle dispatch plans to a certain extent, it is possible to improve the satisfaction of general users with the ride dispatch service. It is expected that this will lead to further revitalization of ride-hailing services.
他の例として、配車計画作成部150は、荷物配送の配車要求が示す荷物属性情報に応じて、保留限界時間を設定し得る。より具体的には、荷物が要冷蔵品や生鮮食料品等のように配送時期の後ろ倒しや遅延がその荷物の価値を減じるおそれがある場合には、保留限界時間は比較的短い第1の保留限界時間として設定される。つまり、生鮮食料品等に対する荷物配送の配車要求ほど保留限界時間を短く設定することで、短時間で素早く配送しなければならないような荷物の配送サービスにも対応が可能になる。
As another example, the vehicle allocation plan creation unit 150 may set the holding limit time according to the package attribute information indicated by the vehicle allocation request for package delivery. More specifically, if the package is a product that requires refrigeration or perishable food, and if there is a risk that delaying or delaying the delivery time will reduce the value of the package, the holding time limit is relatively short. Set as the hold limit time. In other words, by setting a shorter holding limit time for requests for delivery of parcels such as perishable foods, it becomes possible to support delivery services for parcels that must be delivered quickly in a short period of time.
更に他の例として、配車計画作成部150は、荷物配送の配車要求が示す積荷地情報に応じて、保留限界時間を設定し得る。より具体的には、荷物の積荷地が一般ユーザの自宅である場合には、保留限界時間は第1の保留限界時間として設定される一方、荷物の積荷地が荷物配送業者の事業所である場合には、保留限界時間は第1の保留限界時間により長い第2の第1の保留限界時間として設定される。つまり、一般ユーザによる単発的な荷物配送の配車要求ほど保留限界時間を短く設定する一方、荷物配送業者には配車計画のある程度の保留を許容してもらうことで、一般ユーザの配車サービスに対する満足度を向上させ、配車サービスの更なる活性が期待できる。
As yet another example, the vehicle allocation plan creation unit 150 may set the holding limit time according to the loading point information indicated by the vehicle allocation request for package delivery. More specifically, if the loading point of the package is the general user's home, the holding limit time is set as the first holding limit time, whereas if the loading point of the package is the business office of the package delivery company. In this case, the hold limit time is set as a second first hold limit time that is longer than the first hold limit time. In other words, by setting the hold limit time shorter for a one-off package delivery request made by a general user, and by allowing package delivery companies to hold their vehicle dispatch plans to a certain extent, it is possible to improve the satisfaction of general users with the ride dispatch service. It is expected that this will improve ride-hailing services and further revitalize ride-hailing services.
車両通信インターフェース部170は、通信ネットワークNを介して、車両Vとの間で各種の情報をやり取りする。例えば、車両通信インターフェース部170は、車両Vの位置情報を含む車両情報を取得する車両情報取得部171と、配車計画に従って車両Vに移動を指示する配車指示部172とを備える。
The vehicle communication interface unit 170 exchanges various 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.
車両情報取得部171は、制御装置300の通信部310との間で通信を行い、位置情報取得部320によって取得された位置情報等を取得する。また、配車指示部172は、配車計画作成部150の指示に従い、配車計画データベース12fを参照し、対応する配車計画を特定し、特定された配車計画に従って車両Vに運行指示を送信する。運行指示を受信した車両Vの制御装置300は、ナビゲーション機能により、例えばユーザインターフェース(図中「UI」と表示)330上に、配車計画に従った走行ルートを表示する。
The vehicle information acquisition unit 171 communicates with the communication unit 310 of the control device 300 and acquires the position information etc. acquired by the position information acquisition unit 320. In addition, the vehicle allocation instruction unit 172 refers to the vehicle allocation plan database 12f in accordance with the instruction from the vehicle allocation plan creation unit 150, identifies a corresponding vehicle allocation plan, and transmits an operation instruction to the vehicle V according to the identified vehicle allocation plan. The control device 300 of the vehicle V, which has received the operation instruction, uses the navigation function to display a travel route according to the vehicle allocation plan, for example, on a user interface (indicated as "UI" in the figure) 330.
図5は、本発明の一実施形態に係る配車管理システムにおける配車サービスの概要を説明するためのシーケンスチャートである。
FIG. 5 is a sequence chart for explaining an overview of a vehicle dispatch service in a vehicle dispatch management system according to an embodiment of the present invention.
まず、車両Vは、GPSシステムから取得される自身の位置情報を、所定のタイミングで、配車管理装置10に送信する(S501)。なお、車両Vによる位置情報の取得及び送信は、定期的に又は配車管理装置10からの送信要求に応じて行われる。これにより、配車管理装置10は、車両Vから送信される位置情報を取得する(S502)。
First, the vehicle V transmits its own position information obtained from the GPS system to the vehicle allocation management device 10 at a predetermined timing (S501). Note that the vehicle V acquires and transmits the position information periodically or in response to a transmission request from the vehicle allocation management device 10. Thereby, the vehicle allocation management device 10 acquires the position information transmitted from the vehicle V (S502).
一方、配車サービスを利用しようとするユーザは、端末装置20に実装された配車アプリを実行して、ユーザインターフェース上に表示された配車要求画面に対して配車要求のための必要な情報を入力し、これにより、端末装置20は、配車要求を配車管理装置10に送信する(S503)。例えば、乗車を希望するユーザは、乗車地及び降車地並びに乗車人数等を入力する。また、荷物配送を希望するユーザは、荷積地及び荷降地並びに荷物の個数、サイズ及び種類等を入力する。乗車地及び降車地(荷積地及び荷降地)は、例えば、配車アプリにより表示された地理的マップから選択され得る。また、乗車地(荷積地)は、例えばユーザのスマートフォンに搭載されたGPS機能により取得される現在位置であっても良い。
On the other hand, a user who wishes to use a ride-hailing service executes a ride-hailing application installed on the terminal device 20 and inputs the necessary information for a ride-hailing request on the ride-hailing request screen displayed on the user interface. , Thereby, the terminal device 20 transmits a vehicle allocation request to the vehicle allocation management device 10 (S503). For example, a user who wishes to ride a vehicle inputs the boarding location, the alighting location, the number of passengers, etc. Further, a user who wishes to have a package delivered inputs the loading and unloading locations, the number, size, type, etc. of the packages. The pick-up and drop-off locations (loading and unloading locations) may be selected from, for example, a geographic map displayed by the ride-hailing app. Further, the boarding place (loading place) may be the current position obtained by, for example, a GPS function installed in the user's smartphone.
配車管理装置10は、端末装置20から配車要求を受信すると(S504)、受信した配車要求に基づいて車両Vの配車計画を作成し、これをユーザに提案するために、作成した配車計画の内容を端末装置20に送信する(S505)。なお、受信された配車要求が荷物配送の配車要求である場合、配車管理装置10は、該荷物配送の配車要求に基づいて配車計画を作成する時点において、他の配車要求を受信していない場合には、該荷物配送の配車要求に基づく車両Vの配車計画の作成を一時的に保留し、所定の条件の下で、保留を解除して、必要に応じて配車計画を更新又は作成し直す。
When the vehicle allocation management device 10 receives the vehicle allocation request from the terminal device 20 (S504), it creates a vehicle allocation plan for the vehicle V based on the received vehicle allocation request, and in order to propose this to the user, the vehicle allocation management device 10 creates the contents of the created vehicle allocation plan. is transmitted to the terminal device 20 (S505). In addition, when the received vehicle allocation request is a vehicle allocation request for package delivery, the vehicle allocation management device 10 does not receive any other vehicle allocation request at the time of creating a vehicle allocation plan based on the vehicle allocation request for package delivery. , temporarily suspends the creation of a vehicle dispatch plan for vehicle V based on the vehicle dispatch request for said package delivery, releases the suspension under predetermined conditions, and updates or re-creates the vehicle dispatch plan as necessary. .
端末装置20は、配車計画の内容を受信すると、これをユーザインターフェース上に配車計画提案画面として表示して、提案した配車計画に対する承諾又は拒否(諾否)をユーザに促す(S506)。ユーザが配車計画提案画面に対して諾否を入力すると、これを受けて、端末装置20は、諾否通知を配車管理装置10に送信し(S507)、配車管理装置10は、端末装置20から送信される諾否通知を受信する(S508)。例えば、諾否通知が配車計画の承諾を示すものである場合、配車管理装置10は、配車計画に従った車両Vの配車計画を確定し、配車予約の確定通知を端末装置20に送信するともに、車両Vに対して該配車計画に従った配車指示を送信する(S509)。
When the terminal device 20 receives the contents of the vehicle allocation plan, it displays this as a vehicle allocation plan proposal screen on the user interface and prompts the user to accept or reject (accept or reject) the proposed vehicle allocation plan (S506). When the user inputs acceptance/disapproval on the vehicle allocation plan proposal screen, in response to this, the terminal device 20 transmits a notification of acceptance/disapproval to the vehicle allocation management device 10 (S507), and the vehicle allocation management device 10 receives the notification sent from the terminal device 20. A notification of acceptance/rejection is received (S508). For example, when the approval/rejection notification indicates approval of the vehicle allocation plan, the vehicle allocation management device 10 finalizes the vehicle allocation plan for the vehicle V according to the vehicle allocation plan, sends a confirmation notification of the vehicle allocation reservation to the terminal device 20, and A vehicle allocation instruction according to the vehicle allocation plan is transmitted to vehicle V (S509).
端末装置20は、配車予約の確定通知を受信すると、これをユーザインターフェース上に表示してユーザに配車の予約が確定したことを知らせる(S510)。一方、車両Vは、配車指示を受信すると、ドライバをナビゲートするために、例えばナビゲーション画面に配車指示が示す配車計画に従った運行ルートを表示する(S511)。これにより、ドライバは、ユーザの配車要求に応じたオンデマンド方式の車両Vの運行が可能になる。
When the terminal device 20 receives the confirmation notification of the vehicle allocation reservation, it displays this on the user interface to inform the user that the vehicle allocation reservation has been confirmed (S510). On the other hand, upon receiving the vehicle allocation instruction, the vehicle V displays, for example, on the navigation screen an operating route according to the vehicle allocation plan indicated by the vehicle allocation instruction, in order to navigate the driver (S511). This allows the driver to operate the vehicle V in an on-demand manner in response to a user's dispatch request.
図6A及び6Bは、本発明の一実施形態に係る配車管理装置による配車管理処理の一例を説明するためのフローチャートである。かかる処理は、配車管理装置が、プロセッサの制御の下、配車管理サーバプログラムを実行することにより、各種のハードウェア資源との協働がなされ、実現される。
FIGS. 6A and 6B are flowcharts for explaining an example of vehicle allocation management processing by the vehicle allocation management device according to an embodiment of the present invention. Such processing is realized by the vehicle dispatch management device executing the vehicle dispatch management server program under the control of the processor, thereby cooperating with various hardware resources.
同図Aに示すように、配車管理装置10は、ユーザからの新規の配車要求があるまで待機している(S601)。一方で、例えば、乗車や荷物の配送を希望するユーザは、端末装置20のユーザインターフェース上で配車アプリを操作して、配車要求を入力する。配車管理装置10は、ユーザからの配車要求があると(S601のYes)、該配車要求に基づいて、地図データベース12dを参照し、発着地を決定する(S602)。
As shown in Figure A, the vehicle allocation management device 10 waits until a new vehicle allocation request is received from the user (S601). On the other hand, for example, a user who desires a ride or delivery of luggage operates a ride allocation application on the user interface of the terminal device 20 and inputs a ride allocation request. When the vehicle allocation management device 10 receives a vehicle allocation request from the user (S601: Yes), the vehicle allocation management device 10 refers to the map database 12d and determines departure and arrival points based on the vehicle allocation request (S602).
次に、配車管理装置10は、発着地に従って1又はそれ以上の候補車両vを抽出する(S603)。例えば、配車管理装置10は、出発地の近傍で待機している又は移動中である車両Vを候補車両vとして抽出する。
Next, the vehicle allocation management device 10 extracts one or more candidate vehicles v according to the departure and arrival points (S603). For example, the vehicle allocation management device 10 extracts a vehicle V that is waiting or moving near the departure point as a candidate vehicle v.
次に、配車管理装置10は、抽出された各候補車両vについて、地図データベース12dを参照して、ルートパターンを導出する(S604)。上述したように、ルートパターンは、決定済みの発着地(経由地)を通る経路に対して新たな発着地を追加した場合に全ての発着地を通るルートを示す。続いて、配車管理装置10は、導出されたルートパターンに基づいて配車計画を作成する(S605)。配車計画は、ルートパターンに対して起点となる待機場所及び終点となる待機場所を加えた運行ルートを含む。
Next, the vehicle allocation 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 the departure and arrival points when a new departure and arrival point is added to the route that passes through the determined departure and arrival points (stopover points). Subsequently, the vehicle allocation management device 10 creates a vehicle allocation plan based on the derived route pattern (S605). The vehicle allocation plan includes an operation route in which a waiting location serving as a starting point and a waiting location serving as an ending point are added to the route pattern.
次に、配車管理装置10は、作成された配車計画のうち、所定の除外条件に該当するたさない配車計画を除外して配車計画を絞り込む(S606)。例えば、配車管理装置10は、新規の配車要求を行ったユーザの乗車時間が配車遅延限界時間を超える場合、該配車計画を除外する。
Next, the vehicle allocation management device 10 narrows down the vehicle allocation plans by excluding the vehicle allocation plans that do not meet the predetermined exclusion conditions from among the created vehicle allocation plans (S606). For example, if the boarding time of the user who has made a new vehicle allocation request exceeds the vehicle allocation delay limit time, the vehicle allocation management device 10 excludes the vehicle allocation plan.
次に、配車管理装置10は、絞り込まれた配車計画について、所定の評価関数に従って評価値を算出し、算出された評価値が最大となる一の配車計画を選定する(S607)。貨客混載の配車計画がある場合には、配車計画作成部150は、その中で、評価関数による評価値が最大のものを選定する。
Next, the vehicle allocation management device 10 calculates evaluation values for the narrowed-down vehicle allocation plans according to a predetermined evaluation function, and selects one vehicle allocation plan with the highest calculated evaluation value (S607). If there is a vehicle allocation plan for mixed cargo and passenger loading, the vehicle allocation plan creation unit 150 selects the one with the highest evaluation value based on the evaluation function.
配車管理装置10は、続いて、配車計画データベース12fを参照し、一時的に保留している配車計画があるか否かを判断する(S608)。保留中の配車計画は、本開示では、単独の荷物配送の配車要求に基づく配車計画である。配車管理装置10は、一時的に保留している配車計画がないと判断する場合(S608のNo)、続いて、配車管理装置10は、現在の配車要求が荷物の配車要求であるか否かを判断する(S609)。一方、配車管理装置10は、一時的に保留している配車計画があると判断する場合(S608のYes)、後述するように、配車管理装置10は、現在の配車要求に基づく配車計画と保留中の配車計画とに基づいて、配車計画を更新又は作成し直す(S620)。
The vehicle allocation management device 10 then refers to the vehicle allocation plan database 12f and determines whether there is a temporarily suspended vehicle allocation plan (S608). A pending dispatch plan, in this disclosure, is a dispatch plan based on a dispatch request for a single package delivery. When the vehicle dispatch management device 10 determines that there is no temporarily pending vehicle dispatch plan (No in S608), the vehicle dispatch management device 10 then determines whether the current vehicle dispatch request is a luggage dispatch request. (S609). On the other hand, when the vehicle dispatch management device 10 determines that there is a temporarily pending vehicle dispatch plan (Yes in S608), as will be described later, the vehicle dispatch management device 10 determines that there is a vehicle dispatch plan based on the current vehicle dispatch request and a pending vehicle dispatch plan. The vehicle allocation plan is updated or re-created based on the vehicle allocation plan (S620).
配車管理装置10は、現在の配車要求が荷物の配車要求でないと判断する場合(S609のNo)、続いて、配車管理装置10は、配車計画が貨客混載であるか否かを判断する(S610)。つまり、配車計画が再作成された場合(S620)、貨客混載である可能性がある。
When the vehicle dispatch management device 10 determines that the current vehicle dispatch request is not a request for cargo dispatch (No in S609), the vehicle dispatch management device 10 then determines whether the vehicle dispatch plan is for mixed freight and passenger loading (S610). ). In other words, when the vehicle allocation plan is re-created (S620), there is a possibility that freight and passengers will be mixed.
配車管理装置10は、現在の配車計画が貨客混載であると判断する場合(S610のYes)、配車管理装置10は、該配車計画の内容をユーザに提案する(図6BのS612)。すなわち、配車管理装置10は、作成した現在の配車計画の内容を端末装置20に送信し、これに応答して、端末装置20は、ユーザインターフェース上にその内容を表示して、ユーザに配車計画の諾否を促す。
When the vehicle allocation management device 10 determines that the current vehicle allocation plan is for mixed cargo and passenger loading (Yes in S610), the vehicle allocation management device 10 proposes the contents of the vehicle allocation 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 to inform the user of the vehicle dispatch plan. Ask them to accept or reject the request.
一方、配車管理装置10は、現在の配車要求が荷物の配車要求であると判断する場合(S609のYes)、更に、配車管理装置10は、該配車要求が示す荷物の個数が所定の保留荷物限界数以上であるか否かを判断する(S611)。配車管理装置10は、該配車要求が示す荷物の個数が所定の保留荷物限界数以上であると判断する場合には(S611のYes)、配車管理装置10は、該配車計画の内容をユーザに提案する(S612)。このように、荷物配送の配車要求が示す荷物の個数が所定の保留荷物限界数以上であるか否かが判断されるので、車両Vの積載率を考慮した配車計画が可能になる。なお、個々の荷物のサイズが小さい場合は、たとえその個数が多くても、その容量(体積)としては小さく、それらの荷物を車両Vに積載しても積載率は低いままとなる。そこで、配車管理装置10は、配車要求が示す荷物の個数に基づく判断に代えて又は追加的に、荷物が所定のサイズ以上であるか否かを判断するようにしても良い。
On the other hand, when the vehicle dispatch management device 10 determines that the current vehicle dispatch request is a request for dispatching packages (Yes in S609), the vehicle dispatch management device 10 further determines that the number of packages indicated by the vehicle dispatch request is a predetermined number of held packages. It is determined whether the number is greater than or equal to the limit number (S611). If the vehicle dispatch management device 10 determines that the number of packages indicated by the vehicle dispatch request is equal to or greater than the predetermined limit number of held packages (Yes in S611), the vehicle dispatch management device 10 informs the user of the contents of the vehicle dispatch plan. A proposal is made (S612). In this way, it is determined whether or not the number of packages indicated by the vehicle allocation request for package delivery is equal to or greater than the predetermined limit number of retained packages, making it possible to plan the vehicle allocation in consideration of the loading rate of the vehicle V. Note that when the size of each piece of baggage is small, even if the number of pieces is large, the capacity (volume) is small, and even if the baggage is loaded onto the vehicle V, the loading rate remains low. Therefore, instead of or in addition to the determination based on the number of packages indicated by the vehicle dispatch request, the vehicle allocation management device 10 may determine whether the package is larger than a predetermined size.
配車管理装置10は、配車計画の提案に対してユーザから承諾を受け付けたか否かを判断する(S613)。配車管理装置10は、配車計画の提案に対してユーザから承諾を受け付けた場合(S613のYes)、配車管理装置10は、現在の配車計画を確定する(S614)。配車管理装置10は、確定した配車計画を配車計画データベース12fに格納する。続いて、配車管理装置10は、配車予約の確定通知を端末装置20に送信するとともに、配車計画に基づく配車指示を車両Vに送信する(S615)。
The vehicle allocation management device 10 determines whether consent has been received from the user for the vehicle allocation plan proposal (S613). When the vehicle allocation management device 10 receives consent from the user for the vehicle allocation plan proposal (S613: Yes), the vehicle allocation management device 10 finalizes the current vehicle allocation plan (S614). The vehicle allocation management device 10 stores the confirmed vehicle allocation plan in the vehicle allocation plan database 12f. Subsequently, the vehicle allocation management device 10 transmits a confirmation notification of the vehicle allocation reservation to the terminal device 20, and also transmits a vehicle allocation instruction based on the vehicle allocation plan to the vehicle V (S615).
これに対して、配車管理装置10は、配車計画の提案に対してユーザから不承諾(拒否)を受け付けた場合(S613のNo)、該ユーザの配車要求に基づく現在の配車計画をキャンセルする(S616)。この場合、配車管理装置10は、配車計画の再作成のために使用された一時的に保留されていた配車計画を元の保留中の配車計画に戻す。ユーザは、別の配車サービスを希望する場合には、新たな配車要求を行うことになる。
On the other hand, when the vehicle allocation management device 10 receives a disapproval (rejection) from the user to the vehicle allocation plan proposal (No in S613), the vehicle allocation management device 10 cancels the current vehicle allocation plan based on the user's vehicle allocation request ( S616). In this case, the vehicle allocation management device 10 returns the temporarily suspended vehicle allocation plan used to recreate the vehicle allocation plan to the original pending vehicle allocation plan. If the user desires another vehicle dispatch service, he or she will make a new vehicle dispatch request.
一方、配車管理装置10は、該配車要求における荷物の個数が所定の保留荷物限界数以上でないと判断する場合(S611のNo)、又は現在の配車計画が貨客混載でないと判断する場合(S610のNo)、配車管理装置10は、保留している配車計画の保留経過時間が保留限界時間を超えたか否かを判断する(図6BのS617)。これは、現在の配車計画が荷物配送の配車要求を受け付けた時点から保留限界時間を超える場合には、それ以上の荷物配送の遅延が発生しないようにするためである。
On the other hand, if the vehicle allocation management device 10 determines that the number of luggage in the vehicle allocation request is not equal to or greater than the predetermined limit number of held luggage (No in S611), or if it determines that the current vehicle allocation plan is not a combination of cargo and passengers (in S610) No), the vehicle allocation management device 10 determines whether the elapsed hold time of the held vehicle allocation plan exceeds the hold limit time (S617 in FIG. 6B). This is to prevent further delays in package delivery if the current vehicle allocation plan exceeds the hold limit time from the time when the package delivery request for vehicle allocation is received.
配車管理装置10は、保留している配車計画の保留経過時間が保留限界時間を超えたと判断する場合(S617のYes)、上述したように、現在の配車計画の内容をユーザに提案する(S612)。つまり、配車管理装置10は、保留している配車計画に基づいて再作成された配車計画の保留経過時間が保留限界時間を超えたと判断する場合には、配車計画の保留を解除することになる。このように、保留している配車計画の保留経過時間が保留限界時間を超えた場合には、配車計画の保留を解除しているので、配車要求に対するユーザの待ち時間を必要以上に長くすることを防止することができる。
When the vehicle dispatch management device 10 determines that the pending elapsed time of the pending vehicle dispatch plan has exceeded the pending limit time (S617: Yes), as described above, the vehicle dispatch management device 10 proposes the contents of the current vehicle dispatch plan to the user (S612). ). In other words, when the vehicle dispatch management device 10 determines that the elapsed time on hold of the vehicle dispatch plan recreated based on the put on hold vehicle dispatch plan has exceeded the hold limit time, the vehicle dispatch management device 10 releases the hold on the vehicle dispatch plan. . In this way, if the elapsed time on hold for a vehicle dispatch plan exceeds the holding limit time, the vehicle dispatch plan is released from hold, so the user's waiting time for a vehicle dispatch request may be longer than necessary. can be prevented.
一方、配車管理装置10は、配車計画の保留経過時間が保留限界時間を超えていないと判断する場合(S617のNo)、続いて、配車管理装置10は、配車計画が需要に依存する保留条件を満たすか否かを判断する(S618)。一例として、配車管理装置10は、予測された将来の需要量が第1の上限値を上回る場合に、配車計画が保留条件を満たしているものと判断する(S618のYes)。他の例として、配車管理装置10は、現在の需要量が所定の下限値を下回る場合には、配車計画が保留条件を満たしていないものと判断する(S618のNo)。
On the other hand, if the vehicle dispatch management device 10 determines that the elapsed time on hold of the vehicle dispatch plan does not exceed the hold limit time (No in S617), then the vehicle dispatch management device 10 determines whether the vehicle dispatch plan is on hold under the demand-dependent hold conditions (No in S617). It is determined whether or not the following is satisfied (S618). As an example, the vehicle allocation management device 10 determines that the vehicle allocation plan satisfies the reservation condition when the predicted future demand exceeds the first upper limit value (Yes in S618). As another example, if the current demand is below a predetermined lower limit, the vehicle allocation management device 10 determines that the vehicle allocation plan does not satisfy the reservation condition (No in S618).
配車管理装置10は、配車計画が保留条件を満たさないと判断する場合(S618のNo)、配車管理装置10は、上述したように、現在の配車計画の内容をユーザに提案する(S612)。これに対して、配車管理装置10は、配車計画が保留条件を満たすと判断する場合(S618のYes)、現在の配車計画の保留を決定する(S619)。配車管理装置10は、保留を決定した配車計画を配車計画データベース12fに格納する。保留された配車計画は、次の配車要求があった場合に参照される。
When the vehicle allocation management device 10 determines that the vehicle allocation plan does not satisfy the reservation conditions (No in S618), the vehicle allocation management device 10 proposes the contents of the current vehicle allocation plan to the user (S612). On the other hand, if the vehicle allocation management device 10 determines that the vehicle allocation plan satisfies the suspension conditions (S618: Yes), it determines to suspend the current vehicle allocation plan (S619). The vehicle allocation management device 10 stores the vehicle allocation plan that has been decided to be put on hold in the vehicle allocation plan database 12f. The suspended vehicle dispatch plan will be referenced when the next vehicle dispatch request is made.
図6Aに戻り、配車管理装置10は、保留中の配車計画があると判断する場合(S608のYes)、配車管理装置10は、現在の配車計画と保留中の配車計画に基づいて、配車計画の再作成を行う(S620)。例えば、新規の乗車の配車要求があった場合、配車管理装置10は、貨客混載となるように配車計画を再作成する。これにより、車両Vの積載率を高めることができ、効率的運用が可能になる。
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 creates a vehicle dispatch plan based on the current vehicle dispatch plan and the pending vehicle dispatch plan. is re-created (S620). For example, when a new vehicle allocation request is received, the vehicle allocation management device 10 re-creates a vehicle allocation plan so that freight and passengers are mixed. Thereby, the loading rate of the vehicle V can be increased, and efficient operation becomes possible.
すなわち、配車計画の再作成処理は、現在の配車要求に基づく配車計画と保留中の配車計画とに基づいて、配車管理装置10がS603からS607の処理に対応する処理を実行することにより行われる。
That is, the vehicle allocation plan re-creation process is performed by the vehicle allocation management device 10 executing 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. .
より具体的には、配車管理装置10は、現在の配車要求に基づく配車計画が示す発着地と保留中の配車計画が示す発着地に基づいて候補車両vを抽出する(S603に対応する処理)。続いて、配車管理装置10は、抽出された各候補車両vについて、ルートパターンを導出する(S604に対応する処理)。次に、配車管理装置10は、導出されたルートパターンに基づいて配車計画を作成し直す(S605に対応する処理)。続いて、配車管理装置10は、再作成された配車計画のうち、所定の除外条件に該当するたさない配車計画を除外して運行ルートを絞り込む(S606に対応する処理)。そして、配車管理装置10は、配車管理装置10は、絞り込まれた配車計画について、所定の評価関数に従って評価値を算出し、算出された評価値が最大となる一の配車計画を選定する(S607に対応する処理)。
More specifically, the vehicle allocation management device 10 extracts candidate vehicles v based on the departure and arrival points indicated by the vehicle allocation plan based on the current vehicle allocation request and the departure and arrival points indicated by the pending vehicle allocation plan (processing corresponding to S603). . Subsequently, the vehicle allocation management device 10 derives a route pattern for each extracted candidate vehicle v (processing corresponding to S604). Next, the vehicle allocation management device 10 re-creates a vehicle allocation plan based on the derived route pattern (processing corresponding to S605). Subsequently, the vehicle allocation management device 10 narrows down the operation route by excluding, from among the re-created vehicle allocation plans, unsatisfactory vehicle allocation plans that meet predetermined exclusion conditions (processing corresponding to S606). Then, the vehicle allocation management device 10 calculates evaluation values for the narrowed-down vehicle allocation plans according to a predetermined evaluation function, and selects one vehicle allocation plan with the largest calculated evaluation value (S607 ).
配車管理装置10は、一の配車計画を選定すると、上述したように、現在の配車要求が荷物の配車要求であるか否かを判断し(S609)、同様に、以降の処理を行う。
When the vehicle allocation management device 10 selects one vehicle allocation plan, as described above, it determines whether the current vehicle allocation request is a luggage allocation request (S609), and similarly performs the subsequent processing.
なお、上述した例では、配車管理装置10は、ユーザからの配車要求の取得(S601)に応答して、保留中の配車計画があるか否かを判断している(S608)が、これに限られない。図示されていないが、配車管理装置10は、配車要求の取得がない場合であっても、保留中の配車計画の保留経過時間が保留限界時間を超えたか否かを判断し、保留経過時間が保留限界時間を超えたと判断する場合には、該配車計画の保留を解除し、ユーザに提案するようにしても良い。
In the above example, the vehicle allocation management device 10 determines whether there is a pending vehicle allocation plan (S608) in response to obtaining a vehicle allocation request from the user (S601). Not limited. Although not shown, the vehicle dispatch management device 10 determines whether or not the elapsed time of the pending vehicle dispatch plan has exceeded the limit time for the pending vehicle dispatch plan, even if no vehicle dispatch request has been obtained. If it is determined that the hold limit time has been exceeded, the hold of the vehicle allocation plan may be canceled and a proposal may be made to the user.
以上のように、本実施形態によれば、荷物配送の配車要求に基づく配車計画を所定の条件で一時的に保留するので、車両Vの効率的な運用が可能になる。とりわけ、一時的に保留となった配車計画は、その後の配車要求に基づく配車計画と合わせて再作成されるので、車両Vの配車効率及び/又は積載率が向上するようになる。また、作成された配車計画はユーザに提案され、これに対してユーザが承諾した場合に、配車計画が確定されるので、種々の配車要求に対して車両Vの柔軟な運用を行うことができ、配車効率及び/又は積載率を向上させることができる。
As described above, according to the present embodiment, the vehicle allocation plan based on the vehicle allocation request for package delivery is temporarily suspended under predetermined conditions, so that the vehicle V can be efficiently operated. In particular, since the temporarily suspended vehicle allocation plan is re-created together with the vehicle allocation plan based on the subsequent vehicle allocation request, the vehicle allocation efficiency and/or loading rate of the vehicle V is improved. In addition, the created vehicle allocation plan is proposed to the user, and if the user accepts the proposal, the vehicle allocation plan is finalized, so vehicles V can be operated flexibly in response to various vehicle allocation requests. , vehicle allocation efficiency and/or loading rate can be improved.
上記各実施形態は、本発明を説明するための例示であり、本発明をこれらの実施形態にのみ限定する趣旨ではない。本発明は、その要旨を逸脱しない限り、さまざまな形態で実施することができる。
Each of the above embodiments is an illustration for explaining the present invention, and is not intended to limit the present invention only to these embodiments. The present invention can be implemented in various forms without departing from the gist thereof.
例えば、本明細書に開示される方法においては、その結果に矛盾が生じない限り、ステップ、動作又は機能を並行して又は異なる順に実施しても良い。説明されたステップ、動作及び機能は、単なる例として提供されており、ステップ、動作及び機能のうちのいくつかは、発明の要旨を逸脱しない範囲で、省略でき、また、互いに結合させることで一つのものとしてもよく、また、他のステップ、動作又は機能を追加してもよい。
For example, in the methods disclosed herein, steps, acts, or functions may be performed in parallel or in a different order unless the results are inconsistent. The steps, acts, and functions described are provided by way of example only, and some of the steps, acts, and functions may be omitted or combined with each other without departing from the spirit of the invention. It is also possible to add other steps, actions, or functions.
また、本明細書では、さまざまな実施形態が開示されているが、一の実施形態における特定のフィーチャ(技術的事項)を、適宜改良しながら、他の実施形態に追加し、又は該他の実施形態における特定のフィーチャと置換することができ、そのような形態も本発明の要旨に含まれる。
Further, although various embodiments are disclosed in this specification, specific features (technical matters) in one embodiment may be added to other embodiments while improving them as appropriate, or Certain features in the embodiments may be replaced and such forms are within the scope of the invention.
1…配車管理システム
10…配車管理装置
110…フロントエンド処理部
120…需要情報取得部
121…現在需要算出部
122…需要予測部
130…配車要求取得部
140…発着地決定部
150…配車計画作成部
160…走行ルート計画部
170…車両通信インターフェース部
171…車両情報取得部
172…配車指示部
12…データベース
12a…稼働実績データベース
12b…荷物情報データベース
12c…ユーザ情報データベース
12d…地図データベース
12e…車両情報データベース
12f…配車計画データベース
20…端末装置
N…通信ネットワーク
V…車両
300…制御装置
310…通信部
320…位置情報取得部
330…ユーザインターフェース部 1...Vehicle allocation management system 10...Vehicle allocation management device 110...Front end processing section 120...Demandinformation acquisition section 121...Current demand calculation section 122...Demand forecasting section 130...Vehicle dispatch request acquisition section 140...Departure/arrival point determination section 150...Vehicle dispatch plan creation Section 160... Driving route planning section 170... Vehicle communication interface section 171... Vehicle information acquisition section 172... Vehicle allocation instruction section 12... Database 12a... Operation record 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...Communication unit 320...Position information acquisition unit 330...User interface unit
10…配車管理装置
110…フロントエンド処理部
120…需要情報取得部
121…現在需要算出部
122…需要予測部
130…配車要求取得部
140…発着地決定部
150…配車計画作成部
160…走行ルート計画部
170…車両通信インターフェース部
171…車両情報取得部
172…配車指示部
12…データベース
12a…稼働実績データベース
12b…荷物情報データベース
12c…ユーザ情報データベース
12d…地図データベース
12e…車両情報データベース
12f…配車計画データベース
20…端末装置
N…通信ネットワーク
V…車両
300…制御装置
310…通信部
320…位置情報取得部
330…ユーザインターフェース部 1...Vehicle allocation management system 10...Vehicle allocation management device 110...Front end processing section 120...Demand
Claims (18)
- 乗客と荷物とを混載可能な複数の車両を用いたオンデマンド方式による配車を管理する配車管理装置であって、
ユーザによる乗車及び荷物配送のいずれかの配車要求を取得する配車要求取得部と、
取得された前記配車要求に基づいて前記複数の車両の中から選択される一の車両に対する配車計画を作成する配車計画作成部と、
前記配車計画に基づく配車指示を前記一の車両に送信する配車指示部と、を備え、
前記配車計画作成部は、前記荷物配送の配車要求に応答して前記一の車両に対する前記配車計画を作成する時点で、他の前記配車要求がない場合には、前記配車計画の作成を一時的に保留する、
配車管理装置。 A vehicle allocation management device that manages on-demand vehicle allocation using multiple vehicles that can carry passengers and luggage together,
a vehicle dispatch request acquisition unit that acquires a vehicle dispatch request for either boarding or package delivery by a user;
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 dispatch instruction unit that transmits a vehicle dispatch instruction based on the vehicle dispatch plan to the one vehicle,
When the vehicle dispatch plan creation unit creates the vehicle dispatch plan for the one vehicle in response to the vehicle dispatch request for package delivery, if there is no other vehicle dispatch request, the vehicle dispatch plan creation unit temporarily stops the creation of the vehicle dispatch plan. to be held in
Vehicle allocation management device. - 前記配車計画作成部は、作成された前記配車計画を前記ユーザに提案し、前記ユーザによる前記提案に対する前記ユーザの承諾があった場合に、前記配車計画を確定する、
請求項1に記載の配車管理装置。 The vehicle dispatch plan creation unit proposes the created vehicle dispatch plan to the user, and finalizes the vehicle dispatch plan if the user consents to the proposal by the user.
The vehicle allocation management device according to claim 1. - 前記複数の車両に対する現在及び将来の需要量を示す需要情報を取得する需要情報取得部を更に備える、
請求項1に記載の配車管理装置。 further comprising a demand information acquisition unit that acquires demand information indicating current and future demand for the plurality of vehicles;
The vehicle allocation management device according to claim 1. - 前記配車計画作成部は、前記需要情報が示す前記将来の需要量が第1の上限値を上回る場合に、前記配車計画の作成を一時的に保留する、
請求項3に記載の配車管理装置。 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.
The vehicle allocation management device according to claim 3. - 前記配車計画作成部は、前記需要情報が示す前記現在の需要量に対する前記将来の需要量の比が所定の変化率を上回る場合に、前記配車計画の作成を一時的に保留する、
請求項3に記載の配車管理装置。 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. - 前記配車計画作成部は、前記需要情報が示す現在の需要量が第2の上限値を上回る場合に、前記配車計画を確定する、
請求項3に記載の配車管理装置。 The vehicle allocation plan creation unit finalizes the vehicle allocation plan when the current demand amount indicated by the demand information exceeds a second upper limit.
The vehicle allocation management device according to claim 3. - 前記配車計画作成部は、前記荷物配送の配車要求が示す荷物の個数が所定の保留荷物限界数以上である場合に、前記配車計画を確定する、
請求項1に記載の配車管理装置。 The vehicle allocation plan creation unit finalizes the vehicle allocation plan when the number of packages indicated by the vehicle allocation request for package delivery is equal to or greater than a predetermined limit number of held packages.
The vehicle allocation management device according to claim 1. - 前記配車計画作成部は、前記需要情報が示す前記現在の需要量に対する前記将来の需要量の比が所定の変化率を超える場合に、前記所定の保留荷物限界数の値を小さくする、
請求項7に記載の配車管理装置。 The vehicle allocation plan creation unit reduces the value of the predetermined limit number of held baggage when the 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. - 前記配車計画作成部は、一時的に保留している前記配車計画がある場合に、前記一時的に保留している前記配車計画に対応する前記配車要求と前記他の配車要求とに基づいて、配車計画を再作成する、
請求項1に記載の配車管理装置。 When there is a temporarily pending vehicle dispatch plan, the vehicle dispatch plan creation unit may perform the following operations based on the vehicle dispatch request corresponding to the temporarily pending vehicle dispatch plan and the other vehicle dispatch request: Re-create the dispatch plan,
The vehicle allocation management device according to claim 1. - 前記配車計画作成部は、前記荷物配送の配車要求が受け付けた時点から所定の保留限界時間を経過した場合に、前記配車計画の保留を解除し、前記配車計画を確定する、
請求項1に記載の配車管理装置。 The vehicle allocation plan creation unit releases the suspension of the vehicle allocation plan and finalizes the vehicle allocation plan when a predetermined hold limit time has elapsed from the time when the vehicle allocation request for package delivery was received.
The vehicle allocation management device according to claim 1. - 前記配車計画作成部は、前記荷物配送の配車要求が行ったユーザの属性情報に応じて、前記所定の保留限界時間を設定する、
請求項10に記載の配車管理装置。 The vehicle dispatch plan creation unit sets the predetermined holding limit time according to the attribute information of the user who made the vehicle dispatch request for package delivery.
The vehicle allocation management device according to claim 10. - 前記配車計画作成部は、前記荷物配送の配車要求が示す荷物属性情報に応じて、前記所定の保留限界時間を設定する、
請求項10に記載の配車管理装置。 The vehicle dispatch plan creation unit sets the predetermined holding limit time according to package attribute information indicated by the vehicle dispatch request for package delivery.
The vehicle allocation management device according to claim 10. - 前記配車計画作成部は、前記荷物配送の配車要求が示す積荷地情報に応じて、前記所定の保留限界時間を設定する、
請求項10に記載の配車管理装置。 The vehicle dispatch plan creation unit sets the predetermined holding limit time according to loading point information indicated by the vehicle dispatch request for package delivery.
The vehicle allocation management device according to claim 10. - 前記需要情報取得部は、前記将来の需要量を予測する需要予測部を含み、
前記需要予測部は、前記複数の車両のうちの前記配車計画の対象となる前記車両の待機台数に基づいて、前記将来の需要量を算出する、
請求項3に記載の配車管理装置。 The demand information acquisition unit includes a demand prediction unit that predicts the future demand amount,
The demand forecasting unit calculates the future demand amount based on the number of waiting vehicles of the plurality of vehicles that are subject to the vehicle allocation plan.
The vehicle allocation management device according to claim 3. - 前記需要予測部は、前記複数の車両の過去の稼働実績に関する稼働実績情報に基づいて、前記将来の需要量を算出する、
請求項14に記載の配車管理装置。 The demand forecasting unit calculates the future demand amount based on operation record information regarding past operation records of the plurality of vehicles.
The vehicle allocation management device according to claim 14. - 前記需要予測部は、前記乗車の配車要求を行った前記ユーザの行動履歴に基づいて、前記将来の需要量を算出する、
請求項14又は15に記載の配車管理装置。 The demand forecasting unit calculates the future demand amount based on the behavior history of the user who requested the ride allocation.
The vehicle allocation management device according to claim 14 or 15. - 前記配車計画作成部は、前記配車要求に応じて前記複数の車両の中から複数の候補車両を抽出し、前記複数の候補車両の各々による複数のルートパターンに基づく複数の配車計画を作成し、所定の評価関数に従って、前記複数の配車計画の中から一の前記配車計画を選定する、
請求項1に記載の配車管理装置。 The vehicle allocation plan creation unit extracts a plurality of candidate vehicles from the plurality of vehicles in response to the vehicle allocation request, and creates a plurality of vehicle allocation plans based on a plurality of route patterns for each of the plurality of candidate vehicles, selecting one of the vehicle allocation plans from the plurality of vehicle allocation plans according to a predetermined evaluation function;
The vehicle allocation management device according to claim 1. - 乗客と荷物とを混載可能な複数の車両を用いたオンデマンド方式による配車を管理する配車管理装置による配車管理方法であって、
ユーザの端末装置から乗車及び荷物配送のいずれかの配車要求を取得することと、
取得された前記配車要求に応答して前記複数の車両の中から選択される一の車両に対する配車計画を作成することと、
確定された前記配車計画に基づく配車指示を前記一の車両に送信することと、を含み、
前記配車計画を作成することは、前記荷物配送の配車要求に応答して前記一の車両に対する前記配車計画を作成する時点で、他の前記配車要求がない場合には、前記配車計画の作成を一時的に保留することを含む、
配車管理方法。 A vehicle dispatch management method using a vehicle dispatch management device that manages vehicle dispatch using an on-demand method using a plurality of vehicles capable of carrying passengers and luggage, the method comprising:
Obtaining a dispatch request for either a ride or a package delivery from a user's terminal device;
creating a vehicle dispatch plan for one vehicle selected from the plurality of vehicles in response to the acquired vehicle dispatch request;
transmitting a vehicle dispatch instruction based on the confirmed vehicle dispatch plan to the one vehicle,
Creating the vehicle allocation plan may include creating the vehicle allocation plan if there is no other vehicle allocation request at the time of creating the vehicle allocation plan for the one vehicle in response to the package delivery vehicle allocation request. including temporarily suspending
Vehicle dispatch management method.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2022-138146 | 2022-08-31 | ||
JP2022138146 | 2022-08-31 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2024048231A1 true WO2024048231A1 (en) | 2024-03-07 |
Family
ID=90099350
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2023/029096 WO2024048231A1 (en) | 2022-08-31 | 2023-08-09 | Vehicle dispatch management device and vehicle dispatch management method |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2024048231A1 (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009146004A (en) * | 2007-12-11 | 2009-07-02 | Hitachi Information & Control Solutions Ltd | Vehicle dispatching planning device and vehicle dispatching planning method |
JP2022003458A (en) * | 2020-06-23 | 2022-01-11 | 日産自動車株式会社 | Vehicle allocation management device and vehicle allocation management method |
JP2022504037A (en) * | 2018-10-10 | 2022-01-13 | ウェイモ エルエルシー | Smart signs for autonomous vehicles |
WO2022162842A1 (en) * | 2021-01-28 | 2022-08-04 | 日産自動車株式会社 | Mixed freight/passenger loading system, vehicle dispatch device for mixed freight/passenger loading system, and vehicle dispatch method for mixed freight/passenger loading system |
-
2023
- 2023-08-09 WO PCT/JP2023/029096 patent/WO2024048231A1/en unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009146004A (en) * | 2007-12-11 | 2009-07-02 | Hitachi Information & Control Solutions Ltd | Vehicle dispatching planning device and vehicle dispatching planning method |
JP2022504037A (en) * | 2018-10-10 | 2022-01-13 | ウェイモ エルエルシー | Smart signs for autonomous vehicles |
JP2022003458A (en) * | 2020-06-23 | 2022-01-11 | 日産自動車株式会社 | Vehicle allocation management device and vehicle allocation management method |
WO2022162842A1 (en) * | 2021-01-28 | 2022-08-04 | 日産自動車株式会社 | Mixed freight/passenger loading system, vehicle dispatch device for mixed freight/passenger loading system, and vehicle dispatch method for mixed freight/passenger loading system |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11062415B2 (en) | Systems and methods for allocating networked vehicle resources in priority environments | |
JP7378831B2 (en) | Information processing device, information processing method and program | |
US20170169366A1 (en) | Systems and Methods for Adjusting Ride-Sharing Schedules and Routes | |
JP6954072B2 (en) | User vehicle dispatch support system | |
CN107767322B (en) | Carpooling method and device | |
US20180268510A1 (en) | Systems and methods for real-time scheduling in a transportation system based upon a user criteria | |
KR20200013243A (en) | System and method for shuttle service management and shuttle service route and service derivation | |
Bischoff et al. | A framework for agent based simulation of demand responsive transport systems | |
JP2019175393A (en) | Carpool support system, carpool support method, program and movable body | |
CN113574579B (en) | Information processing apparatus, moving body, computer-readable storage medium, and method | |
JP7359083B2 (en) | Vehicle allocation planning device, vehicle allocation planning system, and vehicle allocation planning program | |
JP2019133356A (en) | Transfer support system, transfer support method, transfer support program, and mobile body | |
WO2024048231A1 (en) | Vehicle dispatch management device and vehicle dispatch management method | |
CN111738646A (en) | Distribution arrangement system and distribution arrangement method | |
JP2021015379A (en) | Vehicle allocation processing device | |
JP2024035060A (en) | Vehicle allocation management device and vehicle allocation management method | |
CN112232537A (en) | Intelligent vehicle distribution method and system for pick-up and delivery machine service | |
WO2024134897A1 (en) | Vehicle dispatch management device and vehicle dispatch management method | |
JP2021152761A (en) | Vehicle allocation management device, vehicle allocation management method, and program | |
JP7504472B2 (en) | PROGRAM AND INFORMATION PROCESSING APPARATUS | |
US20170308971A1 (en) | Method of organization of passenger travel in a transport system, associated computer program product and system of organization | |
JP2021009514A (en) | Ride-sharing vehicle arrangement system | |
CN113597635A (en) | Information processing apparatus, moving object, program, and method | |
JP7223623B2 (en) | Vehicle management device and program | |
JP2024092465A (en) | Vehicle allocation management device and vehicle allocation management method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23858427 Country of ref document: EP Kind code of ref document: A1 |