Vehicle allocation management device and vehicle allocation management method

Abstract

The present invention relates to a vehicle allocation management device which manages a vehicle allocation service on demand. The device comprises: a user information database for storing user information including at least one visitable place that a secondary user under the protection and supervision of a primary user can visit and a schedule of the secondary user; an event selection unit for selecting a specific event, in which the secondary user can participate, via a user interface on an information communication terminal device operated by the primary user; a schedule creation unit for creating the schedule of the secondary user on the basis of the selected specific event; a vehicle allocation plan creation unit for creating a vehicle allocation plan, of a vehicle to be allocated to the secondary user, on the basis of the created schedule; and a vehicle allocation instruction unit for giving a vehicle allocation instruction to the vehicle according to the created vehicle allocation plan.

Description

Vehicle allocation management device and vehicle allocation management method

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

[0002] One example of a mobility service is a service in which a guardian arranges a vehicle for picking up or dropping off a child or other person under their care. For example, Patent Document 1 below discloses a vehicle monitoring system in which a guardian can check the riding status of a person under their care in real time.

[0003] Japanese Patent Application Laid-Open No. 2022-069033

[0004] However, the system described in the above Patent Document 1 was unable to manage locations (e.g., bus stops) where the person being watched over could get on and off a vehicle under the protective supervision of a guardian. As a result, there was a risk that the person being watched over might get on or off a vehicle at a location not intended by the guardian, and the system was not sufficient to ensure the safety of the person being watched over.

[0005] Furthermore, the system was unable to take into account the schedule of the person being watched over and dispatch a vehicle for the person being watched over at the appropriate time and place, which meant that the guardian had to make an appropriate vehicle dispatch request on their own, taking into account the schedule of the person being watched over, which was inconvenient.

[0006] Therefore, the present invention aims to provide a service that appropriately dispatches vehicles to protected persons, such as children, based on events in the schedule of the protected person associated with places that the protected person can visit (visitable places).

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

[0008] According to one aspect, the present invention provides a vehicle dispatch management device for providing an on-demand vehicle dispatch service, the device comprising: a user information database that stores and manages user information, including at least one visitor location that a secondary user under the protective supervision of a primary user can visit and the secondary user's schedule; an event selection unit that selects a specific event in which the secondary user can participate via a user interface on an information communication terminal device operated by the primary user; a schedule creation unit that creates the schedule for the secondary user based on the selected specific event; a vehicle dispatch plan creation unit that creates a vehicle dispatch plan for vehicles to be dispatched to the secondary user based on the created schedule; and a vehicle dispatch instruction unit that issues vehicle dispatch instructions to the vehicles in accordance with the created vehicle dispatch plan.

[0009] The present invention also applies to a vehicle allocation management method executed by 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.

[0010] According to the present invention, a vehicle can be appropriately dispatched to a secondary user (e.g., a protected person) under the protective supervision of a primary user (e.g., a guardian) based on events in the secondary user's schedule associated with places (visitable places) that the secondary user can visit. In particular, according to the present invention, by having the primary user pre-register the visitable places of the secondary user, it becomes possible to create and manage the secondary user's schedule based on events associated with the registered visitable places. Furthermore, according to the present invention, a vehicle can be appropriately dispatched to the secondary user in accordance with the implementation of events in the secondary user's schedule.

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

[0012] 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. FIG. 2 is a block diagram illustrating an example of a functional configuration model of a vehicle dispatch management device according to an embodiment of the present invention. FIG. 3 is a diagram illustrating an example of the data structure of a user information database. FIG. 4 is a diagram illustrating an example of the table structure of a movement range management table in a vehicle dispatch management device according to an embodiment of the present invention. FIG. 5 is a diagram illustrating an example of the table structure of a movement range management table in a vehicle dispatch management device according to an embodiment of the present invention. FIG. 6 is a block diagram illustrating details of the vehicle dispatch management device in the vehicle dispatch management device according to an embodiment of the present invention. FIG. 7 is a flowchart illustrating an example of a process for creating a schedule management table by the vehicle dispatch management device according to an embodiment of the present invention. FIG. 8 is a flowchart illustrating an example of a process for creating a vehicle dispatch plan by the vehicle dispatch management device according to an embodiment of the present invention. FIG. 9 is a diagram illustrating an example of a user interface of a vehicle dispatch app on an information communication terminal device in the vehicle dispatch management system according to an embodiment of the present invention. FIG. 10A is a diagram illustrating an example of a user interface of a vehicle dispatch app on an information communication terminal device in the vehicle dispatch management system according to an embodiment of the present invention. FIG. 10B is a diagram illustrating an example of a user interface of a vehicle dispatch app on an information communication terminal device in the vehicle dispatch management system according to an embodiment of the present invention. FIG. 11 is a diagram showing an example of a user interface of a vehicle dispatch application on an information communication terminal device in a vehicle dispatch management system according to one embodiment of the present invention.

