Patent Description:
A technology for guiding a user to a meeting location where the user is to meet a vehicle is known from the prior art (Patent Document <NUM>).

XP93073196 "Directions service - Maps JavaScript API" discloses how to calculate directions by using the DirectionService object which communicates with Google Maps API Direction Service.

However, the invention disclosed in Patent Document <NUM> only presents the user with one route. The user cannot select a route other than the presented route, and thus has few options regarding movement.

In view of the problem described above, an object of the present invention is to provide a movement assistance device and a movement assistance method that present at least one route to a meeting location.

A movement assistance device according to the present invention comprises and is characterized by:.

With the present invention, it is possible to present at least one route to a meeting location to the user.

An embodiment of the present invention is described below with reference to the figures. In the descriptions of the figures, identical parts have been assigned the same reference numerals, and their descriptions have been omitted.

A configuration example of a movement assistance system <NUM> according to the present embodiment will be described with reference to <FIG>. As shown in <FIG>, the movement assistance system <NUM> includes a management server <NUM>, a communication network <NUM>, taxis <NUM> to <NUM>, a user <NUM>, and a communication device <NUM> in the possession of the user <NUM>. In <FIG>, there are three taxis, but no limitation is implied thereby. The movement assistance system <NUM> may include four or more taxis.

The management server <NUM> communicates with the taxis <NUM> to <NUM> and the communication device <NUM> via the communication network <NUM>. The management server <NUM> is a general-purpose computer equipped with a CPU (Central Processing Unit) <NUM>, a memory <NUM>, a communication I/F <NUM>, and a storage device <NUM>; these constituent elements are electrically connected via a bus, etc., not shown in the figure. The management server <NUM> is used in a dispatch service for the taxis <NUM> to <NUM>. Although the installation location of the management server <NUM> is not particularly limited, the management server <NUM> is installed, for example, in the control center of the business that operates the taxis <NUM> to <NUM>.

The CPU <NUM> reads various programs stored in the storage device <NUM>, etc., into the memory <NUM> and executes various instructions contained in the programs. The memory <NUM> is a storage medium such as a ROM (Read Only Memory), RAM (Random Access Memory), etc. The storage device <NUM> is a storage medium such as an HDD (Hard Disk Drive). Some (or all) of the movement assistance system <NUM>, including the functions of the management server <NUM> described below may be provided by means of an application (Software as a Service (SaaS), etc.) located on the communication network <NUM>.

The communication I/F <NUM> is implemented as hardware, such as a network adapter, various types of communication software, or a combination thereof, and is configured to realize wired or wireless communication via the communication network <NUM>, etc. Further, the communication I/F <NUM> functions as an input/output unit for sending and receiving data.

The communication network <NUM> may be configured by a wireless and/or wired method, and the communication network <NUM> may include the Internet. In this embodiment, the management server <NUM>, the taxis <NUM> to <NUM>, and the communication device <NUM> are connected to the communication network <NUM> by using a wireless communication method.

In this embodiment, the taxis <NUM> to <NUM> are described as autonomous driving vehicles without a driver. Therefore, the taxis <NUM> to <NUM> may be described as robot taxis or unmanned taxis. However, the taxis <NUM> to <NUM> are not limited to autonomous driving vehicles without drivers. The taxis <NUM> to <NUM> may be ordinary vehicles with drivers.

The user <NUM> requests (reserves) a taxi using the communication device <NUM>. A vehicle dispatch application (hereinafter referred to simply as a vehicle dispatch app) used for reserving taxis is installed in the communication device <NUM>, and the user <NUM> requests a taxi using the vehicle dispatch app.

Next, with reference to <FIG>, detailed configurations of the management server <NUM>, the taxi <NUM>, and the communication device <NUM> will be described. Although the taxis <NUM> and <NUM> have been omitted from <FIG>, the taxis <NUM> and <NUM> are configured in the same manner as the taxi <NUM>.

The communication device <NUM> comprises a communication I/F <NUM>, a vehicle dispatch app <NUM>, a GPS receiver <NUM>, and a display <NUM>. The communication I/F <NUM> has the same configuration as the communication I/F <NUM> (refer to <FIG>) and communicates with the management server <NUM> via the communication network <NUM>. The communication device <NUM> is a portable device such as a smartphone or a tablet. The communication device <NUM> may also be a wearable device. Although not shown in the figure, the communication device <NUM> comprises a CPU (controller), memory, storage device, etc., in the same manner as the management server <NUM>.

