JP4747777B2 - Navigation system - Google Patents

Description

  The present invention relates to a navigation system.

  Conventionally, in a navigation apparatus mounted on a vehicle such as an automobile, when an operator such as a driver operates a predetermined input unit to set a destination, the destination and the current position detection processing unit detect the destination. Based on the current position of the vehicle, a route from the current position to the destination is searched, and the searched route is guided. In this case, the navigation device searches for a route based on map data including search data, road data, and the like stored in a storage medium such as a CD-ROM, DVD-ROM, or hard disk. And based on the said map data, a map is displayed on the display screen of a display part, and route guidance is performed by displaying the searched route on this map.

However, since the navigation device searches for a route based on the map data stored in the storage medium, it becomes impossible to search for an appropriate route when a new road is opened. End up. In addition, if a new facility is created, the facility is not included in the map data and cannot be searched. If an existing facility is abolished, information on the facility that does not exist at the present time or the facility Display the route to the operator, giving incorrect information to the operator. Therefore, a navigation device has been proposed that can use a communication means to receive a new version of map data and update the map data stored in a storage medium (see, for example, Patent Document 1).
JP 2002-279437 A

  In recent years, in navigation devices, travel history data when a vehicle travels is stored in a storage means so that an appropriate route can be set in consideration of actual traffic volume and traffic jam information. Is used to set the optimum route to the destination. Since the travel history data is stored in association with the link of the map data, when the map data link number is changed when the map data is updated as in the conventional navigation device, it corresponds to the travel history data. The link number of the attached link must be rewritten. Without such rewriting, it is impossible to set a route using the above-described travel history data, display traffic jam information on a map using the travel history data, and the like. However, if the link numbers are rewritten for all the travel history data, the processing load is large and it takes an enormous amount of time.

  FIG. 2 is a diagram showing an operation of updating travel history data in a conventional navigation device.

  In the data stored in the data storage unit of the navigation device, in addition to the drawing data for drawing the map, as shown in FIG. 2A, the travel history data is stored in association with the links. Contains data tables. In the example shown in FIG. 2A, the degree of congestion as traffic information included in the travel history data is shown, and the degree of congestion is “free” for all links.

  When the map data is updated, that is, when the map data is updated, the road data is also updated, so that the link number of the link data included in the road data is changed. Therefore, it is necessary to change all link numbers included in the data table before update to the link numbers after update. In this case, all link numbers included in the data table before the update are changed by referring to the road data conversion table in which the link numbers before and after the update are associated with each other as shown in FIG. Is done. Thereby, an updated data table as shown in FIG. 2C can be obtained.

  In this case, since the link numbers for all the travel history data are rewritten, if the data amount of the travel history data is large, the processing load is large and it takes an enormous time.

  In the present invention, when the map data is updated by resolving the conventional problems and updating the map data, the association with the link is updated only for the travel history data having a high utility value. An object of the present invention is to provide a navigation system that can reduce the processing load of the vehicle and can update travel history data in a short time.