[0013] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the embodiments described below are merely examples, and are not intended to exclude various modifications or applications of techniques not explicitly described below. The present invention can be implemented in various modifications (e.g., 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.

[0014] 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, an information communication terminal device 20, and a vehicle V, which are interconnected so as to be able to communicate with each other via a communication network N. The vehicle dispatch management system 1 can also be connected via the communication network N to a road traffic information management system (not shown) that provides various traffic information in real time.

[0015] The vehicle dispatch management system 1 of the present disclosure provides, for example, an on-demand vehicle dispatch service using multiple vehicles V for a certain area. An "on-demand vehicle dispatch service" refers to a service that allocates (dispatches) a specific vehicle to a user in response to a vehicle dispatch request from the user. In other words, with an on-demand vehicle dispatch service, there is no user-specified vehicle reservation time; instead, an appropriate vehicle V is dispatched to the user based on the vehicle availability at that time. Furthermore, "immediate response" not only refers to dispatching a vehicle immediately in response to a user's vehicle dispatch request, but also includes a certain degree of time that the user would normally tolerate. The vehicle dispatch service of the present disclosure will be described as an example in which a vehicle V is dispatched to a secondary user under the supervision and care of a primary user to participate in various events, such as extracurricular activities. A guardian is an example of a primary user, and a protected individual, such as a child, is an example of a secondary user. Hereinafter, when there is no need to particularly distinguish between a primary user and a secondary user, either or both of them may be simply referred to as a "user."

[0016] The vehicle dispatch management device 10 is a computing device that comprehensively manages a vehicle dispatch service using multiple vehicles V in a target area of ​​the vehicle dispatch service (hereinafter referred to as the "service target area"). The service target area may be divided into several small areas (sub-areas). The vehicle dispatch management device 10, for example, implements 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. In particular, the vehicle dispatch management server program of the present disclosure includes subprograms or modules for creating and managing a schedule for a secondary user based on events related to predetermined locations that the secondary user can visit, creating an appropriate vehicle dispatch plan tailored to the events indicated in the schedule, and dispatching vehicles V to the secondary user in accordance with the vehicle dispatch plan.

[0017] The vehicle dispatch 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, and a vehicle dispatch plan database 12d (see FIG. 2). The databases 12 may be configured as part of the vehicle dispatch management device 10, or all or part of the databases 12 may be configured separately from the vehicle dispatch management device 10.

[0018] In general, the vehicle allocation management device 10 accepts a vehicle allocation request from a user who desires a vehicle allocation for travel to the user's destination (place to be visited), selects a vehicle V to be allocated to the user based on the vehicle allocation request, creates a vehicle allocation plan for the vehicle, and proposes the created vehicle allocation plan to the user. The vehicle allocation management device 10 confirms the proposed vehicle allocation plan upon the user's consent to the proposed vehicle allocation plan, and issues vehicle allocation instructions to the vehicle V in accordance with the confirmed vehicle allocation plan. For example, vehicle allocation requests are made directly by the primary user, or in conjunction with the implementation of an event associated with a place that the secondary user can visit.

[0019] The vehicle V is a vehicle registered in the vehicle information database 12c that is 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) driven by an automated driving system, and the so-called automated driving level does not matter.

[0020] The vehicle V is equipped with a control device CTL that controls the vehicle V itself or its onboard equipment (see FIG. 2). Although not shown, the control device CTL includes a processor, memory, etc., and realizes various functions by executing a vehicle control program. The control device CTL also acquires geographical position information of the vehicle V in real time using a positioning system such as GPS, and can use the acquired position information for navigation functions and transmit it to the vehicle dispatch management device 10.

[0021] The information communication terminal device 20 is, for example, a computing device through which a user (e.g., a primary user) wishing to arrange a vehicle operates a user interface to make a vehicle dispatch request. The information 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 communication terminal device 20 implements, for example, a vehicle dispatch management client program (a so-called vehicle dispatch app). The information communication terminal device 20 typically has a positioning function that acquires its own geographical location information in real time using a positioning system such as GPS. The information 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 management device 10. Note that the present disclosure does not exclude secondary users from owning the information communication terminal device 20. For example, the information communication terminal device 20 of the secondary user may be configured to be able to check its own location information, as well as its own schedule and vehicle dispatch plan (described later) on the user interface of the vehicle dispatch app.

[0022] As one example, the primary user may register at least one or more accessible locations that the secondary user can visit using vehicle V via a user interface (dispatch app screen) of a vehicle dispatch app executed on the information communication terminal device 20. As another example, the primary user may check events in the secondary user's schedule via the user interface of the vehicle dispatch app and, as necessary, select events in which the secondary user will participate. This allows the primary user to efficiently select events in which the secondary user will participate while referring to the secondary user's schedule. In response to the event selection, the vehicle dispatch management device 10 accepts an application to use the vehicle dispatch service and creates an appropriate vehicle dispatch plan so that vehicles are dispatched in accordance with the event. As yet another example, the primary user may review and accept the vehicle dispatch plan created to match the selected event via the user interface of the vehicle dispatch app. In response, the vehicle dispatch management device 10 confirms the created vehicle dispatch plan and issues a dispatch instruction to vehicle V in accordance with the vehicle dispatch plan.