The vehicle dispatch app <NUM> is used for requesting a taxi, as described above. The vehicle dispatch app <NUM> functions as a user interface when the user <NUM> requests a taxi. The vehicle dispatch app <NUM> is realized by the CPU provided in the communication device <NUM> reading and executing a dedicated application program from a storage device provided in the communication device <NUM>. When the user <NUM> requests a taxi, the user <NUM> inputs a desired boarding location, boarding time, deboarding location, etc., into the vehicle dispatch app <NUM> to request a taxi. The vehicle dispatch app <NUM> transmits a dispatch request to the management server <NUM> in accordance with the input from the user <NUM>. Further, the communication device <NUM> displays on the display <NUM> various types of information (dispatch request receipt, scheduled arrival time, scheduled travel route, etc.) included in the signal returned from the management server <NUM> in response to the dispatch request. However, the method of realizing the vehicle dispatch app <NUM> is not limited in this way. For example, the communication device <NUM> may access a server that provides the functions of the vehicle dispatch app <NUM>, receive the functions provided, and display the results of executing the functions transmitted from the server in a browser.

The location information of the communication device <NUM> acquired by the GPS receiver <NUM> is transmitted to the management server <NUM> at any given time.

The taxi <NUM> is equipped with a communication I/F <NUM>, a vehicle ECU (Electronic Control Unit) <NUM>, and a GPS receiver <NUM>. The communication I/F <NUM> has the same configuration as the communication I/F <NUM> and the communication I/F <NUM>, and communicates with the management server <NUM> via the communication network <NUM>. The vehicle ECU <NUM> is a computer for controlling the taxi <NUM>. The vehicle ECU <NUM> controls various actuators (brake actuator, accelerator pedal actuator, steering actuator, etc.) based on the commands received from the management server <NUM>. The location information of the taxi <NUM> acquired by the GPS receiver <NUM> is transmitted to the management server <NUM> at any given time.

As shown in the block diagram of <FIG>, the CPU <NUM> (the controller) of the management server <NUM> is provided with, as examples of the plurality of functions, a vehicle dispatch acceptance unit <NUM>, an assignment unit <NUM>, a location information acquisition unit <NUM>, a required time calculation unit <NUM>, a walking route calculation unit <NUM>, a determination unit <NUM>, and a walking route setting unit <NUM>. As shown in <FIG>, a map database <NUM> and a client database <NUM> are stored in the storage device <NUM> of the management server <NUM>.

The map information required for route guidance, such as road information and facility information, is stored in the map database <NUM>. The map information includes the number of lanes on a road, road width information, and road undulation information. The map information also includes road signs indicating the speed limit, one-way streets, etc., as well as road markings indicating pedestrian crossings, lane markings, etc. The map information may also include information related to road structures (for example, traffic signals and telephone poles), buildings, and other facilities.

The client database <NUM> stores account information, such as the ID of the user <NUM>, taxi usage history, and attributes of the user <NUM>.

The dispatch acceptance unit <NUM> accepts a dispatch request from the user <NUM> entered into the communication device <NUM>. The dispatch acceptance unit <NUM> has the function of notifying the communication device <NUM> of the acceptance of the dispatch request from the user <NUM>, as well as of the scheduled arrival time to the boarding location, the scheduled travel route to the boarding location, etc..

The assignment unit <NUM> assigns a suitable taxi from among the plurality of taxis <NUM> to <NUM> (refer to <FIG>) based on the accepted dispatch request. For example, for reasons of efficiency, the dispatch acceptance unit <NUM> can assign the unoccupied taxi that, of the plurality of taxis <NUM> to <NUM>, is closest to the boarding location desired by the user <NUM>. In the present embodiment, it is assumed that the taxi <NUM> has been assigned.

The assignment unit <NUM> also sets a travel route from the current location of the taxi <NUM> to the boarding location desired by the user <NUM> by referencing the map database <NUM> and sends an instruction to the taxi <NUM> to travel to the boarding location desired by the user <NUM> via the set travel route. The travel route calculated by the assignment unit <NUM> is, for example, the route via which the boarding location desired by the user <NUM> can be reached from the current location of the taxi <NUM> in the shortest amount of time. The assignment unit <NUM> outputs the set travel route to the required time calculation unit <NUM>.

The location information acquisition unit <NUM> acquires the location information of the user <NUM> from the communication device <NUM> and acquires location information of the taxi <NUM> from the taxi <NUM>. The location information of the user <NUM> means the location information of the communication device <NUM> in the possession of the user <NUM>. The location information acquisition unit <NUM> outputs the acquired location information to the required time calculation unit <NUM>.

The required time calculation unit <NUM> (the first required time calculation unit, the second required time calculation unit) uses the travel route acquired from the assignment unit <NUM> and the location information of the taxi <NUM> acquired from the location information acquisition unit <NUM> to calculate a first required time or time required for the taxi <NUM> to arrive at the boarding location desired by the user <NUM> from its current location The required time calculation unit <NUM> outputs this calculated first required time to the determination unit <NUM>.

