WO2012020445A1 - Vehicle-mounted information device - Google Patents

Abstract

A vehicle-mounted information device is provided with a map data management unit (7) which acquires, from map data, the coordinates of a stop-off point at which a vehicle traveling on the basis of a set route stops off, a history data management unit (8) which stores, in a history table, and manages the coordinates of the stop-off point acquired by the map data management unit (7), and a via point setting unit (6) which, when a route is set, reads the coordinates of the stop-off point acquired in the same route as the set route from the history table and sets the coordinates as a via point.

Description

Car information system

The present invention relates to an in-vehicle information device that is mounted on a vehicle and processes information.

Conventionally, in order to be able to easily search a place visited previously, there is known a technique capable of quickly searching for a destination by obtaining position information and date / time information of a parked or stopped place ( For example, see Patent Document 1).

In the technique disclosed in Patent Document 1, there is a problem that it takes time to draw a route, for example, a user needs to set a destination after performing a search every time, even if it is a parking spot that stops many times. is there.

The present invention has been made to solve such a problem, and it is an object of the present invention to provide an in-vehicle information device that can draw a route through a point desired by a driver with little effort.

JP 2002-340593 A

The in-vehicle information device according to the present invention is acquired by the map data management unit that acquires from the map data the coordinates of the stop point that is the point where the vehicle that travels based on the set route stops, and the map data management unit. The history data management unit that stores and manages the coordinates of the stop points in the history table, and when a route is set, the coordinates of the stop points acquired by the same route as the set route are read from the history table and passed And a waypoint setting unit for setting the ground.

According to the in-vehicle information device according to the present invention, it is possible to draw a route via a point desired by the driver with little effort.

It is a block diagram which shows the structure of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a figure which shows the example of the parking / route log | history table used with the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a figure which shows the example of the plant | facility detailed information table used with the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a figure which shows the example of the setting information used with the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a flowchart for demonstrating the operation | movement at the time of parking of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a flowchart for demonstrating the operation | movement at the time of the route setting of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a flowchart for demonstrating operation | movement when a user sets a waypoint in the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a flowchart for demonstrating the operation | movement which selects the waypoint setting of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a figure which shows the example of a screen for performing trigger input in the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a flowchart for demonstrating the operation | movement at the time of setting a waypoint from the parking and the waypoint history of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a figure which shows the example of a screen for performing the waypoint selection operation from all the candidates in the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a flowchart for demonstrating operation | movement when the user of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention instruct | indicates the spot set to a stopover. It is a figure which shows the example of a screen for performing the waypoint selection operation from the narrowed-down candidate in the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a flowchart for demonstrating operation | movement when the system of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention sets to a stopover. It is a flowchart for demonstrating operation | movement when a user sets the number of waypoint settings in the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a figure which shows the example of the condition setting screen in which the number of waypoint settings was shown in the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a flowchart for demonstrating operation | movement from narrowing down the candidate of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention, and waypoint setting. It is a flowchart for demonstrating the operation | movement from narrowing down a candidate by the distance of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention to a waypoint setting. It is a flowchart for demonstrating operation | movement from narrowing down of the candidate by the frequency | count of parking of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention to waypoint setting. It is a flowchart for demonstrating operation | movement from narrowing down the candidate by the date by the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention, and waypoint setting. It is a flowchart for demonstrating operation | movement from narrowing down of a candidate by the waypoint setting by the parking spot of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention being unset. It is a flowchart for demonstrating the operation | movement from narrowing down of the candidate by the similar genre by the in-vehicle information device concerning Embodiment 1 of this invention to waypoint setting. It is a flowchart for demonstrating operation | movement from narrowing down of a candidate by the similar information of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention to a waypoint setting. It is a flowchart for demonstrating operation | movement from narrowing down of a candidate by the distance between the points of the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention to waypoint setting. It is a flowchart for demonstrating the operation | movement of the inquiry about whether to set to a waypoint in the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a figure which shows the example of a screen of the inquiry about whether to set to a transit place in the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a flowchart for demonstrating the operation | movement which automatically turns off a waypoint setting function in the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a flowchart for demonstrating the operation | movement which memorize | stores parking information, when the own vehicle stops in the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention. It is a flowchart for demonstrating the operation | movement which memorize | stores parking information, when an engine turns off in the vehicle-mounted information apparatus which concerns on Embodiment 1 of this invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
Embodiment 1 FIG.
1 is a block diagram showing a configuration of an in-vehicle information device according to Embodiment 1 of the present invention. This in-vehicle information device includes an information acquisition unit 2, a vehicle state detection unit 3, an input unit 4, an output unit 5, a waypoint setting unit 6, a map data management unit 7, a history data management unit 8, a setting information management unit 9, and a comparison A determination unit 10 and a control unit 11 are provided.

The information acquisition unit 2 acquires information at the time of route setting or information at the time of parking, such as route setting date and time or driver information indicating a driver at the time of route setting. The information at the time of route setting or the information at the time of parking includes the position information of the own vehicle received by a GPS (Global Positioning System) receiver. The vehicle state detection unit 3 acquires the state of the host vehicle, detects whether the host vehicle is in a stopped state, and detects whether the engine is turned off. The input unit 4 acquires input information input by the user from an input device (not shown) and sends the input information to the control unit 11. In addition, the control unit 11 uses the current position of the vehicle acquired by the information acquisition unit 2, the destination input by the input unit 4, and the map data acquired by the map data management unit 7, to the destination. Set the route.

The output unit 5 outputs information to be presented to the user, such as an inquiry screen or a transit point candidate selection screen, in response to an instruction from the control unit 11. The waypoint setting unit 6 sets a waypoint according to an instruction from the control unit 11. The map data management unit 7 manages the map data 12. The map data 12 includes coordinates of each point, road information, address, facility name, facility genre name, and facility meta genre name. The map data 12 managed by the map data management unit 7 is read by the control unit 11.

The history data management unit 8 includes a parking / route history table (history table) 13 for storing history information set at parking points and via points, and a facility detailed information table (facility) for storing detailed information on facilities at the parking / route points. (Information table) 14, temporary management data 15 for storing temporary data, and negative count data 17 indicating the number of times the driver has answered negative in response to an inquiry as to whether to set a transit point. The parking / route history table 13, the facility detailed information table 14, the temporary management data 15, and the negative count data 17 managed by the history data management unit 8 are accessed by the control unit 11.

The setting information management unit 9 manages setting information 16 (details will be described later) for storing information set on the selection method of the corresponding parking / route points. The setting information 16 managed by the setting information management unit 9 is accessed by the control unit 11. The comparison determination unit 10 determines whether or not to set a route point based on the information at the time of route setting and the information at the time of parking, and narrows down the route point candidates. The determination result in the comparison determination unit 10 is accessed by the control unit 11.

The control unit 11 includes the above-described information acquisition unit 2, vehicle state detection unit 3, input unit 4, output unit 5, waypoint setting unit 6, map data management unit 7, history data management unit 8, setting information management unit 9 and The comparison / determination unit 10 controls data transmission / reception performed mutually. In the following description, the description that data transmitted / received between the above components passes through the control unit 11 is omitted.

