EP1938296B1 - Évaluation des conditions de circulation routière au moyen de données provenant de sources de données mobiles - Google Patents

Évaluation des conditions de circulation routière au moyen de données provenant de sources de données mobiles Download PDF

Info

Publication number
EP1938296B1
EP1938296B1 EP07752080A EP07752080A EP1938296B1 EP 1938296 B1 EP1938296 B1 EP 1938296B1 EP 07752080 A EP07752080 A EP 07752080A EP 07752080 A EP07752080 A EP 07752080A EP 1938296 B1 EP1938296 B1 EP 1938296B1
Authority
EP
European Patent Office
Prior art keywords
data samples
data
road
traffic
road segment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP07752080A
Other languages
German (de)
English (en)
Other versions
EP1938296A2 (fr
Inventor
Craig H. Chapman
Alec Barker
Mitchel A. Burns, Jr.
Robert C. Cahn
Oliver B. Downs
Jesse S. Hersch
Scott R. Love
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Inrix Inc
Original Assignee
Inrix Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US11/431,980 external-priority patent/US20070208493A1/en
Priority claimed from US11/432,603 external-priority patent/US20070208501A1/en
Priority claimed from US11/438,822 external-priority patent/US7831380B2/en
Priority claimed from US11/444,998 external-priority patent/US8014936B2/en
Priority claimed from US11/473,861 external-priority patent/US7912627B2/en
Priority claimed from US11/540,342 external-priority patent/US7706965B2/en
Priority to EP10013472A priority Critical patent/EP2278573B1/fr
Application filed by Inrix Inc filed Critical Inrix Inc
Publication of EP1938296A2 publication Critical patent/EP1938296A2/fr
Publication of EP1938296B1 publication Critical patent/EP1938296B1/fr
Application granted granted Critical
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions

Definitions

  • the following disclosure relates generally to techniques for assessing road traffic conditions based on data obtained from various data sources, such as by inferring traffic-related information for roads of interest based on data samples that reflect actual travel on those roads.
  • One source for obtaining information about current traffic conditions includes observations supplied by humans (e.g ., traffic helicopters that provide general information about traffic flow and accidents, reports from 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). While human-supplied observations 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.
  • Traffic sensor networks can provide more detailed information about traffic conditions on some roads in some situations.
  • various problems exist with respect to such information, as well as to information provided by other similar sources.
  • 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, which greatly diminishes the value of the data provided by the traffic sensors.
  • One cause of inaccurate and/or unreliable data includes traffic sensors that are broken, and therefore provide no data, intermittent data, or data readings that are incorrect.
  • Another cause of inaccurate and/or unreliable data includes temporary transmission problem in data from one or more sensors, resulting in intermittent delivery, delayed delivery, or no delivery of data.
  • many traffic sensors are not configured or designed to report information about their operational status (e.g ., whether they are functioning normally or not), and even if operational status information is reported it may be incorrect ( e.g . reporting that they are functioning normally when in fact they are not), thus making it difficult or impossible to determine if data provided by the traffic sensors is accurate.
  • some traffic-related information may be available only in raw and/or disaggregated form, and therefore may be of limited utility.
  • US2004034467 A1 discloses a system and method for maintaining a road network traffic status database comprised of map segments with the network where vehicles' locations and speeds with the network are wireless received and used to update an average speed of the map segments and where an optimal route between a first and second location is determined from the database.
  • W098/5468 discloses a system that generates map database information from the movement of vehicles by passively geolocating and tracking at least one vehicle carrying a mobile transmitter.
  • the generated information may be stored in a database of location-sensitive data for other purposes.
  • Custom travel-related information is provided to a vehicle by passively geolocating the vehicle's mobile transmitter selecting relevant travel-related information from a database of location-sensitive data, and sending the selected information to the vehicle's mobile receiver.
  • Techniques are described for assessing road traffic conditions in various ways based on obtained traffic-related data, such as data samples from vehicles and other mobile data sources traveling on the roads and/or from road traffic sensors (e.g ., physical sensors that are embedded in or otherwise near to the roads).
  • data samples from the mobile data sources may be supplemented with data from one or more other sources, such as by obtaining data readings from physical sensors that are near or embedded in the roads.
  • the assessment of road traffic conditions based on obtained data samples may include various filtering and/or conditioning of the data samples and readings, and various inferences and probabilistic determinations of traffic-related characteristics of interest.
  • obtained road traffic condition information data may include multiple data samples provided by mobile data sources (e.g ., vehicles), data readings from road-based traffic sensors (e.g ., loop sensors embedded in road pavement), and data from other data sources.
  • the data may be analyzed in various manners to facilitate determination of traffic condition characteristics of interest, such as estimated average traffic speed and estimated total volume of vehicles for particular portions of roads of interest, and to enable such traffic condition determinations to be performed in a realtime or near-realtime manner (e.g ., within a few minutes of receiving the underling data samples and/or readings).
  • obtained data may be conditioned in various ways in order to detect and/or correct errors in the data.
  • Obtained road traffic condition information data may further be filtered in various ways in various embodiments in order to remove data from consideration if it is inaccurate or otherwise unrepresentative of actual traffic condition characteristics 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 performing the associating of the data samples with particular roads.
  • the filtered data samples may further include 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 actual vehicle travel on roads of interest.
  • Assessing obtained data may in at least some embodiments include determining traffic conditions (e.g ., traffic flow and/or average traffic speed) for various portions of a road network in a particular geographic area, based at least in part on obtained data samples. The assessed data may then be utilized in order to perform other functions related to analyzing, predicting, forecasting, and/or providing traffic-related information.
  • a data sample manager system uses at least some of the described techniques to prepare data for use by traffic data clients, such as a predictive traffic information provider system that generates multiple predictions of traffic conditions at multiple future times, as described in greater detail below.
  • the conditioning of obtained data samples may include rectifying erroneous data samples, such as by detecting and/or correcting errors present in the data in various ways (e.g ., for data readings received from road traffic sensors).
  • rectifying erroneous data samples such as by detecting and/or correcting errors present in the data in various ways (e.g ., for data readings received from road traffic sensors).
  • techniques are described for assessing the "health" of particular data sources (e.g ., road-based traffic sensors) in order to determine whether the data sources are operating correctly and reliably providing accurate data samples, such as based on analysis of the data samples provided by those data sources.
  • current data readings provided by a given traffic sensor may be compared to past data readings provided by that traffic sensor (e.g ., historical average data) in order to determine whether the current traffic data readings are significantly different than typical past data readings, such as may be caused by the traffic sensor operating incorrectly and/or other problems in the data, and/or may instead reflect unusual current traffic conditions.
  • detection and analysis of possible errors with particular data sources and/or in current traffic data readings may be performed in various ways in various embodiments, as discussed in greater detail below, including based at least in part on classification techniques such as by using neural networks, Bayesian classifiers, decision trees, etc.
  • missing and unreliable data samples for one or more data sources may be rectified in some embodiments by using one or more other sources of related information, such as via contemporaneous data samples from nearby or otherwise related traffic sensors that are operating correctly ( e.g ., by averaging data readings provided by adjacent traffic sensors), via predictive information related to the missing and unreliable data samples ( e.g ., by determining expected data readings for the one or more data sources using predicted and/or forecast traffic condition information for those data sources), via historical information for the one or more data sources ( e.g ., by utilizing historical average data readings), via adjustments to incorrect data samples using information about consistent bias or other types of errors causing errors that can be compensated for, etc. Additional details related to rectifying missing and unreliable data samples are included below.
  • traffic condition information in various other ways, such as in cases where currently available data may not allow rectification of data samples for a particular data source (e.g ., a particular traffic sensor) to be reliably performed. For example, the presence of multiple nearby unhealthy traffic sensors that are operating incorrectly may result in there being insufficient data to assess traffic flow information with sufficient confidence for individual ones of those traffic sensors.
  • traffic condition information may be estimated in various other ways, including based on groups of related traffic sensors and/or other information related to the structure of a road network.
  • each road of interest may be modeled or represented by the use of multiple road segments, each of which may have multiple associated traffic sensors and/or available data from one or more other data sources (e.g ., mobile data sources).
  • road traffic condition information may be estimated for a particular road segment (or other group of multiple related traffic sensors) in various ways, such as by using traffic condition information assessed for neighboring road segments, predicted information for the particular road segment (e.g ., that is generated for a limited future time period, such as three hours, based at least in part on current and recent conditions at a time of the predicting), forecast information for the particular road segment ( e.g ., that is generated for a longer future time period, such as two weeks or longer, in a manner that does not use some or all of the current and recent condition information used for predicting), historical average conditions for the particular road segment, etc.
  • traffic condition information may be provided even in the presence of little or no current traffic condition data for one or more nearby traffic sensors or
  • the mobile data sources include vehicles on the road, which may each include one or more computing systems that provide data about movement of the vehicle.
  • each vehicle may include a GPS ("Global Positioning System") device and/or other geo-location device capable of determining the geographic location, speed, direction, and/or other data that characterizes or is otherwise related to the vehicle's travel, and one or more devices on the vehicle (whether the geo-location device(s) or a distinct communication device) may from time to time provide such data (e.g ., by way of a wireless link) to one or more systems able to use the data (e.g ., a data sample manager system, as described in more detail below).
  • GPS Global Positioning System
  • Such vehicles may include, for example, a distributed network of vehicles operated by individual unrelated users, fleets of vehicles (e.g ., for delivery companies, taxi and bus 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 condition 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), vehicles with on-board cellphone devices (e.g ., as built-in equipment and/or in the possession of a vehicle occupant) capable of providing location information (e.g ., based on GPS capabilities of the devices and/or based on geo-location capabilities provided by the cellular network), etc.
  • a distributed network of vehicles operated by individual unrelated users e.g ., for delivery companies, taxi and bus companies, transportation companies, governmental bodies or agencies, vehicles of a vehicle rental service, etc.
  • the mobile data sources may include or be based on computing devices and other mobile devices of users who are traveling on the roads, such as users who are operators and/or passengers of vehicles on the roads.
  • Such user devices may include devices with GPS capabilities (e.g ., cellphones and other handheld devices), or location and/or movement information may instead be produced in other manners in other embodiments.
  • devices in vehicles and/or user devices may communicate with external systems that can detect and track information about devices (e.g ., for devices passing by each of multiple transmitters/receivers in a network operated by the system), thus allowing location and/or movement information for the devices to be determined in various manners and with various levels of detail, or such external systems may otherwise be able to detect and track information about vehicles and/or users without interacting with devices (e.g ., camera systems that can observe and identify license plates and/or users' faces).
  • external systems e.g ., for devices passing by each of multiple transmitters/receivers in a network operated by the system
  • Such external systems may include, for example, cellular telephone towers and networks, other wireless networks (e.g ., a network of Wi-Fi hotspots), detectors of vehicle transponders using various communication techniques (e.g ., RFID, or "Radio Frequency Identification”), other detectors of vehicles and/or users (e.g ., using infrared, sonar, radar or laser ranging devices to determine location and/or speed of vehicles), etc.
  • RFID Radio Frequency Identification
  • the road traffic condition information obtained from the mobile data sources may be used in various ways, whether alone or in combination with other road traffic condition information from one or more other sources (e.g ., from road traffic sensors).
  • road traffic condition information obtained from mobile data sources is used to provide information similar to that from road sensors but for roads that do not have functioning road sensors (e.g ., for roads that lack sensors, such as for geographic areas that do not have networks of road sensors and/or for arterial roads that are not significantly large to have road sensors, for road sensors that are broken, etc.), to verify duplicative information that is received from road sensors or other sources, to identify road sensors that are providing inaccurate data ( e.g ., due to temporary or ongoing problems), etc.
  • road traffic conditions may be measured and represented in one or more of a variety of ways, whether based on data samples from mobile data sources and/or from traffic sensor data readings, such as in absolute terms (e.g ., average speed; volume of traffic for an indicated period of time; average occupancy time of one or more traffic sensors or other locations on a road, such as 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, such as measured based on one or more other traffic condition measures; etc.) and/or in relative terms (e.g ., to represent a difference from typical or from maximum).
  • absolute terms e.g ., average speed; volume of traffic for an indicated period of time; average occupancy time of one or more traffic sensors or other locations on a road, such as 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, such as measured based on one or more other traffic condition measures; etc.
  • some road traffic condition information may take the form of data samples provided by various data sources, such as data sources associated with vehicles to report travel characteristics of the vehicles. Individual data samples may include varying amounts of information.
  • data samples provided by mobile data sources may include one or more of a source identifier, a speed indication, an indication of a heading or direction, an indication of a location, a timestamp, and a status identifier.
  • the source identifier may be a number or string that identifies the vehicle (or person or other device) acting as a mobile data source.
  • the mobile data source identifier may be permanently or temporarily (e.g ., for the life of the mobile data source; for one hour; for a current session of use, such as to assign a new identifier each time that a vehicle or data source device is turned on; etc.) associated with the mobile data source.
  • source identifiers are associated with mobile data sources in such a manner as to minimize privacy concerns related to the data from the mobile data sources (whether permanently or temporarily associated), such as by creating and/or manipulating the source identifiers in a manner that prevents the mobile data source associated with an identifier from being identified based on the identifier.
  • the speed indication may reflect the instant or average velocity of the mobile data source expressed in various ways (e.g ., miles per hour).
  • the heading may reflect a direction of travel and be an angle expressed in degrees or other measure (e.g ., in compass-based headings or radians).
  • the indication of location may reflect a physical location expressed in various ways ( e.g ., latitude/longitude pairs or Universal Transverse Mercator coordinates).
  • the timestamp may denote the time at which a given data sample was recorded by the mobile data source, such as in local time or UTC ("Universal Coordinated Time") time.
  • a status indicator may indicate the status of the mobile data source (e.g ., that the vehicle is moving, stopped, stopped with engine running, etc.) and/or the status of at least some of the sensing, recording, and/or transmitting devices (e.g ., low battery, poor signal strength, etc.).
  • the network of roads in a given geographic region may be modeled or represented by the use of multiple road segments.
  • Each road segment may be used to represent a portion of a road (or of multiple roads), such as by dividing a given physical road into multiple road segments ( e.g ., with each road segment being a particular length, such as a one-mile length of the road, or with road segments being selected to reflect portions of the road that share similar traffic condition characteristics) - such multiple road segments may be successive portions of the road, or may alternatively in some embodiments be overlapping or have intervening road portions that are not part of any road segments.
  • a road segment may represent one or more lanes of travel on a given physical road.
  • 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.
  • multiple lanes of a single 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.
  • 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 network of road segments.
  • Figure 1 is a block diagram illustrating data flow between components of an embodiment of a Data Sample Manager system.
  • the illustrated data flow diagram is intended to reflect a logical representation of data flow between data sources, components of an embodiment of a Data Sample Manager system, and traffic data clients. That is, actual data flow may occur via a variety of mechanisms including direct flows (e.g ., implemented by parameter passing or network communications such as messages) and/or indirect flows via one or more database systems or other storage mechanisms, such as file systems.
  • direct flows e.g ., implemented by parameter passing or network communications such as messages
  • indirect flows via one or more database systems or other storage mechanisms, such as file systems.
  • the illustrated Data Sample Manager system 100 includes a Data Sample Filterer component 104, a Sensor Data Conditioner component 105, a Data Sample Outlier Eliminator component 106, a Data Sample Speed Assessor component 107, and a Data Sample Flow Assessor component 108, and an optional Sensor Data Aggregator component 110.
  • the components 104-108 and 110 of the Data Sample Manager system 100 obtain data samples from various data sources, including vehicle-based data sources 101, road traffic sensors 103, and other data sources 102.
  • Vehicle-based data sources 101 may include multiple vehicles traveling on one or more roads, which may each include one or more computing systems and/or other devices that provide data about the travel of the vehicle.
  • each vehicle may include GPS and/or other geo-location devices capable of determining location, speed, and/or other data related to the vehicle's travel.
  • Road traffic sensors 102 may include multiple sensors that are installed in, at, or near various streets, highways, or other roads, such as loop sensors embedded in the pavement 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 flow. Data may similarly be obtained from the road traffic sensors 102 via wire-based or wireless-based data links.
  • Other data sources 103 may include a variety of other types of data sources, including map services and/or databases that provide information regarding road networks such as the connections between roads as well as traffic control information related to such roads (e.g ., the existence and/or location of traffic control signals and/or speed zones).
  • the illustrated data sources 101-103 in this example provide data samples directly to various components 104-108 and 110 of the Data Sample Manager system 100
  • the data samples may instead be processed in various ways in other embodiments prior to their provision to those components.
  • processing may include organizing and/or aggregating data samples into logical collections based on time, location, geographic region, and/or the identity of the individual data source (e.g ., vehicle, traffic sensor, etc.).
  • processing may include merging or otherwise combining data samples into higher-order, logical data samples or other values. For example, data samples obtained from multiple geographically co-located road traffic sensors may be merged into a single, logical data sample by way of averaging or other aggregation.
  • processing may include deriving or otherwise synthesizing data samples or elements of data samples based on one or more obtained data samples.
  • vehicle-based data sources may each provide data samples that include only a source identifier and a geographic location, and if so groups of multiple distinct data samples provided periodically over a particular time interval or other time period can thereby be associated with one another as having been provided by a particular vehicle.
  • Such groups of data samples may then be further processed in order to determine other travel-related information, such as a heading for each data sample ( e.g .
  • the Data Sample Filterer component 104 obtains data samples from the vehicle-based data sources 101 and the other data sources 102 in the illustrated embodiment, and then filters the obtained data samples before providing them to the Data Sample Outlier Eliminator component 106 and optionally to the Data Sample Flow Assessor component 108.
  • filtering may include associating data samples with road segments corresponding to roads in a geographic area and/or identifying data samples that do not correspond to road segments of interest or that otherwise reflect vehicle locations or activities that are not of interest.
  • Associating data samples with road segments may include using the reported location and/or heading of each data sample to determine whether the location and heading correspond to a previously defined road segment.
  • Identifying data samples that do not correspond to road segments of interest may include removing or otherwise identifying such data samples so that they will not be modeled, considered, or otherwise processed by other components of the Data Sample Manager system 100 - such data samples to be removed may include those corresponding to roads of certain functional road classes (e.g ., residential streets) that are not of interest, those corresponding to particular roads or road segments that are not of interest, those corresponding to portions or sections of roads that are not of interest (e.g ., ramps and collector/distributor lanes/roads for freeways), etc.
  • certain functional road classes e.g ., residential streets
  • those corresponding to particular roads or road segments that are not of interest those corresponding to portions or sections of roads that are not of interest (e.g ., ramps and collector/distributor lanes/roads for freeways), etc.
  • Identifying data samples that otherwise reflect vehicle locations or activities that are not of interest may include identifying data samples corresponding to vehicles that are in an idle state (e.g ., parked with engine running), that are driving in a parking structure ( e.g ., circling at a very low speed), etc.
  • filtering may in some embodiments include identifying road segments that are (or are not) of interest for presentation or further analysis.
  • such filtering may include analyzing variability of traffic flow and/or level of congestion of various road segments within a particular time period (e.g ., hour, day, week), such as to exclude some or all road segments with low intra-time period variability and/or low congestion (e.g ., for road segments for which sensor data readings are not available or whose functional road class otherwise indicates a smaller or less-traveled road) from further analysis as being of less interest than other roads and road segments.
  • a particular time period e.g ., hour, day, week
  • the Sensor Data Conditioner component 105 assists in rectifying erroneous data samples, such as by detecting and correcting errors in readings obtained from the road traffic sensors 103. For example, data samples that are detected by the Sensor Data Conditioner component as being unreliable are not forwarded on to other components for use (or indications of the unreliability of particular data samples are provided so that the other components can handle those data samples accordingly), such as to the Data Sample Outlier Eliminator component 106. If so, the Data Sample Outlier Eliminator component may then determine whether sufficient reliable data samples are available, and initiate corrective action if not.
  • the Sensor Data Conditioner component may further perform at least some corrections to the data samples, as discussed in greater detail below, and then provide the corrected data to the Sensor Data Aggregator component 110 (and optionally to other components such as the Data Sample Outlier Eliminator component and/or the Data Sample Flow Assessor component). Detecting erroneous data samples may use various techniques, including statistical measures that compare the distribution of current data samples reported by a given road traffic sensor to the historical distribution of data samples reported by that road traffic sensor during a corresponding time period ( e.g ., same day-of-week and time-of-day).
  • the extent to which the actual and historical distributions differ may be calculated by statistical measures, such as the Kullback-Leibler divergence, which provides a convex measure of the similarity between two probability distributions, and/or by statistical information entropy.
  • some road sensors may report indications of sensor health, and such indications may also be utilized to detect errors in obtained data samples. If errors are detected in obtained data samples, erroneous data samples may be rectified in various ways, including by replacing such data samples with averages of adjacent ( e.g ., neighbor) data samples from adjacent/neighbor road sensors that have not been determined to be erroneous. In addition, erroneous data samples may be rectified by instead using previously or concurrently forecasted and/or predicted values, such as may be provided by a predictive traffic information system. Additional details regarding predictive traffic information systems are provided elsewhere.
  • the Data Sample Outlier Eliminator component 106 in accordance with the present invention obtains filtered data samples from the Data Sample Filterer component 104 and/or conditioned or otherwise rectified data samples from the Sensor Data Conditioner component 105, and then identifies and eliminates from consideration those data samples that are not representative of actual vehicle travel on the roads and road segments of interest.
  • the component analyzes a group of data samples that were recorded during a particular time period and associated with the road segment ( e.g ., by the Data Sample Filterer component 104) in order to determine which, if any, should be eliminated.
  • Such determinations of unrepresentative data samples may be performed in various ways, including based on techniques that detect data samples that are statistical outliers with respect to the other data samples in the group of data samples. Additional details regarding data sample outlier elimination are provided elsewhere.
  • the Data Sample Speed Assessor component 107 obtains data samples from the Data Sample Outlier Eliminator component 106, such that the obtained data samples in the illustrated embodiment are representative of actual vehicle travel on the roads and road segments of interest. The Data Sample Speed Assessor component 107 then analyzes the obtained data samples to assess one or more speeds for road segments of interest for at least one time period of interest based on a group of the data samples that have been associated with the road segment ( e.g ., by the Data Sample Filterer component 104, or by readings from traffic sensors that are part of the road segment) and the time period.
  • the assessed speed(s) may include an average of the speeds for multiple of the data samples of the group, possibly weighted by one or more attributes of the data samples (e.g ., age, such as to give greater weight to newer data samples, and/or source or type of the data samples, such as to vary the weight for data samples from mobile data sources or from road sensors so as to give greater weight to sources with higher expected reliability or availability) or by other factors. More details regarding speed assessment from data samples are provided elsewhere.
  • attributes of the data samples e.g ., age, such as to give greater weight to newer data samples, and/or source or type of the data samples, such as to vary the weight for data samples from mobile data sources or from road sensors so as to give greater weight to sources with higher expected reliability or availability
  • the Data Sample Flow Assessor component 108 assesses traffic flow information for road segments of interest for at least one time period of interest, such as to assess traffic volume (e.g ., expressed as a total or average number of vehicles arriving at or traversing a road segment over a particular amount of time, such as per minute or hour), to assess traffic density (e.g ., expressed as an average or total number of vehicles per unit of distance, such as per mile or kilometer), to assess traffic occupancy ( e.g ., expressed as an average or total amount of time that vehicles occupy a particular point or region over a particular amount of time, such as per minute or hour), etc.
  • traffic volume e.g ., expressed as a total or average number of vehicles arriving at or traversing a road segment over a particular amount of time, such as per minute or hour
  • traffic density e.g ., expressed as an average or total number of vehicles per unit of distance, such as per mile or kilometer
  • traffic occupancy e.g ., expressed as an average or total amount of time
  • the assessment of the traffic flow information in the illustrated embodiment is based at least in part on traffic speed-related information provided by the Data Sample Speed Assessor component 107 and the Data Sample Outlier Eliminator component 106, and optionally on traffic data sample information provided by the Sensor Data Conditioner component 105 and the Data Sample Filterer component 104. Additional details regarding data sample flow assessment are provided elsewhere.
  • the Sensor Data Aggregator component 110 aggregates sensor-based traffic condition information provided by the Sensor Data Conditioner component 105, such as after the Sensor Data Conditioner component has removed any unreliable data samples and/or has rectified any missing and/or unreliable data samples. Alternatively, the Sensor Data Aggregator component may instead perform any such removal and/or correction of missing and/or unreliable data samples. In some cases, the Sensor Data Aggregator component 110 may provide traffic flow information for each of various road segments by aggregating ( e.g ., averaging) Information provided by the multiple individual traffic sensors associated with each of those road segments.
  • the Sensor Data Aggregator component 110 may provide information that is complementary to assessed traffic condition information provided by components such as the Data Sample Speed Assessor component 107 and/or the Data Sample Flow Assessor component 108, or may instead be used if data samples from mobile data sources are not available at all or in sufficient quantity of reliable data samples to allow other components such as the Data Sample Speed Assessor component 107 and Data Sample Flow Assessor component 108 to provide accurate assessed road traffic condition information.
  • the one or more traffic data clients 109 may obtain assessed road traffic condition information (e.g ., speed and/or flow data) provided by the Data Sample Speed Assessor component 107 and/or the Data Sample Flow Assessor component 108, and may utilize such data in various ways.
  • traffic data clients 109 may include other components and/or traffic information systems operated by the operator of the Data Sample Manager system 100, such as a predictive traffic information provider system that utilizes traffic condition information in order to generate predictions of future traffic conditions at multiple future times, and/or a realtime (or near-realtime) traffic information presentation or provider system that provides realtime (or near-realtime) traffic condition Information to end-users and/or third-party clients.
  • traffic data clients 109 may include computing systems operated by third parties in order to provide traffic information services to their customers.
  • the one or more traffic data clients 109 may optionally in some circumstances (e.g ., in instances when insufficient data is available for the Data Sample Speed Assessor component and/or Data Sample Flow Assessor component to perform accurate assessments, and/or if no data is available from vehicle-based or other data sources) obtain road traffic condition information provided by the Sensor Data Aggregator component 110, whether instead of or in addition to data from the Data Sample Speed Assessor component and/or Data Sample Flow Assessor component.
  • Figures 2A-2E illustrate examples of assessing road traffic conditions based on data obtained from vehicles and other mobile data sources, such as may be performed by an embodiment of the described Data Sample Manager system.
  • Figure 2A illustrates an example of data sample filtering for an example area 200 with several roads 201, 202, 203. and 204, and with a legend indication 209 indicating the direction of north.
  • road 202 is a divided, limited access road such as a freeway or toll road, with two distinct groups of lanes 202a and 202b for vehicle travel in the west and east directions, respectively.
  • Lane group 202a includes an HOV lane 202a2 and multiple other regular lanes 202a1, and lane group 202b similarity includes an HOV lane 202b2 and multiple other regular lanes 202b1.
  • Road 201 is an arterial road with two lanes 201 a and 201 b for vehicle travel in the south and north directions, respectively.
  • Road 201 passes over road 202 ( e.g ., via an overpass or bridge), and road 204 is an on-ramp that connects the northbound lane 201b of road 201 to the eastbound lane group 202b of road 202.
  • Road 203 is a local frontage road adjoining road 202.
  • the roads depicted in Figure 2A may be represented in various ways for use by the described Data Sample Manager system.
  • one or more road segments may be associated with each physical road, such as to have northbound and southbound road segments associated with the northbound lane 201 b and southbound lane 201b, respectively.
  • at least one westbound road segment and at least one eastbound road segment may be associated with the westbound lane group 202a and the eastbound lane group 202b of road 202, respectively.
  • the portion of the eastbound lane group 202b east of road 201 may be a separate road segment from the portion of the eastbound lane group 202b west of road 201, such as based on the road traffic conditions typically or often varying between the road portions ( e.g ., due to a typically significant influx of vehicles to lane group 202b east of road 201 from the on-ramp 204, such as that may typically cause greater congestion in lane group 202b to the east of road 201).
  • one or more lane groups may be decomposed into multiple road segments, such as if different lanes typically or often have differing road traffic condition characteristics (e.g ., to represent any given portion of lane group 202b as a first road segment corresponding to lanes 202b1 based on those lanes sharing similar traffic condition characteristics, and as a second road segment corresponding to HOV lane 202b2 due to its differing traffic condition characteristics) - in other such situations, only a single road segment may be used for such a lane group, but some data samples (e.g ., those corresponding to HOV lane 202b2) may be excluded from use (such as by a Data Sample Filterer component and/or a Data Sample Outlier Eliminator component) when assessing road traffic conditions for the lane group.
  • differing road traffic condition characteristics e.g ., to represent any given portion of lane group 202b as a first road segment corresponding to lanes 202b1 based on those lanes sharing similar traffic condition characteristics, and as a
  • some embodiments may represent multiple lanes of a given road as a single road segment, even if the lanes are used for travel in opposite directions, such as if the road traffic conditions are typically similar in both directions - for example, frontage road 205a may have two opposing lanes of travel, but may be represented by a single road segment.
  • Road segments may be determined at least in part in a variety of other ways , such as to be associated with geographic information (e.g ., physical dimensions and/or heading(s)) and/or traffic-related information (e.g ., speed limits).
  • Figure 2A further depicts multiple data samples 205a-k reported by multiple mobile data sources (e.g ., vehicles, not shown) traveling in the area 200 during a particular time interval or other time period (e.g . 1 minute, 5 minutes, 10 minutes, 15 minutes, etc.).
  • Each of the data samples 205a-k is depicted as an arrow that indicates a heading for the data sample, as reported by one of the multiple mobile data sources.
  • the data samples 205a-k are superimposed upon the area 200 in such a manner as to reflect locations reported for each of the data samples (e.g ., expressed in units of latitude and longitude, such as based on GPS readings), which may differ from the actual locations of the vehicle when that data sample was recorded ( e.g ., due to an inaccurate or erroneous reading, or due to a degree of variability that is inherent for the location sensing mechanism used).
  • data sample 205g shows a location that is slightly north of the road 202b, which may reflect a vehicle that was pulled over off the north side of lane 202b2 ( e.g ., because of a mechanical malfunction), or it instead may reflect an inaccurate location for a vehicle that was in fact traveling in the eastbound direction in lane 202b2 or other lane.
  • a single mobile data source may be the source of more than one of the illustrated data samples, such as if both sample 205i and sample 205h were reported by a single vehicle based on its travel eastbound along road 202 during the time period ( e.g ., via a single transmission containing multiple data samples for multiple prior time points, such as to report data samples every 5 minutes or every 15 minutes). More details regarding storing and providing multiple acquired data samples are included below.
  • the described Data Sample Manager system may filter the obtained data samples, such as to map data samples to predefined road segments and/or identify data samples that do not correspond to such road segments of interest.
  • a data sample may be associated with a road segment if its reported location is within a predetermined distance (e.g ., 5 meters) of the location of a road and/or lane(s) corresponding to the road segment and if its heading is within a predetermined angle (e.g ., plus or minus 15 degrees) of the heading of the road and/or lanes(s) corresponding to the road segment.
  • Road segments may be associated with sufficient location-based information (e.g ., heading of the road segment, physical bounds of the road segment, etc.) to make such a determination, although the association of data samples to road segments may be also performed before the data samples are made available to the Data Sample Manager system.
  • location-based information e.g ., heading of the road segment, physical bounds of the road segment, etc.
  • data sample 205a may be associated with a road segment corresponding to road 203, because its reported location falls within the bounds of road 203 and its heading is the same (or nearly the same) as at least one of the headings associated with road 203.
  • the heading of a data sample may be compared to both headings of the road segment in order to determine whether the data sample may be associated with the road segment.
  • data sample 205k has a heading approximately opposite that of data sample 205a, but it may also be associated with the road segment corresponding to road 203, if that road segment is utilized to represent the two opposing lanes of road 203.
  • data sample 205k reflects a vehicle traveling in lane group 202a, such as if the reported location of data sample 205k is within a margin of error for locations of vehicles traveling in one or more of the lanes of lane group 202a, since the heading of data sample 205k is the same (or nearly the same) as the heading of lane group 202a.
  • such cases of multiple possible road segments for a data sample may be disambiguated based on other information associated with the data sample - for example, in this case, an analysis of the reported speed of data sample 205k may be used to assist in the disambiguation, such as if lane group 202a corresponds to a freeway with a 65mph speed limit, road 203 is a local frontage road with a 30mph speed limit, and a reported speed of the data sample is 75mph (resulting in an association with the freeway lane(s) being much more likely than an association with the local frontage road).
  • the reported speed of data sample 205k is more similar to the observed or posted speed for road 203 than to the observed or posted speed for lane group 202a, such information may be used as part of determining to associate the data sample with road 203 and not lane group 202a.
  • the reported speed of data sample 205k is more similar to the observed or posted speed for lane group 202a than to the observed or posted speed for road 203, it may be associated with lane group 202a and not road 203.
  • Other types of information may similarly be used as part of such disambiguation (e.g ., location; heading; status; information about other related data samples, such as other recent data samples from the same mobile data source; etc.), such as part of a weighted analysis to reflect a degree of match for each type of information for a data sample to a candidate road segment.
  • data sample 205c includes a reported location that may match multiple roads/lanes ( e.g ., lane 201 a, lane 201 b, and lane group 202a), but its heading (approximately westbound) may be used to select a road segment for lane group 202a as the most appropriate road segment for the data sample.
  • roads/lanes e.g ., lane 201 a, lane 201 b, and lane group 202a
  • its heading approximately westbound
  • data sample 205d may not be associated with any road segment, because its heading (approximately eastbound) is in the opposite direction as that of lane group 202a (westbound) whose position corresponds to the data sample's reported location. If there are no other appropriate candidate road segments that are near enough ( e.g ., within a predetermined distance) to the reported location of data sample 205d, such as if lane group 202b with a similar heading is too far way, this data sample may be excluded during filtering from subsequent use in analysis of the data samples.
  • Data sample 205e may be associated with a road segment corresponding to lane group 202a, such as a road segment corresponding to HOV lane 202a2, since its reported location and heading correspond to the location and heading of that lane, such as if a location-based technique used for the location of the data sample has sufficient resolution to differentiate between lanes (e.g ., differential GPS, infrared, sonar, or radar ranging devices). Data samples may also be associated with a particular lane of a multi-lane road based on factors other than location-based information, such as if the lanes have differing traffic condition characteristics.
  • a location-based technique used for the location of the data sample has sufficient resolution to differentiate between lanes (e.g ., differential GPS, infrared, sonar, or radar ranging devices).
  • Data samples may also be associated with a particular lane of a multi-lane road based on factors other than location-based information, such as if the lanes have differing traffic condition characteristics.
  • the reported speed of a data sample may be used to fit or match the data sample to a particular lane by modeling an expected distribution (e.g ., a normal or Gaussian distribution) of observed speeds (or other measures of traffic flow) of data samples for each such candidate lane and determining a best fit for the data sample to the expected distributions.
  • an expected distribution e.g ., a normal or Gaussian distribution
  • data sample 205e may be associated with the road segment corresponding to HOV lane 202a2 because the reported speed of that data sample is closer to an observed, inferred or historical average speed of vehicles traveling in HOV lane 202a2 than to an observed, inferred or historical average speed for vehicles traveling in regular lanes 202a1, such as by determining an observed or inferred average speed based on other data samples (e.g ., using data readings provided by one or more road traffic sensors) and/or analysis of other related current data.
  • other data samples e.g ., using data readings provided by one or more road traffic sensors
  • data samples 205f, 205h, 205i, and 205j may be associated with the road segments corresponding to lane 201a, lanes 202b1, lanes 202b1, and ramp 204, respectively, because their reported locations and headings correspond to the locations and headings of those roads or lanes.
  • Data sample 205g may be associated with a road segment corresponding to lane group 202b (e.g ., a road segment for HOV lane 202b2) even though its reported location is outside of the bounds of the illustrated road, because the reported location may be within the predetermined distance (e.g ., 5 meters) of the road. Alternatively, data sample 205g may not be associated with any road segment if its reported location is sufficiently far from the road. In some instances, different predetermined distances may be used for data samples provided by different data sources, such as to reflect a known or expected level of accuracy of the data source.
  • data samples provided by mobile data sources that utilize uncorrected GPS signals may use a relatively high (e.g ., 30 meters) predetermined distance, whereas data samples provided by mobile data sources utilizing differential-corrected GPS devices may be compared using a relatively low (e.g ., 1 meter) predetermined distance.
  • data sample filtering may include identifying data samples that do not correspond to road segments of interest and/or are unrepresentative of actual vehicle travel on the roads. For instance, some data samples may be removed from consideration because they have been associated with roads that are not being considered by the Data Sample Manager system. For example, in some instances data samples associated with roads of lesser functional road classes (e.g ., residential streets and/or arterials) may be filtered. Referring back to Figure 2A , for example, data samples 205a and/or 205k may be filtered because road 203 is a local frontage road that is of a sufficiently low functional classification to not be considered by the Data Sample Manager system, or data sample 205j may be filtered because the on-ramp is too short to be of interest separate from the freeway.
  • data samples 205a and/or 205k may be filtered because road 203 is a local frontage road that is of a sufficiently low functional classification to not be considered by the Data Sample Manager system, or data sample 205j may be filtered because the on-ramp is too
  • Filtering may further be based on other factors, such as inferred or reported activity of mobile data sources relative to the inferred or reported activity of other mobile data sources on one or more road segments. For example, a series of data samples associated with a road segment and provided by a single mobile data source that all indicate the same location likely indicates that the mobile data source has stopped. If all other data samples associated with the same road segment indicate moving mobile data sources, the data samples corresponding to the stopped mobile data source may be filtered out as being unrepresentative of actual vehicle travel on the road segment, such as due to the mobile data source being a parked vehicle.
  • data samples may include reported indications of the driving status of the vehicle (e.g ., that the vehicle transmission is in "park” with the engine running, such as a vehicle stopped to make a delivery), and if so such indications may similarly be used to filter such data samples as being unrepresentative of actual traveling vehicles.
  • Figure 2B illustrates a graphical view of multiple data samples associated with a single road segment obtained from multiple data sources during a particular time interval or other time period, with the data samples plotted on a graph 210 with time measured on the x-axis 210b and speed measured on the y-axis 210a.
  • the illustrated data samples have been obtained from multiple mobile data sources as well as one or more road traffic sensors associated with the road segment, and are shown with differing shapes as illustrated in the displayed legend ( i.e ., with darkened diamonds (" ⁇ ”) for data samples obtained from road traffic sensors, and with open squares (" ⁇ ”) for data samples obtained from mobile data sources).
  • the illustrated data samples from mobile data sources may have been associated with the road segment as described with reference to Figure 2A .
  • Exemplary data samples include road traffic sensor data samples 211 a-c and mobile data source data samples 212a-d.
  • the reported speed and recording time of a given data sample may be determined by its position on the graph.
  • mobile data source data sample 212d has a reported speed of 15 miles per hour (or other speed unit) and was recorded at a time of approximately 37 minutes (or other time unit) relative to some starting point.
  • some exemplary instances may analyze or otherwise process obtained data samples within particular time windows during the time period being represented, such as time window 213.
  • time window 213 contains data samples recorded during a 10-minute interval from time 30 minutes to time 40 minutes.
  • some exemplary instances may further partition the group of data samples occurring within a particular time window into two or more groups, such as group 214a and group 214b.
  • group 214a and group 214b may further partition the group of data samples occurring within a particular time window into two or more groups, such as group 214a and group 214b.
  • group 214a and group 214b may further partition the group of data samples occurring within a particular time window into two or more groups, such as group 214a and group 214b.
  • group 214a and group 214b may further partition the group of data samples occurring within a particular time window into two or more groups, such as group 214a and group 214b.
  • the illustrated data samples appear to reflect a bi-modal distribution of reported speeds, with the bulk of the data samples reporting speeds in the range of 25-30 miles per hour or in the range of 0-8 miles per hour.
  • Such a bi-modal or other multi-modal distribution of speeds may occur, for example, because the underlying traffic flow patterns are nonuniform, such as due to a traffic control signal that causes traffic to flow in a stop-and-go pattern, or to the road segment including multiple lanes of traffic that are moving at different speeds (e.g ., an HOV or express lane with relatively higher speeds than other non-HOV lanes).
  • some exemplary instances may partition the data samples into two or more groups for further processing, such as to produce improved accuracy or resolution of processing (e.g ., by calculating distinct average speeds that more accurately reflect the speeds of various traffic flows) as well as additional information of interest (e.g ., the speed differential between HOV traffic and non-HOV traffic), or to identify a group of data samples to exclude ( e.g ., to not include HOV traffic as part of a subsequent analysis).
  • additional information of interest e.g ., the speed differential between HOV traffic and non-HOV traffic
  • identify a group of data samples to exclude e.g ., to not include HOV traffic as part of a subsequent analysis.
  • such distinct groups of data samples may be Identified in various ways, Including by modeling a distinct distribution (e.g ., a normal or Gaussian distribution) for the observed speeds of each group.
  • Figure 2C illustrates an example of performing data sample outlier elimination to filter or otherwise exclude from consideration those data samples that are unrepresentative of vehicles traveling on a particular road segment, which in this example is based on the reported speed for the data samples (although in other instances one or more other attributes of the data samples could instead be used as part of the analysis, whether instead of or in addition to the reported speeds).
  • Figure 2C shows a table 220 that illustrates data sample outlier elimination being performed on an example group of ten data samples (in actual use, the numbers of data samples being analyzed may be much larger).
  • the illustrated data samples may, for example, be all of the data samples occurring within a particular time window (such as time window 213 of Figure 2B ), or alternatively may include only a subset of the data samples of a particular time window (such as those included in group 214a or 214b of Figure 2B ) or may include all data samples available for a larger time period.
  • unrepresentative data samples are identified as being statistical outliers with respect to other data samples in a determined group of data samples by determining the deviation of the speed of each data sample in a group of data samples from the average speed of the other data samples in the group.
  • the deviation of each data sample may be measured, for example, in terms of the number of standard deviations difference from the average speed of the other data samples In the group, with data samples whose deviations are greater than a predetermined threshold (e.g ., 2 standard deviations) being identified as outliers and being excluded from further processing ( e.g ., by being discarded).
  • Table 220 includes a heading row 222 that describes the contents of multiple columns 221a-f.
  • Each row 223a-j of table 220 illustrates a data sample outlier elimination analysis for a distinct one of the ten data samples, with column 221a indicating the data sample being analyzed for each row - as each data sample is analyzed, it is excluded from the other samples of the group to determine the difference that results.
  • the data sample of row 223a may be referred to as the first data sample
  • the data sample of row 223b may be referred to as the second data sample, and so on.
  • Column 221b contains the reported speed of each of the data samples, measured in miles per hour.
  • Column 221 c lists the other data samples in the group against which the data sample of a given row will be compared, and column 221d lists the approximate average speed of the group of data samples indicated by column 221 c.
  • Column 221 e contains the approximate deviation between the speed of the excluded data simple from column 221b and the average speed listed in column 221d of the other data samples, measured in number of standard deviations.
  • Column 221f indicates whether the given data sample would be eliminated, based on whether the deviation listed in column 221e is greater than 1.5 standard deviations for the purposes of this example.
  • the averages speed 224 for all 10 data samples is shown to be approximately 25.7 miles per hour, and the standard deviation 225 of all 10 data samples is shown to be approximately 14.2.
  • row 223a illustrates that the speed of data sample 1 is 26 miles per hour.
  • the average speed of the other data samples 2-10 is calculated as approximately 25.7 miles per hour.
  • the deviation of the speed of data sample 1 from the average speed of the other data samples 2-10 is then calculated as being approximately .02 standard deviations.
  • data sample 1 is determined to not be an outlier since its deviation is below the threshold of 1.5 standard deviations.
  • row 223c illustrates that the speed of data sample 3 is 0 miles per hour and that the average speed of the other data samples 1-2 and 4-10 is calculated as approximately 28.6 miles per hour.
  • the deviation of the speed of data sample 3 from the average speed of the other data samples 1-2 and 4-10 is calculated as approximately 2.44 standard deviations.
  • data sample 3 is determined to be eliminated as an outlier because its deviation is above the threshold of 1.5 standard deviations.
  • a current data sample v i will be eliminated if v i - v ⁇ i ⁇ i ⁇ c
  • v i is speed of the current data sample being analyzed
  • ⁇ i is the average of the speed of the other data samples ( ⁇ 0 , ..., ⁇ i - l , v i + l , ..., v n );
  • ⁇ i is the standard deviation of the other data samples; and
  • c is a constant threshold ( e.g ., 1.5).
  • the current sample v i will be eliminated if the standard deviation of the other data samples, ⁇ i , is zero and the speed of the current data sample is not equal to the average speed of the other data samples, ⁇ i .
  • the averages and standard deviations may be efficiently calculated, and in particular may be calculated in constant time. Since the above algorithm calculates an average and a standard deviation for each data sample in each road segment, the algorithm runs in O( MN ) time, where M is the number of road segments and N is the number of data samples per road segment.
  • outlier detection and/or data elimination algorithms comprise techniques based on neural network classifiers, na ⁇ ve Bayesian classifiers, and/or regression modeling, as well as techniques in which groups of multiple data samples are considered together ( e.g ., if at least some data samples are not independent of other data samples).
  • Figure 2D illustrates an example of performing average speed assessment using data samples, and shows example data samples similar to those depicted in Figure 2B for a particular road segment and period of time.
  • the data samples have been plotted on a graph 230, with time measured on the x-axis 230b and speed measured on the y-axis 230a.
  • the average speed for a given road segment may be computed on a periodic basis ( e.g . every 5 minutes). Each computation may consider multiple data samples within a predetermined time window (or interval), such as 10 minutes or 15 minutes.
  • data samples within a time window may be weighted in various manners when aggregating the speeds of the data samples, such as to take into account the age of data samples (e.g ., to discount older data samples based on the intuition and the expectation that they do not provide as accurate information as to the actual traffic conditions at the end of the time window or other current time as younger data samples recorded relatively nearer the current time due to changing traffic conditions).
  • weighting data samples such as a type of data source or a particular data source for a data sample (e.g ., to weight data samples more heavily if they come from a type of data source or a particular data source that is believed to be more accurate than others or to otherwise provide better data than others), as well as one or more other types of weighting factors.
  • an average speed for the example road segment is computed every five minutes over a 15-minute time window.
  • the example depicts the relative weights of two illustrative data samples, 231 a and 231 b, as they contribute to the computed average speed of each of two time windows, 235a and 235b.
  • the time window 235a includes data samples recorded between times 30 and 45
  • the time window 235b includes data samples recorded between times 35 and 50.
  • Data samples 231 a and 231 b both fall within both time windows 235a and 235b.
  • each data sample in a given time window is weighted in proportion to its age. That is, older data samples weigh less (and therefore contribute less to the average speed) than younger data samples. Specifically, the weight of a given data sample decreases exponentially with age in this example.
  • This decaying weighting function is illustrated by way of two weight graphs 232a and 232b corresponding to time windows 235a and 235b, respectively. Each weight graph 232a and 232b plots data sample recording time on the x-axis (horizontal) against weight on the y-axis (vertical).
  • Samples recorded later in time weigh more than samples recorded earlier in time (e.g ., nearer the beginning of the time window).
  • the weight for a given data sample may be visualized by dropping a vertical line downwards from the data sample in graph 230 to where it intersects with the curve of the weight graph corresponding to the time window of interest.
  • weight graph 232a corresponds to time window 235a, and in accordance with the relative ages of data samples 231a (older) and 231 b (younger), the weight 233a of data sample 231 a is less than the weight 233b of data sample 231 b.
  • weight graph 232b corresponds to time interval 235b, and it similarly can be seen that the weight 234a of data sample 231a is less than the weight 234b of data sample 231 b.
  • the weight of a given data sample decays over time with respect to subsequent time windows. For example, the weight 233b, of data sample 231 b in time window 235a is greater than the weight 234b of the same data sample 231b in the later time window 235b, because data sample 231 b is relatively younger during time window 235a compared to time window 235b.
  • Other forms of confidence values may similarly be determined for computed or generated average speeds.
  • data samples may be weighted based on other factors, whether instead of or in addition to recency of the data samples.
  • data samples may be time-weighted as described above but by utilizing different weight functions (e.g ., to have the weight of a data sample decrease linearly, rather than exponentially, with age).
  • data sample weighting may be further based on the total number of data samples in the time interval of interest.
  • variable parameter ⁇ described above may depend or otherwise vary based on the total number of data samples, such that greater numbers of data samples result in higher penalties (e.g ., lower weights) for older data samples, to reflect the increased likelihood that there will be more low latency ( e.g ., younger) data samples available for purposes of computing average speed.
  • data samples may be weighted based on other factors, including type of data source. For example, it may be the case that particular data sources (e.g ., particular road traffic sensors, or all traffic sensors of a particular network) are known ( e.g ., based on reported status information) or expected ( e.g ., based on historical observations) to be unreliable or otherwise inaccurate.
  • data samples obtained from such road traffic sensors may be weighted less than data samples obtained from mobile data sources (e.g ., data sample 212a of Figure 2B ).
  • Figure 2E facilitates an example of performing traffic flow assessment for road segments based on data samples, such as may include inferring traffic volumes, densities, and/or occupancy.
  • traffic volume of a given road segment is expressed as a total number of vehicles flowing in a given time window over the road segment or a total number of vehicles arriving at the road segment during the time window
  • traffic density of a given road segment is expressed as a total number of vehicles per unit distance ( e.g ., miles or kilometers)
  • traffic occupancy is expressed as an average amount of time that a particular road segment or point on the road segment is occupied by a vehicle.
  • An unsophisticated approach to estimating total traffic volume of a particular road segment during a particular time window would be to simply divide the number of mobile data sample sources for that time window by the percentage of actual vehicles expected to be mobile data sample sources - thus, for example, if mobile data samples are received from 25 mobile data sources during the time window and 10% of the total vehicles on the road segment are expected to be mobile data sample sources, the estimated total volume would be 250 actual vehicles for the amount of time of the time window.
  • this approach may lead to large variability of volume estimates for adjacent time windows due to the inherent variability of arrival rates of vehicles, particularly if the expected percentage of mobile data sample sources is small.
  • total traffic volume of a given road segment may be inferred as follows.
  • Bayesian statistics can be utilized to infer an underlying mean rate of arrival of mobile data sources, ⁇ .
  • the arrival of mobile data sources on the stretch of road corresponding to the road segment may be modeled as a random, discrete process in time, and therefore may be described by Poisson statistics, such that: p n
  • ⁇ ⁇ n ⁇ e - ⁇ n !
  • a likelihood that n mobile data sources will be observed may be calculated, given a mean arrival rate ⁇ and an observed number of vehicles n .
  • Bayes Theorem is: p ⁇
  • n p n
  • a proportional or relative likelihood of an arrival rate ⁇ may be calculated, providing a probability distribution over possible values of ⁇ given various observed values for n.
  • the distribution of likelihoods over various arrival rate values allows a single representative arrival rate value to be selected (e.g ., a mean or a median) and a degree of confidence in that value to be assessed.
  • Total traffic volume for a road segment during a time period may alternatively be expressed as a total number of vehicles k flowing in time ⁇ over a length / of the road segment.
  • Figure 2E depicts a three dimensional graph 240 that plots observed number of mobile data sources (n) on the y-axis 241 against inferred traffic arrival rate volume on the x-axis 242 and against likelihood of each Inferred traffic volume value on the z-axis 243.
  • the likelihood that the total actual traffic volume is near 2143 vehicles per unit time is approximately 0.1, as illustrated by bar 244c, which appears to be close to the median value for total actual traffic volume.
  • the average speed v of vehicles on the road segment may be obtained by utilizing speed assessment techniques, such as those described with reference to Figure 2D .
  • Figures 10A-10B illustrate examples of conditioning and otherwise rectifying erroneous data samples from road traffic sensors, such as unreliable and missing data samples.
  • Figure 10A shows a number of example data readings obtained from multiple traffic sensors at various times, organized into a table 1000.
  • the table 1000 includes multiple data reading rows 1004a-1004y that each include a traffic sensor ID ("Identifier") 1002a that uniquely identifies the traffic sensor that provided the reading, a traffic sensor data reading value 1002b that includes traffic flow information reported by the traffic sensor, a time of traffic sensor data reading 1002c that reflects the time at which the data reading was taken by the traffic sensor, and a traffic sensor state 1002d that includes an indication of the operational state of the traffic sensor.
  • Identifier traffic sensor ID
  • 1002b that includes traffic flow information reported by the traffic sensor
  • time of traffic sensor data reading 1002c that reflects the time at which the data reading was taken by the traffic sensor
  • a traffic sensor state 1002d that includes an indication of the operational state of the traffic sensor.
  • the data readings 1004a-1004y have been taken by multiple traffic sensors at various times and recorded as represented in the table 1000.
  • data readings may be taken by traffic sensors on a periodic basis (e.g ., every minute, every five minutes, etc.) and/or reported by the traffic sensors on such a periodic basis.
  • traffic sensor 123 takes data readings every five minutes, as shown by data readings 1004a-1004d and 1004f-1004i that illustrate a number of data readings taken by traffic sensor 123 between 10:25AM and 10:40AM on two separate days (in this example, 8/13/06 and 8/14/06).
  • Each illustrated data reading 1004a-1004y includes a data reading value 1002b that includes traffic flow information observed or otherwise obtained by the data sensor.
  • traffic flow information may include the speed of one or more vehicles traveling at, near, or over a traffic sensor.
  • data readings 1004a-1004d show that traffic sensor 123 observed, at four different times, vehicle speeds of 34 miles per hour (mph), 36 mph, 42 mph, and 38 mph, respectively.
  • traffic flow information may include total or incremental counts of vehicles traveling at, near, or over a traffic, sensor, whether instead of or in addition to speed and/or other information. Total counts may be a cumulative count of vehicles observed by a traffic sensor since the sensor was installed or otherwise activated.
  • Incremental counts may be a cumulative count of vehicles observed by a traffic sensor since the traffic sensor took a previous data reading.
  • Data readings 1004w-1004x show that traffic sensor 166 counted, at two different times, 316 cars and 389 cars, respectively.
  • recorded data readings may not include data reading values, such as when a given traffic sensor has experienced a sensor malfunction, such that it cannot make or record an observation or report an observation ( e.g ., due to a network failure).
  • data reading 1004k shows that traffic sensor 129 was unable to provide a data reading value at 10:25 AM on the day of 8/13/06, as indicated by a "--" in the data reading value column 1002b.
  • a traffic sensor state 1002d may be associated with at least some data readings, such as if a traffic sensor and/or corresponding communications network provides an indication of the operational state of the traffic sensor.
  • Operational states may include indications that a sensor is functioning properly (e.g ., OK), that a sensor is in a power-off state ( e.g . OFF), that a sensor is stuck reporting a single value ( e.g ., STUCK), and/or that a communications link to the network is down ( e.g ., COM_DOWN), as illustrated in data readings 1004m, 1004k, 1004o, and 1004s, respectively.
  • traffic sensors 123 and 166 in this example are not configured to provide indications of traffic sensor state, as indicated by a "--" in the traffic sensor state column 1002d.
  • Rows 1004e, 1004j, 1004n, 1004q, 1004v, and 1004y and column 1002e indicate that additional traffic sensor data readings may be recorded in some instances and/or that additional information may be provided and/or recorded as part of each data reading. Likewise, less information than is shown may be utilized as a basis for the techniques described herein.
  • Figure 10B illustrates examples of detecting errors in traffic sensor data readings that may be indicative of unhealthy traffic sensors that are operating incorrectly.
  • many traffic sensors may not provide an indication of traffic sensor state, and because in some cases such indications of traffic sensor state may be unreliable (e.g ., indicating that a sensor is not functioning properly when in fact it is, or indicating that a sensor is functioning properly when in fact it is not), it may be desirable to utilize statistical and/or other techniques to detect unhealthy traffic sensors based on reported data reading values.
  • an unhealthy traffic sensor may be detected by comparing a current distribution of data readings reported by a given traffic sensor during a time period (e.g ., between 4:00PM and 7:29PM) on a particular day to a historical distribution of data readings reported by the traffic sensor during the same time period over multiple past days ( e.g ., the past 120 days).
  • Such distributions may be generated by, for example, processing multiple data readings obtained from a traffic sensor, such as those shown in Figure 10A .
  • Figure 10B shows three histograms 1020, 1030, and 1040 that each represents a data reading distribution based on data readings obtained from traffic sensor 123 during a time period of interest.
  • the data represented in histograms 1020, 1030, and 1040 is discretized into 5 mile per hour intervals ( e.g ., 0 to 4 miles per hour, 5 to 9 miles per hour, 10 to 14 miles per hour, etc.) and is normalized, such that each bar ( e.g , bar 1024) represents a probability between 0 and 1 that vehicle speeds within the 5 mile per hour bucket for that bar occurred during the time period ( e.g ., based on a percentage of data readings during the time period that fall within the bucket).
  • 5 mile per hour intervals e.g ., 0 to 4 miles per hour, 5 to 9 miles per hour, 10 to 14 miles per hour, etc.
  • bar 1024 represents a probability between 0 and 1 that vehicle speeds within the 5 mile per hour bucket for that bar occurred during the time period
  • bar 1024 indicates that vehicle speeds between 50 and 54 miles per hour were observed by traffic sensor 123 with a probability of approximately 0.23, such as based on approximately 23% of the data readings obtained from traffic sensor 123 having reported speeds between 50 and 54 miles per hour, inclusive.
  • one or more other bucket sizes may be used, whether in addition to or instead of a 5 mph bucket.
  • a 1 mph bucket may provide a finer granularity of processing, but may also cause high variability between adjacent buckets if sufficient data readings are not available for the time period, while a 10 mph bucket would provide less variability but also less detail.
  • average speed as the measure for analysis and comparison for data readings
  • one or more other measures may be used, whether instead of or in addition to average speed.
  • traffic volume and/or occupancy may similarly be used.
  • histogram 1020 represents a historical distribution of data readings taken by traffic sensor 123 between 9:00AM and 12:29PM on Mondays over the last 120 days.
  • Histogram 1030 represents a distribution of data readings taken by sensor 123 between 9:00AM and 12:29 on a particular Monday when traffic sensor 123 was functioning properly. It can be visibly discerned that the shape of histogram 1030 resembles that of histogram 1020, given that traffic patterns on a particular Monday would be expected to be similar to traffic patterns on Mondays in general, and the degree of similarity may be computed in various ways, as discussed below.
  • Histogram 1040 represents a distribution of data readings taken by traffic sensor 123 between 9:00AM and 12:29 on a particular Monday when traffic sensor 123 was not functioning properly, and was instead outputting data readings that did not reflect actual traffic flows.
  • the shape of histogram 1040 differs markedly from that of histogram 1020, as is visibly discernible, reflecting the erroneous data readings reported by traffic sensor 123. For example, a large spike in the distribution is visible at bar 1048, which may be indicative of sensor 123 being stuck for at least some of the time between 9:00AM and 12:30PM and reporting a substantial number of identical readings that were not reflective of actual traffic flows.
  • the Kullback-Leibler divergence between two traffic sensor data distributions may be utilized to determine the similarity between the two distributions, although similarities or differences between distributions may be calculated in other manners.
  • the Kullback-Leibler divergence (“DKL") 1036 between the data reading distribution shown in histogram 1020 and the data reading distribution shown in histogram 1030 for the healthy traffic sensor is approximately 0.076
  • the Kullback-Leibler divergence 1046 between the data reading distribution shown in histogram 1020 and the data reading distribution shown in histogram 1040 for the unhealthy traffic sensor is approximately 0.568.
  • the DKL 1036 is significantly smaller than the DKL 1046 (in this case, approximately 13% of DKL 1046), reflecting the fact that histogram 1030 (e.g ., representing the output of traffic sensor 123 while it was functioning properly) is more similar to histogram 1020 ( e.g ., representing the average behavior of traffic sensor 123) than histogram 1040 ( e.g ., representing traffic sensor 123 while it was malfunctioning) is similar to histogram 1020.
  • histogram 1030 e.g ., representing the output of traffic sensor 123 while it was functioning properly
  • histogram 1040 e.g ., representing traffic sensor 123 while it was malfunctioning
  • some instances may use other statistical measures to detect erroneous data readings provided by traffic sensors, such as statistical information entropy, whether instead of or in addition to a similarity measure such as from the Kullback-Leibler divergence.
  • the statistical entropy of a probability distribution is a measure of the diversity of the probability distribution.
  • the statistical entropy 1022 of the distribution shown in histogram 1020 is approximately 2.17
  • the statistical entropy 1032 of the distribution shown in histogram 1030 is approximately 2.14
  • the statistical entropy 1042 of the distribution shown in histogram 1040 is approximately 2.22.
  • the statistical entropy 1042 is greater than both the statistical entropy 1032 and the statistical entropy 1022, reflecting the more chaotic output pattern exhibited by traffic sensor 123 while it was malfunctioning.
  • the difference between two statistical entropy measures may be measured by calculating the entropy difference measure.
  • the entropy difference measure (“EM") 1034 between the distribution shown in histogram 1020 and the distribution shown in histogram 1030 is approximately 0.0010
  • the entropy difference measure 1044 between the distribution shown in histogram 1020 and the distribution shown in histogram 1040 is approximately .0023.
  • the entropy difference measure 1044 is significantly larger than the entropy difference measure 1034 (in this case, more than twice as large), reflecting the greater difference between the statistical entropy of the distribution shown in histogram 1040 and the statistical entropy of the distribution shown in histogram 1020, compared to the difference between the statistical entropy of the distribution shown in histogram 1030 and the statistical entropy of the distribution shown in histogram 1020.
  • various information about a current data reading distribution is provided as input to a sensor health (or data reading reliability) classifier, such as based on a neural network, Bayesian classifier, decision tree, etc.
  • the classifier input information may include, for example, the Kullback-Leibler divergence between a historical data reading distribution for the traffic sensor and the current data reading distribution for the traffic sensor, and the statistical entropy of the current data reading distribution.
  • the classifier then assesses the health of the traffic sensor based on the provided inputs, and provides an output that indicates an unhealthy or healthy sensor.
  • additional information may also be provided as input to the classifier, such as an indication of the time-of-day (e.g ., a time period from 5:00AM to 9:00AM), day or days of week (e.g ., Monday through Thursday, Friday, Saturday or Sunday) corresponding to the time-of-day and/or day-of-week to which the current and historical data reading distributions correspond, size of the mph buckets, etc.
  • Classifiers may be trained by utilizing actual prior data readings, such as those that include indications of traffic sensor state, as illustrated in Figure 10A .
  • unhealthy traffic sensors may be identified without the use of a classifier.
  • a traffic sensor may be determined to be unhealthy if one or more statistical measures are above a predetermined threshold value. For instance, a traffic sensor may be determined to be unhealthy if the Kullback-Leibler divergence between a historical data reading distribution for the traffic sensor and a current data reading distribution for the traffic sensor is above a first threshold value, if the statistical entropy of the current data reading distribution is above a second threshold value, and/or if the entropy difference measure between the current data reading distribution and the historical data reading distribution is above a third threshold.
  • other non-statistical information may be utilized, such as whether the traffic sensor is reporting a sensor state that may be interpreted as healthy or unhealthy.
  • FIG. 3 is a block diagram illustrating an embodiment of a computing system 300 that is suitable for performing at least some of the described techniques, such as by executing an embodiment of a Data Sample Manager system.
  • the computing system 300 includes a central processing unit (“CPU") 335, various input/output (“I/O") components 305, storage 340, and memory 345, with the illustrated I/O components including a display 310, a network connection 315, a computer-readable media drive 320, and other I/O devices 330 (e.g ., keyboards, mice or other pointing devices, microphones, speakers, etc.).
  • CPU central processing unit
  • I/O components 305 storage 340
  • memory 345 with the illustrated I/O components including a display 310, a network connection 315, a computer-readable media drive 320, and other I/O devices 330 (e.g ., keyboards, mice or other pointing devices, microphones, speakers, etc.).
  • I/O components including a display 310, a network
  • various systems are executing in memory 345 in order to perform at least some of the described techniques, including a Data Sample Manager system 350, a Predictive Traffic Information Provider system 360, a Key Road Identifier system 361, a Road Segment Determiner system 362, an RT Information Provider system 363, and optional other systems provided by programs 369, with these various executing systems generally referred to herein as traffic information systems.
  • the computing system 300 and its executing systems may communicate with other computing systems via a network 380 (e.g ., the internet, one or more cellular telephone networks, etc.), such as various client devices 382, vehicle-based clients and/or data sources 384, road traffic sensors 386, other data sources 388, and third-party computing systems 390.
  • a network 380 e.g ., the internet, one or more cellular telephone networks, etc.
  • the Data Sample Manager system 350 obtains various information regarding current traffic conditions and/or previous observed case data from various sources, such as from the road traffic sensors 386, vehicle-based mobile data sources 384 and/or other mobile or non-mobile data sources 388.
  • the Data Sample Manager system 350 then prepares the obtained data for use by other components and/or systems by filtering (e.g ., eliminating data samples from consideration) and/or conditioning (e.g ., correcting errors) the data, and then assesses road traffic conditions such as traffic flow and/or speed for various road segments using the prepared data.
  • the Data Sample Manager system 350 includes a Data Sample Filterer component 352, a Sensor Data Conditioner component 353, a Data Sample Outlier Eliminator component 354, a Data Sample Speed Assessor component 356; a Data Sample Flow Assessor component 358, and an optional Sensor Data Aggregator component 355, with the components 352-358 performing functions similar to those previously described for corresponding components of Figure 1 (such as the Data Sample Filterer component 104, the Sensor Data Conditioner component 105, the Data Sample Outlier Eliminator component 106, the Data Sample Speed Assessor component 107, the Data Sample Flow Assessor component 108, and the optional Sensor Data Aggregator component 110).
  • the components 352-358 performing functions similar to those previously described for corresponding components of Figure 1 (such as the Data Sample Filterer component 104, the Sensor Data Conditioner component 105, the Data Sample Outlier Eliminator component 106, the Data Sample Speed Assessor component 107, the Data Sample Flow Assessor component 108, and the optional Sensor Data Aggregator component 110).
  • the Data Sample Manager system performs its assessment of road traffic conditions in a substantially realtime or near-realtime manner, such as within a few minutes of obtaining the underlying data (which may be itself be obtained in a substantially realtime manner from the data sources).
  • the other traffic information systems 360-363 and 369 and/or the third-party computing systems 390 may then use data provided by the Data Sample Manager system in various ways.
  • the Predictive Traffic Information Provider system 360 may obtain (either directly, or indirectly via a database or storage device) such prepared data to generate future traffic condition predictions for multiple future times, and provide the predicted information to one or more other recipients, such as one or more other traffic information systems, client devices 382, vehicle-based clients 384, and/or third-party computing systems 390.
  • the RT Information Provider system 363 may obtain information about assessed road traffic conditions from the Data Sample Manager system, and make the road traffic condition information available to others (e.g ., client devices 382, vehicle-based clients 384, and/or third-party computing systems 390) in a realtime or near-realtime manner - when the Data Sample Manager system also performs its assessment in such a realtime or near-realtime manner, the recipients of the data from the RT Information Provider system may be able to view and use information about current traffic conditions on one or more road segments based on contemporaneous actual vehicle travel on those road segments (as reported by mobile data sources traveling on those road segments and/or by sensors and other data sources providing information about actual vehicle travel on those road segments).
  • the client devices 382 may take various forms, and may generally include any communication devices and other computing devices capable of making requests to and/or receiving information from the traffic information systems.
  • the client devices may execute interactive console applications (e.g ., Web browsers) that users may utilize to make requests for traffic-related information (e.g ., predicted future traffic conditions information, realtime or near-realtime current traffic conditions information, etc.), while in other cases at least some such 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 information systems.
  • traffic-related information e.g ., predicted future traffic conditions information, realtime or near-realtime current traffic conditions information, etc.
  • the road traffic sensors 386 include multiple sensors that are installed in, at, or near various streets, highways, or other roads, such as for one or more geographic areas. These sensors may 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 flow. In addition, such sensors may include cameras, motion sensors, radar ranging devices, RFID-based devices, and other types of sensors that are located adjacent to or otherwise near a road.
  • the road traffic sensors 386 may periodically or continuously provide measured data readings via wire-based or wireless-based data link to the Data Sample Manager system 350 via the network 380 using one or more data exchange mechanisms (e.g ., push, pull, polling, request-response, peer-to-peer, etc.).
  • data exchange mechanisms e.g ., push, pull, polling, request-response, peer-to-peer, etc.
  • one or more aggregators of such road traffic sensor information may instead obtain the raw data and make that data available to the traffic information systems (whether in raw form or after it is processed).
  • the other data sources 388 include a variety of types of other sources of data that may be utilized by one or more of the traffic information systems to provide traffic-related information to users, customers, and/or other computing systems.
  • Such data sources include map services and/or databases that provide information regarding road networks, such as the connectivity of various roads to one another as well as traffic control information related to such roads (e.g ., the existence and location of traffic control signals and/or speed zones).
  • Other data sources may also include sources of information about events and/or conditions that impact and/or reflect traffic conditions, such as short-term and long-term weather forecasts, school schedules and/or calendars, event schedules and/or calendars, traffic incident reports provided by human operators (e.g ., first responders, law enforcement personnel, highway crews, news media, travelers, etc.), road work information, holiday schedules, etc.
  • sources of information about events and/or conditions that impact and/or reflect traffic conditions such as short-term and long-term weather forecasts, school schedules and/or calendars, event schedules and/or calendars, traffic incident reports provided by human operators (e.g ., first responders, law enforcement personnel, highway crews, news media, travelers, etc.), road work information, holiday schedules, etc.
  • the vehicle-based clients/data sources 384 in this example may each be a computing system and/or communication system located within a vehicle that provides data to one or more of the traffic information systems and/or that receives data from one or more of those systems.
  • the Data Sample Manager system 350 may utilize a distributed network of vehicle-based mobile data sources and/or other user-based mobile data sources (not shown) that provide information related to current traffic conditions for use by the traffic information systems.
  • each vehicle or other mobile data source may have 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, and possibly other information such as speed, direction, elevation and/or other data related to the vehicle's travel, with the geo-location device(s) or other distinct communication devices obtaining and providing such data to one or more of the traffic information systems (e.g ., by way of a wireless link) from time to time.
  • GPS Global Positioning System
  • the geo-location device(s) or other distinct communication devices obtaining and providing such data to one or more of the traffic information systems (e.g ., by way of a wireless link) from time to time.
  • traffic information systems e.g ., by way of a wireless link
  • the vehicle-based clients/data sources 384 may each have a computing system and/or communication system located within a vehicle to obtain information from one or more of the traffic information systems, such as for use by an occupant of the vehicle.
  • the vehicle may contain an in-dash navigation system with an installed Web browser or other console application that a user may utilize to make requests for traffic-related information via a wireless link from one of the traffic information systems, such as the Predictive Traffic Information Provider system and/or RT information Provider system, or instead such requests may be made from a portable device of a user in the vehicle.
  • one or more of the traffic information systems may automatically transmit traffic-related information to such a vehicle-based client device based upon the receipt or generation of updated information.
  • the third-party computing systems 390 include one or more optional computing systems that are operated by parties other than the operator(s) of the traffic information systems, such as parties who receive traffic-related data from one or more of the traffic information systems and who make use of the data in some manner.
  • the third-party computing systems 390 may be systems that receive traffic information from one or more of the traffic information systems, and that 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).
  • the third-party computing systems 390 may be operated by other types of parties, such as media organizations that gather and report traffic conditions to their consumers, or online map companies that provide traffic-related information to their users as part of travel-planning services.
  • the Predictive Traffic Information Provider system 360 may use data prepared by the Data Sample Manager system 350 and other components to generate future traffic condition predictions for multiple future times.
  • the predictions are generated using probabilistic techniques that incorporate various types of input data In order to repeatedly produce future time series predictions for each of numerous road segments, such as In a realtime manner based on changing current conditions for a network of roads in a given geographic area.
  • one or more predictive Bayesian or other models e.g ., decision trees
  • Predicted future traffic condition information may be used in a variety of ways to assist in travel and for other purposes, such as to plan optimal routes through a network of roads based on predictions about traffic conditions for the roads at multiple future times.
  • the Road Segment Determiner system 362 may utilize map services and/or databases that provide information regarding road networks in one or more geographic areas in order to automatically determine and manage information related to the roads that may be used by other traffic information systems.
  • road-related information may include determinations of particular portions of roads to be treated as road segments of interest (e.g ., based on traffic conditions of those road portions and other nearby road portions), as well as automatically generated associations or relationships between road segments in a given road network and indications of other information of interest (e.g ., physical locations of road traffic sensors, event venues, and landmarks; information about functional road classes and other related traffic characteristics; etc.).
  • the Road Segment Determiner system 362 may execute periodically and store the information it produces in storage 340 or a database (not shown) for use by other traffic information systems.
  • the Key Road Identifier system 361 utilizes a road network representing a given geographic area and traffic condition information for that geographic area to automatically identify roads that are of interest for tracking and assessing road traffic conditions, such as for used by other traffic information systems and/or traffic data clients.
  • the automatic identification of a road (or of one or more road segments of the road) as being of interest may be based at least in part on factors such as the magnitude of peak traffic volume or other flow, the magnitude of peak traffic congestion, intra-day variability of traffic volume or other flow, intra-day variability of congestion for the road, inter-day variability of traffic volume or other flow, and/or inter-day variability of congestion for the road.
  • Such factors may be analyzed by way of, for example, principal components analysis, such as by first computing a covariance matrix S of traffic condition information for all roads (or road segments) in a given geographic area, and then computing an Eigen decomposition of the covariance matrix S . In descending order of Eigenvalue, the Eigenvectors of S then represent the combinations of roads (or road segments) that independently contribute most strongly to the variance of the observed traffic conditions.
  • a realtime traffic information provider or presenter system may be provided by the RT Information Provider system, or instead by one or more of the other programs 369.
  • the information provider system may utilize data analyzed and provided by the Data Sample Manager system 350 and/or other components (such as the Predictive Traffic Information Provider system 360) in order to provide traffic information services to consumers and/or business entities that are operating or otherwise utilizing client devices 382, vehicle-based clients 384, third-party computing systems 390, etc., such as to provide data in a realtime or near-realtime manner based at least in part on data samples obtained from vehicles and other mobile data sources.
  • Computing system 300 may be connected to other devices that are not illustrated, including through one or more networks such as the internet or via the Web.
  • a "client” or “server” computing system or device, or traffic information system and/or component 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.
  • the functionality provided by the illustrated system components may be combined in fewer components or distributed in additional components. Similarly, the functionality of some of the illustrated components may not be provided and/or other additional functionality may be available.
  • the system components and data structures can 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).
  • generated data signals e.g., as part of a carrier wave or other analog or digital propagated signal
  • computer-readable transmission mediums including wireless-based and wired/cable-based mediums
  • Such computer program products may also take other forms in other instances. Accordingly, the present invention may be practiced with other computer system configurations.
  • FIG 4 is a flow diagram of an example embodiment of a Data Sample Filterer routine 400 related to the present invention.
  • the routine may be provided by, for example, execution of an embodiment of a Data Sample Filterer component 352 of Figure 3 and/or Data Sample Filterer component 104 of Figure 1 , such as to receive data samples corresponding to roads in a geographic area and to filter data samples that are not of interest for later assessments.
  • the filtered data samples may then subsequently be used in various ways, such as to use the filtered data samples to calculate average speeds for particular road segments of interest and to calculate other traffic flow-related characteristics for such road segments.
  • the routine begins in step 405, where a group of data samples is received for a geographic area for a particular period of time.
  • the routine then optionally generates additional information for some or all of the data samples based on other related data samples. For example, if a particular data sample for a vehicle or other mobile data source lacks information of interest (such as speed and/or heading or orientation for the mobile data source), such information may be determined in conjunction with one or both of the prior and subsequent data samples for the same mobile data source.
  • information from multiple data samples for a particular mobile data source may be aggregated in order to assess additional types of information regarding the data source, such as to assess an activity of the data source over a period of time that spans multiple data samples (e.g ., to determine if a vehicle has been parked for several minutes rather than temporarily stopped for a minute or two as part of the normal flow of traffic, such as at a stop sign or stop light).
  • step 410 the routine continues to steep 415 to attempt to associate each data sample with a road in the geographic area and a particular road segment of that road, although in other embodiments this step may not be performed or may be performed in other manners, such as if at least an initial association of a data sample to a road and/or road segment is instead received in step 405, or instead if the entire routine is performed at a single time for a single road segment such that all of the data samples received in step 405 as a group correspond to a single road segment.
  • the association of a data sample to a road and road segment may be performed in various ways, such as to make an initial association based solely on a geographic location associated with the data sample (e.g ., to associate the data sample with the nearest road and road segment).
  • the association may optionally include additional analysis to refine or revise that initial association - for example, if a location-based analysis indicates multiple possible road segments for a data sample (such as multiple road segments for a particular road, or instead multiple road segments for nearby but otherwise unrelated roads), such additional analysis may use other information such as speed and orientation to affect the association ( e.g ., by combining location information and one or more other such factors in a weighted manner).
  • information about the reported speed of the data sample may be used to assist in associating the data sample with the appropriate road (e.g ., by determining that a data sample with an associated speed of 70 miles per hour is unlikely to originate from a frontage road with a speed limit of 25 miles per hour).
  • additional information about the data sample such as speed and/or orientation may be used to select the most likely road segment of the road for the data sample.
  • step 420 filter any data samples that are not associated with road segments that are of interest for later processing, including data samples (if any) that are not associated with any road segment.
  • certain roads or portions of roads may not be of interest for later analysis, such as to exclude roads of certain functional road classes (e.g ., if the size of the road and/or its amount of traffic is not sufficiently large to be of interest), or to exclude portions of roads such as a freeway ramp or feeder road or collector/distributor road since the traffic characteristics of such road portions are not reflective of the freeway as a whole.
  • step 420 the routine continues to step 425 to determine whether to filter data samples based on activity of the data sources, although in other embodiments such filtering may not be performed or may always be performed.
  • step 430 to perform such filtering, such as to remove data samples corresponding to data sources whose behavior does not reflect the traffic flow activity of interest to be measured (e.g ., to exclude vehicles that are parked with their engines running for an extended period of time, to exclude vehicles that are driving around in a parking lot or parking garage or other small area for an extended period of time, etc.).
  • step 490 the routine continues to step 490 to store the filtered data for later use, although in other embodiments the filtered data could instead be provided directly to one or more clients.
  • the routine then continues to step 495 to determine whether to continue. If so, the routine returns to step 405, and if not continues to step 499 and ends.
  • Figure 5 is a flow diagram of an example embodiment of a Data Sample Outlier Eliminator routine 500 according to the present invention.
  • the routine may be provided by, for example, execution of an embodiment of a Data Sample Outlier Eliminator component 354 of Figure 3 and/or Data Sample Outlier Eliminator component 106 of Figure 1 , such as to eliminate data samples for a road segment that are outliers with respect to the other data samples for the road segment.
  • the routine begins in step 505, where a set of data samples for a road segment and a time period are received.
  • the received data samples may be, for example, filtered data samples obtained from the output of the Data Sample Filterer routine.
  • the routine then optionally separates the data samples into multiple groups to reflect distinct parts of the road segment and/or distinct behaviors. For example, if multiple freeway lanes are included together as part of a single road segment and the multiple lanes include at least one HOV lane and one or more non-HOV lanes, the vehicles in the HOV lane(s) may be separated from vehicles in the other lanes if the traffic flow during the time period is significantly different between the HOV and non-HOV lanes.
  • Such grouping may be performed in various ways, such as by fitting the data samples to multiple curves that each represent typical data sample variability within a particular group of data samples (e.g ., a normal or Gaussian curve). In other embodiments, such grouping may not be performed, such as if the road segment is instead divided such that all of the data samples for the road segment reflect similar behavior (e.g ., if a freeway with an HOV lane and other non-HOV lanes is instead split into multiple road segments).
  • the routine next continues to step 515 to, for each of the one or more groups of data samples (with all of the data samples being treated as a single group if the data sample separating of step 510 is not performed), calculate average traffic condition characteristics for all of the data samples.
  • average traffic condition characteristics may include, for example, an average speed, as well as corresponding statistical information such as a standard deviation from the mean.
  • the routine then continues to step 520 to, for each of the one or more data sample groups, successively perform a leave-one-out analysis such that a particular target data sample is selected to be provisionally left out and average traffic condition characteristics are determined for the remaining traffic condition characteristics.
  • step 525 the routine then optionally performs one or more additional types of outlier analysis, such as to successively leave out groups of two or more target data samples in order to assess their joint effect, although in some embodiments such additional outlier analysis may not be performed.
  • step 590 the routine continues to step 590 to remove data samples that are identified as outliers in steps 520 and/or 525, and stores the remaining data samples for later use. In other embodiments, the routine may instead forward the remaining data samples to one or more clients for use. The routine then continues to step 595 to determine whether to continue. If so, the routine returns to step 505, and if not the routine continues to step 599 and ends.
  • FIG 6 is a flow diagram of an example embodiment of a Data Sample Speed Assessor routine 600 related to the present invention.
  • the routine may be provided by, for example, execution of the Data Sample Speed Assessor component 356 of Figure 3 and/or the Data Sample Speed Assessor component 107 of Figure 1 , such as to assess a current average speed for a road segment during a period of time based on various data samples for the road segment.
  • the routine will perform successive calculations of average speed for the road segment for each of multiple time intervals or windows during the period of time, although in other embodiments each invocation of the routine may instead be for a single time interval ( e.g ., with multiple time intervals assessed via multiple invocations of the routine).
  • a new average speed calculation may be performed every five minutes, such as with 5-minute time intervals (and thus with each time interval not overlapping with prior or successive time intervals), or with 10-minute time intervals (and thus overlapping with adjacent time intervals).
  • the routine begins at step 605, where an indication is received of data samples (e.g ., data samples from mobile data sources and physical sensor data readings) for a road segment for a period of time, or of insufficient data for a road segment for a period of time, although in some embodiments only one of data samples from mobile data sources and from sensor data readings may be received.
  • the received data samples may be, for example, obtained from the output of the Data Sample Outlier Eliminator routine.
  • the indication of insufficient data may be received from the Data Sample Outlier Eliminator routine.
  • the indication of insufficient data may be based on having an insufficient number of data samples, such as when there have been no data samples from mobile data sources associated with the road segment for the period of time and/or when some or all sensor data readings for the road segment are missing or have been detected to be erroneous ( e.g ., by the Sensor Data Conditioner component 105 of Figure 1 ).
  • the routine continues in step 610 to determine whether an indication of insufficient data has been received. If so, the routine continues to step 615, and if not, the routine continues to step 625.
  • step 615 the routine executes an embodiment of the Traffic Flow Estimator routine (described with reference to Figure 14 ) in order to obtain estimated average traffic speed for the road segment for the period of time.
  • step 620 the routine then provides an indication of the estimated average speed.
  • step 625 the routine selects the next time interval or window for which an average speed is to be assessed, beginning with the first time interval.
  • step 630 the routine then calculates a weighted average traffic speed for the data samples within the time interval, with the weighting of the data samples being based on one or more factors.
  • the weighting for each data sample is varied ( e.g ., in a linear, exponential, or step-wise manner) based on the latency of the data sample, such as to give greater weight to data samples near the end of the time interval (as they may be more reflective of the actual average speed at the end of the time interval).
  • the data samples may further be weighted in the illustrated embodiment based on the source of the data, such as to weight data readings from physical sensors differently from data samples from vehicles and other mobile data sources, whether more or less heavily.
  • a data reading from one physical sensor may be weighted differently than a data reading from another physical sensor, such as to reflect available information about the sensors (e.g ., that one of the physical sensors is intermittently faulty or has a less accurate data reading resolution than another sensor), and a data sample from one vehicle or other mobile data source may similarly be weighted differently from that of another such vehicle or mobile data source based on information about the mobile data sources.
  • Other types of factors that in some embodiments may be used in the weightings include confidence values or other estimates of the possible error in a particular data sample, a degree of confidence that a particular data sample should be associated with a particular road segment, etc.
  • step 630 the routine continues to step 635 to provide an indication of the average calculated traffic speed for the time interval, such as to store the information for later use and/or to provide the information to a client.
  • step 640 the routine then optionally obtains additional data samples for the time period that have become available subsequent to the receipt of information in step 605. It is then determined in step 645 whether more time intervals are to be calculated for the time period, and if so the routine returns to step 625. If there are instead no more time intervals, or after step 620, the routine continues to step 695 to determine whether to continue. If so, the routine returns to step 605, and if not continues to step 699 and ends.
  • Figure 7 is a flow diagram of an example embodiment of a Data Sample Flow Assessor routine 700 related to the present invention.
  • the routine may be provided by, for example, execution of an embodiment of a Data Sample Flow Assessor component 358 of Figure 3 and/or Data Sample Flow Assessor component 108 of Figure 1 , such as to assess traffic condition flow characteristics other than average speed for a particular road segment during a particular period of time.
  • the flow characteristics to be assessed include a total volume of vehicles (or other mobile data sources) arriving at or present on a particular road segment during a period of time, and a percentage occupancy for the road segment during the period of time to reflect the percentage of time that a point on or area of the road segment is covered by a vehicle.
  • the routine begins at step 705, where an indication is received of data samples for a road segment for a period of time and an average speed for the road segment during the period of time, or of insufficient data for a road segment for a period of time.
  • the data samples may be obtained from, for example, output of the Data Sample Outlier Eliminator routine, and the average speed may be obtained from, for example, output of the Data Sample Speed Assessor routine.
  • the indication of insufficient data may be obtained from, for example, output of the Data Sample Outlier Eliminator routine.
  • the indication of insufficient data may be based on having an insufficient number of data samples, such as when there have been no data samples from mobile data sources associated with the road segment for the period of time and/or when some or all sensor data readings for the road segment are missing or have been detected to be erroneous ( e.g ., by the Sensor Data Conditioner component 105 of Figure 1 ).
  • the routine then continues in step 706 to determine whether an indication of insufficient data has been received. If so, the routine continues to step 750, and if not, the routine continues to step 710.
  • step 750 the routine executes an embodiment of the Traffic Flow Estimator routine (described with reference to Figure 14 ) in order to obtain estimated total volume and occupancy for the road segment for the period of time.
  • step 755 the routine then provides an indication of the estimated total volume and occupancy.
  • the routine determines a number of vehicles (or other mobile data sources) that provided the data samples, such as by associating each data sample with a particular mobile data source.
  • the routine then probabilistically determines the most likely arrival rate to the road segment of the vehicles providing the data samples, based in part on the determined number of vehicles. In some embodiments, the probabilistic determination may further use information about the a priori probability of the number of such vehicles and the a priori probability of a particular arrival rate.
  • step 730 the routine then infers the total volume of all vehicles passing through the road segment during the period of time, such as based on the determined number of vehicles and information about what percentage of the total number of vehicles are vehicles that provide data samples, and further assesses a confidence interval for the inferred total volume.
  • step 740 the routine then infers the percentage occupancy for the road segment during the period of time based on the inferred total volume, the average speed, and an average vehicle length. Other types of traffic flow characteristics of interest may similarly be assessed in other embodiments.
  • the routine then continues to step 790 to provide indications of the inferred total volume and the inferred percentage occupancy. After steps 755 or 790, if it is then determined in step 795 to continue; the routine returns to step 705, and if not continues to step 799 and ends.
  • FIG 11 is a flow diagram of an example embodiment of a Sensor Data Reading Error Detector routine 1100 related to the present invention.
  • the routine may be provided by, for example, execution of the Sensor Data Conditioner component 353 of Figure 3 and/or the Sensor Data Conditioner component 105 of Figure 1 , such as to determine the health of one or more traffic sensors.
  • the routine is performed at various times of day to determine the health of one or more traffic sensors, based on traffic sensor data readings recently obtained during an indicated time period.
  • data being output by a traffic sensor for one or more of various types of traffic conditions measures may be analyzed by the routine In various embodiments, such as traffic speed, volume, occupancy, etc.
  • data for at least some of traffic conditions may be measured and/or aggregated in various ways, such as at various levels of granularity (e.g ., 5mph buckets of groups of data for speed information), and the routine may in some embodiments analyze data for a particular traffic sensor at each of one or more levels of granularity (or other level of aggregation) for each of one or more traffic conditions measures.
  • levels of granularity e.g ., 5mph buckets of groups of data for speed information
  • the routine may in some embodiments analyze data for a particular traffic sensor at each of one or more levels of granularity (or other level of aggregation) for each of one or more traffic conditions measures.
  • the routine begins at step 1105 and receives an indication of one or more traffic sensors and of a selected time category (e.g ., the most recent time category, if the routine executes after each time category to provide results in a near-realtime manner, or one or more prior time categories selected for analysis), although in other embodiments multiple time categories may instead be indicated.
  • a selected time category e.g ., the most recent time category, if the routine executes after each time category to provide results in a near-realtime manner, or one or more prior time categories selected for analysis
  • time may be modeled by way of time categories that each include a time-of-day category (e.g ., 12:00AM to 5:29AM and 7:30PM to 11:59PM, 5:30AM to 8:59AM, 9:00AM to 12:29PM, 12:30PM to 3:59PM, 4:00PM to 7:29PM, and 12:00AM to 11:59PM) and/or a day-of-week category (e.g ., Monday through Thursday, Friday, Saturday and Sunday, or instead with Saturday and Sunday grouped together).
  • time-of-day category e.g ., 12:00AM to 5:29AM and 7:30PM to 11:59PM, 5:30AM to 8:59AM, 9:00AM to 12:29PM, 12:30PM to 3:59PM, 4:00PM to 7:29PM, and 12:00AM to 11:59PM
  • day-of-week category e.g ., Monday through Thursday, Friday, Saturday and Sunday, or instead with Saturday and Sunday grouped together.
  • time categories may be selected in various ways in various embodiments, including to reflect time periods during which traffic is expected to have similar characteristics (e.g ., based on commuting times and patterns, or other consistent activities that affect traffic), such as to group evening and early morning hours together if traffic is typically relatively sparse during those times.
  • time categories may be selected to differ for different traffic sensors (e.g ., by geographic area, road, individual sensor, etc.), whether manually or in an automated manner by analyzing historical data to determine time periods that have similar traffic flow characteristics.
  • the routine then performs a loop in which it analyzes traffic sensor data readings from each of the indicated one or more traffic sensors for the indicated time categories in order to determine the traffic sensor health status of each of the traffic sensors during that time category.
  • the routine selects the next traffic sensor of the indicated one or more traffic sensors, beginning with the first, and selects the indicated time category (or, if multiple time categories were instead indicated in step 1105, the next combination of traffic sensor and indicated time category).
  • the routine retrieves an average historical data reading distribution for the traffic sensor during the selected time category.
  • the historical data reading distribution may be based on data readings provided by the traffic sensor during the selected time category (e.g ., between 4:00PM and 7:29PM on days of the week that include Monday through Thursday) over an extended time period, such as the last 120 days or a recent 120 day period).
  • step 1120 the routine determines a target traffic sensor data distribution for the selected traffic sensor and selected time category.
  • step 1125 the routine then determines the similarity of the target traffic sensor data reading distribution and the historical traffic sensor data reading distribution. As described in more detail elsewhere, in some embodiments, such a similarity measure may be determined by calculating the Kullback-Leibler divergence between the target traffic sensor data reading distribution and the historical traffic sensor data reading distribution.
  • step 1130 the routine next determines the information entropy of the target traffic sensor data reading distribution, as discussed in greater detail elsewhere.
  • the routine next assesses the health of the selected traffic sensor for the selected time category by using various information to perform a health classification (e.g ., an indication of "healthy” or “unhealthy", or a value on a "health” scale such as from 1 to 100), which in this example includes the determined similarity, determined entropy, and the selected time category (e.g ., the selected time-of-day category, such as 4:00PM to 7:29PM, and/or the selected day-of-week category, such as Monday to Thursday).
  • a health classification e.g ., an indication of "healthy” or “unhealthy", or a value on a "health” scale such as from 1 to 100
  • the selected time category e.g ., the selected time-of-day category, such as 4:00PM to 7:29PM, and/or the selected day-of-week category, such as Monday to Thursday.
  • other types of information could be used, such as an indication of a degree of granularity of the data being measured (
  • the routine determines the traffic sensor health status for the selected traffic sensor and selected time category (in this example as healthy or unhealthy) based on the assessed traffic sensor health and/or other factors.
  • the health status for a traffic sensor may be determined to be healthy whenever the traffic sensor health for the selected time category is assessed as healthy in step 1135.
  • the health status for the traffic sensor may be determined to be unhealthy whenever the traffic sensor health for the selected time category is assessed as unhealthy ( e.g ., in step 1135), and the selected time category has an associated time-of-day category that covers a sufficiently large time period ( e.g ., at least 12 or 24 hours).
  • information about related time categories may be retrieved and used, such as to classify traffic sensor health over a longer period of time (e.g ., a day).
  • Such logic may reduce the risk of a false negative determination of sensor health status (e.g ., determining the traffic sensor health status as unhealthy when in fact the traffic sensor is healthy) based on temporary unusual traffic patterns that the traffic sensor is accurately reporting.
  • false negative determinations may occur due to substantial intra-day variability in data readings due to external factors (e.g ., traffic accidents, weather incidents, etc.).
  • An automobile accident occurring at or near a particular traffic sensor may result in that traffic sensor providing atypical and erratic data readings for a relatively short time period ( e.g ., one to two hours).
  • a determination of sensor health status is solely based on data readings obtained primarily during the time of the disturbance caused by the traffic accident, a false negative determination will likely result.
  • false positive determinations e.g ., determining the traffic sensor health as healthy when in fact it is unhealthy
  • Some embodiments may effect such differential logic by executing the illustrated routine multiple times per day with time categories reflective of shorter time periods (e.g ., executing the routine every three hours with a time category having a time-of-day category extending over the previous three hours) and at least once per day with a time category reflective of the entire previous day (e.g ., executing the routine at midnight with a time category having a time-of-day category extending over the previous 24 hours).
  • the determination of sensor health status may be based on other factors, such as whether a sufficient number of data readings can be obtained for the selected time category (e.g ., because the traffic sensor is intermittently reporting data readings) and/or based on indications of sensor state provided by the traffic sensor ( e.g ., that the traffic sensor is stuck).
  • the routine provides the determined traffic sensor health status.
  • the traffic sensor health status may be stored (e.g ., in a database or file system) for later use by other components (e.g ., the Sensor Data Aggregator component 110 of Figure 1 ) and/or directly provided to other components (e.g ., a Data Sample Outlier Eliminator component).
  • the routine determines whether there are more traffic sensors (or combinations of traffic sensors and time categories) to process. If so, the routine continues to step 1110 to continue, and if not continues to step 1155 to perform other actions as appropriate.
  • Such other actions may include, for example; periodically (e.g ., once per day, once per week, etc.) recalculating historical data reading distributions (e.g ., for the last 120 days) for each of one or more time categories for each of multiple traffic sensors.
  • the routine may continue to provide accurate traffic sensor health status determinations in the face of gradually changing traffic conditions (e.g ., due to the initiation or completion of road construction projects).
  • the routine continues to step 1199 and returns.
  • FIG 12 is a flow diagram of an example embodiment of a Sensor Data Reading Error Corrector routine 1200 related to the present invention.
  • the routine may be provided by, for example, execution of the Sensor Data Conditioner component 353 of Figure 3 and/or the Sensor Data Conditioner component 105 of Figure 1 , such as to determine corrected data readings for one or more traffic sensors associated with a road segment.
  • this routine may be executed periodically ( e.g ., every 5 minutes) to correct data readings for traffic sensors that have been identified as unhealthy by the Sensor Data Reading Error Corrector routine.
  • the routine may be executed on demand, such as by the Sensor Data Aggregator routine, in order to obtain corrected data readings for a particular road segment, or instead may not be used in various circumstances.
  • data analysis and correction may be performed more generally by determining if all data samples (e.g ., from multiple data sources, such as of multiple types that may include traffic sensors and one or more distinct types of mobile data sources) for a particular road segment provide sufficient data to analyze traffic flow conditions for that road segment, and if so to not perform correction of data from individual traffic sensors.
  • data samples e.g ., from multiple data sources, such as of multiple types that may include traffic sensors and one or more distinct types of mobile data sources
  • the routine begins at step 1205, where it receives an indication of a road segment with which one or more traffic sensors are associated (e.g ., based on results from the Sensor Data Reading Error Detector routine that one or more of the associated traffic sensors have been classified as unhealthy), and optionally of one or more time categories to be processed (e.g ., time categories during which at least one of the associated traffic sensors have been classified as at least potentially being unhealthy).
  • one or more traffic sensors of interest may be indicated in other manners, such as by directly receiving indications of one or more traffic sensors.
  • the routine performs a loop in which it processes unhealthy traffic sensors in the indicated road segment to determine and provide corrected data readings for those traffic sensors during one or more time categories (e.g ., the time categories indicated in step 1205).
  • step 1210 the routine selects the next unhealthy traffic sensor in the indicated road segment, beginning with the first.
  • the routine also selects a time category to use, such as one of one or more time categories indicated in step 1205, by selecting one of one or more time categories during which the traffic sensor was previously designated to be unhealthy, etc.
  • step 1215 the routine determines whether there are sufficient other traffic sensors in the indicated road segment that are healthy and may be used to assist in the correction of the readings for the unhealthy traffic sensor for the selected time category.
  • This determination may be based on whether there are at least a predetermined number (e.g ., at least two) and/or a predetermined percentage (e.g ., at least 30%) of healthy traffic sensors in the indicated road segment during the selected time category, and may further consider the relative location of the healthy traffic sensors in the indicated road segment ( e.g ., neighboring or otherwise nearby traffic sensors may be preferred to traffic sensors that are farther away from the unhealthy traffic sensor). If it is determined in step 1215 that there are sufficient healthy traffic sensors, the routine continues to step 1220, where it determines a corrected data reading for the unhealthy traffic sensor based on data readings from other healthy traffic sensors in the road segment for the selected time category.
  • a predetermined number e.g ., at least two
  • a predetermined percentage e.g ., at least 30%
  • a corrected data reading may be determined in various ways, such as by calculating the average of two or more data readings obtained from healthy traffic sensors in the indicated road segment for the selected time category.
  • all healthy traffic sensors may be used for the averaging, while in other embodiments only selected healthy traffic sensors may be used. For example, if a predetermined percentage (e.g ., at least 30%) of traffic sensors in the indicated road segment are healthy during the selected time category, all healthy traffic sensors may be used for the averaging, and otherwise only a predetermined number ( e.g ., at least two) of the nearest healthy traffic sensors may be used.
  • step 1215 If it is instead determined in step 1215 that there are not sufficient healthy traffic sensors in the indicated road segment for the selected time category, the routines continues to step 1225, where it attempts to determine a corrected data reading for the unhealthy traffic sensor based on other information related to the traffic sensor and/or the road segment.
  • information may include predicted traffic condition information for the road segment and/or unhealthy traffic sensor, forecast traffic condition information for the road segment and/or unhealthy traffic sensor, and/or historical average traffic condition information for the road segment and/or the unhealthy traffic sensor.
  • Various logic may be implemented to reflect the relative reliability of various types of information.
  • predicted traffic condition information may be used in preference to ( e.g ., so long as it is available) to forecast traffic condition information, which may in turn be used in preference to historical average traffic condition information. Additional details related to predicting and forecasting future traffic flow conditions are available in U.S. Patent Application No. 11/367,463, filed March 3, 2006 and entitled "Dynamic Time Series Prediction Of Future Traffic Conditions," which is hereby incorporated by reference in its entirety.
  • steps 1215 and 1225 may not be performed, such as if the data reading correction in step 1220 is always performed based on the best data that is available from other healthy traffic sensors during the selected time category and/or related time categories.
  • the data reading correction may be based on all wealthy traffic sensors in the indicated road segment for the selected time category if at least a predetermined percentage (e.g ., at least 30%) of those traffic sensors are healthy, or otherwise on the nearest neighbor healthy traffic sensors in the indicated and/or nearby road segments during the selected time category and/or related time categories.
  • a predetermined percentage e.g ., at least 30%
  • the routine proceeds to step 1230 and provides the determined traffic sensor data reading for use as a corrected reading for the traffic sensor during the selected time category.
  • the determined traffic sensor data reading may be stored ( e.g ., in a database or file system) for later use by other components ( e.g ., the Sensor Data Aggregator component 110 of Figure 1 ).
  • the routine determines whether there are additional combinations of traffic sensor and time category to process. If so, the routine returns to step 1210, and if not proceeds to step 1299 and returns.
  • Figure 13 is a flow diagram of an example embodiment of a Sensor Data Reading Aggregator routine 1300 related to the present invention.
  • the routine may be provided by, for example, execution of the Sensor Data Aggregator component 355 of Figure 3 and/or the Sensor Data Aggregator component 110 of Figure 1 , such as to determine and provide traffic condition information for multiple traffic sensors during a particular time category or other time period, such as for multiple traffic sensors associated with a particular road segment.
  • the routine is performed for particular road segments, but in other embodiments may aggregate information from other types of groups of multiple traffic sensors.
  • this routine may provide traffic condition information that is complementary to information provided by other routines that perform assessments of traffic condition information (e.g ., the Data Sample Flow Assessor routine), such as to provide traffic condition information in situations in which other routines cannot provide accurate assessments (e.g ., due to insufficient data).
  • assessments of traffic condition information e.g ., the Data Sample Flow Assessor routine
  • the routine begins at step 1305 and receives an indication of one or more road segments and of one or more time categories or other time periods.
  • the routine selects the next road segment of the one or more indicated road segments, beginning with the first.
  • the routine obtains some or all available traffic sensor data readings taken during the indicated time period(s) by all traffic sensors associated with the road segment. Such information may be obtained from, for example, the Sensor Data Conditioner component 105 of Figure 1 and/or the Sensor Data Conditioner component 353 of Figure 1 .
  • the routine may in some cases obtain traffic sensor data readings for traffic sensors determined to be healthy and/or corrected traffic sensor data readings for traffic sensors determined to be unhealthy, such as those provided or determined by the Sensor Data Reading Error Corrector routine of Figure 12 .
  • the routine then aggregates the obtained data readings In one or more of various ways, such as to determine average speed, volume, and/or occupancy for the road segment during the indicated time period(s).
  • the average speed may, for example, be determined by averaging data readings that reflect the speed of vehicles passing over one or more traffic sensors.
  • the traffic volume may be determined with reference to data readings that report vehicle counts. For example, given a loop sensor that reports a cumulative number of vehicles that have passed over the sensor since the sensor was activated, a traffic volume may be inferred simply by subtracting two data readings obtained during the indicated time period and dividing the result by the time interval between the data readings.
  • the density may be determined based on the determined average speed, volume, and an average vehicle length, as described in more detail elsewhere.
  • data readings may be weighted In various ways ( e.g ., by age), such that more recent data readings have a greater impact than older data readings on an average flow determination.
  • step 1325 the routine then determines whether there are more road segments (or other groups of multiple traffic sensors) to process. If so, the routine returns to step 1310, and otherwise proceeds to step 1330 to provide the determined traffic flow information.
  • the determined flow information may be stored ( e.g ., in a database or file system) for later provision to traffic data clients 109 of Figure 1 and/or the RT Information Provider system 363 of Figure 3 .
  • the routine continues to step 1339 and returns.
  • FIG 14 is a flow diagram of an example embodiment of a Traffic Flow Estimator routine 1400 related to the present invention.
  • the routine may be provided by, for example, execution of a Traffic Flow Estimator component (not shown), such as to estimate various types of traffic flow information for a road segment in various ways.
  • the routine may be Invoked by the Data Sample Speed Assessor routine of Figure 6 to obtain estimates of average speed and/or by the Data Sample Flow Assessor routine of Figure 7 to obtain estimates of volume and/or occupancy, such as in situations when those routines are unable to obtain sufficient data for otherwise accurately performing their respective assessments.
  • the routine begins at step 1405 and receives an indication of a road segment, one or more time categories or other time periods, and of one or more types of traffic flow information, such as speed, volume, density, occupancy, etc.
  • the routine determines whether to estimate the indicated type of traffic flow information based on one or more related road segments, such as based on whether such road segments have accurate information for the one or more types of traffic flow information during the one or more indicated time periods.
  • Related road segments may be identified in various ways.
  • information about road segments may include information about relationships between road segments, such as a first road segment typically having similar traffic patterns to a second (e.g ., neighboring) road segment, such that traffic flow information for the second road segment may be utilized to estimate traffic flow on the first road segment.
  • such relationships may be determined automatically, such as based on a statistical analysis of the respect traffic flow patterns on the two road segments ( e.g ., in a manner similar to that discussed previously with respect to identifying similar data distributions for a given traffic sensor at different times, but instead analyzing similarity between two or more different traffic sensors, such as at the same time), whether an analysis that was previously and/or dynamically performed.
  • one or more neighboring road segments may be selected as being related for an indicated road segment without any determination of a particular relationship between road segments having been performed, If it is determined to estimate traffic flow information based on related road segments, the routine proceeds to step 1415 and estimates value(s) for the indicated type(s) of traffic flow information based on the same type(s) of traffic flow information for the one or more related road segments. For example, average speed of the road segment may be determined based on the average traffic speed of one or more neighboring road segments ( e.g ., by using the traffic speed from one neighboring road segment, or averaging the traffic speeds from two or more neighboring road segments).
  • step 1410 determines whether to estimate traffic flow information for the indicated road segment during the one or more indicated time periods based on predicted information for the indicated road segment and indicated time periods.
  • predicted information may only be available under certain conditions, such as if predictions are repeatedly made for multiple future times ( e.g . every 15 minutes for the next three hours) while accurate current data is available. As such, if accurate input data for generating predictions becomes available for an extended time ( e.g ., for more than three hours), it may not be possible to obtain future traffic condition information predictions that may be utilized by this routine.
  • step 1420 If it is determined in step 1420 to estimate traffic flow information based on predicted information, the routine proceeds to step 1425 and estimates the indicated type(s) of traffic flow information for the indicated road segment and indicated time period(s) based on predicted information obtained from, for example, the Predictive Traffic Information Provider system 360 of Figure 3 . Additional details related to predicting and forecasting future traffic flow conditions are available in U.S. Patent Application No. 11/367,463, filed March 3, 2006 and entitled "Dynamic Time Series Prediction Of Future Traffic Conditions," which is hereby incorporated by reference in its entirety.
  • step 1420 If it is instead determined in step 1420 not to estimate traffic flow information for the indicated segment based on predicted information (e.g ., due to that information not being available), the routine continues to step 1430 and determines whether to estimate traffic flow information for the indicated road segment during the one or more indicated time periods based on forecast information for that road segment and time period(s).
  • traffic conditions may be forecast for future times beyond those for which traffic conditions are predicted, such as in a manner that does not use at least some current condition information.
  • predicted information is not available (e.g ., because accurate input data for generating predictions has not been available for more than three hours), it still may be possible to utilize forecast information, such as information generated significantly in advance.
  • step 1430 If it is determined in step 1430 to estimate traffic flow information based on forecast information, the routine proceeds to step 1435 and estimates the indicated type(s) of traffic flow information for the indicated road segment and time period(s) based on forecast information obtained from, for example, the Predictive Traffic Information Provider system 360.
  • step 1430 If it is instead determined in step 1430 not to estimate traffic flow information for the indicated road segment based on forecast information (e.g ., due to the information not being available), the routine continues to step 1440 and estimates the indicated type(s) of traffic flow information for the indicated road segments and time period(s) based on historical average flow information for the indicated road segment ( e.g ., for the same or corresponding time periods, such as based on time categories that include a time-of-day category and/or day-of-week category).
  • the routine may use historical average flow information for the indicated road segment. Additional details related to generating historical average flow information are available in U.S. Patent Application No. (Attorney Docket Number 480234.410P1), filed concurrently and entitled "Generating Representative Road Traffic Flow Information From Historical Data," which is hereby incorporated by reference in its entirety.
  • step 1445 provides estimated traffic flow information of the indicated type(s) for the indicated road segment and indicated time period(s).
  • the provided information may, for example, be returned to a routine (e.g ., the Data Sample Flow Assessor routine) that called the routine and/or be stored ( e.g ., in a database or file system) for later utilization.
  • a routine e.g ., the Data Sample Flow Assessor routine
  • the routine continues to step 1499 and returns.
  • Figures 9A-9C illustrate examples of actions of mobile data sources in obtaining and providing information about road traffic conditions.
  • Information about road traffic conditions may be obtained from mobile devices (whether vehicle-based devices and/or user devices) in various ways, such as by being transmitted using a wireless link (e.g ., satellite uplink, cellular network, WI-FI, packet radio, etc.) and/or physically downloaded when the device reaches an appropriate docking or other connection point (e.g ., to download information from a fleet vehicle once it has returned to its primary base of operations or other destination with appropriate equipment to perform the information download).
  • a wireless link e.g ., satellite uplink, cellular network, WI-FI, packet radio, etc.
  • an appropriate docking or other connection point e.g ., to download information from a fleet vehicle once it has returned to its primary base of operations or other destination with appropriate equipment to perform the information download.
  • While information about road traffic conditions at a first time that is obtained at a significantly later second time provides various benefits (e.g ., verifying predictions about the first time, for use as observed case data in later improving a prediction process, etc.), such as may be the case for information that is physically downloaded from a device, such road traffic condition information provides additional benefits when obtained in a realtime or near-realtime manner.
  • mobile devices with wireless communication capabilities may provide at least some acquired information about road traffic conditions on a frequent basis, such as periodically (e.g ., every 30 seconds, 1 minute, 5 minutes, etc.) and/or when a sufficient amount of acquired information is available (e.g ., for every acquisition of a data point related to road traffic condition information; for every N acquisitions of such data, such as where N is a configurable number; when the acquired data reaches a certain storage and/or transmission size; etc.).
  • a sufficient amount of acquired information is available (e.g ., for every acquisition of a data point related to road traffic condition information; for every N acquisitions of such data, such as where N is a configurable number; when the acquired data reaches a certain storage and/or transmission size; etc.).
  • such frequent wireless communications of acquired road traffic condition information may further be supplemented by additional acquired road traffic condition information at other times (e.g ., upon a subsequent physical download from a device, via less-frequent wireless communications that contain a larger amount of data, etc.), such as to include additional data corresponding to each data point, to include aggregated information about multiple data points, etc.
  • a particular wireless link e.g ., satellite uplink
  • a mobile device may temporarily lose an ability to transmit data over a wireless link, such as due to a lack of wireless coverage in an area of the mobile device ( e.g ., due to no nearby cellphone receiver station), due to other activities being performed by the mobile device or a user of the device, or due to a temporary problem with the mobile device or an associated transmitter.
  • At least some such mobile devices may be designed or otherwise configured to store multiple data samples (or to cause such multiple data samples to be stored on another associated device) so that at least some information for the multiple data samples may be transmitted together during a single wireless transmission.
  • at least some mobile devices are configured to store acquired road traffic condition information data samples during periods when the mobile device is unable to transmit data over a wireless link (e.g ., such as for a mobile device that typically transmits each data sample individually, such as every 30 seconds or 1 minute), and to then transmit those stored data samples together (or a subset and/or aggregation of those samples) during the next wireless transmission that occurs.
  • Some mobile devices may also be configured to perform wireless transmissions periodically (e.g ., every 15 minutes, or when a specified amount of data is available to be transmitted), and in at least some embodiments may further be configured to acquire and store multiple data samples of road traffic condition information (e.g ., at a predetermined sampling rate, such as 30 seconds or a minute) over the time interval between wireless transmissions and to then similarly transmit those stored data samples together (or a subset and/or aggregation of those samples) during the next wireless transmission.
  • a predetermined sampling rate such as 30 seconds or a minute
  • the road traffic condition information obtained from the transmissions still provides near-realtime information.
  • additional information may be generated and provided by a mobile device based on multiple stored data samples. For example, if a particular mobile device is able to acquire only information about a current instant position during each data sample, but is not able to acquire additional related information such as speed and/or direction, such additional related information may be calculated or otherwise determined based on multiple subsequent data samples.
  • Figure 9A depicts an example area 955 with several interconnected roads 925, 930, 935 and 940, and a legend indication 950 indicates the direction of North for the roads (with roads 925 and 935 running in a north-south direction, and with roads 930 and 940 running in an east-west direction). While only a limited number of roads are indicated, they may represent a large geographic area, such as interconnected freeways over numerous miles, or a subset of city streets spanning numerous blocks.
  • a mobile data source e.g ., a vehicle, not shown
  • the mobile data source acquires and transmits a first data sample at location 945a (as indicated in this example by an asterisk "*"), acquires and transmits a second data sample 15 minutes later at location 945b, and acquires and transmits a third data sample a total of 30 minutes later at location 945c.
  • each data sample includes an indication of current position (e.g ., in GPS coordinates), current direction (e.g ., northbound), current speed (e.g ., 30 miles per hour), and current time, as represented for the 945a transmission using data values P a , D a , S a and T a , and may optionally include other information as well (e.g ., an identifier to indicate the mobile data source). While such acquired and provided current traffic conditions information provides some benefit, numerous details cannot be determined from such data, including whether the route from location 945b to 945c occurred in part along road 930 or along 940. Moreover, such sample data does not allow, for example, portions of road 925 between locations 945a and 945b to be treated as distinct road segments for which distinct traffic conditions can be reported and predicted.
  • Figure 9B depicts an example 905 with a mobile data source traveling over the interconnected roads 925, 930, 935 and 940 from location 945a to 945c over a period of 30 minutes, and with the mobile data source transmitting information about traffic conditions each 15 minutes (as indicated by the asterisks shown at locations 945a, 945b and 945c).
  • the mobile data source is configured to acquire and store data samples every minute, with a subsequent transmission including data from each of the data samples during the prior 15 minutes.
  • the mobile data source acquires a set 910b of 15 data samples 910b1-910b15, with each data sample indicated in this example with an arrow pointed in the direction of the mobile data source at the time of the data sample.
  • each data sample similarly includes an indication of current position, current direction, current speed, and current time, and the subsequent transmission at location 945b includes those data values for each of the data samples 910b.
  • the mobile data source acquires 15 data samples 910c1-910c15, and the subsequent transmission at location 945c includes the acquired data values for each of those 15 data samples.
  • various additional information may be obtained. For example, it is now easily determined that the route from location 945b to 945c occurred in part along road 930 rather than road 940, allowing corresponding traffic condition information to be attributed to road 930.
  • particular data samples and their adjacent data samples may provide various information about smaller sections of roads, such as to allow road 925 between locations 945a and 945b to be represented as, for example, up to 15 distinct road segments ( e.g ., by associating each data sample with a distinct road segment) that each has potentially distinct road traffic conditions.
  • the average speed for data samples 910b1-910b6 is approximately static (since the data samples are approximately equally spaced), that the average speed increased for data samples 910b7 and 910b8 (since the data samples correspond to locations that are farther part, reflecting that greater distance was traveled during the given 1-minute interval between data samples for this example), and that the average speed decreased for data samples 910b11-910b15. While the data samples in this example provide information about such speed directly, in other embodiments such speed information may be derived from data sample information that includes only current position.
  • Figure 9C depicts a third example 990 with a mobile data source traveling over a portion of the interconnected roads from location 965a to 965c over a period of 30 minutes, and with the mobile data source transmitting information about traffic conditions each 15 minutes (as indicated by the asterisks shown at locations 965a, 965b and 965c).
  • the mobile data source is configured in this example to acquire and store data samples every minute, with a subsequent transmission including data from each of at least some of the data samples during the prior 15 minutes. Accordingly, as the mobile data source travels between location 965a and 965b, the mobile data source acquires a set 960b of 15 data samples 960b1-960b15.
  • the mobile data source has stopped for approximately 9 minutes at a location to the side of road 925 ( e.g ., to stop at a coffee shop).
  • the transmission may in some embodiments include all of the information for all of the data samples, or may instead omit at least some such information (e.g ., to omit information for data samples 960b6-960b12, since in this situation they do not provide additional useful information if it is known that the mobile data source remained immobile between data samples 960b5 and 960b13).
  • the subsequent transmission may be delayed until 15 data samples to be transmitted are available (e.g ., if the periodic transmissions are performed based on amount of data to send rather than time).
  • the mobile data source acquires data samples 960c13 and 960c14 in an area in which wireless communications are not currently available (as indicated in this example, with open circles rather than arrows).
  • these data samples would be lost, but in this example are instead stored and transmitted along with the other data samples 960c1-960c12 and 960c15 at location 965c.
  • a mobile data source may further temporarily lose the ability to obtain one or more data samples using a primary means of data acquisition (e.g ., if a mobile data source loses the ability to obtain GPS readings for a few minutes) - if so, the mobile data source may in some embodiments report the other obtained data samples without further action (e.g ., such as to allow the recipient to interpolate or otherwise estimate those data samples if so desired), while in other embodiments may attempt to obtain data samples in other manners ( e.g ., by using a less accurate mechanism to determine location, such as cellphone tower triangulation, or by estimating current location based on a prior known location and subsequent average speed and heading, such as via dead reckoning), even if those data samples have less precision or accuracy (e.g ., which may be reflected by including a lesser degree of confidence or higher degree of possible error to those data samples, or by otherwise including an indication of how those and/or other data samples were generated).
  • a primary means of data acquisition e.g .,
  • each of Figures 9B and 9C are illustrated for a single vehicle or other mobile data source for the purposes of clarity, in other embodiments the multiple data samples for a particular mobile data source may not be used to determine a particular route taken by that mobile data source, and more generally may not even be associated with each other ( e.g ., if the source of each mobile data sample is anonymous or otherwise undifferentiated from other sources).
  • a recipient may not be provided in some embodiments with identifying data related to the source of the mobile data samples and/or with indications that the multiple data samples are from the same mobile data source (e.g ., based on a design decision to increase privacy related to the mobile data sources).
  • multiple mobile data sources are used together to determine road condition information of interest, such as to use multiple data samples from all mobile data sources for a particular road segment (or other portion of a road) to determine aggregate information for that road segment.
  • road condition information of interest such as to use multiple data samples from all mobile data sources for a particular road segment (or other portion of a road) to determine aggregate information for that road segment.
  • numerous unrelated mobile data sources may each provide one or more data samples related to their own travel on a particular road segment during that time period, and if each such data sample includes speed and direction information (for example), an average aggregate speed may be determined for that time period and that road segment for all mobile data sources that are generally moving in the same direction, such as in a manner similar to a road sensor that aggregates information for multiple vehicles passing the sensor.
  • a particular data sample may be associated with a particular road segment in various ways, such as by associating the data sample location with the road (or road segment) having the nearest location (whether for any road, or only for roads meeting specified criteria, such as being of one or more indicated functional road classes) and then selecting the appropriate road segment for that road, or by using an indication provided by a mobile data source along with a data sample of an associated road (or road segment).
  • roads other than 1-way roads will be treated as distinct roads for the purposes of assigning data samples to roads and for other purposes (e.g ., to treat the northbound lances of a freeway as being a distinct road from the southbound lanes of the freeway), and if so the direction for a mobile data sample may further be used to determine the appropriate road with which the data sample is associated - in other embodiments, however, roads may be modeled in other manners, such as to treat a two-way city street as a single road ( e.g ., with average traffic conditions being reported and predicted for vehicles moving in both directions), to treat each lane of a multiple lane freeway or other road as a distinct logical road, etc.
  • fleet vehicles may be configured in various ways to provide data samples of use. For example, if a large fleet of vehicles will each leave the same origination point at a similar time each day, various of the fleet vehicles may be configured differently regarding how soon and how often to begin providing data samples, such as to minimize a very large number of data points all near the single origination point and/or to provide variability in when data samples will be acquired and transmitted.
  • a mobile data source device may be configured in various ways regarding how and when to acquire data samples, including based on total distance covered since a starting point (e.g ., an origination point for a group of fleet vehicles), distance covered since a last data sample acquisition and/or transmission, total time elapsed since a starting time (e.g ., a departure time of a fleet vehicle from an origination point), time elapsed since a last data sample acquisition and/or transmission, an indicated relationship having occurred with respect to one or more indicated locations (e.g ., passing by, arriving at, departing from, etc.), etc.
  • a starting point e.g ., an origination point for a group of fleet vehicles
  • distance covered since a last data sample acquisition and/or transmission e.g a departure time of a fleet vehicle from an origination point
  • time elapsed since a last data sample acquisition and/or transmission e.g ., an indicated relationship having occurred with respect to one or more indicated locations (e.g ., passing
  • a mobile data source device may be configured in various ways regarding how and when to transmit or otherwise provide one or more acquired data samples, such as when predefined conditions are satisfied, including based on total distance covered since a starting point, distance covered since a last data sample acquisition and/or transmission, total time elapsed since a starting time, time elapsed since a last data sample acquisition and/or transmission, an indicated relationship having occurred with respect to one or more indicated locations, an indicated number of data samples having been gathered, an indicated amount of data having been gathered ( e.g ., an amount such as to fill or substantially fill a cache used to store the data samples on the mobile device, or an amount such as to fill or substantially fill an indicated amount of time for a transmission), etc.
  • FIG 8 is a flow diagram of an example embodiment of a Mobile Data Source information Provision routine 800 related to the present invention, such as may be provided by, for example, operation of a mobile data source device for each of one or more of the vehicle-based data sources 384 of Figure 3 and/or other data sources 388 ( e.g ., user devices) of Figure 3 and/or vehicle-based data sources 101 of Figure 1 and/or other data sources 102 of Figure 1 .
  • the routine acquires data samples for a particular mobile data source to indicate current traffic conditions, and stores the data samples as appropriate such that a subsequent transmission may include information for multiple data samples.
  • the routine begins at step 805, where parameters are retrieved that will be used as part of the data sample acquisition and providing, such as configurable parameters to indicate when data samples should be acquired and when transmissions should occur with information corresponding to one or more data samples.
  • the routine continues to step 810 to wait until it is time to acquire a data sample, such as based on the retrieved parameters and/or other information (e.g ., an indicated amount of time having passed since a prior data sample acquisition, an indicated distance having been traveled since a prior data sample acquisition, an indication to acquire data samples in a substantially continuous manner, etc.).
  • the routine then continues to step 815 to acquire a data sample based on the current location and movement of the mobile data source, and stores the data sample in step 820.
  • step 825 If it is determined in step 825 that it is not yet time to transmit data, such as based on the retrieved parameters and/or other information (e.g ., an indicated amount of time having passed since a prior transmission, an indicated distance having been traveled since a prior transmission, an.indication to transmit data samples as soon as they become available or in a substantially continuous manner, etc.), the routine returns to step 810.
  • the routine returns to step 810.
  • step 830 retrieve and select any stored data samples since the prior transmission (or since startup, for the first transmission).
  • the routine then optionally in step 835 generates aggregated data based on multiple of the selected data samples (e.g ., an overall average speed for all of the data samples, an average speed and a direction for each data sample if the acquired information provides only location information, etc.), although in other embodiments such aggregated data generation may not be performed.
  • step 840 the routine then optionally removes some or all of the acquire information for some or all of the data samples from the selected set of data samples (e.g ., to transmit only selected types of data for each data sample, to remove data samples that appear to be outliers or otherwise erroneous, to remove data samples that do not correspond to actual movement of the mobile data source, etc.), although in other embodiments such information removal may not be performed.
  • step 845 the routine then transmits the current information in the current set of data samples and any aggregated information to a recipient that will use the data in an appropriate manner.
  • step 895 the routine determines whether to continue (e.g ., whether the mobile data source continues to be in use and mobile), and if so returns to step 810.
  • the routine continues to step 899 and ends.
  • the steps 830-845 may not be performed until such time as the mobile data source is able to transmit or otherwise provide ( e.g ., via physical download) some or all of the data samples that have been acquired and stored since a prior transmission.
  • the road traffic conditions information may be used in various ways, such as to report current road traffic conditions in a substantially realtime manner, or to use past and current road traffic condition information to predict future traffic conditions at each of multiple future times.
  • the types of input data used to generate predictions of future traffic conditions may include a variety of current, past, and expected future conditions, and outputs from the prediction process may include the generated predictions of the expected traffic conditions on each of multiple target road segments of interest for each of multiple future times (e.g ., every 5, 15 or 60 minutes in the future) within a pre-determined time interval (e.g ., three hours, or one day), as discussed in greater detail elsewhere.
  • a pre-determined time interval e.g ., three hours, or one day
  • types of input data may include the following: information about current and past amounts of traffic for various target road segments of interest in a geographic area, such as for a network of selected roads in the geographic area; information about current and recent traffic accidents; information about current, recent and future road work; information about current, past and expected future weather conditions (e.g ., precipitation, temperature, wind direction, wind speed, etc.); information about at least some current, past and future scheduled events (e.g ., type of event, expected start and end times of the event, and/or a venue or other location of the event, etc., such as for all events, events of indicated types, events that are sufficiently large, such as to have expected attendance above an indicated threshold (for example, 1000 or 5000 expected attendees), etc.); and information about school schedules (e.g ., whether school is in session and/or the location of one or more schools).
  • information about current and past amounts of traffic for various target road segments of interest in a geographic area such as for a network of selected roads in the geographic area
  • the multiple future times at which future traffic conditions are predicted are each points in time
  • such predictions may instead represent multiple time points (e.g ., a period of time), such as by representing an average or other aggregate measure of the future traffic conditions during those multiple time points.
  • some or all of the input data may be known and represented with varying degrees of certainty (e.g ., expected weather), and additional information may be generated to represent degrees of confidence in and/or other metadata for the generated predictions.
  • the prediction of future traffic conditions may be initiated for various reasons and at various times, such as in a periodic manner, ( e.g ., every five minutes), when any or sufficient new input data is received, in response to a request from a user, etc.
  • Some of the same types of input data may be used to similarly generate longer-term forecasts of future traffic conditions (e.g ., one week in the future, or one month in the future) in some embodiments, but such longer-term forecasts may not use some of the types of input data, such as information about current conditions at the time of the forecast generation (e.g ., current traffic, weather, or other conditions).
  • such longer-term forecasts may be generated less-frequently than shorter-term predictions, and may be made so as to reflect different future time periods than for shorter-term predictions ( e.g ., for every hour rather than every 15 minutes).
  • the roads and/or road segments for which future traffic condition predictions and/or forecasts are generated may also be selected in various manners in various embodiments.
  • future traffic condition predictions and/or forecasts are 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 current traffic condition information is readily available (e.g ., based on networks of road sensors for at least some of the roads in the area) and/or in which traffic congestion is a significant problem.
  • the roads for which future traffic condition predictions and/or forecasts are generated include those roads for which current traffic condition information is readily 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.).
  • future traffic condition predictions and/or forecasts may be made for a single road, regardless of its size and/or inter-relationship with other roads.
  • segments of roads for which future traffic condition predictions and/or forecasts are generated may be selected in various manners, such as to treat each road sensor as a distinct segment; to group multiple road sensors together for each road segment ( e.g ., to reduce the number of independent predictions and/or forecasts that are made, such as by grouping specified numbers of road sensors together); to select road segments so as to reflect logically related sections of a road in which traffic conditions are typically the same or sufficiently similar ( e.g ., strongly correlated), such as based on traffic condition information from traffic sensors and/or from other sources (e.g ., data generated from vehicles and/or users that are traveling on the roads, as discussed in greater detail elsewhere); etc.
  • future traffic condition prediction and/or forecast information may be used in a variety of ways in various embodiments, as discussed in greater detail elsewhere, including to provide such information to users and/or organizations at various times (e.g ., in response to requests, by periodically sending the information, etc.) and in various ways (e.g ., by transmitting the information to cellular telephones and/or other portable consumer devices; by displaying information to users, such as via Web browsers and/or application programs; by providing the information to other organizations and/or entities that provide at least some of the information to users, such as third parties that perform the information providing after analyzing and/or modifying the information; etc.).
  • the prediction and/or forecast information is used to determine suggested travel routes and/or times, such as an optimal route between a starting location and an ending location over a network of roads and/or an optimal time to perform indicated travel, with such determinations based on predicted and/or forecast information at each of multiple future times for one or more roads and/or road segments.
  • various embodiments provide various mechanisms for users and other clients to interact with one or more of the traffic information systems (e.g ., the Data Sample Manager system 350, RT information Provider system 363, and/or Predictive Traffic information Provider system 360 of Figure 3 , etc.).
  • some embodiments may provide an interactive console (e.g . a client program providing an interactive user interface, a Web browser-based interface, etc.) from which clients can make requests and receive corresponding responses, such as requests for information related to current and/or predicted traffic conditions and/or requests to analyze, select, and/or provide information related to travel routes.
  • some embodiments provide an API (“Application Programmer Interface") that allows client computing systems to programmatically make some or all such requests, such as via network message protocols (e.g ., Web services) and/or other communication mechanisms.

Landscapes

  • Chemical & Material Sciences (AREA)
  • Analytical Chemistry (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Traffic Control Systems (AREA)

Claims (30)

  1. Procédé mis en oeuvre par ordinateur pour évaluer des échantillons de données représentant des véhicules circulant sur des routes, procédé comprenant :
    la réception d'indications d'un ou plusieurs segments d'une ou de plusieurs routes, chaque segment de route comprenant de multiples échantillons de données associés reflétant chacun une vitesse rapportée d'un véhicule circulant sur un segment de route ; et
    pour chacun des segments de route, l'analyse automatique des multiples échantillons de données associés pour le segment de route de façon à déterminer un ou plusieurs des échantillons de données qui sont non représentatifs d'un trajet effectif de véhicule sur le segment de route, le ou les échantillons de données étant des valeurs statistiques aberrantes par rapport à d'autres échantillons parmi les multiples échantillons de données associés ; et
    la fourniture d'une ou plusieurs indications d'exclusion de l'utilisation ultérieure des échantillons de données déterminés de sorte que les autres échantillons de données puissent être utilisés pour faciliter la circulation sur le segment de route ;
    dans lequel la détermination du ou des échantillons de données est effectuée sur la base d'une analyse de valeur aberrante qui comprend :
    la détermination d'une caractéristique de condition de circulation moyenne pour tous les multiples échantillons de données associés ; et
    pour chacun des multiples échantillons de données associés, la détermination d'une caractéristique de
    condition de circulation moyenne pour tous les multiples échantillons de données associés autres que l'échantillon de données, l'identification d'une différence entre la caractéristique de condition de circulation moyenne déterminée pour tous les multiples échantillons de données associés autres que l'échantillon de données et la caractéristique de condition de circulation moyenne déterminée pour tous les multiples échantillons de données associés, et
    la détermination, sur la base de la différence identifiée, si l'échantillon de données est ou non une valeur statistique aberrante.
  2. Procédé conformément à la revendication 1, dans lequel, pour un ou plusieurs desdits segments de route, la fourniture des indications d'exclusion de l'utilisation ultérieure des échantillons de données déterminés comprend en outre l'analyse des échantillons de données associés pour le segment de route autres que les échantillons de données déterminés afin de déterminer une vitesse moyenne des véhicules circulant sur le segment de route, et comprend l'indication de la vitesse moyenne déterminée à utiliser pour faciliter la circulation d'autres véhicules sur le segment de route.
  3. Procédé conformément à la revendication 1, dans lequel, pour un ou plusieurs desdits segments de route, la fourniture des indications d'exclusion de l'utilisation ultérieure des échantillons de données déterminés comprend l'analyse des échantillons de données associés pour le segment de route autres que les échantillons de données déterminés afin de déterminer l'écoulement de circulation de véhicules circulant sur le segment de route, et comprend l'indication de l'écoulement de circulation déterminé à utiliser pour faciliter la circulation d'autres véhicules sur le segment de route.
  4. Procédé conformément à la revendication 1, dans lequel, pour chacun desdits segments de route, la détermination de la caractéristique de condition de circulation moyenne pour les multiples échantillons de données autres que le ou les échantillons de données comprend la détermination d'une vitesse moyenne et d'une déviation standard pour tous les multiples échantillons de données pour le segment de route, et dans lequel l'identification de la différence entre la caractéristique de condition de circulation moyenne déterminée et la seconde caractéristique de condition de circulation moyenne comprend, pour chacune desdits échantillons de données déterminés pour le segment de route,
    la détermination d'une vitesse moyenne et d'une déviation standard pour tous les autres échantillons parmi les multiples échantillons de données pour le segment de route en fonction de la vitesse moyenne déterminée et de la vitesse standard pour tous les multiples échantillons de données pour le segment de route ;
    la détermination d'une différence entre la vitesse rapportée pour l'échantillon de données et la vitesse moyenne déterminée pour tous les autres échantillons parmi les multiples échantillons de données pour le segment de route ;
    la détermination d'un seuil sur la base, au moins en partie, de la déviation standard déterminée pour tous les autres échantillons parmi les multiples échantillons de données pour le segment de route ; et
    l'identification de l'échantillon de données en tant que valeur statistique aberrante sur la base de la différence déterminée excédant le seuil déterminé.
  5. Procédé conformément à la revendication 1, dans lequel, pour chacun desdits segments de route, la détermination de la caractéristique de condition de circulation moyenne pour tous les multiples échantillons de données associés autres que l'échantillon de données est basée, au moins en partie, sur la vitesse rapportée de tous les multiples échantillons de données associés autres que l'échantillon de données.
  6. Procédé conformément à la revendication 1, dans lequel, pour chacun desdits segments de route, la détermination que lesdits échantillons de données sont non représentatifs d'un trajet effectif de véhicule sur le segment de route sur la base d'au moins l'un des échantillons de données déterminés en tant que valeur statistique aberrante par rapport à d'autres échantillons parmi les multiples échantillons de données associés au segment de route est effectuée sensiblement en temps réel.
  7. Procédé conformément à la revendication 1, dans lequel, pour un ou plusieurs desdits segments de route, la détermination desdits échantillons de données pour le segment de route qui sont non représentatifs d'un trajet effectif de véhicule sur le segment de route comprend l'évaluation d'une activité de chaque véhicule dont la vitesse rapportée est reflétée par au moins l'un des échantillons de données déterminés et la détermination que l'activité évaluée de chacun des véhicules ne correspond pas à un trajet effectif de véhicule sur le segment de route.
  8. Procédé conformément à la revendication 7, dans lequel l'activité évaluée d'au moins l'un des véhicules correspond à un véhicule garé.
  9. Procédé conformément à la revendication 7, dans lequel l'activité évaluée d'au moins l'un des véhicules sur la base d'un ou de plusieurs échantillons de données déterminés correspond à un trajet sur un segment de route autre qu'un segment de route auquel le ou les échantillons de données déterminés est/sont associé(s).
  10. Procédé conformément à la revendication 1 comprenant en outre, pour chacune de multiples périodes de temps distinctes, la réception de multiples échantillons de données associés pour l'un des segments de route reflétant chacun une vitesse rapportée d'un véhicule à un temps rapporté sur le segment de route au cours de la période de temps, et dans lequel l'analyse automatique est effectuée pour le segment de route pour chacune des périodes de temps sur la base des échantillons de données dont les temps rapportés sont compris dans la période de temps.
  11. Procédé conformément à la revendication 1, dans lequel, pour un ou plusieurs desdits segments de route, la détermination d'un ou plusieurs échantillons de données pour le segment de route qui est/sont non représentatif(s) d'un trajet effectif de véhicule sur le segment de route comprend l'identification de multiples échantillons de données qui sont rapportés par un véhicule unique circulant sur le segment de route, la détermination d'une activité du véhicule unique au fil du temps sur la base des échantillons de données identifiés, et
    la détermination que les échantillons de données identifiés sont non représentatifs d'un trajet effectif de véhicule sur le segment de route en fonction de l'activité déterminée.
  12. Procédé conformément à la revendication 1, dans lequel, pour un ou plusieurs desdits segments de route, la détermination d'un ou plusieurs échantillons de données pour le segment de route qui sont non représentatifs d'un trajet effectif de véhicule sur le segment de route comprend l'identification de valeurs prévues pour les multiples échantillons de données associés au segment de route et la détermination que les échantillons de données déterminés ne correspondent pas aux valeurs prévues identifiées.
  13. Procédé conformément à la revendication 1, dans lequel pour un ou plusieurs desdits segments de route, la détermination d'un ou plusieurs échantillons de données pour le segment de route qui sont non représentatifs d'un trajet effectif de véhicule sur le segment de route comprend la détermination d'une distribution statistique pour les multiples échantillons de données associés au segment de route et la détermination que les échantillons de données déterminés ne correspondent pas à la distribution statistique déterminée.
  14. Procédé conformément à la revendication 1, dans lequel pour un ou plusieurs desdits segments de route, la détermination d'un ou plusieurs échantillons de données pour le segment de route qui sont non représentatifs d'un trajet effectif de véhicule sur le segment de route comprend l'identification de multiples courbes de données distinctes pour le segment de route, chacune des courbes de données reflétant un sous-ensemble distinct d'un trajet du véhicule sur au moins une partie du segment de route, et dans lequel les échantillons de données déterminés correspondent à au moins l'une des courbes de données qui reflètent un sous-ensemble de trajet de véhicule qui ne présente pas d'intérêt.
  15. Procédé conformément à la revendication 14, dans lequel au moins l'une des courbes de données identifiées est une courbe gaussienne.
  16. Procédé conformément à la revendication 1, dans lequel, pour ou un ou plusieurs desdits segments de route, les multiples échantillons de données associés pour le segment de route reflètent en outre chacun un temps rapporté correspondant à la vitesse rapportée du véhicule pour l'échantillon de données, l'analyse automatique des multiples échantillons de données associés pour le segment de route correspondant en outre à une période de temps prédéfinie de sorte que le trajet effectif de véhicule sur le segment de route est un trajet se déroulant dans la période de temps prédéfinie.
  17. Procédé conformément à la revendication 16, dans lequel pour chacun desdits segments de route, la détermination desdits échantillons de données pour le segment de route qui sont non représentatifs d'un trajet effectif de véhicule sur le segment de route comprend l'identification que le temps rapporté pour chacun des échantillons de données déterminés n'est pas compris dans la période de temps prédéfinie du segment de route.
  18. Procédé conformément à la revendication 1, dans lequel au moins quelques multiples échantillons de données associés à au moins quelques segments de route sont acquis par les véhicules circulant sur lesdits quelques segments de route et rapportés à partir de ces derniers, l'établissement du rapport desdits quelques échantillons de données survenant sensiblement en temps réel après l'acquisition d'un ou plusieurs desdits quelques échantillons de données.
  19. Système informatique conçu pour évaluer des échantillons de données représentant des véhicules qui circulent comprenant :
    un premier élément qui est conçu, pour chacune des multiples routes, pour la réception d'une indication de multiples échantillons de données pour la route reflétant chacun une vitesse rapportée d'un véhicule circulant sur la route ; et
    un élément d'élimination de valeur aberrante d'échantillon de données qui est conçu, pour chacune des multiples routes, pour la détermination automatique d'un ou de plusieurs des multiples échantillons de données pour la route qui sont des valeurs statistiques aberrantes par rapport à d'autres échantillons parmi les multiples échantillons de données pour la route et la fourniture d'une ou de plusieurs indications des multiples échantillons de données pour la route autres que les échantillons de données déterminés de sorte que les échantillons de données indiqués puissent être utilisés pour faciliter la circulation sur la route ; et
    dans lequel l'élément de valeur aberrante d'échantillon de données est en outre conçu pour déterminer le ou les échantillons de données sur la base d'une analyse de valeur aberrante qui comprend :
    la détermination d'une caractéristique de condition de circulation moyenne pour tous les multiples échantillons de données ;
    pour chacun des multiples échantillons de données, la détermination d'une caractéristique de condition de circulation moyenne pour tous les multiples échantillons de données autres que l'échantillon de données, l'identification d'une différence entre la caractéristique de condition de circulation moyenne pour tous les multiples échantillons de données autres que l'échantillon de données et la caractéristique de condition de circulation moyenne déterminée pour tous les multiples échantillons de données ; et
    la détermination, sur la base de la différence identifiée, si l'échantillon de données est ou non une valeur statistique aberrante.
  20. Système informatique conformément à la revendication 19, dans lequel, pour chacune d'au moins une des multiples routes, la détermination des échantillons de données pour la route qui sont des valeurs statistiques aberrantes comprend la mise en oeuvre de l'analyse de valeur aberrante sensiblement en temps réel, et dans lequel la fourniture des indications des échantillons de données pour la route comprend l'analyse des échantillons de données pour déterminer la vitesse moyenne de véhicules circulant sur la route et pour indiquer la vitesse moyenne déterminée à utiliser pour faciliter la circulation d'autres véhicules sur la route.
  21. Système informatique conformément à la revendication 19, dans lequel le premier élément et l'élément d'élimination de valeur aberrante d'échantillon de données comprennent chacun des instructions de logiciel destinées à être exécutées dans la mémoire du système informatique.
  22. Support lisible par ordinateur dont les contenus permettent à un dispositif informatique d'évaluer des échantillons de données représentant des véhicules qui circulent, par l'exécution d'un procédé comprenant :
    la réception d'une indication de multiples échantillons de données reflétant chacun des caractéristiques de trajet rapportées d'un véhicule parmi de multiples véhicules circulant sur une ou plusieurs routes, les caractéristiques de trajet rapportées pour les échantillons de données reflétant les positions des véhicules ;
    la détermination automatique si un ou plusieurs des multiples échantillons de données est/sont non représentatif(s) ou non d'un trajet effectif de véhicule présentant un intérêt sur la ou les routes, la détermination étant basée, au moins en partie, sur les caractéristiques de trajet ; et
    la fourniture d'une ou plusieurs indications des échantillons de données qui ne sont pas déterminés comme étant non représentatifs de sorte que les échantillons de données indiqués puissent être utilisés pour faciliter la circulation sur la ou les routes ; et
    dans lequel la détermination si un ou plusieurs des multiples échantillons de données est/sont non représentatif(s) ou non est effectuée à partir d'une analyse de valeur aberrante qui comprend :
    la détermination d'une caractéristique de condition de circulation moyenne pour tous les multiples échantillons de données ; et
    pour chacun des multiples échantillons de données, la détermination d'une caractéristique de condition de circulation moyenne pour tous les multiples échantillons de données autres que l'échantillon de données, l'identification d'une différence entre la caractéristique de condition de circulation moyenne déterminée pour tous les multiples échantillons de données autres que l'échantillon de données et la première caractéristique de condition de circulation moyenne déterminée pour tous les multiples échantillons de données, et la détermination, sur la base de la différence identifiée, si l'échantillon de données est ou non une valeur statistique aberrante.
  23. Support lisible par ordinateur conformément à la revendication 22, dans lequel les caractéristiques de trajet rapportées de chaque échantillon de données comprennent une position rapportée du véhicule à laquelle correspond l'échantillon de données, et dans lequel la détermination si un ou plusieurs échantillons de données est/sont non représentatif(s) ou non d'un trajet effectif de véhicule présentant un intérêt sur la ou les routes comprend la détermination que le ou les échantillons de données est/sont non représentatif(s) sur la base, au moins en partie, des positions de véhicule rapportées des échantillons de données ne correspondant pas à des positions pour un trajet effectif de véhicule sur la ou les routes.
  24. Support lisible par ordinateur conformément à la revendication 23, dans lequel la détermination que le ou les échantillons de données est/sont non représentatif(s), sur la base, au moins en partie, des positions de véhicule rapportées des échantillons de données qui ne correspondent pas aux positions pour le trajet effectif de véhicule sur la ou les routes comprend la détermination que les positions de véhicule rapportées de ces échantillons de données ne correspondent pas à des positions d'intérêt prédéfinies pour la ou les routes.
  25. Support lisible par ordinateur conformément à la revendication 22, dans lequel les contenus sont des d'instructions, lesquelles, lorsqu'elles sont exécutées, amènent le dispositif informatique à exécuter le procédé.
  26. Support lisible par ordinateur conformément à la revendication 22, dans lequel les caractéristiques de trajet rapportées de chaque échantillon de données comprennent une destination de trajet rapportée du véhicule à laquelle l'échantillon de données correspond, et dans lequel la détermination si un ou plusieurs échantillons de données est/sont non représentatif(s) ou non d'un trajet effectif de véhicule sur la ou les routes comprend la détermination que le ou les échantillons de données est/sont non représentatif(s) sur la base, au moins en partie, des destinations de trajet de véhicule rapportées des échantillons de données ne correspondant pas à une ou plusieurs destinations pour le trajet effectif de véhicule sur la ou les routes.
  27. Support lisible par ordinateur conformément à la revendication 26, dans lequel la détermination que le ou les échantillons de données est/sont non représentatif(s) sur la base, au moins en partie, des destinations de trajet de véhicule rapportées des échantillons de données ne correspondant pas à la ou les destinations pour le trajet effectif de véhicule sur la ou les routes comprend la détermination que les destinations de trajet de véhicule rapportées de ces échantillons de données ne correspondent pas aux destinations de trajet d'intérêt prédéfinies pour la ou les routes.
  28. Support lisible par ordinateur conformément à la revendication 22, dans lequel la détermination si un ou plusieurs échantillons de données est/sont non représentatif(s) ou non du trajet effectif de véhicule présentant un intérêt sur la ou les routes comprend l'identification d'une ou plusieurs activités dans lesquelles un ou plusieurs véhicules est/sont engagé(s) sur la base des caractéristiques de trajet rapportées à partir d'au moins un échantillon de données pour chacun de ces véhicules et la détermination que le ou les échantillons de données est/sont non représentatif(s) sur la base, au moins en partie, des activités identifiées, lesquelles ne présentent pas d'intérêt.
  29. Support lisible par ordinateur conformément à la revendication 22, dans lequel le support lisible par ordinateur est une mémoire d'un dispositif informatique.
  30. Support lisible par ordinateur conformément à la revendication 22, dans lequel le support lisible par ordinateur est un support de transmission de données qui transmet un signal de données généré comprenant les contenus.
EP07752080A 2006-03-03 2007-03-02 Évaluation des conditions de circulation routière au moyen de données provenant de sources de données mobiles Active EP1938296B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP10013472A EP2278573B1 (fr) 2006-03-03 2007-03-02 Évaluation des conditions de circulation routière au moyen de données provenant de sources differentes

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
US77894606P 2006-03-03 2006-03-03
US78974106P 2006-04-05 2006-04-05
US11/431,980 US20070208493A1 (en) 2006-03-03 2006-05-11 Identifying unrepresentative road traffic condition data obtained from mobile data sources
US11/432,603 US20070208501A1 (en) 2006-03-03 2006-05-11 Assessing road traffic speed using data obtained from mobile data sources
US11/438,822 US7831380B2 (en) 2006-03-03 2006-05-22 Assessing road traffic flow conditions using data obtained from mobile data sources
US11/444,998 US8014936B2 (en) 2006-03-03 2006-05-31 Filtering road traffic condition data obtained from mobile data sources
US11/473,861 US7912627B2 (en) 2006-03-03 2006-06-22 Obtaining road traffic condition data from mobile data sources
US83870006P 2006-08-18 2006-08-18
US11/540,342 US7706965B2 (en) 2006-08-18 2006-09-28 Rectifying erroneous road traffic sensor data
PCT/US2007/005355 WO2007103180A2 (fr) 2006-03-03 2007-03-02 Évaluation des conditions de circulation routière au moyen de données provenant de sources de données mobiles

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP10013472.5 Division-Into 2010-10-08

Publications (2)

Publication Number Publication Date
EP1938296A2 EP1938296A2 (fr) 2008-07-02
EP1938296B1 true EP1938296B1 (fr) 2011-09-07

Family

ID=38181159

Family Applications (2)

Application Number Title Priority Date Filing Date
EP07752080A Active EP1938296B1 (fr) 2006-03-03 2007-03-02 Évaluation des conditions de circulation routière au moyen de données provenant de sources de données mobiles
EP10013472A Active EP2278573B1 (fr) 2006-03-03 2007-03-02 Évaluation des conditions de circulation routière au moyen de données provenant de sources differentes

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP10013472A Active EP2278573B1 (fr) 2006-03-03 2007-03-02 Évaluation des conditions de circulation routière au moyen de données provenant de sources differentes

Country Status (7)

Country Link
EP (2) EP1938296B1 (fr)
JP (1) JP2009529187A (fr)
CN (6) CN102289936B (fr)
AT (1) ATE523869T1 (fr)
AU (1) AU2007224206A1 (fr)
ES (2) ES2373336T3 (fr)
WO (1) WO2007103180A2 (fr)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102341833A (zh) * 2009-03-03 2012-02-01 丰田自动车株式会社 驾驶辅助装置
CN102032911B (zh) * 2009-09-29 2014-05-28 宏达国际电子股份有限公司 车辆导航方法及***
WO2014114751A1 (fr) 2013-01-24 2014-07-31 Eilertsen Roger André Système de surveillance et de guidage de circulation routière
CN105303833A (zh) * 2015-11-05 2016-02-03 安徽四创电子股份有限公司 基于微波车辆检测器的高架桥突发事件判别方法
US9640071B2 (en) 2015-06-30 2017-05-02 Here Global B.V. Method and apparatus for identifying a bi-modality condition upstream of diverging road segments
US9911327B2 (en) 2015-06-30 2018-03-06 Here Global B.V. Method and apparatus for identifying a split lane traffic location
US10147315B2 (en) 2016-07-27 2018-12-04 Here Global B.V. Method and apparatus for determining split lane traffic conditions utilizing both multimedia data and probe data
US10198941B2 (en) 2016-07-27 2019-02-05 Here Global B.V. Method and apparatus for evaluating traffic approaching a junction at a lane level
US11004335B2 (en) 2018-11-07 2021-05-11 Beijing Didi Infinity Technology And Development Co., Ltd. Systems and methods for speed prediction

Families Citing this family (118)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6587781B2 (en) 2000-08-28 2003-07-01 Estimotion, Inc. Method and system for modeling and processing vehicular traffic data and information and applying thereof
US7620402B2 (en) 2004-07-09 2009-11-17 Itis Uk Limited System and method for geographically locating a mobile device
JP4924407B2 (ja) 2007-12-25 2012-04-25 富士通株式会社 センサ診断方法及びセンサ診断装置
JP4935704B2 (ja) * 2008-02-14 2012-05-23 アイシン・エィ・ダブリュ株式会社 駐車場混雑状態判定装置、駐車場混雑状態判定方法及びコンピュータプログラム
JP4983660B2 (ja) * 2008-03-14 2012-07-25 アイシン・エィ・ダブリュ株式会社 ナビゲーションシステム及び経路探索方法
GB0901588D0 (en) 2009-02-02 2009-03-11 Itis Holdings Plc Apparatus and methods for providing journey information
JP5378002B2 (ja) * 2009-02-19 2013-12-25 アイシン・エィ・ダブリュ株式会社 車両動作推定装置、車両動作推定方法および車両動作推定プログラム
CN101694743B (zh) * 2009-08-25 2011-09-21 北京世纪高通科技有限公司 预测路况的方法和装置
CN102262819B (zh) * 2009-10-30 2014-10-15 国际商业机器公司 基于移动通信网络确定道路的实时通行时间的方法和装置
US9406229B2 (en) * 2009-11-12 2016-08-02 Gm Global Technology Operations, Llc Travel lane advisor
JP5382136B2 (ja) * 2009-12-17 2014-01-08 トヨタ自動車株式会社 車両制御装置
CN101782396B (zh) * 2010-03-05 2011-12-28 中国软件与技术服务股份有限公司 一种导航方法及导航***
JPWO2011125185A1 (ja) * 2010-04-07 2013-07-08 トヨタ自動車株式会社 車両走行支援装置
JP5195848B2 (ja) * 2010-08-31 2013-05-15 株式会社デンソー 交通状況予測装置
KR101506927B1 (ko) * 2010-09-16 2015-04-06 에스케이플래닛 주식회사 이동통신망을 이용한 교통정보 수집시스템, 그 유효 표본 보정 장치 및 그룹 별 평균 속도 산출 방법, 이를 위한 기록매체
KR101776807B1 (ko) 2010-09-16 2017-09-19 에스케이텔레콤 주식회사 이동통신망을 이용한 교통정보 수집시스템, 그 유효 표본 보정 장치 및 속도 측정 방법, 이를 위한 기록매체
BE1019524A3 (nl) * 2010-09-30 2012-08-07 Be Mobile Nv Systeem en werkwijze voor reistijdmeting.
CN102446413A (zh) * 2010-09-30 2012-05-09 西门子公司 一种基于移动终端切换信息获取路径信息方法和装置
KR101508136B1 (ko) * 2010-10-22 2015-04-06 에스케이플래닛 주식회사 교통정보 수집 시스템, 그 유효표본 보정 장치 및 유효표본 보정 방법
JP5601177B2 (ja) * 2010-11-30 2014-10-08 アイシン・エィ・ダブリュ株式会社 位置特定装置、位置特定方法、及び位置特定プログラム
CN102044153B (zh) * 2010-12-22 2015-11-25 广州通易科技有限公司 一种交通流通畅等级评价的方法与***
JP5739182B2 (ja) 2011-02-04 2015-06-24 インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ 制御システム、方法およびプログラム
JP5731223B2 (ja) 2011-02-14 2015-06-10 インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ 異常検知装置、監視制御システム、異常検知方法、プログラムおよび記録媒体
JP5689333B2 (ja) 2011-02-15 2015-03-25 インターナショナル・ビジネス・マシーンズ・コーポレーションＩｎｔｅｒｎａｔｉｏｎａｌ Ｂｕｓｉｎｅｓｓ Ｍａｃｈｉｎｅｓ Ｃｏｒｐｏｒａｔｉｏｎ 異常検知システム、異常検知装置、異常検知方法、プログラムおよび記録媒体
CN102169630B (zh) * 2011-03-31 2013-04-24 上海电科智能***股份有限公司 一种道路连续交通流数据质量控制方法
CN102157070B (zh) * 2011-03-31 2013-01-09 天津大学 基于手机数据的道路交通流预测方法
GB2492369B (en) 2011-06-29 2014-04-02 Itis Holdings Plc Method and system for collecting traffic data
CN102360529B (zh) * 2011-09-20 2013-07-24 张忠义 直接获取城市道路通行速度的方法
CN102521985A (zh) * 2012-01-06 2012-06-27 北京捷易联科技有限公司 一种交通信息评价方法及装置
JP5880580B2 (ja) * 2012-01-20 2016-03-09 トヨタ自動車株式会社 車両挙動予測装置及び車両挙動予測方法、並びに運転支援装置
CN102568207A (zh) * 2012-02-02 2012-07-11 北京捷易联科技有限公司 交通数据处理方法和装置
US9132742B2 (en) * 2012-02-23 2015-09-15 International Business Machines Corporation Electric vehicle (EV) charging infrastructure with charging stations optimumally sited
GB201205348D0 (en) * 2012-03-27 2012-05-09 Tomtom Belgium Nv Digital location-based data methods and product
CN102779410B (zh) * 2012-07-19 2014-08-06 杭州师范大学 一种多源异类海量交通数据融合的并行实现方法
CN102867421B (zh) * 2012-09-24 2014-07-09 东南大学 一种识别有效停车泊位占有率中离群数据的方法
US20140143184A1 (en) * 2012-11-21 2014-05-22 Microsoft Corporation Turn restriction inferencing
CN103888893A (zh) * 2012-12-19 2014-06-25 ***通信集团公司 一种获取交通状态信息的***及方法
US9195938B1 (en) 2012-12-27 2015-11-24 Google Inc. Methods and systems for determining when to launch vehicles into a fleet of autonomous vehicles
CN103903464B (zh) * 2012-12-28 2016-01-20 观致汽车有限公司 交通阻塞信息预告方法及***
US9014957B2 (en) 2012-12-29 2015-04-21 Google Inc. Methods and systems for determining fleet trajectories to satisfy a sequence of coverage requirements
CN104123833B (zh) * 2013-04-25 2017-07-28 北京搜狗信息服务有限公司 一种道路状况的规划方法和装置
KR101338496B1 (ko) * 2013-07-18 2013-12-10 주식회사 로드코리아 도로 감시 방법
CN104376712B (zh) * 2013-08-16 2017-10-13 株式会社日立制作所 缺失交通信息补全装置及其方法
CN103473928B (zh) * 2013-09-24 2015-09-16 重庆大学 基于rfid技术的城市交通拥堵判别方法
CN104580292B (zh) * 2013-10-16 2019-03-05 电信科学技术研究院 一种行驶状态信息的获取方法、上报方法及设备
MX344376B (es) * 2013-10-17 2016-12-13 Ford Global Tech Llc Prediccion de caracteristicas de la carretera.
CN103561123B (zh) * 2013-10-28 2017-05-10 北京国双科技有限公司 Ip段归属确定方法和装置
JP5613815B1 (ja) * 2013-10-29 2014-10-29 パナソニック株式会社 滞留状況分析装置、滞留状況分析システムおよび滞留状況分析方法
CN103578274B (zh) * 2013-11-15 2015-11-04 北京四通智能交通***集成有限公司 一种交通流预测方法及装置
EP2887332B1 (fr) * 2013-12-23 2016-09-07 Siemens Aktiengesellschaft Procédé et système de détermination d'une situation de trafic sur une voie de circulation
JP6324101B2 (ja) * 2014-02-21 2018-05-16 株式会社ゼンリン 旅行時間データ調製装置、旅行時間データ調製方法およびプログラム
CN105091889B (zh) * 2014-04-23 2018-10-02 华为技术有限公司 一种热点路径的确定方法及设备
CN105303820A (zh) * 2014-07-18 2016-02-03 中兴通讯股份有限公司 一种交通状况信息提供方法、装置及服务端
CN104182618B (zh) * 2014-08-06 2017-06-30 西安电子科技大学 一种基于贝叶斯网络的追尾预警方法
JP6079721B2 (ja) 2014-08-07 2017-02-15 トヨタ自動車株式会社 車両用運転支援システム
EP3186662B1 (fr) * 2014-08-26 2019-03-20 Microsoft Technology Licensing, LLC Mesure de la vitesse du trafic dans un réseau routier
KR102303231B1 (ko) * 2014-12-15 2021-09-16 현대모비스 주식회사 차량용 레이더 시스템의 동작방법
KR101673307B1 (ko) 2014-12-19 2016-11-22 현대자동차주식회사 네비게이션 시스템 및 그에 의한 경로 예측 방법, 그리고 이를 실행하는 컴퓨터 판독 가능한 기록매체
JP6229981B2 (ja) * 2014-12-26 2017-11-15 パナソニックＩｐマネジメント株式会社 車両感知器異常検知装置、交通状況分析装置、車両感知器異常検知システム、交通状況分析システムおよびプログラム
CN104599499B (zh) * 2015-01-12 2017-08-29 北京中交兴路车联网科技有限公司 一种分布式统计交通位置的方法及装置
CN104778834B (zh) * 2015-01-23 2017-02-22 哈尔滨工业大学 一种基于车辆gps数据的城市道路交通拥堵判别方法
CN106156966A (zh) 2015-04-03 2016-11-23 阿里巴巴集团控股有限公司 物流监测方法及设备
CN104751644B (zh) * 2015-04-14 2017-02-22 无锡物联网产业研究院 一种交通检测方法以及交通检测装置
CN104933860B (zh) * 2015-05-20 2017-07-11 重庆大学 基于gps数据的公交车堵车延误时间预测方法
EP3106836B1 (fr) * 2015-06-16 2018-06-06 Volvo Car Corporation Unité et procédé pour régler une limite de route
DE102015213517A1 (de) * 2015-07-17 2017-01-19 Robert Bosch Gmbh Verfahren und Vorrichtung zum Warnen anderer Verkehrsteilnehmer bei einem falsch fahrenden Fahrzeug
US10317243B2 (en) * 2015-10-15 2019-06-11 Intertrust Technologies Corporation Sensor information management systems and methods
JP6494782B2 (ja) * 2015-10-30 2019-04-03 三菱電機株式会社 報知制御装置及び報知制御方法
CN105404772A (zh) * 2015-11-04 2016-03-16 成都天衡电科科技有限公司 基于分段***记忆效应的自适应历史数据分析方法
CN105389980B (zh) * 2015-11-09 2018-01-19 上海交通大学 基于长短时记忆递归神经网络的短时交通流预测方法
CN106683447B (zh) * 2015-11-11 2019-11-19 ***通信集团公司 一种交通灯控制方法及装置
CN105575155B (zh) * 2016-01-08 2018-09-18 上海雷腾软件股份有限公司 用于确定车辆行驶信息的方法和设备
CN105486322B (zh) * 2016-01-14 2020-07-03 上海博泰悦臻网络技术服务有限公司 一种区域道路的路况信息获取方法和***
CN105679055A (zh) * 2016-04-01 2016-06-15 深圳市智汇十方科技有限公司 一种道路状况预测方法和预测***
US10068470B2 (en) 2016-05-06 2018-09-04 Here Global B.V. Determination of an average traffic speed
JP6780456B2 (ja) * 2016-05-09 2020-11-04 株式会社デンソー 運転特性記憶装置
CN108010357B (zh) * 2016-11-01 2020-11-27 武汉四维图新科技有限公司 限速信息校验/统计方法、装置及***
CN106781489B (zh) * 2016-12-29 2019-07-26 北京航空航天大学 一种基于递归神经网络的路网状态预测方法
GB201711408D0 (en) * 2016-12-30 2017-08-30 Maxu Tech Inc Early entry
US10262479B2 (en) * 2017-02-24 2019-04-16 Huf North America Automotive Parts Mfg. Corp. System and method for communicating with a vehicle
CN106846816B (zh) * 2017-04-12 2019-09-17 山东理工大学 一种基于深度学习的离散化交通状态判别方法
CN107180530B (zh) * 2017-05-22 2019-09-06 北京航空航天大学 一种基于深度时空卷积循环网络的路网状态预测方法
WO2018224872A1 (fr) 2017-06-09 2018-12-13 Prannoy Roy Système de gestion de trafic prédictif
CN107705560B (zh) * 2017-10-30 2020-10-02 福州大学 一种融合视觉特征和卷积神经网络的道路拥堵检测方法
CN109754594B (zh) * 2017-11-01 2021-07-27 腾讯科技（深圳）有限公司 一种路况信息获取方法及其设备、存储介质、终端
CN107978153B (zh) * 2017-11-29 2019-07-26 北京航空航天大学 一种基于空间向量自回归模型的多模式交通需求影响分析方法
JP7353747B2 (ja) * 2018-01-12 2023-10-02 キヤノン株式会社 情報処理装置、システム、方法、およびプログラム
GB201802366D0 (en) * 2018-02-14 2018-03-28 Tom Tom Traffic B V Methods and systems for generating taffic volumn or traffic density data
US10895468B2 (en) * 2018-04-10 2021-01-19 Toyota Jidosha Kabushiki Kaisha Dynamic lane-level vehicle navigation with lane group identification
CN108510740A (zh) * 2018-05-04 2018-09-07 百度在线网络技术（北京）有限公司 误报路况的挖掘方法及装置
CN108898851B (zh) * 2018-06-20 2020-11-27 东南大学 城市道路断面交通量组合预测方法
CN109214175B (zh) * 2018-07-23 2021-11-16 中国科学院计算机网络信息中心 基于样本特征训练分类器的方法、装置及存储介质
CN109035775B (zh) * 2018-08-22 2020-12-08 青岛海信网络科技股份有限公司 一种突发事件识别的方法及装置
CN110936960A (zh) * 2018-09-21 2020-03-31 阿里巴巴集团控股有限公司 一种辅助驾驶方法和***
CN109410562B (zh) * 2018-10-29 2020-12-22 重庆交通大学 一种社区公交的优化调度方法
US11087617B2 (en) * 2018-11-26 2021-08-10 GM Global Technology Operations LLC Vehicle crowd sensing system and method
DE102018133457B4 (de) * 2018-12-21 2020-07-09 Volkswagen Aktiengesellschaft Verfahren und System zum Bereitstellen von Umgebungsdaten
US11631333B2 (en) * 2019-02-26 2023-04-18 Beijing Didi Infinity Technology And Development Co., Ltd. Multi-agent reinforcement learning for order-dispatching via order-vehicle distribution matching
FR3093690B1 (fr) * 2019-03-14 2021-02-19 Renault Sas Procédé de sélection pour un véhicule automobile d’une voie de circulation d’un rond-point
CN110164127B (zh) * 2019-04-04 2021-06-25 中兴飞流信息科技有限公司 一种车流量预测的方法、装置及服务器
CN111325993B (zh) * 2019-04-24 2021-02-19 北京嘀嘀无限科技发展有限公司 通行速度确定方法、装置、电子设备及计算机存储介质
US10752253B1 (en) 2019-08-28 2020-08-25 Ford Global Technologies, Llc Driver awareness detection system
IL269263B (en) * 2019-09-10 2021-09-30 Veeride Geo Ltd A navigation method based on a cell phone
CN111008119A (zh) * 2019-12-13 2020-04-14 浪潮电子信息产业股份有限公司 一种硬盘预测模型的更新方法、装置、设备及介质
CN113808384B (zh) * 2020-06-16 2023-02-10 英业达科技有限公司 交通状况侦测方法
CN111627219B (zh) * 2020-06-20 2021-07-09 天津职业技术师范大学(中国职业培训指导教师进修中心) 一种利用汽车电子标识来检测弯道行车信息的车协同方法
WO2022086482A1 (fr) * 2020-10-20 2022-04-28 ThruGreen, LLC Système de gestion de trafic à adaptation probabiliste
CN112489419B (zh) * 2020-10-28 2022-04-26 华为技术有限公司 道路容量的确定方法、装置及存储介质
CN112937584B (zh) * 2021-03-31 2022-06-03 重庆长安汽车股份有限公司 一种自动换道控制方法、装置及汽车
CN113256968B (zh) * 2021-04-30 2023-02-17 山东金宇信息科技集团有限公司 一种基于手机活动数据的交通状态预测方法、设备及介质
CN113469425B (zh) * 2021-06-23 2024-02-13 北京邮电大学 深度交通拥堵预测方法
CN113407559A (zh) * 2021-07-15 2021-09-17 广州小鹏自动驾驶科技有限公司 更新方法、装置及计算机存储介质
CN113593242A (zh) * 2021-09-28 2021-11-02 之江实验室 一种基于路口车辆检测器组的在途量估算方法
CN114120632B (zh) * 2021-11-01 2022-12-09 东南大学 基于导航地图的高速改扩建期间交通管控方法
WO2023127033A1 (fr) * 2021-12-27 2023-07-06 日本電気株式会社 Dispositif d'analyse de signal, procédé d'analyse de signal et support lisible par ordinateur
CN115683142A (zh) * 2022-10-25 2023-02-03 天津经纬恒润科技有限公司 一种感兴趣区域确定方法及装置
CN116913097B (zh) * 2023-09-14 2024-01-19 江西方兴科技股份有限公司 一种交通状态预测方法及***
CN117058888B (zh) * 2023-10-13 2023-12-22 华信纵横科技有限公司 一种交通大数据处理方法及其***

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5590217A (en) * 1991-04-08 1996-12-31 Matsushita Electric Industrial Co., Ltd. Vehicle activity measuring apparatus
DE19631630C2 (de) 1996-08-05 2001-05-31 Homag Maschinenbau Ag Bearbeitungsmaschine mit einer Saugspanneinrichtung
JPH10160494A (ja) * 1996-11-29 1998-06-19 Toyota Motor Corp 車載通信処理装置
WO1998054682A1 (fr) 1997-05-30 1998-12-03 Booth David S Generation et transmission d'informations liees au deplacement et en fonction d'un emplacement geographique
DE19805869A1 (de) * 1998-02-13 1999-08-26 Daimler Chrysler Ag Verfahren und Vorrichtung zur Bestimmung der Verkehrslage auf einem Verkehrswegennetz
CA2290301A1 (fr) * 1999-03-05 2000-09-05 Loran Network Management Ltd. Methode de detection des observations aberrantes lors de mesures d'activite
CA2266208C (fr) * 1999-03-19 2008-07-08 Wenking Corp. Systeme d'echange de donnees sur la circulation routiere a distance et de vehicules routiers intelligents
DE19928082C2 (de) * 1999-06-11 2001-11-29 Ddg Ges Fuer Verkehrsdaten Mbh Filterungsverfahren zur Bestimmung von Reisegeschwindigkeiten bzw. -zeiten und Domänen-Restgeschwindigkeiten
US6490519B1 (en) * 1999-09-27 2002-12-03 Decell, Inc. Traffic monitoring system and methods for traffic monitoring and route guidance useful therewith
US6989765B2 (en) * 2002-03-05 2006-01-24 Triangle Software Llc Personalized traveler information dissemination system
JP3990641B2 (ja) * 2002-03-27 2007-10-17 松下電器産業株式会社 道路情報提供システム及び装置と道路情報生成方法
US20040034467A1 (en) * 2002-08-09 2004-02-19 Paul Sampedro System and method for determining and employing road network traffic status
JP4657728B2 (ja) * 2002-08-29 2011-03-23 アイティス・ホールディングス・ピーエルシー トラフィック情報を提供するための装置および方法
JP3874745B2 (ja) * 2003-01-22 2007-01-31 松下電器産業株式会社 交通情報提供方法、交通情報提供システム及び装置
JP2004280521A (ja) * 2003-03-17 2004-10-07 Matsushita Electric Ind Co Ltd プローブカーシステムでの走行軌跡の伝送方法と装置
JP4255007B2 (ja) * 2003-04-11 2009-04-15 株式会社ザナヴィ・インフォマティクス ナビゲーション装置、およびその旅行時間算出方法
JP4392747B2 (ja) * 2003-12-24 2010-01-06 アイシン・エィ・ダブリュ株式会社 ナビゲーションシステム
CN100416584C (zh) * 2005-01-19 2008-09-03 北京交通大学 一种道路交通流数据质量控制方法与装置
CN100337256C (zh) * 2005-05-26 2007-09-12 上海交通大学 城市路网交通流状态估计方法

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102341833A (zh) * 2009-03-03 2012-02-01 丰田自动车株式会社 驾驶辅助装置
CN102341833B (zh) * 2009-03-03 2014-01-08 丰田自动车株式会社 驾驶辅助装置
CN102032911B (zh) * 2009-09-29 2014-05-28 宏达国际电子股份有限公司 车辆导航方法及***
WO2014114751A1 (fr) 2013-01-24 2014-07-31 Eilertsen Roger André Système de surveillance et de guidage de circulation routière
US9652983B2 (en) 2013-01-24 2017-05-16 Roger André EILERTSEN Traffic surveillance and guidance system
US9640071B2 (en) 2015-06-30 2017-05-02 Here Global B.V. Method and apparatus for identifying a bi-modality condition upstream of diverging road segments
US9911327B2 (en) 2015-06-30 2018-03-06 Here Global B.V. Method and apparatus for identifying a split lane traffic location
CN105303833A (zh) * 2015-11-05 2016-02-03 安徽四创电子股份有限公司 基于微波车辆检测器的高架桥突发事件判别方法
CN105303833B (zh) * 2015-11-05 2017-06-20 安徽四创电子股份有限公司 基于微波车辆检测器的高架桥突发事件判别方法
US10147315B2 (en) 2016-07-27 2018-12-04 Here Global B.V. Method and apparatus for determining split lane traffic conditions utilizing both multimedia data and probe data
US10198941B2 (en) 2016-07-27 2019-02-05 Here Global B.V. Method and apparatus for evaluating traffic approaching a junction at a lane level
US11004335B2 (en) 2018-11-07 2021-05-11 Beijing Didi Infinity Technology And Development Co., Ltd. Systems and methods for speed prediction

Also Published As

Publication number Publication date
CN101438335B (zh) 2011-09-21
CN102289936B (zh) 2014-08-06
AU2007224206A1 (en) 2007-09-13
CN102394008B (zh) 2015-01-07
WO2007103180A2 (fr) 2007-09-13
CN102394009A (zh) 2012-03-28
ES2386529T3 (es) 2012-08-22
EP2278573B1 (fr) 2012-05-16
JP2009529187A (ja) 2009-08-13
CN102394008A (zh) 2012-03-28
EP2278573A1 (fr) 2011-01-26
CN102289936A (zh) 2011-12-21
WO2007103180A3 (fr) 2007-12-06
CN102289935B (zh) 2015-12-16
ES2373336T3 (es) 2012-02-02
CN102289935A (zh) 2011-12-21
CN102254434A (zh) 2011-11-23
CN102394009B (zh) 2014-05-14
CN102254434B (zh) 2013-05-01
EP1938296A2 (fr) 2008-07-02
ATE523869T1 (de) 2011-09-15
CN101438335A (zh) 2009-05-20

Similar Documents

Publication Publication Date Title
EP1938296B1 (fr) Évaluation des conditions de circulation routière au moyen de données provenant de sources de données mobiles
US7706965B2 (en) Rectifying erroneous road traffic sensor data
US10403130B2 (en) Filtering road traffic condition data obtained from mobile data sources
US7831380B2 (en) Assessing road traffic flow conditions using data obtained from mobile data sources
US8160805B2 (en) Obtaining road traffic condition data from mobile data sources
US9280894B2 (en) Filtering road traffic data from multiple data sources
US20070208501A1 (en) Assessing road traffic speed using data obtained from mobile data sources
US20070208493A1 (en) Identifying unrepresentative road traffic condition data obtained from mobile data sources
WO2008021551A2 (fr) Informations de flux de circulation routière représentatives basées sur des données historiques
US10719899B1 (en) Method and apparatus for utilizing estimated patrol properties and historic patrol records
US11781883B1 (en) Method and apparatus for utilizing estimated patrol properties and historic patrol records

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20080331

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

17Q First examination report despatched

Effective date: 20081008

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: INRIX, INC.

TPAC Observations filed by third parties

Free format text: ORIGINAL CODE: EPIDOSNTIPA

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

TPAC Observations filed by third parties

Free format text: ORIGINAL CODE: EPIDOSNTIPA

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

TPAC Observations filed by third parties

Free format text: ORIGINAL CODE: EPIDOSNTIPA

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602007016999

Country of ref document: DE

Effective date: 20111117

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20110907

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2373336

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20120202

LTIE Lt: invalidation of european patent or patent extension

Effective date: 20110907

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20111208

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 523869

Country of ref document: AT

Kind code of ref document: T

Effective date: 20110907

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120107

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20120109

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

26N No opposition filed

Effective date: 20120611

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602007016999

Country of ref document: DE

Effective date: 20120611

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120331

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120302

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120331

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120331

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20111207

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110907

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120302

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070302

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 10

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20170327

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20170324

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20170328

Year of fee payment: 11

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602007016999

Country of ref document: DE

Representative=s name: PATENTANWAELTE LAMBSDORFF & LANGE, DE

Ref country code: DE

Ref legal event code: R082

Ref document number: 602007016999

Country of ref document: DE

Representative=s name: LAMBSDORFF & LANGE PATENTANWAELTE PARTNERSCHAF, DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180302

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180331

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20190904

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180303

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240306

Year of fee payment: 18

Ref country code: GB

Payment date: 20240307

Year of fee payment: 18