Vehicle dispatch management device and vehicle dispatch management method

Abstract

To dispatch vehicles with sensor configuration and / or characteristics adapted to travel routes.SOLUTION: A vehicle dispatch management device for managing vehicle dispatch in response to a vehicle dispatch request, includes: a vehicle information database for storing vehicle information for each of a plurality of vehicles; a road map information database for storing road map information associated with sensor requirements; a travel route extraction unit for extracting at least one travel route based on the vehicle dispatch request by referring to the road map information database; a sensor requirement determination unit for determining the sensor requirements for the extracted travel route by referring to the road map information database; a vehicle selection unit for selecting, based on the determined sensor requirements, a vehicle adapted to travel on the travel route from among the plurality of vehicles by referring to the vehicle information database; and a vehicle dispatch planning unit for creating a vehicle dispatch plan for the selected vehicle based on the travel route.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a vehicle allocation management device and a vehicle allocation management method. [Background technology]

[0002] Mobility services are services that provide smooth transportation of passengers and / or luggage by vehicles. Mobility services require efficient vehicle allocation to increase the utilization rate of each vehicle and improve user convenience.

[0003] For example, Patent Document 1 below discloses a technique for calculating a route that improves the reliability of travelling along the travel route when a plurality of vehicles having an automatic driving function or a driving assistance function are centrally managed. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] International Publication No. WO2020 / 194062 Summary of the Invention [Problem to be solved by the invention]

[0005] The technology disclosed in the above Patent Document 1 uses a fleet of vehicles with uniform sensor configurations and / or characteristics for vehicle dispatch management, making it impossible to dispatch vehicles that are suited to the calculated driving route.

[0006] In addition, there is a cost problem in arranging vehicles with high-spec sensor configurations and / or characteristics so that they can travel any travel route. For example, roads where high-speed travel is planned, such as expressways, require sensor configurations and / or characteristics that recognize the distant area ahead of the vehicle, while roads where people, bicycles, and motorcycles pass by, such as residential roads, require sensor configurations and / or characteristics that recognize the sides of the vehicle. However, currently, there is no consideration of arranging various vehicles with sensor configurations and / or characteristics of different specifications and dispatching vehicles with sensor configurations and / or characteristics suitable for a calculated travel route.

[0007] Therefore, an object of the present invention is to provide a vehicle dispatch management device and a vehicle dispatch management method capable of dispatching vehicles having a sensor configuration and / or characteristics adapted to a travel route. [Means for solving the problem]

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

[0009] The present invention according to one aspect is a vehicle dispatch management device that manages the dispatch of vehicles in response to a dispatch request. The vehicle dispatch management device includes a vehicle information database that stores vehicle information of each of a plurality of vehicles, a road map information database that stores road map information associated with a sensor requirement, a travel route extraction unit that refers to the road map information database based on the dispatch request and extracts at least one travel route, a sensor requirement determination unit that refers to the road map information database and determines the sensor requirement for the extracted travel route, a vehicle selection unit that refers to the vehicle information database based on the determined sensor requirement and selects a vehicle suitable for traveling the travel route from among the plurality of vehicles, and a vehicle dispatch plan creation unit that creates a vehicle dispatch plan for the selected vehicles based on the travel route.

[0010] The present invention also provides a vehicle allocation management method using a vehicle allocation management device that manages vehicle allocation in response to a vehicle allocation request, a computer program for executing the method, and a recording medium on which the method is non-temporarily recorded. Effect of the Invention

[0011] According to the present invention, by stocking a variety of vehicles having different sensor configurations and / or characteristics, it becomes possible to dispatch vehicles having sensor configurations and / or characteristics suited to a travel route.

[0012] Other technical features, objects, and operational effects or advantages of the present invention will become apparent from the following embodiments described with reference to the accompanying drawings. The effects described in this specification are merely examples and are not limited thereto, and other effects may also be present. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram illustrating an example of a schematic configuration of a vehicle dispatch management system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram for explaining an example of the recognition range of a sensor mounted on a vehicle in the vehicle dispatch management system according to one embodiment of the present invention. [Diagram 3] FIG. 3 is a block diagram showing an example of a functional configuration model of a vehicle dispatch control device according to an embodiment of the present invention. [Figure 4] FIG. 4 is a block diagram showing an example of a functional configuration model of a vehicle allocation plan formulation unit in a vehicle allocation management device according to an embodiment of the present invention. [Figure 5A] FIG. 5A is a flowchart for explaining an example of a vehicle dispatch management process by the vehicle dispatch management device according to one embodiment of the present invention. [Figure 5B] FIG. 5B is a flowchart for explaining an example of a vehicle dispatch management process by the vehicle dispatch management device according to one embodiment of the present invention. [Figure 5C]FIG. 5C is a flowchart for explaining an example of a vehicle allocation management process by the vehicle allocation management device according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. However, the embodiment described below is merely an example, and there is no intention to exclude various modifications and application of techniques not specified below. The present invention can be implemented by various modifications (for example, combining the respective embodiments) within the scope of the gist of the present invention. In addition, in the following description of the drawings, the same or similar parts are represented by the same or similar reference numerals. The drawings are schematic and do not necessarily correspond to actual dimensions, ratios, etc. The drawings may also include parts with different dimensional relationships and ratios.