Therefore, in the navigation system of the present invention, a map data storage unit that stores map data including link data of each link belonging to a road, a travel history data acquisition unit that acquires travel history data, and the travel history data acquisition A travel history data storage unit that stores the travel history data acquired by the unit in association with the link, a data update processing unit that performs an update process of the map data and an update process of the association between the travel history data and the link, has, the data update processing unit is configured to update the map data, a navigation system for updating the correspondence between links only travel history data selected based on the number of travels, the travel number , The number of times of traveling history data obtained by traveling the corresponding link, the data update processing unit, Serial number of running times selects the travel history data is not less than a predetermined number, the number of travels deletes the travel history data is less than a predetermined number.

  According to the present invention, when updating the map data, the navigation system updates the association with the link only for the travel history data having a high utility value. Therefore, the processing burden when the map data is updated can be reduced, and the travel history data can be updated in a short time.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing an operation of updating travel history data in the first embodiment of the present invention, FIG. 3 is a diagram showing an example of a link in the first embodiment of the present invention, and FIG. 4 is a diagram of the present invention. A flowchart showing the operation of the navigation system in the first embodiment, and FIG. 5 is a flowchart showing the operation of a subroutine of history data conversion processing in the first embodiment of the present invention.

  In the present embodiment, the navigation system may be a single device such as a vehicle navigation device mounted on a vehicle such as a passenger car, a truck, a bus, or a motorcycle, or may be disposed in an information center or the like. For example, an information providing server that stores map data, traffic information, and the like, and data received from the information providing server may be used. In addition, a navigation system including an in-vehicle device that displays a map or searches for a route may be used. The navigation system is a system composed of a kind of computer that includes arithmetic means such as a CPU and MPU, storage means such as a semiconductor memory, a magnetic disk, and an optical disk, and a communication interface. The navigation system includes a GPS (Global Positioning System), a geomagnetic sensor, a distance sensor, a steering sensor, a beacon sensor, a gyro sensor, a current position detection processing unit that detects a current position, map data including road data, search data, and the like A data storage unit as a storage means for storing a route, a route search process for searching for a route to a set destination based on input information, a route guidance process, and a POI (Point for searching for points and facilities) of Interest) A navigation processing unit that performs various arithmetic processes such as a navigation process such as a search process, an input unit, a display unit, a voice input unit, a voice output unit, and a communication unit, and has a route to a set destination. Search and give guidance.

  The data storage unit stores map data as information used for searching. That is, the data storage unit includes a database including various data files, and in addition to search data for searching for a route, the display unit displays a guide map along the searched route, In order to display guidance information, various data such as facility data are stored. The data storage unit also includes link data that is information relating to a link, which is a unit constituting a road. The link data includes information such as a link number, which is an identification number assigned to the link, coordinates of the start point and end point of the link, and a distance from the start point to the end point. Further, the data storage unit also stores various data for outputting predetermined information by the audio output unit.

  The input unit is for correcting a position at the start of traveling or inputting a destination, and includes an operation key, a push button, a jog dial, and a cross arranged on the in-vehicle device of the navigation system. Although it consists of a key etc., a remote controller may be sufficient. When the display unit is a touch panel, it is preferable that the display unit includes operation switches such as operation keys and operation menus displayed on the display screen of the display unit. In this case, an input can be performed by pressing, that is, touching, the operation switch like a normal touch panel.

  The display unit displays operation guidance, an operation menu, operation key guidance, a route from the current position to the destination, guidance information along the route, and the like. As the display unit, a CRT, a liquid crystal display, an LED (Light Emitting Diode) display, a plasma display, a hologram device that projects a hologram on a windshield, or the like can be used.

  In the present embodiment, from the viewpoint of function, the navigation system includes a map data storage unit that stores map data including link data of each link belonging to a road, a travel history data acquisition unit that acquires travel history data, and an acquisition A travel history data storage unit that stores the travel history data associated with the link, and a data update processing unit that performs map data update processing.

  Here, the map data storage unit and the travel history data storage unit are included in the data storage unit. The travel history data acquisition unit acquires travel history data including information such as the vehicle speed acquired from the speedometer, the vehicle speed sensor, the vehicle position information detected by the current position detection processing unit, and the travel locus. It is stored in the travel history data storage unit. The travel history data is acquired in association with the link of the road on which the vehicle has traveled. When the route search process is performed, the navigation system corrects the required time using the travel history data, and can set a route with the shortest required time to the destination. .

  In the present embodiment, the travel history data stored in the travel history data storage unit also includes a degree of congestion as traffic information of the link. Here, since the correspondence between the vehicle speed and the degree of congestion is defined in advance, the degree of congestion can be determined based on the vehicle speed. For example, on a general road, when the vehicle speed is 10 km / h or less, it is “congested”, when it exceeds 10 km / h and is 20 km / h or less, it is “congested”, 20 [ km / h] is defined as “free”. The correspondence between the vehicle speed and the degree of congestion can be changed as appropriate according to the type of road. Further, in the present embodiment, the traffic congestion degree has three levels of “traffic jam”, “congestion”, and “empty”, but the traffic congestion degree may be two levels, or in four or more levels. There may be.

  Further, the travel history data stored in the travel history data storage unit includes the number of travels of the link. The number of times of traveling is the number of times of traveling history data acquired by traveling the corresponding link. And a data update process part updates matching with a link only about the travel history data selected based on the number of times of travel. Specifically, the travel history data whose number of travels is a predetermined number or more is selected, and the link number of the link associated with the selected travel history data is updated.

  Next, the operation of the navigation system having the above configuration will be described. Here, an operation of updating the travel history data when the map data is updated will be described.

  When the map data stored in the map data storage unit is updated, the road data included in the map data is also updated, and the link number of the link data included in the road data is updated. Therefore, it is necessary to update the travel history data and set the link number of the travel history data stored in association with the link to the updated link number.

  First, the data update processing unit reads travel history data. In this case, as shown in FIG. 1A, a table of travel history data associated with each link and including the degree of congestion and the number of travels is read from the travel history data storage unit. FIG. 3 shows an example of a link. Each link is given a link number and a degree of traffic for explanation. Although the actual link data includes a large number of links, only a small number of links are shown in FIG. 3 for convenience of explanation.

  And the said data update process part performs a travel history data conversion process. In the travel history data conversion process, link numbers as road data are converted only for travel history data for links with a large number of travels. That is, refer to the road data conversion table as shown in FIG. 1 (c) for the link number of the table that selects only the travel history data for the links with a large number of travels as shown in FIG. 1 (b). Rewrite to the new link number. As a result, as shown in FIG. 1D, a travel history data table in which the corresponding link numbers are converted can be obtained.

  This is because links with a high number of trips are likely to run and use travel history data in the future, so the use value of travel history data is high and the need to rewrite and update the link number is high. Because. On the other hand, the travel history data with a small number of travels is deleted without updating the link number as road data. This is because a link with a small number of times of travel is considered to be less likely to travel in the future, and thus the utility value of travel history data is low, and the need to rewrite and update the link number is low. Whether the number of runnings is large or small is determined based on a predetermined number set in advance. Thereby, the processing burden for updating the travel history data can be reduced.

  Subsequently, the data update processing unit writes the travel history data and ends the process. In this case, a table of travel history data that has undergone link number conversion as shown in FIG. 1D is written in the travel history data storage unit. Thereby, the update of the travel history data is completed.

