JP4134510B2 - In-vehicle information terminal - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
  The present invention relates to an in-vehicle information terminal that performs guidance and search based on map information and a target selection method.
[0002]
[Prior art]
  Conventionally, when setting the destination or waypoint of a route in an in-vehicle information terminal, the user directly sets the position on the map, or uses the result of processing such as nearest search, information search, etc. (For example, JP 2000-2556 A).
[0003]
[Problems to be solved by the invention]
  However, if a complicated route is set by this method, the user has to repeatedly search for a target or a facility and search for a route many times in order to obtain his desired route, which is complicated. Met.
[0004]
  On the other hand, in addition to the above, there is a method of storing a plurality of fixed sightseeing routes in advance, but this is a route on which a travel agency decided, and the place where the user wants to go is not necessarily in the route. However, if the user wishes to change the route, the user cannot change the route or the operation becomes complicated.
[0005]
  The present invention has been made to solve such a problem, and provides an in-vehicle information terminal and a travel route creation method for obtaining a travel route that meets a user's preference with a simple operation.
[0006]
[Means for Solving the Problems]
  In-vehicle information terminal of the present invention,Means to create a travel locus that includes the type of landmark, total stoppage time for the landmark, and landmarkUser preferences and interestsIncludes a visit coefficient indicating the degree ofUser informationFor each landmarkStoreIn addition, a correspondence table showing the relationship between the time indicating the reference value of the total stop-off time for the landmark and the coefficient indicating the reference value of the visit coefficient is stored for each landmark.Storage means;Based on the driving trajectory, the stop time for the landmark is calculated, and the new stop time is calculated by adding this stop time to the total stop time included in the user information, and corresponding to the type of landmark A new visit coefficient is obtained from the new total stop-off time according to the table, and the updating means for updating the user informationIt is configured. With this configuration, in the vicinity of the current position or specified position,Learn and update the user's preference and interest level quantitatively from the driving historycan do.
[0007]
  The in-vehicle information terminal of the present invention isFurther comprising means for selecting a landmark based on a visit coefficient included in the user informationIt is configured.The vehicle further includes a vehicle position calculation means for calculating a current position by at least one of a satellite and a vehicle sensor, and an input means for inputting designated position data and course type data, and selects a landmark based on a visit coefficient. The means selects a landmark in the vicinity of the current position or the designated position in the order of the visit coefficient among the types of landmarks corresponding to the course type data.With this configuration,Learn and update the user's preference and interest level quantitatively from the driving historycan do.
[0008]
  The in-vehicle information terminal of the present invention is updatedBased on the time when the means last visited the landmark and the time when the landmark was visited again, an update interval, which is the time until the landmark was revisited, was calculated. Correct the visit factor. The storage means stores the time when the landmark was last visited, and represents the relationship between the time that is the reference value of the update interval and the coefficient that is the reference value of the correction coefficient for correcting the stop time A table is stored for each type of landmark, and the updating means refers to the correspondence table and obtains a correction coefficient from the update interval.With this configuration, the accuracy of the visit coefficient can be improved.
[0009]
  The in-vehicle information terminal of the present invention isThe updating means calculates a straight line distance between the vehicle and the landmark based on the vehicle position and the landmark position included in the travel locus, and this calculated Correct the drop-in time according to the straight line distance. In addition, the storage means stores a correspondence table that represents a relationship between a distance that is a reference value of the straight line distance between the vehicle and the landmark and a coefficient that is a reference value of a correction coefficient for correcting the stop-by time. The means obtains a correction coefficient from the linear distance with reference to this correspondence table.By this, the accuracy of the visit coefficientTheFurther improvementcan do.
[0010]
  The in-vehicle information terminal of the present invention isSelected landmarkIt is the structure which added the course preparation means to perform the round route search to. With this configuration, an appropriate travel route can be obtained.
[0011]
  The in-vehicle information terminal of the present invention is selectedLandmarksAnd explorationWasIn this configuration, display means for displaying a patrol route on a map is added. This configuration allows the user to selectLandmarkYou can easily travel around.
[0012]
DETAILED DESCRIPTION OF THE INVENTION
  Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0013]
  FIG. 1 is a functional block diagram showing a configuration of an embodiment of an in-vehicle information terminal according to the present invention.
[0014]
  The in-vehicle information terminal according to the present embodiment controls input from a user, a sensor, etc., and outputs an input data control unit 1 for outputting a current position, a designated position, a traveling purpose, and the like, and reading a recorded map database A map control unit 2 that creates and outputs a predetermined range of map data and travel locus data centered on the current position and the specified position, and a target that reflects the user's preference and interest User information describing information related to land, facilities, buildings, etc.) and memory 3 for recording the travel locus data, etc., and learning and using the user's preferences and interests from the travel locus data. A user information update unit 4 that updates the user information, a course creation unit 5 that performs a route search by determining a target or the like based on the map data and the user information, etc., an overall view of the search route, and each target To It is obtained and a display unit 6 for displaying such estimated time.
