JP7643162B2 - Transit route proposal device and transit route proposal method - Google Patents

Description

The present invention relates to a transfer route suggestion device and a transfer route suggestion method.

There is a known invention that provides users with alternative routes to avoid crowded stations when transferring between public transport (Patent Document 1).

Patent No. 6470010

However, during periods when an infectious disease is prevalent, it is necessary to consider the length of time that a person will be in contact with others, but this is not taken into consideration in the invention described in Patent Document 1. Even in places that are not very crowded, if a person stays there for a long time, there is a risk that the number of people with whom a person comes into contact will increase.

The present invention was made in consideration of the above problems, and its purpose is to provide a transfer route suggestion device and a transfer route suggestion method that can reduce the number of people who come into contact during a transfer.

In one aspect of the present invention, when a transfer of transportation means is required, a transfer route suggestion device extracts multiple possible transfer route candidates, predicts the number of contacts, which indicates the number of other users who will come into contact with the user within a specified range at the transfer point per unit time, based on specified information for each of the extracted transfer route candidates, and suggests to the user, among the multiple transfer route candidates, transfer route candidates with fewer contacts over transfer route candidates with a larger number of contacts.

The present invention makes it possible to reduce the number of people who come into contact with each other during transfers.

FIG. 1 is a schematic diagram of a connecting route suggestion system 10 according to an embodiment of the present invention. FIG. 2 is a functional block diagram of the management server 20, the communication device 60, and the taxi 40 according to the embodiment of the present invention. FIG. 3 is a diagram illustrating a plurality of connecting route candidates. FIG. 4 is a diagram for explaining the number of contacts. FIG. 5 is a diagram illustrating an example of a route suggestion method. FIG. 6 is a flowchart illustrating an example of an operation of the connecting route proposal device according to the embodiment of the present invention. FIG. 7 is a flowchart illustrating an example of the operation of the connecting route proposal device according to the modified example of the present invention.

Embodiments of the present invention will be described below with reference to the drawings. In the description of the drawings, identical parts are given the same reference numerals and the description will be omitted.

An example of the configuration of a transit route proposal system 10 according to this embodiment will be described with reference to Figures 1 and 2. As shown in Figure 1, the transit route proposal system 10 includes a management server 20, a communication network 30, taxis 40 to 42, a user 70, and a communication device 60 owned by the user 70. Note that although there are three taxis in Figure 1, this is not limiting. The transit route proposal system 10 may include four or more taxis.

The management server 20 communicates with the taxis 40-42 and the communication device 60 via the communication network 30. The management server 20 is a general-purpose computer equipped with a CPU (Central Processing Unit) 21, a memory 22, a communication I/F 23, and a storage device 24, and these components are electrically connected via a bus (not shown). The management server 20 is used for the dispatch service of the taxis 40-42. There are no particular limitations on where the management server 20 is installed, but for example, the management server 20 is installed in the management center of the company that operates the taxis 40-42.

The CPU 21 loads various programs stored in the storage device 24 and the like into the memory 22 and executes various commands contained in the programs. The memory 22 is a storage medium such as a ROM (Read Only Memory) or a RAM (Random Access Memory). The storage device 24 is a storage medium such as a SSD (Solid State Drive) or a HDD (Hard Disk Drive). Note that a part (or all) of the transit route proposal system 10, including the functions of the management server 20 described below, may be provided by an application (such as Software as a Service (SaaS)) located on the communication network 30.

The communication I/F 23 is implemented as hardware such as a network adapter, various communication software, or a combination of these, and is configured to realize wired or wireless communication via a communication network 30 or the like. The communication I/F 23 also functions as an input unit and an output unit for transmitting and receiving data.

The communication network 30 may be configured using either a wireless or wired system, or both, and may include the Internet. In this embodiment, the management server 20, the taxis 40 to 42, and the communication device 60 are connected to the communication network 30 using a wireless communication system.

The taxis 40 to 42 may be normal vehicles with a driver, or may be autonomous vehicles without a driver. An autonomous vehicle without a driver may be referred to as a robot taxi or an unmanned taxi. In this embodiment, the taxis 40 to 42 are described as autonomous vehicles without a driver.