FIG. 2 is a diagram showing an example of the parking / route history table 13. This parking / route history table 13 includes (1) History No. , (2) the coordinates of the point where the parking / intermediate point is set, (3) the coordinates of the destination point set at the time of parking at the parking point or when setting the transit point, (4) the address of the parking / passing point , (5) Name of the facility at the parking / via point, (6) Sum of the number of times of parking at the relevant point and the number of times set at the relevant point as the transit point, (7) Date and time of parking at the relevant parking point, (8) Applicable Road information indicating whether the road facing the point is a general road or an expressway, (9) Date and time of route setting (route setting by user), (10) Driver information indicating a driver at the time of parking / route point setting including. Note that the name of the facility at (5) parking / route point is blank when there is no facility at the parking / route point. In addition, you may manage separately the frequency | count of having parked at the applicable point, and the number of times which set the applicable point as a transit point.

FIG. 3 is a diagram showing an example of the facility detailed information table 14. If there is a facility indicated by “(5) Facility name at parking / route point” in the parking / route history table 13 shown in FIG. 2, detailed information on the facility is further stored in the facility detail information table 14. The This facility detailed information table 14 includes (A) the name of the facility at the parking / route point, (B) the facility genre of the corresponding facility, (C) the parking lot information indicating whether or not the parking lot of the corresponding facility is empty, ( D) Business hours of the relevant facility, and (E) Meta genre of the facility genre of the relevant facility. The parking / route history table 13 and the facility detailed information table 14 are linked with "(5) Facility name at parking / route point" and "(A) Facility name at parking / route point" as keys. .

FIG. 4 is a diagram illustrating an example of the setting information 16. FIG. 4A is a table for storing setting values of conditions for the way of selecting a waypoint. This table shows the setting for the waypoint setting execution method (executed when the user triggers, or automatically executed by the system), and the setting for the waypoint setting method (specifies the point the user wants to make a waypoint) Or whether the system will automatically specify), setting for the waypoint setting method by the user (the user wants to specify the point that he / she wants to make the waypoint from all candidates, or the system sets all the candidates as appropriate conditions) ) And the setting for the waypoint setting method by the system (the system sets all candidates as waypoints unconditionally, or only places that meet the conditions are route points Information).
The “all candidates” in the present invention are not all points stored in the parking / route history table but all points where the set route and the destination are acquired by the same route. Routes with the same destination are called the same route. In addition, routes having the same destination and starting point may be the same route. Furthermore, all the points acquired by the route having a part shared with the set route may be set as candidates. In this way, it is possible to prevent a point that has nothing to do with the current route from among points stored in the parking / route history table.

FIG. 4 (b) is a table for storing setting values for the condition of whether to set a waypoint. FIG. 4B shows that the setting for the waypoint setting method by the user in FIG. 4A is “specified from candidates after the system narrows down under appropriate conditions”, or the setting for the waypoint setting method by the system. Can be set when is set to “Set only a point that meets the conditions as a transit point”. This table includes setting information for the number of waypoint settings, the distance at which the waypoints are set, the threshold value of the sum of the number of parking points and the number of waypoints to be set and the date threshold value at which the waypoints are set. In addition, the state of use / non-use is also stored for each function described above.

Next, the operation of the in-vehicle information device according to Embodiment 1 configured as described above will be described in several cases.

[1] First, a process for storing the coordinates of the parking spot and automatically setting the parking spot as a transit point when setting the route will be described with reference to the flowcharts shown in FIGS. 5 and 6.

FIG. 5 is a flowchart showing processing at the time of parking. In this process, first, the state of the host vehicle is acquired (step ST101). That is, the vehicle state detection unit 3 acquires the state of the own vehicle. Next, it is checked whether or not the vehicle is parked (step ST102). That is, the vehicle state detection unit 3 checks whether the state of the own vehicle acquired in step ST101 indicates a parking state. If it is determined in step ST102 that the host vehicle is not parked, the sequence returns to step ST101, and the above-described processing is repeated until the host vehicle is parked. Conditions for determining whether or not the parking state is performed in step ST102 will be described later.

On the other hand, if it is determined in step ST102 that the host vehicle is parked, it is checked in step ST103 if the destination is set. If the destination is not set, the process ends. If the destination is set, the coordinates of the parking spot are acquired (step ST104). That is, the map data management unit 7 acquires the coordinates of the parking spot from the map data 12. Next, the coordinates of the destination are acquired (step ST105). That is, the map data management unit 7 acquires the coordinates of the destination from the map data 12.

Next, the address of the parking spot is acquired (step ST106). That is, the map data management unit 7 acquires the address of the parking spot from the map data 12. Next, road information is acquired (step ST107). That is, the map data management unit 7 acquires the road information of the road facing the parking spot from the map data 12. Next, the facility name at the parking spot is acquired (step ST108). That is, the map data management unit 7 acquires the facility name at the parking spot from the map data 12.

Next, the parking date and time is acquired (step ST109). That is, the information acquisition unit 2 acquires the parking date and time. Next, driver information is acquired (step ST110). That is, the information acquisition unit 2 acquires driver information.

Next, all candidates (2), (4), and (5) are acquired from the parking / route history table (step ST111). In other words, the history data management unit 8 selects “(2) coordinates of points where parking / route points are set”, “(4) addresses of parking / route points” and “(5 ) “Facility name at parking / route point” is acquired and passed to the comparison determination unit 10.

Next, it is checked whether or not the same point exists in the parking / route history table (step ST112). That is, the map data management unit 7 passes the coordinates of the parking spot acquired in step ST104, the address of the parking spot acquired in step ST106, and the facility name at the parking spot acquired in step ST108 to the comparison determination unit 10. The comparison determination unit 10 determines whether the same point exists in the parking / route history table 13 based on whether the address and the facility name are equal, or the longitude and latitude are close, or both.

If it is determined in step ST112 that the same point exists in the parking / route history table, the number of times of parking in the corresponding history in the parking / route history table is increased by one (step ST113). That is, the history data management unit 8 increases “(6) the sum of the number of times of parking at the corresponding point and the number of times of setting the corresponding point as a waypoint” in the parking / route history table 13 by one. Thereafter, the process ends.

On the other hand, if it is determined in step ST112 that the same location does not exist in the parking / route history table, it is then checked whether the facility name has been acquired (step ST114). That is, in step ST108, the comparison determination unit 10 checks whether the facility name at the parking spot acquired from the map data 12 by the map data management unit 7 can be acquired (not set).

If it is determined in step ST114 that the facility name has been acquired, then the facility genre and meta genre name are acquired (step ST115). That is, if the map data management unit 7 determines that the facility name is not yet set, the map data management unit 7 acquires the facility genre name and the meta genre name from the map data 12. Next, business hours are acquired (step ST116). That is, the information acquisition unit 2 acquires business hours by the communication means based on the facility name acquired by the map data management unit 7.

Next, the description in the facility detailed information table is performed (step ST117). That is, the data acquired in step ST104 to step ST110, step ST115, and step ST116 is passed to the history data management unit 8, and the history data management unit 8 is based on the data acquired in steps ST108, ST115, and ST116. In the information table 14, (A) the name of the facility at the parking spot, (B) the genre name of the facility at the parking spot, (D) the business hours of the facility at the parking spot, and (E) the meta genre name are described.