[0015] 1 is a diagram illustrating an example of a schematic configuration of a vehicle dispatch management system according to an embodiment of the present invention. As shown in the figure, the vehicle dispatch management system 1 includes a vehicle dispatch management device 10, a terminal device 20, and a vehicle V, which are connected to each other so as to be able to communicate with each other via a communication network N. In addition, the vehicle dispatch management system 1 can be connected via the communication network N to a road traffic information management system 30 that provides various types of traffic information in real time.

[0016] The vehicle dispatch management system 1 of the present disclosure provides, for example, a vehicle dispatch service for a certain area using a plurality of vehicles V. The vehicle dispatch service may be either an "on-demand" system or a "reservation" system.

[0017] The vehicle dispatch management device 10 is a computing device that comprehensively manages a vehicle dispatch service by a plurality of vehicles V in a target area. The vehicle dispatch management device 10 implements, for example, a vehicle dispatch management server program and executes the vehicle dispatch management server program under the control of a processor, thereby realizing the vehicle dispatch service of the present disclosure.

[0018] The vehicle dispatch management device 10 includes various databases 12 that accumulate and manage data necessary to realize such a vehicle dispatch service. The databases 12 may include, for example, a user information database 12a, a road map information database 12b, a vehicle information database 12c, and a vehicle dispatch plan database 12d (see FIG. 2). The databases 12 may be configured as a part of the vehicle dispatch management device 10, or all or a part of the databases 12 may be configured separately from the vehicle dispatch management device 10.

[0019] In general, the vehicle allocation management device 10 receives a vehicle allocation request from a user who wishes to allocate a vehicle V for travel, extracts an appropriate vehicle V as a candidate vehicle from among multiple vehicles V under the vehicle allocation service based on the vehicle allocation request, and creates a vehicle allocation plan for the extracted vehicle V. In addition, the vehicle allocation management device 10 confirms the vehicle allocation plan in response to the user's consent to the created vehicle allocation plan, and issues a vehicle allocation instruction to the vehicle V according to the vehicle allocation plan.

[0020] The vehicle allocation plan includes a driving route that is determined from a location where the vehicle V waits (a waiting location that is a starting point) to a waiting location that is an end point (not necessarily the same as the initial waiting location) via several points (boarding and disembarking points) along the way where the user gets on and off. In the present disclosure, the vehicle allocation management device 10 extracts a driving route based on the vehicle allocation plan, determines predetermined sensor requirements according to the extracted driving route, extracts and selects a vehicle V equipped with a sensor that satisfies the predetermined sensor requirements, and creates a vehicle allocation plan for the selected vehicle V. This makes it possible to select and allocate a vehicle having a sensor configuration / performance suitable for the driving route from various vehicles having different sensor configurations and / or characteristics. In addition, in the present disclosure, the vehicle allocation plan includes a vehicle allocation plan for transfers of different vehicles V. This makes it possible to divide a driving route into a plurality of sections, extract and select a vehicle V equipped with a sensor that satisfies the predetermined sensor requirements for each divided section, and allocate the vehicle.

[0021] The vehicle V is a vehicle registered in a vehicle information database that is available for use by a user. The vehicle V may be of any type (e.g., a sedan, a minivan, an SUV, etc.). The vehicle V may be an electric vehicle (EV) powered by an on-board battery. In this disclosure, the vehicle V is an unmanned vehicle capable of autonomous driving using an autonomous driving system, but the so-called level of autonomous driving does not matter.

[0022] The vehicle V is equipped with a control device CTL that controls the vehicle V itself or its on-board equipment according to instructions from the vehicle dispatch management device 10. Although not shown, the control device 300 is configured to include a processor, a memory, and the like. The control device CTL acquires geographical position information (hereinafter referred to as "position information") of the vehicle V via, for example, a GPS system, transmits the same to the vehicle dispatch management device 10, and receives dispatch instructions from the vehicle dispatch management device 10 to control the operation of various devices or equipment of the vehicle V. If the control device CTL is a manned vehicle, it includes, for example, a navigation function that presents a driving route according to a vehicle dispatch plan. Also, if the control device CTL is an unmanned vehicle, it includes an autonomous driving control function that controls the autonomous driving of the vehicle V in consideration of actual road conditions based on the driving route of the vehicle V.