A user 70 uses a communication device 60 to request (reserve) a taxi. A transit dispatch application (hereinafter simply referred to as a transit dispatch app) used for reserving a taxi is installed in the communication device 60, and the user 70 uses the transit dispatch app to request a taxi.

Next, the detailed configurations of the management server 20, taxi 40, and communication device 60 will be described with reference to FIG. 2. Note that taxis 41 and 42 are omitted in FIG. 2, but taxis 41 and 42 have the same configuration as taxi 40.

The communication device 60 includes a communication I/F 601, a transit dispatch app 602, a GPS receiver 603, and a display 604. The communication I/F 601 has a configuration similar to that of the communication I/F 23 (see FIG. 1), and communicates with the management server 20 via the communication network 30. The communication device 60 is, for example, a portable device such as a smartphone or a tablet. The communication device 60 may also be a wearable device. Although not shown in the figure, the communication device 60 also includes a CPU (controller), memory, storage device, etc., like the management server 20.

The transfer dispatch app 602 is used to request a taxi as described above. The transfer dispatch app 602 functions as a user interface when the user 70 requests a taxi. The transfer dispatch app 602 is realized by the CPU provided in the communication device 60 reading and executing a dedicated application program from a storage device provided in the communication device 60. When the user 70 requests a taxi, the user 70 inputs a desired boarding location, a desired boarding time, a desired disembarking location, and the like into the transfer dispatch app 602 and requests a taxi. In this embodiment, "transfer required" means that the user 70 is on a train at the time of the request and needs to transfer to a taxi at the station where the user disembarks from the train to head to the destination. The user 70 does not necessarily need to input a desired boarding location and a desired boarding time. This will be described later.

The transfer ride dispatch app 602 transmits a ride dispatch request to the management server 20 in accordance with input from the user 70. The communication device 60 also displays on the display 604 various pieces of information (receipt of ride dispatch request, estimated arrival time, planned route, number of contacts, etc.) contained in the signal returned from the management server 20 in response to the ride dispatch request. However, the method of realizing the transfer ride dispatch app 602 is not limited to this. For example, the communication device 60 may access a server that provides the functions of the transfer ride dispatch app 602 to receive the functions, and display the execution results of the functions transmitted from the server on the browser. The number of contacts will be described later.

The location information of the communication device 60 acquired by the GPS receiver 603 is transmitted to the management server 20 at any time.

The taxi 40 includes a communication I/F 401, a vehicle ECU (Electronic Control Unit) 402, and a GPS receiver 403. The communication I/F 401 has a configuration similar to that of the communication I/F 23 and the communication I/F 601, and communicates with the management server 20 via the communication network 30. The vehicle ECU 402 is a computer for controlling the taxi 40. The vehicle ECU 402 controls various actuators (such as a brake actuator, an accelerator actuator, and a steering actuator) based on commands received from the management server 20. The position information of the taxi 40 acquired by the GPS receiver 403 is transmitted to the management server 20 at any timing.

As shown in the block diagram of FIG. 2, the CPU 21 (controller) of the management server 20 includes, as examples of multiple functions, a vehicle dispatch reception unit 211, an allocation unit 212, a route extraction unit 213, a location information acquisition unit 214, a required time calculation unit 215, a population density prediction unit 216, a contact number prediction unit 217, and a route proposal unit 218. As shown in FIG. 2, the storage device 24 of the management server 20 stores a map database 241, a customer database 242, an event information database 243, and a transportation congestion information database 244.

Map database 241 stores map information necessary for route guidance, such as road information and facility information. Map information includes the number of lanes on a road, road width information, and road undulation information. Map information also includes road signs indicating speed limits, one-way streets, etc., and road markings indicating crosswalks, dividing lines, etc.

The customer database 242 stores account information such as the ID of the user 70, taxi usage history, etc. The taxi usage history is the history of use of the transit route proposal system 10 according to this embodiment.

The dispatch reception unit 211 receives a dispatch request from the user 70 input to the communication device 60. The dispatch reception unit 211 has a function of notifying the communication device 60 that the dispatch request from the user 70 has been received, the expected arrival time at the boarding location, the planned driving route to the boarding location, etc.