[0015]
  The user information that plays an important role in the present invention will be described with reference to FIG. This user information includes the type code and name of the target that matches the user's preferences and interests, the total number of times the target has been stopped by the previous time, and the date and time of the previous stop and the preference and interest. A visit coefficient indicating the degree is included. In addition, data symbols UA to UH for explanation are attached to each data of the user information in FIG.
[0016]
  The type code is represented by a 4-digit hexadecimal number, and a code “0x” representing the hexadecimal number is attached to the head. In this example, as shown in FIG. 11, the major classification is in the first digit, the middle classification is in the second digit,3Digits and4The small classification is represented by the digit. The major classifications 1 to 3 represent travel-related, and the major classifications 4 to 6 represent life-related processing classifications.
[0017]
  The date of stoppage is represented by a six-digit decimal number, and the last two digits of the year and the month and date are each represented by a two-digit number. The time of the stop is represented by a four-digit number, and the hour and minute of the 24-hour display are each represented by a two-digit number.
[0018]
  The visit coefficient is a number between 0 and 1 according to a calculation method described later, and has a larger value when the degree of preference / interest is higher.
[0019]
  First, the outline of the operation of the above embodiment will be described with reference to FIGS. First, the course creation processing performed by the course creation unit 5 will be described with reference to the flowcharts of FIGS.
[0020]
  In the input data control unit, the round trip point pickup conditions (the round trip point pickup conditions are, as shown in FIG. Is input and supplied to the course creation unit 5 (step 2 in FIG. 2, abbreviated as S2 in the flowchart below), the course creation unit executes a round-point pick-up process (step 3 in FIG. 2). , The processing shifts to the cyclic point pickup processing START of FIG. 3).
[0021]
  In this round point pickup process, the following processes are mainly performed.
[0022]
  1) Select and read map data near the patrol reference point from the map database (step 6).
[0023]
  2) User information is sequentially read (step 6 or step 13), and data suitable for the course type is selected (step 7 and step 8 or step 10 and step 11).
[0024]
  3) From the map data selected in the item 1), select the target type code that matches the type code of the data selected in the item 2) and add it to the cyclic point list ( Step 9 or Step 12).
[0025]
  4) Repeat steps 2) and 3) until the user information is completed (step 14). By this round trip point pick-up process, a target near the round base point, that is, a round trip point, that matches the target type code that represents the preference and interest of the user recorded in the user information is obtained.
[0026]
  Next, the user information update operation performed by the user information update unit 4 will be described with reference to the flowcharts of FIGS. When the travel locus data is supplied from the map information unit 2 (step 36 in FIG. 5), the user information update unit 4 executes the user information update process (from step 37 in FIG. 5 to the user information update process in FIG. 6). Processing shifts to START). The user information update process mainly performs the following process.
[0027]
  1) It is determined whether or not the vehicle is parked from the travel locus data (step 45).
[0028]
  2) In the case of parking, the following processing is continued on the assumption that the vehicle has stopped at a target near the current location (hereinafter also referred to as a landmark) obtained from the map data. In addition, the assumption of an Example can also be confirmed if a user's confirmation is added.
[0029]
  3) The stop time is estimated from the parking time based on the distance between the vehicle and the target value (step 59 and step 60 in FIG. 7).
[0030]
  4) It is determined whether or not the user information includes data including the target (step 63 in FIG. 7).
[0031]
  A. If the user information includes data that includes the target,
  i) Add a stoppage time to the total stoppage time of the user information to obtain a new total stoppage time (step 64),
  ii) The difference between the time when the user stops and the time when the user information stops is set as the update interval (step 65).
[0032]
  iii) The visit coefficient is obtained from the new total stop-off time by a calculation method that differs depending on the target type code (step 73 or 76), the correction coefficient is obtained from the update interval time (step 72 or 75), and the product of both coefficients Is a visit coefficient (step 74).
[0033]
  iv) The total stop time / date and time / time / visit coefficient of the user information data are updated (S78).
[0034]
  B. If there is no data including the target in the user information,
  i) The stoppage time is set as the new total stopover time (step 66).
[0035]
  ii) A visit coefficient is obtained from the new total stop-off time by a calculation method that differs depending on the type code of the target (step 68 or 69).
