110 likes | 240 Views
Integrated Project Co-operative Systems for Road Safety “Smart Vehicles on Smart Roads” Tobias Schendzielorz TUM (Germany) tobias.schendzielorz@vt.bv.tum.de. SAFESPOT. T2.3.3 Data Fusion. Objective and Overview Status Further Steps for T2.3.3. Partners involved:.
E N D
Integrated Project Co-operative Systems for Road Safety “Smart Vehicles on Smart Roads” Tobias Schendzielorz TUM (Germany) tobias.schendzielorz@vt.bv.tum.de SAFESPOT
T2.3.3 Data Fusion • Objective and Overview • Status • Further Steps for T2.3.3 Partners involved: TUM, NAVTEQ, MIZAR, CRF, CSST, SODIT, PTV AG, IBEO
T2.3.3 Data Fusion - Objective • General Objective of Data Fusion… • …is the combination of data from multiple sensors (roadside and in-vehicle) as well as from external sources... • …in order to perform interferences that may not be possible from a single sensor or source alone.
T2.3.3 Data Fusion – Main Goals • Increasing the quality of data in terms of Reliability, Accuracy , and Consistency. • Providing information which can not be measured directly by a sensor. • Prioritising information. • Closing gaps of detection. The impact of a potential breakdown of single sensor can be mitigated.
T2.3.3 Data Fusion - Status • 5.3.1. Definition and Goals of Data Fusion • 5.3.2. Review on Models and Architectures of Data Fusion (based on the U.S. Joint Directors of Laboratories (JDL) Data Fusion Group) • 5.3.3. Lessons Learned from Other ITS Projects • (PReVENT ProFusion 1&2, PAROTO, INVENT) • 5.3.4. Proposed Levels of Data Fusion • 5.3.5. Further Steps within the Data Fusion
T2.3.3 Data Fusion - Status Proposed Model
T2.3.3 Data Fusion - Status • Kinds of Data Fusion: • Complementarythe information or data covers not the same area, objects or object attributes • Competitivesame entities are detected by different types of sensors or information sources. • Co-operativedata is achieved which is not possible to be detected by a sensors or because there is no sensor available
T2.3.3 Data Fusion – Further Steps TUM will provided an detailed work plan. Open Topics: • Will T2.3.3 be responsible for the specification of the RSU / MFO? (Hardware specifications, power supply…)
Thank you for your attention! Tobias Schendzielorz TUM (Germany) tobias.schendzielorz@vt.bv.tum.de SAFESPOT