The allocation unit 212 allocates an appropriate taxi from among the multiple taxis 40-42 (see FIG. 1) based on the received dispatch request. For example, for the sake of efficiency, the dispatch reception unit 211 can allocate an available taxi from among the multiple taxis 40-42 that is closest to the boarding location desired by the user 70.

The allocation unit 212 also refers to the map database 241 to set a driving route from the current location of the allocated taxi to the boarding location desired by the user 70, and sends a command to the taxi 40 to drive along the set driving route to the boarding location desired by the user 70. The driving route calculated by the allocation unit 212 is, for example, a route that can arrive at the boarding location desired by the user 70 in the shortest time from the current location of the taxi 40. Note that if the route extraction unit 213 determines that a transfer of transportation means is necessary, the route may be set by another method.

When the route extraction unit 213 determines that a transfer is necessary, it extracts multiple possible transfer route candidates. Here, the possible transfer route candidates will be described with reference to FIG. 3. The scene shown in FIG. 3 is a scene in which a user 70 is on a train 80 heading to station A 81. Reference numeral 83 is the destination of the user 70. The user 70 on the train 80 operates the transfer dispatch app 602 to request a taxi. In the scene of FIG. 3, it is assumed that the user 70 inputs the destination 83, the desired arrival time at the destination 83, and that a transfer is necessary. Here, it is assumed that the user 70 does not input the desired boarding location, i.e., the station where the taxi will be boarded.

The allocation unit 212 that receives the request from the user 70 extracts stations where the user 70 may get off to arrive at the destination 83 based on the current location information of the user 70 (more precisely, the current location information of the communication device 60 owned by the user 70). This is realized by extracting stations in order of proximity to the destination 83 by referring to the current location information of the user 70 and the map database 241. The current location information of the user 70 is acquired by the location information acquisition unit 214. In the scene of FIG. 3, it is assumed that two stations, Station A 81 and Station B 82, are extracted as stations where the user 70 may get off to arrive at the destination 83. The allocation unit 212 allocates taxis that are near Station A 81 and Station B 82 as taxis that will pick up the user 70. In the scene of FIG. 3, the allocated taxi is Taxi 40. In this way, when a transfer of transportation means is required to arrive at the destination 83, the route extraction unit 213 determines that a transfer of transportation means is required. This determination is made automatically mainly based on the current location information of the user 70 and the destination 83 of the user 70. However, it is not limited to this. When requesting a taxi, the user 70 may input that a transfer is required on the transfer dispatch app 602. Then, when the route extraction unit 213 receives a signal from the user 70 indicating that a transfer is required, the route extraction unit 213 may extract multiple transfer route candidates that allow transfer.

The route extraction unit 213 extracts the driving route of the taxi 40. Specifically, the route extraction unit 213 extracts two driving routes, a driving route R1 and a driving route R2. The driving route R1 is a route that picks up the user 70 at station A 81 and then heads to the destination 83. From the perspective of the user 70, the driving route R1 is a route that heads to the destination 83 along the route indicated by the symbol 84. The driving route R2 is a route that picks up the user 70 at station B 82 and then heads to the destination 83. From the perspective of the user 70, the driving route R2 is a route that heads to the destination 83 along the route indicated by the symbol 85. The driving routes R1 and R2 are routes that can arrive at the destination 83 by the desired arrival time of the user 70, even including the transfer time at the station. In this way, when the route extraction unit 213 determines that a transfer of transportation means is necessary, it extracts multiple transfer route candidates that can be transferred. The multiple transfer route candidates here refer to the driving route R1 and the driving route R2. The multiple transfer route candidates extracted by the route extraction unit 213 are merely candidates, and the user 70 has the final decision on which travel route to select. As explained above, the user 70 does not necessarily need to input the desired boarding location or desired boarding time. This is because if the destination of the user 70 is reference number 83, the system automatically determines that the station where the user 70 may get off is station A 81 or station B 82. In addition, the system automatically determines the arrival time at station A 81 or station B 82, so if the transfer time at a station is known, the boarding time at the station is also automatically determined by the system.