[0023] FIG. 2 is a block diagram illustrating an example of a functional configuration model of a vehicle dispatch management device according to an embodiment of the present invention. As shown in the figure, the vehicle dispatch management device 10 may be configured as a functional configuration model including functional components such as a front-end processing unit 110, a user management unit 120, a vehicle dispatch planning unit 130, and a vehicle communication unit 140. The vehicle dispatch management device 10 is also configured to be able to access various databases 12. This functional model is realized when the vehicle dispatch management device 10 executes a vehicle dispatch management server program under the control of a processor, thereby cooperating with various hardware resources. The functional configuration model shown here is an example, and all or part of the functions of a certain functional component may be realized by other functional components.

[0024] The user information database 12a stores information about users who use the ride-hailing service (hereinafter referred to as "user information"). FIG. 3 is a diagram showing an example of the data structure of the user information database 12a. As shown in the figure, the user information includes, for example, the user's user ID and password, email address, and information about personal attributes (gender, age, address, etc.). The user information is registered in the user information database 12a under the control of the ride-hailing management device 10, for example, when the user inputs predetermined information when the ride-hailing app is first launched. In the present disclosure, if a user is a primary user, the user information is associated with or configured to include information about a secondary user (hereinafter referred to as "secondary user information"). The secondary user information includes, for example, the secondary user's user ID, name (nickname), attribute information, activity range management table, and schedule management table.

[0025] 4 shows an example of a movement range management table. The movement range management table 12a_1 is a table for managing the movement range of a secondary user. As shown in the figure, the movement range management table 12a_1 may include items such as visitable locations, geographical location information, bus stops, and usage times. The movement range management table 12a_1 is set for each secondary user, for example, via a ride-hailing app on the information communication terminal device 20 of the primary user.

[0026] FIG. 5 also shows an example of a schedule management table. The schedule management table 12a_2 is a table used by the primary user to manage the schedules of each secondary user. The schedule management table 12a_2 is set for each secondary user, for example, via a ride-hailing app on the primary user's information communication terminal device 20. The schedule management table 12a_2 has a certain data structure, but is shown in calendar format in FIG. 5 for ease of understanding. Each event in the secondary user's schedule is the secondary user's unit of action. Although not shown, each event is associated with the travel time required to participate in the event (hereinafter referred to as the "estimated travel time"). The estimated travel time is the scheduled start time for participating in the event.

[0027] Returning to FIG. 2 , the road map information database 12b stores road map information for the target area of ​​the vehicle dispatch service. The road map information includes, for example, map data related to 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, feature information, and environmental information. The road information includes, for example, road type such as a community road or a main road, and road attribute information such as road width, pedestrian / vehicle divider, median, and lane. The road map information is used, for example, to determine the driving route of the vehicle V indicated by the vehicle dispatch plan.

[0028] The vehicle information database 12c stores information (vehicle information) about vehicles V available for use by users. The vehicle information includes information about 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, current location, and current status (service status, remaining battery capacity (travel distance), number of occupants, etc.). The vehicle information is used, for example, to select the optimal vehicle V to be dispatched to a user.

[0029] The vehicle allocation plan database 12d stores a vehicle allocation plan for each vehicle V created by the vehicle allocation plan unit 130 based on a vehicle allocation request. The vehicle allocation plan includes a driving route from a waiting location serving as a starting point to a waiting location serving as a terminal point via several boarding and disembarking points (departure and arrival points), an estimated arrival time at each intermediate point, and the like.

[0030] The front-end processing unit 110 performs various processes by communicating information with the user's information communication terminal device 20. As one example, the front-end processing unit 110 performs login authentication processing in response to a login request with a vehicle dispatching app executed on the information communication terminal device 20 of the primary user. As another example, the front-end processing unit 110 performs various processes related to the secondary user with the primary user's vehicle dispatching app under the control of the user management unit 120. As yet another example, the front-end processing unit 110 performs processing under the control of the vehicle dispatch planning unit 130 with the primary user's vehicle dispatching app to propose a vehicle dispatch plan for vehicles to be dispatched to the secondary user and receive an acceptance or rejection of the plan.

[0031] The user management unit 120 manages users who use the ride-hailing service. In the present disclosure, the user management unit 120 performs various processes, particularly for the primary user to manage secondary users when using the ride-hailing service. For example, as described below, the user management unit 120 receives the secondary user's visitable locations (available bus stops) from the primary user's ride-hailing app and registers them in the movement range management table 12a_1 in the user information database 12a. The user management unit 120 also creates a schedule for the secondary user and registers it in the schedule management table 12a_2. The schedule may be created based on events associated with the secondary user's visitable locations, for example.

[0032] The vehicle allocation planning unit 130 extracts candidate vehicles from the vehicles V in the target area based on the vehicle allocation request and creates a provisional vehicle allocation plan. A provisional vehicle allocation plan may be created for each of several different candidate driving routes. The vehicle allocation planning unit 130 proposes the provisional vehicle allocation plan to the user and confirms it upon receiving the user's approval. The vehicle allocation planning unit 130 then 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 140.