[0036]
  iii) Add the type code and name of the target, the total stoppage time, the date and time of stoppage, the time, and the visit coefficient (step 70). The type code and name of the target, and the total stop time, the date and time of the stop, the time, and the visit coefficient are added (step 70).
[0037]
  5) Rearrange the user information data in descending order of visit coefficient (step 79).
[0038]
  By the user information update operation as described above, the user's preference / interest is automatically learned about the target, and the user information data is updated. Therefore, by repeating the updating operation of the user information, learning of the user's preference and interest proceeds, and the above-described course creation can be performed more appropriately.
[0039]
  Subsequently, the operation of the above embodiment will be described in detail.
[0040]
  When the in-vehicle information terminal starts operation by turning on the power or resetting, the course creation unit 5 and the user information update unit 4 are activated. The course creation unit 5 performs a predetermined initialization process in step 1 of FIG. 2, and then waits for input of pickup conditions (step 2 of FIG. 2). Hereinafter, a case where the embodiment of the pickup condition (described below) in FIG. 8 is input will be described.
[0041]
  Departure longitude: 139 ° 23'35 "Departure latitude: 35 ° 34'07"
  Traveling reference point longitude: 139 ° 02'06 ″ Traveling reference point latitude: 35 ° 11′58 ″
  Destination Longitude: 139 ° 01'29 "Destination Latitude: 35 ° 12'03"
  Course type: Travel
  In the cyclic point pick-up process of FIG. 3, the map control unit first reads map data such as a predetermined range centered on the cyclic reference point C, for example, a radius or a range of 10 km from east, west, south, and north, which is indicated in the cyclic point pickup condition. The departure place S is registered in the traveling point list (FIG. 12), and the top data of the user information record, which is the user information data, is acquired (step 6).
[0042]
  The head data UA in the embodiment of the user information recording in FIG. 9 is as follows.
[0043]
  Type code: 0x5112 Name: Convenience store 1
  Total stop-off time: 1150 minutes Date of stop: 00328
  Time of stop: 2015 Visit coefficient: 0.92
  Processing is performed on this acquired data (step 7). If the course type indicated in the round trip pickup condition is travel, step 8 is executed, and if not, step 10 is executed. In the embodiment of FIG. 8, step 8 is executed because the course type is travel.
[0044]
  The type code indicated in the data acquired from the user information record is determined (step 8). If the type code is travel-related, the loop point list creation process of step 9 is executed. Do not execute. Since the type code of the acquired user information record data UA is related to life, step 9 is not executed, and the next data of the user information record is acquired (step 13). It is determined whether or not the user information recording is finished (step 14), and if finished, step 15 is executed. If not finished, the process returns to step 7 and the above processing is repeatedly executed.
[0045]
  The user information record data UB and the data UC type codes are also related to daily life, and the next step UD and subsequent steps are followed to acquire the next data UD of the user information record and perform processing.
[0046]
  Type code: 0x3611  Name: Ski resort 1
  Total stop-off time: 19900 minutes Date of stop-off: 00301
  Time of stop: 1320 Visit coefficient: 0.57
  Since the type code of the data UD of the user information record is related to travel, the round point list addition process in step 9 is executed. Next, the cyclic point list addition process of FIG. 4 will be described. First, the following data MA of the map data is acquired, and the middle classification match flag is set to 0 (step 16).
[0047]
  Type code: 0x1421 Landmark name: Hakone Sekisho site
  Landmark center longitude: 139 ° 01'45 "Landmark center latitude: 35 ° 11'21"
  Nearest road: 0x1120
  Processing is performed on the acquired data MA. It is determined whether the type code coincides with the data UD of the user information record and the data MA of the map data (step 18). If they match, step 20 is executed, and if they do not match, step 19 is executed. Since the type code of the data UD being searched is 0x3611, step 19 is executed. Next, it is determined whether or not the classification code of the data UD of the user information record matches the middle classification of the classification code of the map data MA (step 23). If they match, step 25 is executed, and if they do not match, step 24 is executed. Since the type code being searched for is 0x3611, step 24 is executed. If the middle classification match flag is 1, step 34 is executed, and if it is not 1, step 29 is executed (step 24). Here, since the middle classification match flag is 0, step 29 is executed. A match between the type code of the data UD of the user information record and the large classification of the type code of the map data MA is determined (step 30).
[0048]
  If they match, step 31 and the subsequent steps are executed. If they do not match, the process jumps directly to step 34. Since the type code of the data UD being searched for is 0x3611 and the type code of the map data MA is 0x1421, the process jumps to step 34 to acquire the next data MB of the map data (step 34).
[0049]
  If the map data is terminated, the process is terminated, and if not terminated, the above step 17 and subsequent steps are repeatedly executed (step 35).
