Vehicle dispatch service management apparatus and vehicle dispatch service management method

Abstract

The present invention is a vehicle dispatch service management apparatus for managing a vehicle dispatch service. The apparatus allows, in response to a request for vehicle dispatch, a user to designate a user scheduled for boarding and select departure and destination stops, and creates a vehicle dispatch plan for a vehicle that is selected in accordance with the request for vehicle dispatch. When a passenger who is not the user scheduled for boarding boards the vehicle that is dispatched to the departure stop in accordance with the request for vehicle dispatch, and the destination stop indicated by the vehicle dispatch plan is a stop at which the passenger cannot alight, the passenger changes the destination to a stop at which the passenger can alight, and the apparatus updates the vehicle dispatch plan on the basis of the changed destination stop, and instructs the vehicle with the updated vehicle dispatch plan.

Description

Vehicle dispatch service management device and vehicle dispatch service management method

[0001] The present invention relates to a vehicle dispatch service management device and a vehicle dispatch service management method.

[0002] Fleet management is known as a method for managing vehicle dispatch to improve user convenience while increasing vehicle utilization rates. For example, it suggests potential pickup locations that are convenient for users who make a vehicle dispatch request.

[0003] For example, Patent Document 1 listed below discloses a technology for selecting one or more potential boarding and alighting locations from a plurality of potential boarding and alighting locations based on personal attributes of a user corresponding to the identification information in response to a vehicle dispatch request including identification information for identifying the user from the information terminal of the user who wishes to board a vehicle.

[0004] Japanese Patent Application Laid-Open No. 2021-43686

[0005] However, some users may be permitted to enter certain premises or areas. For example, school children and school personnel can enter the school grounds, but visitors who are not school personnel usually have to go through a reception procedure at the entrance gate or the like before entering the school, and third parties who have no business at the school are not permitted to enter the school in the first place.

[0006] In such circumstances, for example, when a parent requests a ride to take their child to school, it is anticipated that the vehicle will need to carry only the child to a specific location on the school grounds and then drop the child off there.

[0007] However, in the above-mentioned Patent Document 1, since boarding and alighting points (stops) are selected based on the identification information of a user in response to a user's dispatch request, no consideration is given to the case where a user other than the user who is scheduled to board the vehicle and specified at the time of the dispatch request actually boards the vehicle. For example, if the original destination is a stop that is available to the user who is scheduled to board but is unavailable (not permitted to be used) to other users, it is not desirable to transport the passenger directly to the destination.

[0008] Therefore, the present invention aims to propose a vehicle dispatch service management device and a vehicle dispatch service management method that enable passengers to be transported to a stop that is available to the user who will actually board the vehicle, even if a user passenger other than the passenger scheduled to board at the time of the vehicle dispatch request boards the vehicle.

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

[0010] According to one aspect, the present invention provides a vehicle dispatch service management device for managing a vehicle dispatch service. The device includes: a bus stop information database for managing bus stop information for each bus stop where users of the dispatch service board and disembark the vehicle; a user information database for managing user information for each user who can use the dispatch service; a dispatch request acquisition unit for acquiring dispatch requests from users' information communication terminal devices; a dispatch plan creation unit for creating a dispatch plan for the vehicle based on the acquired dispatch request; and a dispatch instruction unit for issuing dispatch instructions to the vehicle based on the created dispatch plan. The dispatch request acquisition unit acquires a user ID of a user who plans to board the vehicle and is associated with the dispatch request, and extracts stops available to the user based on the user information of the user in the user information database corresponding to the acquired user ID and the stop information in the stop information database. The dispatch plan creation unit creates the dispatch plan according to a driving route based on the extracted stops. Then, when a passenger riding in the vehicle dispatched in accordance with the dispatch instruction is not the same as the user who is scheduled to board, the device updates the driving route based on stops available to the passenger that are different from stops available to the user who is scheduled to board, and updates the vehicle dispatch plan based on the updated driving route.

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

[0012] According to the present invention, when a user (passenger) other than the user who is scheduled to board the vehicle and who was specified at the time of the vehicle dispatch request boards the vehicle, the passenger who will actually board can select an available stop and transport the passenger to that stop.

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

[0014] FIG. 1 is a diagram illustrating an example of a schematic configuration of a vehicle dispatch service management system according to an embodiment of the present invention. FIG. 2 is a block diagram illustrating an example of a functional configuration model of a vehicle dispatch service management device according to an embodiment of the present invention. FIG. 3 is a diagram illustrating an example of a user information database of a vehicle dispatch service management device according to an embodiment of the present invention. FIG. 4 is a diagram illustrating an example of a bus stop information database of a vehicle dispatch service management device according to an embodiment of the present invention. FIG. 5 is a block diagram showing details of a vehicle dispatch planning unit in a vehicle dispatch service management device according to an embodiment of the present invention. FIG. 6A is a sequence chart illustrating an overview of a vehicle dispatch service in a vehicle dispatch service management system according to an embodiment of the present invention. FIG. 6B is a sequence chart illustrating an overview of a vehicle dispatch service in a vehicle dispatch service management system according to an embodiment of the present invention. FIG. 7 is a diagram illustrating an example of a planned-ride user selection screen displayed on a user interface of an information communication terminal device in the vehicle dispatch service system according to an embodiment of the present invention. FIG. 8 is a diagram illustrating an example of a bus stop selection screen displayed on a user interface of an information communication terminal device in the vehicle dispatch service system according to an embodiment of the present invention. FIG. 9 is a diagram illustrating an example of a bus stop selection screen displayed on a user interface of an information communication terminal device in the vehicle dispatch service system according to an embodiment of the present invention. Fig. 10 is a flowchart for explaining an example of a process for responding to a vehicle dispatch request in a vehicle dispatch service management device according to an embodiment of the present invention. Fig. 11A is a flowchart for explaining an example of a process at the time of vehicle dispatch in a vehicle dispatch service management device according to an embodiment of the present invention. Fig. 11B is a flowchart for explaining an example of a process at the time of vehicle dispatch in a vehicle dispatch service management device according to an embodiment of the present invention.

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

[0016] FIG. 1 is a diagram illustrating an example of a schematic configuration of a vehicle dispatch service management system according to an embodiment of the present invention. As shown in the diagram, the vehicle dispatch service management system 1 includes a vehicle dispatch service management device 10, an information and communication terminal device 20, and a vehicle V, which are communicatively connected to each other via a communication network N. The vehicle dispatch service management system 1 may also be connected via the communication network N to a road traffic information management system 30 that provides various traffic information in real time. The vehicle dispatch service management system 1 provides a vehicle dispatch service that dispatches multiple vehicles V to a certain area in response to a vehicle dispatch request from a user, for example. In the present disclosure, the vehicle V is assumed to be a manned vehicle driven by a driver, but is not limited thereto and may also be an unmanned vehicle (autonomous vehicle) without a driver.

[0017] The vehicle dispatch service management device 10 is a computing device that comprehensively manages vehicle dispatch services using multiple vehicles V in a target area of ​​the vehicle dispatch service (hereinafter referred to as the "service target area"). The service target area may be divided into several areas (sub-areas). Within the service target area, locations (hereinafter referred to as "stops") for users to board and disembark the vehicles V are set. The vehicle dispatch service management device 10, for example, implements a vehicle dispatch management server program and realizes the vehicle dispatch service by executing the vehicle dispatch management server program under the control of a processor.

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