The walking route calculation unit <NUM> uses the map database <NUM> and the location information of the user <NUM> acquired from the location information acquisition unit <NUM> to calculate walking routes. In the present embodiment, a walking route is a route that the user <NUM> can take on foot from the current location of the user <NUM> to the boarding location. The walking route calculation unit <NUM> calculates a plurality of walking routes to the boarding location. The required time calculation unit <NUM> also calculates a second required time, which is the time required for the user <NUM> to arrive at the boarding location from his or her current location, for each of the plurality of walking routes calculated by the walking route calculation unit <NUM>. The required time calculation unit <NUM> outputs these calculated second required times to the determination unit <NUM>. Each second required time is associated with the corresponding walking route.

The determination unit <NUM> determines whether the user <NUM> can be on time to meet the taxi <NUM> using the first required time and the second required times obtained from the required time calculation unit <NUM>. For example, if a second required time is shorter than the first required time, the determination unit <NUM> determines that the user <NUM> can be on time to meet the taxi <NUM>. Further, if a second required time and the first required time are the same, the determination unit <NUM> determines that the user <NUM> can be on time to meet the taxi <NUM>. Here, "a second required time and the first required time are the same" does not imply an exact equivalence. "A second required time and the first required time are the same" means that the times are essentially the same (i.e., approximately the same) and that a difference of several seconds is negligible.

In the present embodiment, "the user <NUM> can be on time to meet the taxi <NUM>" means that the user <NUM> can arrive at the boarding location ahead of the taxi <NUM>. Alternatively, "the user <NUM> can be on time to meet the taxi <NUM>" can mean that the user <NUM> and the taxi <NUM> may arrive at the boarding location at the same time (or approximately the same time).

If it is determined that the user <NUM> can be on time to meet the taxi <NUM>, the determination unit <NUM> outputs the walking routes associated with the second required times used to arrive at this determination to the walking route setting unit <NUM>.

The walking route setting unit <NUM> sets the walking routes acquired from the determination unit <NUM> as the walking routes to be presented to the user <NUM> and transmits a signal indicating the set walking routes to the communication device <NUM> in the possession of the user <NUM> via the communication I/F <NUM>.

Details of the walking route will now be described with reference to <FIG>.

It is assumed that the user <NUM> shown in <FIG> requests a taxi using the vehicle dispatch app <NUM>. Reference numeral <NUM> in <FIG> indicates the boarding location desired by the user <NUM>. That is, reference numeral <NUM> indicates the location where the user <NUM> is to meet the taxi <NUM>. Reference numeral <NUM> is hereafter designated as meeting location <NUM>. The taxi <NUM> travels to the meeting location <NUM> in order to board the user <NUM> based on a command received from the management server <NUM>. The taxi <NUM> is omitted in <FIG>.

As described above, the required time calculation unit <NUM> uses the travel route acquired from the assignment unit <NUM> and the location information of the taxi <NUM> acquired from the location information acquisition unit <NUM> to calculate a first required time, which is the time required for the taxi <NUM> to arrive at the meeting location <NUM> from its current location. In the following description, it is assumed that the first required time has been calculated as <NUM> minutes.

As shown in <FIG>, the walking route calculation unit <NUM> uses the map database <NUM> and the location information of the user <NUM> acquired from the location information acquisition unit <NUM> to calculate walking routes R1 to R4. Walking routes R1 to R4 are routes that the user <NUM> can take on foot from the current location of the user <NUM> to the meeting location <NUM>.

The required time calculation unit <NUM> calculates a second required time, which is the time required to arrive at the meeting location <NUM> from the current location of the user <NUM>, for each of the walking routes R1 to R4 calculated by the walking route calculation unit <NUM>. It is assumed only in <FIG> that the second required times for traversing the walking routes are calculated as <NUM> minutes for the walking route R1, <NUM> minutes for the walking route R2, <NUM> minutes for the walking route R3, and <NUM> minutes for the walking route R4.

The determination unit <NUM> determines whether the user <NUM> can be on time to meet the taxi <NUM> using the first required time (<NUM> minutes) and the second required times (R1: <NUM> minutes, R2: <NUM> minutes, R3: <NUM> minutes, R4: <NUM> minutes) acquired from the required time calculation unit <NUM>. Since the taxi <NUM> will arrive at the meeting location <NUM> in <NUM> minutes, if the user <NUM> can arrive at the meeting location <NUM> within <NUM> minutes, the user can meet the taxi <NUM> on time.

