JP2005114464A - Destination information providing method and information-providing system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide users with information on destination candidates, in such a way to make the users recognize the presence or the absence of a link to be avoided from passing in the vicinity. <P>SOLUTION: An information providing system 1 comprises both location DB 121 registering location information and avoidance DB 171 for registering avoidance information of each link set as an object to be avoided. Location information, which satisfies retrieval conditions included in destination retrieval requirements transmitted from a navigation system 21, is retrieved from the location DB 121 as location information on destination candidates. Each retrieved location information of the destination candidates is examined as to whether the avoidance information of a link in the vicinity of a location specified by the location information is registered in the avoidance DB 171, and the avoidance information is read from the avoidance DB 171 in the case that it is registered. Each location information on the destination candidates is transmitted with the avoidance information to the navigation system 21, when the avoidance information has been read. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a technique for providing destination candidate information to a communication terminal such as a navigation device having a communication function.

  Patent Document 1 discloses a navigation device that allows a user to accurately and easily set an avoidance area in route search. In this navigation device, an area to be avoided in route search can be designated by an area indicated by a two-dimensional plane. Further, in Patent Document 2, although it is not necessary at the present time, it is expected that it is necessary to avoid traffic in the future, and it is possible to display information in an area or point that the user himself / herself does not recognize. There has been disclosed a navigation device capable of setting an appropriate route in consideration of a region or a point. In this navigation apparatus, information (avoidance area information) related to an area or a point that is expected to be avoided in the future delivered from an information center can be displayed together with a road map. In addition, the route is set in consideration of the avoidance area information distributed from the information center.

JP 2002-243475 A

JP 2002-156236 A

  As described above, Patent Document 1 discloses using avoidance area information for route search. Patent Document 2 discloses displaying avoidance area information together with road map information and using the avoidance area information for route search. However, neither Patent Document 1 nor Patent Document 2 discloses the use of avoidance area information for destination setting. For example, when there is a link that should avoid traffic among links constituting a road near a certain point, the operator usually wants to avoid making such a point a destination for route guidance. Patent Document 1 and Patent Document 2 do not consider this point at all.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to present destination candidate information to a user so that it can be determined whether or not there is a link to avoid traffic in the vicinity.

  In order to solve the above-mentioned problems, the present invention provides, for each point of the destination candidate, the point information of the point to the communication terminal that has transmitted the destination search request including the destination search condition using the information providing system. Is provided together with the avoidance information of the link when the link constituting the road near the point is set as the avoidance target.

  For example, the information providing system includes, for each point, a point information database in which the point information of the point is registered and an avoidance target that is generated in the link for each link that configures a road set as the avoidance target. And an avoidance information database in which avoidance information including event type information for identifying the event that caused the setting of the event is registered. Further, the information providing system searches the point information database for point information that satisfies the search condition included in the destination search request transmitted by the communication terminal, as point information of the destination candidate. For each point information of the destination candidate searched in the search step and the destination candidate search step, whether or not link avoidance information existing in the vicinity of the point specified by the point information is registered in the avoidance information database If it is registered, the avoidance information reference step for reading out the avoidance information from the avoidance information database, and the point information of the destination candidate searched in the destination candidate search step, respectively, in the avoidance information search step When avoidance information is read, together with the avoidance information, a destination candidate providing step for transmitting to the communication terminal; Carried out.

  According to the present invention, for each point of the destination candidate searched according to the search condition included in the transmitted destination search request transmitted by the communication terminal, a link that constitutes a road near the point (to go to the point) If a link that is likely to pass) is set as an avoidance target, the point information of the point is provided to the communication terminal together with the avoidance information of the link. Therefore, the user can know, for each destination candidate point, whether the point can be reached without using a link that should be avoided.

  Hereinafter, embodiments of the present invention will be described.