Next, a flowchart will be described.
Step S1 The travel history data is read out.
Step S2 A travel history data conversion process is executed.
Step S3 The travel history data is written and the process is terminated.

  Next, a subroutine for the travel history data conversion process will be described.

  First, the data update processing unit reads the number of travels. In this case, one travel history data for each link is selected from the travel history data table as shown in FIG. 1A read from the travel history data storage unit, and the selected travel history is selected. The number of runs included in the data is read. The travel history data is selected in order.

  Subsequently, the data update processing unit determines whether or not the number of travels is 10 or more as a predetermined number. Thereby, it is possible to select only the travel history data for the link having a large number of travels, with a predetermined number set in advance as a reference. Note that 10 times is merely an example, and the predetermined number can be arbitrarily set.

  And a data update process part erase | eliminates data, when the frequency | count of driving is not 10 times or more. As a result, the travel history data for the link having a small number of travels is deleted. If the number of runnings is 10 or more, leave it as it is. That is, the travel history data for the link having a large number of travels is left.

  Subsequently, the data update processing unit determines whether there is a next link. That is, it is determined whether or not there is travel history data for the next link. If there is a next link, the data update processing unit again reads the number of times of travel and repeats the above-described operation.

  If there is no next link, the data update processing unit converts the link number and ends the process. When there is no next link, only the travel history data for the link having a large number of travels is extracted from the travel history data table as shown in FIG. 1A read from the travel history data storage unit. As a result, a table of travel history data as shown in FIG. 1B is obtained. Therefore, referring to the road data conversion table as shown in FIG. 1 (c), the link number of the table in which only the travel history data for the link with a large number of travels as shown in FIG. 1 (b) is selected. Is converted to a new link number. As a result, a travel history data table in which the link numbers are converted as shown in FIG. 1D is obtained.