Thus, the determination unit <NUM> determines whether there is a walking route via which the meeting location <NUM> can be reached within the first required time. For example, the determination unit <NUM> compares the first required time and a second required time, and if this second required time is shorter than the first required time, determines that the walking route associated with this second required time is a walking route via which the meeting location <NUM> can be reached within the first required time.

In <FIG>, since the second required times (R1: <NUM> minutes, R2: <NUM> minutes, R3: <NUM> minutes) associated with the walking routes R1 to R3 are shorter than the first required time (<NUM> minutes), the determination unit <NUM> determines that the walking routes R1 to R3 are the walking routes via which the meeting location <NUM> can be reached within the first required time. Since the second required time (<NUM> minutes) associated with the walking route R4 is longer than the first required time (<NUM> minutes), on the other hand, the determination unit <NUM> determines that the walking route R4 cannot be used to arrive at the meeting location <NUM> within the first required time. The determination unit <NUM> outputs the walking routes R1 to R3 (the walking routes via which the user <NUM> can meet the taxi <NUM> on time) to the walking route setting unit <NUM>. Walking route R4, on the other hand, is deleted since it cannot be used to arrive at the meeting location <NUM> within the first required time.

The walking route setting unit <NUM> then sets the walking routes R1 to R3 acquired from the determination unit <NUM> as the walking routes to be presented to the user <NUM> and transmits a signal indicating the set walking routes R1 to R3 to the communication device <NUM> in the possession of the user <NUM> via the communication I/F <NUM>.

As shown in <FIG>, walking routes R1 to R3 acquired from the management server <NUM> are displayed on the display <NUM> of the communication device <NUM>. Regardless of which walking route of the walking routes R1 to R3 the user <NUM> selects, the user <NUM> can be on time to meet the taxi <NUM>. By means of the present embodiment, a plurality of the walking routes R1 to R3 can be presented to the user <NUM> via which the taxi <NUM> can be met on time; thus, the user <NUM> can select his or her preferred route from the plurality of the walking routes R1 to R3. This increases the number of options that the user <NUM> can choose from when he/she departs for the meeting location <NUM>. When the user <NUM> selects his/her preferred route, the user is guided along this route to the meeting location <NUM>, as with a well-known navigation system.

An example of the operation of the movement assistance system <NUM> will now be explained with reference to the sequence charts of <FIG>.

In Step S101, the user <NUM> requests a taxi using the vehicle dispatch app <NUM>. The process proceeds to Step S103, in which the dispatch acceptance unit <NUM> accepts the dispatch request of the user <NUM>. The process proceeds to Step S105, in which the assignment unit <NUM> assigns an appropriate taxi from among the plurality of taxis <NUM> to <NUM> (refer to <FIG>) based on the accepted dispatch request. The process proceeds to Step S107, in which the assignment unit <NUM> references the map database <NUM> and sets the travel route from the current location of the taxi <NUM> to the boarding location desired by the user <NUM> (meeting location <NUM>).

The process proceeds to Step S109, in which the management server <NUM> transmits the set travel route to the taxi <NUM>. The process then proceeds to Step S111, in which the taxi <NUM> travels to the meeting location <NUM> desired by the user <NUM> via the acquired travel route.

In Step S113, the communication device <NUM> transmits the location information of the communication device <NUM> acquired by the GPS receiver <NUM> to the management server <NUM>. In Step S115, the taxi <NUM> transmits the location information of the taxi <NUM> acquired by the GPS receiver <NUM> to the management server <NUM>. In Step S117, the management server <NUM> receives the location information transmitted from the communication device <NUM> and the taxi <NUM>. The process of Step S115 is repeated until the taxi <NUM> arrives at the meeting location <NUM> (Step S119).

The process proceeds to Step S121, in which the required time calculation unit <NUM> calculates the first required time, i.e., the time required for the taxi <NUM> to arrive at the meeting location <NUM> from its current location. The process proceeds to Step S123, in which the walking route calculation unit <NUM> calculates the walking routes R1 to R4 (refer to <FIG>) using the map database <NUM> and the location information of the user <NUM> acquired in Step S117.

The process proceeds to Step S125, in which the determination unit <NUM> determines whether any of the walking routes R1 to R4 calculated in Step S123 cannot be used to arrive at the meeting location <NUM> within the first required time. If there is a walking route R4, as is shown in <FIG>, via which it is not possible to arrive at the meeting location <NUM> within the first required time (YES in Step S125), the process proceeds to Step S127, and the walking route R4 is deleted. If, on the other hand, there are the walking routes R1 to R3 via which the meeting location <NUM> can be reached within the first required time (NO in Step S125), the walking route setting unit <NUM> sets the walking routes R1 to R3 as the walking routes to be presented to the user <NUM> (Step S129). The process proceeds to Step S131, in which the walking route setting unit <NUM> transmits a signal indicating the set walking routes R1 to R3 to the communication device <NUM> in the possession of the user <NUM> via the communication I/F <NUM>.