[0033] In the present disclosure, the vehicle allocation planner 130 creates a vehicle allocation plan for vehicles to be allocated to a secondary user based on the secondary user's schedule. For example, the vehicle allocation planner 130 may refer to the created schedule management table 12a_2 and calculate the scheduled departure time from the departure point (boarding point) and the scheduled arrival time at the destination (drop-off point) based on the implementation time (e.g., start time) of an event in which the secondary user will participate and is registered in the schedule, thereby creating a vehicle allocation plan. In other words, because the vehicle allocation service of the present disclosure is an on-demand vehicle allocation service, the vehicle allocation planner 130 selects an appropriate vehicle V depending on the situation at the time of allocation for participation in the event, and creates a vehicle allocation plan for that vehicle.

[0034] The vehicle communication unit 140 exchanges various types of information with the vehicle V via the communication network N. For example, the vehicle communication unit 140 acquires vehicle information including the location information of the vehicle V and passes it to the vehicle allocation planning unit 130, and also transmits to the vehicle V a vehicle allocation instruction in accordance with the vehicle allocation plan made by the vehicle allocation planning unit 130.

[0035] FIG. 6 is a block diagram showing details of a vehicle dispatch management device according to an embodiment of the present invention. The diagram focuses on a functional configuration model of a user management unit 120 and a vehicle dispatch planner 130, which are particularly relevant to the present disclosure. As shown in the diagram, the user management unit 120 includes, for example, a visitable place registration unit 121, an event information acquisition unit 122, an event selection unit 123, a schedule creation unit 124, and a usage application acceptance unit 125. Here, the movement range management table 12a_1 and the schedule management table 12a_2 associated with the user information database 12a are configured as part of the user management unit 120. The vehicle dispatch planner 130 includes a vehicle dispatch plan creation unit 131 and a vehicle dispatch instruction unit 132.

[0036] The visitable place registration unit 121 acquires at least one visitable place that the secondary user can visit via the user interface of the ride-hailing app on the primary user's information communication terminal device 20 and registers it in the activity range management table 12a_1. The visitable place is associated with, for example, geographical location information, available bus stops, and usage hours (such as business hours). Specifically, the visitable place registration unit 121 acquires the secondary user's visitable places by, for example, displaying a list of facility names on the user interface of the ride-hailing app on the primary user's information communication terminal device 20, allowing the primary user to select a desired facility, and selecting a secondary user who can visit the facility (see FIG. 9 ). Alternatively, the visitable place registration unit 121 may acquire the secondary user's visitable places by having the primary user select a facility searched for by the primary user on a map displayed on the user interface of the ride-hailing app. The visitable place registration unit 121 registers the acquired visitable places of the secondary user in the activity range management table 12a_1 together with the geographical location information, bus stops, and usage hours.

[0037] The event information acquisition unit 122 acquires event information about various events from an external event information database (not shown), etc. The event information may include, for example, information about the event content (such as a festival, craft experience, extracurricular activities, or cram school), the event date and location, the number of participants, and eligibility requirements (such as age) for participation. This allows events taking place at or near accessible locations to be reflected in the secondary user's schedule.

[0038] The event selection unit 123 extracts and selects at least one event in which the secondary user can participate, based on the secondary user's visitable locations indicated in the user information and the acquired event information. For example, if a "Japanese drumming" event is being held at a "BB Exchange Center" within the service area, the event selection unit 123 extracts "Japanese drumming" as an event because the "BB Exchange Center" is a visitable location for the secondary user. This creates a schedule for the secondary user based on events in which the secondary user can participate at or near the visitable locations. Furthermore, the event selection unit 123 may control the display of a specific event in the user interface of the ride-hailing app so that the primary user can select a specific event in which the secondary user will participate from the extracted at least one event. This allows the primary user to easily and reliably select an event in which the secondary user can participate, based on the visitable locations registered in advance.

[0039] The schedule creation unit 124 creates a schedule for the secondary user based on the selected specific event. For example, the schedule creation unit 124 registers the specific event in the secondary user's schedule management table 12a_2 based on event information related to the specific event. This allows a schedule suitable for the secondary user to be created in accordance with the event participation conditions, such as the event content, date and time, location, number of participants, and eligibility, indicated by the event information.

[0040] The schedule creation unit 124 may also create a schedule based on at least one event extracted by the event selection unit 123. This allows a schedule to be created based on events suitable for the secondary user from various events. In this case, the events registered in the schedule are in an undetermined or unknown state as to whether the secondary user will participate. Therefore, the schedule creation unit 124 may control the events to be displayed on the user interface of the ride-hailing app so that the primary user can select whether or not to participate in the undetermined events indicated in the schedule. This allows the primary user to efficiently select events in which the secondary user can participate while referring to the secondary user's schedule.

