JP7697653B2 - Information processing system, information processing program, and information processing method - Google Patents

Description

The present invention relates to an information processing system, an information processing program, and an information processing method.

Currently, in the context of MaaS (Mobility as a Service), on-demand mobility (also called on-demand transportation), which operates based on user requests rather than on a timetable, is attracting attention. For example, some local governments are conducting demonstration experiments of on-demand bus transportation in order to operate bus services more efficiently.

In light of such circumstances, there is a demand for on-demand mobility to be incorporated into route searches. Incidentally, the route search service provided by the present applicant is equipped with a flight-specified search function that searches for a route using the public transportation that the user wants to ride (for example, a Shinkansen train with a reserved seat) by searching and specifying the flight name or timetable. When a route search is performed using the flight-specified search function and a route including a transfer from on-demand mobility (for example, a taxi) to a designated public transportation flight is searched and displayed, if the user executes a request for dispatching an on-demand mobility vehicle (immediate dispatch) immediately after checking the route in the search results, the timing of the dispatch request may be too early, resulting in a long waiting time after arriving at the public transportation station. On the other hand, if the user requests a dispatch too late, the user will miss the public transportation that he or she wants to ride. Therefore, even if a route including a transfer from on-demand mobility to a designated public transportation flight is searched and displayed, the user cannot determine when to call the on-demand mobility vehicle, and must constantly be concerned about the timing of the dispatch request.

Patent Document 1 proposes a technology that searches for a route from a departure point to a destination, and if the route search results include a route by taxi, asks the user whether or not to reserve the taxi. When a taxi reservation request is received from the user, the taxi boarding location and the scheduled transfer time are extracted, and the location, scheduled time, and the name of the person reserving the taxi are sent to a taxi reservation center to arrange the reservation.

However, currently it is difficult to realize reserved vehicle dispatch for on-demand mobility. For operators, making various preparations for reservations would significantly reduce utilization rates, making it unprofitable. Furthermore, if they tried to design it to be profitable, the reservation fees would be high, which would be disadvantageous for users, and so operators almost always do not accept reserved vehicle dispatch.

JP 2002-365082 A

The present invention has been made in consideration of the above points. The object of the present invention is to provide an information processing system, an information processing program, and an information processing method that can make a vehicle dispatch request at an appropriate time when a route is searched for and output that includes a transfer from on-demand mobility to a designated public transportation service or to public transportation with a fixed departure time, or when a route is searched for and output that includes a transfer from public transportation to on-demand mobility, even if the on-demand mobility cannot be reserved.

The information processing system according to the present invention comprises:
A search condition acquisition means for acquiring route search conditions;
a route search means for searching for a route based on the route search conditions;
a route output control means for outputting the route as a result of the search;
When outputting a route that includes a transfer from on-demand mobility to a designated public transportation service or public transportation with a fixed departure time, or when outputting a route that includes a transfer from public transportation to on-demand mobility, the route output control means obtains a predicted dispatch time for on-demand mobility to the on-demand mobility boarding position, and performs control related to the dispatch request taking into account the predicted dispatch time.

According to the present invention, when a route is searched for and output that includes a transfer from on-demand mobility to a designated public transportation service or to public transportation with a fixed departure time, or when a route is searched for and output that includes a transfer from public transportation to on-demand mobility, a vehicle dispatch request can be made at an appropriate time even if the on-demand mobility cannot be reserved.

FIG. 1 is a diagram showing a schematic configuration of an information processing system according to an embodiment. FIG. 2 is a flowchart showing a first example of the operation of the information processing system. FIG. 3A is a flowchart showing a second example of the operation of the information processing system. FIG. 3B is a flowchart showing a third example of the operation of the information processing system. FIG. 4 is a diagram showing an example of a screen displayed by the information processing system. FIG. 5 is a diagram showing an example of a screen displayed by the information processing system. FIG. 6 is a diagram showing an example of a screen displayed by the information processing system. FIG. 7 is a diagram showing an example of a screen displayed by the information processing system. FIG. 8 is a diagram showing an example of a screen displayed by the information processing system. FIG. 9 is a diagram showing an example of a screen displayed by the information processing system.

Below, an embodiment of the present invention will be described in detail with reference to the attached drawings. Note that in each drawing, components having equivalent functions are given the same reference numerals, and detailed descriptions of components with the same reference numerals will not be repeated.

In the embodiments described below, taxis are used as an example of "on-demand mobility." However, "on-demand mobility" is not limited to taxis, and includes various on-demand services such as ride-sharing taxis, shared buses, demand buses, and services that can dispatch a means of transportation to a user's desired location (car delivery rentals), so long as the service is a transportation service that operates based on a user's request and not on a timetable. "On-demand mobility" may also be an autonomous vehicle.

(Configuration of Information Processing System)
1 is a diagram showing a schematic configuration of an information processing system 1 according to an embodiment of the present invention. In the diagram, each functional unit that performs each function can be said to be a means for performing each function.

As shown in FIG. 1, the information processing system 1 includes a terminal device 2 and a server 3. The terminal device 2 and the server 3 are connected to each other so that they can communicate with each other via a network 4 such as the Internet. The network 4 may be either a wired line or a wireless line, and the type and form of the line are not important. At least a portion of the terminal device 2 and the server 3 are realized by a computer.

The terminal device 2 is used by a user, and is, for example, an electronic device such as a mobile terminal such as a smartphone or a tablet terminal, a notebook computer, or a desktop computer.

As shown in FIG. 1, the terminal device 2 has a terminal communication unit 21, a terminal control unit 22, a terminal storage unit 23, a terminal input unit 24, a terminal output unit 25, and a terminal positioning unit 26. Each unit is connected to each other via a bus so that they can communicate with each other.

The terminal communication unit 21 is a communication interface between the terminal device 2 and the network 4. The terminal communication unit 21 transmits and receives information between the terminal device 2 and the server 3 via the network 4.

The terminal control unit 22 is a control means that performs various processes of the terminal device 2. The terminal control unit 22 may be realized by a processor in the terminal device 2 executing a predetermined program, or may be implemented in hardware.