The process proceeds to Step S133, in which the communication device <NUM> receives a signal indicating the walking routes R1 to R3 transmitted from the management server <NUM>. The process proceeds to Step S135, in which walking routes R1 to R3 are displayed on the display <NUM>, as shown in <FIG>. The process of Step S113 is repeated until the user <NUM> arrives at the meeting location <NUM> (Step S137).

As described above, the following actions and effects can be achieved by means of the management server <NUM> according to the present embodiment.

The management server <NUM> is equipped with the location information acquisition unit <NUM>, the first required time calculation unit (the required time calculation unit <NUM>), the route calculation unit (the walking route calculation unit <NUM>), the second required time calculation unit (the required time calculation unit <NUM>), the determination unit <NUM>, and the output unit (the communication I/F <NUM>).

The location information acquisition unit <NUM> acquires the location information of the communication device <NUM> in the possession of the user <NUM> as well as the location information of the taxi <NUM> dispatched in accordance with the dispatch request of the user <NUM>. The first required time calculation unit calculates, based on the location information of the taxi <NUM>, the first required time or time required for the taxi <NUM> to arrive at the meeting location <NUM> where the user <NUM> who requested the dispatch is to board.

The route calculation unit calculates, based on the location information of the communication device <NUM>, a plurality of routes from the current location of the user <NUM> to the meeting location <NUM>. The second required time calculation unit calculates a second required time, which is the time required to arrive at the meeting location from the current location of the user, for each of the plurality of routes calculated by the route calculation unit.

If a second required time is the same as or shorter than the first required time, the determination unit <NUM> determines that the route associated with the second required time is a route via which the taxi <NUM> could be met on time. The output unit causes the communication device <NUM> to output information indicating the route or routes determined by the determination unit <NUM> to be thee route or routes via which the taxi <NUM> could be met on time.

As a result, as shown in <FIG>, the user <NUM> can be presented with the plurality of the walking routes R1 to R3 via which the taxi <NUM> could be met on time, thereby allowing the user <NUM> to select a preferred route from the plurality of the walking routes R1 to R3. This increases the number of options that the user <NUM> can choose from when the user departs for the meeting location <NUM>.

The first modified example of the present embodiment will now be described with reference to <FIG>.

As shown in <FIG>, when the management server <NUM> transmits a signal indicating the walking routes R1 to R4 to the communication device <NUM>, the management server may also transmit a signal indicating the second required times associated with the walking routes R1 to R4 to the communication device <NUM>.

As a result, as shown in <FIG>, the walking routes R1 to R4 acquired from the management server <NUM> and the second required times associated with the walking routes R1 to R4 are displayed on the display <NUM> of the communication device <NUM>. In the following description, it is assumed that the second required times for traversing the walking routes have been calculated as <NUM> minutes for the walking route R1, <NUM> minutes for the walking route R2, <NUM> minutes for the walking route R3, and <NUM> minutes for the walking route R4.

In the same manner as the example shown in <FIG>, the walking routes R1 to R3 are walking routes via which the meeting location <NUM> can be reached within the first required time. Further, in <FIG> onwards, walking route R4 is also a walking route via which the meeting location <NUM> can be reached within the first required time. Because the second required time (<NUM> minutes) associated with the walking route R4 is the same as the first required time (<NUM> minutes), the determination unit <NUM> determines that walking route R4 is a walking route via which the meeting location <NUM> can be reached within the first required time.

As shown in <FIG>, because walking routes R1 to R4 and the second required times associated with the walking routes R1 to R4 are displayed on the display <NUM>, the user <NUM>, when choosing between the walking routes, can ascertain at a glance the associated walking times. The user <NUM> can select his or her preferred route from the walking routes R1 to R4 in consideration of the walking time.

The second modified example of the present embodiment will now be described with reference to <FIG>.

In the second modified example, the required time calculation unit <NUM> calculates a margin time. The margin time is the time in minutes that indicates how much longer it will take the taxi <NUM> to arrive at the meeting location <NUM> after the user <NUM> has arrived at the meeting location <NUM>. The margin time is calculated by subtracting the second required time from the first required time (<NUM> minutes). Since the second required times to traverse the walking routes are <NUM> minutes for the walking route R1, <NUM> minutes for the walking route R2, <NUM> minutes for the walking route R3, and <NUM> minutes for the walking route R4, as shown in <FIG>, the margin times associated with traversing the walking routes are <NUM> minutes for the walking route R1, <NUM> minutes for the walking route R2, <NUM> minute for the walking route R3, and <NUM> minutes for the walking route R4. The margin times are associated with the corresponding walking routes in the same manner as are the second required times.