[0041] The schedule creation unit 124 may also perform control so that the selected specific event is displayed in a visually distinct manner from other events in the schedule. Furthermore, the schedule creation unit 124 may also perform control so that events for which an application to use the ride-hailing service has been accepted by the application acceptance unit 125 (described below) are displayed in a visually distinct manner. This makes it possible to easily identify events in the schedule in which the secondary user will participate and for which an application to use the ride-hailing service has been accepted.

[0042] The application acceptance unit 125 accepts an application for the ride-hailing service based on an event that the secondary user will participate in. For example, the application acceptance unit 125 accepts an application for the ride-hailing service based on an event selected for a schedule displayed on the user interface of the ride-hailing app. This allows the application for the ride-hailing service to be made in accordance with the implementation of the event indicated in the schedule, thereby freeing the primary user from the hassle and hassle of forgetting to request a ride.

[0043] The vehicle allocation plan creation unit 131 accepts a vehicle allocation request from a user via the front-end processing unit 110 and determines a driving route to the destination based on the vehicle allocation request by referring to the road map information database 12b. Next, the vehicle allocation plan creation unit 131 refers to the vehicle information database 12c to select a vehicle V to be allocated to the user according to the determined driving route, and creates a vehicle allocation plan for the selected vehicle V. If the vehicle V is waiting, the vehicle allocation plan is created based on a new vehicle allocation request, while if the vehicle V is already operating with the user on board, the vehicle allocation plan creation unit 131 can be updated based on the new vehicle allocation request. The vehicle allocation plan creation unit 131 then proposes the created vehicle allocation plan to the user and confirms the proposed vehicle allocation plan based on the user's consent to the proposed vehicle allocation plan.

[0044] In the present disclosure, the vehicle dispatch plan creation unit 131 may create a vehicle dispatch plan based on a service application for a vehicle dispatch service related to an event. This results in a vehicle dispatch plan created to coincide with the implementation of the event associated with the service application. Alternatively, the vehicle dispatch plan creation unit 131 may create a vehicle dispatch plan according to the secondary user's schedule. For example, the vehicle dispatch plan creation unit 131 may refer to the secondary user's schedule management table 12a_2 and create a vehicle dispatch plan to coincide with the implementation time of the event indicated by event information related to the event in the schedule. "To coincide with the implementation time" includes the meaning of taking into account the expected travel time of the secondary user. This results in a vehicle dispatch plan being created for dispatching a vehicle V to the secondary user in time for the implementation time of the event.

[0045] More specifically, the vehicle allocation plan creation unit 131 creates a vehicle allocation plan for vehicle V based on the start time of the event, taking into account the expected travel time from the available bus stop (boarding point) near or closest to the secondary user's current location to the available bus stop (drop-off point) near or closest to the event location. The secondary user's current location may be identified using, for example, location information acquired from the secondary user's information communication terminal device 20, or may be estimated based on the unit of action for the time frame preceding the time frame for the event indicated in the schedule. The vehicle allocation plan creation unit 131 also takes into account travel time, such as walking, to each bus stop. For example, if a secondary user is at home and wants to participate in a Japanese drumming event at the BB Exchange Center at 15:00, and it takes 3 minutes to walk from the secondary user's home to the boarding location, 20 minutes to travel by vehicle V from the boarding location to the disembarking location, and 3 minutes to walk from the disembarking location to the event location, the vehicle dispatch plan creation unit 131 will select vehicle V that can arrive at the boarding location at, for example, 14:30, and create a vehicle dispatch plan for that vehicle.

[0046] Furthermore, the vehicle allocation plan creation unit 131 proposes the created vehicle allocation plan to the primary user, and upon receiving acceptance thereof, finalizes the vehicle allocation plan. That is, the vehicle allocation plan creation unit 131 transmits the vehicle allocation plan to the information communication terminal device 20 of the primary user via the front-end processing unit 110, and causes the vehicle allocation plan to be displayed on the user interface of the vehicle allocation app on the information communication terminal device 20. The primary user accepts or rejects the vehicle allocation plan, and in response, the information communication terminal device 20 transmits a notification of acceptance or rejection. Upon receiving the user's acceptance notification via the front-end processing unit 110, the vehicle allocation plan creation unit 131 finalizes the vehicle allocation plan.

[0047] The vehicle dispatch plan creation unit 131 may create a vehicle dispatch plan based on an event for which an application for the vehicle dispatch service has not yet been accepted, and propose this to the primary user along with the event. If the vehicle dispatch plan creation unit 131 accepts the primary user's consent, it may finalize the created vehicle dispatch plan even if an application for the vehicle dispatch service has not yet been accepted. This allows the primary user to receive proposals for vehicle dispatch services that match the event based on the secondary user's schedule, even if the secondary user's participation in the event is on hold.