The terminal storage unit 23 is a data storage such as an internal memory or an external memory (such as an SD memory card). Various data handled by the terminal control unit 22 is stored in the terminal storage unit 23. The terminal storage unit 23 does not necessarily have to be provided in the terminal device 2, and a part or all of the terminal storage unit 23 may be provided in another device that is communicatively connected to the terminal device 2 via the network 4.

The terminal input unit 24 is an interface through which the user inputs information into the terminal device 2, such as a touch panel or microphone in a mobile terminal, or a touch pad, keyboard, or mouse in a notebook computer.

The terminal output unit 25 is an interface that outputs various information from the terminal device 2 to the user, and is, for example, a video display means such as a liquid crystal display or an audio output means such as a speaker. Specifically, for example, the terminal output unit 25 may display a GUI (Graphical User Interface) for receiving operations from the user.

The terminal positioning unit 26 is a positioning means that measures the current position of the terminal device 2. The terminal positioning unit 26 measures the current position based on positioning information from radio navigation means such as GPS or the Quasi-Zenith Satellite System (QZSS). The terminal positioning unit 26 may also use positioning information from autonomous navigation means such as an acceleration sensor or a geomagnetic sensor for positioning. Because the terminal device 2 moves together with the user, the position information measured by the terminal positioning unit 26 indicates the user's current position.

Next, the server 3 will be described. As shown in FIG. 1, the server 3 has a server communication unit 31, a server control unit 32, and a server storage unit 33. Each unit is connected to each other so that they can communicate with each other via a bus or a network.

Of these, the server communication unit 31 is a communication interface between the server 3 and the network 4. The server communication unit 31 transmits and receives information between the server 3 and the terminal device 2 via the network 4.

The server storage unit 33 is, for example, a fixed data storage such as a hard disk. The server storage unit 33 stores various data handled by the server control unit 32. For example, the server storage unit 33 includes a route network information database 33a including transportation network information, a map information database 33b including map information, and a vehicle dispatchable area database 33c.

Transportation network information is information that defines transportation networks such as railroads and buses, and road networks. Transportation network information includes transportation route information, timetable information, fare information, etc. Road network information is expressed by a combination of data on nodes, which are junctions on the road network representation, such as intersections, and data on links, which are road sections between the nodes.

The map information includes map data such as national and regional road maps, and map object information associated with the map data. The map object information includes shape information about the shapes of facilities displayed on the map, note information about notes displayed on the map, and symbol information about symbols displayed on the map. The map information may also include route map information about public transportation route maps.

The above traffic network information and map information may be updated at a predetermined timing.

The dispatchable area database 33c stores information on areas where dispatchable vehicles can be used (or areas where dispatchable vehicles cannot be used). Dispatchable areas include, for example, areas with narrow roads, areas with heavy traffic, prohibited areas such as near taxi stands, and areas where a U-turn is required. In the case of shared taxis, the dispatchable areas may be areas where picking up a vehicle would be a long detour or inefficient, for example areas where the fare or time would increase by more than a specified value for the ride-sharing users already in the vehicle.

Information about available (or unavailable) areas may be updated in real time based on the vehicle's current or future travel conditions.

Note that the server storage unit 33 does not necessarily have to be provided within the server 3, and part or all of the server storage unit 33 may be provided within another device that is communicatively connected to the server 3 via the network 4.

As shown in FIG. 1, the server control unit 32 has a search condition acquisition unit 32a, a route search unit 32b, and a route output control unit 32c. Each of these units may be realized by a processor in the server 3 executing a predetermined program, or may be implemented in hardware.

The search condition acquisition unit 32a acquires route search conditions from the user's terminal device 2. The route search conditions include information on the departure point, destination, and departure time (or arrival time). The departure point may be the current location of the terminal device 2 measured by the terminal positioning unit 26, or may be a specific location input (specified) by the user via the terminal input unit 24. The departure time may be the current time, or may be a specific time input (specified) by the user via the terminal input unit 24.

Information on a designated public transportation service (e.g., a public transportation service identified by searching for a service name) or a public transportation service with a fixed departure time (e.g., a public transportation service selected from a timetable) may be manually registered (input) by the user via the terminal input unit 24 as part of the route search conditions, and the search condition acquisition unit 32a may acquire the information on the designated public transportation service or the public transportation service with a fixed departure time as part of the route search conditions.

Based on the route search conditions acquired by the search condition acquisition unit 32a, the route search unit 32b searches for information on routes that satisfy the route search conditions by referring to the route network information database 33a and the map information database 33b. When information on a designated public transportation service or a public transportation service with a fixed departure time is included in the route search conditions, the route search unit 32b searches for a route that uses the designated public transportation service or the public transportation service with a fixed departure time.

The route search unit 32b may identify a designated public transportation service or a public transportation service with a fixed departure time by referring to the user's ticket purchase history stored in an external database (not shown), and search for a route that uses the designated public transportation service or the public transportation service with a fixed departure time. Specifically, for example, the route search unit 32b refers to the user's ticket purchase history and determines whether there is a public transportation service for which a ticket (reserved boarding ticket, reserved seat ticket, etc.) has been purchased. Then, if there is a public transportation service for which a ticket has been purchased, the route search unit 32b adds the use of the public transportation service for which a ticket has been purchased to the route search conditions and searches for a route.

When searching for a route that includes a transfer from on-demand mobility (e.g., a taxi) to public transportation (e.g., a train), the route search unit 32b may refer to the vehicle dispatchable area database 33c and determine whether the departure point included in the route search conditions is a vehicle dispatchable area. If it is determined that the departure point included in the route search conditions is a vehicle dispatchable area, the route search unit 32b may search for a route using the departure point as the on-demand mobility boarding position. On the other hand, if it is determined that the departure point included in the route search conditions is an area where a vehicle cannot be dispatched, the route search unit 32b may identify a vehicle dispatchable area near the departure point and search for a route using the vehicle dispatchable area as the on-demand mobility boarding position (i.e., a travel route from the departure point to the on-demand mobility boarding position and a travel route from the on-demand mobility boarding position to the destination).