The longer the margin time, the less hurried the pace of the user <NUM> as he/she moves toward the meeting location <NUM>. The shorter the margin time, on the other hand, the less extra time available to the user <NUM>. For example, if the margin time is <NUM> minutes, as is the case with the walking route R4, the user <NUM> understands that there is no time to waste; the user <NUM> may therefore avoid selecting the walking route R4, or may decide to select walking route R4 and set out immediately, moving quickly, not stopping along the way, heeding the time, etc., as he/she moves toward the meeting location <NUM>.

In the second modified example, when the management server <NUM> transmits a signal indicating the walking routes R1 to R4 to the communication device <NUM>, the management server also transmits a signal indicating the margin times associated with the walking routes R1 to R4 to the communication device <NUM>.

As a result, as shown in <FIG>, the walking routes R1 to R4 acquired from the management server <NUM> and the margin times associated with the walking routes R1 to R4 are displayed on the display <NUM> of the communication device <NUM>. The display allows the user <NUM> to ascertain at a glance the margin time for each walking route that may be selected. Thus, the user <NUM> can base their selection of walking routes R1 to R4 on the margin time.

The third modified example of the present embodiment will now be described with reference to <FIG>.

When the user <NUM> departs for the meeting location <NUM>, the user may be able to take side roads, branch roads, etc., depending the condition of the roads. Reference numerals <NUM>, <NUM> shown in <FIG> are arrows that indicate the directions that can be taken at side roads and branch roads. Consider the walking routes R1 and R3, for example. At the side and branch roads between the walking routes R1 and R3, arrow <NUM> indicates that it would be possible to take the walking route R1 to the walking route R3, or the walking route R3 to the walking route R1. More specifically, arrow <NUM> indicates that whether the user were to take the walking route R1 to the walking route R3 or the walking route R3 to the walking route R1, it would be possible to meet the taxi <NUM> on time.

In contrast, arrows <NUM> indicate that it is possible to take the walking route R3 to the walking route R1, but not the walking route R1 to the walking route R3. More specifically, arrows <NUM> indicate that if the user were to take the walking route R3 to the walking route R1, it would be possible to meet the taxi <NUM> on time, but if the user were to take the walking route R1 to the walking route R3, it would not be possible to meet the taxi <NUM> on time.

The same applies to arrows <NUM>, <NUM> for the side roads and branch roads between the walking route R1 and the walking route R2, as well as to arrows <NUM>, <NUM> for the side roads and branch roads between the walking route R2 and the walking route R4; thus, their descriptions have been omitted.

In the third modified example, when transmitting a signal indicating the walking routes R1 to R4 to the communication device <NUM>, the management server <NUM> also transmits a signal indicating the arrows that indicate the directions that can be taken at the side roads and branch roads.

As a result, as shown in <FIG>, the walking routes R1 to R4 acquired from the management server <NUM> and arrows <NUM>, <NUM> that indicate the directions that can be taken at the side roads and branch roads are displayed on the display <NUM> of the communication device <NUM>. The display allows the user <NUM> to ascertain at a glance the direction to take at the side roads and branch roads, and how to proceed on the preferred side roads and branch roads. This gives the user more movement-related options when the user <NUM> departs for the meeting location <NUM>.

The fourth modified example of the present embodiment will now be described with reference to <FIG>.

Roads available to the user <NUM> may be hilly, have stairs, pedestrian crossing bridges, etc. Hills, stairs, pedestrian crossing bridges, etc., are elements that impose a greater burden of movement compared with flat routes. Depending on the user <NUM>, there may be a need to avoid traversing hills, stairs, pedestrian crossing bridges, etc. As an example, such a need may arise for a user <NUM> who uses a wheelchair. In Fourth Modified example, if a walking route set by the walking route setting unit <NUM> includes hills, stairs, pedestrian crossing bridges, etc., when the management server <NUM> transmits a signal indicating the walking routes R1 to R4 to the communication device <NUM>, a signal indicating that the presence of the hills, stairs, pedestrian crossing bridges, etc., is also transmitted to the communication device <NUM>.