Next, the entry into the parking / route history table is performed (step ST118). That is, the history data management unit 8 uses the data acquired in steps ST104 to ST110 as the (1) history No. in the parking / route history table 13. (Automatically assigned), (2) coordinates of parking spot, (3) coordinates of destination, (4) address of parking spot, (5) name of facility at parking spot, (6) number of parkings and waypoints It is described in the sum of the set times (“1” is described), (7) parking date and time, (8) road facing the parking spot, and (10) driver information. Thereafter, the process ends. If it is determined in step ST114 that the facility name could not be acquired, the processing in steps ST115 to ST117 is skipped, and the sequence proceeds to step ST118 and described in the parking / route history table.

Next, processing at the time of route setting will be described with reference to the flowchart shown in FIG. In this process, first, information on the input unit is acquired (step ST119). That is, when the user performs a route setting operation, some input information is notified to the input unit 4, so the input unit 4 acquires the information and passes it to the comparison determination unit 10.

Next, it is checked whether the information in the input unit is route setting information (step ST120). That is, the comparison / determination unit 10 checks whether the passed information is information that a route has been set. If it is determined in step ST120 that the information in the input unit is route setting information, all candidates (2) are acquired from the parking / route history table (step ST121). That is, the history data management unit 8 obtains “(2) coordinates of a point where a parking / passage point is set” from the parking / passage history table 13, and passes it to the relay point setting unit 6.

Next, the value acquired in step ST121 is set as a waypoint (step ST122). That is, the waypoint setting unit 6 sets the point acquired in step ST121 as a waypoint. Thereafter, the process ends. As described above, since all the points acquired by the same route as the set route are candidates for waypoint setting, in step ST122, the points acquired by the same route as the set route are Set as a stopover.
If it is determined in step ST120 that the information in the input unit is not route setting information, the processes in steps ST121 and ST122 are skipped, and the process ends.

By the processing described above, it is possible to set a stop point as a transit point without a troublesome operation by the user without having to perform a troublesome operation on a place (parking point) where the user stopped by the same route in the past. As a result, it is possible to navigate the route via the stop-by point. In addition, since the stop point is automatically set as a stopover point simply by the user setting the destination, it is not necessary to remember the place where the user visited before. That is, the route via the point desired by the driver can be drawn with little effort. The stop point does not have to be a point set by the user as a destination or a stopover.

[2] Next, the operation of storing the coordinates of the waypoint set by the user and automatically setting the corresponding waypoint as the waypoint when setting the route will be described with reference to the flowchart shown in FIG. Note that the processing at the time of setting a route is the same as the processing already described with reference to FIG.

FIG. 7 is a flowchart showing an operation when the user sets a waypoint. In this process, information on the input unit is first acquired (step ST123). That is, when the user performs a route setting operation, some input information is notified to the input unit 4, so the input unit 4 acquires the information and passes it to the comparison determination unit 10.

Next, it is checked whether or not the information in the input unit is route setting information by the user (step ST124). That is, the comparison / determination unit 10 checks whether the information passed in step ST123 is information that the user has set a waypoint. If it is determined in step ST124 that the information in the input unit is not the waypoint setting information by the user, the process ends.

On the other hand, if it is determined in step ST124 that the information in the input unit is the waypoint setting information by the user, then the coordinates of the waypoint are obtained (step ST125). That is, the map data management unit 7 acquires the coordinates of the waypoint from the map data 12. Next, the coordinates of the destination are acquired (step ST126). That is, the map data management unit 7 acquires the coordinates of the destination from the map data 12.

Next, the address of the waypoint is acquired (step ST127). That is, the map data management unit 7 acquires the address of the waypoint from the map data 12. Next, road information is acquired (step ST128). That is, the map data management unit 7 acquires the road information of the road facing the waypoint from the map data 12.

Next, the facility name at the waypoint is acquired (step ST129). That is, the map data management unit 7 acquires the facility name at the waypoint from the map data 12. Next, driver information is acquired (step ST130). That is, the information acquisition unit 2 acquires driver information.

Next, all candidates (2), (4), and (5) are acquired from the parking / route history table (step ST131). In other words, the history data management unit 8 selects “(2) coordinates of points where parking / route points are set”, “(4) addresses of parking / route points” and “(5 ) “Facility name at parking / route point” is acquired and passed to the comparison determination unit 10.

Next, it is checked whether or not the same point exists in the parking / route history table (step ST132). That is, the map data management unit 7 passes the coordinates of the waypoint acquired in step ST125, the address of the waypoint acquired in step ST127, and the facility name at the waypoint acquired in step ST129 to the comparison determination unit 10. The comparison determination unit 10 determines whether the same point exists in the parking / route history table 13 based on whether the address and the facility name are equal, or the longitude and latitude are close, or both.

In this step ST132, when it is determined that the same point exists in the parking / route history table, the number of route setting points of the corresponding history in the parking / route history table is increased by one (step ST133). That is, the history data management unit 8 increases “(6) the sum of the number of times of parking at the corresponding point and the number of times of setting the corresponding point as a waypoint” in the parking / route history table 13 by one. Thereafter, the process ends.

On the other hand, if it is determined in step ST132 that the same point does not exist in the parking / route history table, it is then checked whether the facility name is not yet set (step ST134). That is, the comparison / determination unit 10 checks whether or not the facility name at the waypoint acquired from the map data 12 by the map data management unit 7 in step ST129 is not set.

If it is determined in step ST134 that the facility name is not yet set, then the facility genre and meta genre name are acquired (step ST135). That is, if the map data management unit 7 determines that the facility name is not yet set, the map data management unit 7 acquires the facility genre name and the meta genre name from the map data 12. Next, business hours are acquired (step ST136). That is, the information acquisition unit 2 acquires business hours by the communication means based on the facility name acquired by the map data management unit 7.

Next, the description in the facility detailed information table is performed (step ST137). That is, the data acquired in step ST125 to step ST130, step ST135, and step ST136 is transferred to the history data management unit 8, and the history data management unit 8 is based on the data acquired in steps ST129, ST135, and ST136. In the information table 14, (A) the name of the facility at the via point, (B) the genre name of the facility at the via point, (D) the business hours of the facility at the via point, and (E) the meta genre name are described.

Next, the entry into the parking / route history table is performed (step ST138). That is, the history data management unit 8 uses the data acquired in steps ST125 to ST130 as (1) History No. (Automatically assigned), (2) coordinates of waypoint, (3) coordinates of destination, (4) address of waypoint, (5) name of facility at waypoint, (6) number of parkings and waypoint The sum of the set times (“1” is described), (8) the road facing the waypoint, and (10) driver information are described. Thereafter, the process ends. If it is determined in step ST134 that the facility name has not been set, the sequence proceeds to step ST138, and is described in the parking / route history table.
In this way, information regarding the waypoint input by the user using the input unit 4 at the time of setting a past route is stored in the parking / route history table. Thereby, when a new route is set, the coordinates of the waypoints acquired by the same route as the set route among the waypoints input by the input unit 4 are read from the parking / route history table. To be set as a stopover.

Through the processing described above, a place that the user has set as a stopover point in the past through the same route can be set as a stopover point without troublesome operations by the user. As a result, it is possible to navigate the route via the waypoint. Note that the transit point may not be a point where the user actually stops.