First, a first embodiment of the present invention will be described. FIG. 1 is a schematic configuration diagram of an information providing system 1 to which the first embodiment of the present invention is applied.

  The information providing system 1 according to the present embodiment provides various information to the navigation device 21 via the Internet 42. A mobile terminal 22 that communicates with a mobile communication network 41 such as a mobile phone network or a PHS network is connected to the navigation device 21. The mobile communication network 41 is connected to the Internet 42. The navigation device 21 uses a mobile terminal 22 to connect to the Internet 42 via a mobile communication network 41.

  The information providing system 1 includes a portal server 11 that provides various information to the navigation device 21 via the Internet 42, a destination search server 12, a route search server 13, a map distribution server 14, a traffic information storage server 15, A weather information storage server 16 and an avoidance information management server 17; These servers 11 to 17 are connected to each other via a network such as an intranet 43, for example.

  The map distribution server 14 includes a map DB (database) 141 and a distribution unit 142. In the map DB 141, map data including a region ID and map composition data such as facilities and roads is registered for each region (mesh) obtained by dividing the map into a plurality of regions. When the distribution unit 142 receives a map distribution request including designation of a region or a point via a network such as the intranet 43, the distribution unit 142 reads out map data of the designated region or a region including the designated point from the map DB 142, Send to request source.

  The traffic information accumulation server 15 includes a traffic DB 151, an update unit 152, and a distribution unit 153. In the traffic DB 151, for each traffic event such as traffic jam, accident, congestion, and regulation, traffic information such as the area where the event occurred, the road where it occurred, and the time of occurrence is registered. FIG. 2 shows an example of registered contents in the traffic DB 151. In the example shown in FIG. 2, the traffic information record is a field 1510 for registering an ID (record ID) for uniquely identifying the record, and an event type of a traffic event such as a traffic jam, an accident, or a congestion. Field 1511, field 1512 for registering a region ID for identifying a region where a traffic event occurs, and a field for registering a link ID for identifying a link where a traffic event occurs (a link constituting a road) 1513, a field 1514 for registering the road name of the road including the link where the traffic event occurs, a field 1515 for registering the coordinate value of the location (representative point) where the traffic event occurs, A field 1516 for registering the occurrence time and a field 1517 for registering the expected end time of the traffic event A field 1518 for registering the travel time of the link where the traffic event occurs, a field 1519 for registering the importance level of the traffic event, and the link cost to be added to the link where the traffic event occurs A field 1520 for registration is provided. Here, the importance level of the traffic event is set according to the event type of the traffic event. The link cost is used when searching for a route between two points by the Dijkstra method or the like.

  The update unit 152 periodically accesses the traffic information providing server 31 that provides traffic information via the Internet 42, obtains the latest traffic information of each region from the traffic information providing server 31, and is registered in the traffic DB 151. Update each record of traffic information. Here, the traffic information providing server 31 manages a record of traffic information of each link constituting the road for each region. However, the link cost is not included in the traffic information record managed by the traffic information providing server 31. Therefore, the update unit 152 sets a link cost according to the importance level registered in the traffic information record, for example, using a table (not shown) indicating the correspondence between the importance level and the link cost, Register in the record.

  When the distribution unit 153 receives a traffic information distribution request including designation of a region, a point, an importance level, or a traffic information record ID via a network such as the intranet 43, the designated region, the region including the point, A traffic information record having a degree level or a record ID is read from the traffic DB 151 and transmitted to the request source.

  3A and 3B are diagrams for explaining the operation flow of the traffic information storage server 15, FIG. 3A shows the operation flow of the update process of the traffic DB 151, and FIG. 3B shows the traffic information distribution process. The operation flow is shown.

  First, the update process of traffic DB151 is demonstrated using FIG. 3 (A). This flow is executed, for example, periodically or when a predetermined event such as an instruction from the operator of the traffic information storage server 15 occurs. First, the update unit 152 specifies an unattended area ID from, for example, an area ID management table (not shown) in which area IDs of all areas are registered, and sets this as an attention area ID (S301). Next, the update unit 152 accesses the traffic information providing server 31 via the Internet 42 and obtains a traffic information record having the attention area ID. Then, the format of the obtained traffic information record is converted into a format for registration in the traffic DB 151 (S302). Here, as described above, since the link cost is not included in the traffic information record managed by the traffic information providing server 31, the field 1520 for registering the link cost of the traffic information record after the format conversion is, for example, Set to NULL state. Next, the updating unit 152 deletes the traffic information record having the attention area ID from the traffic DB 151 and registers the traffic information record obtained from the traffic information providing server 31 and converted in format in the traffic DB 151. Thereby, the record of the traffic information having the attention area ID registered in the traffic DB 151 is updated (S303). Next, the update unit 152 registers a link cost predetermined according to the importance level registered in the field 1519 of the record in the field 1520 of the newly added traffic information record (S304). Thereafter, if there is an unfocused area ID in the area ID management table (YES in S305), the update unit 152 returns to S301 and continues the process. On the other hand, if all the region IDs are noticed (NO in S305), this flow ends.

  Next, traffic information distribution processing will be described with reference to FIG. When the distribution unit 153 receives a traffic information distribution request including a region ID, a coordinate value of a point, an importance level, or a record ID of traffic information via a network such as the intranet 43 (S311), the specified region The traffic information record in which the region ID including the ID or the coordinate value of the point is registered in the field 1512 is read from the traffic DB 151. Here, when the coordinate value of the point is specified, for example, a table (not shown) showing the correspondence between the region ID and the range of the region is used to indicate the range of the region to which the coordinate value of the specified point belongs. The associated region ID is specified. If an importance level is designated, a traffic information record in which a level higher than the importance level is registered in the field 1519 is read from the traffic DB 151. If the record ID is specified, the traffic information record in which the record ID is registered in the field 1510 is read from the traffic DB 151 (S312). The distribution unit 153 then transmits the read traffic information record to the transmission source of the traffic information distribution request via a network such as the intranet 43. In S312, when such a traffic information record is not registered in the traffic DB 151, a response including a message to that effect is transmitted to the transmission source of the traffic information distribution request (S313). Thereafter, the process returns to S311.

  Returning to FIG. 1, the description will be continued. The weather information storage server 16 includes a weather DB 161, an update unit 162, and a distribution unit 163. In the weather DB 161, for each region obtained by dividing the map into a plurality of regions, the weather information of the region is registered. FIG. 4 shows an example of registered contents in the weather DB 161. In the example shown in FIG. 4, a weather information record registers a field 1610 for registering an ID (record ID) for uniquely identifying the record, and an event type of a weather event such as rain, fine weather, snow, and fog. Field 1611, field 1612 for registering an area ID for identifying the target area, field 1613 for registering temperature, field 1614 for registering humidity, field for registering the importance level of a weather event 1615 and a field 1616 for registering a link cost to be added to a link existing in the target area. Here, the importance level of the weather event is set according to the event type of the weather event.

  The update unit 162 periodically accesses the weather information providing server 32 that provides weather information via the Internet 42, acquires the latest weather information of each region from the weather information providing server 32, and is registered in the weather DB 161. Update each record of weather information. Here, the weather information providing server 32 manages a record of weather information for each region. However, the weather information record managed by the weather information providing server 32 does not include the link cost. Therefore, the update unit 162 sets a link cost according to the importance level registered in the weather information record, for example, using a table (not shown) indicating the correspondence between the importance level and the link cost, Register in the record.

  When the distribution unit 163 receives a weather information distribution request including designation of a region, a point, an importance level, or a weather information record ID via a network such as the intranet 43, the designated region, the region including the point, A weather information record having a frequency level or record ID is read from the weather DB 161 and transmitted to the request source.

  FIG. 5 is a diagram for explaining the operation flow of the weather information storage server 16, FIG. 5 (A) shows the operation flow of the update process of the weather DB 161, and FIG. 5 (B) shows the weather information distribution process. The operation flow is shown.

  First, the update process of the weather DB 161 will be described with reference to FIG. This flow is executed, for example, periodically or when a predetermined event such as an instruction from the operator of the weather information storage server 16 occurs. First, the update unit 162 accesses the weather information providing server 32 via the Internet 42 and obtains a record of weather information for each region. Then, the format of the obtained weather information record is converted into a format for registration in the weather DB 161 (S501). Here, since the link cost is not included in the weather information record managed by the weather information providing server 32 as described above, the field 1616 for registering the link cost of the weather information record after format conversion is, for example, Set to NULL state. Next, the update unit 162 deletes the weather information record of each region registered in the weather DB 161 and registers the weather information record obtained from the weather information providing server 32 and converted in format in the weather DB 161. . Thereby, the record of the weather information of each area registered in the weather DB 161 is updated (S502). Next, the update unit 162 registers a link cost predetermined according to the importance level registered in the field 1615 of the record in the field 1616 of the newly added weather information record (S503).

  Next, the weather information distribution process will be described with reference to FIG. When the distribution unit 163 receives a weather information distribution request including a region ID, a coordinate value of a point, an importance level, or a record ID of weather information via a network such as the intranet 43 (S511), the specified region A weather information record in which the area ID of the area including the ID or the coordinate value of the point is registered in the field 1612 is read from the weather DB 161. Here, when the coordinate value of the point is specified, for example, a table (not shown) showing the correspondence between the region ID and the range of the region is used to indicate the range of the region to which the coordinate value of the specified point belongs. The associated region ID is specified. If an importance level is designated, a record of weather information in which a level higher than the importance level is registered in the field 1615 is read from the weather DB 161. If a record ID is specified, a record of weather information in which this record ID is registered in the field 1610 is read from the weather DB 161 (S512). Then, the distribution unit 163 transmits the read weather information record to the transmission source of the weather information distribution request via a network such as the intranet 43. In S512, when such a weather information record is not registered in the weather DB 161, a response including a message to that effect is transmitted to the sender of the weather information distribution request (S513). Thereafter, the process returns to S511.

  Returning to FIG. 1, the description will be continued. The avoidance information management server 17 includes an avoidance DB 171, an update unit 172, and a distribution unit 173. In the avoidance DB 171, avoidance information of the link is registered for each link (link constituting the road) set as a traffic avoidance target. FIG. 6 shows an example of registered contents of the avoidance DB. In the example illustrated in FIG. 6, the record of avoidance information includes a field 1710 for registering an ID (record ID) for uniquely identifying the record, and a link ID of a link set as an avoidance target. Field 1711, field 1712 for registering the region ID of the region including the link set as the avoidance target, field 1713 for registering the cause type indicating whether the avoidance cause is a traffic event or a weather event, avoidance cause A field 1714 for registering the event type of the meteorological event or the traffic event, and a record ID of the weather information specifying the weather event causing the avoidance or a record ID of the traffic information specifying the traffic event are registered. For this purpose, a field 1715 is provided.

  The update unit 172 periodically accesses the traffic information storage server 15 via a network such as the intranet 43, and obtains a traffic information record in which the importance level of a predetermined value or higher is registered in the field 1519 from the traffic DB 151. And the record of the avoidance information which makes the traffic event registered into the avoidance DB171 the cause of avoidance is updated using the record of this traffic information. Similarly, the update unit 172 periodically accesses the weather information storage server 16 via a network such as the intranet 43, and updates the weather information whose importance level of a predetermined value or more is registered in the field 1615 from the weather DB 161. A record is obtained, and the record of avoidance information whose cause is a weather event registered in the avoidance DB 171 is updated using the record of weather information.

  When the delivery unit 173 receives the avoidance information delivery request including the designation of the area or the point via the network such as the intranet 43, the delivery unit 173 reads the avoidance information record of the area including the designated area or the spot from the avoidance DB 171. Send to request sender.

  FIG. 7 shows an operational flow of avoidance information distribution processing of the avoidance information management server 17. When the distribution unit 173 receives the avoidance information distribution request including the specification of the coordinate value of the point where the area ID is located via the network such as the intranet 43 (S711), the specified area ID is registered in the field 1712. The avoidance information record is read from the avoidance DB 171. When the coordinate value of the point is designated, for example, a table (not shown) showing the correspondence relationship between the region ID and the region range is used to correspond to the region range to which the coordinate value of the designated point belongs. A region ID is identified, and a record of avoidance information in which this region ID is registered in the field 1712 is read from the avoidance DB 171 (S712). Then, the distribution unit 173 transmits the read avoidance information record to the transmission source of the avoidance information distribution request via a network such as the intranet 43. In S712, when such a record of avoidance information is not registered in the avoidance DB 171, a response including a message to that effect is transmitted to the transmission source of the avoidance information distribution request (S713). Thereafter, the process returns to S711.

  FIG. 8 shows an operation flow of the avoidance DB update process of the avoidance information management server 17. The update unit 172 uses a timer or the like (not shown) to update the avoidance information based on the traffic event (the record of the avoidance information whose cause type is the field 1713) and the avoidance information based on the weather event (field 1713). It is monitored whether or not the cause type is any one of the update timings of the weather event avoidance information record (S801, S802). And if it becomes the update timing of avoidance information based on a traffic event (YES in S801), the processing of S810 to S816 is performed, and if it is the update timing of avoidance information based on a weather event (YES in S802), The process of S820-S825 is performed.

  Now, if it transfers to S810, the update part 172 will delete the record of the avoidance information whose cause classification of the field 1713 is a traffic event from the avoidance DB171. Then, a traffic information distribution request including designation of a predetermined importance level is transmitted to the traffic information storage server 15 via a network such as the intranet 43, and the importance level equal to or higher than the predetermined importance level is a field. The traffic information record registered in 1519 is obtained from the traffic information storage server 15 (S811).

  Next, the update unit 172 pays attention to an unfocused traffic information record from the acquired traffic information records, and sets this as the attention information record (S812). Then, according to a predetermined rule, a search area is set based on the coordinate values registered in the field 1515 of the record of attention information. Then, from the obtained traffic information record, the traffic information record in which the coordinate value located in the search area is registered in the field 1515 is specified (S813). For example, as shown in FIG. 9, it is assumed that coordinate values 901 registered in the field 1515 of each acquired traffic information record are plotted on a map. One of them is set as a coordinate value 901a registered in the field 1515 of attention information. In the process of S813, the search area 902 is set based on the coordinate value 901a of the attention information. Then, a traffic information record having a coordinate value 901 in the search area 902 is specified. In the example shown in FIG. 9, a rectangular area having a predetermined side length centered on the coordinate value 901a is set in the search area 902, but the present invention is not limited to this. For example, a circular area having a predetermined radius centered on the coordinate value 901a may be set as the search area.

  Next, the update unit 172 checks whether or not the number of traffic information records in which the coordinate value in the search area specified in S813 is registered in the field 1515 is greater than or equal to a predetermined value (S814). Here, the predetermined value may be set in consideration of the possibility of encountering a traffic event indicated by any of the traffic information records obtained in S811, for example, when heading to an arbitrary point in the search area. In S814, if the value is equal to or greater than the predetermined value, the avoidance information record in which the newly generated record ID (for example, serial number) is registered in the avoidance DB 171 is added to the avoidance DB 171, and the avoidance information record field 1711 is added. The link ID registered in the field 1513 of the attention information record, the area ID registered in the field 1512 of the attention information record in the field 1712 of the avoidance information record, and the field 1713 of the avoidance information record. The cause type “traffic event”, the event type registered in the field 1511 of the attention information record in the field 1714 of the avoidance information record, and the field of the record of attention information in the field 1715 of the avoidance information record Registered in 1510 To register the code ID (S815). Then, the process proceeds to S816. On the other hand, if it is not greater than the predetermined value in S814, the process immediately proceeds to S816.

  Next, in S816, the update unit 172 checks whether or not all the traffic information records obtained in S811 are set as the record of attention information. If it is not set, the process returns to S812, a record of traffic information that has not been noticed is set as a record of attention information, and the processing of S813 to S815 is performed. On the other hand, if it is set, the process returns to S801 and S802 to monitor the update timing of avoidance information based on traffic events and the update timing of avoidance information based on weather events.

  In S820, the update unit 172 deletes from the avoidance DB 171 a record of avoidance information whose cause type in the field 1713 is the weather event. Then, a weather information distribution request including designation of a predetermined importance level is transmitted to the weather information storage server 16 via a network such as the intranet 43, and the importance level equal to or higher than the predetermined importance level is a field. The weather information record registered in 1615 is obtained from the weather information storage server 16 (S821).

  Next, the update unit 172 pays attention to an unfocused weather information record from the acquired weather information records, and sets this as the attention information record (S822). Then, a link data distribution request including designation of the area ID registered in the field 1612 of the record of attention information is transmitted to the route search server 13 via the network such as the intranet 43, and belongs to the area indicated by the area ID. A record of link data of the link is obtained from the route search server 13 (S823). The processing in the route search server 13 will be described later.

  Next, the update unit 172 adds the avoidance information record in which the newly generated record ID (for example, serial number) is registered in the avoidance DB 171 to the avoidance DB 171 and obtains the avoidance information record in the field 1711 in S823. The link ID of the link data record, the area ID registered in the field 1612 of the attention information record in the field 1712 of the avoidance information record, and the cause type “weather event” in the field 1713 of the avoidance information record. The event type registered in the field 1611 of the attention information record is registered in the field 1714 of the attention information record, and the field 1715 of the avoidance information record is registered in the field 1610 of the attention information record. Register the record ID. This process is repeated for the number of link data records obtained in S823. That is, for each link data record obtained in S823, a record of avoidance information corresponding to the link data record is added to the avoidance DB 171 (S824).

  Next, in S825, the update unit 172 checks whether or not all the weather information records obtained in S821 are set as the attention information records. If it is not set, the process returns to S822, a record of unattended weather information is set as a record of attention information, and the processes of S823 to S824 are performed. On the other hand, if it is set, the process returns to S801 and S802 to monitor the update timing of avoidance information based on traffic events and the update timing of avoidance information based on weather events.

  Returning to FIG. 1, the description will be continued. The destination search server 12 includes a point DB 121 and a search unit 122. In the point DB 121, point information including the name, address, genre, guide information, and the like of the point is registered for each point that can be the target of the destination. FIG. 10 shows an example of registered contents in the point DB 121. In the example shown in FIG. 10, the point information record includes a field 1210 for registering a record ID for uniquely identifying the record, a field 1211 for registering a region ID of the region to which the point belongs, and the name of the point. Field 1212 for registration, field 1213 for registering the coordinate value (latitude and longitude) of the point, field 1214 for registering the location (address) of the point, and the genre of the point such as park, gas station, lodging, meal A field 1215 for registration and a field 1216 for registering point guide information are formed.

  When the search unit 122 receives a destination search request including a search condition via a network such as the intranet 43, the search unit 122 reads a record of point information satisfying the search condition from the point DB 121 and relates to the record of the read point information. A record of avoidance information having high characteristics is obtained from the avoidance information management server 17. And the record of the acquired point information and avoidance information is transmitted to the transmission origin of a request | requirement.

  FIG. 11 shows an operation flow of the destination search process of the destination search server 12. When receiving a destination search request including a search condition via a network such as the intranet 43 (S1101), the search unit 122 reads a record of point information satisfying the search condition from the point DB 121 (S1102). For example, if the search condition is designation of a spot name, a record of spot information in which the spot name designated in the field 1212 is registered. If the search condition is designation of a location, the record is designated in the field 1214. If the location information is registered, and if the search condition is genre designation, the location information record in which the genre designated in the field 1215 is registered is read from the location DB 121. If the search condition is a keyword, a point information record in which the keyword specified in any of the fields 1212, 1214, 1215, and 1216 is registered is read from the point DB 121.

  Next, the search unit 122 transmits to the avoidance information management server 17 an avoidance information distribution request including designation of the area ID registered in the field 1211 of each of the point information records read in S1102, and the avoidance information management server 17 A record of avoidance information having the same area ID as the area ID included in the avoidance information distribution request is obtained (S1103). Then, the search unit 122 transmits a link data distribution request including designation of the link ID registered in the field 1711 of each record of the obtained avoidance information to the route search server 13 via the network such as the intranet 43. A record of link data for each link for which avoidance information is set is obtained from the route search server 13 (S1104). The processing in the route search server 13 will be described later.

  Next, the search unit 122 pays attention to the record of unfocused spot information from the record of spot information read in S1102, and sets this as the record of spot information (S1105). Then, the search unit 122 selects the avoidance information record in which the same area ID as that registered in the field 1211 of the attention information record is registered in the field 1712 from the avoidance information records obtained in S1103. Identify. Further, the link data having the link ID registered in the field 1711 of the specified avoidance information record is specified from the link data records obtained in S1104. Then, the coordinate value registered in each of the specified link data records is compared with the coordinate value registered in the field 1213 of the attention information record, and avoidance information is set near the point indicated by the attention information. It is checked whether or not a link exists (S1106). For example, it is checked whether or not there is a record of link data in which a coordinate value with which a distance to a coordinate value registered in the field 1213 of the record of attention information is within a predetermined value (for example, 50 m) is registered. If such a link exists (Yes in S1106), when going to the point indicated by the attention information, there is a high possibility that the link will pass, and therefore, the event indicated by the avoidance information set for the link. There is a high probability of encounter. Therefore, in this case, the avoidance information record having the link ID of the corresponding link data record is associated with the end of the record of attention information, for example (S1107). Then, the process proceeds to S1108. On the other hand, if there is no link for which avoidance information is set near the point indicated by the attention information (NO in S1106), the process immediately proceeds to S1108.

  Next, in S1108, the search unit 122 checks whether or not all the spot information records read in S1102 are set as the record of attention information. If it is not set, the process returns to S1105, a record of unattended weather information is set as a record of attention information, and the processing of S81106 to S1107 is performed. On the other hand, if it is set, each of the point information records read in S1102 is set as destination candidate information together with the avoidance information record if the avoidance information record is associated. The search request is transmitted to the transmission source (S1109). Thereafter, the process returns to S1101.

  Returning to FIG. 1, the description will be continued. The route search server 13 includes a road network DB 131, an update unit 132, and a search unit 133. In the road network DB 131, link data of each link constituting a road on the map is registered. FIG. 12 shows an example of registered contents in the road network DB 131. In the example shown in FIG. 12, the record of the link data includes a field 1310 for registering a link ID for uniquely identifying the link, a field 1311 for registering the area ID of the area to which the link belongs, and a road including the link. A field 1312 for registering the road name of the field, a field 1313 for registering the coordinate value (latitude and longitude) of the representative point (for example, the center) of the link, and registering start node information including the coordinate value of the link start node. Field 1314, field 1315 for registering end node information including the coordinate value of the link end node, field 1316 for registering the link length, field 1317 for registering the standard travel time of the link, link Field 1318 for registering the travel time indicated by the traffic information of A field 1319 for registering a standard cost, a field 1320 for registering a cost indicated by link traffic information, a field 1321 for registering a cost indicated by link weather information, and an avoidance flag are registered. For this purpose, a field 1322 is provided. Among these fields, data is registered in advance in fields 1310 to 1317 and 1319. In the fields 1318 and 1320, data is registered based on traffic information records having the same link ID. Data is registered in the field 1321 based on a record of weather information having the same area ID. In the field 1322, on / off of an avoidance flag is registered based on a record of avoidance information having the same link ID.

  The update unit 132 periodically accesses the traffic information storage server 15, the weather information storage server 16, and the avoidance information management server 17 via a network such as the intranet 43, and each link data registered in the road network DB 131. Update the traffic travel time, traffic cost, weather cost and avoidance flag in the record.

  When the search unit 133 receives a route search request including designation of a departure point and a destination via a network such as the intranet 43, the cost between the departure point and the destination is minimized using, for example, the Dijkstra method. By searching the road network DB 131 for a link constituting the route, a recommended route for the starting point and the destination is searched. However, links for which the avoidance flag is on are not adopted as recommended routes. Then, route information including link data of each link constituting the searched recommended route is transmitted to the transmission source of the request.

  FIG. 13 shows an operation flow of the road network DB update process of the route search server 13. This flow is executed, for example, periodically or when a predetermined event such as an instruction from the operator of the route search server 13 occurs. First, the update unit 132 extracts a record of unextracted link data from the road network DB 131 (S1301). Next, the update unit 132 transmits a traffic information distribution request including the designation of the link ID registered in the field 1310 of the extracted record to the traffic information accumulation server 15 via the network such as the intranet 43, and traffic A response is received from the information storage server 15 (S1302). If the received response includes a traffic information record of the link having the specified link ID, the travel time registered in the field 1318 of the extracted record is registered in the field 1518 of this traffic information record. While updating with time, the traffic cost in the field 1320 of the extracted record is updated with the link cost registered in the field 1520 of this traffic information record (S1303).

  Next, the update unit 132 transmits a weather information distribution request including designation of the area ID registered in the field 1311 of the extracted record to the weather information storage server 16 via a network such as the intranet 43, and the weather A response is received from the information storage server 16 (S1304). If the received response includes a weather information record of the area having the specified area ID, the weather cost in the field 1321 of the extracted record is set to the link cost registered in the field 1616 of this weather information record. (S1305).

  Next, the avoidance information delivery request including the designation of the link ID registered in the field 1310 of the extracted record is transmitted to the update unit 132 via the network such as the intranet 43 to the avoidance information management server 17 to avoid the avoidance information. A response is received from the information management server 17 (S1306). Then, if the received response includes a record of avoidance information of the link having the specified link ID, the avoidance flag in the field 1322 of the extracted record is turned on, and if not included, it is turned off (S1307). .

  Next, the update unit 132 returns to S1301 if there is unextracted link data from the road network DB 131, and ends this flow if there is no link data (S1308).

  FIG. 14 shows an operation flow of route search processing of the route search server 13.

  When the search unit 133 receives a route search request including designation of the departure point and the destination via a network such as the intranet 43 (S1401), the search unit 133 sets a predetermined area including the departure point and the destination as the route search area ( S1402). Then, for example, using a table (not shown) indicating the correspondence between the area ID and the area range, the area ID associated with the area range including the route search area is specified. Next, the search unit 133 specifies records of link data in which the area ID specified in the field 1311 is registered from the road network DB 131 and the avoidance flag registered in the field 1322 is off. Is set as a search target record (S1403). Then, using the costs registered in the fields 1319 to 1321 of each search target record, search for a route that minimizes the total cost of the links constituting the route connecting the starting point and the destination by, for example, the Dijkstra method. (S1404). Then, the search unit 133 transmits route data including link data of each link constituting the searched route as recommended route information to the transmission source of the route search request (S1405).

  Returning to FIG. 1, the description will be continued. The portal server 11 includes a reception unit 111 and a request unit 112. The receiving unit 111 receives the request transmitted from the navigation device 21 via the Internet 42 and analyzes the content of the reception request. Then, the analysis result is notified to the request unit 112. The request unit 112 acquires information requested by the navigation device 21 from the servers 12 to 17 according to the analysis result received from the reception unit 111 and transmits the information to the navigation device 21. In response to this, the navigation device 21 receives and displays the information provided from the portal server 11.

  FIG. 15 is a diagram for explaining an operation flow of the portal server 11. When receiving the request from the navigation device 21 via the Internet 42 (S1501), the accepting unit 111 analyzes the content of the request and notifies the request unit 112 of the analysis result (S1502).

  If the analysis result of the receiving unit 11 is a destination search request including a search condition such as a keyword or genre specification, the request unit 112 sends the search condition to the destination search server 12 via a network such as the intranet 43. The accompanying destination search request is transmitted, and the destination candidate point information is received from the destination search server 12 (S1503).

  If the analysis result of the reception unit 11 is a route search request including designation of the departure point and destination, the request unit 112 sends the departure point and destination to the route search server 13 via the network such as the intranet 43. A route search request accompanied by designation of the route is transmitted, and the route information of the recommended route is received from the route search server 13 (S1504).

  Further, if the analysis result of the receiving unit 11 is a map distribution request including the specification of a region ID or a point, the request unit 112 specifies a region ID or a point to the map distribution server 14 via a network such as the intranet 43. A map distribution request accompanied by "" is transmitted and map information is received from the map distribution server 14 (S1505).

  If the analysis result of the reception unit 11 is a traffic information distribution request including a region ID, a point designation, or a traffic information record ID, the request unit 112 receives the traffic information storage server 15 via a network such as the intranet 43. In addition, a traffic information distribution request including a region ID, a point designation or a traffic information record ID is transmitted to receive traffic information from the traffic information storage server 15 (S1506).

  If the analysis result of the reception unit 11 is a weather information distribution request including a region ID, a point designation, or a weather information record ID, the request unit 112 receives the weather information storage server 16 via a network such as the intranet 43. In addition, a weather information distribution request including a region ID, a point designation, or a weather information record ID is transmitted to receive weather information from the weather information storage server 16 (S1507).

  Then, if the analysis result of the reception unit 11 is an avoidance information distribution request including the designation of the area ID or the point, the request unit 112 sends the area ID or the point to the avoidance information management server 17 via the network such as the intranet 43. The avoidance information distribution request with the designation of is transmitted, and the avoidance information is received from the avoidance weather information accumulation server 17 (S1508).

  If the request unit 112 obtains information from the servers 12 to 17 as described above, the request unit 112 passes the information to the reception unit 111. The reception unit 111 transmits the information received from the request unit 112 to the navigation device 21 via the Internet 42 (S1509).

  Next, the navigation device 21 will be described. FIG. 16 is a schematic configuration diagram of the navigation device 21. As illustrated, the navigation device 21 sends a request to the instruction receiving unit 211 that receives an instruction from the operator, a display unit 212 that displays information, a terminal IF 213 for connecting to the mobile terminal 22, and the portal server 11. An information acquisition unit 214 that transmits and obtains information, a current location detection unit 215 that detects the current location using GPS data obtained by, for example, a GPS (Global Positioning System) receiver, and an instruction received by the instruction reception unit 211 The navigation processing for displaying a map near the current location using the information acquired by the information acquisition unit 214 and the current location detected by the current location detection unit 215, or displaying a recommended route to the destination on the map together with the current location Part 216.

  The servers 11 to 17 and the navigation device 21 configured as described above include, for example, a CPU 901, a memory 902 used as a data storage unit and a work area for the CPU 901, an external storage device 903 such as an HDD, and a CD as shown in FIG. A reading device 905 that reads information from a portable storage medium 904 such as a ROM or a DVD-ROM, an input device 906 such as a keyboard or a mouse, an output device 907 such as a display, and a communication device (servers 11, 15, 16, a communication device for connecting to a network such as the Internet 42 and an intranet 43, the servers 12 to 14 and 17, a communication device for connecting to a network such as the intranet 43, and the navigation device 21 communicating with a mobile terminal 22. Communication device for performing 8, in a computer system including a can be realized by executing a predetermined program CPU901 it is loaded into the memory 902. The predetermined program may be downloaded from the storage medium 904 or the communication device 908 attached to the reading device 905 to the external storage device 903, and then loaded onto the memory 902 and executed by the CPU 901. Alternatively, the program may be directly loaded on the memory 902 from the storage medium 904 or the communication device 908 attached to the reading device 905 and executed by the CPU 901.

  Next, the operation of the information providing system 1 of the present embodiment will be described by taking as an example the case where the navigation device 21 requests destination search, route search, traffic information, weather information, and map distribution.

  FIG. 18 is a diagram for explaining an operation when processing a request from the navigation device 21 in the information providing system 1 to which the first exemplary embodiment of the present invention is applied.

  First, in the navigation device 21, the instruction receiving unit 211 receives a destination search request instruction when a search condition such as a keyword or a genre is input from an operator, and generates a destination search request including the input search condition. And transmitted to the portal server 11 (S1801). In response to this, the portal server 11 transmits the destination search request to the destination search server 12 according to the flow shown in FIG.

  Upon receiving the destination search request, the destination search server 12 specifies the point information of the point satisfying the search condition included in the destination search request as the point information of the destination candidate by the flow shown in FIG. S1802). And the avoidance information delivery request | requirement containing area ID which the point information of a destination candidate shows is produced | generated, and it transmits to the avoidance information management server 17 (S1803). In response to this, the avoidance information management server 17 specifies avoidance information having the area ID included in the avoidance information distribution request according to the flow shown in FIG. 7 (S1804), and uses the avoidance information as the destination search server 12. (S1805). When the destination search server 12 receives the avoidance information from the avoidance information management server 17, for each point indicated by the destination candidate point information by the flow shown in FIG. If there is, the avoidance information is added to the spot information of the spot (S1806). Then, the point information of each destination candidate is transmitted to the portal server 11. In response to this, the portal server 11 transmits the point information of each destination candidate to the navigation device 21 (S1807).

  In the navigation device 21, the navigation processing unit 216 displays the point information of each destination candidate received by the information acquisition unit 214 from the portal server 11 on the display unit 212 (S1808). Here, when avoidance information is added to the point information, the avoidance information is also displayed. FIG. 19A is an example of destination candidate information displayed on the navigation device 21. The spot names included in the destination candidate spot information are listed in the list display frame 2121, and details of the spot information including the spot name selected from the list display frame 2121 by operating the cursor 2126 by the operator are displayed. Are displayed in the detail display frame 2122. The detailed display frame 2122 is provided with a traffic avoidance event display frame 2123 and a weather avoidance event display frame 2124. In the traffic avoidance event display frame 2123, when the avoidance information of the cause type “traffic event” is added to the point information displayed in the detailed display frame 2122, the event type of the avoidance information (registration information in the field 1714) ) Is displayed. Further, in the weather avoidance event display frame 2124, when the avoidance information of the cause type “weather event” is added to the point information displayed in the detailed display frame 2122, the event type of the avoidance information (in the field 1714) Registration information) is displayed.

  In the navigation device 21, when the instruction receiving unit 211 detects that the operator has selected the traffic avoidance event display frame 2123 by operating the cursor 2126 on the screen shown in FIG. 19A, the navigation processing unit 216. Is a traffic information distribution request including the cause ID (the record ID of the traffic information registered in the field 1715) of the avoidance information of the cause type “traffic event” added to the spot information displayed in the detailed display frame 2122 Is transmitted to the portal server 11 (S1809). The portal server 11 transmits the traffic information distribution request to the traffic information accumulation server 15 according to the flow shown in FIG. In response to this, the traffic information accumulation server 15 extracts the traffic information according to the flow of FIG. The portal server 11 transmits the traffic information received from the traffic information storage server 15 to the navigation device 21 (S1811).

  In the navigation device 21, the navigation processing unit 216 displays the traffic information received from the portal server 11 by the information acquisition unit 214 on the display unit 212 (S1812). FIG. 19B is an example of traffic information displayed on the navigation device 21. A display frame 2135 is superimposed and displayed on the screen shown in FIG. 19A, and traffic information corresponding to the avoidance information displayed in the traffic avoidance event display frame 2123 is superimposed and displayed on the display frame 2135.

  In the navigation device 21, when the instruction receiving unit 211 detects that the operator has selected the weather avoidance event display frame 2124 by operating the cursor 2126 on the screen illustrated in FIG. 19A, the navigation processing unit 216. Is a weather information distribution request including the cause ID of the avoidance information of the cause type “weather event” (the record ID of the weather information registered in the field 1715) added to the spot information displayed in the detailed display frame 2122 Is transmitted to the portal server 11 (S1813). In response to this, the portal server 11 transmits the weather information distribution request to the weather information storage server 16 according to the flow shown in FIG. In response to this, the weather information storage server 15 extracts the weather information according to the flow of FIG. 5B (S1814) and transmits it to the portal server 11. The portal server 11 transmits the weather information received from the weather information storage server 16 to the navigation device 21 (S1815).

  In the navigation device 21, the navigation processing unit 216 displays the weather information received by the information acquisition unit 214 from the portal server 11 on the display unit 212 in the same manner as the traffic information (S1816).

  Next, in the navigation device 21, when the instruction receiving unit 211 detects that the operator has selected the destination setting 2125 by operating the cursor 2126 on the screen shown in FIG. 19A, the navigation processing unit 216 Then, a route search request is generated using the current location detected by the current location detection unit 215 as the departure location, and the destination candidate specified by the point information displayed in the detailed display frame 2122 as the destination, and transmitted to the portal server 11 (S1817). The portal server 11 transmits the route search request to the route search server 13 according to the flow shown in FIG. In response to this, the route search server 13 searches for a recommended route according to the flow shown in FIG. The portal server 11 transmits the recommended route information received from the route search server 13 to the navigation device 21 (S1819).

  In the navigation device 21, the navigation processing unit 216 checks whether or not the map information of the area including the route indicated by the recommended route information received from the portal server 11 by the information obtaining unit 214 is stored in a storage unit such as a memory. If not stored, a map distribution request having a region ID of the region including the route is generated and transmitted to the portal server 11 (S1820). In response to this, the portal server 11 transmits the map distribution request to the map distribution server 14 according to the flow shown in FIG. In response to this, the map distribution server 14 searches the map information of the area having the area ID included in the map distribution request (S1821), and transmits the map information to the portal server 11. The portal server 11 transmits the map information received from the map distribution server 14 to the navigation device 21 (S1822).

  Next, in the navigation device 21, when the navigation processing unit 216 receives an instruction to start route guidance from the operator via the instruction receiving unit 211, the navigation processing unit 216 uses the route information and map information of the recommended route obtained from the portal server 11. Route guidance processing is performed (S1823).

  The first embodiment of the present invention has been described above. According to the present embodiment, for each point of the destination candidate searched according to the search condition included in the destination search request transmitted by the navigation device 21, the link that configures the road near the point (to go to the point) When a link that has a high possibility of passing through, for example, a link nearest to the point) is set as an avoidance target, the point information of the point is provided to the navigation device 21 together with the avoidance information of the link. . Therefore, the user of the navigation device 21 can know, for each destination candidate point, whether the point can be reached without using a link that should be avoided. That is, the operator of the navigation device 21 can set a destination that is unlikely to encounter an event that becomes a traffic obstacle such as congestion.

  In this embodiment, the route search is performed using a link other than the link for which avoidance information is set. For this reason, it is possible to search for a route with a low possibility of encountering an event that obstructs traffic such as congestion. In the present embodiment, by turning on the avoidance flag (field 1322) of the link data of the link for which avoidance information is set in the road network DB 131, the link data of the link is employed when searching for a route. I'm trying not to be. However, the present invention is not limited to this. For example, instead of turning on the avoidance flag, a further cost may be added to the link cost. By doing in this way, the possibility that the said link will be employ | adopted at the time of a route search can be made low.

  Next, a second embodiment of the present invention will be described.

  In this embodiment, the display conditions of avoidance information can be changed for each operator of the navigation device 21 in the first embodiment. Note that in the information providing system 1 of the present embodiment, the map distribution server 14, the weather information storage server 16, and the weather information storage server 17 are the same as those in the first embodiment, and a description thereof will be omitted.

  The portal server 11 of the present embodiment performs the following processing in addition to the processing of the portal server 11 of the first embodiment (the flow shown in FIG. 15). That is, when the request received from the navigation device 21 by the reception unit 111 is an avoidance location search request including a search condition such as a keyword or genre specification, the request unit 112 transmits the destination search server 12 via a network such as the intranet 43. In addition, an avoidance location search request with this search condition is transmitted, and the location information of the avoidance location candidate is received from the destination search server 12. Then, the reception unit 111 transmits the point information of the avoidance place candidate to the navigation device 21. In addition, when the request received from the navigation device 21 by the reception unit 111 is an avoidance location registration request for registering an avoidance location, and avoidance for setting whether to use avoidance information for each cause event If the request is a use condition setting request, the request unit 112 transmits an avoidance location registration request and an avoidance use condition setting request to the avoidance information management server 17 via a network such as the intranet 43.

  The avoidance information management server 17 of this embodiment has a user profile DB 174 in addition to the configuration (the avoidance DB 171, the update unit 172, and the distribution unit 173) of the avoidance information management server 17 of the first embodiment. The user profile DB 174 includes avoidance information TL (table) 1720 and user setting TL 1730. The avoidance information TL 1720 is provided for each operator of the navigation device 21, and avoidance information for avoidance places set by the operator is registered. In the user setting TL 1730, an event type of avoidance information to be used is registered for each operator of the navigation device 21. FIG. 20A shows an example of registered contents of avoidance information TL (table) 1720, and FIG. 20B shows an example of registered contents of user setting TL 1730. As shown in FIG. 20A, the avoidance information TL 1720 is associated with the user ID 1721 of the operator for each operator of the navigation device 21. The avoidance information record registered in the avoidance information TL 1720 includes a field 1722 for registering an ID (record ID) for uniquely identifying the record, and a point ID of a point set as an avoidance target. A field 1723, a field 1724 for registering the area ID of the area including the point set as the avoidance target, and a field 1725 for registering the cause type “user setting” of the avoidance target are formed. . Further, as shown in FIG. 20B, the record registered in the user setting TL 1730 includes a field 1731 for registering the user ID of the operator of the navigation device 21 and use of avoidance information due to a traffic event as a cause of avoidance. A field 1732 for registering the presence / absence of a circumstance, a field 1733 for registering the presence / absence of use of avoidance information caused by a weather event, and a registration of the presence / absence of use of avoidance information caused by a user setting. Field 1734.

  The avoidance information management server 17 of this embodiment performs the process shown in FIG. 21 in addition to the process of the avoidance information management server 17 of the first embodiment (the flow shown in FIGS. 7 and 8). That is, when the update unit 172 receives a avoidance location registration request including a user ID, a point ID, and a region ID via a network such as the intranet 43 (YES in S2101), the update unit 172 is associated with the user ID and the user profile DB 174 Is added to the avoidance information TL 1720 registered in the field 1722, a record having a new record ID registered in the field 1722, the point ID included in the avoidance point registration request in the field 1723 of the record, and the field 1724 The area ID included in the avoidance point registration request and the cause type “user setting” are registered in the field 1725 of the record (S2102). In addition, when the update unit 172 receives the avoidance use condition setting request including the user ID and the presence / absence of use of the avoidance information of the traffic event, the weather event, and the user setting via a network such as the intranet 43 (S2103). YES), the record in which the user ID is registered in the field 1731 is specified from the user setting TL 1730. Then, in the fields 1732 to 1734 of the specified record, the presence / absence of use of traffic events, weather events, and user setting avoidance information is registered (S2104).

  Moreover, in the avoidance information management server 17 of this embodiment, the avoidance information delivery process shown in FIG. 7 is as follows. That is, when the distribution unit 173 receives the avoidance information distribution request including designation of the user ID and the area ID or the coordinate value of the spot (S711), the record in which the user ID is registered in the field 1731 is set as the user setting TL1730. Extract from If the presence / absence of use of the avoidance information due to the avoidance of the traffic event registered in the field 1732 of the extracted record is “Yes”, the area ID of the area including the designation of the area ID or the coordinate value of the point Is a record of avoidance information registered in the field 1712, and a record of avoidance information in which the cause type “traffic event” is registered in the field 1713 is read from the avoidance DB 171. In addition, when the presence / absence of use of the avoidance information caused by the weather event registered in the field 1733 of the record extracted from the user setting TL 1730 is “present”, the specification of the area ID or the coordinate value of the point is included. The avoidance information record in which the area ID of the area is registered in the field 1712 and the cause type “weather event” is registered in the field 1713 is read from the avoidance DB 171. If the presence / absence of use of the avoidance information caused by the user setting registered in the field 1734 of the record extracted from the user setting TL 1730 is “present”, the designation of the area ID or the coordinate value of the point is included. A record of avoidance information in which the region ID of the region is registered in the field 1712 is read from the avoidance information TL 1720 having the user ID (S712). Then, the distribution unit 173 transmits the read avoidance information record to the transmission source of the avoidance information distribution request via a network such as the intranet 43. In S712, when such a record of avoidance information is not registered in the avoidance DB 171, a response including a message to that effect is transmitted to the transmission source of the avoidance information distribution request (S713). Thereafter, the process returns to S711.

  Next, the destination search server 12 of this embodiment differs from the destination search process of the destination search server 12 of the first embodiment shown in FIG. 11 in the following points in the destination search process. That is, in S1103, the search unit 122 includes the designation of the user ID of the navigation device 21 that transmitted the destination search request and the area ID registered in the field 1211 of each of the point information records read out in S1102. The information distribution request is transmitted to the avoidance information management server 17, and a record of avoidance information having the same area ID as the area ID included in the avoidance information distribution request is obtained from the avoidance information management server 17. Further, in S1104, the search unit 122 causes the route search server 13 to register the link ID registered in the field 1711 of each record of the cause type “traffic event” and “weather event” among the obtained avoidance information records. The link data distribution request including the designation of the link is transmitted, the link data record of each link for which the avoidance information is set is obtained from the route search server 13, and the field 1723 of each record whose cause type is “user setting” A record of point information including the designation of the point ID registered in is acquired from the point DB 121. In S1106, the search unit 122 compares the coordinate value registered in the record of link data and point information acquired in S1104 with the coordinate value registered in the field 1213 of the record of attention information. It is checked whether or not there is a link and / or point where avoidance information is set in the vicinity of the point indicated by the attention information. If such a link and / or point exists, in S1107, a record of avoidance information having a link ID of the corresponding link data record and / or a record of avoidance information having a point ID of the point information record Are connected to the end of the record of attention information, for example.

  Further, the destination search server 12 of the present embodiment further performs the following processing. That is, when the search unit 122 receives an avoidance location search request including a search condition via a network such as the intranet 43, the search unit 122 reads a record of point information satisfying the search condition from the point DB 121. For example, if the search condition is designation of a spot name, a record of spot information in which the spot name designated in the field 1212 is registered. If the search condition is designation of a location, the record is designated in the field 1214. If the location information is registered, and if the search condition is genre designation, the location information record in which the genre designated in the field 1215 is registered is read from the location DB 121. If the search condition is a keyword, a point information record in which the keyword specified in any of the fields 1212, 1214, 1215, and 1216 is registered is read from the point DB 121. And each read point information is transmitted to the transmission source of the avoidance place search request as the avoidance place candidate point information.

  Next, the route search server 13 of the present embodiment includes an avoidance flag DB 134 in addition to the configuration of the route search server 13 of the first embodiment (the road network DB 131, the update unit 132, and the search unit 133). Further, the field 1322 for registering the avoidance flag from the link data record registered in the road network DB 131 is omitted. As shown in FIG. 22, the avoidance flag DB 134 has a table 1341 that is associated with the user ID of the operator for each operator of the navigation device 21. The record registered in the table 1341 is for registering the field 1342 in which the area ID is registered and the link ID of the link that exists in the area having the area ID and for which the avoidance flag for the user is set. Field 1343 is formed.

  In the route search server 13 of this embodiment, the road network DB update process is different from the road network DB update process of the route search server 13 of the first embodiment shown in FIG. 13 in the following points. That is, the process of S1307 is not performed. On the other hand, the route search server 13 of the present embodiment further performs an avoidance flag DB update process shown in FIG. This process is performed periodically or when a predetermined event such as an instruction from the operator of the route search server 13 occurs. First, the update unit 132 pays attention to the unattended user table 1341 from the avoidance flag DB 134 and sets this as the attention table (S2201). Next, the update unit 132 generates an avoidance information distribution request including the user ID associated with the attention table and the unattended area ID, and transmits the avoidance information distribution request to the avoidance information management server 13. A record of avoidance information is obtained (S2202). Then, the link ID registered in the obtained avoidance information record (cause type “traffic event” and / or “weather event” record) is registered, and the attention area ID of the attention table 1341 is registered in the field 1342. Is registered in the field 1343 (S2203). Then, if the updating unit 132 focuses on all the area IDs (YES in S2204), the updating unit 132 proceeds to S2205. If there is an unattended area ID (NO in S2204), the process returns to S2202. In S2205, when the updating unit 132 pays attention to the table 1341 of all users registered in the avoidance flag DB 134 (YES in S2205), the flow ends. If there is an unfocused table 1341 (NO in S2205), the process returns to S2201 to continue the processing.

  In the route search server 13 of the present embodiment, the route search process is different from the route search process of the route search server 13 of the first embodiment shown in FIG. 14 in the following points. That is, in S1403, the search unit 133 is a record of link data in which the area ID of the area including the route search area is registered, and is included in the user ID (operation of the navigation device 21) included in the route search request. The record of the link data other than the link in which the link ID is registered in the record having the area ID in the table 1341 having the user ID) is specified, and these are set as the search target records.

  Next, the operation of the information providing system 1 according to the present embodiment will be described by taking as an example the case where the navigation device 21 requests avoidance place search, avoidance place registration, and avoidance use condition setting.

  FIG. 24 is a diagram for explaining an operation when processing a request from the navigation device 21 in the information providing system 1 to which the second exemplary embodiment of the present invention is applied.

  First, in the navigation device 21, the instruction receiving unit 211 receives a search condition such as a keyword or a genre from an operator and receives an instruction for an avoidance place search request, and generates an avoidance place search request including the input search condition. Then, it is transmitted to the portal server 11 (S2401). In response to this, the portal server 11 transmits the avoidance place search request to the destination search server 12.

  When receiving the avoidance location search request, the destination search server 12 specifies the location information of each location satisfying the search conditions included in the avoidance location search request as the avoidance location candidate location information (S2402). And each point information of a avoidance place candidate is transmitted to the navigation apparatus 21 (S2403).

  In the navigation device 21, the navigation processing unit 216 displays the location information of each avoidance area supplement received from the portal server 11 by the information acquisition unit 214 on the display unit 212 (S <b> 2404). FIG. 25 is an example of avoidance location candidate information displayed on the navigation device 21. The name of the spot included in the spot information of the avoidance place candidate is displayed as a list in the list display frame 2127, and details of the spot information including the spot name selected from the list display frame 2127 by operating the cursor 2126 by the operator are displayed. Are displayed in a detailed display frame 2128.

  In the navigation device 21, when the instruction receiving unit 211 detects that the operator has selected the avoidance place setting 2129 by operating the cursor 2126 on the screen illustrated in FIG. 25, the navigation processing unit 2126 displays the user ID and An avoidance place registration request including the spot ID and the area ID included in the selected spot information is generated and transmitted to the portal server 11 (S2405). The portal server 11 transmits the avoidance location registration request to the avoidance information management server 17. In response to this, the avoidance information management server 13 adds a record to the avoidance information TL 1720 having the user ID included in the avoidance information registration request according to the flow shown in FIG. 21, and registers the avoidance information in this record. The area ID and spot ID included in the request and the cause type “user setting” are registered (S2406).

  Further, in the navigation device 21, the instruction receiving unit 211 avoids the use of avoidance information due to a traffic event as a cause of avoidance and a weather event from the operator via the avoidance use condition setting screen displayed on the display unit 212. The presence / absence of use of avoidance information as a cause and the use of avoidance information due to a user setting as an avoidance cause are accepted (S2407). FIG. 26 is an example of an avoidance usage condition setting screen displayed on the navigation device 21. As shown in the figure, a check box 2128 for checking whether or not use of avoidance information due to a traffic event is used, a check box 2129 for checking whether or not avoidance information is used as a cause of avoidance of a weather event, and user settings are set. A check box 2130 indicating whether to use avoidance information as a cause of avoidance.

  In the navigation device 21, the instruction receiving unit 211 has selected the setting button 2131 by checking the check boxes 2128 to 2130 as necessary by operating the cursor 2126 on the screen shown in FIG. , The navigation processing unit 2126 uses the user ID, the presence / absence of use of the avoidance information caused by the traffic event specified by the check state of the check boxes 2128 to 2130, and the avoidance information caused by the weather event. An avoidance usage condition setting request including the presence / absence of use and the presence / absence of use of avoidance information due to the user setting is generated and transmitted to the portal server 11 (S2408). The portal server 11 transmits the avoidance usage setting request to the avoidance information management server 17. In response to this, the avoidance information management server 13 is included in the avoidance information registration request in the record of the user setting TL 1730 having the user ID included in the avoidance use setting request according to the flow shown in FIG. The presence / absence of use of avoidance information caused by a traffic event, the presence / absence of use of avoidance information caused by a weather event, and the presence / absence of use of avoidance information caused by a user setting are registered (S2409).

  In the present embodiment, when the navigation device 21 requests destination search, route search, traffic information, weather information, and map distribution, information exchange between the devices is basically the first embodiment shown in FIG. In the case of (S1801 to S1823). However, in the present embodiment, since the cause type of the avoidance information includes a user setting in addition to the traffic event and the weather event, the point information of each destination candidate displayed on the navigation device 21 in S1808 is, for example, FIG. As shown. In the display example shown in FIG. 27, a user setting avoidance event display frame 2133 is provided in the detailed display frame 2122 in the display example shown in FIG. The user setting avoidance event display frame 2133 is displayed in a different display form so that when the avoidance information of the cause type “user setting” is added to the spot information displayed in the detailed display frame 2122, it can be identified. Is done.

  The second embodiment of the present invention has been described above.

  According to the present embodiment, in addition to the effects of the first embodiment described above, the use conditions of the avoidance information can be changed for each operator of the navigation device 21.

  Next, a third embodiment of the present invention will be described.

  In the first embodiment described above, an operator of the navigation device 21 has instructed a distribution request for traffic information and / or weather information that is a cause type of avoidance information associated with point information of a destination candidate. In the case (when it is detected on the screen shown in FIG. 19A that the operator operates the cursor 2126 to select the traffic avoidance event display frame 2123 and / or the weather avoidance event display frame 2124), the navigation device 21 Is trying to send. On the other hand, in this embodiment, the portal server 11 is provided with avoidance information having traffic information and / or weather information as a cause type to the point information of each destination candidate received from the destination search server 12. In this case, the traffic information and / or weather information delivery request is transmitted. In the information providing system 1 according to the present embodiment, the servers 12 to 17 other than the portal server 11 are the same as those according to the first embodiment, and thus description thereof is omitted.

  The processing of the portal server 11 of this embodiment is different from the processing of the portal server 11 of the first embodiment shown in FIG. 15 in the following points. That is, in S1503, a destination search request is transmitted to the destination search server 12, and a record of destination candidate point information is received from the destination search server 12. Next, it is checked whether or not a record of avoidance information is added to each of the received destination candidate point information records. If the avoidance information record is added and the cause type registered in the avoidance information record field 1713 is a traffic event, the traffic information registered in the avoidance information record field 1715 A traffic information distribution request including the record ID is generated and transmitted to the traffic information storage server 15. Then, traffic information is obtained from the traffic information storage server 15. On the other hand, if the cause type registered in the field 1713 of the avoidance information record is a weather event, a weather information distribution request including the record ID of the weather information registered in the field 1715 of the avoidance information record is generated. To the weather information storage server 16. Then, traffic information is obtained from the weather information storage server 16.

  Next, taking the case where the navigation device 21 requests a destination search as an example, the operation of the information providing system 1 of the present embodiment will be described.

  FIG. 28 is a diagram for explaining an operation when processing a request from the navigation device 21 in the information providing system 1 to which the third exemplary embodiment of the present invention is applied.

  First, in the navigation device 21, the instruction receiving unit 211 receives a destination search request instruction when a search condition such as a keyword or a genre is input from an operator, and generates a destination search request including the input search condition. And transmitted to the portal server 11 (S2801). In response to this, the portal server 11 transmits the destination search request to the destination search server 12.

  Upon receiving the destination search request, the destination search server 12 specifies the point information of the point that satisfies the search condition included in the destination search request as the point information of the destination candidate (S2802). And the avoidance information delivery request | requirement containing area ID which the point information of a destination candidate shows is produced | generated, and it transmits to the avoidance information management server 17 (S2803). In response to this, the avoidance information management server 17 specifies avoidance information having the area ID included in the avoidance information distribution request (S2804), and transmits the avoidance information to the destination search server 12 (S2805). When the destination search server 12 receives the avoidance information from the avoidance information management server 17, the destination search server 12 checks whether or not there is avoidance information about the link near the point for each point indicated by the point information of the destination candidate. The avoidance information is added to the spot information of the spot (S2806). Then, the point information of each destination candidate is transmitted to the portal server 11 (S2807).

  When the portal server 11 receives the location information of each destination candidate and receives the location information of each destination candidate from the destination search server 12, the portal server 11 determines whether or not avoidance information is added to each location information of the destination candidate. Investigate. If avoidance information is added and the cause type of the avoidance information is a traffic event, a traffic information distribution request including the cause ID of the avoidance information (traffic information record ID) is generated, and the traffic information accumulation server 15 (S2808). In response, the traffic information accumulation server 15 extracts traffic information (S2809) and transmits it to the portal server 11 (S2810). If the cause type of the avoidance information is a weather event, a weather information distribution request including the cause ID of the avoidance information (weather information record ID) is generated and transmitted to the weather information storage server 16 (S2811). In response to this, the weather information storage server 16 extracts the weather information (S2812) and transmits it to the portal server 11 (S2813).

  The portal server 11 navigates the location information of each destination candidate received from the destination search server 12 together with the traffic information and weather information received from the traffic information storage server 15 and the weather information storage server 16 as necessary. The data is transmitted to the device 21 (S2814).

  In the navigation device 21, the navigation processing unit 216 displays the point information of each destination candidate received from the portal server 11 by the information obtaining unit 214 on the display unit 212 as shown in FIG. 19A (S2815).

  In the navigation device 21, when the instruction receiving unit 211 detects that the operator operates the cursor 2126 and selects the traffic avoidance event display frame 2123 on the screen illustrated in FIG. 19A, the navigation processing unit 216. 19B, the cause type “traffic event” added to the spot information displayed in the detailed display frame 2122 received together with the spot information of each destination candidate from the portal server 11 as shown in FIG. The traffic information including the cause ID of the avoidance information is displayed on the display unit 212 (S2816).

  In the navigation device 21, when the instruction reception unit 211 detects that the operator has selected the weather avoidance event display frame 2124 by operating the cursor 2126 on the screen illustrated in FIG. 19A, the navigation processing unit 216. The weather information including the cause ID of the avoidance information of the cause type “weather event” added to the spot information displayed in the detailed display frame 2122 received together with the spot information of each destination candidate from the portal server 11. It is displayed on the display unit 212 (S2817).

  The third embodiment of the present invention has been described above. This embodiment also has the same effect as the first embodiment. In the present embodiment, the traffic information and / or weather information causing the avoidance information is transmitted to the navigation device 21 together with the avoidance information. Therefore, the avoidance event display frame 2123 is displayed on the screen shown in FIG. When 2124 is selected, traffic information and weather information can be displayed quickly.

  In addition, this invention is not limited to said embodiment, A various deformation | transformation is possible within the range of the summary.

  For example, in the above embodiment, the navigation device 21 is connected to the Internet 42 via the mobile communication network 22 using the mobile terminal 22. However, the present invention is not limited to this. Any network that can interconnect the navigation device 21 and the portal server 11 may be used.

  Moreover, although said embodiment demonstrated taking the case where the servers 12-17 and the portal server 11 were connected by the intranet 43, the present invention is not limited to this. The servers 12 to 16 and the portal server 11 may be connected via the Internet 42. Moreover, in said embodiment, the servers 11-17 which comprise the information provision system 1 do not need to be constructed | assembled on the separate computer system. The servers 11 to 17 may be constructed on one computer system. Alternatively, each of the servers 11 to 17 may be constructed on a plurality of computer systems.

  Moreover, in said embodiment, although the terminal which acquires information from the portal server 11 is used as the navigation apparatus 21, this invention is not limited to this. Any terminal that can obtain information from the portal server 11 may be used. The navigation device 21 may be of a PDA (Personal Digital Assistant) type as well as an in-vehicle navigation device.