The particulars will be described with reference to <FIG>. It is assumed that there are stairs on the walking route R4 shown in <FIG>. In this case, when transmitting the signal indicating the walking routes R1 to R4 to the communication device <NUM>, the management server <NUM> also transmits a signal indicating that there are stairs on the walking route R4 to the communication device <NUM>. When the communication device <NUM> receives these signals, as shown in <FIG>, the walking routes R1 to R3 are displayed as ordinary lines, whereas the walking route R4 is displayed as a dotted line on the display <NUM>. If it is set in advance, as a display rule, that walking routes indicated by dotted lines mean that there are stairs, the user <NUM> can ascertain at a glance that there are stairs on the walking route R4. As described above, in the case that the user <NUM> uses a wheelchair, the user <NUM> can avoid stairs by selecting the walking routes R1 to R3.

The walking route on which there are stairs is indicated by the dotted line in <FIG>, but the display example is not limited in this way. Walking routes on which there are stairs may be displayed with a thick line or a one-dotted chain line. Walking routes on which there are stairs and flat walking routes may be distinguished by color. As an example, walking routes with stairs may be displayed in red, while flat walking routes are displayed in green. Further, the display may be different for hills, stairs, and pedestrian crossing bridges.

Further, the management server <NUM> (the determination unit <NUM>) can refer to the map database <NUM> in order to determines whether there are hills, stairs, pedestrian crossing bridges, etc., on the walking routes R1 to R4. The means of transportation of the user <NUM> includes walking, use of a wheelchair, bicycling, and running (running).

The management server <NUM> may compare the heights of the walking routes R1 to R4 (plurality of routes) with respect to a horizontal plane in order to determine if there is an element that imposes a high burden of movement. Specifically, the management server <NUM> may determine that there is an element that imposes a high burden of movement when the height of a certain route (the walking route R4 of <FIG>) with respect to a horizontal plane is higher or lower than that of another route (the walking routes R1 to R3 of <FIG>).

The fifth modified example of the present embodiment will now be described with reference to <FIG>.

In the fourth modified example described above, if there are stairs on the walking route R4, the walking route R4 is displayed using a dotted line. The method of presenting to the user <NUM> that the walking route R4 has stairs is not limited in this way. As shown in <FIG>, a balloon indicating the walking route R4 may display the words "with stairs. " By use of this display, the user <NUM> can ascertain at a glance that there are stairs on the walking route R4.

As an operation example of the management server <NUM> in the fifth modified example, when transmitting the signal indicating the walking routes R1 to R4 to the communication device <NUM>, the management server <NUM> also transmits a signal (signals for displaying a balloon) indicating that there are stairs on the walking route R4 to the communication device <NUM>.

The sixth modified example of the present embodiment will now be described with reference to <FIG>.

Roads available to the user <NUM> include sidewalks, roads in parks, station yards, etc. There are cases in which stores such as convenience stores are present, or events such as product exhibits and festivals taking place in such areas. For example, as shown in <FIG>, it is assumed that a convenience store is present on the walking route R3, that a product exhibition is taking place on the walking route R1, and that a festival is being held on the walking route R4.

In this case, when transmitting the signal indicating the walking routes R1 to R4 to the communication device <NUM>, the management server <NUM> also transmits a signal indicating store information and event information on the walking routes R1 to R4 to the communication device <NUM>. By means of the communication device <NUM> receiving these signals, as shown in <FIG>, balloons indicating that a convenience store is present on the walking route R3, that a product exhibition is taking place on the walking route R1, and that a festival is being held on the walking route R4, are displayed on the display <NUM>.

Users who like to purchase local specialty goods at product exhibitions can satisfy their needs by selecting walking route R1. Alternatively, by selecting walking route R4, users who like to see festivals would be able to do so as they travel toward the meeting location <NUM>. In this manner, when a plurality of the walking routes R1 to R4 is displayed, store and event information associated with these walking routes can also be displayed, thereby providing the user <NUM> with a wide range of options.

The management server <NUM> (information acquisition unit) can obtain information pertaining to stores, such as convenience stores, by referring to the map database <NUM>. Further, with regard to event information such as product exhibitions and festivals, the management server <NUM> (information acquisition unit) can use the location information of the user <NUM> to search for and obtain event information on the Internet for the area where the user <NUM> is located. Both store information and event information may be displayed, as shown in <FIG>, or only one may be displayed.

Further, when store information and event information is displayed on the walking routes using balloons, the margin time described above may also be displayed, as shown in <FIG>. This makes it easier for the user <NUM> to arrive at such decisions as, "I can't stop at the convenience store on the walking route R3 since it only gives me one extra minute, but I can stop at the product exhibition on the walking route R1 since it gives me three extra minutes. " Note that. As an operation example of the management server <NUM> in this case, when transmitting the signal indicating the walking routes R1 to R4 to the communication device <NUM>, the management server <NUM> also transmits a signal indicating store information and event information associated with the walking routes R1 to R4, as well as the signal indicating the margin times associated with the walking routes R1 to R4, to the communication device <NUM>.