[3] Next, a process for making it possible to select whether the waypoint is set when the user triggers or the system automatically sets the waypoint will be described with reference to the flowchart shown in FIG.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Specifically, first, information on the input unit is acquired (step ST119), and then it is checked whether the information on the input unit is route setting information (step ST120). In step ST120, it is determined that the information in the input unit is route setting information (the specific description is omitted below). If step ST120 is YES, the value of the waypoint setting execution method is then acquired (step ST139). That is, the setting information management unit 9 acquires the value of “route place setting execution method” from the setting information 16 illustrated in FIG. 4A and passes the value to the comparison determination unit 10.

Next, it is checked whether or not the waypoint setting is triggered by the user (step ST140). That is, the comparison / determination unit 10 checks whether or not the value of “execution method of waypoint setting” is set to be executed when the user applies a trigger. In this step ST140, if it is determined that the execution of the waypoint setting is in a form to be triggered by the user, then a waypoint setting button and a guidance start button are output (step ST141). That is, the output unit 5 outputs the waypoint setting button 18 and the guidance start button 18A to the navigation screen as shown in FIG. Here, it is assumed that the trigger by the user is pressing of the waypoint setting button 18.

Next, information that the button has been pressed is acquired (step ST142). That is, when the waypoint setting button 18 is pressed by the user, information indicating that the button has been pressed is notified to the input unit 4, so that the control unit 11 acquires the information from the input unit 4 and performs comparison determination. Pass to part 10.

Next, it is checked whether or not a button press is detected (step ST143). That is, the comparison / determination unit 10 checks whether it is detected that the waypoint setting button 18 or the guidance start button 18A is pressed. If it is determined in step ST143 that no button press has been detected, the sequence returns to step ST142, and the processes in steps ST142 and ST143 are repeated until the button press is detected. When the pressing of the button is detected, it is determined in step ST143A whether the trigger (pressing of the waypoint setting button 18) is detected or the pressing of the guidance start button 18A is detected. If the pressing of the guidance start button 18A is detected, the process is terminated. That is, the route guidance is started without setting the waypoint.

If it is determined in step ST143A that a trigger has been detected during the repeated execution of steps ST142 to ST143A, that is, if depression of the waypoint setting button 18 is detected, steps ST121 and ST122 is executed. Specifically, the history data management unit 8 acquires all candidates (2) from the parking / route history table 13 (step ST121), and passes them to the route setting unit 6. Next, the waypoint setting unit 6 sets the value acquired in step ST121 as a waypoint (step ST122). Thereafter, the process ends.

If it is determined in step ST140 that the waypoint setting is not triggered by the user, that is, the system is set to execute automatically, steps ST121 and ST122 similar to those in FIG. 6 are executed. The That is, the waypoint setting unit 6 sets a waypoint. Thereafter, the process ends.

As described above, the user who wants to decide whether or not to set the waypoint can set the trigger to be set, and the user who does not want to make the decision can make the system automatically decide the waypoint. It is possible to determine whether or not to perform setting according to the user's intention.

[4] Next, referring to the flowchart shown in FIG. 10, a process for enabling the user to select a point to be set as a transit point from the parking / route history or whether the system automatically designates a point. While explaining.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, the value of the waypoint setting method is acquired (step ST144). That is, the setting information management unit 9 acquires the value of the waypoint setting method from the setting information 16 shown in FIG.

Next, it is checked whether or not the user has set to specify a point to be routed (step ST145). That is, the comparison / determination unit 10 checks whether or not the value acquired in step ST144 is set to specify the waypoint by the user. If it is determined in this step ST145 that the user has set the point to be set as a stopover, a stopover selection screen is output (step ST146). That is, the history data management unit 8 acquires (1) to (10) of all candidates in the parking / route history table 13 and passes them to the output unit 5, which outputs the information shown in FIG. A waypoint selection screen like this is output.

Next, a point is designated by the user (step ST147). That is, on the waypoint selection screen shown in FIG. 11, the user puts a check in the selection field of a point to be set as a waypoint and presses the enter button 20. As a result, the No. of the point designated by the user is displayed. Is notified to the history data management unit 8.

Next, (2) of the designated point is acquired from the parking / route history table (step ST148). That is, the history data management unit 8 receives the No. notified in step ST147. “(2) the coordinates of the point where the parking / passage point is set” is acquired from the parking / passage history table 13 corresponding to “” and is passed to the via point setting unit 6.

Next, the value acquired in step ST148 is set as the waypoint (step ST149). That is, the waypoint setting unit 6 sets the point acquired in step ST148 as a waypoint. Thereafter, the process ends. If it is determined in step ST145 that the user does not have a setting for specifying a point to be routed, steps ST121 and ST122 similar to those in FIG. 6 are performed. Set the ground. Thereafter, the process ends.

Through the process described above, users who want to specify a stopover by themselves can be specified by themselves, and users who do not want to specify a stopover by themselves can be specified by the system. It can be performed.

[5] Next, when the user designates a point to be set as a transit point, a process for enabling selection from among all candidates or a candidate after the system narrows down the conditions. This will be described with reference to the flowchart shown in FIG.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, the setting for the user's waypoint setting method is acquired (step ST150). That is, the setting information management unit 9 acquires the value of the waypoint setting method by the user from the setting information 16 shown in FIG.

Next, it is checked whether or not the setting is designated by the user from all candidates (step ST151). That is, the comparison / determination unit 10 checks whether or not the value of the waypoint setting method by the user passed in step ST150 is a setting designated by the user from all candidates. If it is determined in this step ST151 that the setting is designated by the user from all candidates, then a waypoint selection screen is output (step ST152). That is, the history data management unit 8 passes (1) to (10) of all candidates in the parking / route history table 13 to the output unit 5, and the output unit 5 uses the received information as shown in FIG. Output the waypoint selection screen.

If it is determined in step ST151 that the user is not set to specify from all candidates, that is, the system is set to specify from candidates after being narrowed down under appropriate conditions, candidates are narrowed down by the system. (Step ST153). That is, the history data management unit 8 compares all the candidates (1) to (10) of the parking / route history table 13, and the setting information management unit 9 compares the setting information 16 shown in FIG. 10, the comparison / determination unit 10 narrows down under appropriate conditions based on the passed information, and passes the result to the output unit 5. Thereafter, the sequence proceeds to step ST152, and a waypoint selection screen is output (step ST152). That is, the output unit 5 outputs a waypoint selection screen as shown in FIG. 13 from the passed information. FIG. 13 shows an example in which the driver information is narrowed down under the condition A. Next, a point is selected by the user (step ST155). In other words, the user puts a check in the waypoint selection column and presses the enter button 20. Thereafter, the processes of steps ST148 and ST149 similar to those in FIG. 10 are performed. Thereby, the waypoint setting unit 6 sets the designated point as a waypoint.

By the processing described above, designation from candidates after narrowing down the target becomes possible, so it is possible to set the waypoint more efficiently.

[6] Next, when the system automatically specifies a point to be set as a stopover, a process for making it possible to select whether to specify all candidates unconditionally or only candidates that meet the conditions is shown in FIG. This will be described with reference to the flowchart shown in FIG.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, the setting for the waypoint setting method of the system is acquired (step ST156). That is, the setting information management unit 9 acquires the value of the waypoint setting method by the system from the setting information 16 shown in FIG.