[0050]
  Since the classification codes of the map data MB to the map data MD do not match up to the major classification, the next data ME of the map data is acquired and the same processing is performed.
[0051]
  Type code: 0x3540 Landmark name: Athletic Garden
  Landmark center longitude: 139 ° 06'16 "Landmark center latitude: 35 ° 13'51"
  Nearest road: 0x01e0
  Since the classification codes of the map data ME match the major classification, the latitude, longitude, nearest road ID, etc. of landmarks necessary for the traveling point list (FIG. 12) are acquired from the map data (step 31). If data that matches the acquired latitude / longitude already exists in the circulation point list, step 34 is executed, and if not, step 33 is executed (step 32). In this case, since the circulation point list has not yet been created, the acquired data is added to the circulation point list (step 33).
[0052]
  The following data MF following the map data is acquired (step 34).
[0053]
  Type code: 0xfff Landmark name:
  Landmark center longitude: Landmark center latitude:
  Nearest road:
  Since the map data MF is end data, the round point list creation processing is ended. Returning to the cyclic point pick-up process of FIG. 3, the next data UE of the user information record is acquired and the process is performed.
[0054]
  Type code: 0x3521  Name: Leisure Land 1
Total stop-off time: 18000 minutes Date of stop-off: 4991224
  Time of stop: 2130 Visit coefficient: 0.55
  Since the type code of the data UE of the user information record is travel-related, the circulation point list addition process of FIG. 4 is executed. In the same manner as before, the process is repeated until the following map data ME is obtained.
[0055]
  Type code: 0x3540 Landmark name: Athletic Garden
  Landmark center longitude: 139 ° 06'16 "Landmark center latitude: 35 ° 13'51"
  Nearest road: 0x01e0
  Since this map data ME exists in the previously added tour point list (FIG. 12), it is not added to the list again (step 32). Since the next map data MF is end data, the round point list addition processing ends. Returning to step 13 of the cyclic point pick-up process in FIG. 3, the following data UF following the user information record is acquired and processed.
[0056]
  Type code: 0x1432  Name: Historic Site 1 Total stop-off time: 5900 minutes
  Date of stop: 980505 Time of stop: 1715
  Visiting coefficient: 0.34
  Since the type code of the data UF of the user information record is travel-related, the circulation point list addition process of FIG. 4 is executed. The following map data MA is acquired, and the process proceeds as before.
[0057]
    Type code: 0x1421  Landmark name: Hakone Sekisho site
  Landmark center longitude: 139 ° 01'45 "Landmark center latitude: 35 ° 11'21"
  Nearest road: 0x1120
  Since the classification codes of the data UF and the map data MA match the large / medium classification, the latitude and longitude of the landmark and the nearest road ID necessary for the traveling point list are acquired from the map data (step 25). Since there is no data matching the acquired latitude and longitude in the circulation point list, the acquired data is added to the circulation point list (step 27). The middle classification match flag is set to 1 (step 28). The following data MB following the map data is acquired (step 34).
[0058]
  Type code: 0x1210 Landmark name: Lake Ashi
  Landmark center longitude: 139 ° 02'01 "Landmark center latitude: 35 ° 11'51"
  Nearest road: 0x111e
  Although the map data MB and the subsequent map data MB to map data ME match in the large classification, the middle classification matching flag is already 1 (step 24).
), The same processing is repeated until the map data MF is acquired (step 34).
[0059]
  Since the next map data MF is end data (step 35), the circulation point list addition process of FIG. 4 is terminated and the process returns to the circulation point pickup process of FIG. The following data UG following the user information record is acquired and the processing is continued.
[0060]
  Type code: 0x1111 Name: National park 1 Total stop-off time: 550 minutes
  Date of stop: 99081 Time of stop: 1045
  Visiting coefficient: 0.15
  Processing is performed on the acquired data. Since the type code of the data UG of the user information record is related to travel, the round point list addition process of FIG. 4 is executed. The next map data MA is processed in the same manner as before.
[0061]
  Type code: 0x1421 Landmark name: Hakone Sekisho site
  Landmark center longitude: 139 ° 01'45 "Landmark center latitude: 35 ° 11'21"
  Nearest road: 0x1120
  Although the type code of the data UG and the map data MA match in the large classification, it already exists in the cyclic point list (step 32), so no data is added and the following data MB next to the map data is acquired. (Step 34).
[0062]
  Type code: 0x1210 Landmark name: Lake Ashi
  Landmark center longitude: 139 ° 02'01 "Landmark center latitude: 35 ° 11'51"
  Nearest road: 0x111e
  Since the type codes of the data UG and the map data MB coincide with each other in a large classification and no data exists in the cyclic point list, they are added to the cyclic point list (step 33).