The route output control unit 32c transmits an output control signal to the terminal device 2 to output the route searched by the route search unit 32, and outputs the route searched via the terminal output unit 25. After the route search by the route search unit 32, the route output control unit 32c may output one route of the search results directly via the terminal output unit 25 as shown in FIG. 4, or may output a list of multiple route candidates of the search results via the terminal output unit 25, and output one route selected from the list via the terminal output unit 25 as shown in FIG. 4.

As shown in FIG. 4, when the route output control unit 32c outputs a route using on-demand mobility (a taxi in the illustrated example) as a route searched by the route search unit 32, the route output control unit 32c may output a vehicle dispatch request button 42 for requesting dispatch of the on-demand mobility. In the example shown in FIG. 4, the vehicle dispatch request button 42 is a button that, when pressed by a user via the terminal input unit 24, transitions the screen to a vehicle dispatch flow for requesting dispatch of a vehicle to the on-demand mobility side. In the vehicle dispatch flow at the screen transition destination, the on-demand mobility boarding position (starting point 45 in the example shown in FIG. 4) may be automatically set as the dispatch destination. In the vehicle dispatch flow at the screen transition destination, the on-demand mobility boarding and disembarking positions and the route may be displayed on a map. When making a vehicle dispatch request, the fare for the on-demand mobility may be paid in advance (i.e., on-demand mobility can be used at a pre-determined fare).

As shown in FIG. 4, when displaying a route that includes a transfer from on-demand mobility (a taxi in the illustrated example) to public transportation (a Shinkansen in the illustrated example), the route output control unit 32c may display pre-dispatch information 41 including at least a dispatch request button 42 in front of the display of the departure point 45. In the example shown in FIG. 4, the display is vertically scrolled, and the pre-dispatch information 41 including the dispatch request button 42 is displayed in front (above) of the display of the departure point 45, "3-8 Minamiaoyama, Minato-ku, Tokyo."

As shown in FIG. 4, when outputting a route using public transportation (the Shinkansen in the illustrated example), the route output control unit 32c may refer to the user's ticket purchase history stored in an external database (not shown), determine whether or not a ticket for that public transportation (such as a reserved flight ticket or a reserved seat ticket) has been purchased, and output information 46 indicating whether or not the user has made a reservation for that public transportation (whether or not a ticket has been purchased). In the example shown in FIG. 4, an icon indicating that a reservation has been made is displayed as information 46 indicating whether or not the user has made a reservation, but text may be used instead of an icon. Also, it is sufficient that the processing is different depending on whether or not a reservation has been made, and if there is no reservation, an icon or text indicating that no reservation has been made may be displayed.

As shown in FIG. 5, when outputting a route including a transfer from on-demand mobility (a taxi in the illustrated example) to public transportation (a Shinkansen in the illustrated example), and the on-demand mobility boarding position 48 is different from the departure point 45 (for example, when the departure point 45 is in an area where vehicles cannot be dispatched), the route output control unit 32c may output a route including a travel route from the departure point 45 to the on-demand mobility boarding position 48 as a route of the search result. In the example shown in FIG. 5, a route for traveling on foot from the departure point 45, "3-8 Minamiaoyama, Minato-ku, Tokyo" to the on-demand mobility boarding position 48, "X Police Box Front", is displayed. The route output control unit 32c may display a mark 49 (button) for providing route guidance for the travel route together with the travel route from the departure point 45 to the on-demand mobility boarding position 48 (the route for traveling on foot in the illustrated example).

When outputting a route that includes a transfer from on-demand mobility to a designated public transportation service or to public transportation with a fixed departure time as a route searched for by the route search unit 32, or when outputting a route that includes a transfer from public transportation to on-demand mobility, the route output control unit 32c obtains a predicted dispatch time for on-demand mobility to the on-demand mobility boarding position.

As a first example of a method for acquiring the estimated dispatch time, the route output control unit 32c may refer to the route network information database 33a and the map information database 33b to search for a route from the current location of the vehicle to the on-demand mobility boarding location, and calculate the estimated dispatch time based on the route information of the search result. In this case, the route output control unit 32c may calculate the estimated dispatch time taking into account traffic congestion information on the route of the search result.

As a second example of a method for acquiring the predicted dispatch time, the route output control unit 32c may use spatial and temporal statistics to predict an approximate predicted dispatch time from the actual operation record in the target area and time (or time zone). Specifically, for example, the route output control unit 32c may use a statistical model (spatio-temporal statistical model) constructed based on the actual data of past dispatch times in each area and time (or time zone) to predict, as the predicted dispatch time, the average pick-up time in on-demand mobility dispatch for the user for the date and time information (weekday, holiday, day of the week, time zone, etc.) at the time of route search in the space in which the departure point input as the route search condition is located (administrative district such as a city, ward, town, village, etc. in which the departure point is located, within an area with a radius of a specified distance from the departure point, etc.).

As a third example of a method for acquiring the predicted dispatch time, the route output control unit 32c may inquire of the on-demand mobility side (the vehicle's communication device or the operator's server) about the predicted dispatch time to the on-demand mobility boarding position, and receive the predicted dispatch time to the on-demand mobility boarding position from the on-demand mobility side as a response to the inquiry.

After obtaining the predicted dispatch time to the on-demand mobility boarding position, the route output control unit 32c performs control related to the dispatch request taking into account the predicted dispatch time.

As a control related to the dispatch request, the route output control unit 32c may calculate the dispatch request execution time and/or the dispatch request execution deadline in consideration of the predicted dispatch time to the on-demand mobility boarding position. The calculated dispatch request execution time and/or the dispatch request execution deadline may be stored in the server storage unit 33. Here, the "dispatch request execution time" is the time when information for executing the dispatch request is transmitted from the server 3 to the on-demand mobility side (the vehicle's communication device or the operator's server), as described below. In addition, the "dispatch request execution deadline" is the deadline by which the dispatch request must be executed in order to board a designated public transportation service or a public transportation service with a fixed departure time. The dispatch request execution time may be earlier than the dispatch request execution deadline, or may be the same as the dispatch request execution deadline.

