Method for generating expected average travel speed
Through historical data, the expected average travel speed and blockage probability of sections in the electronic navigation device are predicted, and the route planning problem caused by inaccurate speed data in the prior art is solved, and the blockage situation prediction and route optimization are achieved in the absence of on-site data.
Patent Information
- Application Number
- CN202110838910.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2011-07-29
- Filing Date
- 2012-02-02
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2032-02-02
AI Technical Summary
In existing electronic navigation devices, the speed data of road sections is inaccurate, resulting in a decrease in the accuracy of route planning, especially when traffic density changes, it is difficult to accurately predict the fastest route and congestion situation.
By using historical data to predict the expected average travel speed on the segment, combined with the probability of blockage and clogging speed, the expected speed in clogging or non-clogging conditions is output, and even provides more accurate predictions in the absence of field data.
Improves the accuracy of route planning, can predict blockages in sections with less or no field data, reduces errors in route selection, and provides more accurate arrival time estimates and fastest route recommendations.
Smart Images

Figure CN113503889B_ABST
Abstract
Description
[0001] Information about divisional applications
[0002] This application is a divisional application. The parent case of this application is a Chinese patent application with application number 201610990130.3, application date February 2, 2012, and invention name “Method for generating expected average travel speed”. Technical Field
[0003] The present invention relates to a method of generating expected average travel speeds over one or more segments in an area covered by an electronic map, and a system, server and navigation device on which part or all of the method may be implemented. The present invention further relates to a method of generating map data indicating a trend of deviation from expected congestion conditions over a set of segments in an area covered by an electronic map, and a system, server and navigation device on which part or all of the method may be implemented. Specifically, but not exclusively, the present invention relates to determining a route over an area for use in a navigation device, and specifically, but not particularly, for use in a portable navigation device (PND). Background Art
[0004] For use in electronic navigation devices (e.g., GPS-based personal navigation devices such as the GO TM ) comes from specialist map suppliers. Such devices are also known as portable navigation devices (PNDs). This map data is particularly designed for use by route guidance algorithms, typically by using position data from a GPS system. For example, a road may be described as a line, i.e. a vector (e.g. start point, end point, direction of the road, where the entire road consists of hundreds of such segments, each segment being uniquely defined by start point / end point direction parameters). A map is then a set of such road vectors, with data associated with each vector (speed limit, direction of travel, etc.) plus points of interest (POIs), plus road names, plus other geographical features such as park boundaries, river boundaries, etc., all of which are defined in terms of vectors. All map features (e.g. road vectors, POIs, etc.) are typically defined in a coordinate system corresponding to or related to the GPS coordinate system, so that the device position as determined by the GPS system can be located on the relevant road shown in the map and used for the best route to be planned to the destination.
[0005] Typically, each such road segment has associated therewith speed data for that road segment, which gives an indication of the speed at which a vehicle can travel along that segment, and is an average speed generated by the party generating the map data. The speed data is used by a route planning algorithm on the PND on which the map is processed. The accuracy of this route planning therefore depends on the accuracy of the speed data. For example, a user is typically presented with an option on their PND to have the PND generate the fastest route between the device's current location and a destination. If the speed data is inaccurate, the route calculated by the PND may not be the fastest route.
[0006] It is known that parameters such as traffic density can significantly affect the speed profile of a section of road, and this speed profile variation means that the fastest route between two points may not always be the same. Inaccuracies in the speed parameters of a road section may also lead to inaccurate estimated times of arrival (ETA) and the selection of a suboptimal fastest route. Congestion, which can significantly affect the fastest route between two points, is particularly problematic.
[0007] To improve accuracy, it is known to collect live data relating to blocked traffic, and use this data to account for known jams in route planning. It will be appreciated that if live data is to give a true indication of road conditions, then a large amount is required: traffic flow has a strong random component, meaning that event detection based on lower grade or scarce live data may be inaccurate. However, it may often be the case that little or no live data is available for a segment, and therefore its true conditions may remain unpredictable. Summary of the invention
[0008] According to a first aspect of the invention, there is provided a method of generating an expected average speed of travel over one or more segments in an area covered by an electronic map, each segment having associated therewith:
[0009] the average speed of travel over the section;
[0010] segment data, including at least one jam probability, the jam probability indicating the likelihood of a jam on the segment; and
[0011] a jam speed indicating the travel speed on the segment when considered jammed, the method comprising:
[0012] using the segment data to predict whether a jam condition exists on at least one or each of the segments; and
[0013] The expected average travel speed over these segments is output as:
[0014] a) in case a jam condition is predicted to exist, a first speed, said first speed being said jam speed for the relevant section or a speed based thereon, or
[0015] b) In case no jam condition is predicted, a second speed, said second speed being said average speed of said relevant section or a speed based thereon.
[0016] The method allows prediction of expected average travel speeds over a segment, including prediction of reduced speeds due to congestion, even where little or no live data is available.
[0017] According to another aspect of the invention there is provided a system arranged to generate an expected average speed of travel over one or more segments in an area covered by an electronic map, each segment having associated therewith:
[0018] the average speed of travel over the section;
[0019] segment data, including at least one jam probability, the jam probability indicating the likelihood of a jam on the segment; and
[0020] a congestion speed indicating a speed on the segment when considered congested, the system comprising a processor arranged to:
[0021] using the segment data to predict whether a jam condition exists on at least one of the segments; and
[0022] The expected average travel speed over these segments is output as:
[0023] a) in case a jam condition is predicted to exist, a first speed, said first speed being said jam speed for the relevant section or a speed based thereon, or
[0024] b) In case no jam condition is predicted, a second speed, said second speed being said average speed of said relevant section or a speed based thereon.
[0025] As will be appreciated, the system and / or processor may be at least a portion of a server or a navigation device.
[0026] Thus, the present invention may encompass a server arranged to generate an expected average travel speed over one or more sections in an area covered by an electronic map. Similarly, the present invention may encompass a navigation device arranged to generate an expected average travel speed over one or more sections in an area covered by an electronic map.
[0027] The average travel speed on the segment can be based on historical data. For example, the historical average speed can be directly recorded, or the historical average speed can be calculated from the recorded historical travel time on the segment.
[0028] A segment may have a plurality of average travel speeds associated therewith, for example each average speed representing the average speed along the segment during a particular time period. In such embodiments, the second speed is preferably the average speed of the relevant segment at the appropriate time, or a speed based thereon.
[0029] There are many ways to collect or generate historical travel times on a segment, such as the time interval between satellite navigation trajectories entering and exiting the segment, or the time interval between two number plate recognition or Bluetooth signal events, or records of departure and arrival times, or even simulations based on traffic flow data.
[0030] In a preferred embodiment, the average speed associated with a segment may be determined according to the method described in WO 2009 / 053411, the entire contents of which are incorporated herein by reference. In this method, a plurality of time-stamped position data is preferably captured / uploaded from a plurality of navigation devices, such as portable navigation devices (PNDs). This data is preferably divided into a plurality of tracks, wherein each track represents data received from a navigation device over a predetermined time period. The recorded speeds over each predetermined time period may then be averaged for each navigable segment.
[0031] It will be appreciated that in the above and following paragraphs, the phrase "average speed" is used. However, it will be appreciated that in practice, it may never be possible to know the average speed with complete accuracy. For example, in some cases, the average speed calculated can only be as accurate as the equipment used to measure time and position. It will therefore be appreciated that whenever the phrase "average speed" is used, it is to be interpreted as the average speed as calculated based on measurements which themselves may have associated errors.
[0032] In this context, the word history should be considered to indicate non-site data, i.e. data that does not directly reflect the conditions on the segment at the current time or shortly before (perhaps within about the previous five, ten, fifteen or thirty minutes). Historical average speeds and historical travel times may, for example, relate to past event days, weeks or even years. Although this data may not therefore be the result of monitoring current road conditions, it may still be relevant to calculating the jam probability of the segment. Using historical data, rather than separate site data, may increase the amount of available relevant data, and may therefore allow a more accurate jam probability of the segment to be calculated. This may be particularly true when there is little or no site travel data available.
[0033] It should be noted that the phrase "associated with" with respect to one or more segments should not be interpreted as requiring any particular limitation on the data storage location. The phrase only requires that the feature is identifiably related to the segment. Thus, the association may be achieved, for example, by means of a reference to a side file (potentially located in a remote server).
[0034] In some embodiments, using the method to determine a route over an area covered by an electronic map includes:
[0035] i) exploring routes based on expected average travel speed over the segments; and
[0036] ii) Generate a navigable route.
[0037] This system may allow timely intervention in routes based on segment-specific jam probabilities. Reduced expected average travel speeds on segments where jams exist may be incorporated when generating routes. Because the method is based on jam probabilities taking into account historical data, it may be possible to usefully predict jams even where little or no live data exists for the segment in question.
[0038] In some embodiments, where a jam condition is predicted to exist, a jam warning is issued. This warning may be issued, for example, from a server via a communication network to one or more navigation devices, for example so that the navigation device can use this information when planning a route, providing traffic information, etc. The navigation device may then in turn output the expected average travel speed over the segment.
[0039] The steps of the method may be performed exclusively on the server, or some on the server and others on the navigation device, or exclusively on the navigation device in any combination. Performing one or more of the steps on the server may be efficient and may reduce the computational burden borne on the navigation device. Alternatively, if one or more steps are performed on the navigation device, this may reduce any bandwidth required for network communications.
[0040] For example, in some embodiments, the step of determining the route on the area covered by the electronic map is performed on the server. In other embodiments, the expected average travel speed on the output segment is sent to the navigation device (from the server), and the determination step is performed on the navigation device.
[0041] As discussed above, each segment in the electronic map has associated therewith a jam speed and at least one jam probability.
[0042] In some embodiments, the jam speed is all or substantially all or a selected average of the average travel speed on the segment when the segment is considered jammed. However, in other embodiments, all or substantially all or a selected mode or percentile of the historical average travel speed on the segment when the segment is considered jammed may be used.
[0043] Each segment preferably also has associated therewith a jam threshold speed indicating the average travel speed over the segment, below which the segment is considered jammed. In other words, the jam threshold speed is selected such that an average travel speed over the segment below the jam threshold speed may be classified as jammed, whereas an average travel speed over the segment above the jam threshold speed may be considered as unjammed.
[0044] In some embodiments, the jam threshold speed is defined according to a selected percentage of the free flow speed of the segment. However, in alternative embodiments, the jam threshold speed may alternatively be defined as a predefined value corresponding to the road type, for example, or simply a specific speed that is considered to indicate jammed traffic.
[0045] The free flow speed for a road segment is preferably defined as the average speed of travel on the segment during a time period in which there is no or substantially little traffic. This period may, for example, be one or more nighttime hours when the speed on the segment may be less affected by other users. Such a measurement of free flow speed will still reflect the influence of, for example, speed limits, road layout, and traffic management infrastructure. Therefore, this may be a more accurate reflection of the true free flow speed than the posted speed limit, legal speed, or speed assignment based on road class. However, in other embodiments, the free flow speed may be calculated or selected differently (it may, for example, simply be regarded as the speed limit for the segment).
[0046] In some embodiments, the selected percentage of free flow rate is between 30% and 70%, more preferably between 40% and 60%, and most preferably substantially 50%.
[0047] In some embodiments, a predefined upper limit may be used as the jam threshold speed, where the method of defining the jam threshold speed would otherwise result in the use of a higher speed. For example, it is possible that the method of defining the jam threshold speed may, in certain circumstances, result in a speed being considered too high for a certain segment to be non-jammed. In such circumstances, the jam threshold speed may default to the upper limit.
[0048] The jam probability of a particular segment may be generated based on the historical travel data of the segment and the jam condition of the segment, wherein the jam condition indicates whether the segment is jammed.
[0049] The manner in which the jam probability of a segment is generated is believed to be novel and advantageous in its own right.
[0050] Therefore, in another aspect of the invention there is provided a method of processing data relating to an electronic map, the map comprising a plurality of segments representing navigable segments in an area covered by the map, the method comprising generating segment data using a processing device, and comprising the steps of:
[0051] collecting historical travel data of the segment;
[0052] defining a blocking condition for the segment such that the segment is classified as blocked when the blocking condition is met and as unblocked otherwise;
[0053] Defining a jam probability for generating the segment based on historical travel data and jam conditions; and
[0054] A jam probability is associated with a segment in an electronic map.
[0055] In another aspect of the invention there is provided a system arranged to process data relating to an electronic map, the map comprising a plurality of segments representing navigable segments in an area covered by the map, and to generate segment data by:
[0056] collecting or receiving historical travel data of the segment;
[0057] defining or receiving as input a congestion condition for the segment such that when the congestion condition is met, the segment is classified as congested, and otherwise classified as not congested;
[0058] Defining a jam probability for generating the segment based on historical travel data and jam conditions; and
[0059] A jam probability is associated with a segment in an electronic map.
[0060] As will be appreciated, the system and / or processor may be at least a portion of a server or a navigation device.
[0061] Therefore, the present invention may include a server arranged to process data related to an electronic map and generate segment data. Similarly, the present invention may include a navigation device arranged to process data related to an electronic map and generate segment data.
[0062] In some embodiments, the jam probability is used by the server to generate routes. For example, it may be the case that the server avoids generating routes that incorporate segments with high jam probability.
[0063] In some embodiments, the generated jam probability may be sent from the server to one or more navigation devices. One or more of the navigation devices may in turn use the jam probability to generate a route.
[0064] As will be appreciated by those skilled in the art, these aspects and embodiments of the invention can, and preferably do, include any one or more or all of the preferred and optional features of the invention described herein, as appropriate.
[0065] Thus, for example, the jam condition is preferably a jam threshold speed, which may be defined as a selected percentage of the free flow speed of the segment.
[0066] In some embodiments, a jam condition is predicted when the jam probability of the segment exceeds a predefined value. For example, it may be the case that a jam condition is predicted and a jam warning is optionally issued when the jam probability exceeds substantially 70% or another relatively high percentage, such as substantially any of the following: 50%, 60%, 80% or 90%.
[0067] In some embodiments, multiple jam probabilities are associated with each segment. Specifically, there may be multiple time-dependent jam probabilities for the segment, which reflect the change in jam probability over time within a selected time interval. In this way, when performing a prediction of whether a jam condition exists, the jam probability for the appropriate time may be used. For example, it may be possible to calculate the jam probability based on the time of year, day of the week, and / or time of day. In some embodiments, the jam probability may be provided at time intervals between 1 minute and 2 hours, between 5 minutes and 1 hour, between 10 minutes and 30 minutes, or at 15 minute time intervals.
[0068] As will be appreciated, the jam probability may vary depending on the time of day, day of week or even time of year. Therefore, the provision of multiple time-dependent jam probabilities may give a more accurate prediction of jam conditions than a single jam probability for a segment.
[0069] In some embodiments, one or more alternative jam probabilities are provided for use in conjunction with a segment within a corresponding time period, allowing the most appropriate jam probability at any given time to be selected based on one or more factors other than time-related variation. Selecting an alternative jam probability for use may be appropriate in particular circumstances, such as under different weather conditions, or where a particular event such as a football match is occurring. Such circumstances may be considered to be factors other than time-related variation. Such circumstances may be considered to be atypical. As will be appreciated, the provision of such alternative jam probabilities may depend on the availability of historical data sufficient to generate accurate jam probabilities.
[0070] In some embodiments, alternative sets of time-dependent jam probabilities are provided, allowing the most appropriate jam probability to be selected based on time and based on other factors. For example, it may be the case that if the weather is dry, one set of time-dependent jam probabilities is used, and if it is raining, another set is used.
[0071] In some embodiments, the jam probability of a segment is calculated based on the ratio of the number of calculated average travel speeds above and below the jam threshold speed on the segment. For example, a collection of GPS probes giving historical travel times on the segment may be analyzed. In this case, the number of probes requiring average speeds above and below the jam threshold speed on the segment may be compared. In one example, the ratio of jammed and unjammed probes may be 70:30, giving a jam probability of 30%.
[0072] In some embodiments, the jam probability of a segment is calculated based on time periods when the segment is jammed and unjammed, such as periods when historical average travel speeds indicate that jam conditions are met.
[0073] In some embodiments, where segments are connected together, the average percentage of blocked segments may be used to calculate the probability of blockage for one, some, or all of the connected segments.
[0074] In an embodiment where multiple time-dependent jam probabilities are associated with a segment, the historical travel data is grouped according to the time of recording. For example, if the historical travel data has been received within a predetermined time period, it can be grouped together. For example, the predetermined time period may be 5 minutes, 10 minutes, 15 minutes, 20 minutes, 30 minutes or 1 hour. In this way, the generated jam probability may be time-dependent and therefore may be accurate when used in jam predictions at corresponding times. For example, it may be the case that the historical segment data for a segment and therefore the jam probability is related to the period between 8.30 am and 8.45 am on Monday mornings during December to February. Therefore, when this jam probability is used at the corresponding time on Monday mornings in the corresponding month, it may be a better jam predictor than a non-time-dependent jam probability.
[0075] In some embodiments, the jam probability is calculated based on or at least partially influenced by the time of year. This can be used to increase the jam probability accuracy since the jam probability may vary depending on seasonal effects such as prevailing weather and road conditions.
[0076] In some embodiments, the jam probability is calculated based on or at least partially affected by the day of the week. This can be used to increase the jam probability accuracy because the jam probability may vary depending on factors related to the day of the week (e.g., weekend shopping, traveling on Friday over the weekend, transportation schedules, and long commutes on Monday).
[0077] In some embodiments, the jam probability is calculated based on or at least partially affected by the time of day. This can be used to increase the jam probability accuracy because the jam probability can vary depending on factors related to the time of day, such as rush hour, school traffic rush hour, opening and closing times (e.g., bars, restaurants, theaters, concert venues, cinemas, clubs, etc.), start and end times (e.g., festivals, shows and sporting events, etc.), arrival and departure times (e.g., trains, ships and airplanes), and the general commonality of activities (e.g., eating or sleeping). In some embodiments, for example, there may be a single jam probability for the night. The night may be a predefined period between set times (e.g., generally between 11 pm and 6 am).
[0078] In some embodiments, the jam probabilities are calculated for substantially fifteen minute time intervals. However, time intervals higher or lower than this may be used, such as 5 minutes, 10 minutes, 15 minutes, 20 minutes, 30 minutes, 1 hour, or longer periods, such as overnight. Additionally, calculated jam probabilities that are adjacent in time may be linked together. This may be particularly useful in situations where the jam probabilities are similar, such as potentially nighttime hours.
[0079] In some embodiments, the jam probability is calculated based on or at least partially affected by the occurrence of certain events or situations, such as certain types of weather, events such as football matches or exhibitions, and public holidays.
[0080] In some embodiments, the jam probability is calculated by or at least partially influenced by one or more of the factors described above.
[0081] As discussed above, when a jam condition is predicted to exist, the expected average travel speed on a segment is the jam speed of the relevant segment or a speed based thereon (the "first speed"). For example, the jam speed of a segment may be modified according to one or more dynamic parameters such as weather.
[0082] Similarly, and again as discussed above, when no jam condition is predicted, the expected average travel speed over a segment is the average speed of the relevant segment (and, for example, at the appropriate time) or a speed based thereon (a "second speed").
[0083] For example, the second speed may be all or substantially all or a selected average of the historical average travel speeds over the segment. However, in other embodiments, all or substantially all or a selected mode or percentile of the historical average travel speeds over the segment may be used. Alternatively, the speed may be selected in another manner.
[0084] In some embodiments, the segment data for one or more of the segments further includes field data for the segment.
[0085] Live data can be considered relatively current data and provides an indication of what is happening on a segment. Live data can typically relate to conditions on a segment within the last 30 minutes, and in some embodiments, can relate to conditions on a segment within the last 15 minutes, 10 minutes, or 5 minutes.
[0086] In some embodiments, the jam probability of a segment may be generated or modified based on live data for that segment. In other words, the jam probability may be calibrated using live data.
[0087] As will be appreciated, using live data in addition to the historical average travel speed on a segment can significantly increase the accuracy of the jam probability of a segment. For example, historical data for a segment may indicate a high probability that the segment is jammed at a particular point in time, when in fact, live data indicates that the segment is not actually jammed.
[0088] In some embodiments, the live data is alternatively or additionally used as a check to increase the likelihood of correctly predicting whether a jam condition exists on the relevant segment. Thus, in this case, at least some of the live data is not used to calibrate the jam probability, but rather to check predictions based thereon. This may be achieved by comparing the live data with the relevant jam probability, with data used in the calculation of the jam probability, and / or with the predictions.
[0089] In some embodiments, an optimizer is used to fuse the available data. Thus, the optimizer may also be viewed as data fusion means, which is arranged to combine historical data with live data, for example to determine what the average speed of travel along a segment should be considered to be. In this way, live data may be used to calibrate the associated jam probability calculated using the historical average speed of travel on the segment. Additionally and / or alternatively, fusion may allow a check to be performed.
[0090] In some embodiments, the optimizer is automated. The optimizer can be, for example, a parameter optimization scheme using an amoeba algorithm or manual result analysis.
[0091] In some embodiments, fusion is performed using a weighted or probabilistic average. Specifically, a greater weight may be given to live data if a larger amount is available and / or if it is felt to be more reliable and / or significant. As will be appreciated, a smaller amount of live data may be random in nature, and therefore may be used to overly distort predictions of jam conditions. Conversely, the more live data is available, the more useful it becomes to the point where it will ultimately prove to be more accurate than the historical average travel speed on a segment as to whether a jam condition exists. In the event that more live data is available for a segment, the weighted average may favor the live data, and even reduce the weighting of the historical travel time, making it relatively less significant.
[0092] In some embodiments, if less live data has been used in the fusion, the jam probability required to predict a jam condition is increased. By adjusting the required jam probability, the method can account for increased uncertainty in the presence of little or no live data.
[0093] In some embodiments, if live data is to be fused, a lower threshold cutoff may be set for the amount of live data available. As previously mentioned, a smaller amount of live data may be random in nature and therefore may be used to distort the true condition of a segment. In such instances, it may therefore be preferable to avoid using live data entirely, with the lower threshold defining this cutoff point.
[0094] In some embodiments, the live data includes one or more live travel times on at least one or each segment. Live travel times can typically be calculated from a GPS probe. This data can be relevant because it can provide an up-to-date indication of the actual situation on the segment. Live travel times can also be calculated from any of the following: data from a cellular telephone network; data generated by a road loop; traffic cameras (including ANPR, automatic number plate recognition).
[0095] In some embodiments, the optimizer uses the live travel times associated with the relevant segment in the function used to calculate the jam probability, factoring in the average speed at which the live travel time requires to be above the jam threshold speed and the average speed at which the live travel time requires to be below the jam threshold speed. In this way, the jam probability associated with the segment can be calibrated. Thus, the prospects for accurate jam condition predictions can be improved. Nevertheless, because historical travel times are always used, the method does not depend on any large amount of live data being available. It will be appreciated that while an amount of live data sufficient to give an accurate jam prediction in isolation may be available for some or even most segments, it may not be available for all segments.
[0096] In some embodiments, the field data includes information about one or each of the segments from one or more of the following sources:
[0097] a calendar indicating identified days and / or times when a segment is expected to have unusual traffic;
[0098] News data indicating blockage;
[0099] The number of GPS probes detected on the segment; and
[0100] Weather monitoring and / or forecasting services.
[0101] News data may include traffic reports from broadcasts and / or other reports from news media regarding factors that have or may have an impact on traffic.
[0102] In this way, live data, such as those relating to weather, local events, public holidays and disasters, may be factored into the prediction of whether a jam condition exists. This data may be more suitable for performing checks rather than being factored into the calculation of the jam probability. It will be appreciated that in some cases this live data may be as useful or even more useful than live data that includes live travel times on a segment. In the case where, for example, news data indicates a traffic jam in a particular segment, it may be the case that the optimizer may weight this information more heavily as being likely to be correct. Particularly recent live data may also be weighted more heavily; that is, more recent live data may be weighted more highly than older live data. As another example, heavy rain forecasted by a weather forecast service may increase the likelihood of slow traffic, and therefore this may be used by the optimizer to correctly identify the cause of slow moving traffic as a weather condition rather than a jam.
[0103] In some embodiments, the live data for one or each of the segments is checked for consistency with the jam probability and / or historical travel times when used in its calculation and / or prediction of whether a jam condition exists based on the jam probability. This may be considered a local check as it relates to a particular segment, which may not be relevant, rather than a group of segments or the entire network.
[0104] In the event that the live data is inconsistent with the jam probability and / or the historical travel times used for its calculation and / or the prediction of whether a jam condition exists based on the jam probability, one or more of the following steps may be taken:
[0105] i) adjusting the jam probability required to predict jam conditions;
[0106] ii) using field data or additional field data in the jam probability calculation;
[0107] iii) adjusting weighted or probabilistic averages to bias or further bias field data;
[0108] iv) using the inconsistency to overturn a jam condition prediction or to make a jam condition prediction that would not otherwise be made; and v) initiating a switch to the use of one or more different jam probabilities that are more consistent with live data.
[0109] By performing one or more of the above steps, the accuracy of jam condition predictions may be improved. For example, it may be the case that live data (e.g. by conflicting with the jam probability) indicates that at the current time, conditions are abnormal, i.e. the jam probability (which may be based exclusively on the historical average travel speed on the segment) is not a good guide to whether a jam condition exists. As a result, mitigating action may be taken, e.g. by overriding the imminent issuance of a jam warning.
[0110] Where the amount of data permits, it may be the case that one or more alternative sets of jam probabilities are available for the segment. Such jam probabilities may relate to specific potential recurrence situations (e.g. football matches, bank holidays or bad weather in the local area). In this case, option (v) may be taken if the live data indicates that this alternative set of jam probabilities is more relevant.
[0111] In some embodiments, the live data for a group of segments is checked for consistency with their corresponding jam probabilities and / or historical travel times used in their calculation and / or prediction of whether a jam condition exists based on the jam probabilities. This can be considered a regional check as it involves a group of segments.
[0112] In case the check indicates a deviation trend from the jam probability and / or the historical travel times used for its calculation and / or the prediction of whether a jam condition exists based on the jam probability, one or more of the following steps may be taken for the segments in the group and / or other related segments:
[0113] i) adjusting the jam probability required to predict jam conditions;
[0114] ii) using field data or additional field data in the jam probability calculation;
[0115] iii) adjusting weighted or probabilistic averages to bias or further bias field data;
[0116] iv) using inconsistencies to overturn predictions of congestion conditions or to make predictions of congestion conditions that would not otherwise have been made; and
[0117] v) Initiate a switch to the use of one or more different jam probabilities that are more consistent with live data.
[0118] In this way, changes may be made based on patterns / trends observed in a group of segments (e.g., patterns of jam probability deviations). The inspection performed on a group of segments may allow inferences to be drawn about the likelihood of jam conditions on segments within the group. Such inferences may not be consistent with the jam probability. Further inferences may be made about segments that are not within the group (e.g., nearby segments that may be affected by conditions on one or more segments within the group). For example, it may be the case that the inspection indicates that most or even all segments within the group are jammed, contrary to the jam probability indication. This in turn may be interpreted as an indication that places with high jam probabilities are even more likely to be jammed than usual, and this should be taken into account when predicting whether a jam condition exists.
[0119] In some alternative embodiments, the deviation trend may lead to a partial or complete override of the use of the jam probability for a period. For example, it may be the case that the live data indicates that the jam probability is completely unsuitable for use in predicting whether a jam condition will exist for a particular period.
[0120] In some embodiments, the set of segments may include one or more of: segments that fall within a predetermined map area, segments that fall within a predetermined radius, segments that include possible routes into or out of the area, segments that have a predetermined direction of travel within the area, and segments that are selected as known bottlenecks, and segments that are selected as containing traffic hotspots. For example, it may be the case that the set includes segments that form what may be referred to as a main route out of the city. This set may be useful, for example, at the beginning of a bank holiday period, where jams are more likely to occur on the main route out of the city.
[0121] In some embodiments, the live data of a set of linked segments is evaluated for significant changes in agreement between the live data of each segment and the jam probability of the segment between the segments. This can be used to assist in predicting jam conditions. In cases where, for example, the live data of an upstream segment is more consistent with its corresponding jam probability for that segment, this can strengthen the prediction of jam conditions for downstream segments. An upstream segment is a segment that feeds traffic from itself to the segment in question for a given direction of travel. Additionally, a chain of gradual changes in agreement over linked segments can indicate the length of a queue, and therefore improve jam condition predictions.
[0122] In some embodiments, the selection of the set of segments is organized hierarchically. This can be achieved via a mesh refinement procedure depending on the field data coverage. For example, it may be the case that segments for which more field data are available are preferentially incorporated into the set.
[0123] In some embodiments, the live data for all segments in the mapped network are checked for consistency with the corresponding jam probabilities and / or historical travel times used in their calculation and / or prediction of whether a jam condition exists based on the jam probabilities. This can be considered a global check as it involves the entire mapped network.
[0124] In case of checking for trends indicating deviations from the jam probability and / or historical travel times used for its calculation and / or prediction of whether a jam condition exists based on the jam probability, one or more of the following steps may be performed for all segments:
[0125] i) adjusting the jam probability required to predict jam conditions;
[0126] ii) using field data or additional field data in the jam probability calculation;
[0127] iii) adjusting weighted or probabilistic averages to bias or further bias field data;
[0128] iv) using inconsistencies to override predictions of congestion conditions or to make predictions of congestion conditions that would not otherwise be made; and
[0129] v) Initiate a switch to the use of one or more different jam probabilities that are more consistent with live data.
[0130] In this way, changes are made based on patterns observed from the inspection performed on all segments. Inspections performed on all segments may allow inferences to be drawn regarding the likelihood of a congestion condition on a segment. This type of inspection may be useful in the event of a phenomenon that has the potential to affect the entire network.
[0131] In some embodiments, jam condition predictions for adjacent segments may be linked into one jam. This may present a more realistic indication of the situation.
[0132] Embodiments of the method may be performed by an offline navigation device. In this way, a navigation device that is not connected to a communication network may still use embodiments of the present invention.
[0133] Where the method is performed by an offline navigation device, live data is provided by evaluation of information collected by the navigation device. In some cases, this data may act as a substitute for the alternative form of live data previously described.
[0134] Where live data is collected by a navigation device, the live data may be checked for consistency with the relevant jam probabilities and / or historical travel times used in their calculation and / or in predicting whether a jam condition exists based on the jam probabilities. This may provide an indication of the relevance of a particular jam probability.
[0135] In the event that the live data is inconsistent with the jam probability and / or the historical travel times used for its calculation and / or the prediction of whether a jam condition exists based on the jam probability, one or more of the following steps may be performed for one or more segments:
[0136] i) adjusting the jam probability required to predict jam conditions;
[0137] ii) using field data or additional field data in the jam probability calculation;
[0138] iii) adjusting weighted or probabilistic averages to bias or further bias field data;
[0139] iv) using inconsistencies to override predictions of congestion conditions or to make predictions of congestion conditions that would not otherwise be made; and
[0140] v) Initiate a switch to the use of one or more different jam probabilities that are more consistent with live data.
[0141] For example, it may be the case that the navigation device detects that it is currently in a jam, and otherwise no jam condition prediction will be made based on the jam probability. This may facilitate calibration or checking of the jam probability for the segment in question and optionally for additional segments. Calibration or checking of the jam probability for additional segments may occur in situations where such segments may be affected by the conditions on the segment in question and / or may be considered to be essentially similar to the segment in question. Additionally or alternatively, the estimated journey time or estimated arrival time calculated based on a route utilizing the jam probability may be different from the actual arrival time. This actual arrival time may be used to calibrate or check one or more jam probabilities used in generating the estimated journey time / estimated arrival time.
[0142] The use of live data obtained for one or more sections in a region to confirm or modify jam probabilities for sections where little or no live data exists is believed to be novel and advantageous in its own right.
[0143] Therefore, according to another aspect of the present invention, there is provided a method of generating map data indicating deviations from expected congestion conditions on a segment of a plurality of segments in an area covered by an electronic map, the segment having associated therewith a congestion probability indicating the likelihood of congestion on the segment, the method comprising:
[0144] establishing an expected congestion condition for the segment based on the congestion probability for the segment;
[0145] obtaining field data indicative of the congestion condition on at least one of a plurality of other sections in the area; and,
[0146] The acquired field data is used to establish a revised jam condition for the segment.
[0147] As will be appreciated, this approach allows for a more accurate determination of congestion conditions on a segment even where little or no live data is available for that segment. In other words, the following inference is made: if, for example, live data indicates that a significant number of segments in a region are congested at a given time, then there is a higher likelihood that connected segments in the region will also be congested (even if historical data indicates that this will not be the case).
[0148] According to another aspect of the invention, there is provided a system arranged to generate map data indicating deviations from expected congestion conditions on a segment of a plurality of segments in an area covered by an electronic map, the segment having associated therewith a congestion probability indicating the likelihood of congestion on the segment, the method comprising:
[0149] establishing an expected congestion condition for the segment based on the congestion probability for the segment;
[0150] obtaining field data indicative of the congestion condition on at least one of a plurality of other sections in the area; and,
[0151] The acquired field data is used to establish a revised jam condition for the segment.
[0152] As will be appreciated, the system and / or processor may be at least a portion of a server or a navigation device.
[0153] Thus, the present invention may encompass a server arranged to generate map data indicating deviations from expected congestion conditions on a segment in an area covered by an electronic map. Similarly, the present invention may encompass a navigation device arranged to generate map data indicating deviations from expected congestion conditions on a segment in an area covered by an electronic map.
[0154] As will be appreciated by those skilled in the art, these aspects and embodiments of the invention can, and preferably do, include any one or more or all of the preferred and optional features of the invention described herein, as appropriate.
[0155] For example, the corrected congestion condition for a segment may be used to assign a suitable average travel speed to the segment, such as for use in generating a route from an origin to a destination.
[0156] As discussed above, live data can be considered relatively current data and provides an indication of what is happening on a segment. Live data can typically relate to conditions on a segment within the last 30 minutes. In some embodiments, live data can relate to conditions on a segment within the last 15 minutes, 10 minutes, or 5 minutes.
[0157] The step of establishing a modified jam condition for a segment may include checking or modifying the jam probability of the segment based on live data. For example, one or more of the following steps may be performed:
[0158] i) adjusting the jam probability required to predict jam conditions;
[0159] ii) using field data or additional field data in the jam probability calculation;
[0160] iii) adjusting the weighting given to live data in predicting whether a congestion condition exists to favor or further favor live data;
[0161] iv) overturn a congestion forecast, or make a congestion forecast that would not otherwise have been made; and
[0162] v) Initially switch to using one or more different jam probabilities that are more consistent with live data.
[0163] In this way, changes may be made based on patterns observed in a group of segments, such as patterns of jam probability deviations. The inspection performed on a group of segments may allow an inference to be drawn about the likelihood of a jam condition on the segments within the group. This inference may not be consistent with the jam probability. Further inferences may be made about segments that are not within the group, such as nearby segments that may be affected by conditions on one or more segments within the group. For example, it may be the case that the inspection indicates that most or even all of the segments within the group are jammed, contrary to the jam probability indication. This in turn may be interpreted as an indication that places with a high jam probability are more likely to be jammed than usual, and this should be taken into account when predicting whether a jam condition exists.
[0164] In some alternative embodiments, the deviation trend may lead to a partial or complete override of the use of the jam probability for a period. For example, the situation may be that the live data indicates that the jam probability is completely unsuitable for use in predicting whether a jam condition exists for a particular period.
[0165] In some embodiments, the set of segments may include segments that fall within a predetermined map area, segments that fall within a predetermined radius, segments that fall within an area with a predetermined direction of travel, or segments that are selected as known bottlenecks, and segments that are selected as containing traffic hotspots, etc. For example, it may be the case that the set includes segments that form what may be called a main route out of an area (e.g. out of a city). This set may be useful, for example, at the beginning of a bank holiday period (where jams are more likely to occur on the main route out of a city).
[0166] In some embodiments, the selection of the set of segments is organized hierarchically. This can be achieved via a mesh refinement procedure depending on the field data coverage. For example, it may be the case that segments for which more field data are available are preferentially incorporated into the set.
[0167] According to another aspect of the invention, there is provided a method of generating map data indicating a trend of deviation from expected congestion conditions over a set of segments in an area covered by an electronic map, each segment having associated therewith:
[0168] a jam probability indicating the likelihood of a jam on the segment; and
[0169] Field data related to whether a congestion condition currently exists on the segment, the method comprising:
[0170] checking the live data for at least some and typically each segment for consistency with corresponding jam probabilities or historical travel times for the segment;
[0171] Establish any deviations from said consistency; and
[0172] Outputs an indication of any deviation trends.
[0173] According to another aspect of the invention, there is provided a system arranged to generate map data indicative of trends of deviations from expected congestion conditions over a set of segments in an area covered by an electronic map, each segment having associated therewith:
[0174] a jam probability indicating the likelihood of a jam on the segment; and
[0175] field data relating to whether a congestion condition currently exists on the segment, the system comprising a processor arranged to:
[0176] checking the live data for at least some and typically each segment for consistency with corresponding jam probabilities or historical travel times for the segment;
[0177] Establish any deviations from said consistency; and
[0178] Outputs an indication of any deviation trends.
[0179] As will be appreciated, the system and / or processor may be at least a portion of a server or a navigation device.
[0180] Any of the methods according to the invention may be implemented at least in part using software (eg, a computer program). The invention therefore also extends to a computer program comprising computer-readable instructions executable to implement the method according to any of the aspects or embodiments of the invention.
[0181] The invention correspondingly extends to a computer software carrier comprising such software, which, when used to operate a system or device comprising a data processing device, causes the device or system to perform the steps of the method of the invention in conjunction with the data processing device. This computer software carrier may be a non-transitory physical storage medium, such as a ROM chip, CD ROM or disk, or may be a signal, such as an electronic signal on a wire, an optical signal or a radio signal, such as to a satellite, etc.
[0182] Without explicitly stating, it will be understood that the present invention in any of its aspects may include any or all of the features described in accordance with other aspects or embodiments of the present invention (to the extent that they are not mutually exclusive). In particular, although various embodiments of operations that may be performed in the method and by the apparatus have been described, it will be understood that any or one or more or all of these operations may be performed in the method and by the apparatus in any combination, as needed and appropriate.
[0183] Advantages of these embodiments are set out below, with further details and features of each of these embodiments being defined in the accompanying dependent claims and elsewhere in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0184] Embodiments of the present invention will now be described, by way of example only, with reference to the accompanying drawings, in which:
[0185] Figure 1 is a schematic illustration of an exemplary portion of a global positioning system (GPS) that may be used by a navigation device;
[0186] Figure 2 is a schematic diagram of a communication system for communication between a navigation device and a server;
[0187] Figure 3 yes Figure 2 Schematic illustration of electronic components of a navigation device or any other suitable navigation device;
[0188] Figure 4 is a schematic diagram of the arrangement for mounting and / or docking the navigation device;
[0189] Figure 5 yes Figure 3 A schematic illustration of an architectural stack used by a navigation device;
[0190] Figure 6 is the average travel speed on the segment histogram of three different time periods: "morning", "noon" and "evening";
[0191] Fig. 7A is the average travel speed on the segment histogram identifying possible jam speeds;
[0192] Figure 7B is the average travel speed on the segment histogram identifying possible jam speeds;
[0193] Figure 7C is the average travel speed on the segment histogram identifying possible jam speeds;
[0194] Fig.7D is the average travel speed on the segment histogram identifying possible jam speeds;
[0195] Figure 8 is a flow chart illustrating an embodiment of the method of the present invention;
[0196] Fig. 9 is a schematic diagram illustrating the architecture of route generation;
[0197] Fig.10 is a plot of field data volume versus time with a blocking probability using a cutoff;
[0198] Fig.11 is a graph of jam probability deviation and speed deviation versus time, illustrating a possible portion of a regional inspection; and
[0199] Fig.12 is a graph of jam probability deviation and speed deviation versus time, illustrating a possible portion of a regional inspection. DETAILED DESCRIPTION
[0200] Embodiments of the present invention will now be described with particular reference to portable navigation devices (PNDs). However, it should be remembered that the teachings of the present invention are not limited to PNDs, but are instead broadly applicable to any type of processing device that is configured to execute navigation software in a portable manner to provide route planning and navigation functionality. Therefore, hereinafter in the context of this application, a navigation device is intended to include (without limitation) any type of route planning and navigation device, whether the device is embodied as a PND, a vehicle such as a car, or a truly portable computing resource such as a portable personal computer (PC), mobile phone or personal digital assistant (PDA) executing route planning and navigation software.
[0201] Additionally, embodiments of the present invention are described with reference to road segments. It will be appreciated that the present invention is also applicable to other navigable segments, such as segments of paths, rivers, canals, cycle paths, towpaths, railway tracks, etc. For ease of reference, these segments will generally be referred to as road segments.
[0202] As will also be apparent below, the teachings of the present invention have utility even in situations where the user is not seeking instructions on how to navigate from one point to another, but rather simply wishes to have a view of a given location. In such situations, the "destination" location selected by the user need not have a corresponding starting location from which the user wishes to begin navigating, and thus references herein to a "destination" location, or indeed to a "destination" view, should not be interpreted as indicating that the generation of a route is necessary, that travel to the "destination" must occur, or indeed that the existence of the destination requires the representation of a corresponding starting location.
[0203] Keep in mind the above conditions. Figure 1 The Global Positioning System (GPS) of the United States and the United States is used for a variety of purposes. In general, GPS is a satellite radio-based navigation system that is capable of determining continuous position, velocity, time, and (in some cases) direction information for an unlimited number of users. GPS, formerly known as NAVSTAR, incorporates a number of satellites that orbit the earth in extremely precise orbits. Based on these precise orbits, the GPS satellites can relay their positions as GPS data to any number of receiving units. However, it will be understood that a global positioning system such as GLOSNASS, the European Galileo Positioning System, the COMPASS Positioning System, or the IRNSS (Indian Regional Navigation Satellite System) may be used.
[0204] The GPS system is implemented when a device (specially equipped to receive GPS data) begins scanning radio frequencies for GPS satellite signals. Upon receiving a radio signal from a GPS satellite, the device immediately determines the precise position of the satellite via one of a number of different conventional methods. In most cases, the device will continue scanning for signals until it has acquired at least three different satellite signals (note that it is not common but other triangulation techniques can be used to determine position with only two signals). By implementing geometric triangulation, the receiver uses the three known positions to determine its own two-dimensional position relative to the satellite. This can be done in a known manner. In addition, acquiring a fourth satellite signal allows the receiving device to calculate its three-dimensional position in a known manner through the same geometric calculations. The position and velocity data can be continuously updated in real time by an unlimited number of users.
[0205] like Figure 1, a GPS system 100 includes a plurality of satellites 102 orbiting the earth 104. A GPS receiver 106 receives GPS data from several of the plurality of satellites 102 as spread spectrum GPS satellite data signals 108. Spread spectrum data signals 108 are continuously transmitted from each satellite 102, and the transmitted spread spectrum data signals 108 each include a data stream containing information identifying the particular satellite 102 from which the data stream originated. The GPS receiver 106 typically requires spread spectrum data signals 108 from at least three satellites 102 in order to be able to calculate a two-dimensional position. Receipt of a fourth spread spectrum data signal enables the GPS receiver 106 to calculate a three-dimensional position using known techniques.
[0206] Steering Figure 2 , a navigation device 200 (i.e., a PND) including or coupled to a GPS receiver device 106 is able to establish a data session (if necessary) with the network hardware of a "mobile" or telecommunication network via a mobile device (not shown) (e.g., a mobile phone, a PDA, and / or any device with mobile phone technology) to establish a digital connection, such as a digital connection via known Bluetooth technology. Thereafter, through its network service provider, the mobile device may establish a network connection (e.g., via the Internet) with a server 150. Thus, a "mobile" network connection may be established between the navigation device 200 (which may be, and typically is, mobile when it is traveling alone and / or in a vehicle) and the server 150 to provide a "real-time" or at least very "fresh" gateway to information.
[0207] Establishing a network connection between a mobile device (via a service provider) and another device (e.g., server 150) using, for example, the Internet can be done in a known manner. In this regard, any number of suitable data communication protocols can be used, such as the TCP / IP layered protocol. In addition, the mobile device can utilize any number of communication standards, such as CDMA2000, GSM, IEEE802.11a / b / c / g / n, etc.
[0208] Thus, it can be seen that an internet connection may be utilised, which may be achieved via a data connection, for example via a mobile phone or mobile phone technology within the navigation device 200 .
[0209] Although not shown, the navigation device 200 may of course include its own mobile phone technology within the navigation device 200 itself (e.g. including an antenna, or optionally using an internal antenna of the navigation device 200). The mobile phone technology within the navigation device 200 may include internal components, and / or may include an insertable card (e.g. a Subscriber Identity Module (SIM) card), for example together with the necessary mobile phone technology and / or antenna. As such, the mobile phone technology within the navigation device 200 may establish a network connection between the navigation device 200 and the server 150 in a manner similar to that of any mobile device, such as via the Internet.
[0210] For phone settings, a Bluetooth enabled navigation device may be used to work correctly with the ever changing spectrum of mobile phone models, manufacturers etc., the model / manufacturer specific settings may for example be stored on the navigation device 200. The data stored for this information may be updated.
[0211] exist Figure 2 , the navigation device 200 is depicted as being in communication with the server 150 via a general communication channel 152 that may be implemented by any of a number of different arrangements. The communication channel 152 generally represents a propagation medium or path connecting the navigation device 200 and the server 150. When a connection via the communication channel 152 is established between the server 150 and the navigation device 200 (note that this connection may be a data connection via a mobile device, a direct connection via the Internet via a personal computer, etc.), the server 150 and the navigation device 200 may communicate.
[0212] The communication channel 152 is not limited to a particular communication technology. In addition, the communication channel 152 is not limited to a single communication technology; that is, the channel 152 may include several communication links using multiple technologies. For example, the communication channel 152 may be suitable for providing a path for electrical, optical, and / or electromagnetic communications, etc. Thus, the communication channel 152 includes (but is not limited to) one or a combination of the following: circuits, electrical conductors (e.g., wires and coaxial cables), fiber optic cables, converters, radio frequency (RF) waves, atmosphere, free space, etc. In addition, the communication channel 152 may include intermediate devices such as routers, repeaters, buffers, transmitters, and receivers.
[0213] In one illustrative arrangement, the communication channel 152 includes telephone and computer networks. In addition, the communication channel 152 may be capable of accommodating wireless communications, such as infrared communications, radio frequency communications, such as microwave frequency communications, etc. In addition, the communication channel 152 may accommodate satellite communications.
[0214] The communication signals transmitted via the communication channel 152 include, but are not limited to, signals as may be required or desired for a given communication technology. For example, the signals may be suitable for use in cellular communication technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), code division multiple access (CDMA), global system for mobile communications (GSM), general packet radio service (GPRS), etc. Both digital and analog signals may be transmitted via the communication channel 152. These signals may be modulated, encrypted, and / or compressed signals as may be required for the communication technology.
[0215] The server 150 includes (among other components that may not be illustrated) a processor 154, which is operatively connected to a memory 156, and further operatively connected to a mass data storage device 160 via a wired or wireless connection 158. The mass storage device 160 contains a large amount of navigation data and map information, and may again be a separate device from the server 150, or may be incorporated into the server 150. The processor 154 is further operatively connected to a transmitter 162 and a receiver 164 to transmit information to and receive information from the navigation device 200 via the communication channel 152. The signals sent and received may include data, communications, and / or other propagated signals. The transmitter 162 and the receiver 164 may be selected or designed according to the communication requirements and the communication technology used in the communication design of the navigation device 200. In addition, it should be noted that the functions of the transmitter 162 and the receiver 164 may be combined into a single transceiver.
[0216] As mentioned above, the navigation device 200 may be arranged to communicate with the server 150 via the communication channel 152, using the transmitter 166 and the receiver 168 to send and receive signals and / or data via the communication channel 152, noting that these devices may further be used to communicate with devices other than the server 150. In addition, the transmitter 166 and the receiver 168 are selected or designed according to the communication requirements and communication technology used in the communication design of the navigation device 200, and as described above with respect to Figure 2 As mentioned, the functionality of the transmitter 166 and the receiver 168 may be combined into a single transceiver. Of course, the navigation device 200 includes other hardware and / or functional parts, which will be described in more detail later herein.
[0217] The software stored in the server memory 156 provides instructions for the processor 154 and allows the server 150 to provide services to the navigation device 200. One service provided by the server 150 involves processing requests from the navigation device 200 and transmitting navigation data from the mass data storage device 160 to the navigation device 200. Another service that may be provided by the server 150 includes processing the navigation data using various algorithms for the desired application and sending the results of these calculations to the navigation device 200.
[0218] The server 150 constitutes a remote data source accessible via a wireless channel by the navigation device 200. The server 150 may include a network server located on a local area network (LAN), a wide area network (WAN), a virtual private network (VPN), or the like.
[0219] The server 150 may include a personal computer, such as a desktop or laptop computer, and the communication channel 152 may be a cable connected between the personal computer and the navigation device 200. Alternatively, a personal computer may be connected between the navigation device 200 and the server 150 to establish an Internet connection between the server 150 and the navigation device 200.
[0220] The navigation device 200 may be provided with information from the server 150 via information downloads, which may be updated automatically, frequently, or after the user connects the navigation device 200 to the server 150 and / or may be more dynamic after a more constant or frequent connection is made between the server 150 and the navigation device 200 via, for example, a wireless mobile connection and a TCP / IP connection. For many dynamic calculations, the processor 154 in the server 150 may be used to handle the bulk of the processing needs, however, the processor ( Figure 2 ) can also handle more processing and computing, typically without requiring a connection to server 150.
[0221] See also Figure 3 , it should be noted that the block diagram of the navigation device 200 does not include all components of the navigation device, but only represents many example components. The navigation device 200 is located within a housing (not shown). The navigation device 200 includes a processing circuit, which includes (for example) the processor 202 mentioned above, and the processor 202 is coupled to an input device 204 and a display device, such as a display screen 206. Although the input device 204 is mentioned in the singular form here, it will be understood by those skilled in the art that the input device 204 represents any number of input devices, including a keyboard device, a voice input device, a touch panel, and / or any other known input device for inputting information. Similarly, the display screen 206 can include any type of display screen, such as a liquid crystal display (LCD).
[0222] In one arrangement, one aspect of the input device 204 (the touch panel) is integrated with the display screen 206 to provide an integrated input and display device, including a touch pad or touch screen input 250 ( Figure 4) to enable both input of information (via direct input, menu selection, etc.) and display of information via a touch panel screen, such that a user need only touch a portion of the display screen 206 to select one of a plurality of displayed selections, or to activate one of a plurality of virtual or "soft" buttons. In this regard, the processor 202 supports a graphical user interface (GUI) that operates in conjunction with the touch screen.
[0223] In the navigation device 200, the processor 202 is operatively connected to the input device 204 via the connection 210 and is capable of receiving input information from the input device 204, and is operatively connected to at least one of the display screen 206 and the output device 208 via a corresponding output connection 212 to output information thereto. The navigation device 200 may include an output device 208, such as an audible output device (e.g., a speaker). Since the output device 208 can produce audible information for the user of the navigation device 200, it should also be equally understood that the input device 204 can include a microphone and software for receiving input voice commands. In addition, the navigation device 200 may also include any additional input devices 204 and / or any additional output devices, such as audio input / output devices.
[0224] The processor 202 is operatively connected to the memory 214 via a connection 216, and is further adapted to receive / send information from / to an input / output (I / O) port 218 via a connection 220, wherein the I / O port 218 may be connected to an I / O device 222 external to the navigation device 200. The external I / O device 222 may include, but is not limited to, an external listening device, such as headphones. The connection to the I / O device 222 may further be a wired or wireless connection to any other external device, such as a car stereo unit, for example for hands-free operation and / or speech-activated operation, for connection to headphones or headsets, and / or for connection to a mobile phone, wherein the mobile phone connection may be used to establish a data connection between the navigation device 200 and, for example, the Internet or any other network, and / or to establish a connection to a server via, for example, the Internet or some other network.
[0225] The memory 214 of the navigation device 200 includes a portion of non-volatile memory (e.g., to store program code), and a portion of volatile memory (e.g., to store data when executing program code). The navigation device also includes a port 228, which communicates with the processor 202 via a connection 230 to allow a removable memory card (commonly referred to as a card) to be added to the device 200. In the embodiment being described, the port is arranged to allow an SD (Secure Digital) card to be added. In other embodiments, the port may allow the connection of other formats of memory (e.g., Compact Flash (CF) card, memory stick, xD memory card, USB (Universal Serial Bus) flash drive, MMC (Multimedia) card, smart media card, micro drive, etc.).
[0226] Figure 3 Further illustrating the operational connection between the processor 202 and the antenna / receiver 224 via the connection 226, wherein the antenna / receiver 224 may be, for example, a GPS antenna / receiver and thus will act as a Figure 1 The GPS receiver 106. It should be understood that the antenna and receiver represented by reference numeral 224 are schematically combined for illustration purposes, but the antenna and receiver may be separately located components, and the antenna may be, for example, a GPS patch antenna or a helical antenna.
[0227] Of course, those skilled in the art will understand that Figure 3 The electronic components shown in the drawings are powered by one or more power supplies (not shown) in a conventional manner. Such power supplies may include internal batteries and / or inputs to a low voltage DC supply, or any other suitable arrangement. As will be appreciated by those skilled in the art, it is contemplated that Figure 3 For example, Figure 3 The components shown in may communicate with each other via wired and / or wireless connections, etc. Thus, the navigation device 200 described herein may be a portable or handheld navigation device 200 .
[0228] in addition, Figure 3 The portable or handheld navigation device 200 can be connected or "docked" to a vehicle, such as a bicycle, motorcycle, car or boat in a known manner. This navigation device 200 can then be removed from the docking position for portable or handheld navigation purposes. Indeed, in other embodiments, the device 200 may be arranged to be disposed to allow navigation by the user.
[0229] See also Figure 4 The navigation device 200 may include Figure 2 The unit includes an integrated input and display device 206 and other components (including, but not limited to, an internal GPS receiver 224, a processor 202, a power supply (not shown), a memory system 214, etc.).
[0230] The navigation device 200 may sit on an arm 252, which itself may be secured to a vehicle dashboard, window, etc. using a suction cup 254. This arm 252 is an example of a docking station to which the navigation device 200 may be docked. The navigation device 200 may be docked or otherwise connected to the arm 252 of the docking station by, for example, snapping the navigation device 200 to the arm 252. The navigation device 200 may then be rotated on the arm 252. To release the connection between the navigation device 200 and the docking station, a button (not shown) on the navigation device 200 may be pressed, for example. Other equally suitable arrangements for coupling and decoupling the navigation device 200 to a docking station are well known to those skilled in the art.
[0231] Steering Figure 5 , the processor 202 and memory 214 cooperate to support a BIOS (Basic Input / Output System) 282, which acts as an interface between the functional hardware components 280 of the navigation device 200 and the software executed by the device. The processor 202 then loads an operating system 284 from the memory 214, which provides an environment in which application software 286 (implementing some or all of the described route planning and navigation functionality) can run. The application software 286 provides an operating environment that includes a graphical user interface (GUI) that supports the core functions of the navigation device (such as map viewing, route planning, navigation functions, and any other functions associated therewith). In this regard, portions of the application software 286 include a view generation module 288.
[0232] In the embodiment being described, the processor 202 of the navigation device is programmed to receive GPS data received by the antenna 224 and, from time to time, store the GPS data, along with a timestamp when the GPS data was received, in the memory 214 to build up a record of the location of the navigation device. Each data record so stored can be considered a GPS position; that is, it is a position of the location of the navigation device and includes latitude, longitude, a timestamp, and an accuracy report.
[0233] In one embodiment, data is stored on a periodic basis, for example, every 5 seconds. Those skilled in the art will appreciate that other periods will be possible and that there is a balance between data resolution and memory capacity; i.e., as the resolution of the data increases by taking more samples, more memory is required to hold the data. However, in other embodiments, the resolution may be substantially every: 1 second, 10 seconds, 15 seconds, 20 seconds, 30 seconds, 45 seconds, 1 minute, 2.5 minutes (or indeed, any period between these periods). Thus, within the memory of the device, a record of the whereabouts of the device 200 at a point in time is established.
[0234] In some embodiments, it may be found that the quality of the captured data degrades as the period increases, and while the degree of degradation will depend at least in part on the speed of movement of the navigation device 200, a period of approximately 15 seconds may provide a suitable upper limit.
[0235] While the navigation device 200 is typically arranged to build a record of its whereabouts, some embodiments do not record data for a predetermined period and / or distance at the beginning or end of a journey. This arrangement helps to protect the privacy of the user of the navigation device 200, as it is possible to protect the location of his / her home and other frequently visited destinations. For example, the navigation device 200 may be arranged not to store data within approximately the first 5 minutes of a journey and / or within approximately the first mile of a journey.
[0236] In other embodiments, GPS may not be stored on a periodic basis, but may be stored in memory when a predetermined event occurs. For example, processor 202 may be programmed to store GPS data when the device passes an intersection, a change of road segment, or other such events.
[0237] In addition, the processor 202 is arranged to upload a record of the whereabouts (i.e., GPS data and timestamps) of the device 200 from time to time to the server 150. In some embodiments where the navigation device 200 has a permanent or at least normally present communication channel 152 connecting it to the server 150, the uploading of data occurs on a periodic basis that may be, for example, once every 24 hours. Those skilled in the art will appreciate that other periods are possible and may be generally any of the following periods: 15 minutes, 30 minutes, hourly, every 2 hours, every 5 hours, every 12 hours, every 2 days, every week, or any time between these periods. In fact, in such embodiments, the processor 202 may be arranged to upload the whereabouts record on a substantially real-time basis, but this may necessarily mean that the data is actually transmitted from time to time with a relatively short period between transmissions, and thus may be more correctly regarded as pseudo-real-time. In such pseudo-real-time embodiments, the navigation device may be arranged to buffer GPS positions within the memory 214 and / or on a card inserted in the port 228, and transmit these positions when a predetermined number has been stored. This predetermined number may be approximately 20, 36, 100, 200, or any number therebetween. Those skilled in the art will appreciate that the predetermined number is controlled in part by the size of the card within the memory 214 / port 228.
[0238] In other embodiments that do not have a generally present communication channel 152, the processor 202 may be arranged to upload a record to the server 152 when the communication channel 152 is created. This may be for example when the navigation device 200 is connected to a user's computer. Also, in such embodiments, the navigation device may be arranged to buffer GPS fixes within the memory 214 or on a card inserted in the port 228. In the event that the memory 214 or a card inserted in the port 228 becomes full of GPS fixes, the navigation device may be arranged to delete the oldest GPS fixes, and thus it may be regarded as a first-in, first-out (FIFO) buffer.
[0239] In the embodiment being described, a whereabouts record comprises one or more tracks, wherein each track represents the movement of the navigation device 200 over a 24 hour period. Each 24 is arranged to coincide with a calendar day, but in other embodiments this need not be the case.
[0240] Generally speaking, the user of the navigation device 200 gives his / her consent for a record of the device's whereabouts to be uploaded to the server 150. If consent is not given, the record is not uploaded to the server 150. The navigation device itself and / or the computer to which the navigation device is connected may be arranged to ask the user for his / her consent to this use of the whereabouts record.
[0241] The server 150 is arranged to receive a record of the whereabouts of the device and store this in the mass data storage device 160 for processing. Thus, over time the mass data storage device 160 accumulates a plurality of records of the whereabouts of the navigation device 200 that has uploaded the data.
[0242] As discussed above, the mass data storage device 160 also contains map data. This map data provides information about the location of road segments, points of interest, and other such information typically found on a map.
[0243] View now Figure 6 , this figure generally shows at 300 a histogram of average travel speeds on a segment within three specific periods (morning 302, noon 304, and evening 306). The average travel speed on a segment (which may have been calculated from raw data such as historical travel times on the segment) is an example of historical travel data. The histogram 300 can be considered to represent historical data in the sense that the recorded data is not live data. Therefore, the data is not a direct result of raw data collection occurring generally at the current time, recording actual events on the road segment within, for example, the last fifteen minutes. However, the data can be used to predict what may be happening on the current time segment based on the patterns and behaviors that are occurring with the traffic level.
[0244] The data used to complete the histogram 300 (historical average travel speed over a segment) was calculated using a track recorded by the server 150 of the type described above. If the location of the navigation device 200 is known from the track, the time elapsed between its entry into the segment and its exit from the segment can be recorded. As will be appreciated, the average travel speed over the segment can then be calculated assuming the segment distance is known.
[0245] The histogram 300 shows that there is relatively less slow moving traffic in the morning 302 and midday 304 periods, while there is substantially more relatively slow moving traffic in the evening period 306. The histogram 300 further shows that in all three periods 302, 304, and 306, there was a greater amount of relatively fast moving traffic.
[0246] The jam threshold speed 308 selected as 60 km / h is shown on the histogram 300. The jam threshold speed is an example of a jam condition. The jam threshold speed is the average speed of travel on the segment, below which travel is considered to be jammed. In this embodiment, the jam threshold speed is simply selected on the basis of a subjective view that the average speed should be considered to be jammed on a particular segment. However, in other embodiments, the jam threshold speed may be selected according to alternative criteria (e.g., the percentage of the average speed of travel on the segment during a cycle in the early morning when the influence of other vehicles is negligible, i.e., the free flow speed). In other words, the jam threshold speed may be a selected percentage of the free flow speed of the segment, and the free flow speed is the average speed of travel on the segment recorded during the selected low traffic cycle. As will be appreciated, once the jam threshold speed has been defined, all average speeds of travel below this speed on the segment are considered to be jammed.
[0247] Also shown on the histogram 300 is a jam speed 310 of 10 km / h. As can be seen, the jam speed 310 is time independent, i.e. the same jam speed 310 is provided for all three periods 302, 304 and 306. In this embodiment, the jam speed 310 has been selected as a hit pattern that is lower than the jam threshold speed 308. Therefore, the jam speed 310 is an indication of the most likely average travel speed over the segment when there is a jam. In other embodiments, the jam speed 310 may be defined differently, and this is discussed later.
[0248] With reference to histogram 300, a method for calculating the time-related jam probability will be explained. As will be appreciated, histogram 300 shows the total number of hits above and below the jam threshold speed 308 for each cycle 302, 304, 306. Considering these totals gives the ratio of each cycle of jam to non-jammed travel. This in turn allows the jam probability of each time cycle to be calculated. The jam probability calculated here will be an example of the generated segment data. For example, if the ratio of jam hits to non-jammed hits is 30:70 for a particular cycle, the jam probability of the cycle may be 30%. For example, the calculation of this situation may be expressed as a function. This jam probability may then be associated with the relevant segment as segment data, thereby giving the jam probability of travel in a particular cycle (e.g., morning). The jam speed may be used in conjunction with the jam probability to not only give the possibility of jam, but also further give the possible average travel speed on the segment in the jam event. In this example, the jam probability is completely based on historical data. As discussed below, the jam probability may be calibrated based on field data.
[0249] View now Figures 7A to 7D , illustrating alternative criteria for defining the jam speed. Fig. 7A Displaying a histogram 312, Figure 7B Displaying a histogram 314, Figure 7C A histogram 316 is shown, and Fig.7D A histogram 318 is shown. Each of these histograms 312, 314, 316, and 318 shows the historical average travel speed over a segment within a single cycle. Figure 6 300 , all of which use historical data.
[0250] In both histograms 312 and 314, there is a clear low speed pattern 320. Given that the jam threshold speed has been selected to be above the low speed pattern 320, the low speed pattern 320 may be particularly suitable for selection as a jam speed. For comparison, the fifth percentile 322 is also shown in both histograms 312 and 314.
[0251] In both histograms 316 and 318, there is no low speed pattern, or it is far less obvious. In this case, specifically, a percentile such as the fifth percentile 322 can be used as the jam speed.
[0252] In other embodiments there are further options for selecting the jam speed.The jam speed may for example be the average of all average travel speeds on the segment that are below the jam threshold speed.
[0253] Now combine Figure 2 See also Figure 8 , a flowchart illustrating an embodiment of the present invention is shown.
[0254] In a prediction step 400, a prediction is made as to whether a jam condition exists on a segment in the area covered by the electronic map. The nature of the prediction depends on the segment data available for the segment in question. In this embodiment, the segment data includes a time-dependent jam probability 402 and field data 404 related to the segment.
[0255] The time-dependent jam probability 402 has been selected from a plurality of other time-dependent jam probabilities to correspond to the current time (eg, Monday morning, between 8:30 am and 8:45 am). For the segment in question at the relevant time, each time-dependent jam probability has been calculated using the historical travel time 406 .
[0256] Live data 404 is information related to traffic conditions on a current time segment, such as live travel time on a segment from a GPS probe, or news data reporting traffic conditions on a segment.
[0257] The segment data is processed by an optimizer 407 run by the processor 154 of the server 150. In this embodiment, if the time-dependent jam probability exceeds a predefined value of 70%, the optimizer defaults to predicting a jam condition. However, the optimizer 407 also considers the live data according to a weighted system. In the case where there is a large amount of consistent live data 404, this is weighted more heavily, while in the case where the live data is inconsistent, unreliable and / or small in amount, it is weighted more lightly. Therefore, the optimizer 407 evaluates the importance and / or reliability of the live data 404 and checks for consistency with the predictions that would otherwise be made based solely on the time-dependent jam probability 402. After the live data 404 has been evaluated, the optimizer 407 determines whether there is a need to overrule the prediction as to whether a jam condition exists (otherwise a prediction would be made), and outputs the expected average travel speed on the segment according to its final prediction.
[0258] The output from the optimizer 407 occurs in an output step 408. Where a jam condition is predicted to exist, the expected average travel speed on the segment that is output is a jam speed 410. The jam speed 410 is calculated based on the historical travel times 406 that were considered jammed (i.e., below a jam threshold speed). Where a jam condition is predicted to not exist, the expected average travel speed on the segment that is output is a default speed, in this case the average of all available historical average travel speeds on the segment during the time period in question (e.g., Monday morning, between 8:30 a.m. and 8:45 a.m.).
[0259] In this embodiment, the output is transmitted to the navigation device 200 via the transmitter 162 over the communication channel 152. On the navigation device, possible routes are explored in an exploration step 412 based on the requested route parameters (e.g., origin and destination) and using map data stored on the navigation device 200. The goal of this exploration may be to find the fastest or most fuel-efficient route (although those skilled in the art will appreciate that many other factors may also be considered). In the case of a segment for which an output has been generated for a route, the expected average travel speed on that segment is used, which is either a jam speed or a default speed. Finally, a navigable route is generated in a generation step 414.
[0260] As you will understand, Figure 8 The flowchart of can be executed exclusively by the navigation device 200 when offline. For example, it may be the case that the navigation device 200 collects / captures information (e.g., field data) while moving, and stores other segment data thereon.
[0261] In the embodiments described above, the time-dependent jam probability itself is not calibrated by incorporating live data. Instead, live data is only used to perform a final check. However, in alternative embodiments, live data may additionally or alternatively be used to calibrate the time-dependent jam probability by incorporating live data with historical travel times by the optimizer. Additionally, there are many other possible ways in which live data may be used to influence whether a jam condition is predicted, such as changing the required jam probability percentage, or even switching to a completely different jam probability if it is more appropriate.
[0262] Although in the above embodiment, the expected average speed of travel on the segment is output, it will be readily appreciated by those skilled in the art that many additional or alternative outputs are possible, such as issues of congestion warnings or instructions to maintain or adjust the status quo. Outputs such as these may be all that is required for the navigation device 200 to select an appropriate expected average speed of travel on the segment. Indeed, it should be further noted that although some of the method steps are described as occurring on the server 150 and some on the navigation device 200, any of the steps may be performed centrally or locally.
[0263] View now Fig. 9 , shows an architecture for route generation, illustrating potential data inputs, processing, and outputs to the device for use. The architecture includes several inputs: live Global System for Mobile Communications (GSM) probe data 500, live Global Positioning System (GPS) probe data 502, live Traffic Message Channel (TMC) jam messages 504, live loop detection data 506, live news data 508, and historical jam probability and jam speed data 510.
[0264] In the processing step, inputs 500, 502, 504, 506, 508 and 510 are processed by an optimizer, in this case a data fusion engine 512. Live GSM probe data 500, live GPS probe data 502, live TMC jam messages 504, live loop detection data 506 and live news data 508 are used to give an indication of any real-time jams 514 currently occurring on the segment, and to give an approximation of real-time travel speeds 516. Historical jam probability and jam speed data 510 give jam speeds 518 and jam condition predictions 520 based on historical data. The data fusion engine 512 processes data from live and historical sources to predict whether a jam condition exists on the segment, and if so, to provide a jam speed. This data is then output.
[0265] The architecture includes several devices to which output may be sent: an embedded navigation device 522, a personal navigation device 524, a web-based route planner 526, a radio DJ portal 528, a business-to-government (B2G) host digital terminal (HDT) or hierarchical data format (HDF) 530, or an original equipment manufacturer (OEM) host digital terminal (HDT) or hierarchical data format (HDF) 532. When a device has received the output, it may use the output, for example, in route planning, or to display a report on conditions on all or part of the network.
[0266] View now Fig.10 , shows a graph indicating the variability of the amount of live data 600 available within a period. The graph also shows an urban lower cutoff threshold 602 for the live data 600 and a rural lower cutoff threshold 604 for the live data.
[0267] In some embodiments, it is advantageous to utilize live data to calibrate jam probabilities or to check whether jam condition predictions should be made. However, in the presence of lower amounts of live data, its use may be counterproductive, as traffic data tends to have a random component. Therefore in some embodiments, a lower cutoff threshold for the amount of live data may be set below which it will not be used. Fig.10 It is noted that this lower threshold can vary. In this embodiment, the lower threshold varies depending on the nature of the road the surface covers (rural or urban). This variation can be justified if, for example, it is known that live data from rural sections is more random than live data from urban sections.
[0268] exist Fig.10 In the embodiment of , when above a lower cutoff threshold 602, live data is only used on urban segments, and when above a rural lower cutoff threshold 604, live data is only used on rural segments.
[0269] View now Fig.11 and12 , illustrating regional inspection and deviation trends for a set of segments.
[0270] A regional check may be performed, wherein the live data for a set of segments is checked for consistency with the corresponding jam probabilities and / or historical travel times used for their calculation and / or prediction of whether a jam condition exists based on the jam probabilities. The results of the check on each segment may then be connected and evaluated for deviation trends. This may be particularly useful because traffic volume and / or traffic flow may be a regional phenomenon (i.e., the traffic situation on one particular segment may be greatly affected by the traffic situation on surrounding segments). Therefore, regional adaptation relative to a predetermined map area, a predetermined radius, possible routes into or out of the area, a predetermined direction of travel, known bottlenecks and / or traffic hotspots may be particularly useful.
[0271] Where the inspection indicates a deviation trend from which a jam prediction would be expected from the jam probability based on historical average travel speeds, mitigating steps may be taken to alter the jam prediction. These steps may occur for the segments in the set, but may also occur for other segments that may be affected by one or more of the segments in the set.
[0272] Potential steps include: 1) adjusting the required jam probability in order to predict jam conditions; 2) using live data or additional live data in the jam probability calculation; 3) adjusting the weighted or probabilistic average to favor or further favor live data; 4) using inconsistencies to override jam condition predictions and make jam condition predictions where otherwise no prediction would be made; and 5) initiating a switch to the use of one or more different jam probabilities that are more consistent with live data. Such steps may be expressed as map data for the segment of interest.
[0273] In some alternative embodiments, the deviation trend may lead to a partial or complete override of the use of the jam probability for a period. For example, the situation may be that the live data indicates that the jam probability is completely unsuitable for use in predicting whether a jam condition exists for a particular period.
[0274] As will be appreciated, performing a regional check can allow accurate adjustment of the jam probability for a segment where there is little or no live data by drawing interference from other segments included in the set. In addition, a regional check can provide an enhanced understanding of conditions on the lower portion of the network, thereby reducing the possibility of misinterpretation.
[0275] In some embodiments, the deviation trend may be assessed by calculating the percentage of segments in the set that are congested according to live data (e.g., by comparing each average travel speed over the segment to a congestion threshold speed, and comparing the proportions above and below the congestion threshold speed). This may be compared to the average over all congestion probabilities for the segments in the set to give a congestion probability deviation. The congestion probability deviation may then be smoothed over a period (e.g., 30 minutes).
[0276] As will be appreciated, calculation of a jam probability deviation may allow for subtle distinctions to be drawn between traffic conditions on segments in a set and ultimately potentially outside of the set.
[0277] Fig.11 A graph of relative deviation versus time of day is shown. The graph plots the jam probability deviation 700 for a set of segments, and the speed deviation 702 for the same set. The speed deviation shows the average deviation from the free flow speed for all segments in the set. The set of segments consists of several known traffic bottlenecks in a particular city.
[0278] As in Fig.11 As can be seen in the example of , the traffic situation is unusual in that there is up to about 45% reduction in the probability of jam when the live data is taken into account; it can be seen that the relative deviation of line 700 drops to about 0.55. This indicates that for the traffic bottlenecks in the set, there is a reduced chance of jam; i.e. it is more likely that there will be free-flowing traffic. This may be caused by the unusual reduction in traffic volume. Therefore, as might be expected, there is virtually no speed deviation; i.e. the relative deviation of line 702 remains roughly at a value of 1. Regional inspection of deviation trends of this nature may suggest reduced jam probabilities for other sections in the city, even where there is little or no live data for these other sections. The data is data from a set of sections that have been used to modify sections in adjacent areas. This is because unjammed traffic bottlenecks are a good indicator of the reduced likelihood of jams in the surrounding network.
[0279] Fig.12 Similar to Fig.11 , has a graph illustrating another area inspection given different traffic scenarios. Here, the jam probability deviation 800 for a set of segments is low, indicating that the likelihood of jams is roughly what would be expected based on historical trends; i.e., line 800 remains roughly about 1, indicating that the field data supports the jam probability. Although the speed deviation 802 illustrates a decrease in average speed over the segments; line 802 decreases below a relative deviation of 1. Thus, the graph shows that jam probability and average speed do not necessarily follow each other. As shown by Fig.12The traffic situation described may be the result of snow, for example, resulting in a general reduction in traffic speeds without an increased probability of jams. Thus, the area check has correctly identified that the probability of jams is relatively normal, but the average speed is decreasing.
Claims
1. A method for predicting whether there is a jam on a segment in an electronic map, the electronic map representing a network in an area covered by the electronic map, each segment representing a navigable segment in the network, and each segment in the electronic map having associated therewith a stored jam probability indicating the likelihood of jam on the segment and calculated using historical travel data, the method comprising: determining a set of a plurality of sections of the electronic map, wherein traffic conditions on a section in the set are affected by traffic conditions on other sections in the set; obtaining live travel data indicative of current or relatively current traffic conditions on at least some of the plurality of segments in the set; predicting whether a segment in the set is congested using the stored congestion probabilities on the segment and the obtained live travel data; as well as When congestion is predicted, a congestion warning is output for the segment.
2. The method of claim 1 , wherein predicting whether the segment is congested using the stored congestion probability of the segment and the acquired live travel data comprises: calculating an adjusted jam probability for the segment in the set using the stored jam probability for the segment and the obtained live travel data; and Whether the segment is congested is predicted using the adjusted congestion probability of the segment.
3. The method of claim 1 , wherein predicting whether the segment is congested using the stored congestion probability of the segment and the acquired live travel data comprises: predicting whether the segment is congested using the stored congestion probability of the segment; and The obtained live travel data and the predicted jam condition for the segment are checked for consistency, and the predicted jam condition is overturned when a discrepancy is found. The method according to claim 2 or 3, wherein the section jam is predicted when the jam probability exceeds a predetermined value. The method of claim 4 , wherein the predetermined value is based on acquired live travel data.
6. The method of claim 1 , wherein predicting whether the segment is congested using the stored congestion probability of the segment and the acquired live travel data comprises: Whether the segment is jammed is predicted using a stored jam probability for the segment, wherein the segment is predicted to be jammed when the jam probability exceeds a predetermined value, and wherein the predetermined value is based on obtained live travel data.
7. The method of any of claims 1-3, wherein each of the plurality of segments has associated therewith a plurality of time-dependent jam probabilities reflecting a change in jam probability over time within a selected time interval.
8. A method as claimed in any one of claims 1 to 3, wherein the output congestion warning for the segment comprises an expected average speed of travel on the segment.
9. A method as claimed in claim 8, wherein each of the plurality of segments has associated therewith a stored jam speed calculated using historical travel data and indicating the speed over the segment when the segment is considered to be jammed, and wherein the expected average travel speed is the stored jam speed or a speed based thereon.
10. A system for predicting whether there is congestion on a segment in an electronic map, the electronic map representing a network in an area covered by the electronic map, each segment representing a navigable segment in the network, and each segment in the electronic map having a stored congestion probability associated therewith, the congestion probability indicating the likelihood of congestion on the segment and calculated using historical travel data, the system comprising at least a processor configured to: determining a set of a plurality of sections of the electronic map, wherein traffic conditions on a section in the set are affected by traffic conditions on other sections in the set; obtaining live travel data indicative of current or relatively current traffic conditions on at least some of the plurality of segments in the set; predicting whether a segment in the set is congested using the stored congestion probabilities on the segment and the obtained live travel data; as well as When congestion is predicted, a congestion warning is output for the segment.
11. The system of claim 10, wherein predicting whether the segment is congested using the stored congestion probability of the segment and the acquired live travel data comprises: calculating an adjusted jam probability for the segment in the set using the stored jam probability for the segment and the obtained live travel data; and Whether the segment is congested is predicted using the adjusted congestion probability of the segment.
12. The system of claim 10, wherein predicting whether the segment is congested using the stored congestion probability of the segment and the acquired live travel data comprises: predicting whether the segment is congested using the stored congestion probability of the segment; and The obtained live travel data and the predicted jam condition on the segment are checked for consistency, and the predicted jam condition is overturned when a discrepancy is found.
13. The system of claim 11 or 12, wherein the segment jam is predicted when the jam probability exceeds a predetermined value.
14. The system of claim 10, wherein predicting whether the segment is congested using the stored congestion probability of the segment and the acquired live travel data comprises: Whether the segment is jammed is predicted using a stored jam probability for the segment, wherein the segment is predicted to be jammed when the jam probability exceeds a predetermined value, and wherein the predetermined value is based on obtained live travel data.
15. The system of claim 10, wherein the system is a server.
16. A machine-readable medium containing instructions which, when read by a machine, cause the machine to operate according to the method of any one of claims 1-9.