[0063]
  The next map data MC and data MD are the same as described above, and no data exists in the circulation point list, so they are added to the circulation point list (step 33).
[0064]
  Subsequently, the following data ME next to the map data is acquired.
[0065]
  Type code: 0x3540 Landmark name: Athletic Garden
  Landmark center longitude: 139 ° 06'16 "Landmark center latitude: 35 ° 13'51"
  Nearest road: 0x01e0
  Since the type code of the data ME does not match even in the large classification (step 30), the next data MF of the map data is acquired (step 34). Since the map data MF is the end data, the circuit point list adding process in FIG. 4 is terminated and the process returns to the circuit point pick-up process in FIG. Since the next data UH of the user information record is the end data, the destination data E of the traveling point pickup condition (FIG. 8) is added to the traveling point list (FIG. 12) (step 15). The traveling point pick-up process in FIG. 3 is terminated, and the process returns to the course creation process in FIG.
[0066]
  The tour points in the tour point list are selected / increased in the order of visit coefficient, and the estimated visit time to the tour points (for example, the total visit time of the user information in FIG. 9 is the number of visits (not shown in the figure)) The sum of the estimated travel time between the target and the target travel time is calculated by dividing the estimated departure time and the desired arrival time at the destination or the expected stay time at the patrol point (for example, the round trip point pick-up). Within the range within the range (set in the condition (FIG. 8)), the selection of the round point and the optimum route around the round point are searched (step 4). Next, an overall view of the route, the arrival time at each traveling point, and the distance between each traveling point are displayed on the display unit 6 (step 5).
[0067]
  Thus, the series of course creation processes is completed, the initial process step 2 is executed again, and data waiting for the next pickup condition is awaited.
[0068]
  Next, the user information update operation of the user information update unit 4 will be described with reference to FIGS. When the in-vehicle information terminal starts operating by turning on the power or resetting, the user information update unit 4 is activated and waits for input of travel locus data (step 36 in FIG. 5).
[0069]
  The case where the example of the travel locus shown in FIG. 15 is input will be described. In this example, the vehicle information terminal starts operating after the power is turned off once at the place shown in FIG.
[0070]
  The travel locus shown in FIG. 15 is the following data.
[0071]
  Own vehicle longitude: 139 ° 09'54 "Own vehicle latitude: 35 ° 14'50" Vehicle speed: 0
  Date: 00403 Time: 1310 Landmark information: P1
  The landmark information (FIG. 16) designated by P1 in the landmark information section includes two pieces of data as follows.
[0072]
  Landmark information of landmark 1 in FIG. 22 (data L1 in FIG. 16)
  Type code: 0xc211 Name: Family restaurant 3
  Longitude: 139 ° 09'35 "Latitude: 35 ° 14'50"
  Landmark information of landmark 2 in FIG. 22 (data L2 in FIG. 16)
  Type code: 0x5111 Name: Convenience store 1
  Longitude: 139 ° 09'54 "Latitude: 35 ° 14'53"
  When the latest travel locus data is sent from the map control unit 2, the process shifts from step 37 in FIG. 5 to the user information update process START in FIG. First, the processed code list (FIG. 13) is initialized, and the first following data LL1 of the landmark list (FIG. 14) obtained from the immediately preceding traveling locus is acquired (step 42).
[0073]
  Type code: 0xc211 Date: 000004 Time: 1220
  Landmark Longitude: 139 ° 09'54 "Landmark Latitude: 35 ° 14'50"
  Own car longitude: 139 ° 09'54 "Own car latitude: 35 ° 14'50"
  Based on the latitude and longitude indicated by the vehicle position in the landmark list data LL1 and the vehicle position in the travel locus data in FIG. 15, the travel distance of the vehicle is determined (step 43).
[0074]
  Data LL1 vehicle position Longitude: 139 ° 09'54 "Latitude: 35 ° 14'50"
  The location of the vehicle in the travel locus data Longitude: 139 ° 09'54 "Latitude: 35 ° 14'50"
  Both positions are the same, and the moving distance of the vehicle position is 0 [m].
[0075]
  The stop time is obtained from the difference between the date and time indicated in the landmark list data LL1 and the date and time indicated in the travel locus data (step 44).
[0076]
  Date of data LL1: 00403 Time of data LL1: 1220
  Date of travel locus data: 00403 Time of travel locus data: 1310
  The drop-in time is 50 minutes from the difference between the two data.
[0077]
  It is determined whether or not both conditions that the movement of the own vehicle is less than 20 [m] and the drop-in time has passed for 3 minutes or more are satisfied (step 45). If it is determined that the vehicle has been parked and stopped, the processing from step 46 onward is executed. In this example, since both conditions are satisfied, Step 46 and subsequent steps are executed.