In the display example of <FIG>, a festival is being held along walking route R4, but the margin time here is <NUM> minutes, so that even if the user <NUM> were to select walking route R4 to see the festival, there would be no time to do so. Therefore, as shown in <FIG>, if the margin time is shorter than a prescribed time, the display may exclude the display of store and event information on the walking route. In other words, store and event information on the walking route may be displayed only when the margin time is greater than or equal to a prescribed time. As an operation example of the management server <NUM> in this case, when transmitting a signal indicating the walking routes R1 to R4 to the communication device <NUM>, the management server <NUM> also transmits a signal indicating store and event information on the walking routes R1 to R4, as well as a signal indicating the margin times associated with the walking routes R1 to R4 to the communication device <NUM>. The management server <NUM> also transmits to the communication device <NUM> a signal indicating whether the margin time is shorter than the prescribed time to the communication device <NUM>. The prescribed time is not particularly limited, but may be <NUM> seconds, for example.

Each of the functions described in the embodiments above may be implemented by means of one or more processing circuits. The processing circuits include programmed processing devices, such as processing devices including electronic circuits. The processing circuits also include such devices as application-specific integrated circuits (ASIC) and electronic components arranged to execute the described functions.

Embodiments of the present invention have been described above, but the descriptions and figures that form part of this disclosure should not be understood as limiting the present invention. From this disclosure, various alternative embodiments, examples, and operating techniques should be apparent to those skilled in the art.

The walking routes may be set from time to time in accordance with the current location of the user <NUM>, rather than being established once in a final form. As shown in <FIG>, the current location of the user <NUM> changes from one time to the next as the user advances from the state at time T to the state at time T+<NUM>. The walking route setting unit <NUM> may set the walking route in accordance with the current location of the user <NUM>, which changes from time to time. The user <NUM> can thereby select a walking route that is different from the walking route that was initially selected.

Further, in the embodiment described above, the entity that transmits to the communication device <NUM> prescribed signals for causing the communication device <NUM> to output (display) the plurality of walking routes, the margin times, etc., is described as the management server <NUM>, but no limitation is implied thereby. The entity that transmits to the communication device <NUM> prescribed signals for causing the communication device <NUM> to output the plurality of walking routes, the margin times, etc., may be the communication device <NUM> itself or the taxi <NUM>.

When the communication device <NUM> is set as the entity that transmits to the communication device <NUM> prescribed signals for causing the communication device <NUM> to output the plurality of walking routes, the margin times, etc., as shown in <FIG>, a computer <NUM> installed in the communication device <NUM> may function as a location information acquisition unit <NUM>, a required time calculation unit <NUM>, a walking route calculation unit <NUM>, a determination unit <NUM>, and a walking route setting unit <NUM>. These functions of the location information acquisition unit <NUM>, the required time calculation unit <NUM>, the walking route calculation unit <NUM>, the determination unit <NUM>, and the walking route setting unit <NUM> are the same as those of the location information acquisition unit <NUM>, the required time calculation unit <NUM>, the walking route calculation unit <NUM>, the determination unit <NUM>, and the walking route setting unit <NUM> shown in <FIG>. In this case, the communication device <NUM> can be said to be a device that outputs to the communication device <NUM> prescribed signals for causing the communication device <NUM> to output the plurality of walking routes, the margin times, etc..

Claim 1:
A movement assistance device characterized by:
a location information acquisition unit (<NUM>) configured to acquire location information of a communication device possessed by a user and location information of a vehicle dispatched in accordance with a dispatch request by the user;
a first required time calculation unit (<NUM>) configured to calculate, based on location information of the vehicle, a first required time until the vehicle arrives at a meeting location where the user who made the dispatch request is to board the vehicle;
a route calculation unit (<NUM>) configured to calculate, based on the location information of the communication device, a plurality of routes from a current location of the user to the meeting location;
a second required time calculation unit (<NUM>) configured to calculate a second required time from the current location of the user to the meeting location, for each of the plurality of routes calculated by the route calculation unit (<NUM>), the plurality of routes including a first route and a second route as routes in which the vehicle could be met on time;
a determination unit (<NUM>) configured to determine the route associated with the second required time is a route in which the vehicle could be met on time when the second required time is the same as or shorter than the first required time; and
an output unit (<NUM>) configured to cause the communication device to output information indicating at least one of the first route and the second route,
upon the determination unit (<NUM>) determining a third route connects the first route and the second route, the output unit (<NUM>) being further configured to output a travel direction from the first route to the second route via the third route, and a travel direction from the second route to the first route via the third route in different formats depending on whether the vehicle could be met on time.