Navigation system

Abstract

A navigation system includes: a storage unit having stored therein roadmap data, first statistical traffic information data pertaining to a first area which are created based upon a first standard related to a time applicable to the first area, and second statistical traffic information data pertaining to a second area which are created based upon a second standard related to a time applicable to the second area; a search unit that searches for a recommended route; and an estimated time of arrival calculation unit that calculates an estimated time of arrival based upon the roadmap data, the first statistical traffic information data and the second statistical traffic information data. The estimated time of arrival calculation unit executes calculation processing of the estimated time of arrival in compliance with the first standard and the second standard.

Claims

What is claimed is: 1. A navigation system, comprising: a search unit that searches for a route for a recommended route for a mobile body traveling from a start point located in a first mesh area to a destination in a second mesh area adjacent to the first mesh area, a first local standard time in the first mesh area and a second local standard time in the second mesh area being different from each other; a storage unit in which a length of traveling time required to travel through each of the links present in the first mesh area and a length of traveling time required to travel through each of links present in the second mesh area are stored; a determining unit that determines a departure time point at which the mobile body departs from the start point based upon the first local standard time; an estimated passing time point calculation unit that calculates a first estimated passing time point at which the mobile body is expected to pass through a waypoint on the recommended route by adding a sum of lengths of traveling time required to travel through links present in the recommended route within the first mesh area in reference to the storage unit, to the departure time point, the waypoint being present at a border between the first mesh area and the second mesh area; a conversion unit that converts the first estimated passing time point based upon the first local standard time to a second estimated passing time point based upon the second local standard time; an estimated time of arrival calculation unit that calculates an estimated time of arrival at which the mobile body is expected to arrive at the destination based upon the second local standard time by adding a sum of lengths of traveling time required to travel through links present in the recommended route within the second mesh area in reference to the storage unit, to the second estimated passing time point; and a display unit that brings up the estimated time of arrival. 2. A navigation system according to claim 1 , wherein: the determining unit further determines a date of departure on which the mobile body departs from the start point based upon the first local standard time; and the length of traveling time required to travel through each of links present in the first mesh area and the length of traveling time required to travel through each of links present in the second mesh area are stored in the storage unit in correspondence to individual day categories indicating specific day types. 3. A navigation system according to claim 1 , further comprising: a decision making unit that makes a decision as to whether or not daylight saving time is applicable, wherein: the determining unit determines the departure time point based upon the decision; the estimated passing time point calculation unit calculates the first estimated passing time point based upon the decision; the conversion unit converts the first estimated passing time point to the second estimated passing time point based upon the decision; and the estimated time of arrival calculation unit calculates the estimated time of arrival based upon the decision. 4. A navigation system according to claim 1 , wherein: the length of traveling time required to travel through each of links present in the first mesh area based upon the first local standard time and the length of traveling time required to travel through each of links present in the second mesh area are stored in the storage unit based upon the second local standard time. 5. A navigation system, comprising: a search unit that searches for a route for a recommended route for a mobile body traveling from a start point located in a first mesh area to a destination in a second mesh area adjacent to the first mesh area, a first local standard time in the first mesh area and a second local standard time in the second mesh area being different from each other; a storage unit in which a length of traveling time required to travel through each of links present in the first mesh area and the second mesh area are stored; a determining unit that determines a first departure time point at which the mobile body departs from the start point based upon a global standard time by converting a second departure time point at which the mobile body departs from the start point based upon the first local standard time to the first departure time point; an estimated time of arrival calculation unit that calculates a first estimated time of arrival at which the mobile body is expected to arrive at the destination based upon the second local standard time by adding a sum of lengths of traveling time required to travel through links present in the recommended route within the first mesh area and the second mesh area in reference to the storage unit, to the first departure time point and that converts the first estimated time of arrival to a second estimated time of arrival at which the mobile body is expected to arrive at the destination based upon the global standard time; and a display unit that brings up the second estimated time of arrival. 6. A navigation system according to claim 5 , wherein: the determining unit further determines a first date of departure on which the mobile body departs from the start point based upon the global standard time by converting a second date of departure on which the mobile body departs from the start point based upon the first local standard time to the first date of departure; and the length of traveling time required to travel through each of links present in the first mesh area and the length of traveling time required to travel through each of links present in the second mesh area are stored in the storage unit in correspondence to individual day categories indicating specific day types. 7. A navigation system according to claim 5 , further comprising: a decision making unit that makes a decision as to whether or not daylight saving time is applicable, wherein: the determining unit determines the first departure time point based upon the decision; and the estimated time of arrival calculation unit converts the first estimated time of arrival to the second estimated time of arrival based upon the decision. 8. A navigation system according to claim 5 , wherein: the length of traveling time required to travel through each of links present in the first mesh area and the second mesh area are stored in the storage unit based upon the global standard time.
INCORPORATION BY REFERENCE The disclosure of the following priority application is herein incorporated by reference: Japanese Patent Application No. 2009-225204 filed Sep. 29, 2009 and Japanese Patent Application No. 2009-225205 filed Sep. 29, 2009. BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a navigation system that executes a route search by using statistical traffic information. 2. Description of Related Art A navigation system may be capable of executing a route search operation and a required traveling time calculation by taking into consideration traffic congestion conditions based upon traffic information. However, while the route search operation and the required traveling time calculation are executed based upon the traffic information available at the time of the route search operation, the congestion conditions may change significantly while the vehicle is en route. Japanese Laid Open Patent Publication No. 2008-96445 discloses a technology whereby traffic information collected in the past is accumulated as statistical data, statistical data for individual links are extracted in correspondence to specific traffic information collection conditions having been selected, changes in the congestion conditions corresponding to various time points are superimposed over a map on display and a search for a shortest route is executed with accuracy. In addition, while the congestion conditions are bound to change as time passes following the time point at which the traffic information is obtained, an accurate search for a recommended route may be executed based upon statistical traffic data collected in the past, which correspond to a specific category of day, e.g., a weekday or a holiday, as disclosed in Japanese Laid Open Patent Publication No. 2004-239741. SUMMARY OF THE INVENTION Statistical traffic data must be used by taking into consideration time-related conditions at the start point and the destination that may not always match, e.g., the start point and the destination may be located in different time zones or located in areas observing different holidays. According to the invention disclosed in Japanese Laid Open Patent Publication No. 2008-96445, the route search is executed at the time of departure by using statistical traffic data based upon the current time point designated as a departure time point or a departure time point entered by the user. This means that the route search will be executed by using the statistical traffic data based upon the wrong time if the vehicle is to cross over into a different time zone as it travels or if the vehicle traveling in an area observing daylight saving time is to move into an area where the daylight saving time is not implemented. The second conversion table correlating dates with specific day categories according to the invention disclosed in Japanese Laid Open Patent Publication No. 2004-239741 remains unchanged unless the user performs a specific operation. This gives rise to an issue in that the route search is likely to be executed by using the statistical traffic data based upon the wrong day category as the vehicle crosses over a border into a region where different holidays are observed or crosses over a border into another country. According to the first aspect of the present invention, a navigation system comprises: a storage unit having stored therein roadmap data expressing a road map between a start point, from which a mobile body departs, and a destination for the mobile body, first statistical traffic information data pertaining to a first area where the start point is located, which are created based upon a first standard related to a time applicable to the first area, and second statistical traffic information data pertaining to a second area where the destination is located, which are created based upon a second standard related to a time applicable to the second area; a search unit that searches, based upon the roadmap data, for a recommended route for the mobile body traveling from the start point to the destination; and an estimated time of arrival calculation unit that calculates an estimated time of arrival at which the mobile body, traveling through the recommended route, is expected to arrive at the destination, based upon the roadmap data, the first statistical traffic information data and the second statistical traffic information data. The estimated time of arrival calculation unit executes calculation processing of the estimated time of arrival based upon the first statistical traffic information data in compliance with the first standard and calculates the estimated time of arrival based upon results of the calculation processing having been executed and the second statistical traffic information data in compliance with the second standard. According to the second aspect of the present invention, in the navigation system according to the first aspect, it is preferred that the navigation system further comprises: a clocking unit that clocks in a departure time point at which the mobile body departs the start point in reference to a start point local standard time in a time zone where the start point is located; an estimated passing time point calculation unit that calculates, in reference to the start point local standard time, a first estimated passing time point, indicating an estimated time point at which the mobile body is expected to pass through a waypoint on the recommended route through calculation of a traveling time length executed by referencing the first statistical traffic information data based upon the departure time point; and an acquisition unit that references the second statistical traffic information data in conjunction with a second estimated passing time point obtained by converting the first estimated passing time point to a time point in compliance with destination local standard time in a time zone where the destination is located when calculating a traveling time length and obtains the estimated time of arrival in the destination local standard time. The first standard is the start point local standard time; the second standard is the destination local standard time; and the estimated time of arrival calculation unit includes the estimated passing time point calculation unit and the acquisition unit. According to the third aspect of the present invention, in the navigation system according to the first aspect, it is preferred that the navigation system further comprises: a clocking unit that clocks in a departure time point at which the mobile body departs the start point in reference to a start point local standard time in a time zone where the start point is located. The first standard is the start point local standard time; and the second standard is a destination local standard time in the time zone where the destination is located; and the search unit searches for the traveling route by searching for a route segment extending from the start point to a waypoint on the recommended route through which the mobile body is to pass, based upon the departure time point, the first statistical traffic information data, and the start point local standard time, calculating a first estimated passing time point at which the mobile body is expected to pass through the waypoint and searching for a route segment extending from the waypoint to the destination based upon a second estimated passing time point obtained through conversion of the first estimated passing time point to a time point in compliance with the destination local standard time, the second statistical traffic information data and the destination local standard time. According to the fourth aspect of the present invention, in the navigation system according to the first aspect, it is preferred that the navigation system further comprises: a clocking unit that clocks in a first departure time point at which the mobile body departs the start point in reference to a start point local standard time in a time zone where the start point is located; a first time point calculation unit that calculates a traveling time length by referencing the first statistical traffic information data and the second statistical traffic information data in conjunction with a second departure time point obtained through conversion of the first departure time point to a time point in compliance with a global standard time so as to calculate a first expected arrival time point indicating a time point at which the mobile body is expected to arrive at the destination in the global standard time; and a second time point acquisition unit that obtains a second expected arrival time point calculated by converting the first expected arrival time point to a time point in compliance with destination local standard time in a time zone where the destination is located. Both the first standard and the second standard are the global standard time; the estimated time of arrival calculation unit includes the first time point calculation unit and the second time point acquisition unit; and the estimated time of arrival is the second expected arrival time point. According to the fifth aspect of the present invention, in the navigation system according to the first aspect, it is preferred that the navigation system further comprises: a clocking unit that clocks in a first departure time point at which the mobile body departs the start point in reference to a start point local standard time in a time zone where the start point is located. Both the first standard and the second standard are global standard time; and the search unit searches for the traveling route based upon a second departure time point obtained by converting the first departure time point to a time point in global standard time, the first statistical traffic information data and the second statistical traffic information data, and the global standard time. According to the sixth aspect of the present invention, in the navigation system according to the first aspect, it is preferred that the navigation system further comprises: a detection unit that detects a position of the mobile body; a selection unit that selects first calendar data corresponding to the first area and second calendar data corresponding to the second area among sets of calendar data for a plurality of regions; a determining unit that determines a first day category corresponding to a traveling date on which the mobile body travels through a first road segment present in the first area along the recommended route and a second day category corresponding to a traveling date on which the mobile body travels through a second road segment present in the second area along the recommended route by referencing the first calendar data and the second calendar data having been selected by the selection unit; and an arithmetic operation unit that calculates an estimated time of arrival at which the mobile body is expected to arrive at the destination based upon the first day category and the second day category determined by the determining unit, time points at which the mobile body is to travel through the first road segment and the second road segment, and the first statistical traffic information data and the second statistical traffic information data. The start point is the position of the mobile body detected by the detection unit; the first calendar data related to a calendar observed in the first area and the first day category and the second calendar data related to a calendar observed in the second area and the second day category are stored in the storage unit; the first standard is the first day category; the second standard is the second day category; and the estimated time of arrival calculation unit includes the arithmetic operation unit. According to the seventh aspect of the present invention, in the navigation system according to the sixth aspect, it is preferred that the selection unit identifies a region through which the recommended route extends based upon the roadmap data. According to the eighth aspect of the present invention, in the navigation system according to the sixth aspect, it is preferred that the navigation system further comprises: an interface unit that accepts an instruction entered by a user to specify the first area and the second area. According to the ninth aspect of the present invention, in the navigation system according to the first aspect, it is preferred that the navigation system further comprises: a detection unit that detects a position of the mobile body; a selection unit that selects first calendar data corresponding to the first area and second calendar data corresponding to the second area among sets of calendar data for a plurality of regions; and a determining unit that determines a first day category corresponding to a traveling date on which the mobile body travels through a first road segment present in the first area along the recommended route and a second day category corresponding to a traveling date on which the mobile body travels through a second road segment present in the second area along the recommended route by referencing the first calendar data and the second calendar data having been selected by the selection unit. The start point is the position of the mobile body detected by the detection unit; the first calendar data related to a calendar observed in the first area and the first day category and the second calendar data related to a calendar observed in the second area and the second day category are stored in the storage unit; the first standard is the first day category; the second standard is the second day category; and the search unit searches for the recommended route based upon the first day category and the second day category having been determined by the determining unit, time points at which the mobile body is to travel through the first road segment and the second road segment, and the first statistical traffic information data and the second statistical traffic information data. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 shows a configuration of a navigation system that may be adopted in an embodiment of the present invention. FIG. 2 illustrates how statistical traffic information stored in the auxiliary storage device may be managed. FIG. 3 presents a flowchart of the processing executed when calculating and displaying an estimated time of arrival at the destination via a selected route. FIG. 4 presents a flowchart of processing executed when calculating an estimated time of arrival at the destination based upon a global standard time (Universal Time). FIG. 5 presents a flowchart of the processing executed when calculating an estimated time of arrival at the destination based upon local standard time. FIG. 6 illustrates a route from a start point to a destination that may be determined through a search. FIG. 7 shows the overall configuration of the estimated destination arrival time calculation system. FIG. 8 presents a flowchart of processing executed when calculating and displaying the estimated time of arrival at the destination by executing route search operation in conjunction with statistical traffic information based upon Universal Time or local standard time. FIGS. 9A and 9B each present an example of a day category registration table that may be stored in the auxiliary storage device. FIG. 10 presents a flowchart of the processing executed when calculating an estimated time of arrival at the destination. FIG. 11 presents a flowchart of processing executed when calculating and displaying an estimated time of arrival at the destination by executing route search operation in conjunction with statistical traffic information corresponding to a specific day category. DESCRIPTION OF PREFERRED EMBODIMENTS FIG. 1 shows the configuration of a navigation system 100 in reference to which a first embodiment and a second embodiment are to be described. -First Embodiment- In reference to FIGS. 1 through 6 , the first embodiment of the navigation system according to the present invention, which is installed in a vehicle, is described. A CPU 110 in FIG. 1 is an arithmetic operation processing device that controls the entire navigation system 100 . The CPU 110 and its peripheral devices are connected with one another via a bus. The peripheral devices include a main storage device 115 , an auxiliary storage device 140 and a display module 150 . The main storage device 115 is constituted with a work memory used as a work area by the CPU 110 and a program memory where a control program is stored. Signals originating from a current position detection device 120 and a user input device 130 are input to the CPU 110 . The current position detection device 120 may be constituted with, for instance, a GPS sensor, a gyro sensor and a vehicle speed sensor. Time point data are included in the data input from the GPS sensor, and the CPU 110 has a clock function for correcting the current time point based upon the time point data, i.e., the CPU 110 is equipped with an internal clock and a calendar function. The user input device 130 may be constituted with a touch panel, pushbutton switches disposed around the panel, a remote control unit and a joystick. The auxiliary storage device 140 is a storage device in which roadmap data and POI (point of interest) information, i.e. information related to sightseeing spots and various types of facilities, to be used in navigation processing are stored. The auxiliary storage device 140 may be a hard disk drive, a CD or DVD in which roadmap data are stored, a flash memory or another type of recording medium, or a reader device capable of reading out roadmap data. Roadmap data provide information related to maps and include map display data, route search data and guidance data. The map display data are used to display roads and backgrounds in a road map. The route search data, which include branch information not directly related to road shapes, are mainly used when calculating through arithmetic operation a recommended route, i.e., when executing a route search. The guidance data include information indicating intersection names, road names, direction names and landmarks and are used when providing route guidance to the user based upon the recommended route having been calculated. A given road in the roadmap data is expressed as link string data with intersections and the like defined as nodes and road segments extending between nodes defined as links. A set of link string data is thus constituted with node data and link data. Node data and link data, grouped into units of mesh areas each assigned with a specific mesh code, are stored as the roadmap data. The term “mesh area” is used to refer to each of areas assuming a predetermined areal range, into which a road map is partitioned. In a mesh code storage area, a number identifying the corresponding mesh area is stored. In a link string data storage area, coordinates indicating node positions, link numbers identifying the links present between nodes and coordinates indicating the positions of interpolation points each dividing a link into shorter segments are stored. These positional coordinates are used as contour data in map display processing and locator processing. Information indicating the local time corresponding to each mesh area and information indicating a daylight saving time observation period in each mesh area are stored together with the roadmap data in the auxiliary storage device 140 . Statistical traffic information is also managed in correspondence to individual mesh codes at the auxiliary storage device 140 . The statistical traffic information is to be described in detail in reference to FIG. 2 later. The display module 150 brings up a screen display of image data containing text and graphics, which are output from the CPU 110 . FIG. 2 illustrates how the statistical traffic information stored in the auxiliary storage device 140 may be managed. As explained earlier, the statistical traffic information is managed in units of individual mesh codes. The statistical traffic information corresponding to mesh code #x_ 1 assumes a hierarchically layered structure and is stored in correspondence to primary day categories indicating specific day types. There may be five different day categories; “weekday (regular day), weekday (day before holiday)”, “holiday (first day of consecutive holidays)”, “holiday (middle day of consecutive holidays)” and “holiday (last day of consecutive holidays)”. Since the characteristics of traffic conditions vary with the day categories, the statistical traffic information is managed in correspondence to the individual day categories. In the next hierarchical layer after the day category layer, statistical information is stored in correspondence to each of the link numbers indicating the links contained in the mesh area represented by mesh code #x_ 1 . For instance, the statistical traffic information stored in correspondence to link number #y_ 1 is organized in correspondence to different time frames in the subsequent hierarchical layer. The statistical traffic information for a time frame 0:00 through 1:00, among the time frames, indicates a traveling time of 257 seconds and congestion level 1 in the example presented in FIG. 2 . This means that the length of time required to travel through the link represented by link number #y_ 1 in the mesh area assigned with mesh code #x_ 1 is estimated to be 257 seconds in the time frame between 0:00 a.m. and 1:00 a.m. and that the conditions of traffic congestion experienced by the vehicle are likely to be level 1 . Next, the route search processing executed by using statistical traffic information in the navigation system 100 in the embodiment is described in detail. The processing executed by using timeframe-by-timeframe statistical traffic information, such as that shown in FIG. 2 , managed in correspondence to different time frames based upon a global standard time (Universal Time) and the processing executed by using timeframe-by-timeframe statistical traffic information based upon local standard time are individually explained in reference to FIGS. 3 through 6 . FIG. 6 presents an example of a route from a start point S to a destination G that may be determined through a search. Mesh areas M 10 and M 20 are adjacent to each other. The searched route is made up with links L 11 , L 12 and L 21 . While the links L 11 and L 12 are present in the mesh area M 10 , the link L 21 is present in the mesh area M 20 . The link L 11 connects the start point S to a waypoint P 1 , the link L 12 connects the waypoint P 1 to a waypoint P 2 and the link L 21 connects the waypoint P 2 to the destination G. (1) Route search execution processing with timeframe-by-timeframe statistical traffic information based upon Universal Time. The navigation system 100 determines the date/time of departure and a specific day of the week on which the date falls (hereafter “the date/time and a specific day of the week” is to be referred to as a “time point and the like”) by engaging the clock function of the CPU 110 at which the local standard time is set, and then converts the time point and the like to time point and the like in Universal Time. Next, the lengths of traveling time likely to be required to travel through the links L 11 , L 12 and L 21 in Universal Time are read out from the timeframe-by-timeframe statistical traffic information managed as shown in FIG. 2 . The lengths of link traveling time are added to the departure time point and the like in order to calculate an estimated time of arrival at the destination in Universal Time, the estimated time of arrival and the like thus calculated are then converted to an estimated time of arrival and the like in local standard time matching the setting at the clock function in the CPU 110 and the estimated time of arrival and the like in local standard time are brought up on display at the panel in the display module 150 . It is to be noted that if the mesh areas M 10 and M 20 are located in different time zones, the estimated time of arrival will be converted to an estimated time of arrival at the destination in the local standard time in the time zone of the destination and the estimated time of arrival resulting from the conversion will be brought up on display at the panel in the display module 150 . When the vehicle travels through areas located in different time zones, as described above, the processing must be executed by taking into consideration whether or not daylight saving time is applicable in each area. The time difference between the local time at the start point and the local time at the destination may also be indicated to the user in the form of a message brought up in a screen display or a voice message. (2) Route search execution processing with timeframe-by-timeframe statistical traffic information managed in correspondence to different time frames based upon the local standard time. The navigation system 100 determines the departure time point and the like by engaging the clock function of the CPU 110 at which the local standard time is set. Next, the lengths of traveling time likely to be required to travel through the links L 11 , L 12 and L 21 in local standard time are read out from the timeframe-by-timeframe statistical traffic information managed as shown in FIG. 2 . The lengths of link traveling time are added to the departure time point and the like so as to calculate an estimated time of arrival at the destination and the like, which are then brought up on display at the panel in the display module 150 . It is to be noted that if the mesh areas M 10 and M 20 are located in different time zones, the lengths of traveling time likely to be required to travel through the links present in the mesh area M 10 will be read out and then a time point at which the subject vehicle is likely to travel through the border between the mesh areas will be determined by adding the sum of the lengths of link traveling time likely to be required to travel through the links present within the mesh area M 10 to the departure time point and the like. When the vehicle travels through areas located in different time zones, as described above, the processing must be executed by taking into consideration whether or not daylight saving time is applicable in each area. The time point at which the subject vehicle is expected to travel through the border between the mesh areas, initially determined in local time in the time zone of the mesh area M 10 , will be converted to a time point in the local standard time in the time zone of the mesh area M 20 , through which the subject vehicle having driven through the border is to travel, is located. An estimated time of arrival at the destination in the local standard time in the time zone of the mesh area M 20 , obtained by reading out the lengths of traveling time likely to be required to travel through the links in the mesh area M 20 and adding the sum of the link traveling time lengths to the time point at which the subject vehicle is expected to cross the border in the local standard time in the time zone of the mesh area M 20 , will then be brought up on display at the panel in the display module 150 . The time difference between the local time at the start point and the local time at the destination may also be indicated to the user in the form of a message brought up in a screen display or a voice message. FIG. 3 presents a flowchart of the route search arithmetic operation processing and the processing for calculating and displaying an estimated time of arrival at the destination through the selected route, executed by the CPU 110 in the navigation system 100 . In step S 301 , the current position of the vehicle equipped with the navigation system 100 is detected via the current position detection device 120 . In step S 302 , a decision is made as to whether or not instructions for setting a destination and executing route search arithmetic operation, issued by the user via the user input device 130 , have been received. Until these execution instructions are received, step S 302 is repeatedly executed in this processing procedure. Once the execution instructions have been received, the route search arithmetic operation is executed in step S 303 . In step S 304 , route search results are brought up on display at the display panel of the display module 150 . In step S 305 , a decision is made as to whether or not an instruction for executing route selection, issued by the user via the user input device 130 , has been received. Until this execution instruction is received, step S 305 is repeatedly executed in this processing procedure. Once the execution instruction has been received, an estimated destination arrival time calculation subroutine, to be detailed later, is executed in step S 306 . The estimated time of arrival at the destination, resulting from the subroutine, is brought up on display at the display panel of the display module 150 in step S 307 , and then the processing procedure ends. FIGS. 4 and 5 each present a flowchart of the estimated destination arrival time calculation subroutine mentioned above. As explained earlier, the timeframe-by-timeframe statistical traffic information in FIG. 2 may be managed based upon Universal Time or based upon the local standard time. The estimated destination arrival time calculation processing procedure executed based upon timeframe-by-timeframe statistical traffic information managed based upon Universal Time is described in reference to FIG. 4 . The estimated destination arrival time calculation processing procedure executed based upon timeframe-by-timeframe statistical traffic information managed based upon local standard time is described in reference to FIG. 5 . FIG. 4 shows the procedure for the estimated destination arrival time calculation processing subroutine executed based upon Universal Time in step S 306 in FIG. 3 . In step S 401 , the current date/time, ascertained via the clock function of the CPU 110 , is converted to a time point T based upon Universal Time. In step S 402 , n mesh areas through which the selected route extends are sorted in the order in which the subject vehicle, traveling from the start point toward the destination, passes through the individual mesh areas (i=1, 2, . . . n). Subsequently, the sequence of processing from step S 403 through step S 412 and step S 413 is repeatedly executed for all the mesh areas i=1 through n. In step S 403 , a time point T′ in local standard time of the time zone of the mesh area #i is set based upon latitude/longitude information by referencing the local standard time information stored in the auxiliary storage device 140 . In step S 404 , a decision is made as to whether or not daylight saving time is applicable in the mesh area #i by referencing daylight saving time information stored in the auxiliary storage device 140 . If an affirmative decision is made, the time point T′ is adjusted by factoring in daylight saving time in step S 405 before the processing proceeds to step S 406 . If, on the other hand, a negative decision is made, the processing directly proceeds to step S 406 . In step S 406 , the estimated time points T and T′ at which the subject vehicle is expected to enter the mesh area #i are stored into the main storage device 115 or the auxiliary storage device 140 . In step S 407 , the link numbers assigned to the links constituting the selected route are sorted in the order in which the corresponding links are to be traveled (j=1, 2, . . . m). Subsequently, the sequence of processing from step S 408 through step S 410 and step S 411 is repeatedly executed for all the links j=1 through m. In step S 408 , the length of traveling time t_ij likely to be required to travel through the link #j at the time point T is searched by referencing the statistical traffic information stored in correspondence to the individual mesh codes in the auxiliary storage device 140 . In step S 409 , estimated time points T and T′ at which the vehicle is expected to finish traveling through the link #j, determined based upon the traveling time t_ij for the link #j, are stored into the main storage device 115 or the auxiliary storage device 140 . In step S 410 , a decision is made as to whether or not j is equal to m (“j=m?”) so as to determine whether or not expected travel end time points T and T′ have been calculated for all the links present in the mesh area #i. If a negative decision is made, j is incremented to j+1 in step S 411 and the processing returns to step S 408 . However, if an affirmative decision is made, the processing proceeds to step S 412 . In step S 412 , a decision is made as to whether or not i is equal to n (“i=n?”) so as to determine whether or not expected travel end time points T and T′ have been calculated for all the mesh areas through which the selected route extends. If a negative decision is made, i is incremented to i+1 in step S 413 and the processing returns to step S 403 . However, if an affirmative decision is made, the processing proceeds to step S 414 . Once the estimated destination arrival time points T and T′ have been stored in step S 414 , the subroutine ends and the processing returns to the main routine in FIG. 3 . FIG. 5 shows the procedure for the estimated destination arrival time calculation processing subroutine executed based upon the local standard time in step S 306 in FIG. 3 . In step S 501 , the current date/time, ascertained via the clock function of the CPU 110 , is set as a time point T in local standard time. In step S 502 , n mesh areas through which the selected route extends are sorted in the order in which the subject vehicle, traveling from the start point toward the destination, passes through the individual mesh areas (i=1, 2, . . . , n). Subsequently, the sequence of processing from step S 503 through step S 512 and step S 513 is repeatedly executed for all the mesh areas i=1 through n. In step S 503 , a time point T in local standard time of the time zone of the mesh area #i is set based upon latitude/longitude information by referencing the local standard time information stored in the auxiliary storage device 140 . In step S 504 , a decision is made as to whether or not daylight saving time is applicable in the mesh area #i by referencing daylight saving time information stored in the auxiliary storage device 140 . If an affirmative decision is made, the time point T is adjusted by factoring in daylight saving time in step S 505 before the processing proceeds to step S 506 . If, on the other hand, a negative decision is made, the processing directly proceeds to step S 506 . In step S 506 , an estimated time point T at which the subject vehicle is expected to enter the mesh area #i is stored into the main storage device 115 or the auxiliary storage device 140 . In step S 507 , the link numbers assigned to the links constituting the selected route are sorted in the order in which the corresponding links are to be traveled (j=1, 2, . . . , m). Subsequently, the sequence of processing from step S 508 through step S 510 and step S 511 is repeatedly executed for all the links j=1 through m. In step S 508 , the length of traveling time t_ij likely to be required to travel through the link #j at the time point T is searched by referencing the statistical traffic information stored in correspondence to the individual mesh codes in the auxiliary storage device 140 . In step S 509 , an estimated time point T at which the vehicle is expected to finish traveling through the link #j, determined based upon the traveling time t_ij for the link #j, is stored into the main storage device 115 or the auxiliary storage device 140 . In step S 510 , a decision is made as to whether or not j is equal to m (“j=m?”) so as to determine whether or not expected travel end time points T have been calculated for all the links present in the mesh area #i. If a negative decision is made, j is incremented to j+1 in step S 511 and the processing returns to step S 508 . However, if an affirmative decision is made, the processing proceeds to step S 512 . In step S 512 , a decision is made as to whether or not i is equal to n (“i=n?”) so as to determine whether or not expected travel end time points T have been calculated for all the mesh areas through which the selected route extends. If a negative decision is made, i is incremented to i+1 in step S 513 and the processing returns to step S 503 . However, if an affirmative decision is made, the processing proceeds to step S 514 . Once the estimated destination arrival time point T has been stored in step S 514 , the subroutine ends and the processing returns to the main routine in FIG. 3 . The navigation system 100 achieved in the first embodiment described above is structured so that information indicating the local standard time in each mesh area and information indicating the period of time during which daylight saving time is applicable in each mesh area are stored in advance together with roadmap data. As a result, an advantage is achieved in that even when the subject vehicle is to travel through different time zones, a route search can be reliably executed by using statistical traffic information. -Variations of the First Embodiment- The navigation system 100 achieved in the first embodiment as described above allows for the following variations. (1) While the local standard time and the daylight saving schedule are ascertained in correspondence to each mesh area in the processing shown in FIGS. 4 and 5 , these factors may be considered in correspondence to each link or each local region instead. (2) The procedure for the estimated destination arrival time calculation processing executed with timeframe-by-timeframe statistical traffic information, such as that shown in FIG. 2 , managed based upon Universal Time and the procedure of the estimated destination arrival time calculation processing executed with timeframe-by-timeframe statistical traffic information managed based upon the local standard time have been described in reference to FIGS. 4 and 5 respectively. The operation in the navigation system may be executed by switching over from one of the two types of estimated destination arrival time calculation processing described above to the other. Such a switchover may be triggered by, for instance, a flag value indicating whether the timeframe-by-timeframe statistical traffic information is currently managed based upon Universal Time or local standard time or triggered in response to a user input operation. (3) While the estimated destination arrival time calculation processing procedure is executed to determine an estimated time of arrival at the destination through a route selected based upon the results of a search before the vehicle equipped with the navigation system 100 departs the start point in the processing shown in FIG. 3 , the estimated destination arrival time calculation processing procedure may also be executed with a given timing after departing the start point so as to indicate the estimated time of arrival at the destination with an even higher level of accuracy. (4) In the processing described in reference to FIG. 3 , the estimated destination arrival time calculation processing is executed by using statistical traffic information stored in the navigation system 100 . As an alternative, the navigation system 100 installed in a vehicle 10 may further include a communication module 160 , statistical traffic information may be stored in a server 40 connected to a communication network 30 , and the navigation system 100 may download an estimated time of arrival at the destination calculated through estimated destination arrival time calculation processing executed at the server 40 , via the communication network 30 and an access point 20 , as illustrated in FIG. 7 . (5) In the processing described in reference to FIG. 3 , the navigation system 100 executes route search arithmetic operation in step S 303 to determine a route from the current position to the destination. Then, in step S 306 the navigation system calculates an estimated time of arrival at the destination for the route selected in step S 305 . However, the processing may be executed by adopting an alternative method such as that shown in FIG. 8 . FIG. 8 presents a flowchart of the processing for executing route search arithmetic operation with statistical traffic information based upon Universal Time or the local standard time and calculating and displaying an estimated time of arrival at the destination. The processing in this figure differs from that in FIG. 3 in that processing steps S 803 and S 804 are executed in place of processing steps S 303 , S 304 and S 307 in FIG. 3 . Provided that the timeframe-by-timeframe statistical traffic information is managed and stored based upon Universal Time, the current time point in local standard time in the time zone of the start point is first converted to a current time point indicated in Universal Time and then an arithmetic operation is executed to search for routes between the current position and the destination by using the timeframe-by-timeframe statistical traffic information corresponding to the current time point resulting from the conversion in step S 803 . If, on the other hand, the timeframe-by-timeframe statistical traffic information is managed and stored based upon local standard time, an arithmetic operation is executed to search for routes between the current position and the destination by using corresponding timeframe-by-timeframe statistical traffic information based upon the local standard time in each of the mesh areas present between the current position and the destination. As a result, in addition to various routes extending between the current position and the destination, estimated time points of arrival at the destination through those routes can be determined. Accordingly, in step S 804 , the estimated time points of arrival at the destination in local standard time in the time zone of the destination are displayed, together with the route search results, at the display panel of the display module 150 . It is preferable that upon receiving in step S 305 an instruction issued by the user for executing route selection, the processing proceed to step S 307 to display the estimated time of arrival at the destination through the selected route at the display panel of the display module 150 before ending the estimated destination arrival time calculation processing procedure. (6) While the present invention is adopted in the navigation system 100 in the first embodiment and the variations thereof described above, the present invention is not limited to this example and it may be adopted in a PND (personal navigation device), a PDA (personal digital assistant), a mobile telephone, a portable personal computer or a portable game machine. -Second Embodiment- In reference to FIGS. 1 through 3 , 6 , 9 A, 9 B and 10 , the second embodiment achieved by installing the navigation system according to the present invention in a vehicle is described. While the navigation system 100 in the embodiment assumes a structure identical to that of the navigation system in the first embodiment, already described in reference to FIG. 1 , calendar data and day category registration tables each correlating calendar dates with day categories are also stored in the auxiliary storage device 140 in addition to the statistical traffic information shown in FIG. 2 . The day category registration tables, to be described in detail later in reference to FIGS. 9A and 9B , are each created in correspondence to a specific region based upon the calendar data pertaining to the particular region. FIGS. 9A and 9B each present an example of a date category registration table that may be stored in the auxiliary storage device 140 . As described earlier, calendar dates are correlated to specific day categories in a day category registration table. The table in FIG. 9A indicates day categories designated to the five days starting on Aug. 28 (Thursday) 2008, when Sep. 1 (Monday), 2008 is a holiday. To be more specific, Aug. 28 (Thursday) 2008, is categorized as “weekday (regular day)”, the 29th (Friday) is categorized as “weekday (day before holiday)”, the 30th (Saturday) is categorized as “holiday (first day of consecutive holidays)”, the 31st (Sunday) is categorized as “holiday (middle day of consecutive holidays)” and Sep. the 1st (Monday), 2008 is categorized as “holiday (last day of consecutive holidays)”. In a given region in, for instance, the United States of America, holidays set forth by the state government are observed in addition to holidays set forth by the national government. For this reason, while the date category registration table for state A may indicate the day category designations in FIG. 9A , the day category registration table for state B adjacent to state A may indicate Aug. 28 (Thursday) 2008 categorized as “weekday (day before holiday)”, the 29th (Friday) categorized as “holiday (first day of consecutive holidays)”, and the 30th (Saturday) categorized as “holiday (middle day of consecutive holidays)” as shown in FIG. 9B . The route search execution processing executed in the navigation system 100 by using statistical traffic information in the embodiment is now described in detail. It is assumed that the mesh area M 10 in FIG. 6 is located in state A. Accordingly, statistical traffic information is used by referencing the day category registration table in FIG. 9A . Since the mesh area M 20 is located in state B, statistical traffic information is used by referencing the day category registration table in FIG. 9B . As the subject vehicle departs the start point S on, for instance, Aug. 29 (Friday), 2008, the latitudes/longitudes of the start point S, the destination G and the like are determined based upon input signals provided from the current position detection device 120 . Thus, the navigation system 100 is able to locate the start point S in the mesh area M 10 , i.e., state A, by referencing the roadmap data stored in the auxiliary storage device 140 . It is likewise able to locate the destination G in the mesh area M 20 , i.e., state B. As FIGS. 9A and 9B indicate, Aug. 29 (Friday), 2008, which falls on a weekday (day before holiday) in state A where the start point S is located, is designated as a holiday (first day of consecutive holidays) in state B where the destination G is located. The link traveling time lengths for the links L 11 , L 12 and L 21 are read out from the timeframe-by-timeframe statistical traffic information shown in FIG. 2 , in correspondence to the specific day categories having been determined as described above. While the link traveling time lengths for the links L 11 and L 12 correspond to a weekday (day before holiday), the link traveling time length for the link L 21 corresponds to a holiday (first day of consecutive holidays). The estimated time of arrival at the destination G is calculated by adding the sum of the link traveling time lengths to the departure time point and the calculated estimated time of arrival is brought up on display at the panel of the display module 150 . The CPU 110 of the navigation system 100 executes the route search arithmetic operation processing and the processing for calculating and displaying an estimated time of arrival at the destination through the selected route by following the procedural steps having already been described in reference to the flowchart presented in FIG. 3 . FIG. 10 presents a flowchart of the estimated destination arrival time calculation processing subroutine executed in step S 306 in FIG. 5 . In step S 1001 , the current date/time, ascertained via the clock function of the CPU 110 , is set as a time point T. In step S 1002 , n mesh areas through which the selected route extends are sorted in the order in which the subject vehicle, traveling from the start point toward the destination, passes through the individual mesh areas (i=1, 2, . . . , n). Subsequently, the sequence of processing from step S 1003 through step S 1010 and step S 1011 is repeatedly executed for all the mesh areas i=1 through n. In step S 1003 , an estimated time point T at which the subject vehicle is expected to enter the mesh area #i is stored into the main storage device 115 or the auxiliary storage device 140 . In step S 1004 , the link numbers assigned to the links constituting the selected route are sorted in the order in which the corresponding links are to be traveled (j=1, 2, . . . , m). Subsequently, the sequence of processing from step S 1005 through step S 1008 and step S 1009 is repeatedly executed for all the links j=1 through m. In step S 1005 , the region where the link #j in the mesh area #i is located, is identified based upon the roadmap data stored in the auxiliary storage device 140 and a specific day category X designated to the current date/time is identified by referencing the day category registration table corresponding to the particular region. In step S 1006 , the length of traveling time t_ij likely to be required to travel through the link #j at the time point T on the day categorized as X is searched by referencing the statistical traffic information stored in correspondence to the individual mesh codes in the auxiliary storage device 140 . In step S 1007 , an estimated time point T at which the vehicle is expected to finish traveling through the link #j, determined based upon the traveling time t_ij for the link #j, is stored into the main storage device 115 or the auxiliary storage device 140 . In step S 1008 , a decision is made as to whether or not j is equal to m (“j=m?”) so as to determine whether or not expected travel end time points T have been calculated for all the links present in the mesh area #i. If a negative decision is made, j is incremented to j+1 in step S 1009 and the processing returns to step S 1005 . However, if an affirmative decision is made, the processing proceeds to step S 1010 . In step S 1010 , a decision is made as to whether or not i is equal to n (“i=n?”) so as to determine whether or not expected travel end time points T have been calculated for all the mesh areas through which the selected route extends. If a negative decision is made, i is incremented to i+1 in step S 1011 and the processing returns to step S 1003 . However, if an affirmative decision is made, the processing proceeds to step S 1012 . Once the estimated destination arrival time point T has been stored in step S 1012 , the subroutine ends and the processing returns to the main routine in FIG. 3 . The navigation system 100 achieved in the second embodiment as described by is structured so that day category registration tables prepared in correspondence to individual regions are stored in advance in the auxiliary storage device 140 . Thus, statistical traffic information corresponding to a specific day category determined by referencing a day category registration table selected in correspondence to the region where the selected route determined based upon search results is located, can be extracted. As a result, even when the subject vehicle travels through a route crossing over from one region to another where different holidays are observed, the navigation system 100 is able to calculate an accurate estimated time of arrival at the destination by executing a route search with optimal statistical traffic information. -Variations of the Second Embodiment- The navigation system 100 achieved in the second embodiment as described above allows for the following variations. (1) While the navigation system 100 in the second embodiment described above detects the current position via the current position detection device 120 and automatically selects the day category registration table corresponding to the region where the detected current position is located, a day category registration table may be manually selected and set when executing the route search arithmetic operation, instead. For instance, the user may issue an instruction for the CPU 110 for setting a day category registration table via the user input device 130 and the CPU 110 , in response to the instruction, may bring up on display a calendar at the panel of the display module 150 . In this case, as the user specifies a target calendar day, selects a corresponding day category and confirms the selection, a day category registration table will be set and selected. If, on the other hand, a day category registration table can be selected exclusively from the day category registration tables stored in advance in the auxiliary storage device 140 , the user may enter the name of the region in which the route is located and the CPU 110 may select the specific day category registration table corresponding to the entered region name by reading it out from the auxiliary storage device 140 . Day category registration tables each corresponding to a plurality of regions sharing a given holiday calendar may be classified as a type 1 table, a type 2 table, . . . and the like and, in such a case, the user may select a day category registration table by specifying the type number assigned to the particular day category registration table instead of entering the name of the region. (2) The navigation system 100 in the second embodiment described above determines the day category corresponding to the current date/time by referencing the day category registration table for the region in order to calculate the link traveling time length based upon statistical traffic information retrieved in correspondence to the day category. As an alternative, the day category corresponding to the current date/time may be determined by referencing calendar data available in correspondence to each region. (3) In the second embodiment described above, day category registration tables for various regions are created based upon calendar data for the individual regions and the day category registration tables are then stored into the auxiliary storage device 140 in advance. As an alternative, the navigation system 100 may further include a communication module and download via the communication module calendar data for various regions from a server connected to a communication network. (4) In the processing described in reference to FIG. 3 , the navigation system 100 executes route search arithmetic operation in step S 303 to search for routes from the current position to the destination and then calculates an estimated time of arrival at the destination in step S 306 for the route selected in step S 305 . However, the processing may be executed by adopting an alternative method such as that shown in FIG. 11 . FIG. 11 presents a flowchart of the processing for executing a route search arithmetic operation with statistical traffic information corresponding to a specific day category and calculating and displaying estimated destination arrival time points. The processing in this figure differs from that in FIG. 3 in that processing steps S 1103 and S 1104 is executed in place of processing steps S 303 , S 304 and S 307 in FIG. 3 . In step S 1103 , day category registration tables corresponding to the regions where the mesh areas present between the current position detected via the current position detection device 120 and the destination are located, are selected from the day category registration tables stored in the auxiliary storage device 140 , day categories are determined by referencing the selected day category registration tables and route search arithmetic operation is executed to search for routes between the current position and the destination by using timeframe-by-timeframe statistical traffic information corresponding to the day categories. As a result, in addition to various routes extending between the current position and the destination, estimated time points of arrival at the destination through those routes can be determined. Accordingly, in step S 1104 , the estimated time points of arrival at the destination are displayed, together with the route search results, at the display panel of the display module 150 . It is desirable that upon receiving in step S 305 an instruction issued by the user for executing route selection, the processing proceed to step S 307 to display the estimated time of arrival at the destination through the selected route at the display panel of the display module 150 before ending the estimated destination arrival time calculation processing procedure. (5) While the present invention is adopted in the navigation system 100 in the second embodiment and the variations thereof described above, the present invention is not limited to this example and it may be adopted in a PND, a PDA, a mobile telephone, a portable personal computer or a portable game console. The first and second embodiments and the variations thereof described above may be adopted in combination. In addition, as long as functions characterizing the present invention are not compromised, the present invention is in no way limited to any of the devices structured and configured as has been described in reference to the embodiments.