Next, it is checked whether or not the system is set to designate all points unconditionally (step ST157). That is, the comparison / determination unit 10 refers to the value of the waypoint setting method by the system passed in step ST156 to check whether the setting is unconditionally set to pass through all points. If it is determined in step ST157 that the system is set to specify all points unconditionally, then the processes of steps ST121 and ST122 similar to those in FIG. 6 are performed. Thereby, the waypoint setting unit 6 sets all the points as the waypoints. Thereafter, the process ends.

If it is determined in step ST157 that the system is not set to specify all points unconditionally, that is, it is set to use only a point that meets the conditions as a transit point, the system narrows down candidates. (Step ST158). That is, the history data management unit 8 compares all the candidates (1) to (10) of the parking / route history table 13, and the setting information management unit 9 compares the setting information 16 shown in FIG. 10, the comparison / determination unit 10 narrows down under appropriate conditions based on the passed information. To the history data management unit 8. Next, processing in steps ST148 and ST149 similar to those in FIG. 10 is performed, that is, the waypoint setting unit 6 sets the designated point as a waypoint.

By the processing described above, the user can select the conditions specified by the system, so it is easy to set a candidate that matches the user's preference as a transit point.

[7] Next, processing when the user sets the number of waypoint settings will be described with reference to the flowchart shown in FIG.

In this process, first, the value of the waypoint setting method by the user and the value of the waypoint setting method by the system are acquired (step ST159). That is, the setting information management unit 9 acquires the value of the waypoint setting method by the user and the value of the waypoint setting method by the system in the setting information 16 shown in FIG.

Next, it is checked whether or not the setting is narrowed down by conditions (step ST160). That is, the comparison / determination unit 10 determines that the value of the waypoint setting method by the user is “a setting designated from candidates after the system narrows down under appropriate conditions” or the value of the waypoint setting method by the system is “ It is checked whether the user is set to be a transit point only at a point that meets the conditions. In this step ST160, the setting is narrowed down by the condition, that is, whether the value of the waypoint setting method by the user is “a setting specified from candidates after the system narrows down under an appropriate condition” or by the system If the value of the waypoint setting method is “the setting is that only the point where the user meets the condition is a waypoint”, then the condition setting screen is output (step ST161). That is, the setting information management unit 9 passes information indicating the number of waypoint settings of the setting information 16 shown in FIG. 4B to the output unit 5, and the output unit 5 receives the information shown in FIG. The condition setting screen showing the number of waypoint settings is output.

Next, conditions are input by the user (step ST162). That is, the user presses the enter button 23. Thereby, each setting value input by the user is notified to the setting information management unit 9. Next, the contents of the setting information 16 are changed (step ST163). That is, the setting information management unit 9 changes the value of the number of waypoint settings in the setting information 16 illustrated in FIG. 4B to the content input in step ST162. Thereafter, the process ends.

Next, processing from narrowing down candidates based on the set conditions to setting them as transit points will be described with reference to the flowchart shown in FIG.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, the value of the number of waypoint settings, (1) of the parking / route history table, and the number of candidates are acquired (step ST164). That is, the setting information management unit 9 sets the value of the number of waypoint settings from the setting information 16 shown in FIG. 4B, and the history data management unit 8 sets all candidates (1) in the parking / wayway history table 13 as (1). Get the number of candidates.

Next, it is checked whether or not the number of candidates in the parking / route history table is larger than the value set by the user (step ST165). That is, the setting information management unit 9 sends the value of the number of waypoint settings, and the history data management unit 8 sends (1) of all candidates in the parking / wayway history table 13 and the number of candidates to the comparison determination unit 10, respectively. The comparison / determination unit 10 checks whether or not the number of candidates in the parking / route history table 13 is larger than the value of the number of waypoint settings.

In this step ST165, it is determined that the number of candidates in the parking / route history table is larger than the value set by the user, that is, the number of candidates in the parking / route history table 13 is larger than the number of route settings. Then, candidates are narrowed down by the number of waypoint settings (step ST166). In the narrowing down, predetermined conditions such as giving priority to newly registered ones and giving priority to ones that have visited many times are used. That is, the comparison / determination unit 10 narrows down the candidates to the value of the number of waypoint settings, and the narrowed point No. To the history data management unit 8. Next, processing in steps ST148 and ST149 similar to those in FIG. 10 is performed. Thereby, the waypoint setting unit 6 sets the designated point as a waypoint.

In step ST165, when the number of candidates in the parking / route history table is not larger than the value set by the user, that is, when the number of candidates in the parking / route history table 13 is less than or equal to the number of route setting numbers. Then, the processes of steps ST121 and ST122 similar to those in FIG. 6 are performed. Thereby, the waypoint setting unit 6 sets all points in the parking / route history table 13 as route points. Thereafter, the process ends.

If the user can determine the conditions for narrowing the waypoints by the processing described above, the waypoints can be set according to the user's preference.

[8] Next, the process from narrowing the waypoint candidates to setting the waypoints according to the distance from the route will be described with reference to the flowchart shown in FIG. Note that the processing when the user sets the upper limit distance from the route of the point set as the waypoint is the same as the processing already described with reference to the flowchart in FIG.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, route information is calculated from the map data (step ST167). That is, the map data management unit 7 obtains the coordinates of the current location, the waypoint set by the user, and the destination from the map data 12, and calculates route information.

Next, (1) and (2) of the parking / route history table are acquired (step ST168). That is, the history data management unit 8 acquires all candidates (1) and (2) from the parking / route history table 13 and passes them to the comparison determination unit 10.

Next, the upper limit distance from the route of the point set as the waypoint is acquired (step ST169). That is, the setting information management unit 9 acquires the value of the distance for setting the waypoint from the setting information 16 shown in FIG. 4B and passes it to the comparison determination unit 10.

Next, it is checked whether or not there are one or more points narrowed down by the distance at which the waypoint is set (step ST170). That is, based on the information passed in steps ST168 and ST169, the comparison / determination unit 10 narrows down the points where the distance from the route falls within the distance value for setting the waypoint, and one or more narrowed points are included. Check if it exists. If it is determined in step ST170 that there are one or more narrowed points, the narrowed point No. Is transferred to the history data management unit 8. Next, processing in steps ST148 and ST149 similar to those in FIG. 10 is performed. Thereby, the waypoint setting unit 6 sets the designated point as a waypoint. Thereafter, the process ends. If it is determined in step ST170 that there are no narrowed points, the process ends.

According to the above-described processing, when a route that is far away from the corresponding parking / route point is set, the route is excluded from the candidates, and an extra route point can be deleted.

[9] Next, processing until the candidates are narrowed down based on the number of parking times and set as a waypoint will be described with reference to the flowchart shown in FIG. Note that the processing when the user sets the threshold of the sum of the number of parking points and the number of waypoints set is the same as the processing already described with reference to the flowchart of FIG. Omitted.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, (1) and (6) of the parking / route history table are acquired (step ST171). That is, the history data management unit 8 acquires all candidates (1) and (6) from the parking / route history table 13 and passes them to the comparison determination unit 10.