Returning to FIG. 2, the location information acquisition unit 214 acquires location information of the user 70 from the communication device 60, and acquires location information of the taxi 40 from the taxi 40. The location information of the user 70 means the location information of the communication device 60 carried by the user 70. The location information acquisition unit 214 outputs the acquired location information to the required time calculation unit 215.

The required time calculation unit 215 uses the location information of the taxi 40 acquired from the location information acquisition unit 214 to calculate the required time from the current location of the taxi 40 via Station A 81 or Station B 82 (including transfer time) to arrive at the destination 83 desired by the user 70. If the required time calculated by the required time calculation unit 215 exceeds the desired arrival time of the user 70, that is, if the desired arrival time of the user 70 is not in time, the route extraction unit 213 excludes candidates that will not make it to the desired arrival time. For example, in the scene of FIG. 3, assume that the next station after Station B 82 is Station C. The route extraction unit 213 can extract a route to the destination 83 via Station C, but if the desired arrival time of the user 70 will not be made if the desired arrival time of the user 70 is not made if the desired arrival time ..., the route via Station C is excluded.

The population density prediction unit 216 predicts the average population density (persons/m ² ) at the transfer point. The transfer point means a place where the user 70 transfers between transportation means to go to the destination 83, and in the example of FIG. 3, it is station A 81 and station B 82. The population density prediction unit 216 predicts the average population density at the transfer point by referring to the event information database 243 or the transportation congestion information database 244. The event information database 243 stores event information such as what events are being held near station A 81 or station B 82. As an example, if a sports event, live performance, etc. is being held near station A 81 or station B 82, the average population density will increase during the time period when the event is being held. In this way, the population density prediction unit 216 can predict the average population density at the transfer point by referring to the event information database 243. Note that the event information database 243 may store the average population density at the time of a past event. In this case, if an event similar to a past event is being held, the current average population density can be predicted by referring to the past data.

The transport congestion information database 244 stores information about station congestion obtained from transport operators (e.g., railway companies). By referring to the transport congestion information database 244, the population density prediction unit 216 is able to predict the average population density at transfer points.

The contact number prediction unit 217 predicts the number of contacts at the transfer point. In this embodiment, the definition of "contact number" is that of the National Institute of Infectious Diseases. According to the definition of the National Institute of Infectious Diseases, a "close contact" is a person who has had contact with a "patient (confirmed case)" for 15 minutes or more at a distance where they can touch each other (approximately 1 meter) without taking necessary infection prevention measures (the infectiousness of the patient is judged comprehensively from individual circumstances such as the surrounding environment and the situation of contact). Note that this definition is an example of the definition of a "close contact," but this definition is used in this embodiment. Please refer to the following link if necessary for this definition. https://www.niid.go.jp/niid/images/epi/corona/COVID19-02-210108.pdf

In this embodiment, the definition of "close contact" is used to define the "number of contacts" as the number of people who have been in contact within 1 m for 15 minutes or more. Details of the "number of contacts" will be described with reference to FIG. 4. Reference numeral 90 in FIG. 4 indicates a circle with a radius of 1 m centered on user 70. If there is a user 71 who has stayed within this circle 90 for 15 minutes or more, the user 71 is counted as a "number of contacts." In other words, contact here does not mean direct contact, but means that if there is a user 71 who has stayed within a radius of 1 m for 15 minutes or more, the user 71 is considered to have been in contact. Next, an example of a method for predicting the number of contacts will be described. The number of contacts can be calculated using Equation 1.

[Equation 1]
Number of contacts = (number of contacts per unit time) x (transfer time) ... (1)

The "number of contacts per unit time" in formula 1 is the number of contacts per unit time (people/minute) calculated by dividing the average population density predicted by the population density prediction unit 216 by 15 minutes. Therefore, formula 1 may be expressed as formula 2.

[Equation 2]
Number of contacts = (average population density ÷ 15) × (transfer time) ... (2)