Description

Topics

Download Full PDF Version (Non-Commercial Use)

Patent Citations (16)

    Publication numberPublication dateAssigneeTitle
    JP-2004239741-AAugust 26, 2004Xanavi Informatics Corp, 株式会社ザナヴィ・インフォマティクスナビゲーション装置の経路探索方法および交通情報表示方法
    JP-2005121425-AMay 12, 2005Xanavi Informatics Corp, 株式会社ザナヴィ・インフォマティクスナビゲーション装置の経路探索方法
    JP-2008083918-AApril 10, 2008Aisin Aw Co Ltd, アイシン・エィ・ダブリュ株式会社Navigation device
    JP-2008096445-AApril 24, 2008Xanavi Informatics Corp, 株式会社ザナヴィ・インフォマティクスRoute searching method of navigation device and traffic information displaying method
    JP-2008241466-AOctober 09, 2008Clarion Co Ltd, クラリオン株式会社Method of estimating traveling time, navigation device, and program
    JP-4297513-B1July 15, 2009株式会社ナビタイムジャパン経路探索システム、経路探索サーバおよび経路探索方法
    US-2005206534-A1September 22, 2005Hitachi, Ltd.Traffic information prediction apparatus
    US-2007162222-A1July 12, 2007Yoshinori Endo, Shinichi AmayaRoute search method for navigation device
    US-2008077314-A1March 27, 2008Aisin Aw Co., Ltd.Navigation device
    US-2011040438-A1February 17, 2011Harman Becker Automotive Systems GmbhMethod of estimating a propulsion-related operating parameter
    US-2011077855-A1March 31, 2011Clarion Co., Ltd.Navigation System
    US-2011246054-A1October 06, 2011Navitime Japan Co., Ltd.Route searching system, route searching server and route searching method
    US-7355528-B2April 08, 2008Hitachi, Ltd.Traffic information providing system and car navigation system
    US-7822540-B2October 26, 2010Aisin Aw Co., Ltd.Systems, methods, and programs for determining a travel-related time
    US-7894981-B2February 22, 2011Hitachi, Ltd.Traffic information providing system and car navigation system
    US-7899611-B2March 01, 2011Inrix, Inc.Detecting anomalous road traffic conditions

