Patent Application
20110106416
The following disclosure relates generally to techniques for combining historical and current information about road traffic conditions in order to generate expected information regarding current and/or future road traffic conditions, such as for use in improving travel over roads in one or more geographic areas.
As road traffic has increased, the effects of increasing traffic congestion have had growing deleterious effects on business and government operations and on personal well-being. Accordingly, efforts have been made to combat the increasing traffic congestion in various ways, such as by obtaining information about current traffic conditions and providing the information to individuals and organizations. Such current traffic condition information may be provided to interested parties in various ways (e.g., via radio broadcasts, an Internet Web site that displays a map of a geographical area with color-coded information about current traffic congestion on some major roads in the geographical area, information sent to cellular telephones and other portable consumer devices, etc.).
One source for obtaining information about current traffic conditions includes observations manually supplied by humans (e.g., traffic helicopters that provide general information about traffic flow and accidents, reports called in by drivers via cellphones, etc.), while another source in some larger metropolitan areas is networks of traffic sensors capable of measuring traffic flow for various roads in the area (e.g., via sensors embedded in the road pavement). Unfortunately, various problems exist with respect to such information, as well as to information provided by other similar sources. For example, many roads do not have road sensors (e.g., geographic areas that do not have networks of road sensors and/or arterial roads that are not sufficiently large to have road sensors as part of a nearby network), and even roads that have road sensors may often not provide accurate data (e.g., sensors that are broken and do not provide any data or provide inaccurate data). In addition, while observations that are manually supplied by human may provide some value in limited situations, such information is typically limited to only a few areas at a time and typically lacks sufficient detail to be of significant use.
Techniques are described for generating information regarding expected current and/or future road traffic flow conditions in various ways, and for using generated traffic flow condition information in various ways. In at least some embodiments, the expected road traffic flow conditions for a particular segment or other portion of a road are generated by combining historical representative information about road traffic flow conditions for that road portion with current or otherwise recent information about actual traffic flow on or near that road portion. The historical information may include, for example, data readings from physical sensors that are near or embedded in the roads and/or data samples from vehicles and other mobile data sources traveling on the roads, and may be filtered, conditioned and/or aggregated in various ways (e.g., to represent average traffic conditions for particular time periods of particular days of the week or other types of days). The current or otherwise recent information about actual traffic flow may include, for example, data samples that are obtained from vehicles and/or other mobile data sources that are currently or recently traveling on particular roads and road portions of interest. Such techniques for combining historical representative traffic flow information and recent actual traffic flow information may, for example, provide benefits for estimating expected traffic flow conditions information for vehicles traveling on roads with structural flow obstructions that cause reduced traffic flow at certain road locations and during at least some time—in particular, the estimating of the expected traffic flow conditions information may be based at least in part on fitting or otherwise adapting partial actual traffic flow information about a vehicle's actual travel path to a historical travel profile for a road that includes representative traffic flow information for various combinations of road locations and time periods. Additional details related to generating and using expected traffic flow condition information in particular manners are included herein. In addition, in at least some embodiments, some or all of the described techniques are automatically performed under control of an embodiment of an Estimated Traffic Information Provider (“ETIP”) system, as described below.
Expected information may be generated for a variety of types of useful measures of traffic conditions in various embodiments, such as for each of multiple road locations (e.g., road segments, road map links, particular points on roads, etc.) or other portions of roads during each of multiple time periods. For example, such traffic conditions measures may include an average speed, a volume of traffic for an indicated period of time, an average occupancy time of one or more traffic sensors or other locations on a road (e.g., to indicate the average percentage of time that a vehicle is over or otherwise activating a sensor), one of multiple enumerated levels of road congestion (e.g., measured based on one or more other traffic conditions measures), etc. Values for each such traffic conditions measure may be represented at varying levels of precision in varying embodiments. For example, values for the average speed conditions measure may be represented at the nearest 1-MPH (“mile per hour”) increment, the nearest 5-MPH increment, in 5-MPH buckets (e.g., 0-5 MPH, 6-10 MPH, 11-15 MPH, etc.), in fractions of 1-MPH increments at varying degrees of precision, etc. Such traffic conditions measures may also be measured and represented in absolute terms and/or in relative terms (e.g., to represent a difference from typical or from maximum). Additional details related to the generation of the expected information are included below.
In some embodiments, historical traffic data may include information about traffic for various target roads of interest in a geographical area, such as for a network of selected roads in the geographic area. In some embodiments, one or more roads in a given geographic region may be modeled or represented by the use of road links. Each road link may be used to represent a portion of a road, such as by dividing a given physical road into multiple road links. For example, each link might be a particular length, such as a one-mile length of the road. Such road links may be defined, for example, by governmental or private bodies that create maps (e.g., by a government standard; by commercial map companies as a quasi-standard or de facto standard; etc.) and/or by a provider of the Expected Traffic Information Provider system (e.g., manually and/or in an automated manner), such that a given road may be represented with different road links by different entities.
In addition, in some embodiments one or more roads in a given geographic region may be modeled or represented by the use of road segments, such as road segments defined by a provider of the Expected Traffic Information Provider system (e.g., manually and/or in an automated manner). Each road segment may be used to represent a portion of a road (or of multiple roads) that has similar traffic conditions characteristics for one or more road links (or portions thereof) that are part of the road segment. Thus, a given physical road may be divided into multiple road segments, such as with multiple road segments that correspond to successive portions of the road, or alternatively in some embodiments by having overlapping or have intervening road portions that are not part of any road segment. In addition, each road segment may be selected so as to include some or all of one or more road links, such as a series of multiple road links. Furthermore, a road segment may represent one or more lanes of travel on a given physical road. Accordingly, a particular multi-lane road that has one or more lanes for travel in each of two directions may be associated with at least two road segments, with at least one road segment associated with travel in one direction and with at least one other road segment associated with travel in the other direction. Similarly, if a road link represents a multi-lane road that has one or more lanes for travel in each of two directions, at least two road segments may be associated with the road link to represent the different directions of travel. In addition, multiple lanes of a road for travel in a single direction may be represented by multiple road segments in some situations, such as if the lanes have differing travel condition characteristics. For example, a given freeway system may have express or high occupancy vehicle (“HOV”) lanes that may be beneficial to represent by way of road segments distinct from road segments representing the regular (e.g., non-HOV) lanes traveling in the same direction as the express or HOV lanes. Road segments may further be connected to or otherwise associated with other adjacent road segments, thereby forming a chain or network of road segments.
The roads and/or road segments/links for which expected traffic conditions information is generated may be selected in various manners in various embodiments. In some embodiments, expected traffic conditions information is generated for each of multiple geographic areas (e.g., metropolitan areas), with each geographic area having a network of multiple inter-connected roads. Such geographic areas may be selected in various ways, such as based on areas in which historical traffic data is readily available (e.g., based on networks of road sensors for at least some of the roads in the area), in which traffic congestion is a significant problem, and/or in which a high volume of road traffic occurs at times. In some such embodiments, the roads for which expected traffic conditions information is generated include those roads for which historical traffic conditions information is available, while in other embodiments the selection of such roads may be based at least in part on one or more other factors (e.g., based on size or capacity of the roads, such as to include freeways and major highways; based on the role the roads play in carrying traffic, such as to include arterial roads and collector roads that are primary alternatives to larger capacity roads such as freeways and major highways; based on functional class of the roads, such as is designated by the Federal Highway Administration; etc.). In addition, in some embodiments, expected traffic conditions information is generated for some or all roads in one or more large regions, such as each of one or more states or countries (e.g., to generate nationwide data for the United States and/or for other countries or regions). In some such embodiments, all roads of one or more functional classes in the region may be covered, such as to include all interstate freeways, all freeways and highways, all freeways and highways and major arterials, all local and/or collector roads, all roads, etc. In other embodiments, expected traffic conditions information generation calculations may be made for a single road, regardless of its size and/or inter-relationship with other roads.
In at least some embodiments, expected traffic conditions information for a particular road link or other portion of road is generated for each of one or more traffic flow aggregation classifications or categories, such as for some or all road links or other road portions. In particular, in at least some embodiments, various time-based categories are selected, and expected traffic conditions information is separately generated for each of the time-based categories. As previously noted, in some embodiments, various time periods of interest may be selected, and each time-based category may be associated with one or more such time periods. As one example, time periods may be based at least in part on information about day-of-week and/or time-of-day (e.g., hour-of-day, minute-of-hour-of-day, etc.), such that each time-based category may correspond to one or more days-of-week and one or more times-of-day on those days-of-week. If, for example, each day-of-week and each hour-of-day are separately modeled with time-based categories, 168 (24*7) time-based categories may be used (e.g., with one category being Mondays from 9am-9:59am, another category being Mondays from 10 am-10:59 am, another category being Sundays from 9 am-9:59 am, etc.). In this example, expected traffic conditions information for a road link and a particular time-based category, such as Mondays from 10 am-10:59 am, is generated at least in part by aggregating historical traffic information that corresponds to that road link and category, such as for traffic conditions information reported for that road link on prior Mondays between 10 am and 10:59 am.
Alternatively, a particular time-based category may include a grouping of multiple days-of-week and/or hours-of-day, such as if the grouped times are likely to have similar traffic conditions information (e.g., to group days of week and times of day corresponding to similar work commute-based times or non-commute-based times). A non-exclusive list of examples of day-of-week groupings include the following: (a) Monday-Thursday, Friday, and Saturday-Sunday; (b) Monday-Friday and Saturday-Sunday; (c) Monday-Thursday, Friday, Saturday, and Sunday; and (d) Monday-Friday, Saturday, and Sunday. A non-exclusive list of examples of time-of-day groupings include the following: (a) 6 am-8:59 am, 9 am-2:59 pm, 3 pm-8:59 pm, and 9 pm-5:59 am; and (b) 6 am-6:59 pm and 7 pm-5:59 am. Accordingly, one example group of time-based categories for which expected traffic conditions information may be generated is as follows:
Furthermore, in some embodiments, time periods for time-based categories may be selected for time increments of less than an hour, such as for 15-minute, 5-minute, or 1-minute intervals. If, for example, each minute-of-day for each day-of-week is separately represented, 10,080 (60*24*7) time-based categories may be used (e.g., with one category being Mondays at 9:00 am, another category being Mondays at 9:01 am, another category being Sundays at 9:01 am, etc.). In such an embodiment, if sufficient historical data is available, expected traffic conditions information may be generated for a particular road link and a particular time-based category using only historical traffic information that corresponds to that road link and the particular minute for the time-based category, while in other embodiments historical information for a larger time duration may be used. For example, for an example time-based category corresponding to Mondays at 9:01 am, historical information from a rolling time duration of one hour (or another time duration) surrounding that time may be used (e.g., on Mondays from 8:31 am-9:31 am, on Mondays from 8:01 am-9:01 am, on Mondays from 9:01 am-10:01 am, etc.). In other embodiments, periods of time may be defined based on other than time-of-day and day-of-week information, such as based on day-of-month, day-of-year, week-of-month, week-of-year, etc.
In addition, in at least some embodiments, the traffic flow aggregation classifications or categories used for expected traffic conditions information may be based on temporary or other variable conditions other than time that alter or otherwise affect traffic conditions, whether instead of or in addition to time-based categories. In particular, in at least some embodiments, various condition-based categories may be selected, and expected traffic conditions information may be separately generated for each of the condition-based categories for one or more road links or other road portions. Each such condition-based category may be associated with one or more traffic-altering conditions of one or more types. For example, in some embodiments, traffic-altering conditions related to a particular road link or other road portion that are used for condition-based categories for that road link/portion may be based on one or more of the following: weather status (e.g., based on weather in a geographic area that includes the road link/portion); status regarding occurrence of a non-periodic event that affects travel on the road link/portion (e.g., based on an event with sufficient attendance to affect travel on the road link/portion, such as a major sporting event, concert, performance, etc.); status regarding a current season or other specified group of days during the year; status regarding occurrence of one or more types of holidays or related days; status regarding occurrence of a traffic accident that affects travel on the road link/portion (e.g., a current or recent traffic accident on the road link/portion or on nearby road links/portions); status regarding road work that affects travel on the road link/portion (e.g., current or recent road work on the road link/portion or on nearby road links/portions); and status regarding school sessions that affects travel on the road link/portion (e.g., a session for a particular nearby school, sessions for most or all schools in a geographic area that includes the road link/portion, etc.).
For illustrative purposes, some embodiments are described below in which specific types of measures of expected traffic conditions are generated in specific ways using specific types of input, and in which generated measures are used in various specific ways. However, it will be understood that such information may be generated in other manners and using other types of input data in other embodiments, that the described techniques may be used in a wide variety of other situations, that information for other types of traffic conditions measures or other measures may similarly be generated and used in various ways, and that the invention is thus not limited to the exemplary details provided.
In some embodiments, various historical data for particular roads may be available, such as to reflect traffic patterns on both highways and secondary roads, and various current or otherwise recent traffic condition information may also be available for those roads (e.g., real-time or near-real-time data samples from vehicles and/or other mobile data sources that are currently or recently traveling on particular roads, also referred to herein as “recent traffic probe data”). If so, the historical traffic information may be combined with the recent traffic probe data to provide estimates of expected current and/or future traffic conditions that have benefits beyond that available from either the historical traffic information alone or the recent traffic probe data alone. As one example, such techniques for combining historical traffic information and recent traffic probe data may provide particular benefits in at least some embodiments for estimating expected average traffic speeds and travel times on roads with structural flow obstructions that are part of the road, such as signal lights, stop signs, traffic circles, speed bumps, crosswalks, intersections, rail crossings, merging lanes or roads, etc., and/or with non-structural flow obstructions that are not part of the road, such as distracting or interesting sights visible from the road, occasional animal crossings, etc. In addition, such techniques for combining historical traffic information and recent traffic probe data may provide particular benefits in at least some embodiments for estimating expected average traffic speeds and travel times on secondary roads that are not highways, such as arterial roads and/or other local city streets, while in other embodiments such techniques may be used with highway roads, whether in addition to or instead of non-highway roads.
In the following illustrative embodiment, a particular illustrated technique for combining historical traffic information with recent traffic probe data to generate estimates of expected current and/or future traffic conditions is described, although it will be appreciated that other embodiments may use other techniques. In the illustrated technique, activities are performed to generate estimates of expected current and/or future traffic conditions, as follows: computing or otherwise generating a “road profile” or “travel profile” for a particular portion of a road; linking together multiple recent traffic probe data points from an individual vehicle to represent portions of the actual travel path of the vehicle, for each of numerous vehicles; and fitting the multiple probe data points from a vehicle's actual travel path to the generated profile for a road portion to which the actual travel path corresponds. The fitting of the multiple probe data points from a vehicle's actual travel path to a generated travel profile may include various activities in various embodiments, such as interpolating travel speeds or other travel flow condition information for the vehicle for portions of the actual travel path for which probe data points are not available, adjusting a portion of the generated travel profile to which the available probe data points are fitted to correspond to different time periods than an actual time period for the actual travel path and/or to correspond to different locations in the travel profile than the actual locations of the actual travel path, etc. Additional exemplary details related to these types of activities follow.
Computing A Travel/Road Profile
A road or travel profile as discussed herein may include representative traffic flow conditions values or other information, such as average or otherwise typical traffic speeds averaged over a period of time for a portion of road. Consider an example portion of road that covers several miles. Average speeds of vehicles at some or all points or other locations on this road portion may be of interest at various times. By collecting reported speeds for this road portion over an extended period of time (referred to as the road “history”), such as at least in part from vehicles or other mobile data sources that travel on the road portion and/or at least in part from road sensors associated with locations on the road portion, the average reported speed may be estimated for some or all points on the road portion, and error estimates (or “error bars”) around an average reported speed for a point may further be generated. As one example, the standard deviation of the average reported speed may be used as a estimate of the error of the average speed for a particular time of day in at least some embodiments. Thus the travel/road profile may be represented or construed in some situations as a 3-dimensional surface, with the x-dimension being time of day, the y-dimension being the distance along the road portion from a starting point, and the z-dimension being the average speed. In other embodiments, a travel/road profile may have other forms, such as a 2-dimensional surface with the x-dimension being one of time-of-day and distance along the road portion from a starting point, and the y-dimension being average speed or other representative traffic flow conditions information.
Even if historical traffic data is collected for the road portion over a very long time, there may be some locations of the road portion for which there is not sufficient data to generate an average speed or other representative traffic flow conditions information, depending on the spatial resolution used to represent the locations (e.g., every foot, every 10 feet, every 100 feet, every 1000 feet, etc.). In such situations, historical data may only be available at intermittent points along the road portion. Actions to smooth this historical data and interpolate/extrapolate data for other points may be performed in various manners in various embodiments. For example, one approach may be the fitting of a parametric surface to the historical data points, while another approach may be the fitting of a non-parametric surface to the historical data points. Yet another approach involves the creation of a “grid” of values that approximates a surface. The grid creation process involves first organizing the road portion into fixed-distance sections (optionally based on defined road links), which will be referred to as “edges” for purposes of this discussion. Such edges may have a length that is determined by the density of the historical data, or instead by other conditions (e.g., based on defined road links). In either case, after the road portion is divided into a fixed number of edges of set length, the average speed and standard deviation for a given time of day and given edge may be computed by using reported speeds (e.g., from physical road sensors and/or from mobile data sources) on that edge or other edges over the road history for that time of day.
In some situations, the average speed in neighboring edges may be very similar, such as for at least some highways in which average speeds are often constant over long stretches. Accordingly, a “segmentation” step may be performed in generating the travel/road profile, involving the merging of neighboring edges in order to reduce the total number of segments representing a road. A number of merging techniques may be used in various embodiments, and a particular example of one such merging technique follows. In particular, beginning at the first point in the road portion, consider the average speed difference between the first and the second edges. The statistical significance of this difference may be calculated to decide whether to merge these two edges—for example, given two edges i and i+1, the following is used in the example merging technique to compute the t-statistics of the two edges,
where v, represents velocity, σi represents the standard deviation, and ni is the number of historical data samples in edge i collected during a length of time for a particular time period (e.g., data may be collected for a length of time of 2 years for a particular time period of 4 pm to 5 pm on Mondays). If the t value is smaller than a certain threshold, the two edges will be merged together to form a new segment. The same procedure may then be performed on the new segment (if the first and second segments are merged) and the edge next to it (in this example, the third segment). This procedure is repeated until all the edges are checked. Other factors may also be incorporated as additional or alternative criteria for merging two similar edges, such as absolute speed difference between the two edges, difference in the standard deviation of the speed between two edges, etc.
In some situations, sufficient data may not be available to compute average speeds for each minute of a day, for example, even when edges are merged. If so, a 24-hour period may be divided into larger time periods (or “time bins”). For example, in a particular embodiment and situation, a time bin may be a 1-hour period, a multi-hour period (e.g., the morning congestion period from 5 am-10 am), an entire day of the week, etc. As discussed above, the merging activities are performed with respect to particular time bins and edges.
Determining Vehicle Travel Paths
Data samples from vehicles and other mobile data sources often include indications of Point (e.g., GPS coordinates), Heading and Speed (PHS), and may also include a proxy identity or some other form of identifier for the vehicle or other device reporting a particular PHS data sample, although the identifier may, for example, be a unique number that does not reveal particular identifying data for a vehicle/device or its driver or other user. In determining information for a travel path, some or all of the data points from a particular vehicle or other device may be gathered, and used to used to represent an actual travel path for that vehicle/device. In particular, in some embodiments, a particular travel path may be the longest set of data points which may be linked together for that vehicle/device. Travel paths may be very long (many miles) or very short (a few feet). Travel paths may be broken in various manners depending on the embodiment, such as if a vehicle/device reports zero speeds (or speeds below a defined speed threshold) for a period of time longer than a defined time threshold, if a vehicle/device reports headings whose variability exceeds a defined threshold, etc.
Fitting A Vehicle Travel Path To A Travel Profile
Consider a travel/road profile for a particular road portion. Historical speeds may rise and fall as a function of distance along the road, such as to reflect persistent congestion regions (e.g., based on traffic flow obstructions such as signal lights, etc.). Recent traffic probe data for this road portion, as represented by travel paths for one or more vehicles/devices, may not match the historical data in the road profile for various reasons. For example, the lack of match may be because travel conditions are different for the particular time corresponding to the travel path(s) rather than a larger time period or time bin for which the historical speed is averaged, because external conditions may be different (e.g., there is a school holiday on the day corresponding to the travel path(s), causing a common congestion region to have much less traffic and resulting congestion), because some or all of the vehicle(s)/device(s) that reported the travel path(s) passed through a traffic light without stopping instead of having to wait as is more typical for the historical average speeds, etc. Performing fitting activities enable a particular vehicle/device actual travel path to be matched to the travel/road profile. Conceptually, such activities involve matching recent traffic probe data speed estimates to the historical speeds represented by the road profile, for the time of day in which the recent traffic probe data has been reported. For example, point pairs may be separated in time by 1 minute or more, and during this time, the reporting vehicle/device may travel a significant distance. Fitting activities may include performing “warping” activities to, for some or all edges of the roadway for which sufficient (e.g., any) traffic probe data points is not available, estimate the travel times over those edges that are most consistent with the travel/road profile. For example, if two speed data points are reported from the same vehicle and are separated by a period of time that is sufficiently large that the vehicle may travel a significant distance, it may be desirable to be able to estimate multiple particular speeds at multiple particular intermediate locations between the data points. In order to do so, historical data may be used to estimate such speeds between the data points, with the described fitting techniques performing such speed estimation between data points in such a manner that the overall travel time is consistent with the time between the reported data points, but with the estimated multiple speeds varying in a manner that reflects variations in typical historical speed variations for the multiple intermediate locations between the data points.
As one particular example, the following equation fits point-pair speeds and computed travel time to the historical speed travel profile of the road between the point pair. With respect to the following equation, it is assumed that the historical average speed viavg and its standard deviation σi are available for each segment i of the road portion for which the travel time will be fitted. The travel time tiavg and associated standard deviation in the travel time σit are computed for segment i according to:
where di is the distance of road segment i, and distance and speed have been appropriately converted to common units. A weight W is then produced according to:
where the difference between the historical travel time and the measured travel time for the paired-points is given by Δt=tavg−tmeasured. Note that W is independent of road segment in this equation. Finally, the estimated travel time tiest for road segment i is given by
t
i
est
=t
i
avg
+Wσ
i
t. (4)
and point speed for segment i can be computed by
With respect to such time warping, several special cases may arise and be addressed in various manners. For example, when travel times for paired-points are much less than the historical average, the algorithm may estimate very large speeds for some segments (those for which σit is large). To limit this effect, equation (4) may be modified as follows:
where vref is the reference speed for the road in which the segment occurs (e.g., the 85th percentile of all speeds on the road), and α is a factor that controls some percentage of the reference speed. Typically α is set to 1.2, so that the estimated travel time for road segment i is never greater than that achievable by exceeding the reference speed by 20%. In addition, if the point speed is known, the weight W may be set to zero, and the speed for the segment replaced by the known speed. There may also be some portions of the road in which such fitting is applied and other portions in which such fitting is not used (or is used to a lesser degree). If so, particular road portions may be predefined to have fitting applied or not, or models may be defined to dynamically detect corresponding differences between road portions, so as to enable fitting to be applied differentially on these portions.
In the examples above, travel path data has been matched within a fixed time bin, such that the fitting occurs within a single time bin on the travel/road profile. In other embodiments and situations, however, the current speeds from recent traffic probe data may significantly differ from the representative average speeds or other typical speeds of the historical travel profile, and if so the fitting may take place in both the space (e.g., road location) and time dimensions. Conceptually, this is the same as finding a path across the road profile surface that has the smallest degree of adjustment applied to the travel path. One example of accomplishing this is the following: for each spatial segment, evaluate all time bins and select the one that requires the lowest degree of adjusting of the travel path, optionally applying a cost factor that is an increasing function of the time difference between the current time bin and the best fitting time bin, so as to tend to improve the continuity of the path across the surface. In other embodiments, fitting may take place in both the space and time dimensions in other situations, and/or fitting may occur with respect to the space dimension without changing the time dimension.
As described above, historical traffic data may be combined with recent traffic flow condition information from vehicles and other devices in various manners and in order to provide various benefits. A non-exclusive list of aspects of the described techniques that provide particular benefits includes the following: the use of historical data to estimate accurate travel times and speeds for data points between reported recent traffic probe data points; the computation of a historical travel/road profile in which the size of spatial and temporal divisions is a function of sample sizes; the creation of a travel path that includes all point pairs from a single vehicle; the splitting of a travel path when vehicle speeds drop below a threshold for a period of time exceeding a temporal threshold; performing fitting of an actual travel path to a travel profile for a road portion by computing accurate travel times for locations of the road portion as a function of the historical travel times at those locations and a total travel time that includes those locations; performing fitting of an actual travel path to a 3-D travel profile for a road portion in a manner that optimizes the path across the 3-D profile by finding the best matching time bin and/or road location; etc. It will be appreciated that other aspects may similarly provide various benefits.
With respect to
In this example, the historical travel profile information includes a line 220 on the graph that shows typical representative traffic flow conditions information for each of a plurality of locations along the road portion, such as may be average historical traffic flow for a given location for a time period based on historical information that is aggregated from a plurality of vehicles at a plurality of prior times. In addition, in this example, the information 200 further includes lines 215 and 210 that represent lower and upper estimates, respectively, of the historical representative traffic flow conditions information—as discussed in greater detail elsewhere, such lower and upper estimates may represent a range of possible or likely values for the historical representative traffic flow conditions information, such as to correspond to, for example, minimum and maximum historical values, one or more standard deviations from the typical values based on the historical information, etc. In addition, such ranges of historical representative traffic flow conditions information values for a given road location and time period may be represented in other manners in other embodiments (e.g., with error bars, as illustrated in
The example information 200 further includes a line 225 that corresponds to estimated traffic flow conditions information for an actual travel path of a vehicle along the road portion represented by the travel profile information, with the line 225 being estimated using the historical representative traffic flow conditions information values of the historical travel profile in combination with partial actual traffic flow information for the vehicle. For example, the line 225 includes indications of two actual data samples 230 that include actual traffic flow speed values of the vehicle at two indicated road locations (in this example, at locations that are approximately 1.7 and 2.5 miles from the starting point, and with actual traffic flow speeds of approximately 21 mph and 18 mph, respectively). If data sample 230a at the 1.7 mile distance location occurred at a first time T, and if the second data sample 230b at the 2.5 mile distance location occurred at a second time T+2.5 minutes, for example, an average speed for the 0.8 miles traveled during those 2.5 minutes is approximately 19 mph. In the absence of the historical travel profile information, traffic speeds 235 could be estimated in an unsophisticated manner by assuming a straight-line change between the actual traffic flow speeds from the data samples 230. However, doing so ignores the three flow obstructions that occur on the road between the locations of the actual data samples 230, with the corresponding variations in the historical representative traffic flow conditions information values.
Accordingly, rather than estimating traffic flow speeds in accordance with the straight-line 235, the described techniques in at least some embodiments determine expected traffic flow speed values 240 based on fitting the actual traffic flow values to the historical travel profile, such as automatically by an embodiment of the estimated traffic information provider system, and with those values 240 being included as part of the line 225 between the two data samples 230. In this example, both of the actual traffic flow speeds for the two actual data samples 230 are below the typical traffic flow speeds for that road location during the relevant time period, and the expected traffic flow speed values 240 have been generated based on the historical representative traffic flow conditions information values of the travel profile for the road locations between the two actual data samples 230, such that the line 225 has a shape that is similar to the line 220 in this example but that deviates from the line 220 to correspond to the actual traffic flow speeds from the data samples 230 (and other actual data samples for other road locations, not shown). Thus, line 225 between the actual data samples 230 may similarly correspond to traveling a distance of 0.8 miles in 2.5 minutes at a mean traffic speed of approximately 19 mph, but may have significant variations in speed during those 0.8 miles.
Accordingly, such expected traffic flow speed values 240 may provide significantly more accurate traffic speed estimates for particular road locations as contrasted with the values 235. For example, if another vehicle is planning on traveling on a route in the near future that includes a portion of the example Road X between the locations at distances 2.0 and 2.2 miles, planning information for such a route may significantly benefit by knowing that current expected values for actual traffic flow conditions for that 0.2 mile stretch of the road include an average speed of approximately 33 mph (as reflected by two of the values 240), rather than the overall average speed of 19 mph between the data samples 230, and in this case are generally consistent with the historical representative traffic flow conditions information values for that 0.2 mile stretch for the time period. Alternatively, if the vehicle that reported data samples 230 has only traveled to the 2.5 mile distance location or a short distance further (e.g., if the data sample 230b is received in a realtime or near-realtime manner), and if the estimated traffic flow conditions information 225 for locations beyond that 2.5 mile distance location are automatically determined by the estimated traffic information provider system in a realtime or near-realtime manner (e.g., within minutes or seconds), the estimated traffic flow conditions information 225 for those locations beyond that 2.5 mile distance location may be used to facilitate further travel of that vehicle on that road, such as update previous time estimates to arrive at particular locations, to suggest alternative routes if the estimated traffic flow conditions are significantly worse than normal, etc. For example, while the expected traffic flow speed values 240 are similar to the corresponding typical historical representative traffic flow conditions information values in this example, the current expected values for actual traffic flow conditions at one or more road locations may in other situations be determined to deviate significantly from typical historical representative traffic flow conditions information values for those road locations at a corresponding time period, such as to reflect current traffic that is unusual relative to historical averages, which may be similarly represented by determined expected traffic flow speed values for those road locations. It will be appreciated that determinations about estimated values for current actual travel flow conditions may further be beneficially made by combining information from multiple vehicles traveling on the road, such that actual traffic flow information from data samples from those vehicles and/or expected traffic flow values based on those data samples from those vehicles may be used.
With respect to the road Interstate 90 in the greater Seattle metro area, road link L1217 is a link 285 in this example that is part of Interstate 90 and has adjacent road links L1216 and L1218. In this example, road link 1217 is a bi-directional link that corresponds to both eastbound and westbound traffic, and thus is part of two road segments 290 and 295 that each correspond to one of the directions. In particular, example road segment S4860 corresponds to westbound traffic and includes the westbound traffic of link L1217 (as well as the westbound traffic of adjacent links L1216 and L1218), and example road segment S2830 corresponds to eastbound traffic and includes the eastbound traffic of link L1217 (as well as the eastbound traffic of nearby links L1218, L1219 and L1220). Road links and road segments may have various relationships in various embodiments, such as road link L1221 and road segment S4861 corresponding to the same portion of road, several road segments corresponding to multiple contiguous road links while road segment S4862 corresponds to non-contiguous road links L1227 and L1222. Thus, if historical representative traffic flow conditions information is being aggregated and determined for segment S4860, for example (e.g., as part of a historical travel profile for the portion of Interstate 90 that is illustrated in the map of
With respect to the example R203 arterial city street (e.g., the Island Crest
Way local road of the city of Mercer Island), it similarly is divided in this example into six contiguous road segments S201a-S201f, but does not have any illustrated road links (e.g., based on having road links that are not illustrated; based on not having any road links, such as being of a functional road classification for which map providers or others have not defined road links; etc.). In this example, the road R203 does not have any associated road sensors, and thus the historical representative traffic flow conditions information for the road R203 is gathered from data samples provided by vehicles (not shown) and/or users (not shown) who are traveling along the road R203. The historical representative traffic flow conditions information for the road R203 further have variability in this example amongst the six contiguous road segments S201a-S201f based on three structural traffic flow obstructions that are illustrated, as follows: the FO202a obstruction that is a traffic signal on segment S201b; the FO202b obstruction that is lane merging location on segment S201c where 4 traffic lanes north of the obstruction (2 lanes in each direction) merge to 3 traffic lanes south of the obstruction (1 lane is each direction and a center turn lane); and the FO202c obstruction that is a stop sign on segment S201e.
In addition,
In this example, however, actual traffic flow conditions are significantly better than historical typical representative traffic flow conditions for this time period (e.g., based on being a holiday, a school break, etc.), such as is reflected by actual data sample 230d having an actual traffic speed value that is well above the upper historical range for road segment S201e during this time period. Nonetheless, in some embodiments, the expected traffic flow condition values 240 may be generated based on the illustrated historical typical representative traffic flow conditions for this time period in a manner similar to that previously discussed, by fitting the actual traffic flow values for the vehicle to the illustrated historical representative traffic flow conditions values, despite two or more of the expected traffic flow condition values 240 being outside of the range of historical representative traffic flow conditions values for their corresponding road segment during this time period.
Alternatively, in some embodiments, the expected traffic flow condition values 240 may be generated based on using other historical representative traffic flow conditions information for the example road R203, such as by shifting the historical representative traffic flow conditions information to which the actual traffic flow values are fitted to another time period that better represents the actual traffic flow conditions on road R203 that produced the actual traffic flow values. For example,
It will be appreciated that the details of
In the illustrated embodiment, an Expected Traffic Information Provider system 150 is executing in memory 145, as is an optional Route Selector system 160 and optional other systems provided by programs 162 (e.g., a predictive traffic forecasting program based at least in part on historical traffic data, a realtime traffic information provider system to provide traffic information to clients in a realtime or near-realtime manner, etc.), with these various executing systems generally referred to herein as traffic analysis systems, and with the system 150 including various software instructions in some embodiments that when executed program the CPU 135 to provide the described functionality. The server computing system and its executing traffic analysis systems may communicate with other computing systems, such as various client devices 182, vehicle-based clients and/or data sources 184, road traffic sensors 186, other data sources 188, and third-party computing systems 190, via network 180 (e.g., the Internet, one or more cellular telephone networks, etc.) and wireless communication link 185.
The client devices 182 may take various forms in various embodiments, and may generally include any communication devices and other computing devices capable of making requests to and/or receiving information from the traffic analysis systems. In some cases, the client devices 182 may include mobile devices that travel on particular roads (e.g., handheld cell phones or other mobile devices with GPS capabilities or other location determination capabilities that are carried by users traveling in vehicles, such as operators and/or passengers of the vehicles), and if so, such client devices may act as mobile data sources that provide current traffic data based on current travel on the roads (e.g., if the users of the client devices are on the roads). In addition, in some situations the client devices may run interactive console applications (e.g., Web browsers) that users may utilize to make requests for generated expected traffic-related information based on historical traffic information, while in other cases at least some such generated expected traffic-related information may be automatically sent to the client devices (e.g., as text messages, new Web pages, specialized program data updates, etc.) from one or more of the traffic analysis systems.
The vehicle-based clients/data sources 184 in this example may each include a computing system located within a vehicle that provides data to one or more of the traffic analysis systems and/or that receives data from one or more of those systems. In some embodiments, the historical information used by the Expected Traffic Information Provider system may originate at least in part from a distributed network of vehicle-based data sources that provide information related to current traffic conditions. For example, each vehicle may include a GPS (“Global Positioning System”) device (e.g., a cellular telephone with GPS capabilities, a stand-alone GPS device, etc.) and/or other geo-location device capable of determining the geographic location, speed, direction, and/or other data related to the vehicle's travel. One or more devices on or in the vehicle (whether the geo-location device(s) or a distinct communication device) may occasionally gather such data and provide it to one or more of the traffic analysis systems (e.g., by way of a wireless link). For example, a system provided by one of the other programs 162 may obtain and use current road traffic conditions information in various ways), and such information (whether as originally obtained or after being processed) may later be used by the Expected Traffic Information Provider system as historical data. Such vehicles may include a distributed network of individual users, fleets of vehicles (e.g., for delivery companies, transportation companies, governmental bodies or agencies, vehicles of a vehicle rental service, etc.), vehicles that belong to commercial networks providing related information (e.g., the OnStar service), a group of vehicles operated in order to obtain such traffic conditions information (e.g., by traveling over predefined routes, or by traveling over roads as dynamically directed, such as to obtain information about roads of interest), etc. In addition, such vehicle-based information may be generated in other manners in other embodiments, such as by cellular telephone networks, other wireless networks (e.g., a network of Wi-Fi hotspots) and/or other external systems (e.g., detectors of vehicle transponders using RFID or other communication techniques, camera systems that can observe and identify license plates and/or users' faces) that can detect and track information about vehicles passing by each of multiple transmitters/receivers in the network.
The road traffic sensors 186 include multiple sensors that are installed in, at, or near various streets, highways, or other roadways, such as for one or more geographic areas. These sensors include loop sensors that are capable of measuring the number of vehicles passing above the sensor per unit time, vehicle speed, and/or other data related to traffic conditions. In addition, such sensors may include cameras, motion sensors, radar ranging devices, and other types of sensors that are located adjacent to a roadway. The road traffic sensors 186 may periodically or continuously provide measured data via wire-based or wireless-based data link to one or more of the traffic analysis systems via the network 180 using one or more data exchange mechanisms (e.g., push, pull, polling, request-response, peer-to-peer, etc.). For example, a system provided by one of the other programs 162 may obtain and use current road traffic conditions information in various ways, and that such information (whether as originally obtained or after being processed) may later be used as historical information by the Expected Traffic Information Provider system. In addition, while not illustrated here, in some embodiments one or more aggregators of such road traffic sensor information (e.g., a governmental transportation body that operates the sensors, a private company that generates and/or aggregates data, etc.) may instead obtain the traffic data and make that data available to one or more of the traffic analysis systems (whether in raw form or after it is processed). In some embodiments, the traffic data may further be made available in bulk to the traffic analysis systems.
The other data sources 188 include a variety of types of other sources of data that may be utilized by one or more of the traffic analysis systems to generate expected traffic conditions information. Such data sources include, but are not limited to, holiday and season schedules or other information used to determine how to group and categorize historical data for specific days and times, schedule information for non-periodic events, schedule information related to traffic sessions, schedule information for planned road construction and other road work, etc.
Third-party computing systems 190 include one or more optional computing systems that are operated by parties other than the operator(s) of the traffic analysis systems, such as parties who provide current and/or historical traffic data to the traffic analysis systems, and parties who receive and make use of traffic-related data provided by one or more of the traffic analysis systems. For example, the third-party computing systems may be map vendor systems that provide data (e.g., in bulk) to the traffic analysis systems. In some embodiments, data from third-party computing systems may be weighted differently than data from other sources. Such weighting may indicate, for example, how many measurements participated in each data point. Other third-party computing systems may receive generated expected traffic-related information from one or more of the traffic analysis systems and then provide related information (whether the received information or other information based on the received information) to users or others (e.g., via Web portals or subscription services). Alternatively, the third-party computing systems 190 may be operated by other types of parties, such as media organizations that gather and report such traffic-related information to their consumers, or online map companies that provide such traffic-related information to their users as part of travel-planning services.
In the illustrated embodiment of
The Expected Traffic Information Provider system obtains historical traffic data from one or more of various sources, and stores the historical data in a database 142 on storage 140 in this example. As previously discussed, the historical data may include data in a raw form as originally previously received from one or more external sources, or may instead be obtained and stored in a processed form. For example, for each of one or more traffic conditions measures of interest, the historical data may include values for that measure for some or all road segments and/or road links for each of a variety of prior time periods. They historical traffic data may have originally been generated by one or more external sources, such as vehicle-based data sources 184, road traffic sensors 186, other data sources 188, and/or third-party computing systems 190, and in some embodiments may alternatively be stored by one or more such sources and currently provided to the Expected Traffic Information Provider system from such storage. In some embodiments, the system 150 or other system may further detect and/or correct various errors in the historical data (e.g., due to sensor outages and/or malfunctions, network outages, data provider outages, etc.), such as if the obtained data is raw historical data that was not previously processed. For example, data may be filtered and/or weighted in various ways to remove or deemphasize data from consideration if it is inaccurate or otherwise unrepresentative of historical traffic conditions of interest, including by identifying data samples that are not of interest based at least in part on roads with which the data samples are associated and/or data samples that are statistical outliers with respect to other data samples. In some embodiments, the filtering may further include associating the data samples with particular roads, road segments, and/or road links. The data filtering may further exclude data samples that otherwise reflect vehicle locations or activities that are not of interest (e.g., parked vehicles, vehicles circling in a parking lot or structure, etc.) and/or data samples that are otherwise unrepresentative of vehicle travel on roads of interest. In some embodiments, the system 150 or other system may also optionally aggregate obtained data from a variety of data sources, and may further perform one or more of a variety of activities to prepare data for use, such as to place the data in a uniform format; to discretize continuous data, such as to map real-valued numbers to enumerated possible values; to sub-sample discrete data; to group related data (e.g., a sequence of multiple traffic sensors located along a single segment of road that are aggregated in an indicated manner); etc.
After obtaining and optionally processing the historical traffic data, a Historical Data Manager module 152 of the Expected Traffic Information Provider system then analyzes the historical data for use in generating expected traffic conditions information for one or more of various measures, such as for use in one or more travel/road profiles being generated. The module 152 or other module may, for example, analyze the historical traffic data to generate average traffic flow conditions information for one or more measures of traffic conditions. The measures may include, for example, average vehicle speed; volume of traffic for an indicated period of time; average occupancy time of one or more traffic sensors, etc. The generated average traffic conditions information may then be stored for later use, such as in the database 142. The module 152 may further perform other activities to enable the generation of expected traffic conditions information, such as by using the historical traffic information to generate one or more travel/road profile grids or other travel/road profiles. Such generated travel/road profile information may also be stored for later use as part of the historical data in database 142, or instead in other manners in other embodiments.
The Expected Traffic Information Provider system 150 may also obtain recent traffic probe data or other recent traffic information in various manners, such as under control of a Current Data Manager module 154 of the system 150. The module 154 may, for example, initiate interactions 195 with particular vehicle-based data sources 184 and/or mobile client devices 182 to gather such information, or such data sources 184 and client devices 182 may instead forward such information to the module 154 (e.g., periodically). As previously noted, such communications may include wireless links 185 in some embodiments and situations. Such recent traffic information may, for example, be stored in the database 143 on storage 140, or instead in other manners in other embodiments. The module 154 may further perform other activities to enable the use of current or recent traffic conditions information, such as by combining multiple probe data samples or other pieces of traffic flow conditions information for a particular vehicle for use in representing at least some of an actual travel path of the vehicle. Such information about actual travel paths of one or more vehicles may also be stored for later use as part of the current data in database 143, or instead in other manners in other embodiments.
After the historical traffic information and recent traffic information is available, the Current Traffic Condition Estimator module 156 of the system 150 may combine and analyze that information in various ways, such as to fit actual travel paths of particular vehicles/devices to portions of particular corresponding travel/road profiles, and to generate expected traffic conditions information for portions of the actual travel paths based on the fitting. The generated expected traffic conditions information for the one or more actual travel paths may then be stored in the database 144 on storage 140, for example, or instead stored in other manners in other embodiments. The generated expected traffic conditions information for the actual travel path of one or more vehicles on a road portion may also be used in various ways, such as to adjust historical representative traffic flow condition information from a generated travel/road profile for the road portion to reflect current or recent changes in the actual traffic flow based at least in part on the generated expected traffic conditions information (e.g., for use in providing the adjusted traffic flow information to facilitate future travel of vehicles over the road portion), and/or in other manners, such as to be provided to the optional Route Selector system, client devices 182, vehicle-based clients 184, third-party computing systems, and/or other users in at least some embodiments. Such generated expected traffic conditions information may also be stored for later use in database 144, or instead in other manners in other embodiments.
In addition, after expected traffic flow conditions information has been generated for one or more traffic conditions measures for the actual travel path of one or more vehicles on a road portion, and optionally used in one or more manners (e.g., to adjust historical representative traffic flow condition information from a generated travel/road profile for the road portion to reflect current or recent changes in the actual traffic flow based at least in part on the generated expected traffic conditions information), the Information Supplier module 158 of the system 150 may provide corresponding information to various clients, such as based on current or previously supplied requests. For example, the Route Selector system 160 may optionally determine travel route information for one or more vehicles based at least in part on the expected traffic flow conditions information, such as based on projected average speed or other traffic conditions projected to currently occur based on that expected traffic conditions information, and may provide such route information to others in various ways. In addition, in some embodiments, the generated expected traffic conditions information may be used as one type of input to a system that predicts and/or forecasts future traffic conditions information based on current conditions, such as by using the expected traffic conditions information to project current conditions (e.g., if the current condition information is not available at the time of prediction, or by using the expected traffic conditions information at an earlier time to perform the prediction or forecast in advance).
It will be appreciated that the illustrated computing systems are merely illustrative and are not intended to limit the scope of the present invention. For example, computing system 100 may be connected to other devices that are not illustrated, including through one or more networks such as the Internet or via the Web. More generally, a “client” or “server” computing system or device, or traffic analysis system and/or module, may comprise any combination of hardware or software that can interact and perform the described types of functionality, including without limitation desktop or other computers, database servers, network storage devices and other network devices, PDAs, cellphones, wireless phones, pagers, electronic organizers, Internet appliances, television-based systems (e.g., using set-top boxes and/or personal/digital video recorders), and various other consumer products that include appropriate inter-communication capabilities. In addition, the functionality provided by the illustrated system modules may in some embodiments be combined in fewer modules or distributed in additional modules. Similarly, in some embodiments the functionality of some of the illustrated modules may not be provided and/or other additional functionality may be available. Furthermore, while the Expected Traffic Information Provider system 150 and its exemplary modules 152-158 are illustrated in this example as being part of one or more programmed computing systems that are remote from the various exemplary vehicles 184, in other embodiments some or all of the Expected Traffic Information Provider system 150 (e.g., one or more of the modules 152-158) may instead execute as part of one or more computing devices that are part of or otherwise traveling with one or more of the vehicles 184, and may optionally communicate some or all generated, calculated or determined information to other remote parts of the system 150 (e.g., other of the modules 152-158).
It will also be appreciated that, while various items are illustrated as being stored in memory or on storage while being used, these items or portions of them may be transferred between memory and other storage devices for purposes of memory management and/or data integrity. Alternatively, in other embodiments some or all of the software modules and/or systems may execute in memory on another device and communicate with the illustrated computing system/device via inter-computer communication. Furthermore, in some embodiments, some or all of the modules may be implemented or provided in other manners, such as at least partially in firmware and/or hardware, including, but not limited to, one or more application-specific integrated circuits (ASICs), standard integrated circuits, controllers (e.g., by executing appropriate instructions, and including microcontrollers and/or embedded controllers), field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), etc. Some or all of the system modules or data structures may also be stored (e.g., as software instructions or structured data) on a non-transitory computer-readable storage medium, such as a hard disk, a memory, a network, or a portable media article to be read by an appropriate drive or via an appropriate connection. The system modules and data structures may also be transmitted as generated data signals (e.g., as part of a carrier wave or other analog or digital propagated signal) on a variety of computer-readable transmission mediums, including wireless-based and wired/cable-based mediums, and can take a variety of forms (e.g., as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). Such computer program products may also take other forms in other embodiments. Accordingly, the present invention may be practiced with other computer system configurations.
The illustrated embodiment of the routine 300 begins at block 305, where information or another indication is received. The routine continues to block 310 to determine whether information is received in block 305 that may be used as historical traffic flow conditions information for one or more roads. If so, the routine continues to block 315 to execute a Historical Data Manager routine to analyze the historical traffic flow conditions information, such as to optionally generate or update one or more historical travel profiles for one or more road portions, with one example embodiment of such a routine being further described with respect to
If it is instead determined in block 310 that the information received in block 305 is not historical traffic flow information, the routine continues to block 320 to determine whether information is received in block 305 that reflects recent or otherwise current traffic flow information for one or more roads. If so, the routine continues to block 325 to execute a Current Data Manager routine to analyze the current traffic flow information, such as to construct representations of travel paths of one or more vehicles using partial actual traffic flow information for the vehicles (e.g., using multiple periodic data samples reported by devices associated with the vehicles), with one example embodiment of such a routine being further described with respect to
After block 330, the routine continues to block 335 to optionally receive and use expected traffic flow conditions information from block 330, such as to perform one or more of the following: updating typical historical traffic flow conditions information for one or more road portions to reflect current traffic flow conditions information that are different from the typical historical traffic flow conditions information; providing information to various vehicles or users that will be traveling on the one or more road portions in the future to indicate the updated typical traffic flow conditions information or other otherwise indicate particular expected traffic flow conditions information received from block 330; providing information to vehicles or users that are currently traveling on the one or more road portions (e.g., vehicles or users from whom the current traffic flow conditions information is received or to whom the current traffic flow conditions information otherwise corresponds) to facilitate further travel by those vehicles/users on part of those road portions; etc. In addition, in the illustrated embodiment, such expected traffic flow conditions information may further be used in other manners, such as to be provided to requesters with respect to block 355 or otherwise be used in block 390.
If it is instead determined in block 320 that the information received in block 305 is not current traffic flow information, the routine continues to block 350 to determine whether a request is received in block 305 for one or more types of traffic flow conditions information, such as from particular vehicles and/or users, from one or more other traffic analysis systems that use information from the estimated traffic information provider system to provide additional functionality to clients, etc. If so, the routine continues to block 355 to retrieve and provide the requested information to the requester as appropriate, such as after optionally determining that the requester is authorized to receive the information (e.g., is an authorized partner or affiliate, has paid corresponding fees to enable access to the requested information, etc.). The types of information that may be requested and provided may have various forms in various embodiments, including any data that is used by and/or produced by any of the blocks 315, 325, 330 and 335. In addition, in some embodiments the functionality of block 355 may be provided as part of an information supplier module of the estimated traffic information provider system, as discussed in greater detail with respect to module 158 of system 150 of
If it is instead determined in block 350 that a request was not received in block 305 for desired traffic flow information, the routine continues to block 390 to perform one or more other operations as appropriate. Such other operations may have various forms in various embodiments, including receiving and storing information for later use (e.g., information about particular roads, about particular traffic flow obstructions, etc.), performing account-related activities for users or other systems that have accounts with the estimated traffic information provider system or that are otherwise affiliated with the estimated traffic information provider system (e.g., registering new users/affiliates, obtaining payment-related information from users/affiliates for fee-based functionality of the estimated traffic information provider system, initiating payment collection activities or other activities related to obtain payment from users/affiliates for past and/or planned future activities that have associated fees, etc.), performing occasional housekeeping operations, etc.
After steps 315, 335, 355 or 390, the routine continues to step 395 to determine whether to continue, such as until an explicit instruction to terminate is received. If so, the routine returns to step 305, and if not continues to step 399 and ends.
The illustrated embodiment of the routine 400 begins at block 405, where information is received that may be used as historical traffic flow conditions information for one or more roads. Such historical traffic flow conditions information may have various forms in various embodiments and situations, as discussed in greater detail elsewhere, including data readings from fixed-location road sensors associated with the one or more roads and/or data samples from devices associated with vehicles and/or users that are traveling on the one or more roads. The routine then continues to block 410 to determine the one or more road portions with which the information is associated (e.g., based on GPS-based locations or other location information that is associated with particular pieces of the historical traffic flow conditions information), and in block 415 stores the received historical information in a manner that is associated with the corresponding determined road portions.
In block 420, the routine then determines whether to generate one or more travel profiles at the current time, such as for at least one of the determined road portions based on the information received in block 405 (e.g., in response to having sufficient data to do such generation for the determined road portions, in response to a corresponding instruction received in block 405 with the historical information, on a periodic basis, etc.). If so, the routine continues to block 425 to retrieve the stored or otherwise available historical traffic flow conditions information for the determined road portion(s), and in block 430 determines aggregation classifications to use for each such determined road portion. As discussed in greater detail elsewhere, the aggregation classifications may in some embodiments be based at least in part on distinct locations on a determined road portion and/or distinct time periods, such as with each aggregation classification having a distinct combination of one or more road locations and at least one time period. Particular road locations and/or time periods to use may be determined and/or modified in at least some embodiments, as discussed in greater detail elsewhere, including in some embodiments based on availability or lack of availability of particular historical information, such as to merge two or more predefined road location groups (e.g., road links) and/or merge two or more predefined time periods, or to separate a single predefined road location group into multiple such groups and/or separate a single predefined time period into multiple such time periods.
After block 430, the routine continues to block 435 to, for each aggregation classification of each road portion being analyzed, aggregate historical traffic flow conditions information that corresponds to that aggregation classification, and determine representative traffic flow conditions information that is typical for that aggregation classification (e.g., for the time period of the aggregation classification at those one or more road locations of the determined road portion). For example, in some embodiments, an average traffic speed may be determined for each aggregation classification, optionally with various error estimates or other variability indications, as discussed in greater detail elsewhere. In block 440, the routine then combines the information from the various aggregation classifications for each of the determined road portion(s) to generate a historical travel profile for that road portion, and stores the generated travel profile for later use.
If it is instead determined in block 420 to not generate one or more travel profiles at the current time, the routine continues to block 490 to optionally perform one or more other indicated operations as appropriate. Such other operations may have various forms in various embodiments, including receiving and storing information for later use (e.g., information about particular roads, about particular time periods and/or road location groups, etc.), updating previously generated travel profiles (e.g., based on new historical traffic flow conditions information received in block 405), etc. After steps 440 or 490, the routine continues to step 495 and returns.
The illustrated embodiment of the routine 500 begins at block 505, where current traffic flow conditions information is received for one or more roads and one or more vehicles. Such current traffic flow conditions information may have various forms in various embodiments and situations, as discussed in greater detail elsewhere, including data samples from devices associated with the vehicles and/or users in the vehicles that are traveling on the one or more roads. The routine then continues to block 510 to, for each of one or more of the vehicles, identify data samples or other pieces of information in the current traffic flow conditions information that are associated with the vehicle, such as to provide partial actual traffic flow conditions information for the vehicle at one or more indicated times and at one or more indicated road locations. In block 515, the routine then uses the identified information pieces for each of the vehicles to construct a representation of a portion of an actual travel path of the vehicle alone or more road portions on which the vehicle recently traveled or is currently traveling, such as by ordering the information pieces by associated time and/or in other manners, and optionally performing additional processing on some or all of the information pieces (e.g., identifying any occurrences of vehicle speed below a defined speed threshold for at least a defined time threshold).
After block 515, the routine continues to block 520 to optionally store the current traffic flow conditions information received in block 505 for later use, such as use as historical traffic flow conditions information at a later time. In block 525, the routine then stores information about the travel profile representations constructed in block 515, and optionally provides indications of one or more of those constructed travel profile representations. The routine then continues to block 599 and returns. While not illustrated here, the routine may further optionally perform other indicated operations as appropriate in some embodiments and at some times, such as to receive and store information for later use (e.g., information about particular roads, about particular speed thresholds and/or time thresholds for use in constructing travel profile representations, etc.), updating previously constructed travel profile representations (e.g., based on new corresponding current traffic flow conditions information received in block 505), etc.
The illustrated embodiment of the routine 600 begins at block 605, where information is received that includes one or more constructed travel path representations for one or more vehicles to reflect actual travel paths of the vehicle(s) on one or more roads, which in this case are received from the output of block 325. Such constructed travel path representations include actual traffic flow conditions information for part of the corresponding actual travel paths, as discussed in greater detail elsewhere. The routine then continues to block 610 to, for each constructed travel path representation, retrieve at least one generated historical travel profile for a road portion to which the constructed travel path representation corresponds, such as may be previously generated with respect to block 315 of
After block 610, the routine continues to block 615 to, for each constructed travel path representation, perform activities to fit the constructed travel path representation to the corresponding retrieved historical travel profile(s), such as by matching actual traffic flow conditions information from the constructed travel path representation to corresponding representative traffic flow conditions information for corresponding aggregation classifications of the constructed travel path representation, and by determining expected traffic flow conditions information for other parts of the constructed travel path representation for which actual traffic flow conditions information is not available, in light of the differing representative traffic flow conditions information for corresponding aggregation classifications of the constructed travel path representation. Additional details are provided elsewhere related to such determining of expected traffic flow conditions information corresponding to an actual travel path of a vehicle, such as based on the fitting of such actual travel path information to a generated historical travel profile.
In block 620, the routine then stores information about the determined expected traffic flow conditions information for the constructed travel path representation(s), and optionally more generally stores information corresponding to the fitting of such actual travel path information from the constructed travel path representation(s) to the historical travel profile(s). The routine further optionally provides indications of at least some of the expected traffic flow conditions information for the constructed travel path representation(s), and then continues to block 599 and returns. While not illustrated here, the routine may further optionally perform other indicated operations as appropriate in some embodiments and at some times, such as to receive and store information for later use (e.g., information about particular information for use in fitting activities), updating information from previous fittings (e.g., based on new information received in block 605), etc.
Additional details related to filtering, conditioning, and aggregating information about road conditions and to generating expected traffic information that is predicted, forecast and expected are available in pending U.S. patent application Ser. No. 11/473,861 (Attorney Docket #480234.402), filed Jun. 22, 2006 and entitled “Obtaining Road Traffic Condition Data From Mobile Data Sources;” in pending U.S. application Ser. No. 11/367,463, filed Mar. 3, 2006 and entitled “Dynamic Time Series Prediction of Future Traffic Conditions;” and in pending U.S. application Ser. No. 11/835,357, filed Aug. 7, 2007 and entitled “Representative Road Traffic Flow Information Based On Historical Data;” each of which is hereby incorporated by reference in its entirety.
It will also be appreciated that in some embodiments the functionality provided by the routines discussed above may be provided in alternative ways, such as being split among more routines or consolidated into fewer routines. Similarly, in some embodiments illustrated routines may provide more or less functionality than is described, such as when other illustrated routines instead lack or include such functionality respectively, or when the amount of functionality that is provided is altered. In addition, while various operations may be illustrated as being performed in a particular manner (e.g., in serial or in parallel) and/or in a particular order, those skilled in the art will appreciate that in other embodiments the operations may be performed in other orders and in other manners. Those skilled in the art will also appreciate that the data structures discussed above may be structured in different manners, such as by having a single data structure split into multiple data structures or by having multiple data structures consolidated into a single data structure. Similarly, in some embodiments illustrated data structures may store more or less information than is described, such as when other illustrated data structures instead lack or include such information respectively, or when the amount or types of information that is stored is altered.
From the foregoing it will be appreciated that, although specific embodiments have been described herein for purposes of illustration, various modifications may be made without deviating from the spirit and scope of the invention. Accordingly, the invention is not limited except as by the appended claims and the elements recited therein. In addition, while certain aspects of the invention may be presented in certain claim forms, the inventors contemplate the various aspects of the invention in any available claim form. For example, while only some aspects of the invention may be recited as being embodied in a computer-readable medium at particular times, other aspects may likewise be so embodied.
This application claims the benefit of U.S. Provisional Patent Application No. 61/171,574, filed Apr. 22, 2009 and entitled “Predicting Expected Road Traffic Conditions Based On Historical And Current Data,” which is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 61171574 | Apr 2009 | US |