Specifically, for example, as shown in FIG. 4, in a route in which an on-demand mobility (here, a taxi) is taken at an on-demand mobility boarding position (here, the starting point 45) at 11:10 to a public transportation station, and then a reserved public transportation 47 (here, a Shinkansen) is transferred there, if the estimated dispatch time to the on-demand mobility boarding position (here, the starting point 45) is "6 minutes", in order to take an on-demand mobility (here, a taxi) at the on-demand mobility boarding position (here, the starting point 45) at 11:10, it is necessary to execute a dispatch request at least 6 minutes before 11:10. Therefore, the route output control unit 32 calculates "11:04" by subtracting 6 minutes from 11:10 as the deadline for executing the dispatch request. Alternatively, although not shown, the route output control unit 32 may calculate "11:02" by subtracting 6 minutes from 11:10 and further subtracting a first reserve time (for example, 2 minutes) as a buffer, as the deadline for executing the dispatch request. In addition, the route output control unit 32 may subtract 6 minutes from 11:10 and then subtract a second reserve time (for example, 4 minutes) as a buffer to calculate "11:00" as the dispatch request execution time.

Here, the first reserve time and the second reserve time may be determined according to whether or not the user has a reservation for a designated public transportation service or a public transportation service with a fixed departure time, the road conditions of the on-demand mobility, whether the travel by the designated public transportation service or the public transportation service with a fixed departure time is the first mile or the last mile, and the like. For example, when there is a reservation for public transportation (when a ticket has been purchased), the reserve time may be determined to be relatively long because the impact of missing the public transportation service is large. Furthermore, when there is a reservation for public transportation and the travel by the public transportation service is the first mile, the impact of missing the public transportation service is large, so the reserve time may be determined to be even longer. Furthermore, when the road conditions of the on-demand mobility service are congested, the actual dispatch may take longer than the predicted dispatch time, so the reserve time may be determined to be relatively long.

In other words, the route output control unit 32c may adjust the deadline for executing the dispatch request and the time for executing the dispatch request depending on whether the user has made a reservation for a designated public transportation service or public transportation service with a fixed departure time, the road conditions for on-demand mobility, and whether the travel on a designated public transportation service or public transportation service with a fixed departure time is the first mile or the last mile.

After calculating the vehicle dispatch request execution deadline, the route output control unit 32 may transmit an output control signal to the terminal device 2 to output information 44 for notifying the vehicle dispatch request execution deadline, as shown in FIG. 4, and output information 44 for notifying the vehicle dispatch request execution deadline via the terminal output unit 25. For example, if the vehicle dispatch request execution deadline is "11:04", the route output control unit 32 may display the vehicle dispatch request execution deadline "11:04" alone as information 44 for notifying the vehicle dispatch request execution deadline, or may display a message such as "*Please dispatch by 11:04 to board the designated flight" as shown in FIG. 4. As shown in FIG. 6, the route output control unit 32 calculates the difference ("10 minutes") between the current time ("10:54") and the deadline for executing the dispatch request ("11:04"), and may display "10 minutes", which is the remaining time until the deadline for executing the dispatch request, as information 44 for notifying the deadline for executing the dispatch request, by itself, or may display a message such as "※Dispatch must be executed within 10 minutes to board the designated service". The route output control unit 32 may blink the entire message or the time portion to indicate that the remaining time until the deadline for executing the dispatch request is a value that changes every moment. By outputting the information 44 for notifying the deadline for executing the dispatch request, the user can appropriately determine the time by which the dispatch request needs to be executed in order to board a designated service of public transportation or a public transportation with a fixed departure time (i.e., the deadline for executing the dispatch request), and thus can make a dispatch request at an appropriate timing.

In addition, after calculating the dispatch request execution time, if the user performs an operation to execute the dispatch request before the dispatch request execution time, the route output control unit 32c may temporarily suspend the execution of the dispatch request until the dispatch request execution time, and execute the dispatch request when the dispatch request execution time arrives. Specifically, for example, when the dispatch request execution time is "11:00", referring to FIG. 4, when the current time 40 is "8:00", when a signal is received indicating that the user has performed an operation to execute the dispatch request (for example, an operation via the dispatch flow by pressing the dispatch request button 42), the route output control unit 32c temporarily suspends the transmission of information to execute the dispatch request to the on-demand mobility side (the vehicle's communication device or the operator's server) until "11:00", and transmits information to execute the dispatch request to the on-demand mobility side at "11:00". This makes it possible to prevent a situation in which the timing of the dispatch request is too early, resulting in a long waiting time after arriving at a public transportation station.

Although not shown in the figure, the route output control unit 32c may notify the user via the terminal output unit 25 by displaying a pop-up or by push notification along with a message such as "Vehicle dispatch has not been executed. There is a possibility that you will not make it to your designated flight" when the time to execute the vehicle dispatch request arrives (for example, one minute before the time to execute the vehicle dispatch request) or when the time to execute the vehicle dispatch request has passed (for example, 30 seconds after the time to execute the vehicle dispatch request).

When the route output control unit 32c receives a signal indicating that the user has performed an operation to execute the dispatch request between the dispatch request execution time (e.g., "11:00") and the dispatch request execution deadline (e.g., "11:04"), the route output control unit 32c may immediately transmit information to execute the dispatch request to the on-demand mobility side (the vehicle's communication device or the operator's server).

After dispatching the on-demand mobility being displayed (for example, after sending information for executing a dispatch request to the on-demand mobility side and receiving a dispatch completion notification from the on-demand mobility side), the route output control unit 32c changes the display of the pre-dispatch information 41 to the display of the post-dispatch information 51, as shown in FIG. 8. In the example shown in FIG. 8, the dispatch request button 42 included in the pre-dispatch information 41 is changed to a dispatch cancellation button 52 for canceling the dispatch in the post-dispatch information 51. Although not shown, the dispatch request button 42 included in the pre-dispatch information 41 may be changed to a dispatch change button for changing the dispatch conditions in the post-dispatch information 51. In the example shown in FIG. 5, the post-dispatch information 51 includes a display of the time until pick-up 53. As shown in FIG. 5, the time until pick-up 43 may be displayed as a message such as "We will pick you up in ** minutes." The post-dispatch information 51 may include a highlight indicating that a car is being picked up. For example, the time to pick up 43 may be displayed blinking to indicate that the value is changing from moment to moment. Also, in the post-dispatch information 51, the icon 54 indicating the type of on-demand mobility may be displayed blinking to intuitively indicate that the vehicle is currently on its way to be picked up.