FIG. 1 is a schematic configuration diagram of an information providing system 1 to which the first exemplary embodiment of the present invention is applied. FIG. 2 is a diagram showing an example of registered contents in the traffic DB 151. FIG. 3 is a diagram for explaining the operation flow of the traffic information storage server 15, FIG. 3 (A) shows the operation flow of the update process of the traffic DB 151, and FIG. 3 (B) shows the traffic information distribution process. It is a figure which shows an operation | movement flow. FIG. 4 is a diagram showing an example of registered contents in the weather DB 161. FIG. 5 is a diagram for explaining the operation flow of the weather information storage server 16, FIG. 5 (A) shows the operation flow of update processing of the weather DB 161, and FIG. 5 (B) shows the distribution processing of weather information. It is a figure which shows an operation | movement flow. FIG. 6 is a diagram illustrating an example of registered contents of the avoidance DB. FIG. 7 is a diagram showing an operational flow of avoidance information distribution processing of the avoidance information management server 17. FIG. 8 is a diagram showing an operation flow of the avoidance DB update process of the avoidance information management server 17. FIG. 9 is a diagram for explaining the principle of avoidance information generation. FIG. 10 is a diagram showing an example of registered contents in the point DB 121. As shown in FIG. FIG. 11 is a diagram for explaining the operation flow of the destination search process of the destination search server 12. FIG. 12 is a diagram showing an example of registered contents in the road network DB 131. FIG. 13 is a diagram for explaining the operation flow of the road network DB update process of the route search server 13. FIG. 14 is a diagram for explaining an operation flow of route search processing of the route search server 13. FIG. 15 is a diagram for explaining the operation flow of the portal server 11. FIG. 16 is a schematic configuration diagram of the navigation device 21. FIG. 17 is a diagram illustrating a hardware configuration example of the servers 11 to 17 and the navigation device 21. FIG. 18 is a diagram for explaining an operation when processing a request from the navigation device 21 in the information providing system 1 to which the first exemplary embodiment of the present invention is applied. FIG. 19A is a diagram illustrating an example of destination candidate information displayed on the navigation device 21, and FIG. 19B is a diagram illustrating an example of traffic information displayed on the navigation device 21. FIG. 20A is a diagram illustrating an example of registered contents of the avoidance information TL 1720, and FIG. 20B is a diagram illustrating an example of registered contents of the user setting TL 1730. FIG. 21 is a diagram for explaining an operation flow of processing performed by the avoidance information management server 17 according to the second embodiment of this invention. It is a figure which shows the example of registration content of the avoidance flag DB134. FIG. 21 is a diagram for explaining an operation flow of processing performed by the route search server 13 according to the second embodiment of this invention. FIG. 24 is a diagram for explaining an operation when processing a request from the navigation device 21 in the information providing system 1 to which the second exemplary embodiment of the present invention is applied. FIG. 25 is a diagram illustrating an example of avoidance location candidate information displayed on the navigation device 21. FIG. 26 is a diagram illustrating an example of the avoidance usage condition setting screen displayed on the navigation device 21. FIG. 27 is a diagram showing an example of destination candidate information displayed on the navigation device 21. FIG. 28 is a diagram for explaining an operation when processing a request from the navigation device 21 in the information providing system 1 to which the third exemplary embodiment of the present invention is applied.