[0078]
  From the latitude and longitude of the landmark indicated in the landmark list data LL1 and the latitude and longitude of the subject vehicle indicated in the travel locus data, a linear distance between the subject vehicle and the landmark 1 is obtained (step 46).
[0079]
  Location of Landmark 1 Longitude: 139 ° 09'55 "Latitude: 35 ° 14'50"
  The location of the vehicle in the travel locus data Longitude: 139 ° 09'54 "Latitude: 35 ° 14'50"
  From these two data, the linear distance between the vehicle and the landmark 1 is 25 [m]. If the type code shown in the data LL1 of the landmark 1 is present in the type code shown in the processed code list, step 48 and the subsequent steps are executed. Step 47). Here, since the data has not yet been created in the processed code list, the update process of FIG. 51 (FIG. 7) is executed. Next, the update process will be described with reference to FIG.
[0080]
  If the parking lot flag, which is the most significant bit of the type code indicated in the landmark list data LL1, is 1, step 57 and the following steps are executed. If not, step 59 is executed (step 56). Since the parking lot flag of the type code (0xc211) of this data LL1 is 1, step 57 is executed, and the parking lot flag of the type code is set to 0 (step 57). In order to set the parking lot flag to 0, the type code of the data LL1 is 0x4211. The distance from the landmark 1 is corrected to 10 [m] (step 58).
[0081]
  Next, a correction coefficient for the stopping time is calculated based on the linear distance from the landmark (step 59). FIG. 17 shows an example of a graph representing the relationship between the linear distance and the drop-in time correction coefficient. Since the linear distance to the landmark 1 is 10 [m], the stop time correction coefficient is 1.0. The stopping time is corrected by multiplying the stopping time by a correction coefficient (step 60). Since the stop time correction factor is 1.0, the stop time is 50 minutes.
[0082]
  First data UA of the user information record (FIG. 9) is acquired (step 61). The user information record data whose type code matches the type code shown in the landmark list data LL1 is searched in order from the data UA (step 62). If matching data is found in the user information record, step 64 and subsequent steps are executed, and if no matching data is found, step 66 and subsequent steps are executed (step 63).
[0083]
  The following data UC matches the type code in the user information record as follows.
[0084]
  Type code: 0x4211  Name: Family Restaurant 1
  Total visit time: 1720 minutes Date of stop: 000322
  Time of stop: 1930 Visit coefficient: 0.60
  An update interval is calculated from the date and time indicated in the travel locus data (FIG. 15) and the date and time of arrival indicated in the data UC of the user information record (step 64).
[0085]
  Date of travel locus data: 00403 Time of travel locus data: 1310
  Date of data UC: 00322 Time of data UC; 1939
  The difference between the two dataRenewalThe new interval is 16900 minutes.
[0086]
  The total stoppage time calculated this time is added to the total stoppage time indicated in the data UC of the user information record to recalculate the total stopover time (step 65). That is, the stop time 50 minutes previously obtained is updated to 1770 minutes in addition to the total stop time 1720 minutes of the user information record data UC.
[0087]
  If the type code is related to life, step 72 and the subsequent steps are executed. If the type code is not related to life, step 75 and the subsequent steps are executed (step 71). Since the type code 0x4211 in this case is related to life, step 72 is executed.
[0088]
  A life-related correction coefficient is calculated from the update interval (step 72).
[0089]
  FIG. 18 is a graph showing an example of the relationship between the life-related update interval and the correction coefficient. Since the update interval is 16900 minutes, the life-related correction coefficient is 0.6.
[0090]
  A life related visit coefficient is calculated from the total stop-off time (step 73).
[0091]
  FIG. 19 is a graph showing an example of the relationship between the total visit time related to daily life and the visit coefficient. The total visit time is 1770 minutes, so the visit factor is 0.61.
[0092]
  The visit coefficient is corrected to 0.37 by multiplying the daily life related visit coefficient 0.61 by the correction coefficient 0.6 (step 74).
[0093]
  The total stoppage time, date and time of stoppage of the data UC of the user information record, and the visit coefficient are updated (step 78).
[0094]
  The user information records are rearranged in descending order of the visit coefficient, the process is terminated (step 79), and the process returns to the user information update process.
[0095]
  The type code of the landmark list 1 (step 52) and the linear distance between the landmark and the vehicle are added to the processed code list (step 53).
[0096]
  The next data of the landmark list (FIG. 14) is obtained (step 54). If the landmark list data is complete, the user information update process is terminated and the process returns to step 38 in FIG. 5. If not complete, step 46 and subsequent steps are executed again (step 55). In the embodiment, the following data LL2 following the landmark list is obtained.