[0048] The dispatch instruction unit 132 issues dispatch instructions to the corresponding vehicle V according to the confirmed dispatch plan. Furthermore, if there is a change in the dispatch plan, the dispatch instruction unit 132 notifies the corresponding vehicle V of the changed dispatch plan. Specifically, the dispatch instruction unit 132 issues a dispatch instruction to the vehicle V to pick up the user at the bus stop where the user is to board and travel to the bus stop where the user is to disembark. The control device CTL of the vehicle V that has received the dispatch instruction navigates the driver to travel according to the travel route in the dispatch plan, for example.

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

[0050] As shown in the figure, when a primary user logs in via the user interface of a vehicle dispatching app executed on the information communication terminal device 20, the vehicle dispatch management device 10 refers to the user information database 12a and acquires the secondary user's movement range from the movement range management table 12a_1 of the secondary user associated with the primary user (S701). For example, the vehicle dispatch management device 10 acquires the secondary user's visitable locations, nearby or nearest available bus stops for accessing the visitable locations, and usage times.

[0051] Meanwhile, the vehicle dispatch management device 10 acquires the latest event information from an external event database (S702). The event information may include, for example, information on the event content, the date and location, the number of participants, and eligibility requirements (such as age) for participation.

[0052] Next, the vehicle dispatch management device 10 extracts specific events that are suitable for the secondary user based on the acquired event information for the secondary user's range of activity (S703). For example, the vehicle dispatch management device 10 extracts events where the secondary user can visit, and further narrows down the events based on the available age and number of participants to extract specific events. The vehicle dispatch management device 10 may also exclude events that overlap with the secondary user's already scheduled events.

[0053] Next, the vehicle dispatch management device 10 calculates the estimated travel time required for the secondary user to travel to the location of the extracted specific event (S704). That is, based on the secondary user's schedule management table 12a_2, the vehicle dispatch management device 10 identifies an action unit for the time frame preceding the specific event time frame, and calculates the estimated travel time from the bus stop (boarding location) at the location indicated by the action unit to the bus stop (drop-off location) for the specific event according to the optimal travel route. For example, if the secondary user is at home during the previous time frame, the estimated travel time is the sum of the walking time near or from the home to the nearest bus stop (boarding location), the vehicle travel time from the boarding location to the specific event stop (drop-off location), and the walking time from the drop-off location to the specific event location. Note that the vehicle travel time here is an estimated travel time that takes into account, for example, the optimal travel route and past travel history, since the actual travel time varies depending on the situation at the time of dispatch (such as the travel route of the selected vehicle V and road congestion conditions) under an on-demand vehicle dispatch service.

[0054] Next, the vehicle dispatch management device 10 registers the extracted specific event in the schedule management table 12a_2 of the secondary user (S705). In this case, the vehicle dispatch management device 10 associates the specific event with the estimated travel time and registers it. As a result, a schedule management table 12a_2 such as that shown in FIG. 5 is created.

[0055] For the schedule shown in the schedule management table 12a_2 created as described above, the primary user can check the events in the secondary user's schedule via the user interface of the ride-hailing app on the information communication terminal device 20, and, if necessary, select the events in which the secondary user will participate.

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

[0057] As shown in the same figure, when a primary user logs in via the user interface of a vehicle dispatching app executed on the information communication terminal device 20, the vehicle dispatch management device 10 executes the process shown in Figure 7, for example, to update the schedule management table 12a_2 of the secondary user associated with the primary user (S801).

[0058] Next, the vehicle dispatch management device 10 determines whether or not there is an event whose scheduled start time has arrived, according to the schedule management table 12a_2 (S802). The scheduled start time is a time set depending on the estimated travel time required to participate in the event. If the vehicle dispatch management device 10 determines that there is no event whose scheduled start time has arrived (No in S802), the vehicle dispatch management device 10 returns to executing the processing step of S801. On the other hand, if the vehicle dispatch management device 10 determines that there is an event whose scheduled start time has arrived (Yes in S802), the vehicle dispatch management device 10 then determines whether or not a usage application for the event has already been made (S803).

[0059] If the vehicle dispatch management device 10 determines that a usage application for the event has not already been submitted (No in S803), the vehicle dispatch management device 10 controls the user interface of the vehicle dispatch app on the primary user's information communication terminal device 20 to display an event participation proposal screen (not shown) to propose that the secondary user participate in the event (S804). Next, the vehicle dispatch management device 10 determines whether the usage application has been accepted via the user interface of the vehicle dispatch app (S805).

[0060] If the vehicle dispatch management device 10 determines that the application for use has not been accepted (No in S805), the vehicle dispatch management device 10 returns to the execution of the processing step of S801. On the other hand, if the vehicle dispatch management device 10 determines that the application for use has been accepted (Yes in S805), the vehicle dispatch management device 10 creates a vehicle dispatch plan (S806). That is, the vehicle dispatch management device 10 determines a driving route based on the boarding and disembarking locations, selects a vehicle V to be assigned to the user, and creates the vehicle dispatch plan.

[0061] On the other hand, if the vehicle dispatch management device 10 determines that a usage application for the event has already been completed (Yes in S803), the vehicle dispatch management device 10 creates a vehicle dispatch plan (S806).