As shown in FIG. 7, if the route output control unit 32c does not receive a signal indicating that the user has performed an operation to execute a vehicle dispatch request by the deadline for executing the vehicle dispatch request (e.g., "11:04"), the route output control unit 32c may output a warning 49 (e.g., a message saying "As time passes, it has become difficult to guarantee travel via this route") or may deactivate the displayed vehicle dispatch request button 47. The route output control unit 32c may output the warning 49 by a pop-up display or a push notification. If the route output control unit 32c does not receive a signal indicating that the user has performed an operation to execute a vehicle dispatch request by the deadline for executing the vehicle dispatch request, the entire route may be grayed out.

As one variation, after calculating the deadline for executing the dispatch request, the route output control unit 32c transmits an output control signal for outputting the dispatch timer button 60 to the terminal device 2 as shown in FIG. 9, and outputs the dispatch timer button 60 via the terminal output unit 25.

When a signal indicating that the dispatch timer button 60 has been pressed by the user via the terminal input unit 24 is received, as a first example of processing related to the dispatch timer button 60, the route output control unit 32c changes the display of the dispatch timer button 60 to a timer cancel button for canceling the dispatch timer, and temporarily suspends notification to the user until the dispatch request execution time arrives. Then, when the dispatch request execution time arrives (for example, one minute before the dispatch request execution time), the route output control unit 32c notifies the user via the terminal output unit 25 by a pop-up display or push notification that it is an appropriate time to execute the dispatch, and changes the display of the timer cancel button to the dispatch request button 42 (see FIG. 4). This allows the user to make a dispatch request at an appropriate time, even if on-demand mobility cannot be reserved. The time difference between the timing of notifying the user and the dispatch request execution time may be determined taking into account the predicted dispatch time of on-demand mobility.

As a second example of processing related to the dispatch timer button 60, when a signal indicating that the dispatch timer button 60 has been pressed by the user via the terminal input unit 24 is received, the route output control unit 32c may change the display of the dispatch timer button 60 to a timer cancel button for canceling the dispatch timer, and temporarily suspend the execution of the dispatch request until the time to execute the dispatch request arrives, and the route output control unit 32c may send information for executing the dispatch request to the on-demand mobility side when the time to execute the dispatch request arrives. This allows the user to make a dispatch request at an appropriate time, even if on-demand mobility cannot be reserved.

(First example of operation)
Next, a first example of the operation of the information processing system 1 according to the embodiment will be described with reference to Fig. 2. Fig. 2 is a flowchart showing the first example of the operation of the information processing system 1.

As shown in FIG. 2, first, when the user of the terminal device 2 inputs route search conditions via the terminal input unit 24, the route search conditions are transmitted from the terminal device 2 to the server 3, and the search condition acquisition unit 32a of the server 3 acquires the route search conditions (step S10). In this embodiment, information on a designated public transportation service (e.g., a public transportation service identified by searching for a service name) or a public transportation service with a fixed departure time (e.g., a public transportation service selected from a timetable) is manually registered (input) by the user via the terminal input unit 24 as part of the route search conditions, and the search condition acquisition unit 32a acquires the information on the designated public transportation service or the public transportation service with a fixed departure time as part of the route search conditions.

Next, the route search unit 32b searches for information on routes that use designated public transportation services or public transportation services with fixed departure times, based on the route search conditions acquired by the search condition acquisition unit 32a, by referring to the route network information database 33a and the map information database 33b (step S11).

As a variant example, even if information on a designated public transportation service or a public transportation service with a fixed departure time is not manually registered (input) by the user via the terminal input unit 24 as part of the route search conditions, the route search unit 32b may identify the designated public transportation service or the public transportation service with a fixed departure time by referring to the user's ticket purchase history stored in an external database (not shown), and search for a route that uses the designated public transportation service or the public transportation service with a fixed departure time.

Next, the route output control unit 32c transmits an output control signal to the terminal device 2 to output the route searched by the route search unit 32, and outputs the route searched via the terminal output unit 25 (step S12). When outputting a route that uses on-demand mobility as the route searched by the route search unit 32, the route output control unit 32c may output a vehicle dispatch request button 42 for requesting the dispatch of the on-demand mobility, as shown in FIG. 4.

As shown in FIG. 4, when outputting a route that includes a transfer from on-demand mobility to a designated public transportation service or a public transportation service with a fixed departure time, the route output control unit 32c refers to the user's ticket purchase history stored in an external database (not shown), determines whether or not a ticket for that public transportation service (such as a reserved-flight ticket or a reserved-seat ticket) has been purchased, and outputs information 46 indicating whether or not the user has made a reservation for that public transportation service (whether or not a ticket has been purchased) (step S13).

Next, the route output control unit 32c acquires the on-demand mobility dispatch predicted time to the on-demand mobility boarding position (step S14). In step S14, the route output control unit 32c may refer to the route network information database 33a and the map information database 33b to search for a route from the current position of the vehicle to the on-demand mobility boarding position, and calculate the dispatch predicted time based on the route information of the search result. In this case, the route output control unit 32c may calculate the dispatch predicted time taking into consideration traffic congestion information on the route of the search result. Alternatively, the route output control unit 32c may predict an approximate dispatch predicted time using spatial and temporal statistics from the usual operation record in the target area and time (or time zone). Alternatively, the route output control unit 32c may inquire of the on-demand mobility side (the vehicle's communication device or the operator's server) about the dispatch predicted time to the on-demand mobility boarding position, and receive the dispatch predicted time to the on-demand mobility boarding position from the on-demand mobility side as a response to the inquiry.

After obtaining the predicted dispatch time to the on-demand mobility boarding position, the route output control unit 32c performs control related to the dispatch request taking into account the predicted dispatch time.

In this embodiment, the route output control unit 32c calculates the dispatch request execution time and/or the dispatch request execution deadline in consideration of the predicted dispatch time to the on-demand mobility boarding position as a control related to the dispatch request (step S15). The calculated dispatch request execution time and/or the dispatch request execution deadline are stored in the server storage unit 33.