[0097]
  Type code: 0x5111 Date: 00403 Time: 1220
  Landmark Longitude: 139 ° 09'54 "Landmark Latitude: 35 ° 14'53"
  Own car longitude: 139 ° 09'54 "Own car latitude: 35 ° 14'50"
  A straight line distance between the vehicle and the landmark 2 is obtained (step 46).
[0098]
  Location of Landmark 2 Longitude: 139 ° 09'54 "Latitude: 35 ° 14'53"
  The location of the vehicle in the travel locus data Longitude: 139 ° 09'54 "Latitude: 35 ° 14'50"
  From the difference between the two positions, the linear distance between the vehicle and the landmark is 93 [m]. Since the type code of the data LL2 does not exist in the data of the processed code list, the step 51 update process (FIG. 7) is executed. Since the parking flag of the type code is not 1, step 59 is executed. Since the linear distance to the landmark 2 is 93 [m], the stop time correction coefficient is 0.65. Since the stop time correction coefficient is 0.65, the stop time is corrected to 33 minutes.
[0099]
  Since no data matching the type code of data LL2 is found in the user information record data, step 66 is executed. The total stop time is set as a stop time (step 66). Total stopover time is 33 minutes. The type code indicated in the landmark list data is determined (step 67). If the type code is related to life, step 68 is executed, and if it is not related to life, step 69 is executed (step 67).
[0100]
  Since the type code 0x5111 of the data LL2 is related to life, Step 68 is executed. A life related visit coefficient is calculated from the drop-in time (step 68). The total visit time is 33 minutes, so the visit factor is 0.13. Data for each item is added to the user information record (step 70).
[0101]
  The user information records are rearranged in descending order of the visit coefficient, the process is terminated, and the process returns to the user information update process (step 79).
[0102]
  Since the landmark list is completed, the user information update process in FIG. 6 is terminated (step 55), and the process returns to the operation of the user information update unit in FIG.
[0103]
  Next, when travel locus data is input from the map control unit 2 (step 38), step 39 is executed. When the vehicle speed indicated in the travel locus data is 20 [km / h] or less, the landmark list update process (steps 40 and 41) is executed. It again waits for the input of travel locus data (step 39).
[0104]
  In the embodiment, since the vehicle speed of the travel locus data is 0 [km / h], step 40 and subsequent steps, which are the landmark list update process, are executed. All data in the current landmark list (FIG. 14) is erased (step 40), and all landmark information (FIG. 16) in the travel locus data is registered and updated in the landmark list (step 41).
[0105]
  Next, in step 38, input of travel locus data is awaited.
[0106]
  As described above, in the present invention, the user information reflecting the degree of preference / interest of the user is automatically updated from the travel locus data.
[0107]
  In the above-mentioned tour point pick-up process, the description has been made on the assumption that the necessary part is extracted from the built-in map database. However, the necessary part is extracted from the map database stored in an external service center by communication. You can also.
[0108]
  In the course creation process described above, it has been described that there is one cyclic reference point in the cyclic point pickup condition (FIG. 8). However, a plurality of cyclic reference points are set and the process is sequentially performed. Can be extended as
[0109]
  Further, reading of map data centering on the patrol reference point (step 6 in FIG. 3) is performed along the route from the starting point to the patrol reference point and the patrol reference point to the destination, or without specifying the patrol reference point. It is also possible to search for a target along the route by sequentially reading out a necessary range along the route from the departure point to the destination.
[0110]
  Further, after the tour point pick-up process (step 3 in FIG. 2) and / or after the route display (step 5 in FIG. 2), the tour points that have been taken out, that is, the target are deleted and added using conventional techniques. Needless to say, it can be done.
[0111]
  In the course creation process (FIGS. 2 to 4) and the user information update operation (FIGS. 5 to 7), the course type is limited to two types of travel and life. -Adding other types such as hobbies does not impair the essence of the present invention.
[0112]
  When the same vehicle is used by a plurality of users, user information for each user can be stored, and corresponding user information can be applied according to the user.
[0113]
  In addition, the user information can be transferred / stored on a storage medium that can be removed from the vehicle, such as an IC card, and the user information can be read from the storage medium at the start of operation to be used even if the vehicle is changed. It is also possible to create a course adapted to the preferences and interests of the person.
[0114]
【The invention's effect】
  As described above, according to the present invention, the user can learn the user's preference / interest about the target by using the traveling trajectory and perform the route search using the learning result without being particularly conscious. Thus, even in a place where the user visits for the first time, a target that matches the user's preference and interest can be selected to obtain a travel route.