[0023] In the present disclosure, the vehicle V includes a first type vehicle V1 equipped with various sensors (first sensors) adapted for high-speed driving on high-standard roads such as expressways, motorways, and major trunk roads, and a second type vehicle V2 equipped with various sensors (second sensors) adapted for driving on general roads other than high-standard roads (including so-called residential roads, etc.).

[0024] FIG. 2 is a diagram for explaining an example of the recognition range of a sensor mounted on a vehicle in a vehicle dispatch management system according to an embodiment of the present invention. FIG. 2(a) shows an example of the recognition range of a sensor of a first type vehicle V1, and FIG. 2(b) shows an example of the recognition range of a sensor of a second type vehicle V2. As shown in these figures, the recognition range of a first sensor of a first type vehicle V1 may be different from the recognition range of a second sensor of a second type vehicle V2 in at least one of the front, side, rear, and up and down directions of the vehicle. Such a recognition range depends on the type of sensor (e.g., visible light image sensor, infrared image sensor, RADAR, LiDAR, etc.), configuration (e.g., number, arrangement location, orientation, etc.), and / or characteristics (e.g., resolution, angle of view, sensitivity, etc.), etc.

[0025] The first sensor also includes an imaging camera having characteristics suitable for recognizing a space far in front of the vehicle. The far in front of the vehicle is a position that is far enough away to obtain information necessary for vehicle control when the vehicle V is traveling at high speed. On the other hand, the second sensor of the second type vehicle includes a sensor having general characteristics for recognizing the space in front of the vehicle (but closer than the far distance), and may further include an additional sensor suitable for recognizing the space around the vehicle (sideways, rearward, and up and down). For example, on general roads, people, bicycles, and motorcycles often approach the sides of the vehicle V, so a sensor is required to recognize people and objects near the vehicle. In this way, the first sensor or the second sensor with different recognition ranges is mounted on the vehicle V, so that the vehicle V can travel under driving conditions (such as road type and speed) that are adapted to each. It should be noted that the first type vehicle can also travel on general roads, and the second type vehicle V2 can also travel on high-standard roads.

[0026] The terminal device 20 is, for example, a computing device for a user who wishes to ride to make a vehicle dispatch request by operating a user interface. The terminal device 20 is, for example, a smartphone, a pad computer, a notebook personal computer, a desktop computer, etc., but is not limited to these. The terminal device 20 implements, for example, a vehicle dispatch management client program (so-called vehicle dispatch application). The terminal device 20 enables a user to use the vehicle dispatch service of the vehicle dispatch management device 10 by executing the vehicle dispatch application under the control of the processor. For example, a user can make a vehicle dispatch request from a vehicle dispatch request screen (not shown) on the user interface of the terminal device 20 and accept a vehicle dispatch plan created by the vehicle dispatch management device 10 in response to the request, thereby making a reservation for a ride on the vehicle V. The vehicle dispatch request includes, for example, a user name, the number of passengers, a departure point (boarding point), and a destination (drop-off point), etc.

[0027] The road traffic information management system 30 is an information and communication system that provides road traffic information in real time. For example, the road traffic information management system 30 collects road traffic data from vehicle sensors and imaging cameras installed on roads, and also collects travel data from a control device 300 mounted on the vehicle V, and manages road traffic information that is integrated, processed, and edited from the data. The edited road traffic information may include, for example, information on road closures and detour routes, and the time required between points via a specific route. The road traffic information management system 30 provides the road traffic information to the vehicle dispatch management device 10 and the vehicle V as appropriate.

[0028] FIG. 3 is a block diagram showing an example of a functional configuration model of a vehicle dispatch management device according to an embodiment of the present invention. As shown in the figure, the vehicle dispatch management device 10 is generally configured as a functional configuration model including functional components such as a front-end processing unit 110, a vehicle dispatch plan formulation unit 120, and a vehicle communication unit 130. As described above, the vehicle dispatch management device 10 includes various databases 12. Such a functional model is realized by the vehicle dispatch management device 10 executing a vehicle dispatch management server program under the control of a processor and 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.

[0029] The user information database 12a stores information about users who use the ride-hailing service (hereinafter referred to as "user information"). The user information includes, for example, a user ID and password, personal attributes, and information about the service usage status. The user information is registered, for example, through a ride-hailing app under the operation of the user.

[0030] The road map information database 12b stores information on road maps (hereinafter referred to as "road map information"). The road map information may include information necessary for searching for a route to a destination, such as road network information, road-related information, and environmental information. The road network information is information consisting of nodes (intersections) and links (roads). The road-related information includes, for example, traffic regulations such as speed limits, one-way streets, no right or left turns, no parking or stopping, and road closures, road types such as community roads and main roads (including lanes, etc.), and information on control of traffic lights at intersections. In addition, the road-related information may include, for example, the situation between buildings and roads (for example, sidewalk width, the presence or absence of accessories such as guardrails and shrubbery, the degree of visibility, etc.). The environmental information includes, for example, the situation of parked and stopped vehicles and pedestrians at each point by time period, the frequency of right and left turns at intersections, the frequency of parking and stopping, and the frequency of traffic accidents. In the present disclosure, a specific node and / or link in the road map information is associated with a sensor requirement required for a sensor mounted on the vehicle V. This makes it possible to identify a vehicle V that is suitable (capable of traveling the travel route) for each travel route from among various vehicles having different sensor configurations and / or characteristics.