Next, a flowchart will be described.
Step S11: The data update processing unit reads the number of travels.
Step S12: The data update processing unit determines whether or not the number of travels is 10 or more. If the number of travels is 10 times or more, the process proceeds to step S14. If the number of travels is not 10 or more, the process proceeds to step S13.
Step S13: The data update processing unit deletes the data.
Step S14: The data update processing unit determines whether there is a next link. If there is a next link, the process returns to step S11, and if there is no next link, the process proceeds to step S15.
Step S15: The data update processing unit converts the link number and ends the process.

  As described above, in the present embodiment, only the travel history data for the link having a large number of travels is selected, the link number of the link associated with the selected travel history data is converted, and the travel history data is updated. Is supposed to do. Therefore, when updating the map data, the link number of the link associated only with the travel history data having a high utility value can be updated, and the processing load for the update process can be reduced. Travel history data can be updated over time.

  Next, a second embodiment of the present invention will be described. In addition, about the thing which has the same structure as 1st Embodiment, the description is abbreviate | omitted by providing the same code | symbol. The description of the same operation and the same effect as those of the first embodiment is also omitted.

  FIG. 6 is a diagram showing an operation of updating the travel history data in the second embodiment of the present invention, and FIG. 7 is a flowchart showing an operation of a subroutine of history data conversion processing in the second embodiment of the present invention. .

  In the present embodiment, the travel history data stored in the travel history data storage unit also includes the last update date as the link update date. The last update date is a date corresponding to the date and time when the corresponding link was last traveled and travel history data was acquired, and indicates the most recent date and time when the corresponding link was traveled. In the travel history data conversion process, the association with the link is updated only for the travel history data selected based on the update date and time. Specifically, the travel history data whose update date and time is after a predetermined date and time is selected, and the link number of the link associated with the selected travel history data is updated.

  This is because the new link of the last update date as the update date / time is considered to be highly likely to travel and use the travel history data in the future. This is because it is highly necessary to do this. On the other hand, the travel history data with the oldest update date is deleted without updating the link number as road data. This is because the link with the oldest update date is considered to have a low possibility of traveling in the future, so that the use value of the travel history data is low, and the necessity for rewriting and updating the link number is low. Whether the last update date is new or old is determined based on a predetermined date and time set in advance.

  Since the configuration and operation of other points are the same as those in the first embodiment, a travel history data conversion processing subroutine will be described here.

  First, the data update processing unit reads the last update date. In the present embodiment, a travel history data table as shown in FIG. 6A is read from the travel history data storage unit. In the table, the travel history data associated with each link includes the last update date instead of the number of travels in the first embodiment. Then, one traveling history data for each link is selected from the traveling history data table as shown in FIG. 6A read from the traveling history data storage unit, and included in the selected traveling history data. The last updated date is read. The travel history data is selected in order.

  Subsequently, the data update processing unit determines whether or not the last update date is after January 1, 2004 as a predetermined date and time. Accordingly, it is possible to select only the travel history data for the new link on the last update date based on a predetermined date and time set in advance. It should be noted that January 1, 2004 is merely an example, and the predetermined date and time can be set arbitrarily.

  Then, the data update processing unit deletes the data when the last update date is not after January 1, 2004. As a result, the travel history data for the link with the oldest update date is deleted. If the last update date is after January 1, 2004, it is left as it is. That is, the travel history data for the new link on the last update date is left.

  Subsequently, the data update processing unit determines whether there is a next link. That is, it is determined whether or not there is travel history data for the next link. If there is a next link, the data update processing unit again reads the last update date and repeats the above-described operation.

  If there is no next link, the data update processing unit converts the link number and ends the process. When there is no next link, only the travel history data for the new link on the last update date is selected from the travel history data table as shown in FIG. 6A read from the travel history data storage unit. This selects the travel history data table as shown in FIG. 6B. Therefore, referring to the road data conversion table as shown in FIG. 6C, the link of the table in which only the travel history data for the new link of the last update date as shown in FIG. 6B is selected. Convert the number and rewrite it with a new link number. As a result, a travel history data table in which the link numbers are converted as shown in FIG. 6D is obtained.