Next, as shown in FIG. 4, the route output control unit 32c transmits an output control signal for outputting information 44 for notifying the dispatch request execution deadline to the terminal device 2, and outputs information 44 for notifying the dispatch request execution deadline via the terminal output unit 25 (step S16). In the example shown in FIG. 4, the dispatch request execution deadline is "11:04", and the route output control unit 32 displays a message "※Please execute dispatch by 11:04 to board the designated flight" as information 44 for notifying the dispatch request execution deadline. As a variation, as shown in FIG. 6, the route output control unit 32 may calculate the difference ("10 minutes") between the current time ("10:54") and the dispatch request execution deadline ("11:04"), and display a message such as "※Please execute dispatch within 10 minutes to board the designated flight" as information 44 for notifying the dispatch request execution deadline. The route output control unit 32 may blink the entire message or the time portion to indicate that the remaining time until the deadline for executing the dispatch request is a value that changes every moment.

Next, the route output control unit 32c determines whether a signal indicating that the user has performed an operation to execute a vehicle dispatch request has been received before the time to execute the vehicle dispatch request (step S17).

If the user performs an operation to execute the dispatch request before the dispatch request execution time (step S17: YES), the route output control unit 32c temporarily suspends the execution of the dispatch request until the dispatch request execution time, and executes the dispatch request when the dispatch request execution time arrives (step S18). Specifically, for example, when the dispatch request execution time is "11:00", referring to FIG. 4, when the current time 40 is "8:00", when a signal is received indicating that the user performed an operation to execute the dispatch request (for example, an operation via the dispatch flow by pressing the dispatch request button 42), the route output control unit 32c temporarily suspends the transmission of information to execute the dispatch request to the on-demand mobility side (the vehicle's communication device or the operator's server) until "11:00", and transmits information to execute the dispatch request to the on-demand mobility side at "11:00". This prevents the timing of the dispatch request from being too early, resulting in a long waiting time after arriving at a public transportation station.

If the user does not perform an operation to execute the vehicle dispatch request before the vehicle dispatch request execution time arrives (step S17: NO), the route output control unit 32c determines whether a signal indicating that the user performed an operation to execute the vehicle dispatch request was received between the vehicle dispatch request execution time and the vehicle dispatch request execution deadline (step S19).

If the user performs an operation to execute a vehicle dispatch request between the dispatch request execution time and the deadline for executing the vehicle dispatch request (step S19: YES), the route output control unit 32c immediately transmits information to execute the vehicle dispatch request to the on-demand mobility side (the vehicle's communication device or the operator's server) (step S20).

After dispatching the on-demand mobility (i.e., after step S18 or step S20 and after receiving a dispatch completion notification from the on-demand mobility side), the route output control unit 32c transmits an output control signal to the terminal device 2 to output the time until pick-up 53, as shown in FIG. 8, and outputs the time until pick-up 53 via the terminal output unit 25 (step S21). The display of the time until pick-up 43 may blink to indicate that it is a value that changes every moment. In step S21, the route output control unit 32c may change the display of the dispatch request button 42 to a dispatch cancellation button 52 (or a dispatch change button).

If the user does not perform an operation to execute a vehicle dispatch request between the dispatch request execution time and the deadline for executing the vehicle dispatch request (step S19: NO), the route output control unit 32c outputs a warning 49 (such as a message saying "Due to the passage of time, it has become difficult to guarantee travel via this route") as shown in FIG. 7, or deactivates the vehicle dispatch request button 47 (step S22). The route output control unit 32c may output the warning 49 by a pop-up display or a push notification. In step S22, the route output control unit 32c may gray out the entire route.

According to this embodiment as described above, when a route is searched for and output that includes a transfer from on-demand mobility to a designated public transportation service or public transportation with a fixed departure time, the route output control unit 32c obtains the predicted dispatch time of on-demand mobility to the boarding position of the on-demand mobility and performs control related to the dispatch request taking into account the predicted dispatch time, so that a dispatch request can be made at an appropriate time even if the on-demand mobility cannot be reserved.

More specifically, as a control related to vehicle dispatch requests, the route output control unit 32c calculates the deadline for executing the vehicle dispatch request taking into account the predicted dispatch time of on-demand mobility, and then outputs information 44 for notifying the user of the deadline for executing the vehicle dispatch request, so that the user can appropriately determine the time by which the vehicle dispatch request needs to be executed in order to board a designated public transportation service or public transportation with a fixed departure time (i.e., the deadline for executing the vehicle dispatch request), thereby making it possible to make a vehicle dispatch request at the appropriate time.

In addition, in this embodiment, the route output control unit 32c, as a control related to a dispatch request, calculates the dispatch request execution time taking into account the on-demand mobility's predicted dispatch time, and if the user performs an operation to execute the dispatch request before the dispatch request execution time, the execution of the dispatch request is temporarily suspended until the dispatch request execution time arrives, and when the dispatch request execution time arrives, information for executing the dispatch request is transmitted to the on-demand mobility side. This makes it possible to make a dispatch request at an appropriate time, and the user does not need to keep worrying about the timing of the dispatch request after getting on public transportation.

(Second example of operation)
Next, a second example of the operation of the information processing system 1 according to the embodiment will be described with reference to Fig. 3A. Fig. 3A is a flowchart showing the second example of the operation of the information processing system 1.

As shown in FIG. 3A, first, when a user of the terminal device 2 inputs route search conditions via the terminal input unit 24, the route search conditions are transmitted from the terminal device 2 to the server 3, and the search condition acquisition unit 32a of the server 3 acquires the route search conditions (step S30).

Next, the route search unit 32b searches for information on a route that satisfies the route search conditions acquired by the search condition acquisition unit 32a by referring to the route network information database 33a and the map information database 33b (step S31).

Next, the route output control unit 32c transmits an output control signal to the terminal device 2 to output the route searched by the route search unit 32, and outputs the route searched via the terminal output unit 25 (step S32).

As shown in FIG. 9, when outputting a route that includes a transfer from public transportation to on-demand mobility, the route output control unit 32c refers to the user's ticket purchase history stored in an external database (not shown), determines whether or not a ticket for that public transportation (such as a reserved flight ticket or a reserved seat ticket) has been purchased, and outputs information 46 indicating whether or not the user has made a reservation for that public transportation (whether or not a ticket has been purchased) (step S33).