[0031] The vehicle information database 12c stores information (vehicle information) about the vehicle V that is provided for use by the user. The vehicle information includes, for example, a vehicle ID, vehicle attributes (vehicle registration number, vehicle model, maximum number of passengers / maximum load capacity, manned or unmanned driving type, etc.), vehicle performance, other specifications, a current vehicle dispatch plan, a current location, and a current state (service state, remaining battery capacity (range), and number of passengers, etc.). The vehicle performance includes various specifications related to autonomous driving. In the present disclosure, the vehicle performance includes information about each sensor mounted on the vehicle V. The information about the sensor includes, for example, information about the type (e.g., visible light image sensor, infrared image sensor, RADAR, LiDAR, etc.), configuration (e.g., number, location, orientation, etc.), and / or characteristics (e.g., resolution, angle of view, sensitivity, etc.). The current location and / or state of the vehicle V may be updated at any time based on the location information transmitted from the vehicle V.

[0032] The vehicle dispatch plan database 12d stores a vehicle dispatch plan for each vehicle V created by the vehicle dispatch management device 10 based on a dispatch request. The vehicle dispatch plan includes a driving route from a waiting location serving as a starting point to a waiting location serving as an end point via several boarding and disembarking points, and an expected arrival time at each intermediate point. If the vehicle V is waiting, the vehicle dispatch plan is newly created based on a new vehicle dispatch request, and if the vehicle V is in operation, the vehicle dispatch plan can be updated based on a new vehicle dispatch request.

[0033] The front-end processing unit 110 performs various processes with the user's terminal device 20. As an example, the front-end processing unit 110 refers to the user information database 12a 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 also receives a vehicle dispatch request from the vehicle dispatch application on the user's terminal device 20, passes it to the vehicle dispatch plan formulation unit 120, and interacts with the terminal device 20 to receive the user's approval or disapproval of the vehicle dispatch plan created by the vehicle dispatch plan formulation unit 120 in response to the request.

[0034] The vehicle allocation plan formulation unit 120 extracts candidate vehicles V from among the vehicles V in the target area based on a given vehicle allocation request, searches for and extracts driving routes, selects a vehicle V that is suitable for the extracted driving route, and creates a vehicle allocation plan for the vehicle. The vehicle allocation plan formulation unit 120 also proposes the created vehicle allocation plan to a user, and in accordance with the user's consent in response thereto, confirms the vehicle allocation plan and issues a vehicle allocation instruction to the vehicle V according to the confirmed vehicle allocation plan. The vehicle allocation plan formulation unit 120 stores the confirmed vehicle allocation plan in the vehicle allocation plan database 12d, and issues a vehicle allocation instruction to the corresponding vehicle V via the vehicle communication unit 130.

[0035] In the present disclosure, the vehicle allocation plan formulation unit 120 determines sensor requirements for the extracted travel route (travel route candidate) by referring to the road map information database 12b, and selects a vehicle V equipped with a sensor that satisfies the sensor requirements. As an example, when a high-standard road such as an expressway is included in the travel route, the vehicle allocation plan formulation unit 120 selects a first type vehicle V1 equipped with a first sensor adapted to high-speed travel on the high-standard road. As another example, when a travel route includes only general roads other than the high-standard road, the vehicle allocation plan formulation unit 120 selects a second type vehicle V2 equipped with a second sensor adapted to travel on the general road. A more specific functional configuration model of the vehicle allocation plan formulation unit 120 will be described with reference to FIG. 4.

[0036] The vehicle communication unit 130 exchanges various information with the vehicle V via the communication network N. For example, the vehicle communication unit 130 acquires vehicle information including the position information of the vehicle V and transfers it to the vehicle allocation plan formulation unit 120, and also transmits driving instructions to the vehicle V according to the vehicle allocation plan formulated by the vehicle allocation plan formulation unit 120.

[0037] 4 is a block diagram showing an example of a functional configuration model of a vehicle dispatch plan formulation unit in a vehicle dispatch management device according to an embodiment of the present invention. As shown in the figure, the vehicle dispatch plan formulation unit 120 includes, for example, a vehicle dispatch request acquisition unit 121, a driving route extraction unit 122, a sensor requirement determination unit 123, a vehicle information acquisition unit 124, a vehicle selection unit 125, a vehicle dispatch plan creation unit 126, a vehicle dispatch plan proposal unit 127, and a vehicle dispatch instruction unit 128.