[0019] In general, the vehicle dispatch service management device 10 responds to a vehicle dispatch request from a user who desires a vehicle dispatch service for travel from a departure point to a destination, selects a vehicle V to be allocated to the user, creates a vehicle dispatch plan for a company fee V, and proposes the created vehicle dispatch plan to the user. The vehicle dispatch service management device 10 confirms the proposed vehicle dispatch plan upon the user's consent to the proposed vehicle dispatch plan, and issues dispatch instructions to the vehicle V in accordance with the confirmed vehicle dispatch plan.

[0020] In the present disclosure, when a user (passenger) intending to board a vehicle V dispatched to a bus stop in accordance with a dispatch request is not the same as the intended boarding user specified at the time of the dispatch request, the dispatch service management device 10 may update the dispatch plan so as to change the destination to a bus stop that is available to the passenger and that is different from the specific bus stop available to the intended boarding user. A specific bus stop is a bus stop that can only be used (for boarding and disembarking) by users belonging to a specific group, and is a stop that is not permitted or restricted for use by users who do not belong to the specific group. Examples of such specific bus stops include bus stops located in locations that are accessible only to authorized personnel, such as on the premises of a school or company.

[0021] The dispatch plan includes a driving route that defines a location where the vehicle V is waiting (a starting waiting location), passing through several points (stops) along the way where users can get on and off, to a destination waiting location (which may not necessarily be the same as the initial waiting location). If the vehicle V is waiting, the dispatch plan is newly created based on a received dispatch request, and if the vehicle V is in operation, the dispatch plan can be updated based on a dispatch request. In a dispatch plan for a vehicle V in operation, users may share a ride.

[0022] The vehicle V is a vehicle registered in the vehicle information database 12c and provided for use by users in the vehicle dispatch service. The vehicle V may be a manned vehicle driven by a driver, or an unmanned vehicle (autonomous vehicle) without a driver. Furthermore, the vehicle V may be of any type (e.g., sedan, minivan, SUV, etc.).

[0023] The vehicle V is equipped with a control device CTL that controls the vehicle V itself or its onboard equipment in accordance with a dispatch instruction from the vehicle dispatch service management device 10 (see FIG. 2). Although not shown, the control device CTL is configured to include a processor, memory, etc., and realizes various functions by executing a vehicle control program. Furthermore, under the control of the control device CTL, the vehicle V acquires driving management information necessary for autonomous driving from various cameras and sensors and transmits this to the vehicle dispatch service management device 10. The vehicle dispatch service management device 10 can monitor and control the driving of the vehicle V in accordance with the driving management information transmitted from the vehicle V.

[0024] The vehicle V also includes a user authentication device UA. The user authentication device UA is a device for authenticating a user who boards the vehicle under the control of the control device CTL. For example, the user authentication device UA may use a camera to read a geometric pattern indicated by a ride-hailing app displayed on the user interface of the user's information communication terminal device 20, perform user authentication to determine whether the user is a user who plans to board the vehicle, and transmit the authentication result to the vehicle dispatch service management device 10. Alternatively, the user authentication device UA may use a camera, sensor, or the like to read the user's facial recognition information or biometric information to perform user authentication, and may transmit the read information (user authentication information) to the vehicle dispatch service management device 10 so that the vehicle dispatch service management device 10 can perform user authentication.

[0025] Although not shown, the vehicle V may be provided with an in-vehicle display for presenting various information to passengers under the control of the control device CTL. The in-vehicle display may have a touch panel function that can receive input from passengers.

[0026] The information and communication terminal device 20 is, for example, a computing device through which a user wishing to ride makes a vehicle dispatch request by operating a user interface. The information and communication terminal device 20 may be, for example, a smartphone, a pad computer, a laptop personal computer, a desktop computer, or the like, but is not limited to these. The information and communication terminal device 20 implements, for example, a vehicle dispatch management client program (a so-called vehicle dispatch app). The information and communication terminal device 20 executes the vehicle dispatch app under the control of a processor, thereby enabling the user to use the vehicle dispatch service of the vehicle dispatch service management device 10. For example, the user makes a vehicle dispatch request from a vehicle dispatch request screen (not shown) on the user interface of the information and communication terminal device 20. When requesting a vehicle dispatch, the user operates the vehicle dispatch app to specify a user who is scheduled to ride in the vehicle V. The user can make a reservation for a ride in the vehicle V by accepting the vehicle dispatch plan created and proposed by the vehicle dispatch service management device 10 in response to the vehicle dispatch request. For example, when getting into vehicle V, the user may receive user authentication by holding a geometric pattern shown by the ride-hailing app on the user interface of the information communication terminal device 20 over the user authentication device UA of vehicle V.