Next, the route output control unit 32c acquires the predicted dispatch time of the on-demand mobility to the on-demand mobility boarding position (step S34). The method of acquiring the predicted dispatch time is the same as step S14 in the first example of the operation described above, and therefore the explanation is omitted.

After obtaining the predicted dispatch time to the on-demand mobility boarding position, the route output control unit 32c performs control related to the dispatch request taking into account the predicted dispatch time.

In this embodiment, the route output control unit 32c calculates the dispatch request execution time in consideration of the predicted dispatch time to the on-demand mobility boarding position as a control related to the dispatch request (step S35). The calculated dispatch request execution time is stored in the server storage unit 33.

Next, as shown in FIG. 9, the route output control unit 32 transmits an output control signal to the terminal device 2 to output the dispatch timer button 60, and outputs the dispatch timer button 60 via the terminal output unit 25 (step S36).

When the route output control unit 32c receives a signal indicating that the dispatch timer button 60 has been pressed by the user via the terminal input unit 24, it changes the display of the dispatch timer button 60 to a timer cancel button display, temporarily suspends the execution of the dispatch request until the dispatch request execution time arrives, and transmits information to the on-demand mobility side to execute the dispatch request when the dispatch request execution time arrives (step S37). This enables the user to make a dispatch request at an appropriate time.

After the on-demand mobility has been dispatched (i.e., after step S37 and after receiving a dispatch completion notification from the on-demand mobility side), the route output control unit 32c transmits an output control signal to the terminal device 2 to output the time until pick-up, and outputs the time until pick-up via the terminal output unit 25 (step S38). The display of the time until pick-up may flash to indicate that it is a value that changes every moment.

According to the present embodiment described above, when a route including a transfer from public transportation to on-demand mobility is searched for and output, the route output control unit 32c calculates the dispatch request execution time taking into account the on-demand mobility's predicted dispatch time as a control related to the dispatch request, and then, if the user performs an operation to execute the dispatch request (i.e., pressing the dispatch timer button 60) before the dispatch request execution time, the dispatch request is temporarily put on hold until the dispatch request execution time arrives, and when the dispatch request execution time arrives, information for executing the dispatch request is transmitted to the on-demand mobility side. This allows the user to make a dispatch request at an appropriate time, and the user does not need to worry about the timing of the dispatch request after getting on public transportation.

(Third example of operation)
Next, a third example of the operation of the information processing system 1 according to the embodiment will be described with reference to Fig. 3B. Fig. 3B is a flowchart showing the third example of the operation of the information processing system 1.

As shown in FIG. 3B, in this embodiment, the process from obtaining route search conditions (step S30) to outputting the dispatch timer button (step S36) is the same as the second example of the operation shown in FIG. 3A, and therefore the description will be omitted.

In this embodiment, as shown in FIG. 3B, after outputting the dispatch timer button 60 (after step S36), if the route output control unit 32c receives a signal indicating that the dispatch timer button 60 has been pressed by the user via the terminal input unit 24, the route output control unit 32c changes the display of the dispatch timer button 60 to a timer cancel button and temporarily suspends notification to the user until the dispatch request execution time. Then, when the dispatch request execution time arrives (for example, one minute before the dispatch request execution time), the route output control unit 32c notifies the user via the terminal output unit 25 by a pop-up display or push notification that it is the appropriate time to dispatch a vehicle, and changes the display of the timer cancel button to the dispatch request button 42 (see FIG. 4) (step S47). This enables the user to make a dispatch request at the appropriate time. When the notified user performs an operation to execute the dispatch request between the dispatch request execution time and the dispatch request execution deadline (for example, an operation via the dispatch flow by pressing the dispatch request button 42), the route output control unit 32c immediately transmits information to execute the dispatch request to the on-demand mobility side (the vehicle's communication device or the operator's server) (step S48).

After the on-demand mobility has been dispatched (i.e., after step S48 and after receiving a dispatch completion notification from the on-demand mobility side), the route output control unit 32c transmits an output control signal to the terminal device 2 to output the time until pick-up, and outputs the time until pick-up via the terminal output unit 25 (step S38). The display of the time until pick-up may flash to indicate that it is a value that changes every moment.

According to this embodiment as described above, when a route that includes a transfer from public transportation to on-demand mobility is searched for and output, the route output control unit 32c, as a control related to the dispatch request, calculates the dispatch request execution time taking into account the predicted dispatch time of on-demand mobility, and then notifies the user when the dispatch request execution time arrives that it is an appropriate time to dispatch the vehicle, so that the timing to dispatch the vehicle can be appropriately determined, and thus it becomes possible to make a dispatch request at an appropriate time.

At least a part of the information processing system 1 described in the above embodiment may be configured with hardware or software. When configured with hardware, a program that realizes at least a part of the functions of the information processing system 1 may be stored on a recording medium such as a flexible disk or CD-ROM, and may be read and executed by a computer. The recording medium is not limited to removable recording media such as magnetic disks and optical disks, but may also be fixed recording media such as a hard disk device or memory.

In addition, a program that realizes at least a part of the functions of the information processing system 1 may be distributed via a communication line (including wireless communication) such as the Internet. Furthermore, the program may be encrypted, modulated, or compressed and distributed via a wired line or wireless line such as the Internet, or stored on a recording medium.

Furthermore, the information processing system 1 may be operated by one or more information processing devices. When multiple information processing devices are used, one of the information processing devices may be a computer, and the computer may execute a predetermined program to realize the function as at least one of the means of the information processing system 1.

In addition, in the method invention, all processes (steps) may be realized by automatic control using a computer. Alternatively, each process may be performed by a computer, while progress control between processes may be performed manually. Furthermore, at least some of the processes may be performed manually.

Based on the above description, a person skilled in the art may be able to conceive additional effects and various modifications of the present invention, but the aspects of the present invention are not limited to the individual embodiments described above. Various additions, modifications, and partial deletions are possible within the scope of the conceptual idea and intent of the present invention derived from the contents defined in the claims and their equivalents.