Explanation of symbols

DESCRIPTION OF SYMBOLS 11 ... Portal server, 12 ... Destination search server, 13 ... Route search server, 14 ... Map distribution server, 15 ... Traffic information storage server, 16 ... Weather information storage server, 17 ... Avoidance information management server, 21 ... Navigation device, DESCRIPTION OF SYMBOLS 22 ... Mobile terminal, 31 ... Traffic information provision server, 32 ... Weather information provision server, 41 ... Mobile communication network, 42 ... Internet, 43 ... Intranet, 111 ... Reception part, 112 ... Request part, 121 ... Point DB, 122 ... Search unit 131 ... Road network DB 132 ... Update unit 133 ... Search unit 141 ... Map DB 142 ... Distribution unit 151 ... Transport DB 152 ... Update unit 153 ... Distribution unit 161 ... Weather DB , 162 ... Update unit, 163 ... Distribution unit, 171 ... Avoidance DB, 172 ... Update unit, 173 ... Distribution unit

Claims (9)

A destination information providing method for providing destination candidate information to a communication terminal that has transmitted a destination search request including a destination search condition using an information providing system, wherein the information providing system includes: In addition, for each link that configures the road that is set as the avoidance target and the point information database in which the point information of the relevant point is registered, the event that causes the setting of the avoidance target that occurs in the link is specified. An avoidance information database in which avoidance information including event type information is registered, and
The information providing system includes:
Destination candidate search step for searching from the point information database as point information of a destination candidate for point information satisfying the search condition included in the destination search request transmitted by the communication terminal;
For each point information of the destination candidate searched in the destination candidate search step, check whether or not the avoidance information of the link existing in the vicinity of the point specified by the point information is registered in the avoidance information database, If registered, avoidance information reference step for reading the avoidance information from the avoidance information database,
Destination candidate providing step of transmitting each piece of destination candidate point information searched in the destination candidate search step to the communication terminal together with the avoidance information when the avoidance information is read out in the avoidance information search step And a destination information providing method characterized by: A destination information providing method according to claim 1,
The information providing system includes, for each link where a traffic event occurs, a traffic information database in which traffic information including coordinate information of the link and event type information specifying the traffic event occurring in the link is registered. In addition,
The information providing system includes:
When the traffic information registered in the traffic information database is used as a target link when a link in which a traffic event of a level higher than a predetermined level according to the traffic event is generated, a predetermined including the target link A link number detection step for detecting the number of links of other links in the area where a traffic event of the level or higher occurs,
When the number of links detected in the link number detection step is a predetermined number or more, the avoidance information update step of setting the attention link as an avoidance target and updating the avoidance information database is performed. To provide destination information. A destination information providing method according to claim 1,
The information providing system specifies a road network database in which road network data including link data of each link constituting a road on a map is registered, and for each area on the map, specifies coordinate information and weather events of the area. A weather information database in which weather information including event type information is registered, and
The information providing system includes:
Using the weather information registered in the weather information database, an avoidance area detecting step of detecting an area where a weather event of a level higher than a predetermined level according to a weather event occurs as an avoidance area;
The avoidance information update step of detecting the link existing in the avoidance area detected in the avoidance area detection step from the road network database, setting the detected link as an avoidance target, and updating the avoidance information database. Destination information provision method characterized by this. A destination information providing method according to claim 1,
The information providing system further includes a road network database in which road network data including link data of each link constituting a road on a map is registered,
The information providing system includes:
When a route search request including designation of a starting point and a destination is received from the communication terminal, it is set as an avoidance target in the avoidance information database using road network data registered in the road network database. A route search step of searching for a route connecting the starting point and the destination, which is configured by a link other than the existing link, and transmitting route data including link data of each link constituting the searched route to the communication terminal A method for providing destination information, characterized in that A destination information providing method according to claim 1,
The information providing system further includes a road network database in which road network data including link data of each link constituting a road on a map is registered,
The information providing system includes:
When the avoidance target search request including the search condition of the avoidance target area is received from the communication terminal, the avoidance target that searches the spot information database for the spot information satisfying the search condition as the avoidance target candidate spot information A candidate search step;
Each avoidance target candidate point information searched in the avoidance target candidate search step is transmitted to the communication terminal that has transmitted the avoidance target search request, and the avoidance target that receives designation of a point to be set as an avoidance target from the communication terminal A setting acceptance step;
By setting the point that has received the designation in the avoidance target setting reception step as the avoidance target, the avoidance information of the point including event type information indicating that the point is designated by the user of the communication terminal, The avoidance information registration step of registering in the avoidance information database,
The avoidance information reference step includes:
When the avoidance information of the point existing in the vicinity of the point specified by the point information of the destination candidate searched in the destination candidate search step is registered in the avoidance information database, the event type information of the avoidance information It is checked whether or not it is specified by the user of the communication terminal that transmitted the destination search request, and the avoidance information is read from the avoidance information database only when indicated. Destination information provision method. A destination information providing method according to claim 1,
The information providing system further includes a user condition database for registering avoidance information presentation conditions for each user,
The information providing system includes:
A user condition registration step of registering the avoidance information presentation condition received from the communication terminal in the user condition database in association with the user of the communication terminal,
The avoidance information reference step includes:
The event indicated by the event type information of the avoidance information when the avoidance information of the link existing in the vicinity of the point specified by the point information of the destination candidate searched in the destination candidate search step is registered in the avoidance information database Is checked whether it satisfies the presentation conditions registered in the user condition database in association with the user of the communication terminal that has transmitted the destination search request, and only when it is satisfied And reading the avoidance information from the avoidance information database. A destination information providing method according to claim 1,
The information providing system further includes a traffic information database in which traffic information including coordinate information of the link and event type information specifying a traffic event of the link is registered for each link constituting a road on the map,
The information providing system includes:
Further performing a traffic information extraction step of reading traffic information of the link in which the avoidance information read in the avoidance information reference step is set from the traffic information database;
The destination candidate providing step includes
When the avoidance information is read in the avoidance information search step for each point information of the destination candidate searched in the destination candidate search step, the avoidance information and the avoidance information read in the traffic information extraction step are A destination information providing method comprising: transmitting to the communication terminal together with traffic information of a set link. A destination information providing method according to claim 1,
The information providing system further includes, for each area on the map, a weather information database in which weather information including coordinate information of the area and event type information that identifies a weather event is registered,
The information providing system includes:
Further performing a weather information extracting step of reading out weather information of an area where there is a link where the avoidance information set read in the avoidance information reference step exists from the weather information database;
The destination candidate providing step includes
When the avoidance information is read in the avoidance information search step for each point information of the destination candidate searched in the destination candidate search step, the avoidance information and the avoidance information read in the weather information extraction step are A destination information providing method comprising: transmitting to a communication terminal together with weather information of a region where a set link exists. An information providing system for providing destination candidate information to a communication terminal that has transmitted a destination search request including a destination search condition,
For each point, a point information database in which the point information of the point is registered,
An avoidance information database in which avoidance information including event type information for identifying an event that causes a setting of an avoidance target occurring in the link is registered for each link that configures a road set as an avoidance target;
Destination candidate search means for searching from the point information database for point information that satisfies the search condition included in the destination search request transmitted by the communication terminal,
Avoidance information reference means for reading out avoidance information of links existing in the vicinity of the point specified by the point information of the destination candidate searched by the destination candidate search means, from the avoidance information database;
Destination candidate providing means for transmitting to the communication terminal the point information of the destination candidate searched by the destination candidate search means and the avoidance information read by the avoidance information reference means. Offer system.