Next, a threshold value of the sum of the number of parkings for which the waypoint setting is performed and the number of times for the waypoint setting is acquired (step ST172). That is, the setting information management unit 9 obtains a threshold value of the sum of the number of parking points to be set for waypoints and the number of waypoints to be set from the setting information 16 shown in FIG.

Next, it is checked whether or not there is one or more points narrowed down by the threshold value of the sum of the number of parking places to be set and the number of waypoints set (step ST173). That is, the comparison / determination unit 10 determines from the information passed in steps ST171 and ST172 that (6) of each point in the parking / route history table is equal to or greater than the threshold of the sum of the number of parking points and the number of route point settings. Narrow down the points that become and check if there are one or more narrowed down points. If it is determined in step ST173 that there are one or more narrowed points, the No. of the narrowed point is set. Is transferred to the history data management unit 8. Next, processing in steps ST148 and ST149 similar to those in FIG. 10 is performed. Thereby, the waypoint setting unit 6 sets the designated point as a waypoint. Thereafter, the process ends. If it is determined in step ST173 that there are no narrowed points, the process ends. In addition, when managing separately the frequency | count which parked at the applicable point, and the frequency | count which set the applicable location to the waypoint, you may provide a threshold value with respect to the number of times of parking or the number of waypoints set.

By the above-described processing, when the number of times the parking spot is visited (the number of parking) is equal to or less than the predetermined number, it is excluded from the waypoint candidates. In the above-described processing, the case where the number of parking is equal to or less than the predetermined number has been described, but the same processing can be performed for the number of times the waypoint is set.

[10] Next, processing from narrowing down candidates based on the date and time until setting a transit point will be described with reference to the flowchart shown in FIG. Note that the processing when the user sets a threshold for setting the waypoint is the same as the processing already described with reference to the flowchart of FIG. 15, and thus the description thereof is omitted here.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, the route setting date and time is acquired (step ST174). That is, the information acquisition unit 2 acquires the route setting date and time and passes it to the history data management unit 8, and the history data management unit 8 stores it as temporary management data 15.

Next, all candidates (1) and (7) are acquired from the parking / route history table 13 and the route setting date / time is acquired from the temporary management data 15 (step ST175). That is, the history data management unit 8 acquires all candidates (1) and (7) from the parking / route history table 13, acquires the route setting date / time from the temporary management data 15, and passes it to the comparison determination unit 10.

Next, a date threshold value for performing waypoint setting is acquired (step ST176). That is, the setting information management unit 9 acquires a threshold value for a date for performing waypoint setting from the setting information 16 illustrated in FIG. 4B and passes it to the comparison determination unit 10.

Next, it is checked whether or not there is one or more points narrowed down by the threshold of the number of parking times for which the waypoint is set (step ST177). That is, the comparison / determination unit 10 narrows down and narrows points that are newer than the threshold value of the date when (7) of each point in the parking / route history table sets the waypoint from the information passed in steps ST175 and ST176. Check if one or more points exist. If it is determined in step ST177 that there are one or more narrowed points, the No. of the narrowed point is displayed. Is transferred to the history data management unit 8. Next, processing in steps ST148 and ST149 similar to those in FIG. 10 is performed. Thereby, the waypoint setting unit 6 sets the designated point as a waypoint. Thereafter, the process ends. If it is determined in step ST177 that there are no narrowed points, the process ends.

According to the processing described above, if the parked date and time is older than the specific date and time, it is removed from the waypoint candidates, so it is easy to set a facility that suits the user's preference as the waypoint. In the above-described processing, the case where the parking date / time is older than the specific date / time has been described. However, the same processing can be performed when the set date / time is older than the specific date / time.

[11] Next, when a parking lot of a facility at a parking spot or waypoint is vacant, processing for setting the parking spot or waypoint as a waypoint will be described with reference to the flowchart shown in FIG.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, (A) is acquired from the facility detailed information table (step ST178). In other words, the history data management unit 8 acquires all candidates (A) from the facility detailed information table 14. All candidates (A) in the acquired facility detailed information table 14 are passed to the information acquisition unit 2.

Next, the parking lot information for the facility acquired in step ST178 is acquired (step ST179). That is, the information acquisition part 2 acquires the parking lot information of the information (facility name) passed by step ST178 with a communication means, and passes it to the historical data management part 8. Next, the parking lot information is described in the facility detailed information table (step ST180). That is, the history data management unit 8 describes the data acquired in step ST179 in (C) of the facility detailed information table 14.

Next, all candidates (1) and (5) are acquired from the parking / route history table, and all candidates (A) and (C) are acquired from the facility detailed information table 14 (step ST181). That is, the history data management unit 8 acquires all candidates (1) and (5) from the parking / route history table 13 and also acquires all candidates (A) and (C) from the facility detailed information table 14. To the comparison determination unit 10.

Next, it is checked whether or not there is one or more points where the parking lot is vacant (step ST182). That is, the comparison / determination unit 10 narrows down points where the parking lot is vacant from the information acquired in steps ST178 and ST181, and checks whether there are one or more narrowed points. If it is determined in step ST182 that there is one or more points where the parking lot is vacant, then the processes of steps ST148 and ST149 similar to those in FIG. 10 are performed. Thereby, the waypoint setting unit 6 sets the designated point as a waypoint. Thereafter, the process ends. If it is determined in step ST182 that there are no narrowed points, the process ends.

By the above-described processing, if the parking spot of the facility at the parking spot or the waypoint is not vacant, it is removed from the candidate of the waypoint, so it becomes easy to set the facility that suits the user's preference as the waypoint.

[12] Next, when there is a facility of a similar genre in the corresponding parking / route point, a process of setting only the representative facility as a route point will be described with reference to the flowchart shown in FIG.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, all candidates (A), (B) and (E) are acquired from the facility detailed information table, and all candidates (1) and (5) are acquired from the parking / route history table (step ST183). That is, the history data management unit 8 acquires (A), (B), and (E) of all candidates from the facility detailed information table 14, and (1) and (5) of all candidates from the parking / route history table 13. ) And passed to the comparison determination unit 10.

Next, it is checked whether or not there are one or more facilities having similar genres in the corresponding parking / route points (step ST184). That is, the comparison / determination unit 10 checks whether there are one or more similar genres from (B) in the facility detailed information table 14. For example, when the genre name and the meta genre name are equal, it is determined that they are similar. If it is determined in step ST184 that there are one or more similar genres, route candidates of similar genres are deleted, leaving one (step ST185). That is, the comparison / determination unit 10 collects points having the same meta genre, leaves one set as a representative facility, deletes the other points, and stores the remaining points. To the history data management unit 8. Selection of the location to leave depends on predetermined conditions such as giving priority to newly registered ones and giving priority to ones that have visited many times.

Next, the processes of steps ST148 and ST149 similar to those in FIG. 10 are performed. Thereby, the waypoint setting unit 6 sets the designated point as a waypoint. Thereafter, the process ends. On the other hand, if it is determined in step ST184 that there is no similar genre, the processes of steps ST121 and ST122 similar to those in FIG. 6 are performed. Thereby, the waypoint setting unit 6 sets all candidates in the parking / route history table 13 as route points. Thereafter, the process ends.

Through the processing described above, facilities of similar genres are left out, and the others are excluded from the waypoint candidates, so it is easy to set a place that suits the user's preference as a waypoint.