The "transfer time" in formulas 1 and 2 is the time required to transfer at a transfer point. As an example, the "transfer time" includes the time from getting off the train to the ticket gate, the time from the ticket gate to the taxi stand, and the like. Here, assume that the "transfer time" at station A 81 in FIG. 3 is 6 minutes, and the "transfer time" at station B 82 in FIG. 3 is 2 minutes. Also assume that the average population density at station A 81 is 0.24 people/1 m radius circle, and the average population density at station B 82 is 0.48 people/1 m radius circle. In this case, the "contact number of people" at station A 81 is 0.24÷15×6≒0.1 people. The "contact number of people" at station B 82 is 0.48÷15×2≒0.06 people. In this way, according to the prediction by the contact number prediction unit 217, it is found that the "contact number of people" at station B 82 is less than the "contact number of people" at station A 81.

The route suggestion unit 218 preferentially suggests to the user 70 a route that is predicted by the contact number prediction unit 217 to have fewer contact people. Taking FIG. 3 as an example, since the travel route R2 via B station 82 is predicted to have fewer contact people than the travel route R1 via A station 81, the route suggestion unit 218 preferentially suggests the travel route R2 to the user 70. The method of preferentially suggesting is not particularly limited, but for example, as shown in FIG. 5, the travel route R2 may be displayed on the screen of the communication device 60 as a recommended route. As shown in FIG. 5, the required time and the number of contact people may be displayed at the same time. This allows the user 70 to know that he or she can arrive at the destination 83 by the desired arrival time, and to know an estimate of how many people he or she will come into contact with at the transfer point. In the example shown in FIG. 5, the travel route R1 is displayed at the bottom of the screen of the communication device 60, but the travel route R1 does not have to be displayed. As another preferential suggestion method, the display of the travel route R2 may be made more prominent.

Next, an example of the operation of the transit route suggestion device will be described with reference to the flowchart in FIG. 6.

In step S101, the dispatch reception unit 211 receives a dispatch request from the user 70 input to the communication device 60. The process proceeds to step S103, where the route extraction unit 213 extracts multiple possible transfer route candidates if it is determined that a transfer of transportation means is necessary. The process proceeds to step S105, where the population density prediction unit 216 predicts the average population density at the transfer point by referring to the event information database 243 or the transportation congestion information database 244. The process proceeds to step S107, where the contact number prediction unit 217 predicts the number of contacts at the transfer point using the average population density predicted in step S105 and the time required for the transfer. The process proceeds to step S109, where the route suggestion unit 218 preferentially suggests to the user 70 the route predicted in step S107 to have a smaller number of contacts (see FIG. 5).

As an example of a method for predicting the number of contacts, a method using average population density and the time required for transfers has been described, but the method is not limited to this. The number of contacts prediction unit 217 may predict the number of contacts using the number of contacts when other users have used the transit route proposal system 10 in the past. Since the number of contacts when other users have used the transit route proposal system 10 in the past is stored in the customer database 242, the number of contacts prediction unit 217 can predict the number of contacts by referring to the customer database 242 and acquiring the number of contacts when other users have used the transit route proposal system 10 in the past. For example, if the date, day of the week, and time period are similar to those in the past history, the past number of contacts may be used as the number of contacts as is.

(Action and Effect)
As described above, the connecting route proposal device (management server 20) according to this embodiment provides the following advantageous effects.

The transit route suggestion device (management server 20) includes a controller 21 that suggests a route to a user's destination 83 based on a user request.
When a transfer of a transportation means is required, the controller 21 extracts a plurality of possible transfer route candidates. An example of a plurality of possible transfer route candidates is the travel route R1 and the travel route R2 shown in FIG. 3. The controller 21 predicts the number of contacts, which indicates the number of other users who come into contact with the user within a predetermined range at the transfer point in a unit time, based on predetermined information, for each of the extracted plurality of transfer route candidates. An example of a transfer point is station A 81 and station B 82 shown in FIG. 3. An example of a predetermined range of the user is within a circle with a radius of 1 m centered on the user 70 shown in FIG. 4. An example of a unit time is 15 minutes. The controller 21 proposes to the user, among the plurality of transfer route candidates, a transfer route candidate with a smaller number of contacts over a transfer route candidate with a larger number of contacts. An example of a method of preferentially proposing is to display the travel route R2 with a smaller number of contacts at the top of the screen than the travel route R1 with a larger number of contacts, as shown in FIG. 5. In this way, by suggesting to the user transit route candidates with fewer contact points over transit route candidates with a larger contact point, it is possible to reduce the number of contact points during transit.