[0038] The dispatch request acquisition unit 121 acquires or accepts a dispatch request from a user via the front-end processing unit 110. The time when the dispatch request acquisition unit 121 acquires the dispatch request becomes the time when timing of various limit times (for example, boarding limit time, disembarking limit time, etc.) starts. The dispatch request acquisition unit 121 passes the acquired dispatch request to each of the travel route extraction unit 122 and the vehicle selection unit 125.

[0039] The travel route extraction unit 122 calculates and extracts at least one or more travel routes based on the user's dispatch request. For example, the travel route extraction unit 122 extracts several travel routes by having a route search engine (not shown) perform a route search while referring to the road map information database 12b based on the boarding and disembarking locations indicated in the dispatch request. The travel route extraction unit 122 passes the extracted travel routes to the sensor requirement determination unit 123 and the vehicle selection unit 125.

[0040] The sensor requirement determination unit 123 determines the sensor requirement for the extracted travel route with reference to the road map information database 12b. For example, the sensor requirement determination unit 123 extracts sensor requirements associated with the nodes and links constituting the travel route from the road map information in the road map information database 12b and determines them as the sensor requirement for the travel route. As an example, when the extracted travel route includes a high-standard road such as an expressway, the sensor requirement determination unit 123 extracts the sensor requirement for the high-standard road. As another example, when the extracted travel route does not include a high-standard road but includes only a general road, the sensor requirement determination unit 123 extracts the sensor requirement for the general road. As yet another example, when the extracted travel route includes a high-standard road and a general road, the sensor requirement determination unit 123 may extract the sensor requirements for the high-standard road and the general road, respectively. In this case, the sensor requirement determination unit 123 may extract the sensor requirement for the general road when the distance of the high-standard road in the travel route is less than a predetermined ratio to the travel route. Here, the predetermined ratio may be, for example, about 1 / 2 or 1 / 3, but is not limited thereto. This makes it possible to select a Type 2 vehicle that meets the sensor requirements for general roads, even if the extracted driving route includes a highway, if the distance is short.

[0041] The vehicle information acquisition unit 124 communicates with the control device CTL of the vehicle V via the vehicle communication unit 130 and acquires vehicle information including position information of the vehicle V under the vehicle dispatch service. The vehicle information acquisition unit 124 may acquire the vehicle information from the vehicle V at the time of acquiring a dispatch request, or may acquire the vehicle information from the vehicle V at a predetermined period. The vehicle information acquisition unit 124 updates the vehicle information database 12c based on the acquired vehicle information. In addition, the vehicle information acquisition unit 124 passes the acquired vehicle information to the vehicle selection unit 125.

[0042] The vehicle selection unit 125 extracts and selects a specific vehicle adapted to the travel route from among the multiple vehicles V based on the sensor requirements determined for the travel route. More specifically, the vehicle selection unit 125 first extracts a vehicle V near the departure point indicated by the dispatch request. Next, the vehicle selection unit 125 selects a vehicle V equipped with a sensor that satisfies the sensor requirements determined for the travel route from among the extracted vehicles V. In this example, the vehicle selection unit 125 selects a first type vehicle V1 and / or a second type vehicle V2 as a vehicle V adapted to the travel route according to the sensor requirements. In addition, the vehicle selection unit 124 may select the second type vehicle V2 if the sensor equipped in the second type vehicle V2 is adapted to the speed limit of the highway on the travel route. Therefore, the second type vehicle V2 may be selected even for a travel route including a highway, which enables flexible and efficient dispatch of the vehicles V under the dispatch service. Furthermore, the vehicle selection unit 125 may, for example, cooperate with the travel route extraction unit 122 to divide the travel route into a plurality of sections (for example, a first section and a second section that are continuous), and select and assign either a first type vehicle V1 or a second type vehicle V2 as a vehicle V suitable for each section. This allows travel to the destination by transferring between the first type vehicle V1 and the second type vehicle V2. The travel route is divided, for example, into sections where a high proportion of highways are occupied and sections where a high proportion of general roads are occupied.

[0043] Furthermore, when the vehicle selection unit 125 is unable to select a specific vehicle adapted to the travel route based on the sensor requirements determined for the travel route, it extracts another travel route instead of the current travel route and similarly attempts to select a vehicle V. As a result, different other travel routes are searched for and extracted, making it possible to select an appropriate vehicle V from a limited type and / or number of vehicles V available under the vehicle dispatch service.