Next, a flowchart will be described.
Step S21: The data update processing unit reads the last update date.
Step S22: The data update processing unit determines whether or not the last update date is after January 1, 2004. If the last update date is after January 1, 2004, the process proceeds to step S24, and if the last update date is not after January 1, 2004, the process proceeds to step S23.
Step S23: The data update processing unit deletes the data.
Step S24: The data update processing unit determines whether there is a next link. If there is a next link, the process returns to step S21. If there is no next link, the process proceeds to step S25.
Step S25: The data update processing unit converts the link number and ends the process.

  Thus, in the present embodiment, only the travel history data for the new link on the last update date is selected, the link number of the link associated with the selected travel history data is converted, and the travel history data Updates are made. Therefore, when updating the map data, the link number of the link associated only with the travel history data having a high utility value can be updated, and the processing load for the update process can be reduced. Travel history data can be updated over time.

  Next, a third embodiment of the present invention will be described. In addition, about the thing which has the same structure as 1st and 2nd embodiment, the description is abbreviate | omitted by providing the same code | symbol. Also, the description of the same operations and effects as those of the first and second embodiments is omitted.

  FIG. 8 is a diagram showing an example of a link in the third embodiment of the present invention, FIG. 9 is a diagram showing an operation of updating travel history data in the third embodiment of the present invention, and FIG. 10 is a diagram of the present invention. It is a flowchart which shows operation | movement of the subroutine of the historical data conversion process in 3rd Embodiment.

  In the present embodiment, the operation of updating the travel history data when the link associated with the selected travel history data is divided by the update of the map data stored in the map data storage unit will be described. . Note that one link may be divided into three or more, but here, for convenience of explanation, it is assumed that one link is divided into two.

  For example, it is assumed that the link as shown in FIG. 8A is updated as shown in FIG. 8B by updating the map data. In this case, the link number of each link is changed to a new link number, and the link L14 before update is divided into two links L1004 and L1005 by the update. Each link is given a link number and a degree of congestion for explanation, but the link length is further given for explanation to the link L14 before update and the links L1004 and L1005 after update. ing.

  The road data conversion table for the example shown in FIG. 8 is as shown in FIG. In the example shown in FIG. 9B, the number of divisions for each link and the distance as the link length are included in the road data conversion table.

  In the present embodiment, the travel history data stored in the travel history data storage unit also includes the last update date of the link, as in the second embodiment. In the travel history data conversion process, the link number as the road data is converted only for the travel history data for the new link on the last update date. Since the configuration and operation of other points are the same as those in the first and second embodiments, a travel history data conversion processing subroutine will be described here.

  First, the data update processing unit reads the last update date. In this case, one travel history data for each link is selected from the travel history data table read from the travel history data storage unit, and the last update date included in the selected travel history data is read. . The travel history data is selected in order.

  Subsequently, the data update processing unit determines whether or not the last update date is after January 1, 2004 as a predetermined date and time. Then, the data update processing unit deletes the data when the last update date is not after January 1, 2004. If the last update date is after January 1, 2004, it is left as it is. Thereby, it is possible to select only the travel history data for the new link on the last update date.

  Subsequently, the data update processing unit determines whether there is a next link. If there is a next link, the data update processing unit again reads the last update date and repeats the above-described operation.

  If there is no next link, the data update processing unit converts the link number and ends the process. When there is no next link, only the travel history data for the new link on the last update date is selected from the travel history data table as shown in FIG. 9A read from the travel history data storage unit. The table which selected is obtained. In the present embodiment, the travel history data associated with each link includes the passage time of the link in addition to the data in the second embodiment.

  Therefore, referring to the road data conversion table as shown in FIG. 9B, the link number of the table in which only the travel history data for the new link on the last update date is selected is converted and rewritten with the new link number. . As a result, a travel history data table in which the link numbers are converted as shown in FIG. 9C is obtained. In this case, the passage time in the travel history data for the divided links L1004 and L1005 is given a value obtained by proportionally distributing the passage time in the travel history data for the link L14 before the division by the distance.

Next, a flowchart will be described.
Step S31: The data update processing unit reads the last update date.
Step S32: The data update processing unit determines whether or not the last update date is after January 1, 2004. If the last update date is after January 1, 2004, the process proceeds to step S34. If the last update date is not after January 1, 2004, the process proceeds to step S33.
Step S33: The data update processing unit deletes the data.
Step S34: If there is a next link, the data update processing unit returns to step S31. If there is no next link, the data update processing unit proceeds to step S35.
Step S35: The data update processing unit converts the link number and ends the process.

  As described above, in the present embodiment, when the link is divided into a plurality of parts by updating the map data, the travel history data is associated with each of the divided links if the link is a new link on the last update date. ing. Therefore, when the map data is updated, the travel history data having a high utility value can be used even after the link is divided.

  In the present embodiment, as described in the second embodiment, the reference for selecting the travel history data to be updated is the last update date. However, the travel history data to be updated is selected. The reference to be performed can also be the number of times of travel, as in the first embodiment.

  The present invention is not limited to the above-described embodiment, and various modifications can be made based on the spirit of the present invention, and they are not excluded from the scope of the present invention.