[0062] Next, the vehicle dispatch management device 10 proposes the contents of the created / updated vehicle dispatch plan to the user (S807). That is, the vehicle dispatch management device 10 transmits the contents of the created / updated vehicle dispatch plan to the information communication terminal device 20 of the primary user, and in response, the information communication terminal device 20 displays the contents on the user interface and prompts the primary user to accept or reject the proposed vehicle dispatch plan. This allows the primary user to decide whether or not to use a vehicle according to the created vehicle dispatch plan without a direct vehicle dispatch request.

[0063] The vehicle dispatch management device 10 determines whether the vehicle dispatch plan proposal has been accepted from the primary user (S808). If the vehicle dispatch management device 10 accepts the vehicle dispatch plan proposal from the user (Yes in S808), the vehicle dispatch management device 10 confirms the current vehicle dispatch plan (S809). The vehicle dispatch management device 10 stores the confirmed vehicle dispatch plan in the vehicle dispatch plan database 12d. Next, the vehicle dispatch 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 (S810).

[0064] On the other hand, if the vehicle dispatch management device 10 receives a non-acceptance (rejection) from the user in response to the proposed vehicle dispatch plan (No in S808), it cancels the current vehicle dispatch plan based on the user's vehicle dispatch request (S811). In this case, the vehicle dispatch management device 10 returns the temporarily held vehicle dispatch plan that was used to recreate the vehicle dispatch plan to the original held vehicle dispatch plan.

[0065] 9 is a diagram showing an example of a user interface of a vehicle dispatch app on an information communication terminal device in a vehicle dispatch management system according to an embodiment of the present invention. More specifically, the diagram shows the transition of the vehicle dispatch app screen when a primary user registers a location that a secondary user can visit.

[0066] First, the primary user logs in to the ride-hailing app on the information communication terminal device 20 and displays a menu screen, such as that shown in FIG. 1A, on the user interface. Next, the primary user selects, for example, "Register visitable locations" by tapping on the menu screen.

[0067] In response to this, the information communication terminal device 20 accesses the vehicle dispatch management device 10 and displays, on the user interface, a visitable place registration screen showing a list of visitable places, as shown in FIG. 1B, for example. Next, the primary user selects, for example, an item "BB Exchange Center" on the visitable place registration screen. In response to this, the information communication terminal device 20 accesses the vehicle dispatch management device 10 and displays, on the user interface, a secondary user registration screen showing a list of secondary users who can visit the "BB Exchange Center," as shown in FIG. 1C, for example. On the secondary user registration screen, the primary user selects a secondary user to be registered for the visitable place "BB Exchange Center" and selects "Register." In response to this, the vehicle dispatch management device 10 updates the secondary user's activity range management table 12a_1 associated with the primary user's user information. In this case, the vehicle dispatch management device 10 references the road map information database 12b, obtains the bus stops near or nearest the visitable places and the usage times of the visitable places, and associates them with the visitable places.

[0068] 10A and 10B are diagrams illustrating an example of a user interface of a vehicle dispatch app on an information communication terminal device in a vehicle dispatch management system according to an embodiment of the present invention. More specifically, FIGS. 10A and 10B illustrate transitions of the vehicle dispatch app screen when a vehicle dispatch service application is made in accordance with an event in which a secondary user is participating in a primary user's schedule.

[0069] First, the primary user operates the ride-hailing app to which they are logged in on the information communication terminal device 20 to display a schedule screen, such as that shown in FIG. 1A, on the user interface. In this example, the schedule screen is displayed in a monthly schedule format. Furthermore, the event "ccc" on the "20th" is displayed visually distinct because an application for the ride-hailing service has already been accepted. Next, the primary user selects, for example, the "15th" on the schedule screen.

[0070] In response, the information communication terminal device 20 accesses the vehicle dispatch management device 10 and displays a schedule screen in the form of a one-day schedule, such as that shown in FIG. 1B. In this example, a "Japanese drumming" event is displayed from 15:00 to 16:00 on the 15th, and below it, it is displayed that no application for the vehicle dispatch service for "Japanese drumming" has yet been made. This allows the primary user to immediately know whether there are any Japanese drumming events at locations that the secondary user can visit, and whether any applications have been made for use. The primary user selects the application button to apply for the vehicle dispatch service for "Japanese drumming."

[0071] In response to this, the information communication terminal device 20 accesses the vehicle dispatch management device 10 and displays, on the user interface, an event participant user registration screen for registering secondary users who will participate in the event, as shown in B(a) of the same figure. Next, the primary user selects a secondary user who will participate in the event from the list of secondary users and selects "Register."

[0072] In response to this, the information communication terminal device 20 accesses the vehicle dispatch management device 10 and displays, on the user interface, a screen indicating completion of application for the vehicle dispatch service, such as that shown in B(b) in the same figure. As a result, the vehicle dispatch management device 10 sets the time (scheduled start time) for creating a vehicle dispatch plan for the "Japanese Taiko" event, taking into account the expected travel time.