[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 various monitoring equipment installed on roads and travel data from a control device CTL mounted on the vehicle V, and manages road traffic information that is processed and edited in an integrated manner. The edited road traffic information may include, for example, information on road closures and detour routes, and the travel time between points via a specific route. The road traffic information management system 30 provides the road traffic information to the vehicle dispatch service management device 10 and the vehicle V as appropriate.

[0028] FIG. 2 is a block diagram illustrating an example of a functional configuration model of a vehicle dispatch service management device according to an embodiment of the present invention. As shown in the figure, the vehicle dispatch service management device 10 may be configured as a functional configuration model including functional components such as a front-end processing unit 110, a vehicle dispatch planning unit 120, and a vehicle communication unit 130. Furthermore, as described above, the vehicle dispatch service management device 10 includes various databases 12. This functional model is realized by the vehicle dispatch service management device 10 executing a vehicle dispatch management server program under the control of a processor, thereby cooperating with various hardware resources. The functional configuration model shown here is merely an example, and all or part of the functions of a certain functional component may be realized by other functional components. For ease of explanation, the figure also illustrates the user's information communication terminal device 20, and the control device CTL and user authentication device UA in the vehicle V.

[0029] The user information database 12a stores information about users who use the ride-hailing service (hereinafter referred to as "user information"). For example, as shown in FIG. 3, the user information includes, for each user, a user ID and password, personal attributes (such as gender, age, and address), and user group information. The user information is registered in the user information database 12a under the control of the ride-hailing service management device 10, for example, when the user inputs predetermined information upon first launching the ride-hailing app. The user ID is identification information for identifying a user who uses the ride-hailing service. In this example, an email address is used, but this is not limited to this and may be a unique code for each user. The user group information is information indicating the group to which the user belongs, and includes, for example, a "specific school student" group indicating that the user is a student attending a specific school, or a "related person" group indicating that the user belongs to a company, organization, family, or the like. In this example, users who do not belong to a specific group are assigned the "N / A" group.

[0030] The road map information database 12b stores road map information for the target area of ​​the vehicle dispatch service. The road map information includes map data on addresses, place names, road networks (links and nodes), various facilities (e.g., police stations), etc. The road map information also includes information necessary for searching for a driving route, such as road information, stop information, feature information, and environmental information. The road information includes road attribute information such as road type (e.g., community road or main road), road width, pedestrian / vehicle divider, median, and lane.

[0031] The vehicle information database 12c stores information (vehicle information) about the vehicle V available for use by the user. As shown in Fig. 3, the vehicle information includes, for example, a vehicle ID, vehicle attributes (vehicle registration number, vehicle model, maximum number of occupants / maximum load capacity, level of autonomous driving, etc.), vehicle characteristics, other specifications (total length, total width, vehicle height, weight, etc.), a current vehicle dispatch plan, a current location, and a current status (service status, remaining battery capacity (travel distance), number of occupants, etc.). The vehicle information, such as location information, acquired from the vehicle V via the vehicle communication unit 130 can be updated as needed.

[0032] The vehicle allocation plan database 12d stores a vehicle allocation plan for each vehicle V created by the vehicle allocation planning unit 120 based on a vehicle allocation request. As described above, the vehicle allocation plan includes a driving route from a waiting location serving as a starting point to a waiting location serving as an end point via several stops, an expected arrival time at each stop and / or intermediate point, and the like.

[0033] The bus stop information database 12e stores bus stop information related to locations (bus stops) where users can get on and off the vehicle V. For example, as shown in FIG. 4, the bus stop information includes, for each bus stop, geographical coordinates (such as latitude and longitude), auxiliary information (such as a name associated with the geographical coordinates), information about user groups that can use the bus stop, information about the available hours of the bus stop, and information about whether the bus stop is publicly available to user groups. This defines the conditions for users who can use each bus stop in the service area, making it possible to provide different vehicle dispatch services to each user. The bus stop information is also associated with the road map information database 12b.

[0034] The available user group information defines the group of users who can use the bus stop. For example, bus stops A and B are available only to users who belong to the group of specific commuter 001. Also, bus stop C is available to any user who can use the taxi dispatch service. This allows the taxi dispatch service management device 10 to extract available bus stops for each user according to the user group information in the user information database 12a.

[0035] The available time information indicates the days and / or times when the users indicated in the available user group information can use the bus stop. This allows you to set whether or not a user can use the bus stop depending on the day and / or time for each bus stop.

[0036] The disclosure information indicates whether the bus stop is to be disclosed to users other than the users indicated in the available user group information. For example, bus stop C is displayed on the screen of the dispatch app on the information communication terminal device 20 of all users who can use the dispatch service, while bus stop D is displayed only on the screen of the dispatch app on the information communication terminal device 20 of users who belong to the related party 101. This makes it possible to protect the privacy of users by displaying private bus stops, such as bus stops near their homes, only to related parties.

[0037] 2 , the front-end processing unit 110 performs various processes between the user and the information communication 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 information communication terminal device 20. The front-end processing unit 110 also receives a vehicle dispatch request from the vehicle dispatch application, passes it to the vehicle dispatch planning unit 120, and interacts with the information communication terminal device 20 to receive the user's approval or disapproval of the vehicle dispatch plan created by the vehicle dispatch planning unit 120 in response to the request.

[0038] In the present disclosure, the front-end processing unit 110 performs interactive processing with a vehicle dispatch app on the user's information communication terminal device 20 to acquire a vehicle dispatch request from the user. For example, when the front-end processing unit 110 receives access for a vehicle dispatch request from the vehicle dispatch app, the front-end processing unit 110 cooperates with a vehicle dispatch request acquisition unit 121 (described later) to display a geographical map including candidate bus stops on the vehicle dispatch app screen on the user interface of the information communication terminal device 20, and controls the front-end processing unit 110 to allow the user to select a bus stop for boarding or disembarking. Furthermore, when the user selects a bus stop on the geographical map, the front-end processing unit 110 passes the selected bus stop to the vehicle dispatch request acquisition unit 121.

[0039] The vehicle allocation planning unit 120 extracts candidate vehicles (candidate vehicles) from among the vehicles V within the target area based on the vehicle allocation request acquired via the front-end processing unit 110, creates a vehicle allocation plan for the candidate vehicles, and performs processing to execute the created vehicle allocation plan. The vehicle allocation planning unit 120 may propose a provisionally created vehicle allocation plan to a user and confirm the plan with the user's consent. The vehicle allocation planning unit 120 stores the confirmed vehicle allocation plan in the vehicle allocation plan database 12d and issues a dispatch instruction to the corresponding vehicle V via the vehicle communication unit 130. The vehicle V that receives the dispatch instruction travels toward the bus stop where the user indicated in the dispatch plan will board. In the present disclosure, the vehicle allocation planning unit 120 changes the destination bus stop according to a predetermined situation when the user (passenger) boarding at the bus stop is different from the user scheduled to board specified at the time of the dispatch request. For example, if the result of user authentication indicates that the passenger and the user planning to board are different, and the passenger does not belong to the group to which the user planning to board belongs and therefore is not available (can disembark) at the specific stop, the dispatch planning unit 120 selects a stop near the specific stop at which the passenger can disembark, and updates the dispatch plan for vehicle V accordingly.

[0040] The vehicle communication unit 130 exchanges various types of information with the vehicle V via the communication network N. For example, the vehicle communication unit 130 acquires vehicle information including the location information of the vehicle V and passes it on to the vehicle allocation planning unit 120, and also transmits operation instructions to the vehicle V in accordance with the allocation plan by the vehicle allocation planning unit 120. The vehicle communication unit 130 also acquires user authentication information of passengers who will board the vehicle V that has been allocated in accordance with the allocation request and passes it on to the vehicle allocation planning unit 120.

[0041] 5 is a block diagram showing details of a vehicle dispatch planner in a vehicle dispatch service management device according to one embodiment of the present invention. As shown in the figure, the vehicle dispatch planner 120 includes, for example, a vehicle dispatch request acquirer 121, a driving route determiner 122, a vehicle information acquirer 123, a vehicle selector 124, a vehicle dispatch plan creator 125, a vehicle dispatch instructor 126, and a passenger user identifier 127.

[0042] The vehicle dispatch request acquisition unit 121 interactively accepts a vehicle dispatch request from a user via the front-end processing unit 110 and acquires a confirmed vehicle dispatch request. The vehicle dispatch request includes the user ID of the user who is scheduled to board the vehicle V. The time when the vehicle dispatch request acquisition unit 121 acquires the vehicle dispatch request is the start time for counting various limit times for creating a vehicle dispatch plan (for example, a boarding limit time and a disembarking limit time, which are the limit times by which a user must board or disembark).

[0043] In this example, the dispatch request acquisition unit 121 includes a user information acquisition unit 1211, a user position information acquisition unit 1212, a display data generation unit 1213, and a bus stop acquisition unit 1214. The dispatch request acquisition unit 121 also acquires bus stops for the boarding users (passengers) identified by the boarding user identification unit 127. In this example, the dispatch request acquisition unit 121 is configured as part of the dispatch planning unit 120, but is not limited to this and may be configured as part of the front-end processing unit 110, etc.

[0044] The user information acquisition unit 1211 acquires user information (such as a user ID) corresponding to the user of the ride-dispatch app when a user's ride-dispatch request is transmitted from the information communication terminal device 20. For example, when the user logs in from the ride-dispatch app on the information communication terminal device 20, the user information acquisition unit 1211 acquires user information at the time of login. Furthermore, the user information acquisition unit 1211 acquires user information (user ID) associated with the ride-dispatch request and corresponding to a user who is scheduled to board the ride and is designated by the user.

[0045] The user location information acquisition unit 1212 acquires user location information indicating the user's current location based on the user's vehicle dispatch request transmitted from the information communication terminal device 20. For example, the user location information acquisition unit 1212 acquires user location information from the information communication terminal device 20 when the information communication terminal device 20 accesses the vehicle dispatch service management device 10 to request a vehicle dispatch from the user. GPS information is an example of user location information. The user location information is used, for example, to extract bus stops near the user's current location.

[0046] The display data generation unit 1213 performs control to display a predetermined ride-hailing app screen on the user interface of the information communication terminal device 20. For example, in response to a user's ride-hailing request transmitted from the information communication terminal device 20, the display data generation unit 1213 reads data from the road map information database 12b based on the acquired user position information and generates display data for displaying a geographical map based on the read map data, in order to allow the user to interactively select a ride-hailing stop. In this case, the display data generation unit 1213 may generate the display data in cooperation with the bus stop acquisition unit 1214. The generated display data is transmitted to the information communication terminal device 20 via the front-end processing unit 110. In response to this, a geographical map based on the display data is displayed in the ride-hailing app on the user interface of the information communication terminal device 20. For example, various potential bus stops available to the user may be visually distinguished and superimposed on the geographical map. The user may interactively select a ride-hailing stop or alighting stop on the geographical map displayed on the user interface of the information communication terminal device 20.

[0047] In response to a dispatch request, the bus stop acquisition unit 1214 extracts bus stop candidates available to the user and acquires a bus stop interactively selected by the user from the extracted bus stop candidates.

[0048] Specifically, the bus stop acquisition unit 1214 extracts bus stops corresponding to the group to which the user belongs as candidate bus stops based on the acquired user information. This allows only bus stops available to the user defined by the user group to be narrowed down and acquired. In this case, the bus stop acquisition unit 1214 may narrow down the candidate bus stops based on other items in the bus stop information database 12e, such as available time information and disclosure information. In the above example, if the user planning to board the bus belongs to the group designated as specific commuter 001, the bus stop acquisition unit 1214 may extract bus stops A and B as specific stops. Note that when extracting candidate bus stops where the user will board, the bus stop acquisition unit 1214 may narrow down the candidate bus stops to those near the user's current location based on user location information. The extracted candidate bus stops are superimposed on a geographical map displayed on the user interface of the user's information communication terminal device 20, and the user can select a desired stop from the candidate bus stops.

[0049] The bus stop acquisition unit 1214 also acquires, as bus stops for boarding and alighting, candidate bus stops selected by the user on the geographical map displayed on the user interface of the user's information communication terminal device 20. In response to this, the bus stop acquisition unit 1214 transfers the acquired bus stops for boarding and alighting to the travel route determination unit %%.

[0050] Furthermore, the bus stop acquisition unit 1214 may extract bus stop candidates for the passenger based on user information corresponding to the user ID of the user (passenger) attempting to board identified by the boarding user identification unit 127 described below. The extracted bus stop candidates may be presented to the passenger for selection via, for example, an in-vehicle display (not shown) of the vehicle V. The bus stop acquisition unit 1214 acquires a stop selected from the bus stop candidates presented to the passenger. This makes it possible to exclude stops at which passengers attempting to board the dispatched vehicle V cannot disembark.

[0051] Furthermore, when the bus stop acquired for the user who is planning to board is a specific stop where passengers cannot disembark, the bus stop acquisition unit 1214 can extract and acquire a bus stop that is located near the specific stop and where passengers can disembark. This makes it possible to ensure the convenience of passengers as much as possible even if passengers who are planning to board a vehicle cannot disembark at the specific stop.

[0052] Furthermore, when a passenger aboard a vehicle V currently receiving a dispatch service in accordance with a dispatch request from a preceding user and dispatched in accordance with the user's dispatch request is not the same as the user who is scheduled to board the vehicle and specified at the time of the dispatch request, and the stop where the preceding user plans to disembark is a specific stop where passengers cannot disembark, the stop acquisition unit 1214 can extract and acquire stops near the specific stop where passengers can disembark. This allows the preceding user and passengers to share the vehicle V, improving the dispatch efficiency of the vehicle V while preventing passengers from accessing the specific stop where they would not normally be able to disembark, in the case of a travel route where the stop where passengers disembark arrives before the specific stop.

[0053] The travel route determination unit 122 calculates and determines an optimal travel route based on the acquired vehicle dispatch request. For example, the travel route determination unit 122 determines a travel route from the departure point to the destination based on the departure point (the stop where the user boards) and the destination (the stop where the user disembarks) indicated in the vehicle dispatch request, by having the route search engine perform a route search while referring to the road map information database 12b.

[0054] The vehicle information acquisition unit 123 acquires vehicle information from each vehicle V via the vehicle communication unit 130 at a predetermined timing. The vehicle information may include vehicle position information and remaining energy amount of the vehicle V. For example, the vehicle information acquisition unit 123 may periodically acquire vehicle information transmitted from each vehicle V, or may periodically or irregularly request a specific vehicle V to transmit vehicle information, and acquire vehicle information transmitted from the specific vehicle V in response to the request. The vehicle information acquisition unit 123 stores the acquired vehicle information of each vehicle V in the vehicle information database 12c. The vehicle position information may be used when extracting a vehicle V to be dispatched to a user based on its positional relationship with the vehicle V's driving route.

[0055] The vehicle selection unit 124 extracts and selects a vehicle suitable for the travel route from among multiple vehicles V. For example, the vehicle selection unit 124 first references the vehicle information database 12c, etc., and extracts vehicles V near the departure point indicated in the vehicle dispatch request based on the location information indicated in the vehicle information. The vehicle selection unit 124 may select a vehicle V that has been dispatched to a preceding user who plans to head to the destination or an area nearby. Next, the vehicle selection unit 124 selects a vehicle V that is suitable for the travel route from among the extracted vehicles V, taking into consideration constraints such as various limit allowable times. For example, if the limit time for disembarking the preceding user to the destination is not met due to the travel route of a user who subsequently requests a vehicle dispatch, the vehicle selection unit 124 excludes the vehicle V in which such a preceding user is riding.

[0056] The vehicle allocation plan creation unit 125 creates a vehicle allocation plan for the selected vehicle V based on the determined driving route. The vehicle allocation plan creation unit 125 updates the vehicle allocation request for the vehicle V that is currently in operation. In the present disclosure, the vehicle allocation plan creation unit 125 can create a vehicle allocation plan for users sharing the vehicle V.

[0057] Furthermore, the vehicle allocation plan creation unit 125 proposes the created vehicle allocation plan to the user via the front-end processing unit 110. This allows the user to accept or reject (accept or reject) the proposed vehicle allocation plan. When the vehicle allocation plan creation unit 125 receives approval from the user for the proposed vehicle allocation plan, it finalizes the accepted vehicle allocation plan, stores the finalized vehicle allocation plan in the vehicle allocation plan database 12d, and issues a vehicle allocation instruction to the vehicles V of the vehicle allocation plan.

[0058] In addition, if the user who plans to board the vehicle V specified at the time of the vehicle dispatch request is not the same as the passenger who actually intends to board the vehicle V dispatched to the departure stop, and the destination stop indicated in the vehicle dispatch plan is not a stop where passengers can disembark (i.e., a specific stop), the vehicle dispatch plan creation unit 125 changes the vehicle dispatch plan so that an alternative stop where passengers can disembark is set as the destination.

[0059] The dispatch instruction unit 126 issues dispatch instructions to the corresponding vehicles V in accordance with the confirmed dispatch plan. Furthermore, if there is a change in the dispatch plan, the dispatch instruction unit 126 instructs the corresponding vehicles V to change the dispatch plan. The control device CTL of the vehicle V that has received the dispatch instruction determines, for example, a detailed actual driving route in accordance with the driving route in the dispatch plan, and performs control so that autonomous driving is performed along the actual driving route. For example, the dispatch instruction unit 126 issues a dispatch instruction to the vehicle V in accordance with the user's dispatch request so that the vehicle V picks up the user at a bus stop at the departure point and travels to a bus stop at the destination point.

[0060] Furthermore, if the user information (user ID) of the passenger is not acquired, the dispatch instruction unit 126 instructs the vehicle V to restrict the passenger from boarding the vehicle V. For example, the dispatch instruction unit 126 instructs the vehicle V to notify the passenger that the passenger is a user who is not registered with the dispatch service and therefore cannot use the service. This makes it possible to prevent a third party who is not eligible to use the dispatch service from unintentionally boarding the vehicle V.

[0061] Furthermore, when a vehicle V is currently providing a dispatch service in accordance with the dispatch request of another preceding user (hereinafter referred to as the "preceding user"), and the passengers aboard the vehicle V dispatched for a shared ride in accordance with the user's dispatch request are not the same as the user who is scheduled to board, and the stop at which the preceding user disembarks is a specific stop at which passengers cannot disembark, the dispatch instruction unit 126 can perform control to restrict passengers from boarding the vehicle V. This makes it possible to prevent passengers from accessing a specific stop at which they would not normally be able to disembark when a shared vehicle V is dispatched.

[0062] Furthermore, the dispatch instruction unit 126 performs control to deny passengers boarding the vehicle V currently undergoing the dispatch service when a stop extracted by the stop acquisition unit 1214 and at which passengers can disembark on the travel route indicated by the dispatch plan is a stop that arrives later than the specific stop at which the preceding user disembarks. As a result, if the stop at which passengers can disembark on the travel route arrives before the specific stop, it is possible to prevent passengers from accessing the specific stop at which they would not normally be able to disembark by allowing the preceding user and passengers to share the vehicle V, while improving the efficiency of vehicle dispatch.

[0063] Furthermore, the vehicle dispatch instruction unit 126 can perform control to deny passengers boarding the vehicle V currently receiving the vehicle dispatch service when the estimated travel time to the stop where the preceding user is to disembark exceeds a predetermined disembarkation limit time on a travel route that passes through other stops to the stop where the preceding user is to disembark. This can prevent a significant delay in the estimated travel time to the stop where the preceding user is to disembark, thereby preventing a deterioration in the vehicle dispatch service for the preceding user.

[0064] The boarding user identification unit 127 determines whether a passenger boarding a vehicle V dispatched in accordance with a dispatch request is the same as the planned boarding user, based on the user authentication information. As an example, the user authentication information may be a geometric pattern indicated by a dispatch app displayed on the user's information communication terminal device 20. As another example, the user authentication information may be the user's facial recognition information or biometric information. This makes it possible to determine whether a passenger who intends to board a vehicle V that has arrived at a bus stop in accordance with a dispatch instruction is eligible for the dispatch service. Furthermore, when the boarding user identification unit 127 determines that the passenger boarding a vehicle V is not the same as the planned boarding user, it refers to the user information database 12a and acquires the passenger's user ID. This makes it possible to use the acquired user ID to determine whether a passenger who intends to board a vehicle that has arrived at a bus stop in accordance with a dispatch instruction is eligible for the dispatch service.

[0065] 6A and 6B are sequence charts for explaining an overview of a vehicle dispatch service in a vehicle dispatch service management system according to an embodiment of the present invention. Specifically, Fig. 6A shows a sequence from when a vehicle V moves to a bus stop under the control of the vehicle dispatch service management device 10 in response to a vehicle dispatch request from a user, to when a passenger other than the user who is scheduled to board the vehicle V gets on board the vehicle V that has been dispatched to the bus stop in accordance with the vehicle dispatch request.

[0066] First, as shown in the figure, a user who wishes to use a vehicle dispatch service launches a vehicle dispatch application implemented in the information and communication terminal device 20 and logs in to the vehicle dispatch service (S601). In response to this, the information and communication terminal device 20 transmits a login request to the vehicle dispatch service management device 10, and the vehicle dispatch service management device 10 performs a login authentication process for the user based on the login request (S602). For example, the vehicle dispatch service management device 10 authenticates the user based on the user ID and password indicated in the login request.

[0067] When the user's login authentication is successful, the vehicle dispatch service management device 10 causes a planned-ride user selection screen, such as that shown in Fig. 7, to be presented on the user interface of the information communication terminal device 20 (S603). The user can select a user who plans to ride in the vehicle V on the planned-ride user selection screen. When the user specifies or selects a planned-ride user, the information communication terminal device 20 notifies the vehicle dispatch service management device 10 of the specified planned-ride user.

[0068] Upon receiving notification of the user who is planning to board, the vehicle dispatch service management device 10 refers to the user information database 12a to identify the group to which the user belongs, and then refers to the bus stop information database 12e to extract bus stops available to the user as candidate bus stops (S604). Note that when extracting candidate bus stops for a user, stops that other users have set as not public are not extracted. Next, the vehicle dispatch service management device 10 generates display data for displaying a bus stop selection screen on which the user can select a desired bus stop from the extracted candidate bus stops, and transmits this to the information communication terminal device 20 (S605). In response to this, a bus stop selection screen such as that shown in FIG. 8 is presented on the user interface of the information communication terminal device 20 (S606).

[0069] A user can select a bus stop for the user planning to board using the bus stop selection screen. FIG. 8 shows candidate bus stops S1-S4 available to the user planning to board, and illustrates the user selecting candidate bus stop S3, the closest candidate bus stop to the user's current location P, as the bus stop for boarding. After selecting the bus stop for boarding, the user may then select the bus stop at which the user planning to board will disembark. FIG. 9 illustrates a bus stop selection screen for selecting candidate bus stops near the user planning to board. In addition to stops S5 and S6 available to the user planning to board, specific stops SS1 and SS2 located on school grounds are also shown in FIG. 9. When the user selects a bus stop for boarding or disembarking, the information communication terminal device 20 notifies the vehicle dispatch service management device 10 of the selected stop.

[0070] When the stops for boarding and alighting are selected, the vehicle dispatch service management device 10 determines a travel route, selects a vehicle V that can be dispatched, and creates a vehicle dispatch plan (S607). Subsequently, the vehicle dispatch service management device 10 transmits the created vehicle dispatch plan to the information communication terminal device 20 to propose it to the user.

[0071] When the information communication terminal device 20 receives the vehicle dispatch plan, it displays it on the user interface as a vehicle dispatch plan proposal screen and prompts the user to accept or reject the proposed vehicle dispatch plan (S608). The vehicle dispatch plan proposal screen includes the above-mentioned expected arrival time, allowing the user to input their acceptance or rejection of the proposed vehicle dispatch plan based on the expected arrival time, etc. When the user inputs their acceptance or rejection on the vehicle dispatch plan proposal screen, the information communication terminal device 20 receives this and transmits an acceptance or rejection notice to the vehicle dispatch service management device 10. The vehicle dispatch service management device 10 confirms the vehicle dispatch plan for vehicle V based on the acceptance or rejection notice transmitted from the information communication terminal device 20 (S609). Next, the vehicle dispatch service management device 10 transmits a confirmation notice of the vehicle dispatch reservation to the information communication terminal device 20 and transmits a dispatch instruction to vehicle V in accordance with the vehicle dispatch plan. In response to this, vehicle V moves to the boarding stop indicated in the vehicle dispatch plan (S610).

[0072] Next, referring to FIG. 6B , when a user boards a vehicle V that has been dispatched to a bus stop in accordance with a dispatch request, the vehicle V cooperates with the dispatch service management device 10 to verify the boarding user (passenger) (S611). For example, the passenger holds a dispatch app over the user authentication device UA of the vehicle V, causing the user authentication device UA to acquire the passenger's user ID and transmit it to the dispatch service management device 10 as user authentication information. Alternatively, the user authentication device UA acquires the passenger's facial recognition information or biometric information and transmits it to the dispatch service management device 10 as user authentication information. In response to this, the dispatch service management device 10 determines whether the passenger is the same as the user who is scheduled to board the vehicle, based on the user authentication information. Here, a case will be described in which the passenger is not the same as the user who is scheduled to board the vehicle and is not able to disembark at a specific bus stop that the user who is scheduled to board the vehicle is available.

[0073] The vehicle dispatch service management device 10 refers to the user information database 12a to identify the group to which the passenger belongs, and then refers to the bus stop information database 12e to extract candidate bus stops at which the passenger can disembark (S612). Next, the vehicle dispatch service management device 10 generates display data for displaying a stop selection screen on which the passenger can select a desired stop from the extracted candidate bus stops (S613) and transmits this to the vehicle V. In response to this, the control device CTL of the vehicle V displays the stop selection screen on an in-vehicle display (S614). Note that if the passenger has an information communication terminal device 20 equipped with a vehicle dispatch app, the vehicle dispatch service management device 10 may control the stop selection screen to be displayed on the user interface of the passenger's information communication terminal device 20.

[0074] A passenger can select a bus stop for the user who is planning to board the bus from a bus stop selection screen displayed on the in-car display. When the user selects a bus stop at which to get off, the control device CTL notifies the vehicle dispatch service management device 10 of the selected bus stop.

[0075] When the stop for disembarking is selected, the vehicle dispatch service management device 10 determines a travel route and updates the vehicle dispatch plan (S615). Subsequently, the vehicle dispatch service management device 10 transmits the created vehicle dispatch plan to the information communication terminal device 20 to propose it to the user.

[0076] 10 is a flowchart illustrating an example of a process for responding to a dispatch request in a vehicle dispatch service management device according to an embodiment of the present invention. This process is realized by the vehicle dispatch service management device executing a vehicle dispatch management server program under the control of a processor, in cooperation with various hardware resources.

[0077] As shown in the figure, the vehicle dispatch service management device 10 waits until a new vehicle dispatch request is received from a user (S1001). Meanwhile, for example, a user who desires a vehicle dispatch accesses the vehicle dispatch service management device 10 from a vehicle dispatch application on the user interface of the information communication terminal device 20, and transmits a user ID and password to the vehicle dispatch service management device 10 to log in. At this time, the information communication terminal device 20 may transmit user location information based on a GPS system to the vehicle dispatch service management device 10.

[0078] When the vehicle dispatch service management device 10 receives an access from a user to request a vehicle dispatch (Yes in S1001), the vehicle dispatch service management device 10 displays a planned-ride user selection screen on the user interface of the information communication terminal device 20 (S1002). When the user selects a planned-ride user on the planned-ride user selection screen, the vehicle dispatch service management device 10 refers to the user information database 12a and acquires the user ID and user group information of the selected planned-ride user (S1003).

[0079] Next, the vehicle dispatch service management device 10 refers to the bus stop information database 12e according to the user group information corresponding to the acquired user ID, and extracts candidate bus stops available to the user who is planning to board the vehicle (S1004). At this time, the vehicle dispatch service management device 10 may narrow down the candidate bus stops to those near the user's current location based on the user location information. Next, the vehicle dispatch service management device 10 controls the information communication terminal device 20 to display a geographical map showing the extracted candidate bus stops on the user interface (S1005). When the user selects a bus stop for boarding or alighting from the candidate bus stops on the geographical map, the information communication terminal device 20 transmits the selected bus stop for boarding or alighting to the vehicle dispatch service management device 10. In response to this, the vehicle dispatch service management device 10 acquires the bus stop for boarding or alighting selected by the user (S1006).

[0080] Next, the vehicle dispatch service management device 10 creates a vehicle dispatch plan based on the acquired stops (S1007). That is, the vehicle dispatch service management device 10 determines a driving route based on the acquired stops, and further selects a vehicle V suitable for the determined driving route and creates a vehicle dispatch plan. If the vehicle dispatch service management device 10 selects a vehicle V in which a preceding user is already riding, it creates a vehicle dispatch plan in accordance with the users sharing a ride.

[0081] Next, the vehicle dispatch service management device 10 proposes the contents of the created / updated vehicle dispatch plan to the user (S1008). That is, the vehicle dispatch service management device 10 transmits the contents of the created vehicle dispatch plan to the information communication terminal device 20, and in response, the information communication terminal device 20 displays the contents on the user interface and prompts the user to accept or reject the proposed vehicle dispatch plan.

[0082] The vehicle dispatch service management device 10 determines whether or not the proposed vehicle dispatch plan has been accepted by the user (S1009). If the vehicle dispatch service management device 10 accepts the proposed vehicle dispatch plan from the user (Yes in S1009), the vehicle dispatch service management device 10 confirms the current vehicle dispatch plan (S1010). The vehicle dispatch service management device 10 stores the confirmed vehicle dispatch plan in the vehicle dispatch plan database 12d. Next, the vehicle dispatch service management device 10 transmits a notification of confirmation of the vehicle dispatch reservation to the information communication terminal device 20, and transmits a dispatch instruction based on the vehicle dispatch plan to the vehicle V (S1011). In response to this, the vehicle V moves to pick up the user at the selected bus stop.

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

[0084] Next, a process will be described when a user (passenger) boards a vehicle V that has been dispatched to a bus stop in accordance with a user's dispatch request. Figures 11A and 11B are flowcharts for explaining an example of a dispatch process in a vehicle dispatch service management device according to an embodiment of the present invention. Prior to this process, for example, the vehicle V acquires facial authentication information of the user (passenger) who is about to board the vehicle and transmits this information to the vehicle dispatch service management device 10 as authentication information.

[0085] That is, as shown in Fig. 11A, the vehicle dispatch service management device 10 acquires user authentication information of a passenger transmitted from a vehicle V that has arrived at a bus stop at the departure point (S1101). Next, the vehicle dispatch service management device 10 determines, based on the acquired user authentication information, whether the passenger attempting to board the vehicle V is the same as the user scheduled to board the vehicle specified at the time of the vehicle dispatch request (S1102).

[0086] If the vehicle dispatch service management device 10 determines that the passenger attempting to board vehicle V is the same as the user scheduled to board specified at the time of the vehicle dispatch request (Yes in S1102), the vehicle dispatch service management device 10 maintains the vehicle dispatch plan as is and terminates the dispatch processing. In other words, since the passenger can disembark at the specified stop, the vehicle dispatch plan is not changed. Therefore, vehicle V continues to board the passenger and heads to the destination stop.

[0087] On the other hand, if the vehicle dispatch service management device 10 determines that the passenger attempting to board the vehicle V is not the same as the planned boarding user specified at the time of the vehicle dispatch request (No in S1102), the vehicle dispatch service management device 10 subsequently determines whether the passenger has a predetermined relationship with the user who made the vehicle dispatch request (S1103). For example, if a guardian specifies a child as the planned boarding user, and the guardian is also a passenger, the vehicle dispatch service management device 10 determines that there is a relationship between the two. If the vehicle dispatch service management device 10 determines that the passenger is not related to the user who made the vehicle dispatch request (No in S1103), the vehicle dispatch service management device 10 instructs the vehicle V to refuse boarding the passenger. In response to this, the vehicle V notifies the passenger that boarding is not possible by displaying a message on the in-vehicle display and / or using audio guidance.

[0088] On the other hand, if the vehicle dispatch service management device 10 determines that the passenger has a relationship with the user who made the vehicle dispatch request (Yes in S1103), the vehicle dispatch service management device 10 subsequently determines whether the dispatched vehicle V is a shared vehicle with the preceding user (S1105). The processing when the vehicle dispatch service management device 10 determines that the dispatched vehicle V is a shared vehicle with the preceding user (Yes in S1105) will be described later (see FIG. 11B).

[0089] If the vehicle dispatch service management device 10 determines that the dispatched vehicle V is not a shared vehicle with a preceding user (No in S1105), the vehicle dispatch service management device 10 then determines whether the destination stop indicated in the dispatch request is a specific stop where passengers cannot disembark (S1106). If the vehicle dispatch service management device 10 determines that the destination stop is not a specific stop where passengers cannot disembark (No in S1106), the vehicle dispatch service management device 10 maintains the dispatch plan as is and terminates the dispatch processing. In other words, since passengers can disembark at the specific stop, the dispatch plan is not changed. Therefore, the vehicle V will pick up passengers and head to the destination stop.

[0090] On the other hand, when the vehicle dispatch service management device 10 determines that the destination stop indicated in the vehicle dispatch request is a specific stop where the passenger cannot get off (Yes in S1106), the vehicle dispatch service management device 10 extracts candidate stops where the passenger can get off, based on the user ID of the passenger based on the user authentication information (S1107). In this case, the vehicle dispatch service management device 10 can extract, as candidate stops, stops located near the specific stop where the user who is planning to board the vehicle planned to get off.

[0091] Next, the vehicle dispatch service management device 10 controls the display of a geographical map showing the extracted candidate stops on, for example, an in-vehicle display of the vehicle V (S1108). Note that the vehicle dispatch service management device 10 may also control the display of the geographical map on the user interface of the passenger's information communication terminal device 20. When the user selects an alternative stop for disembarking from the candidate stops on the geographical map, the vehicle V, under the control of the control device CTL, transmits the selected stop for disembarking to the vehicle dispatch service management device 10. In response to this, the vehicle dispatch service management device 10 acquires the stop for disembarking selected by the user (S1009).

[0092] When the vehicle dispatch service management device 10 acquires the bus stops for disembarking, it updates the vehicle dispatch plan based on the acquired bus stops (S1010). That is, the vehicle dispatch service management device 10 changes the travel route based on the acquired bus stops and updates the vehicle dispatch plan. Then, the vehicle dispatch service management device 10 instructs the vehicle V to travel in accordance with the updated vehicle dispatch plan (S1111).

[0093] Next, sharing a vehicle V will be described with reference to FIG. 11B . When the vehicle dispatch service management device 10 determines that the dispatched vehicle V is a shared vehicle with the preceding user (Yes in S1105), the vehicle dispatch service management device 10 determines whether the travel route indicated by the dispatch request includes a specific stop where the preceding user will disembark (S1112). That is, it is determined whether the travel section of the passenger who intends to board the dispatched shared vehicle V includes the specific stop where the preceding user will disembark. For example, if the stop at which the passenger can disembark on the travel route indicated by the dispatch plan is a stop that arrives later than the specific stop where the preceding user will disembark, it is determined that the travel section of the passenger includes the specific stop where the preceding user will disembark.

[0094] If the vehicle dispatch service management device 10 determines that the travel route indicated by the dispatch request does not include the specific stop where the preceding user will get off (No in S1112), the vehicle dispatch service management device 10 maintains the dispatch plan as is and terminates the dispatch processing. In other words, since passengers can get off at the specific stop of the preceding user, the dispatch plan is not changed. Therefore, the vehicle V continues to pick up passengers and head to the destination stop.

[0095] On the other hand, if the vehicle dispatch service management device 10 determines that the travel route indicated by the vehicle dispatch request includes the specific stop where the preceding user will get off (Yes in S1112), the vehicle dispatch service management device 10 then determines whether the passenger can get off at the specific stop where the preceding user will get off (S1113).If the vehicle dispatch service management device 10 determines that the passenger cannot get off at the specific stop where the preceding user will get off (No in S1113), the vehicle dispatch service management device 10 performs control to refuse the passenger from boarding the dispatched vehicle V (S1119).In this case, the vehicle dispatch service management device 10 may perform control to arrange for another vehicle V for the passenger.

[0096] On the other hand, if the vehicle dispatch service management device 10 determines that the passenger can get off at the specific stop where the preceding user is to get off (Yes in S1113), the vehicle dispatch service management device 10 subsequently determines whether the destination stop indicated in the dispatch request is a specific stop where passengers cannot get off (S1114).If the vehicle dispatch service management device 10 determines that the destination stop indicated in the dispatch request is a specific stop where passengers cannot get off (Yes in S1114), the vehicle dispatch service management device 10 performs control to deny the passenger from boarding the dispatched vehicle V (S1119).

[0097] On the other hand, if the vehicle dispatch service management device 10 determines that the destination stop indicated in the dispatch request is not a specific stop where the passenger cannot disembark (No in S1114), the vehicle dispatch service management device 10 acquires the destination stop where the passenger will disembark (S1115). That is, as described in the processing steps S1107 to S1109, the vehicle dispatch service management device 10 acquires an alternative disembarkation stop by displaying, for example, on an in-vehicle display of the vehicle V, a geographical map showing candidate stops where the passenger can disembark, extracted based on the passenger's user ID, and having the user select a stop. Next, the vehicle dispatch service management device 10 calculates a driving route that passes through the stop where the passenger will disembark (S1116).

[0098] Next, the vehicle dispatch service management device 10 determines, based on the calculated driving route, whether the estimated time required to reach the stop where the preceding user will disembark exceeds the disembarkation limit time (S1117). If the vehicle dispatch service management device 10 determines that the estimated time required to reach the stop where the preceding user will disembark exceeds the disembarkation limit time (Yes in S1117), the vehicle dispatch service management device 10 performs control to deny passengers from boarding the dispatched vehicle V (S1119). As a result, in the case of shared rides between users, if it is expected that the vehicle dispatch service for the preceding user will be impaired if a passenger other than the user scheduled to board specified at the time of the vehicle dispatch request boards the vehicle, it is possible to ensure the vehicle dispatch service for the preceding user by refusing to board the passenger.

[0099] On the other hand, if the vehicle dispatch service management device 10 determines that the estimated required time to the preceding user's bus stop does not exceed the disembarkation limit time (No in S1117), the vehicle dispatch service management device 10 updates the vehicle dispatch plan based on the calculated driving route (S1118).Then, the vehicle dispatch service management device 10 instructs the vehicle V to travel according to the updated vehicle dispatch plan (S1111).

[0100] As described above, according to this embodiment, when a user (passenger) other than the user who is scheduled to board and specified at the time of the dispatch request boards a vehicle V, the vehicle dispatch service management system 1 can select a stop that is available to the passenger who will actually board and transport the passenger there. In particular, according to this embodiment, when a passenger other than the user who is scheduled to board and specified at the time of the dispatch request actually boards a vehicle V dispatched in accordance with a dispatch request, and the original destination is a stop that is available to the user who is scheduled to board but not available to the passenger, the vehicle dispatch service management device 10 can transport the passenger to the changed destination by updating the dispatch plan to change the destination to a stop that is available to the passenger.

[0101] The above-described embodiments are merely illustrative examples of 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 invention. For example, in the methods disclosed herein, steps, operations, or functions may be performed in parallel or in a different order as long as the results are consistent. The described steps, operations, and functions 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. Furthermore, although various embodiments are disclosed in this specification, specific features (technical matters) in one embodiment may be added to or substituted for specific features in other embodiments, with appropriate modifications, and such forms are also within the spirit of the present invention.

[0102] 1... Vehicle dispatch service management system 10... Vehicle dispatch service management device 110... Front-end processing unit 120... Vehicle dispatch planning unit 121... Vehicle dispatch request acquisition unit 1211... User information acquisition unit 1212... User position information acquisition unit 1213... Display data generation unit 1214... Bus stop acquisition unit 122... Travel route determination unit 123... Vehicle information acquisition unit 124... Vehicle selection unit 125... Vehicle dispatch plan creation unit 126... Vehicle dispatch instruction unit 127... Passenger user identification unit 130... Vehicle communication unit 12... Database 12a... User information database 12b... Road map information database 12c... Vehicle information database 12d... Vehicle dispatch plan database 12e... Bus stop information database 20... Information communication terminal device 30... Road traffic information management system N... Communication network V... Vehicle CTL... Control device UA... User authentication device

Claims

1. A vehicle dispatch service management device that manages a vehicle dispatch service, comprising: a stop information database that manages stop information for each stop where users who use the vehicle dispatch service get on and off the vehicle; a user information database that manages user information for each user who can use the vehicle dispatch service; a vehicle dispatch request acquisition unit that acquires vehicle dispatch requests from users' information communication terminal devices; a vehicle dispatch plan creation unit that creates a vehicle dispatch plan for the vehicle based on the acquired vehicle dispatch request; and a vehicle dispatch instruction unit that issues dispatch instructions to the vehicle based on the created vehicle dispatch plan, wherein the vehicle dispatch request acquisition unit acquires a user ID of a user who plans to board the vehicle and is associated with the vehicle dispatch request, and extracts stops that can be used by the user based on the user information of the user who plans to board in the user information database that corresponds to the acquired user ID and the stop information in the stop information database, and the vehicle dispatch plan creation unit creates the vehicle dispatch plan in accordance with the extracted stops, a vehicle dispatch service management device that, when a passenger riding in the vehicle dispatched in accordance with the dispatch instruction is not the same as the user who is scheduled to board, updates a travel route based on stops available to the passenger that are different from stops available to the user who is scheduled to board, and updates the vehicle dispatch plan based on the updated travel route.

2. The vehicle dispatch service management device of claim 1, further comprising a passenger user identification unit that determines whether the passenger who will board the vehicle dispatched in accordance with the dispatch instruction is the same as the user who is scheduled to board.

3. The vehicle dispatch service management device described in claim 2, wherein the passenger user identification unit acquires the user ID of the passenger when the passenger who will board the vehicle dispatched in accordance with the dispatch instruction is not the same as the user who is scheduled to board.

4. The vehicle dispatch service management device of claim 2, wherein the vehicle dispatch request acquisition unit includes a stop acquisition unit that extracts and acquires stops available to the passenger based on user information corresponding to the acquired user ID of the passenger.

5. The vehicle dispatch service management device of claim 4, wherein, when the bus stop acquired for the user planning to board is a specific bus stop that is not available to the passenger, the stop acquisition unit extracts a stop that is located near the specific bus stop and is available to the passenger.

6. The vehicle dispatch service management device according to claim 2, wherein the vehicle dispatch instruction unit instructs the vehicle to restrict the passenger from boarding the vehicle if the user ID of the passenger is not obtained.

7. The vehicle dispatch service management device of claim 4, wherein the bus stop information includes at least one of information regarding a user group that can use the bus stop, information regarding the available hours of the bus stop, and information regarding whether the bus stop is publicly available to the user group.

8. The vehicle dispatch service management device according to claim 7, wherein the bus stop acquisition unit refers to the bus stop information in accordance with information relating to a user group indicated by the user information corresponding to the user ID, and extracts the bus stops.

9. The vehicle dispatch service management device of claim 4, wherein the dispatch instruction unit controls to restrict passengers from boarding a vehicle currently undergoing dispatch service in accordance with a dispatch request from a preceding user when the passengers boarding the vehicle dispatched in accordance with the user's dispatch request are not the same as the user scheduled to board, and the stop at which the preceding user disembarks is a specific stop that is not available to the passengers.

10. The vehicle dispatch service management device described in claim 9, wherein the dispatch instruction unit performs control to refuse the passenger from boarding a vehicle currently providing the dispatch service if a stop available to the passenger on the driving route of the dispatch plan is a stop that arrives later than the specific stop.

11. The vehicle dispatch service management device of claim 9, wherein the stop acquisition unit extracts other stops that are available to the passenger near a specific stop when a passenger riding in a vehicle currently undergoing dispatch service in accordance with a dispatch request of a preceding user and dispatched in accordance with the user's dispatch request is not the same as the user who is scheduled to board, and the stop that the preceding user plans to use is a specific stop that is not available to the passenger.

12. The vehicle dispatch service management device of claim 11, wherein the vehicle dispatch instruction unit performs control to refuse to allow the passenger to board a vehicle currently providing the vehicle dispatch service if the estimated travel time to the stop where the preceding user is to disembark exceeds a predetermined limit time on a route that passes through the other stops to the stop where the preceding user is to disembark.

13. A vehicle dispatch service management method by a vehicle dispatch service management device that manages a vehicle dispatch service, comprising: managing, in a stop information database, bus stop information for each stop where users who use the vehicle dispatch service get on and off the vehicle; managing, in a user information database, user information of each user who can use the vehicle dispatch service; acquiring a vehicle dispatch request from a user's information communication terminal device; creating a vehicle dispatch plan for the vehicle based on the acquired vehicle dispatch request; and issuing a dispatch instruction to the vehicle based on the created vehicle dispatch plan, wherein acquiring the vehicle dispatch request comprises: acquiring a user ID of a user who plans to board the vehicle and is associated with the vehicle dispatch request; and extracting stops that can be used by the user based on the user information of the user who plans to board in the user information database that corresponds to the acquired user ID and the stop information in the stop information database, wherein creating the vehicle dispatch plan comprises: creating the vehicle dispatch plan in accordance with a driving route based on the extracted stops, A vehicle dispatch service management method comprising: when a passenger riding in the vehicle dispatched in accordance with the dispatch instruction is not the same as the user who is scheduled to board, updating a travel route based on stops available to the passenger that are different from stops available to the user who is scheduled to board; and updating the vehicle dispatch plan based on the updated travel route.

Images