The predetermined information includes the average population density of the transfer point and the time required for the transfer, or the number of contacts when other users have used a transfer in the past. The controller 21 predicts the number of contacts using the average population density and the time required for the transfer, or predicts the number of contacts using the number of contacts when other users have used a transfer in the past. This makes it possible to accurately predict the number of contacts at the transfer point.

The multiple transfer route candidates are routes that will arrive at the destination within the user's desired arrival time. This allows the user to select a route with fewer contacts at the transfer point from among the routes that will arrive at the destination within the desired time.

The transportation means includes a first transportation means and a second transportation means different from the first transportation means. The controller 21 determines that a transfer between transportation means is necessary when a transfer from the first transportation means to the second transportation means is necessary based on the user's location information and the user's destination. The second transportation means is a vehicle. The vehicle may be a taxi or a private car. The first transportation means is a train.

(Modification)
Next, a modified example of this embodiment will be described with reference to Fig. 7. In this modified example, the required ventilation volume at the transfer point is also taken into consideration. The processing of steps S201 to S205 shown in Fig. 7 is similar to the processing of steps S101 to S105 shown in Fig. 6, and therefore the description will be omitted.

In step S207, the route extraction unit 213 calculates the required ventilation volume at the transfer point. The definition of "required ventilation volume" in this embodiment is that of the Ministry of Health, Labor and Welfare. In this embodiment, the "required ventilation volume" is the ventilation volume required to avoid a "poorly ventilated enclosed space." According to the Ministry of Health, Labor and Welfare, in order to avoid a "poorly ventilated enclosed space," which is one of the risk factors for infectious diseases, the carbon dioxide content must be 1,000 parts per million or less (= 1,000 ppm or less), that is, the ventilation volume must be 30 ^m3 per person per hour. Please refer to the following link if necessary for this definition. https://www.mhlw.go.jp/content/10900000/000618969.pdf

The ventilation volume is calculated using Equation 3.

The CO2 concentration in the breath, the indoor concentration, and the outdoor concentration may be obtained from a transportation facility (e.g., a railroad company). If the calculated ventilation volume is 30 ^m3 /(h·person) or more, the route extraction unit 213 determines that the transfer point is possible to stay at (YES in step S209). If it is determined that both Station A 81 and Station B 82 shown in Fig. 3 are possible to stay at, the processes in steps S211 and S213 are the same as steps S107 and S109 shown in Fig. 6. If it is determined that either Station A 81 or Station B 82 is possible to stay at, the number of contacts is predicted in step S211, but the route proposed in step S213 is a route that passes through the transfer point determined to be possible to stay at.

On the other hand, if the calculated ventilation volume is less than 30 ^m3 /(h·person), the route extraction unit 213 determines that the user 70 cannot stay at that transfer point (NO in step S209). Note that NO in step S209 means that the user 70 cannot stay at all transfer points. In other words, the user 70 cannot stay at both station A 81 and station B 82, so the dispatch reception unit 211 notifies the user 70 that a taxi cannot be dispatched (step S215).

According to this modification, the controller 21 calculates the ventilation volume at the transfer point for each of the multiple transfer route candidates. If the calculated ventilation volume is equal to or greater than a predetermined standard, the controller 21 predicts the number of contacts. An example of the predetermined standard is 30 ^m3 /(h·person). If the calculated ventilation volume is less than the predetermined standard, the controller 21 excludes the transfer route candidate that passes through the target transfer point from the route to be proposed to the user. According to this modification, by also using the ventilation volume at the transfer point, places with poor ventilation, i.e., places considered to have a high risk of infection, can be excluded from the guidance, thereby reducing the user's risk of infection.

Each of the functions described in the above embodiments may be implemented by one or more processing circuits. Processing circuits include programmed processing devices, such as processors that include electrical circuitry. Processing circuits also include devices, such as application specific integrated circuits (ASICs) or circuit components, arranged to perform the described functions.