[Brief description of the drawings]
FIG. 1 is a functional block diagram of an embodiment of the present invention.
FIG. 2 is a flowchart of course creation processing in an embodiment of the present invention.
FIG. 3 is a flow diagram of a cyclic point pick-up process in an embodiment of the present invention.
FIG. 4 is a flowchart of a cyclic point list addition process in the embodiment of the present invention.
FIG. 5 is a flowchart of a user information update operation in the embodiment of the present invention.
FIG. 6 is a flowchart of user information update processing in the embodiment of the present invention.
FIG. 7 is a flowchart of update processing in the embodiment of the present invention.
FIG. 8 is a diagram showing an example of a tour point pickup condition according to the present invention.
FIG. 9 is a diagram showing an example of a user information record according to the present invention.
FIG. 10 is a diagram showing an example of map data in the vicinity of the traveling reference point according to the present invention.
FIG. 11 is a diagram showing an example of a type code according to the present invention.
FIG. 12 is a diagram showing an example of a cyclic point list according to the present invention.
FIG. 13 is a diagram showing an example of a processed code list according to the present invention.
FIG. 14 is a diagram showing an example of a landmark list according to the present invention.
FIG. 15 is a diagram showing an example of travel locus data according to the present invention.
FIG. 16 is a diagram showing an example of landmark information of a traveling locus according to the present invention.
FIG. 17 is a diagram illustrating a relationship between a linear distance from a landmark and a stop time correction coefficient in the embodiment of the present invention.
FIG. 18 is a diagram showing the relationship between the life-related update interval and the correction coefficient in the embodiment of the present invention.
FIG. 19 is a diagram showing the relationship between the life-related total stop-in time and the visit coefficient in the embodiment of the present invention
FIG. 20 is a diagram showing a relationship between a travel-related update interval and a correction coefficient in the embodiment of the present invention.
FIG. 21 is a diagram showing the relationship between travel-related total stop-in time and visit coefficient in an embodiment of the present invention.
FIG. 22 is an explanatory diagram of an operation start point in an embodiment of the present invention.
[Explanation of symbols]
  1 Input data controller
  2 Map controller
  3 memory
  4 user information update department
  5 Course creation department
  6 Display section

Claims (9)

Means for creating a travel locus including landmark types;
The total drop in time to the landmark, and the user information including a visit coefficient indicating the degree of preference-interest of a user of the landmark stored in each of the landmark, and the total drop in the time to landmarks A storage unit storing a correspondence table representing a relationship between a time indicating a reference value and a coefficient indicating a reference value of a visit coefficient for each landmark ;
Based on the travel trajectory, a stoppage time for the landmark is calculated, a new total stoppage time is calculated by adding the stoppage time to the total stoppage time included in the user information, and the type of the landmark vehicle information terminal said corresponding calculated new visiting coefficients from the new total drop time according to table, characterized in that a updating means for updating the user information corresponding to. The in-vehicle information terminal according to claim 1 , further comprising means for selecting a landmark based on a visit coefficient included in the user information . Own vehicle position calculating means for calculating a current position by at least one of a satellite and a vehicle sensor;
An input means for inputting designated position data and course type data;
The means for selecting a landmark based on the visit coefficient selects a landmark in the vicinity of the current position or a specified position in the order of the visit coefficient from landmarks of the type corresponding to the course type data. The in-vehicle information terminal according to claim 2 . The update means calculates an update interval which is a time until the landmark is revisited based on a time when the landmark was visited last time and a time when the landmark was visited again. vehicle information terminal according to claim 1, wherein the modifying the visiting coefficients based on the update interval. The storage means stores the time when the landmark was last visited, and the relationship between the time indicating the reference value of the update interval and the coefficient indicating the reference value of the correction coefficient for correcting the stop time. A corresponding correspondence table is stored for each landmark type,
5. The in-vehicle information terminal according to claim 4 , wherein the updating unit obtains the correction coefficient from the update interval with reference to the correspondence table . The updating means calculates a linear distance between the vehicle and the landmark based on the vehicle position and the landmark position included in the travel locus, and the stop time is calculated based on the calculated linear distance. The in-vehicle information terminal according to claim 1 , wherein the information is corrected . The storage means stores a correspondence table representing a relationship between a distance indicating a reference value of a straight line distance between the vehicle and the landmark and a coefficient which is a reference value of a correction coefficient for correcting the stop time;
The in-vehicle information terminal according to claim 6 , wherein the updating means obtains the correction coefficient from the linear distance with reference to the correspondence table . The in-vehicle information terminal according to claim 2 , further comprising course creation means for searching for a route to the selected landmark . The in-vehicle information terminal according to claim 8 , further comprising display means for displaying the selected landmark and the tour route on a map.