[0044] The vehicle allocation plan creation unit 126 creates a vehicle allocation plan for the vehicle V based on the travel route and the vehicle V. The vehicle allocation plan includes a travel route that defines a location where the vehicle V is waiting (a waiting location that is a starting point) via several points (starting and ending points) along the way where the user gets on and off, to a waiting location that is an end point (not necessarily the same as the initial waiting location). The vehicle allocation plan also includes a location (boarding and disembarking point) where the user actually gets on and off based on the user's desired boarding and disembarking point. If the vehicle V is waiting, the vehicle allocation plan creation unit 126 creates a new vehicle allocation plan based on the vehicle allocation request, and if the vehicle V is in operation, updates the vehicle allocation plan for the vehicle V stored in the vehicle allocation plan database 12d based on the vehicle allocation request. If either the first type vehicle V1 or the second type vehicle V2 is assigned to each section of the travel route, the vehicle allocation plan creation unit 126 can create a vehicle allocation plan in which the vehicle V transfers at the connection points of each section. As a result, even if it is not possible to assign either the first type vehicle V1 or the second type vehicle V2 to the travel route based on the dispatch request, the user can travel to the destination by transferring between the first type vehicle V1 and the second type vehicle V2.

[0045] The vehicle allocation plan proposal unit 127 proposes to the user a vehicle allocation plan (vehicle V) created based on the determined travel route, and when the user's consent to the vehicle allocation plan is received, the vehicle allocation plan proposal unit 127 confirms the vehicle allocation plan. That is, the vehicle allocation plan proposal unit 127 transmits the vehicle allocation plan to the user's terminal device 20 via the front-end processing unit 110, and causes the terminal device 20 to display the vehicle allocation plan on the user interface. The user accepts or rejects the vehicle allocation plan, and in response, the terminal device 20 transmits a notification of the acceptance or rejection. When the vehicle allocation plan proposal unit 127 receives the user's consent notification via the front-end processing unit 110, the vehicle allocation plan proposal unit 127 confirms the vehicle allocation plan and notifies the vehicle allocation plan creation unit 126. In response, the vehicle allocation plan creation unit 126 registers the confirmed vehicle allocation plan in the vehicle allocation plan database 12d, and notifies the vehicle allocation instruction unit 128.

[0046] The dispatch instruction unit 128 issues dispatch instructions to the corresponding vehicles V according to the confirmed dispatch plan. The control device CTL of the vehicle V that receives the operation instructions determines a detailed actual driving route according to the driving route in the dispatch plan, and controls the vehicle V so that the vehicle V travels autonomously along the driving route. In addition, in the case of a dispatch plan that involves transfers of the vehicle V, the dispatch instruction unit 128 issues dispatch instructions to each vehicle V.

[0047] 5A to 5C are flowcharts for explaining an example of a vehicle dispatch management process by a vehicle dispatch management device according to an embodiment of the present invention. Such a process is realized by the vehicle dispatch management device executing a vehicle dispatch management server program under the control of a processor, in cooperation with various hardware resources.

[0048] As shown in FIG. 1A, the vehicle dispatch management device 10 waits until a new vehicle dispatch request is received from a user (S501). Meanwhile, for example, a user who wishes to ride or have luggage delivered operates a vehicle dispatch application on the user interface of the terminal device 20 to input a vehicle dispatch request. When a vehicle dispatch request is received from a user (Yes in S501), the vehicle dispatch management device 10 refers to the road map information database 12b based on the vehicle dispatch request and determines a departure point and a destination (S502).

[0049] Next, the vehicle allocation management device 10 refers to the vehicle information database 12c according to the departure point and the destination, and extracts one or more vehicles V as candidate vehicles (S503). 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.

[0050] The vehicle allocation management device 10 also performs route search according to the departure point and destination with reference to the road map information database 12b to extract candidate travel routes (S504). Next, the vehicle allocation management device 10 extracts sensor requirements for each node and link with reference to the road map information database 12b according to the extracted travel route, and determines the sensor requirements for the travel route (S505). In this case, if the vehicle allocation management device 10 determines that the distance of the highway in the travel route is less than a predetermined ratio, it may extract sensor requirements for general roads.

[0051] Next, the vehicle allocation management device 10 selects a vehicle adapted to the travel route from among a plurality of candidate vehicles based on the sensor requirements determined for the travel route. Specifically, the vehicle allocation management device 10 judges whether or not a first-class vehicle V1 among the extracted candidate vehicles satisfies the sensor requirements determined for the travel route (S506). If there are a plurality of first-class vehicles V1, the vehicle allocation management device 10 judges in order of proximity to the departure point, for example. If the vehicle allocation management device 10 judges that the first-class vehicle V1 among the extracted candidate vehicles satisfies the sensor requirements determined for the travel route (Yes in S506), the vehicle allocation management device 10 creates a vehicle allocation plan for the first-class vehicle V1 (S507). The created vehicle allocation plan is proposed to the user, as described later (see FIG. 5C).