[0073] 11 is a diagram illustrating an example of a user interface of a vehicle dispatch application on an information communication terminal device in a vehicle dispatch management system according to an embodiment of the present invention. More specifically, the diagram illustrates a vehicle dispatch plan proposal screen by the vehicle dispatch application of a primary user.

[0074] That is, when the scheduled start time for participating in the event arrives, the vehicle dispatch management device 10 creates a vehicle dispatch plan and controls so that a vehicle dispatch plan proposal screen such as that shown in Fig. 1(a) is displayed on the user interface of the vehicle dispatch app on the information communication terminal device 20. By selecting, for example, "details" on this vehicle dispatch plan proposal screen, the primary user can display a details screen such as that shown in Fig. 1(b) and check the details of the movement by vehicle V.

[0075] As described above, according to this embodiment, the vehicle dispatch management device 10 can appropriately dispatch vehicles to secondary users based on events in the schedule of the secondary users associated with the secondary users' visitable locations under the primary user's protective supervision. In particular, according to this embodiment, the vehicle dispatch management device 10 can create and manage the secondary users' schedules based on events associated with the secondary users' pre-registered visitable locations. Furthermore, according to this embodiment, the vehicle dispatch management device 10 can appropriately dispatch vehicles to secondary users in accordance with the implementation of events in the secondary users' schedules.

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

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

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

[0079] DESCRIPTION OF SYMBOLS 1... Vehicle dispatch management system 10... Vehicle dispatch management device 110... Front-end processing unit 120... User management unit 121... Visitable place registration unit 122... Event information acquisition unit 123... Event selection unit 124... Schedule creation unit 125... Usage application acceptance unit 130... Vehicle dispatch planning unit 131... Vehicle dispatch plan creation unit 132... Vehicle dispatch instruction unit 140... Vehicle communication unit 12... Database 12a... User information database 12a_1... Movement range management table 12a_2... Schedule management table 12b... Road map information database 12c... Vehicle information database 12d... Vehicle dispatch plan database 20... Information communication terminal device N... Communication network V... Vehicle CTL... Control device

Claims

1. A vehicle dispatch management device that provides an on-demand vehicle dispatch service, comprising: a user information database that manages user information including at least one or more accessible locations that a secondary user under the protective supervision of a primary user can visit, and the secondary user's schedule; an event selection unit that selects specific events in which the secondary user can participate, via a user interface on an information communication terminal device operated by the primary user; a schedule creation unit that creates the schedule for the secondary user based on the selected specific events; a vehicle dispatch plan creation unit that creates a vehicle dispatch plan for vehicles to be dispatched to the secondary user based on the created schedule; and a vehicle dispatch instruction unit that issues dispatch instructions to the vehicles in accordance with the created vehicle dispatch plan.

2. The vehicle dispatch management device of claim 1, further comprising an event information acquisition unit that acquires event information related to events, wherein the event selection unit extracts at least one event in which the secondary user can participate based on the visitable locations indicated by the user information and the acquired event information.

3. The vehicle dispatch management device of claim 2, wherein the event selection unit controls the specific event to be displayed on the user interface so that the primary user can select the specific event from the at least one extracted event.

4. The vehicle dispatch management device according to claim 3, wherein the schedule creation unit creates the schedule based on the selected specific event.

5. The vehicle dispatch management device according to claim 2, wherein the schedule creation unit creates the schedule based on the extracted at least one event.

6. The vehicle dispatch management device according to claim 5, wherein the schedule creation unit controls the display of events indicated by the schedule in which the secondary user will participate on the user interface to allow the primary user to select the events.

7. The vehicle dispatch management device according to claim 5, further comprising an application acceptance unit that accepts an application to use the vehicle dispatch service based on the event selected by the primary user in the displayed schedule.

8. The vehicle dispatch management device according to claim 7, wherein the schedule creation unit performs control so that the events corresponding to accepted applications for use of the vehicle dispatch service are displayed in a visually distinct manner in the schedule.

9. The vehicle dispatch management device according to claim 7, wherein the vehicle dispatch plan creation unit creates the vehicle dispatch plan based on the received application for use.

10. The vehicle dispatch management device according to claim 7, wherein the vehicle dispatch plan creation unit creates the vehicle dispatch plan in accordance with the implementation time of the selected event indicated by the event information.

11. The vehicle dispatch management device according to claim 1, wherein the vehicle dispatch plan creation unit controls the vehicle dispatch plan to be displayed on the user interface in order to have the primary user approve the created vehicle dispatch plan.

12. A vehicle dispatch management method using a vehicle dispatch management device that provides an on-demand vehicle dispatch service, comprising: managing user information in a user information database, including at least one or more visitor locations that a secondary user under the protective supervision of a primary user can visit, and the secondary user's schedule; selecting specific events that the secondary user can participate in via a user interface on an information communication terminal device operated by the primary user; creating the secondary user's schedule based on the selected specific events; creating a vehicle dispatch plan for vehicles to be dispatched to the secondary user based on the created schedule; and issuing dispatch instructions to the vehicles in accordance with the created vehicle dispatch plan.

Images