JP7848872B2 - Vehicle dispatch traffic system, shared terminal control device, and shared terminal control method - Google Patents

Description

The present invention relates to a vehicle dispatching system, a shared terminal control device, and a method for controlling a shared terminal.

Conventional ride-sharing support systems that shorten the waiting time for transfers to shared vehicles have been known (for example, Patent Document 1). The ride-sharing support system described in Patent Document 1 acquires user travel information relating to the public transportation services used by the user, the planned disembarkation stations, and the user's destination. It generates user group information indicating user groups for each destination, targeting users who are estimated to arrive at the planned disembarkation station within a predetermined time period including the time of arrival at the disembarkation station. The ride-sharing support system then assigns available shared vehicles to the user groups indicated by the user group information and transmits the user group information to the provider of the shared vehicle. In such a ride-sharing support system, the input screen for user travel information displayed on the user's mobile terminal displays a list of routes used, a list of planned disembarkation stations, a list of services used, and a destination input box. The user inputs user travel information by touching the lists and boxes on the screen, and the mobile terminal transmits the input information to the ride-sharing support system.

Japanese Patent Publication No. 2020-135642

However, the above-mentioned ride-sharing support system has a problem in that users have to perform many input operations, such as looking at the input screen of their mobile device and entering multiple pieces of information in order to use a ride-sharing vehicle, making the operation cumbersome.

The problem that this invention aims to solve is to provide a vehicle dispatching system, a shared terminal control device, and a shared terminal control method that can prevent users from having to perform complicated information input operations.

The present invention solves the above problem by extracting candidate locations for at least one of the drop-off locations where the user alights from a dispatched vehicle and the destination to which the user is heading using the dispatched vehicle, based on the user's usage history of the transportation system, or by acquiring information on such candidate locations, and by displaying the information on the candidate locations on a display device of a shared terminal or on the user terminal when a user's approach is detected.

According to the present invention, user convenience can be improved.

Figure 1 is a conceptual diagram illustrating the vehicle dispatch system in this embodiment. Figure 2 is a block diagram showing an example of the configuration of a vehicle dispatching system. Figure 3 is a flowchart showing the flow of user actions, shared terminals, and server control processes. Figure 4 shows an example of the display screen of a shared terminal's display device. Figure 5 is a flowchart of the subflow included in the control process of step S7 in Figure 3. Figure 6 is a classification table used to categorize the usage history of the sub-transportation system.

An embodiment of the vehicle dispatch transportation system according to the present invention will be described based on the drawings. Figure 1 is a conceptual diagram for illustrating the vehicle dispatch transportation system according to this embodiment, and Figure 2 is a block diagram showing an example of the configuration of the vehicle dispatch transportation system. Referring to Figure 1, the vehicle dispatch transportation system according to this embodiment is a system for assigning vehicles for users to travel from their boarding location to their destination by transferring between vehicles. The transportation system has vehicle dispatch vehicles (hereinafter also referred to as "patrol vehicles") that travel in a patrol area 100 and vehicle dispatch vehicles that travel in a non-patrol area 200. Patrol vehicles are vehicles that travel in circles along a designated route within the patrol area 100. The patrol area 100 includes a patrol route and boarding/alighting points set up at predetermined intervals along the patrol route. Patrol vehicles travel along the patrol route and stop at boarding/alighting points on the patrol route. Users of the transportation system board and alight from patrol vehicles at boarding/alighting points on the patrol route. The pick-up and drop-off points on the patrol route can be designated as the user's departure point and/or destination, and can also be set as transfer points for the user. Dispatched vehicles traveling in the non-patrol area 200 travel along a route connecting the pick-up or drop-off point designated by the user with the transfer points on the patrol route.

For example, as shown in Figure 1, if a user designates a pick-up/drop-off point A within the patrol area 100 as their departure point and a pick-up/drop-off point C (e.g., their home) within area 200 as their destination, the transportation system determines a travel plan for moving from pick-up/drop-off point A to pick-up/drop-off point C. The travel plan includes information about the dispatched vehicle's operation, such as the vehicle the user should ride, the vehicle's route, and the vehicle's arrival and departure times at the pick-up/drop-off points. In the example in Figure 1, the travel plan would be to travel from pick-up point A to transfer point B in patrol vehicle X on the patrol route, then transfer from patrol vehicle X to dispatched vehicle Y at pick-up/drop-off point B, and finally travel to destination C within the non-patrol area 200 in dispatched vehicle Y. Note that the user's departure point and/or destination do not necessarily have to be within the patrol area 100; they may be in the non-patrol area 200, and both the user's departure point and destination may be within either the patrol area 100 or the non-patrol area 200. Furthermore, the means of transportation from the departure point to the transfer point, or from the transfer point to the destination, do not need to be a pre-booked vehicle; they may be public transportation such as buses, trains, airplanes, or taxis, and multiple modes of transportation may be combined.