[0052] On the other hand, when the vehicle allocation management device 10 determines that the first type vehicle V among the extracted candidate vehicles does not satisfy the sensor requirements determined for the travel route (No in S506), the vehicle allocation management device 10 then determines whether the second type vehicle V2 among the extracted candidate vehicles satisfies the sensor requirements determined for the travel route (S508). In addition, when there are multiple second type vehicles V2, the vehicle allocation management device 10 similarly judges in order of proximity to the departure point, for example. When the vehicle allocation management device 10 determines that the second type vehicle V2 among the extracted candidate vehicles satisfies the sensor requirements determined for the travel route (Yes in S508), the vehicle allocation management device 10 creates a vehicle allocation plan for the second type vehicle V2 (S509). The created vehicle allocation plan is proposed to the user as described later (see FIG. 5C).

[0053] On the other hand, when the vehicle dispatch management device 10 determines that the second type vehicle V2 among the extracted candidate vehicles does not satisfy the sensor requirements determined for the travel route (No in S508), the vehicle dispatch management device 10 divides the travel route into a plurality of sections (two sections in this example) (S510 in FIG. 5B). The travel route is divided into, for example, a first section in which a high proportion of highways is occupied, and a second section in which a high proportion of general roads is occupied.

[0054] Next, the vehicle allocation management device 10 determines whether the first type vehicle V1 or the second type vehicle V2 satisfies the sensor requirements for each section (S511). That is, the vehicle allocation management device 10 determines whether the user can reach the destination from the departure point by transferring between the first type vehicle V1 and the second type vehicle V. When the vehicle allocation management device 10 determines that the first type vehicle V1 or the second type vehicle V2 satisfies the sensor requirements for each section (Yes in S511), the vehicle allocation management device 10 creates a vehicle allocation plan with transfers between the first type vehicle V1 and the second type vehicle V2 (S512).

[0055] On the other hand, if it is determined that the first type vehicle V1 or the second type vehicle V2 does not satisfy the sensor requirements for any section (No in S511), the process proceeds to the processing step of S504, where the next driving route is searched for and extracted, and the above processing is repeated for the extracted driving route in the same manner. As a result, when a vehicle suitable for the extracted driving route cannot be selected, another driving route different from the extracted driving route is searched for and extracted, so that an appropriate vehicle V can be selected from the limited types and / or number of vehicles V available under the vehicle dispatch service.

[0056] After creating a vehicle allocation plan for the first type vehicle V1 or the second type vehicle V2 or a vehicle allocation plan for transfers between the first type vehicle V1 and the second type vehicle V2 through the above processing, the vehicle allocation management device 10 then proposes the created vehicle allocation plan to the user (S513 in FIG. 5C). That is, the vehicle allocation management device 10 transmits the contents of the created current vehicle allocation plan to the terminal device 20, and in response, the terminal device 20 displays the contents on the user interface and prompts the user to accept or reject the vehicle allocation plan.

[0057] Next, the vehicle allocation management device 10 judges whether or not the vehicle allocation plan proposal has been accepted from the user (S512). If the vehicle allocation management device 10 accepts the vehicle allocation plan proposal from the user (Yes in S512), the vehicle allocation management device 10 finalizes the vehicle allocation plan and stores the finalized vehicle allocation plan in the vehicle allocation plan database 12d (S513). Next, the vehicle allocation management device 10 transmits a notification of the confirmation of the vehicle allocation reservation to the terminal device 20, and transmits a vehicle allocation instruction based on the vehicle allocation plan to the vehicle V (S514).

[0058] On the other hand, when the vehicle allocation management device 10 receives a non-acceptance (rejection) from the user for the proposed vehicle allocation plan (No in S512), it judges whether the non-acceptance indicates the continuation of the re-proposal of the vehicle allocation plan (S515). When the vehicle allocation management device 10 judges that the non-acceptance indicates the continuation of the re-proposal of the vehicle allocation plan (Yes in S515), it excludes the current driving route (S516), proceeds to the processing step of S504, searches for and extracts the next driving route, and similarly repeats the above processing for the extracted driving route.

[0059] On the other hand, when the vehicle allocation management device 10 determines that the non-acceptance does not indicate the continuation of the re-proposal of the vehicle allocation plan (No in S515), it cancels the vehicle allocation plan based on the user's vehicle allocation request (S517).

[0060] As described above, according to this embodiment, by preparing various vehicles having different sensor configurations and / or characteristics, it becomes possible to dispatch vehicles having sensor configurations and / or characteristics adapted to the travel route. In particular, according to this embodiment, since the sensor requirements are determined for the travel route extracted based on the vehicle dispatch request, it becomes possible to select a vehicle equipped with a sensor that satisfies the sensor requirements. Furthermore, according to this embodiment, when a certain proportion of high-standard roads are included in the travel route, a first type vehicle equipped with a sensor adapted to high-speed travel is selected, and otherwise, a second type vehicle equipped with a sensor that is resistant to travel on general roads is selected. Therefore, it becomes unnecessary for all vehicles V under the vehicle dispatch service to be equipped with sensors having configurations and / or characteristics adapted to all travel conditions, and vehicle costs can be reduced.