NO-Patent Citations (1)

    Title
    The Extended European Search Report dated Feb. 3, 2011 (Six (6) pages).

Cited By (33)

    Publication numberPublication dateAssigneeTitle
    US-2014100772-A1April 10, 2014Clarion Co., Ltd.Navigation System
    US-2014309929-A1October 16, 2014Christopher P. RicciTravel itinerary based on user profile data
    US-9020697-B2April 28, 2015Flextronics Ap, LlcVehicle-based multimode discovery
    US-9058703-B2June 16, 2015Flextronics Ap, LlcShared navigational information between vehicles
    US-9082238-B2July 14, 2015Flextronics Ap, LlcSynchronization between vehicle and user device calendar
    US-9082239-B2July 14, 2015Flextronics Ap, LlcIntelligent vehicle for assisting vehicle occupants
    US-9117318-B2August 25, 2015Flextronics Ap, LlcVehicle diagnostic detection through sensitive vehicle skin
    US-9123186-B2September 01, 2015Flextronics Ap, LlcRemote control of associated vehicle devices
    US-9135764-B2September 15, 2015Flextronics Ap, LlcShopping cost and travel optimization application
    US-9142071-B2September 22, 2015Flextronics Ap, LlcVehicle zone-based intelligent console display settings
    US-9142072-B2September 22, 2015Flextronics Ap, LlcInformation shared between a vehicle and user devices
    US-9147296-B2September 29, 2015Flextronics Ap, LlcCustomization of vehicle controls and settings based on user profile data
    US-9147297-B2September 29, 2015Flextronics Ap, LlcInfotainment system based on user profile
    US-9147298-B2September 29, 2015Flextronics Ap, LlcBehavior modification via altered map routes based on user profile information
    US-9153084-B2October 06, 2015Flextronics Ap, LlcDestination and travel information application
    US-9183685-B2November 10, 2015Autoconnect Holdings LlcTravel itinerary based on user profile data
    US-9218698-B2December 22, 2015Autoconnect Holdings LlcVehicle damage detection and indication
    US-9230379-B2January 05, 2016Autoconnect Holdings LlcCommunication of automatically generated shopping list to vehicles and associated devices
    US-9235941-B2January 12, 2016Autoconnect Holdings LlcSimultaneous video streaming across multiple channels
    US-9239241-B2January 19, 2016Clarion Co., Ltd.Navigation system
    US-9290153-B2March 22, 2016Autoconnect Holdings LlcVehicle-based multimode discovery
    US-9305411-B2April 05, 2016Autoconnect Holdings LlcAutomatic device and vehicle pairing via detected emitted signals
    US-9317983-B2April 19, 2016Autoconnect Holdings LlcAutomatic communication of damage and health in detected vehicle incidents
    US-9349234-B2May 24, 2016Autoconnect Holdings LlcVehicle to vehicle social and business communications
    US-9373207-B2June 21, 2016Autoconnect Holdings LlcCentral network for the automated control of vehicular traffic
    US-9378601-B2June 28, 2016Autoconnect Holdings LlcProviding home automation information via communication with a vehicle
    US-9378602-B2June 28, 2016Autoconnect Holdings LlcTraffic consolidation based on vehicle destination
    US-9384609-B2July 05, 2016Autoconnect Holdings LlcVehicle to vehicle safety and traffic communications
    US-9412273-B2August 09, 2016Autoconnect Holdings LlcRadar sensing and emergency response vehicle detection
    US-9524597-B2December 20, 2016Autoconnect Holdings LlcRadar sensing and emergency response vehicle detection
    US-9536361-B2January 03, 2017Autoconnect Holdings LlcUniversal vehicle notification system
    US-9646439-B2May 09, 2017Autoconnect Holdings LlcMulti-vehicle shared communications network and bandwidth
    US-9883209-B2January 30, 2018Autoconnect Holdings LlcVehicle crate for blade processors