As described above, an embodiment of the present invention has been described, but the descriptions and drawings that form part of this disclosure should not be understood as limiting this invention. Various alternative embodiments, examples, and operating techniques will become apparent to those skilled in the art from this disclosure.

In the above embodiment, the transfer was described by taking a case of transferring from a train to a taxi, but the transfer is not limited to this. The present invention is applicable as long as there are multiple transfer locations, so it is also applicable to transfers from a bus to a taxi, and from a taxi to a taxi.

The transit route proposal device has been described as the management server 20, but is not limited to this. The transit route proposal device may be the communication device 60. When the transit route proposal device is the communication device 60, it is sufficient for the communication device 60 to obtain the necessary information from the management server 20.

10 Transit route proposal system 20 Management server 211 Vehicle dispatch reception unit 212 Allocation unit 213 Route extraction unit 214 Position information acquisition unit 215 Required time calculation unit 216 Population density prediction unit 217 Contact number prediction unit 218 Route proposal unit 241 Map database 242 Customer database 243 Event information database 244 Transportation congestion information database

Claims (6)

A transit route suggestion device comprising a controller that suggests a route to a destination of a user based on a request from the user,
The controller:
If a transfer is required, multiple transfer route candidates are extracted.
predicting a first number of users, which indicates the number of other users who stay within a predetermined range of the user at the transfer point for a unit time, for each of the extracted multiple transfer route candidates, based on predetermined information;
A transit route suggestion device, comprising: a transit route candidate having a smaller number of first passengers among the plurality of transit route candidates, the transit route candidate being suggested to the user in preference to a transit route candidate having a larger number of first passengers. A transit route suggestion device comprising a controller that suggests a route to a destination of a user based on a request from the user,
The controller:
If a transfer is required, multiple transfer route candidates are extracted.
predicting a first number of users, which indicates the number of other users who stay within a predetermined range of the user at the transfer point for a unit time, for each of the extracted multiple transfer route candidates, based on predetermined information;
Among the plurality of transit route candidates, a transit route candidate having a smaller number of first passengers is proposed to the user in preference to a transit route candidate having a larger number of first passengers ;
Calculating a ventilation volume at the transfer point for each of the plurality of transfer route candidates;
When the calculated ventilation volume is equal to or greater than a predetermined standard, predicting the first number of people ;
A transfer route suggestion device characterized in that, if the calculated ventilation volume is less than a predetermined standard, transfer route candidates that pass through the target transfer point are excluded from the routes suggested to the user. The predetermined information includes an average population density of the transfer point and a time required for the transfer, or a first number of other users who have used the transfer in the past;
The controller:
The transit route suggestion device according to claim 1 or 2 , characterized in that the first number of people is predicted using the average population density and the time required for the transfer, or the first number of people is predicted using the first number of people when the other users used a transfer in the past. 4. The transit route suggestion device according to claim 1, wherein the plurality of transit route candidates are routes that arrive at the destination within a desired arrival time of the user. the moving means includes a first moving means and a second moving means different from the first moving means,
The controller determines, when a transfer from the first transportation means to the second transportation means is necessary based on the user's location information and the user's destination, that a transfer of the transportation means is necessary;
5. The connecting route proposal device according to claim 1, wherein the second transportation means is a vehicle. A transit route suggestion method for a transit route suggestion device including a controller that suggests a route to a destination of a user based on a request from the user, the method comprising:
The controller:
If a transfer is required, multiple transfer route candidates are extracted.
predicting a first number of users, which indicates the number of other users who stay within a predetermined range of the user at the transfer point for a unit time, for each of the extracted multiple transfer route candidates, based on predetermined information;
Among the plurality of transit route candidates, a transit route candidate having a smaller number of first passengers is proposed to the user in preference to a transit route candidate having a larger number of first passengers ;
Calculating a ventilation volume at the transfer point for each of the plurality of transfer route candidates;
When the calculated ventilation volume is equal to or greater than a predetermined standard, predicting the first number of people ;
A method for suggesting a transfer route, comprising the steps of: excluding a transfer route candidate that passes through the transfer point in question from the routes to be suggested to the user if the calculated ventilation volume is less than a predetermined standard.

Images