[13] Next, when the information in the parking / route history table is similar to the information at the time of route setting, the processing for setting the corresponding parking / route point as a route will be described with reference to the flowchart shown in FIG. To do. When setting the route here, parking / waypoint history information includes the date, time, day information, season information, driver information indicating who was driving, and the road facing the parking / waypoint. Information, business hours of the facility at the parking / route point.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, the day of the week is acquired from the parking / route history table (step ST186). That is, the history data management unit 8 acquires all candidate days of the week from the parking / route history table 13.

Next, the day of the week on the set route is acquired (step ST188). The acquired set route and the day of the week of all candidates in the parking / route history table 13 are passed to the comparison determination unit 10.

Next, it is checked whether or not there is one or more points where the day of the week with the set route is the same (step ST190). That is, the comparison determination unit 10 narrows down the points in the parking / route history table 13 set on the same day of the week as the set route from the information passed in steps ST186 and ST188, and there is one or more narrowed points Find out if you want to.

In this step ST188, if it is determined that there is one or more narrowed points, the narrowed point No. Is transferred to the history data management unit 8. Next, processing in steps ST148 and ST149 similar to those in FIG. 10 is performed. Thereby, the waypoint setting unit 6 sets the designated point as a waypoint. Thereafter, the process ends. On the other hand, if it is determined in step ST190 that there are no narrowed points, the process ends.

By the processing described above, since it is excluded from candidates when it is not close to the parking / route point history information, it is possible to suppress unnecessary route point settings.

Note that the above description is an example of the day of the week, but even the date, time, or season information can be realized by the same processing.

[14] Next, in a state where the user has set a destination or waypoint, and the distance between each point (current location to waypoint or waypoint to destination, etc.) is a certain length or more, The process of setting the corresponding parking / route point that matches the existing conditions as the waypoint will be described with reference to the flowchart shown in FIG.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, distances and route information between points are calculated from the map data (step ST191). That is, the map data management unit 7 acquires the coordinates of the current location, the waypoints set by the user, and the destination from the map data 12, calculates the distance between each point and route information, and passes them to the comparison determination unit 10.

Next, it is checked whether or not there is one or more sections where the distance between the points is equal to or greater than a certain distance (step ST192). That is, the comparison / determination unit 10 examines whether or not there is one or more sections in which the distance between the points on the route has a certain length or more. If it is determined in step ST192 that there is no section in which the distance between the points is equal to or greater than a certain distance, the process ends.

On the other hand, if it is determined in step ST192 that there is at least one section having a certain distance between points, all candidates (2) are acquired from the parking / route history table (step ST193). That is, the history data management unit 8 acquires (2) of all candidates from the parking / route history table 13. The acquired (2) of the acquired parking / route history table 13 is passed to the comparison determination unit 10.

Next, it is checked whether or not there is at least one parking / route history table (2) in a section having a certain length or more (step ST194). That is, the comparison / determination unit 10 checks whether or not at least one (2) of each point in the parking / route history table 13 is included in a section having a certain length or more from the passed information. In step ST194, when it is determined that one or more (2) of the parking / route history table is not included in a section having a certain length or more, the process ends.

On the other hand, if it is determined in step ST194 that at least one (2) of the parking / passing history table is included in a section having a certain length or longer, then the corresponding parking / passing point in the section is routed. Set to the ground (step ST195). That is, (2) of the point in the section having a certain length or more in the parking / route history table 13 is passed to the route point setting unit 6, and the route point setting unit 6 sets the passed point to the route point. Set.

The processing described above can prompt the driver to take breaks at appropriate intervals.

[15] Next, a process for inquiring of the user whether or not to set the corresponding parking / route point as a waypoint will be described with reference to the flowchart shown in FIG.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, an inquiry screen as to whether to set a waypoint is output (step ST196). That is, the history data management unit 8 passes (1) to (10) of all candidates in the parking / route history table 13 to the output unit 5, and the output unit 5 makes an inquiry as shown in FIG. Output the screen.

Next, information that the button has been pressed is acquired (step ST197). That is, when the user inputs any answer to the inquiry screen (presses the button), information indicating that the button has been pressed is notified to the input unit 4, so that the control unit 11 receives the information from the input unit 4. Acquired and passed to the comparison determination unit 10.

Next, it is checked whether or not an affirmative answer has been pushed to the inquiry about whether to set a waypoint (step ST198). That is, the comparison / determination unit 10 checks whether or not the button 26 to be set has been pressed. If it is detected in step ST198 that an affirmative answer has been pressed, that is, the button 26 to be set has been pressed, the processing in steps ST121 and ST122 similar to those in FIG. 6 is performed. Thereby, the waypoint setting unit 6 sets the designated point as a waypoint. Thereafter, the process ends. If it is determined in step ST198 that an affirmative answer has not been pressed, the process ends.

Thus, when the user gives an affirmative answer to the inquiry, the corresponding parking / route point is set as a transit point, and when a negative answer is made, the route is set without setting the transit point.

By the processing described above, it is possible to suppress the waypoint setting unnecessary for the user.

[16] Next, a process for automatically turning off the waypoint setting function for the corresponding parking / route point when the user makes a negative response more than a certain number of times will be described with reference to the flowchart shown in FIG. In the following description, steps that perform the same processes as those shown in the flowchart of FIG. 25 are denoted by the same reference numerals as those used in FIG. 25 to simplify the description.

In this process, first, steps ST119 and ST120 similar to those in FIG. 6 are executed. Next, an inquiry screen as to whether to set a waypoint is output (step ST196). Next, information that the button has been pressed is acquired (step ST197).

Next, it is checked whether or not an affirmative answer has been pushed to the inquiry about whether to set a waypoint (step ST198). In this step ST198, when it is detected that the positive answer is not pushed, that is, the guidance start button 27 is pushed without the button 26 being pushed, the value of the negative answer data is incremented by 1 (step ST199). That is, the history data management unit 8 increases the value of the negative count data 17 by one.

Next, it is checked whether or not the value of the negative count data has reached a certain number (step ST200). That is, the history data management unit 8 passes the value of the negative count data 17 of the temporary management data 15 to the comparison determination unit 10, and the comparison determination unit 10 checks whether the value of the negative count data 17 is equal to or greater than a certain number. .

In this step ST200, when it is determined that the value of the negative count data has reached a certain number or more, it is changed to a setting not to inquire from the next time (step ST201). In other words, the setting information management unit 9 performs setting so that the waypoint setting is not performed at the next and subsequent route settings. Thereafter, the process ends. On the other hand, if it is determined in step ST200 that the value of the negative count data is not a certain number or more, the process of step ST201 is skipped and the process ends.

If it is detected in step ST198 that an affirmative answer has been pressed, that is, the button 26 has been pressed, the value of the negative answer data is set to 0 (step ST212). That is, the history data management unit 8 writes “0” in the negative count data 17. Next, the processes of steps ST121 and ST122 similar to those in FIG. 6 are performed. Thereby, the waypoint setting unit 6 sets the designated point as a waypoint. Thereafter, the process ends.

By the processing described above, it is possible to suppress the waypoint setting unnecessary for the user.