REFERENCE SIGNS LIST 1 Information processing system 2 Terminal device 21 Terminal communication unit 22 Terminal control unit 23 Terminal storage unit 24 Terminal input unit 25 Terminal output unit 26 Terminal positioning unit 3 Server 31 Server communication unit 32 Server control unit 32a Search condition acquisition unit 32b Route search unit 32c Route output control unit 33 Server storage unit 33a Route network information database 33b Map information database 33c Vehicle dispatchable area database 4 Network

Claims (13)

A search condition acquisition means for acquiring route search conditions;
a route search means for searching for a route based on the route search conditions;
a route output control means for outputting the route as a result of the search;
The route output control means, when outputting a route that includes a transfer from on-demand mobility to a designated public transportation service or public transportation with a fixed departure time, or when outputting a route that includes a transfer from public transportation to on-demand mobility, obtains a predicted dispatch time for on-demand mobility to the boarding position of the on-demand mobility, calculates a deadline for executing the dispatch request taking into account the predicted dispatch time , and outputs information for notifying of the deadline for executing the dispatch request. A search condition acquisition means for acquiring route search conditions;
a route search means for searching for a route based on the route search conditions;
a route output control means for outputting the route as a result of the search;
The route output control means, when outputting a route that includes a transfer from on-demand mobility to a designated public transportation service or public transportation with a fixed departure time, or when outputting a route that includes a transfer from public transportation to on-demand mobility, obtains a predicted dispatch time for on-demand mobility to the boarding position of the on-demand mobility, calculates a dispatch request execution time taking into account the predicted dispatch time , and, if a user performs an operation to execute the dispatch request before the dispatch request execution time, temporarily suspends the execution of the dispatch request until the dispatch request execution time arrives, and executes the dispatch request when the dispatch request execution time arrives. This is an information processing system. The information processing system according to claim 1 or 2 , wherein the route of the search result includes a travel route from a departure point to an on-demand mobility boarding position. The information processing system according to any one of claims 1 to 3 , wherein the route output control means outputs the pick-up time until the on-demand mobility included in the route being output arrives at the on-demand mobility boarding position after dispatching the on-demand mobility. The information on the designated public transportation service or the public transportation service with a fixed departure time is manually registered by a user as part of the route search conditions, and the search condition acquisition means acquires the information on the designated public transportation service or the public transportation service with a fixed departure time as part of the route search conditions, or
The information processing system according to any one of claims 1 to 4 , wherein the route search means identifies the public transportation with a designated service or a public transportation with a fixed departure time by referring to a ticket purchase history of the user. The information processing system according to claim 1, wherein the route output control means outputs a warning or deactivates a displayed vehicle dispatch request execution button if the user does not perform an operation to execute the vehicle dispatch request by the vehicle dispatch request execution deadline . The information processing system according to claim 1, wherein the route output control means adjusts the deadline for executing the dispatch request depending on whether or not the user has made a reservation for the designated public transportation service or for public transportation service with a fixed departure time, the road conditions of on-demand mobility, and whether the travel on the designated public transportation service or for public transportation service with a fixed departure time is the first mile or the last mile . The information processing system according to any one of claims 1 to 7, wherein when outputting a route that includes a transfer from on-demand mobility to a public transportation service with a designated flight or a public transportation service with a fixed departure time, the route output control means outputs whether or not the user has a reservation for the public transportation service with a designated flight or the public transportation service with a fixed departure time. 3. The information processing system according to claim 2 , wherein the route output control means notifies the user when a vehicle dispatch request execution time arrives or when the vehicle dispatch request execution time has passed. Computer,
A search condition acquisition means for acquiring route search conditions;
a route search means for searching for a route based on the route search conditions; and
An information processing program that functions as a route output control means that outputs a route resulting from a search, and when outputting a route that includes a transfer from on-demand mobility to a designated public transportation service or public transportation with a fixed departure time, or when outputting a route that includes a transfer from public transportation to on-demand mobility, obtains a predicted dispatch time for on-demand mobility to the boarding position of the on-demand mobility, calculates a deadline for executing a dispatch request taking into account the predicted dispatch time, and outputs information for notifying of the deadline for executing the dispatch request. Computer,
A search condition acquisition means for acquiring route search conditions;
a route search means for searching for a route based on the route search conditions; and
An information processing program that functions as a route output control means that outputs a route resulting from a search, and when outputting a route that includes a transfer from on-demand mobility to a designated public transportation service or public transportation with a fixed departure time, or when outputting a route that includes a transfer from public transportation to on-demand mobility, obtains a predicted dispatch time for on-demand mobility to the boarding position of the on-demand mobility, calculates a dispatch request execution time taking into account the predicted dispatch time, and, if a user performs an operation to execute the dispatch request before the dispatch request execution time, temporarily suspends the execution of the dispatch request until the dispatch request execution time arrives, and executes the dispatch request when the dispatch request execution time arrives. 1. A computer-implemented information processing method, comprising:
Obtaining route search conditions;
searching for a route based on the route search conditions;
An information processing method including a step of outputting a route resulting from the search, wherein, when outputting a route that includes a transfer from on-demand mobility to a designated public transportation service or public transportation with a fixed departure time, or when outputting a route that includes a transfer from public transportation to on-demand mobility, a predicted dispatch time for on-demand mobility to the boarding position of the on-demand mobility, calculating a deadline for executing a dispatch request taking into account the predicted dispatch time, and outputting information for notifying of the deadline for executing the dispatch request. 1. A computer-implemented information processing method, comprising:
Obtaining route search conditions;
searching for a route based on the route search conditions;
An information processing method including a step of outputting a route resulting from the search, wherein, when outputting a route that includes a transfer from on-demand mobility to a designated public transportation service or public transportation with a fixed departure time, or when outputting a route that includes a transfer from public transportation to on-demand mobility, a predicted dispatch time for on-demand mobility to the boarding position of the on-demand mobility is obtained, a dispatch request execution time is calculated taking into account the predicted dispatch time, and, if a user performs an operation to execute the dispatch request before the dispatch request execution time, the execution of the dispatch request is temporarily suspended until the dispatch request execution time arrives, and the dispatch request is executed when the dispatch request execution time arrives.