[0061] The above-described embodiments are merely examples for explaining the present invention, and are not intended to limit the present invention to these embodiments. The present invention can be embodied in various forms without departing from the spirit of the present invention.

[0062] For example, in the methods disclosed herein, steps, operations, or functions may be performed in parallel or in a different order, provided that the results are consistent. The steps, operations, and functions described are provided merely as examples, and some of the steps, operations, and functions may be omitted or combined into one, or other steps, operations, or functions may be added, without departing from the spirit of the invention.

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

[0064] 1. Vehicle dispatch management system 10...Vehicle allocation management device 110...Front-end processing unit 120… Vehicle Allocation Planning Department 121…Dispatch request acquisition unit 122...Route extraction unit 123…Sensor requirements determination unit 124…Vehicle information acquisition unit 125…Vehicle selection section 126… Vehicle Allocation Planning Department 127… Vehicle Allocation Planning Proposal Department 128…Dispatch Instructions Department 130…Vehicle communication unit 12. Database 12a…User information database 12b…Road map information database 12c…Vehicle information database 12d…Vehicle allocation plan database 20...Terminal device 30...Road Traffic Information Management System N: Communication network V…Vehicle

Claims

1. A vehicle dispatch management device that manages vehicle dispatch in response to a vehicle dispatch request, a vehicle information database that stores vehicle information for each of a plurality of vehicles; a road map information database for storing road map information associated with sensor requirements; a travel route extraction unit that refers to the road map information database based on the vehicle dispatch request and extracts at least one travel route; a sensor requirement determination unit that refers to the road map information database and determines the sensor requirements for the extracted travel route; a vehicle selection unit that refers to the vehicle information database based on the determined sensor requirements and selects a vehicle suitable for traveling on the travel route from among the plurality of vehicles; and a vehicle allocation plan creation unit that creates a vehicle allocation plan for the selected vehicle based on the travel route. Vehicle dispatch management device.

2. the sensor requirements are associated with nodes and / or links in the road map information; The vehicle dispatch management device according to claim 1.

3. the plurality of vehicles include at least a first type vehicle equipped with a first sensor, and a second type vehicle equipped with a second sensor having characteristics different from those of the first sensor; the vehicle selection unit selects the first type vehicle when the first sensor satisfies the sensor requirement for the travel route, and selects the second type vehicle when the second sensor satisfies the sensor requirement for the travel route. The vehicle dispatch management device according to claim 2.

4. The recognition range of the first sensor is different from that of the second sensor in at least one of the front, side, rear, and up and down directions of the vehicle. The vehicle dispatch management device according to claim 3.

5. The first sensor includes a sensor adapted for high-speed driving on a highway, and the second sensor includes a sensor adapted for driving on a general road other than the highway. The vehicle dispatch management device according to claim 3.

6. the vehicle selection unit selects the second type vehicle when the second sensor is adapted to a speed limit of the highway on the travel route. The vehicle dispatch management device according to claim 5.

7. the travel route extraction unit extracts another travel route different from the current travel route when the vehicle selection unit cannot select the vehicle suitable for the travel route. The vehicle dispatch management device according to claim 1.

8. the sensor requirement determination unit determines, when a distance of a high-standard road in the travel route is less than a predetermined ratio, that the sensor requirement is a sensor requirement for a general road; The vehicle dispatch management device according to claim 1.

9. when the vehicle selection unit cannot select a vehicle that satisfies the sensor requirements for the travel route, the vehicle selection unit selects a vehicle that satisfies a sensor requirement for a first section on the travel route, and selects the vehicle that satisfies a sensor requirement for a second section on the travel route that is adjacent to the first section. The vehicle dispatch management device according to claim 1.

10. the vehicle allocation plan creation unit creates a vehicle allocation plan with transfers based on the vehicle selected for the first section and the vehicle selected for the second section. The vehicle dispatch management device according to claim 9.

11. A vehicle allocation management method by a vehicle allocation management device that manages vehicle allocation in response to a vehicle allocation request, comprising: storing vehicle information for each of a plurality of vehicles in a vehicle information database; storing road map information associated with the sensor requirements in a road map information database; extracting at least one driving route by referring to the road map information database based on the vehicle dispatch request; referencing the road map information database to determine the sensor requirements for the extracted driving route; selecting a vehicle suitable for traveling the travel route from among the plurality of vehicles by referring to the vehicle information database based on the determined sensor requirements; and creating a vehicle dispatch plan for the selected vehicle based on the travel route. Vehicle allocation management methods.

Images