[17] Next, a process for storing parking information when the host vehicle stops will be described with reference to the flowchart shown in FIG. In the following, steps that perform the same processing as the processing shown in the flowchart of FIG. 5 are denoted by the same reference numerals as those used in FIG. 5 to simplify the description.

In this process, first, the vehicle state detection unit 3 acquires the state of the host vehicle (step ST101). Next, the vehicle state detection unit 3 checks whether or not the own vehicle has stopped until a predetermined time elapses from sensor information such as a vehicle speed sensor as the state of the own vehicle (step ST202). If it is determined in step ST202 that the own vehicle has not stopped, the sequence returns to step ST101, and the above-described processing is repeated until the own vehicle stops.

On the other hand, if it is determined in step ST202 that the own vehicle has stopped, the same processing of steps ST103 to ST118 as in FIG. 5 is executed, and parking information is acquired and described.

Since the parking information can be stored as long as the vehicle stops, the parking information can be easily stored. Since it is a condition that the destination is set, it can suppress that excessive parking information increases too much.

[18] Next, a process of storing parking information when the user turns off the engine will be described with reference to the flowchart shown in FIG. In the following, steps that perform the same processing as the processing shown in the flowchart of FIG. 5 are denoted by the same reference numerals as those used in FIG. 5 to simplify the description.

In this process, first, the vehicle state detection unit 3 acquires the state of the host vehicle (step ST101). Next, it is checked whether or not the user has turned off the engine (step ST206). That is, the vehicle state detection unit 3 acquires the state of the host vehicle and checks whether the engine is turned off. If it is determined in step ST206 that the user has turned off the engine, the same processing of steps ST103 to ST118 as in FIG. 5 is executed, and parking information related to parking is acquired and described. On the other hand, if it is determined in step ST206 that the user has not turned off the engine, the process ends.

According to the above-described processing, parking information cannot be stored unless the engine is turned off, so that it is possible to suppress excessive parking information from increasing.

The present invention can be used for navigation devices that require easy setting of waypoints.

Claims (17)

In the in-vehicle information device that sets the route to the destination entered in the input unit,
A map data management unit that acquires coordinates of a stop point, which is a point where the vehicle traveling based on the set route stops, from map data;
A history data management unit that stores and manages the coordinates of the stop points acquired by the map data management unit in a history table;
An in-vehicle information device comprising: a transit point setting unit that, when a route is set, reads out the coordinates of the stop point obtained from the same route as the set route from the history table and sets the coordinates as a transit point. The history data management unit stores and manages the coordinates of the waypoints input by the input unit in the history table in the past route setting,
When the route is set, the route setting unit reads out the coordinates of the route point input by the same route as the set route from the route points input by the input unit, and reads the route point from the history table. The on-vehicle information device according to claim 1, wherein A setting information management unit for storing and managing setting information in which a value for selecting whether to perform the waypoint setting by using the operation input by the input unit as a trigger or to automatically execute the waypoint setting Prepared,
The route setting unit, according to the setting information managed by the setting information management unit, executes the waypoint setting by using the operation input as a trigger, or automatically executes the waypoint setting. The in-vehicle information device according to claim 1. The setting information management unit stores setting information in which a value for selecting whether the user specifies a waypoint or automatically specifies a waypoint using the input unit,
The waypoint setting unit is configured so that a user uses the input unit among the stop points acquired by the same route as the set route according to the setting information managed by the setting information management unit. 4. The in-vehicle information device according to claim 3, wherein a specified point is set as a transit point, or the stop point acquired by the same route as the set route is automatically set as a transit point. . With an output section,
The setting information management unit is a setting in which a value for selecting whether a point stored in the history table is unconditionally a candidate for waypoint designation or a point narrowed down by a predetermined condition is set as a candidate Remember information,
The history data management unit, according to the value of the setting information managed by the setting information management unit, out of the points stored in the history table, all of the points acquired by the same route as the set route A point is presented as a waypoint designation candidate via the output unit, or a point narrowed down by the predetermined condition is presented as a waypoint designation candidate via the output unit. The in-vehicle information device according to claim 4. The history data management unit presents candidates for waypoint designation via the output unit at the number of points set using the input unit when selecting the points narrowed by the predetermined condition. The in-vehicle information device according to claim 5. The history data management unit exists within the distance specified by using the input unit from the set route among the points stored in the history table when selecting a point narrowed down by the predetermined condition. The in-vehicle information device according to claim 5, wherein a point to be performed is presented as a waypoint designation candidate via the output unit. The history data management unit
Stores the number of stops or the number of stops set in the history table,
Of the points stored in the history table, a point that is narrowed down under the predetermined condition is either the number of stops or the number of times set at the waypoint, or a point where the sum of these points is equal to or greater than a predetermined threshold. The vehicle-mounted information device according to claim 5, wherein the information is presented as a waypoint designation candidate via the output unit. The history table management unit
The coordinates of the stop point are stored in the history table together with the date and time when the vehicle stopped,
In setting a point narrowed down under the predetermined condition as a candidate, out of the points stored in the history table, the date stored using the input unit and the points stored at the date and time thereafter are set as the output unit. The vehicle-mounted information device according to claim 5, wherein the vehicle-mounted information device is presented as a candidate for waypoint designation via, and a point before the designated date and time is not presented. Provided with an information acquisition unit that acquires information from outside via communication means,
When it is determined that a parking lot of a facility existing at a point that is a candidate for waypoint designation is vacant based on the information acquired by the information acquisition unit, the route point setting unit 6. The in-vehicle information device according to claim 5, wherein the in-vehicle information device is set to a transit point. The history table management unit stores and manages a facility and its genre existing at the stop point in a facility information table,
When the plurality of points stored in the history table are candidates for waypoint setting, the route point setting unit is a representative facility for a facility having a similar genre among the plurality of waypoint setting candidates. The in-vehicle information device according to claim 5, wherein only the point where there exists is set as a transit point. The history table management unit stores the coordinates of the stop point, date / time season information, driver identification information, and road information facing the stop point in the history table, and relates to a facility existing at the stop point. Storing the information in the facility information table;
The waypoint setting unit includes the coordinates of the stop point at the time when the route is set, the date and time information, the identification information of the driver, the information on the road facing the stop point, and the information on the facility existing at the stop point. 6. The in-vehicle information according to claim 5, wherein when the information stored in the history table and the facility information table is similar, the coordinates of a point where the information is similar are read from the history table and set as a waypoint. apparatus. When the distance between the destination of the set route or the point of the waypoint is a certain distance or more, the waypoint setting unit selects a point existing between the points among the points stored in the history table. The on-vehicle information device according to claim 1, wherein 2. The in-vehicle information device according to claim 1, further comprising an output unit that displays an inquiry screen for inquiring the user about whether or not the waypoint setting is possible. The route point setting unit automatically stops the route point setting function when a negative answer is executed by the input unit a predetermined number of times or more with respect to the inquiry screen. In-vehicle information device. A vehicle state detection unit for detecting the state of the vehicle;
The history table management unit stores the coordinates of the point as the stop point in the history table when the vehicle state detection unit detects a stop state of the host vehicle until a predetermined time elapses. The in-vehicle information device according to claim 1. The history table management unit, when the vehicle state detection unit detects that the vehicle engine is turned off, stores the coordinates of the point as the stop point in the history table. The on-vehicle information device described.

Images