It is a figure which shows the operation | movement which updates the driving history data in the 1st Embodiment of this invention. It is a figure which shows the operation | movement of the update of the driving history data in the conventional navigation apparatus. It is a figure which shows the example of the link in the 1st Embodiment of this invention. It is a flowchart which shows operation | movement of the navigation system in the 1st Embodiment of this invention. It is a flowchart which shows operation | movement of the subroutine of the historical data conversion process in the 1st Embodiment of this invention. It is a figure which shows the operation | movement which updates the driving history data in the 2nd Embodiment of this invention. It is a flowchart which shows operation | movement of the subroutine of the historical data conversion process in the 2nd Embodiment of this invention. It is a figure which shows the example of the link in the 3rd Embodiment of this invention. It is a figure which shows the operation | movement which updates the driving history data in the 3rd Embodiment of this invention. It is a flowchart which shows operation | movement of the subroutine of the historical data conversion process in the 3rd Embodiment of this invention.

Claims (4)

A map data storage unit for storing map data including link data of each link belonging to the road;
A travel history data acquisition unit for acquiring travel history data;
A travel history data storage unit that stores the travel history data acquired by the travel history data acquisition unit in association with a link;
A data update processing unit that performs an update process of the map data and an update process of the association between the travel history data and the link,
The data update processing unit is a navigation system that updates the map data and updates the association with the link only for the travel history data selected based on the number of travels ,
The number of times traveled is the number of times the travel history data was acquired by traveling the corresponding link,
The navigation system characterized in that the data update processing unit selects travel history data in which the number of travels is equal to or greater than a predetermined number and deletes travel history data in which the number of travels is less than a predetermined number . A map data storage unit for storing map data including link data of each link belonging to the road;
A travel history data acquisition unit for acquiring travel history data;
A travel history data storage unit that stores the travel history data acquired by the travel history data acquisition unit in association with a link;
A data update processing unit that performs an update process of the map data and an update process of the association between the travel history data and the link,
The data update processing unit is a navigation system that updates the map data and updates the association with the link only for the travel history data selected based on the update date and time ,
The update date and time is the date and time when the corresponding link was last traveled to acquire travel history data,
The navigation system, wherein the data update processing unit selects travel history data whose update date is after a predetermined date and time, and deletes travel history data whose update date is before the predetermined date . A map data storage unit for storing map data including link data of each link belonging to the road;
A travel history data acquisition unit for acquiring travel history data;
A travel history data storage unit that stores the travel history data acquired by the travel history data acquisition unit in association with a link;
A data update processing unit that performs an update process of the map data and an update process of the association between the travel history data and the link,
The data update processing unit is a navigation system that updates the map data and updates the association with the link only for the travel history data selected based on the number of travels,
The travel history data includes data related to the transit time of each link,
The data update processing unit updates a link number of a link associated with the selected traveling history data, and divides the traveling history data when the link associated with the selected traveling history data is divided. A navigation system characterized by assigning a value obtained by proportionally distributing the passage time of a link before division to the distance of each link after division in association with each of the subsequent links . A map data storage unit for storing map data including link data of each link belonging to the road;
A travel history data acquisition unit for acquiring travel history data;
A travel history data storage unit that stores the travel history data acquired by the travel history data acquisition unit in association with a link;
A data update processing unit that performs an update process of the map data and an update process of the association between the travel history data and the link,
The data update processing unit is a navigation system that updates the map data and updates the association with the link only for the travel history data selected based on the update date and time,
The travel history data includes data related to the transit time of each link,
The data update processing unit updates a link number of a link associated with the selected traveling history data, and divides the traveling history data when the link associated with the selected traveling history data is divided. A navigation system characterized by assigning a value obtained by proportionally distributing the passage time of a link before division to the distance of each link after division in association with each of the subsequent links .

Images