The dispatched vehicles do not necessarily have to make rounds, and the driving area of the dispatched vehicles does not have to be a round-trip driving area. For example, in the example in Figure 1, vehicle X may take the shortest route on the map from boarding point A to transfer point B as the first driving route, and vehicle Y may take the shortest route on the map from transfer point B to destination C as the second driving route. Area 100 is the driving area of vehicle X. In the example in Figure 1, since the destination (the user's drop-off point) is specified outside area 100, the user transfers from dispatched vehicles X to Y at the transfer point and moves from the first driving route to the first driving route. In the following explanation, the driving area 100 of the dispatched vehicles will be described as the dispatched vehicle's round-trip driving area, but driving area 100 does not have to be a round-trip driving area. Area 200 may also be the round-trip driving area.

When a user uses the ride-hailing service provided by the transportation system, they travel to a boarding/alighting point where a shared terminal is installed, using either a dispatched vehicle or another means of transportation. When a user approaches the shared terminal, the terminal detects the user and transmits the detected user's information to the server. The server identifies the user based on the user's information and extracts candidate destinations for the dispatched vehicle and/or the user's destination based on the identified user's usage history. The shared terminal retrieves the candidate destination information from the server and displays the candidate destinations on the terminal's display screen. The user selects their desired candidate destination on the shared terminal's display screen. Once a candidate destination is selected, a dispatched vehicle heading to that destination is assigned to the user, and the user becomes ready to board the dispatched vehicle. Thus, in the transportation system according to this embodiment, a user can use a dispatched vehicle simply by checking the screen of the shared terminal's display device, which shows candidate destinations such as the destination, and performing a selection operation to select a candidate destination.

Users may also reserve a vehicle to use the ride-hailing service provided by the transportation system. Users access the server using their own terminal or a shared terminal and enter the information necessary to reserve a vehicle. Based on the entered information, the server assigns a vehicle that meets the user's preferences and completes the reservation. This allows the user to use the reserved vehicle.

Shared terminals 10 are installed at boarding and alighting points along the patrol route. Shared terminals 10 are devices (e.g., digital signage, roadside terminals) that communicate with a server and output guidance information about the traffic system by displaying images and text on a flat-panel display or projector. Shared terminals 10 do not necessarily have to be installed on the roadside. For example, shared terminals 10 may be installed in parking spaces or terminals used in facilities such as shops. Also, shared terminals 10 are not necessarily limited to outdoor use, but may be terminals used indoors. Furthermore, shared terminals 10 may be terminals that can be moved by users. In the following explanation, shared terminals 10 will be described as roadside terminals. Shared terminals 10 are installed at each boarding and alighting point along the patrol route. The guidance information for the traffic system is not limited to general guidance information for the system (information for an unspecified number of users), but is guidance information for detected users.

For example, in the example shown in Figure 1, user P boards a patrol vehicle X from boarding point A and arrives at transfer point B. When user P approaches a shared terminal 10 installed at the transfer point, the shared terminal 10 detects user P and displays information about candidate destinations for user P on its display device. Suppose user P has previously boarded a dispatched vehicle X to travel from boarding point A to transfer point B, then transferred to dispatched vehicle Y at transfer point B and traveled to destination C. Such user P activity history is stored in the server as usage history, and the server extracts destination C as a candidate destination from transfer point B for the current use from user P's usage history. The display device of the shared terminal 10 then displays candidate destinations including destination C. In other words, the information about candidate destinations including destination C becomes guidance information for user P. When user P selects destination C, the server assigns dispatched vehicle Y, which is traveling from transfer point B to destination C, to user P's reservation.

As shown in Figure 2, the transportation system according to this embodiment comprises a shared terminal 10, a server 20, a dispatched vehicle 30, and a user terminal 40. The shared terminal 10 is a terminal set up at the pick-up and/or drop-off locations of the dispatched vehicle and is a device for displaying information such as transportation system guidance information and advertising information. The server 20 manages the dispatched vehicles. The dispatched vehicle 30 is a vehicle dispatched to the user and can be an electric vehicle, a hybrid vehicle, or a vehicle powered solely by an engine. The dispatched vehicle can also be a vehicle driven by a driver, or a vehicle with autonomous driving capabilities. Vehicles with autonomous driving capabilities may be vehicles that can operate autonomously without driver intervention, such as driverless taxis, or they may be manned taxis. The user terminal 40 is a terminal owned by the user. The shared terminal 10, server 20, dispatched vehicle 30, and user terminal 40 are connected to each other via a telecommunications network such as the Internet, enabling them to send and receive information from one another.

The shared terminal 10 comprises a shared terminal control device 11, a display device 18, and a communication device 19. The shared terminal control device 11 is a device that controls the shared terminals 10 installed on the patrol routes of the dispatched vehicles 30, and is a computer equipped with a program storage ROM (Read Only Memory), a CPU (Central Processing Unit) that executes each function by executing the program, and RAM (Random Access Memory). The shared terminal control device 11 has functions to detect when a user approaches the terminal device, to acquire information about the dispatched vehicle's drop-off location or the user's candidate destination, to display guidance information on the display device 18, to accept user input operations, to accept reservation input, and to establish a link between the shared terminal and the user terminal. The shared terminal control device 11 includes a detection unit 12, an information acquisition unit 13, a display control unit 14, an operation input unit 15, a reservation acceptance unit 16, and a link establishment unit 17 as functional blocks for executing various functions. The shared terminal control device 11 is not limited to the functions of the detection unit 12; it may also have other functions, such as a function for managing reservations for dispatched vehicles, or it may have some of the functions included in the server 20.

The detection unit 12 detects a user proximity state, which is when a user approaches the shared terminal 10. The user proximity state is when the user is located within a predetermined range (for example, within a few meters) from the installation location of the shared terminal 10. The detection unit 12 detects the user, for example, by facial recognition or gaze detection using a camera installed on the shared terminal 10. The detection unit 12 may also detect the user from the user's gestures. Alternatively, the detection unit 12 may detect the user proximity state using the location information of the user terminal.

The detection unit 12 detects a user, for example, in the following flow. The detection unit 12 detects the user's face from the image captured by the active camera and determines whether the detected state was maintained for a predetermined time. For example, if the user passes in front of the camera, the detection unit 12 determines that the face could not be detected because it could not be maintained for the predetermined time. If a user is detected, the detection unit 12 acquires the user's biometric information. The user's biometric information is information used to identify the individual user, such as the user's facial expression, iris, and gait (way of walking). When a user uses the transportation system, they register their face image during initial registration, and the server 20 stores the user's registration information in the database. Registration of the user's biometric information (personal information), such as a face image, is required to use the transportation system. Note that the user's biometric information only needs to be managed by the shared terminal 10 and/or the server 20.

The detection unit 12 compares the biometric information obtained from the facial image with the biometric information managed by the server 20. If a match is found, it determines that a registered user has been identified (authentication complete). If a user is identified, the detection unit 12 sends a flag to the server 20 indicating that the user has been identified. If the detection unit 12 cannot identify a registered user from the biometric information, the shared terminal control device 11 may display a guidance screen on the display device 18 to prompt the user to complete the initial registration required to use the transportation system. The detection unit 12 may also detect a user approach state when a user is approaching the shared terminal 10 and the detection unit 12 has identified that the approaching user is a registered user who will use the transportation system (i.e., the individual user has been identified).

The process for identifying individual users by the detection unit 12 may also be performed on the server 20. If the server performs user identification (personal authentication), the detection unit 12 transmits information about the detected user (e.g., captured image) to the server 20. The server 20 stores the user's biometric information in the database 25 and identifies the individual by referring to the stored user biometric information.

The information acquisition unit 13 acquires information on candidate locations extracted based on the user's usage history of the transportation system. The extracted candidate locations are at least one of the following: the drop-off location where the user alights from the dispatched vehicle, and the destination to which the user is heading using the dispatched vehicle. In the following description, the drop-off location where the user alights from the dispatched vehicle and the destination to which the user is heading using the dispatched vehicle are collectively referred to as "candidate destinations." In the example in Figure 1, user P alights from the patrol vehicle X at transfer point B and approaches the shared terminal 10 installed at transfer point B. The detection unit 12 detects the user approaching user P and sends a flag to the server 20 indicating that the user has been identified. As a response signal to the flag, the information acquisition unit 13 acquires information on user P's candidate destinations from the server 20. In the example in Figure 1, the information on user P's candidate destinations includes at least information on destination C.

Furthermore, the information acquisition unit 13 may acquire reservation information for the dispatched vehicle 30 as guidance information for the user. The reservation information for the dispatched vehicle 30 is information related to the travel plan of the dispatched vehicle reserved by the user using the transportation system, and includes time information such as the departure time of the dispatched vehicle 30, location information such as the departure point, and information on the travel route of the dispatched vehicle 30. If the dispatched vehicle 30 requires a transfer, the travel plan for the dispatched vehicle 30 may also include information on the transfer point and the transfer vehicle 30.

The display control unit 14 controls the display device 18 of the shared terminal 10. When the detection unit 12 detects a user approaching, it causes the display device 18 to display information about the destination candidates. When the detection unit 12 detects a user approaching and the information acquisition unit 13 acquires information about the destination candidates, the display control unit 14 generates a control command to display the destination candidate information acquired by the information acquisition unit 13 on the display device 18 and outputs it to the display device 18.

The operation input unit 15 accepts input operations from the user. For example, if the display device 18 is a touch panel display, the operation input unit 15 controls the display device 18 and accepts input operations via touch operation on the display device 18. For example, if destination candidate information is displayed on the display screen of the display device 18 and the user selects a destination by touch operation, the operation input unit 15 accepts the destination selection operation. If the destination desired by the user is not included among the destination candidates displayed on the display device 18, the user may specify any destination on the screen of the display device 18. Furthermore, the user does not necessarily need to operate the touch panel of the display device 18; the user may operate the user terminal 40, and the shared terminal 10 may accept input operations via the user terminal 40.

The reservation acceptance unit 16 accepts the reservation operation entered into the operation input unit 15 if it is a reservation operation to reserve a vehicle, and displays a reservation guidance screen for reserving a vehicle on the display device 18. The reservation acceptance unit 16 works in cooperation with the reservation management unit 21 of the server 20 to proceed with the control processing for reserving a vehicle. Specifically, the reservation acceptance unit 16 obtains the information necessary for the reservation from the server 20 via the information acquisition unit 13, executes the reservation application, and displays a guidance screen for accepting the reservation operation on the display device 18. When the display device 18 is touched, the reservation acceptance unit 16 accepts the reservation for the vehicle 30 and transmits the accepted information to the server 20. Then, the reservation acceptance unit 16 works in cooperation with the reservation management unit 21 of the server 20 to process the reservation of the vehicle 30 to meet the user's wishes.

The link establishment unit 17 establishes a link between the shared terminal 10 and the user terminal 40 and outputs information to the user terminal 40 via the communication device 19. The link is a communication network connecting the shared terminal 10 and the user terminal 40, and is a short-range communication network such as Bluetooth®. For example, when the user terminal 40 enters the range where a link can be established (the range where short-range communication is possible), the link establishment unit 17 sends an email to the user terminal 40, and if the user operates the user terminal 40, receives the email, and authorizes the establishment of the link, the link establishment unit 17 establishes a link with the user terminal 40. The detection unit 12 may also use the link establishment by the link establishment unit 17 to detect the user's proximity state. That is, if the link establishment unit 17 is able to establish a link with the user terminal 40, the detection unit 12 may detect that the user is in a proximity state.

Furthermore, if the link establishment unit 17 has successfully established a link between the shared terminal 10 and the user terminal 40, it may output the guidance information acquired by the information acquisition unit 13 to the user terminal. Also, if the link establishment unit 17 has received a control command from the display control unit 14 to display the guidance information acquired by the information acquisition unit 13 on the display device of the user terminal 40, it may transmit the control command to the user terminal.

The display device 18 displays information on potential destinations, traffic system guidance information, and reservation information. The display device 18 is, for example, a flat-panel display or a projector. The communication device 19 is connected to the telecommunications network NW and transmits and receives signals with the server 20, the dispatched vehicle 30, and the user terminal 40. If the link establishment unit 17 has established a link between the shared terminal 10 and the user terminal 40, the communication device 19 can also connect to the user terminal 40 via a dedicated line.

Server 20 comprises a reservation management unit 21, a vehicle management unit 22, a usage history storage unit 23, a candidate location extraction unit 24, a database 25, and a communication device 26. Server 20 controls the shared terminal 10 and the dispatched vehicles 30 to perform tasks such as registration for use of the transportation system, information management of user information, and reservation management of dispatched vehicles. Server 20 has a program to be executed in order to manage the dispatch service using the transportation system, and performs various functions by executing this program. Server 20 has a ROM that stores the program, a CPU for executing the program, etc.

Server 20 has a reservation management unit 21, a vehicle management unit 22, a usage history storage unit 23, and a candidate location extraction unit 24 as functional blocks. The reservation management unit 21, vehicle management unit 22, usage history storage unit 23, and candidate location extraction unit 24 are functional blocks that perform some of the functions of Server 20, and Server 20 can also perform functions other than those of the functional blocks shown in Figure 2.

The reservation management unit 21 manages reservation information, including user information of users who have registered to use the transportation system, the vehicles reserved by the users, and the travel plans of the reserved vehicles. Users perform initial registration by operating the shared terminal 10 or user terminal 40 in order to use the transportation system. As part of the initial registration, users enter personal information such as their name and home address, and may also enter attribute information indicating the user's attributes, such as their gender and preferences. The reservation management unit 21 manages user information by saving the information entered during initial registration via the shared terminal 10 or user terminal 40 to the database 25.

When reserving a ride, the user operates the application software on their user terminal 40 to input the necessary information for reserving a ride, such as the desired departure location, departure time, number of passengers, destination, and arrival time. The information required for the reservation may be entered not only by operating the user terminal 40, but also by operating the shared terminal 10. The entered reservation information is sent to the server 20, and the reservation management unit 21 of the server 20 extracts a ride 30 that can meet the user's request from the available rides 30 and determines a travel plan. In the example in Figure 1, the reservation management unit 21 determines a travel plan to travel from pick-up/drop-off location A to destination C. The reservation management unit 21 may also determine the travel plan while confirming the user's requests regarding the ride 30, pick-up/drop-off locations, pick-up/drop-off times, transfer locations, etc. For example, if a user enters a tourist spot or commercial facility as their desired destination, the reservation management unit 21 extracts potential destinations that the dispatched vehicle 30 can reach, in order of proximity to the desired destination, and transmits the information of the potential destinations to the shared terminal 10 or user terminal 40. The user then operates the shared terminal 10 or user terminal 40 to select a destination from the potential destinations.

The reservation management unit 21 records the determined travel plan as reservation information for the dispatched vehicle 30, linking it with the personal information of the user who made the reservation, and records it in the database 25. The reservation management unit 21 also transmits the reservation information stored in the database 25 to the shared terminal 10 or user terminal 40 in response to a request from the shared terminal 10 or user terminal 40.

The vehicle management unit 22 manages the operation of the dispatched vehicle 30 using the dispatched vehicle 30's travel plan, its current location, and the current traffic conditions. The dispatched vehicle 30's travel plan may be determined according to a predetermined operating schedule if it is within the patrol area 100. For non-patrol areas 200, which are outside the patrol area 100, the dispatch plan corresponds to a travel plan determined by the reservation management unit 21 according to the user's wishes. The vehicle management unit 22 also updates the travel plan according to traffic conditions, etc. The vehicle management unit 22 also calculates the travel route included in the travel plan. When information on candidate destinations is displayed on the display screen of the display device 18, and the user selects a destination from the candidate destinations by touching the display device 18, the vehicle management unit 22 calculates the travel route of the dispatched vehicle traveling toward the selected destination. For example, in the example in Figure 1, this is the travel route from transfer point B to destination C, and is the travel route of dispatched vehicle Y. In this embodiment, the vehicle management unit 32 corresponds to the "calculation unit" of the present invention.

The usage history storage unit 23 stores the usage history by acquiring the user's usage history of the transportation system and storing the acquired usage history in the database 25. The usage history of the transportation system is the usage history of the dispatched vehicle 30 used by the user. The usage history of the transportation system may also include the user's activity history. The usage history includes at least one piece of information from the following: the location where the user boarded and/or alighted from the dispatched vehicle 30, the time of boarding and/or alighting from the dispatched vehicle 30, the route of the dispatched vehicle 30, the type of dispatched vehicle 30, etc. The activity history includes at least one piece of information from the following: facilities or places visited by the user using the dispatched vehicle 30, facilities visited by the user before boarding the dispatched vehicle 30, facilities visited by the user after alighting from the dispatched vehicle 30, usage history of other means of transportation used by the user other than the dispatched vehicle 30, places where the user frequently stays such as their home, etc. The usage history and activity history may also include information on other users who acted together.

For example, in Figure 1, assuming location C is the user's home, user P travels to transfer point B in a private car driven by a family member, transfers to a dispatched vehicle X at transfer point B, boards the dispatched vehicle X and travels to location A, and alights from the dispatched vehicle X at location A. Furthermore, user P dines at restaurant S on the way from location C to transfer point B, alights from the dispatched vehicle X at location A, and then arrives at hospital T, which is user P's destination. In this user behavior, user P's usage history includes information on transfer point B (boarding location) and location A (alighting location), information on boarding and alighting times for the dispatched vehicle X, etc. User P's behavioral history includes information on restaurant S and hospital T, information on the use of the private car, information on passengers, etc.

The usage history storage unit 23 acquires the user's usage history of the transportation system and the user's behavior history from the user terminal 40, the reservation information of the dispatched vehicle 30, the driving plan of the dispatched vehicle 30, and the user's input information. If the user uses the dispatched vehicle 30 in accordance with the reservation information of the dispatched vehicle 30, the usage history storage unit 23 only needs to acquire the reservation information as usage history. Alternatively, the usage history storage unit 23 may acquire the driving plan of the dispatched vehicle 30 after its journey as usage history.

The usage history storage unit 23 connects to the dispatched vehicle 30 after the user has finished using the dispatched vehicle 30 and extracts the usage history from the vehicle 30's driving history data. The usage history storage unit 23 may also extract data related to the user's activity history from the user terminal 40 when the server 20 and the user terminal 40 are connected. The user terminal 40 has applications such as GPS functionality, ticket booking for accommodations and transportation, and user schedule management. The user terminal 40 identifies data related to the user's activity history from the data used by various applications and sends it to the server 20. In this way, the user terminal 40 can obtain the user's activity history.

The candidate destination extraction unit 24 extracts potential destinations based on the user's transportation system usage history detected by the detection unit 12. The candidate destination extraction unit only needs to extract at least one of the following locations as potential destinations: the drop-off point where the user alights from the dispatched vehicle 30, and the destination to which the user is going using the dispatched vehicle 30. Specifically, when a user approaches the shared terminal 10 and is detected by the detection unit 12, the candidate destination extraction unit 24 identifies the user's behavioral history until they arrive at the shared terminal 10. If the user traveled to the shared terminal 10 using the dispatched vehicle 30, the user's usage history of the dispatched vehicle 30 corresponds to the behavioral history. The candidate destination extraction unit 24 refers to the database 25 to identify the detected user's past transportation system usage history. The candidate destination extraction unit 24 compares the most recent behavioral history with the transportation system usage history stored in the database 25 and calculates the correlation. The candidate location extraction unit 24 then identifies usage history from the usage history of the transportation system stored in the database 25 that has a high correlation with the most recent behavioral history, and extracts the disembarking locations and/or destinations indicated by the highly correlated usage history as destination candidates. As an example of the conditions for extracting destination candidates by the candidate location extraction unit 24, the user approaching the shared terminal 10 and being detected by the detection unit 12 is given, but the shared terminal 10 in this condition is not necessarily limited to transfer points where multiple means of transportation are transferred, but may also be the departure point of the dispatched vehicle within the patrol area 100 (corresponding to boarding/alighting location A in Figure 1). Furthermore, the behavioral history and usage history compared to calculate the correlation may not be limited to the most recent, but may also be behavioral history and usage history from a predetermined period in the past.

The candidate location extraction unit 24 may extract not only candidate destinations but also candidate locations for transfers between multiple modes of transportation. The user approaches a shared terminal 10 installed at a boarding/alighting point on the circulating route near the departure point. When the detection unit of the shared terminal 10 detects the user's approach, the candidate location extraction unit 24 refers to the database 25 to obtain the usage history of the detected user and extracts the usage history starting from the boarding point of the vehicle used by the detected user. From the extracted usage history, the candidate location extraction unit 24 extracts transfer locations with a high frequency of use as candidate locations. At this time, the candidate location extraction unit 24 may also extract destinations and/or alighting points with a high frequency of use as target destinations from the extracted usage history.

Database 25 stores registered user personal information, vehicle reservation information, user usage history of the transportation system, user activity history, etc. Communication device 26 is connected to the telecommunications network NW and transmits and receives signals with the shared terminal 10, the vehicle 30, and the user terminal 40.

The dispatched vehicle 30 is a vehicle used for user transportation under the management of the server 20. The dispatched vehicle 30 has at least a communication device 31 capable of communicating with the server 20. The dispatched vehicle 30 transmits the current location information of the vehicle to the server 20 via the communication device 31. The communication device 31 is connected to a telecommunications network NW and transmits and receives signals with the server 20. The communication device 31 may also communicate with the shared terminal 10 and the user terminal 40.

The user terminal 40 is a user-owned device, such as a smartphone or tablet, and is a portable terminal device. The user terminal 40 has a display and displays traffic system guidance information transmitted from the shared terminal 10 or server 20 on its screen.

Next, referring to Figure 3, we will explain the user's actions, the control processes of the shared terminal 10 and server 20, from the user's arrival at the boarding location, through the transfer of the dispatched vehicle 30 at the transfer point, to arrival at the destination. Figure 3 is a flowchart showing the flow of the user's actions and the control processes of the shared terminal 10 and server 20.

In step S1, the user moves to a pick-up/drop-off point on the patrol route using a means of transportation such as a dispatched vehicle 30, other means of transport, walking, or a private car. In step S2, the detection unit 12 of the shared terminal 10 installed at the pick-up/drop-off point detects the user's approach. In step S3, the server 20 performs authentication processing to identify the user.

The control processes of steps S2 and S3 will now be explained. Figure 4 is a diagram illustrating the display screen of the display device 18 of the shared terminal 10, where Figure 4(a) shows a state in which multiple users have been detected, and Figure 4(b) shows a state in which one user has been detected.

The display screen of the display device 18 has a detection area that can detect the user's face, iris, or gait, and when the user's face or other features appear within this area, the display device 18 detects the user through image processing. As shown in Figure 4(a), if the detection unit 12 detects multiple users on the display device 18's screen, the detection unit 12 displays an "Authentication Start" button on the screen. When multiple users appear on the screen, it may not be possible to select a target for individual identification, so the "Authentication Start" button is displayed, and when the user touches the "Authentication Start" button, authentication for user identification begins. The detection unit 12 also displays a circle over the face of the detected user, indicating that the detected user has been successfully identified on the screen. By confirming this circle display, the user can determine that the user to be authenticated has been successfully detected.

Furthermore, the detection unit 12 starts a timer in conjunction with the display of the "Start Authentication" button. The detection unit 12 starts authentication if the "Start Authentication" button is touched within a predetermined time, or if a predetermined time has elapsed without any touch operation of the "Start Authentication" button. To start authentication, the detection unit 12 sends the image of the selected person along with the authentication start flag to the server 20. Selection may be made by the user's touch operation, or the person enclosed in a circle may be automatically selected.

As shown in Figure 4(b), when the detection unit 12 detects one user on the display device 18 screen, the detection unit 12 displays a "Cancel Authentication" button on the screen and starts a timer. Similar to the case of multiple users, the detection unit 12 displays a circle around the face of the detected user. When only one user is detected, the reliability of user detection is higher compared to the case of multiple users, so there is no button display such as "Start Authentication," and authentication for user identification begins after a predetermined time has elapsed. However, since there may be cases where other users who need to be authenticated should be visible on the screen, a "Cancel Authentication" button is provided. If a user wants to display other users on the screen, they can touch the "Cancel Authentication" button to perform user detection again. Then, to start authentication, the detection unit 12 sends the image of the detected person along with an authentication start flag to the server 20. Note that the person's image represents the user's personal information.

When the server 20 receives an authentication start flag from the detection unit 12 of the shared terminal 10, it accesses the database 25, which stores the user's biometric information, based on the user's image, which is personal information. The database 25 may include, for example, multiple databases separated by elements of biometric information. Elements of biometric information include, for example, facial images, iris information, gait models, etc. The server 20 compares the image of the person obtained from the detection unit 12 with the biometric information stored in the database 25. If multiple users are detected, each user is identified individually. For example, if multiple users are detected and some users can be identified from their facial images but the remaining users cannot, the detection unit 12 performs authentication using other elements of biometric information. The server 20 then outputs the authentication result to the shared terminal 10 or the user terminal 40. Authentication may also be performed by combining multiple databases separated by elements of biometric information.

When a user is identified through the control process in step S3, in step S4, the candidate location extraction unit 24 of the server 20 acquires the location information of the shared terminal 10 where the user was detected. In step S5, the candidate location extraction unit 24 acquires the activity history of the detected user. If the user traveled to the shared terminal 10 using the dispatched vehicle 30, the candidate location extraction unit 24 acquires the activity history from the travel plan (travel history) of the dispatched vehicle 30 that the user was riding in. If the user traveled to the shared terminal 10 by means other than the dispatched vehicle 30, the candidate location extraction unit 24 connects to the user terminal 40 and acquires the activity history from the data related to the user's activity history. The candidate location extraction unit 24 also accesses the database and acquires the usage history of the detected user.

In step S6, the candidate location extraction unit 24 acquires time information of when the user operates the shared terminal 10. For example, the timing of receiving the authentication start flag from the detection unit 12 is considered to be when the user operates the shared terminal 10.

In step S7, the candidate location extraction unit 24 extracts candidate destinations. The candidate location extraction unit 24 extracts candidate destinations in the following manner. The usage history stored in the database 25 includes various elements such as the departure point/transfer point/destination of the dispatched vehicle 30, the user's boarding/alighting points/stopping points, usage time, the driving route of the dispatched vehicle 30, and the user's travel route. The usage history stored in the database 25 may be separated into elements and then stored in multiple databases 25 in association with user information and candidate destinations. First, the candidate location extraction unit 24 obtains the most recent activity history. For example, in the example in Figure 1, suppose the user departs from point C near their home and travels to transfer point B by train and on foot, arriving at transfer point B at 2:00 PM. If the detection unit 12 of the shared terminal 10 installed at transfer point B detects the user (hereinafter also referred to as "example of travel from home A"), the activity history from home to transfer point B becomes the most recent activity history (hereinafter also referred to as the most recent activity history). Furthermore, if a user makes a stop at a hospital or other location before traveling from their home to transit point B, that stop will also be included in their recent travel history.

The candidate location extraction unit 24 identifies usage history from the database 25 that correlates with the most recent activity history, based on the location information of the shared terminal 10 and the time information when the user operated the shared terminal 10. The candidate location extraction unit 24 extracts activity history from the usage history stored in the database 25 (hereinafter also referred to as "stored usage history") that uses the current user's location as a transfer point and that includes the time the shared terminal 10 was operated within the time period of the usage history. For example, in the case of "Example A of travel from home," the candidate location extraction unit 24 extracts usage history that satisfies the following two conditions: that transfer point B was used as the transfer point, and that the time period of use of the transportation system includes 2 p.m.

If there are many usage histories that meet the conditions, the candidate location extraction unit 24 may, for example, extract only the stored usage histories that are close to the current time. Stored usage histories that are close to the current time include, for example, the history from several weeks or several months prior to the current date and time.

Furthermore, the candidate destination extraction unit 24 extracts the user's travel history according to the travel route from the user's departure point to the transfer point. The control flow of the candidate destination extraction unit 24 will be explained below with reference to Figure 5. Figure 5 is a flowchart of the subflow included in the control processing of step S7.

In step S21, the candidate location extraction unit 24 identifies the user's most recent activity history, specifically the activity history up to the transfer point. In step S22, the candidate location extraction unit 24 determines whether the user traveled to the transfer point from outside the patrol area. In the above "Example A of travel from home," since the departure point is outside the patrol area 100, the candidate location extraction unit 24 determines that the user traveled to the transfer point from a registered location outside the patrol area. If the user traveled to the transfer point from outside the patrol area, in step S23, the candidate location extraction unit 24 extracts the usage history from the stored usage history that shows travel from a registered location outside the patrol area to the transfer point. On the other hand, if the user traveled to the transfer point from a registered location within the patrol area, in step S24, the candidate location extraction unit 24 extracts the usage history from the stored usage history that shows travel from a registered location within the patrol area to the transfer point. In other words, in the control processing steps S22 to S24, the registered location such as home is used as the starting point, and the usage history compared when calculating the correlation is separated depending on whether the starting point is within or outside the patrol area. Note that the starting point does not necessarily have to be the registered location.

In step S25, the candidate location extraction unit 24 compares the detected user's recent activity history with the extracted stored usage history and extracts three candidate locations in order of highest correlation. The candidate location extraction unit 24 compares the spots included in the recent activity history and the stored usage history and calculates the correlation. The spots indicate locations included in the activity history and usage history, such as the departure point/transfer point/destination of the dispatched vehicle 30, the user's boarding/alighting points/places visited, etc. For example, in the "Example of travel from home A" above, let's assume that the user stopped at "workplace," "supermarket," and "hospital" while traveling from point C to transfer point B. In such a case, the stored usage history from when the user traveled from point C to transfer point B identifies the stored usage history in which the user stopped at at least one of the spots among "workplace," "supermarket," and "hospital."

The candidate location extraction unit 24 compares the spots in the most recent activity history with the spots in the stored usage history, and usage histories with many common spots are considered to have a high correlation. Furthermore, the candidate location extraction unit 24 extracts destinations from the stored usage history as candidate destinations in order of the degree of correlation. For example, if stored usage history for the number of uses (20 times) is extracted by the control process in step S23, it is determined whether the spots from point C to transfer point B among those stored usage history matches "workplace," "supermarket," and "hospital." The higher the degree of match, the higher the correlation. For example, suppose stored usage history for the number of uses (20 times) is extracted, and of the extracted usage histories, 15 stored usage histories are common to 3 spots, 4 stored history histories are common to 2 spots, and 1 stored usage history is common to 1 spot. The candidate location extraction unit 24 extracts the destinations of the 15 most highly correlated stored usage histories as the candidate location with the highest correlation, and the destination of the 1 least correlated stored usage histories as the candidate location with the lowest correlation. If the destinations of the 15 most correlated stored usage histories differ for each history, the destination with the most occurrences may be used as the candidate location. The correlation does not need to be calculated from the degree of spot matching; for example, it may be calculated from the travel route or the mode of transportation used. The candidate location extraction unit 24 then terminates the control processing of step S7.

As a user characteristic, if the user's behavioral history from a place where they frequently stay, such as their home, to a transfer point on the patrol route shows a high correlation with their past use of transportation systems, they tend to head to the same destination or disembarkation point as in their past usage history after transferring at the transfer point. For example, suppose a user's workplace is within the patrol route, and their home is outside the patrol route, and the user boards the patrol vehicle at a boarding point near their workplace and disembarks at a transfer point. Furthermore, suppose the user goes shopping at a supermarket before disembarking at the boarding point. In such behavioral history, it can be predicted with a high probability that the user will return home after the transfer point, and the candidate destination extraction unit 24 extracts "home" as a highly correlated destination candidate for the user.

Furthermore, in this embodiment, in the control flow of step S21, the usage history of the transportation system referenced for extracting candidate locations is distinguished depending on whether the route taken by the user to the transfer point is within the patrol area 100 or not. That is, the usage history stored in the database 25 includes a first behavioral history showing the behavioral history when the user moves from within the patrol area 100 of the dispatched vehicle 30 to outside the patrol area 100 via the transfer point, and a second behavioral history showing the behavioral history when the user moves from outside the patrol area 100 to inside the patrol area via the transfer point. The candidate location extraction unit 24 extracts candidate locations based on the first behavioral history when the user arrives at the transfer point using the dispatched vehicle 30 traveling along the patrol route, and extracts candidate locations based on the second behavioral history when the user arrives at the transfer point using transportation from outside the patrol area. This improves the accuracy of predicting candidate locations. Note that the patrol area 100 corresponds to the "predetermined travel area" of the present invention.

If the dispatched vehicle 30 does not travel along the predetermined route, the database 25 stores a first behavioral history showing the user's movement history when the user moves from within the predetermined driving area to outside the predetermined driving area via a transfer point, and a second behavioral history showing the user's movement history when the user moves from outside the predetermined driving area to within the predetermined driving area via a transfer point. The predetermined driving area is the area in which a specific dispatched vehicle 30 can travel, and in the example of Figure 1, it is driving area 100. The candidate destination extraction unit 24 then extracts candidate destinations based on the first behavioral history when the user arrives at a transfer point using a dispatched vehicle 30 traveling within the predetermined driving area, and extracts candidate destinations based on the second behavioral history when the user arrives at a transfer point using other means of transportation from outside the predetermined driving area.

Referring to Figure 3, in step S8, the information acquisition unit 13 acquires information on candidate locations extracted based on the usage history of the transportation system from the server 20. The display control unit 14 displays the information on candidate locations on the display device 18 of the shared terminal 10. In step S9, the user checks the candidate destinations on the display screen of the display device 18 and selects a candidate location by touch operation. The display of destinations on the display screen of the display device 18 is a simple display. For example, it may be a display format that shows only text such as "Restaurant X", "Station A", and "Home", or a display format that shows the location of the candidate location and the driving route from the current location to the candidate location. Also, it is better to display a small number of candidate locations, for example, three. This simplifies the user's touch operation and provides a highly convenient system for the user.

In step S10, the shared terminal 10 sends the selection result to the server 20. In step S11, the reservation management unit 21 of the server 20 sets the selected candidate location as the destination. In step S12, the vehicle management unit 22 calculates the route of the dispatched vehicle 30 traveling towards the selected destination. In step S13, the reservation management unit 21 assigns a dispatched vehicle 30 that can travel the route and confirms the reservation of the dispatched vehicle 30. The reservation management unit 21 sends the confirmed reservation information to the shared terminal 10.

In step S14, the display control unit 13 of the shared terminal 10 displays the confirmed reservation information on the display device 18 to inform the user that the reservation is complete. In step S15, the user confirms the reservation details of the dispatched vehicle 30 from the transfer point to the destination from the display screen of the display device 18. After that, the user boards the reserved dispatched vehicle 30 and travels to the destination.

Next, referring to Figure 6, we will explain how to store the usage history in the database 25. Figure 6 is a classification table for sorting the usage history. Note that the classification shown in Figure 6 is just one example, and other classifications may be used. The usage history storage unit 23 classifies the acquired user usage history of the transportation system based on the classification table in Figure 6, and then stores the usage history in the database 25. The classification items are "travel route," "travel distance," "date and time," and "long-distance element." The classification item "travel route" classifies whether the travel route starts from a registered location such as home, or whether it ends at a registered location such as home. The classification item "travel distance" classifies whether the travel distance is long-distance or short-distance. This is because the possible stops that can be considered points of interest differ depending on whether the travel distance is short or long, so it is included as a classification item.

The classification item "Date and Time" is categorized into "Time of day (e.g., AM, PM)", "Day of the week", "Week", and "Month". Since human behavior is predetermined by time cycles, "Date and Time" is used as a classification item to align with these behavioral cycles. For example, suppose a user travels from outside the patrol area to a transfer point to buy groceries for dinner, transfers to a vehicle at the transfer point, and heads to a supermarket within the patrol area. Since such user behavior occurs daily, the time of departure from the starting point (such as home) and the time of arrival at the transfer point are often the same for each trip. Furthermore, in daily behavioral history, for example, if the departure time is in the late afternoon (e.g., 3 PM to 4 PM), the behavioral history often involves going to a supermarket, while if the departure time is in the early morning (e.g., 7 AM to 8 AM), the behavioral history often involves going to work. In other words, there can be a correlation between the time of day a user uses the transportation system and their destination, so the usage history database will be created to include user destination information for each time of day a user uses the transportation system. Furthermore, the classification item "long-distance elements" is further classified into "accommodation facilities" and "tourist destinations." For example, in the case of business trips involving overnight stays, a person's behavior differs significantly from their daily behavior. Therefore, in cases involving special activities such as business trips involving overnight stays or sightseeing, the usage history is separated and stored in database 25. The usage history storage unit 23 stores the user's usage history in database 25 based on this classification. Note that database 25 may include multiple databases separated by classification items. When the candidate destination extraction unit 24 calculates the correlation by comparing the user's recent activity history with the stored usage history, it may compare the recent activity history with the stored usage history for each classification item and calculate the correlation such that the more matching items there are, the higher the correlation.

As described above, the transportation system according to this embodiment detects a user approach state, which is when a user is approaching the shared terminal 10, controls the display device 18 of the shared terminal 10, extracts candidate destinations based on the detected user's transportation system usage history, and displays information about the candidate destinations on the display device 18 of the shared terminal 10 when the user approach state is detected. As a result, the destination candidates are displayed on the display device 18 of the shared terminal 10 in accordance with the timing when the user approaches the shared terminal 10, allowing the user to select a drop-off point or destination with simple operation. Consequently, the convenience of the system for the user can be improved.

In this embodiment, the travel route of the dispatched vehicle 30 heading towards the location selected by the user from among the candidate locations is calculated, and the travel route information is displayed on the display device 18 of the shared terminal 10. This allows the user to easily confirm the travel route to the selected candidate location.

Furthermore, the shared terminal control device 11 and the shared terminal control method according to this embodiment detect a user approaching state, acquire information on candidate destinations extracted based on the user's usage history of the transportation system, and, when a user approaching state is detected, display the information on the candidate destinations on the display device 18 of the shared terminal 10. As a result, the candidate destinations are displayed on the display device 18 of the shared terminal 10 in accordance with the timing when the user approaches the shared terminal 10, allowing the user to select a disembarking point or destination with simple operation. Consequently, the convenience of the system for the user can be improved.

In a modified version of this embodiment, the detection unit 12 of the shared terminal 10 may detect the user's attributes, and the candidate destination extraction unit 24 of the server 20 may extract candidate destinations based on the user's attributes. For example, if the number of data points in the user's stored usage history is small and the number of destination candidates extracted is small, or if there are few destination candidates, the candidate destination extraction unit 24 identifies other users who have the same attributes as the detected user. Then, the candidate destination extraction unit 24 extracts destination candidates based on the usage history of the other users. This makes it possible to extract destination candidates even when the number of data points in the user's stored usage history is small.

In a modified version of this embodiment, the display control unit 14 of the shared terminal 10 may display information on candidate transfer points extracted by the candidate transfer point extraction unit 24 on the display device 18 of the shared terminal 10. As a result, candidate transfer points are displayed on the display device 18 of the shared terminal 10 in accordance with the timing when the user approaches the shared terminal 10, allowing the user to select a transfer point with simple operation. Consequently, the user's convenience to the system can be improved.

In this embodiment, the candidate location extraction unit 24 may extract various candidate locations depending on the traffic conditions when extracting target value candidates and transfer location candidates. For example, if the candidate location extraction unit 24 extracts the destination with the highest correlation to the stored usage history, but determines from the current traffic conditions that the roads around that destination are congested, it will change to another destination with a higher correlation.

In this embodiment, the candidate location extraction unit 24 may extract various candidate locations according to the user's appearance when extracting target value candidates and transfer location candidates. For example, when the usage history acquisition unit 23 stores the user's usage history of the transportation system in the database 25, it includes information about the user's appearance in the behavioral history and stores it in the database 25. Information about the user's appearance includes the user's clothing, etc. The database 25 includes "appearance" as a classification item. The candidate location extraction unit 24 refers to the database 25 to obtain the usage history of the detected user and extracts usage history of the transportation system used by the detected user with the same or similar appearance. From the extracted usage history, the candidate location extraction unit 24 extracts transfer locations and/or destinations that have been used frequently as candidate locations.

For example, if a user wears a suit to work, the departure time from their home or other starting point and the arrival time at their transfer point are often the same for each trip. In such cases, even if the departure time is the same as when going to work, if the user is dressed casually, they are likely to go to a different place than their workplace. The candidate location extraction unit 24 refers to the database 25 and extracts usage history from the user's usage history when they used the transportation system at the same time of day while dressed casually, and extracts candidate locations such as destinations. If multiple candidate locations are extracted, the priority is increased for the candidate location with the most usage history or the candidate location with a higher degree of clothing match. The display control unit 14 should then display the candidate locations with the highest priority.

In this embodiment, the candidate destination extraction unit 24 may extract candidates for the dispatched vehicle 30, and the display control unit 14 of the shared terminal 10 may display information about the candidate dispatched vehicle 30 on the display device 18 of the shared terminal 10. For example, if there are multiple dispatched vehicles that can travel to the destination extracted by the candidate destination extraction unit 24, the vehicle type information and in-vehicle congestion information of the candidate dispatched vehicles 30 are displayed on the display device 18 of the shared terminal 10. This provides the user with a selection of dispatched vehicles 30.

The embodiments described above are provided to facilitate understanding of the present invention and are not intended to limit it. Therefore, each element disclosed in the above embodiments is intended to include all design modifications and equivalents that fall within the technical scope of the present invention.

10 Shared terminal 11 Shared terminal control device 12 Detection unit 13 Information acquisition unit 14 Display control unit 15 Operation input unit 16 Reservation acceptance unit 17 Link establishment unit 18 Display device 19 Communication device 20 Server 21 Reservation management unit 22 Vehicle management unit 23 Usage history storage unit 24 Candidate location extraction unit 25 Database 26 Communication device 30 Dispatched vehicle 40 User terminal

Claims (9)

In a vehicle dispatching transportation system,
A shared terminal installed along the route of the aforementioned dispatched vehicle,
The system includes a controller for managing the dispatched vehicles,
The aforementioned shared terminal is
It is installed at a transfer point where multiple modes of transportation, including the aforementioned dispatched vehicle, are used for transfers.
A detection unit that detects a user approaching the shared terminal,
It has a display control unit that controls the display device of the shared terminal,
The aforementioned controller,
Based on the user's usage history of the transportation system detected by the detection unit, the system includes a candidate location extraction unit that extracts candidate locations for at least one of the following: the drop-off location where the user alights from the dispatched vehicle, and the destination to which the user is going using the dispatched vehicle.
The aforementioned candidate site extraction unit,
Based on the user's travel route from their departure point to their transfer point, their activity history is extracted.
Disembarking locations and/or destinations indicated by usage history that has a high correlation with the aforementioned travel history up to the aforementioned transfer point are extracted as candidate locations.
The display control unit is a traffic system that, when the detection unit detects the user approaching, displays information about the candidate location on the shared terminal or user terminal . In the transportation system according to claim 1,
The aforementioned controller,
The system includes a calculation unit that calculates the travel route of the dispatched vehicle traveling toward the point selected by the user from among the candidate locations,
The display control unit is a traffic system that displays the travel route information on the shared terminal or user terminal . In the transportation system according to claim 1 or 2,
The detection unit detects the user's attributes,
The candidate location extraction unit is a transportation system that extracts candidate locations based on the user's attributes. A transportation system according to claim 1 or 2,
The candidate location extraction unit extracts candidate locations for the transfer point based on the user's usage history of the transportation system.
The display control unit is a transportation system that displays information about candidate transfer points on the shared terminal or user terminal . A transportation system according to claim 1 or 2,
The usage history includes a first behavioral history showing the user's actions when the user moves from within a predetermined driving area of the dispatched vehicle to outside the predetermined driving area via the transfer point, and a second behavioral history showing the user's actions when the user moves from outside the predetermined driving area to within the predetermined driving area via the transfer point.
The aforementioned candidate site extraction unit,
When the user arrives at the transfer point using the dispatched vehicle traveling along a route within the predetermined travel area, the candidate destinations are extracted based on the first travel history.
A transportation system that extracts candidate destinations based on the second travel history when the user arrives at the transfer point from outside the predetermined travel area using the means of transport. A transportation system according to claim 1 or 2 ,
The aforementioned usage history includes the user's destination information for each time period during which the user used the transportation system. A transportation system according to claim 1 or 2 ,
The candidate location extraction unit is a transportation system that extracts candidate locations according to the user's appearance. A shared terminal control device that controls a shared terminal installed on the route of a dispatched vehicle,
A detection unit that detects a user approaching the shared terminal,
An information acquisition unit acquires information on candidate locations, which are at least one of the drop-off locations where the user alights from the dispatched vehicle, and the destination to which the user is going using the dispatched vehicle, and which are extracted based on the user's usage history of the transportation system.
The system comprises a display control unit that, when the detection unit detects the user approaching state, displays information about the candidate location on the shared terminal or the user terminal , and the shared terminal is installed at a transfer point where multiple means of transportation, including the dispatched vehicle, are transferred.
The user's travel history is extracted according to the route taken from the user's departure point to the transfer point.
Disembarking locations and/or destinations indicated by usage history that has a high correlation with the aforementioned travel history up to the aforementioned transfer point are extracted as candidate locations.
The display control unit is a shared terminal control device that displays the extracted candidate location information on the shared terminal or user terminal . A control method for controlling a shared terminal installed on the route of a dispatched vehicle, which is executed by a processor,
The aforementioned shared terminal is installed at a transfer point where multiple modes of transportation, including the aforementioned dispatched vehicle, are transferred.
The aforementioned processor,
The system detects a user approaching the shared terminal,
Based on the user's travel route from their departure point to their transfer point, their activity history is extracted.
The user extracts candidate locations that are highly correlated with the user's travel history up to the aforementioned transfer point, the drop-off location where the user alights from the dispatched vehicle, and/or the destination to which the user travels using the dispatched vehicle.
A method for controlling a shared terminal to display information about the candidate location on the shared terminal or user terminal when the user approach state is detected.