PRE-DRIVE C2X Deliverable D0.3 Final report_20100929.pdf

More documents

Recommendations

Info

Final Report PRE-DRIVE C2X 29.9.2010 could cause a too low emission simulation while traffic congestion occurs. More aggressive driver models in future traffic simulators can help to get more realistic simulation results for the vehicle emissions in congested areas. Probably, these more realistic driver models will result in higher emissions when the V2X penetration rate is low. It would extend the scope of this report by far if the results of the application of the integrated simulation toolset to all selected applications were described here. They can be found in deliverable D2.3 “Complete Prototype System, including Hardware and Software components”. 2.3.3 WP3000 Prototyping/ integration The work of WP3000 aimed at the prototypical realisation of the common European architecture for vehicle-to-vehicle and vehicle-to-infrastructure communication for system demonstration and functional verification. The results of the work in WP3000 are described in the following. 2.3.3.1 Software Implementation PRE-DRIVE C2X has developed a platform which follows the common European architecture for vehicle-to-vehicle and vehicle-to-infrastructure communication developed together with COMeSafety. The components have been developed taking into consideration the needs of a robust prototype which is suitable for field operational testing and real environment. PRE-DRIVE C2X has developed software components (Figure 28) for field operational testing, for the integration of backend services and for system management. Figure 28: PRE-DRIVE C2X Software Platform Deliverable D0.3 Version 1.0 41 Final Report
Final Report PRE-DRIVE C2X 29.9.2010 This Software Middleware Platform is composed by several software components at the bottom are access technology drivers (i.e., IEEE 802.11p, WiFi, UMTS and Ethernet) and selected data sources (i.e., CAN, Sensors, and GPS). Connected to the access technologies is the NWT (Network and Transport) component that provides networking and routing functionalities, such as GeoNetworking and IPv6. On top of the NWT component, a set of “facilities” provide application support for messaging – CAM (Cooperative Awareness Messages) and DENM (Decentralized Environmental Notification Messages), for safety and traffic efficiency applications, and the so called BIM (Backend Integration Module) for business-related use cases. Other components are for storing of contextual information in an ITS station’s surrounding (i.e., the Local Dynamic Map, LDM) and facilitate the decoupling of the HMI from the applications (i.e., HMI support). In addition, some components like ‘Relevance checker’ and ‘Location referencing’ provide interfaces to use digital maps and to evaluate the relevance, .i.e., the importance, of transmitted information. All the facility components make use of OSGi, same as applications and management components do. Finally, security components mainly cover cryptographic protection and identity management. 2.3.3.2 Reference On-Board-Unit The reference On Board Unit (OBU) is composed by the following hardware components shown in Table 3. The technical detail of each component is reported in Deliverable D3.4 “Detailed report on the core components’ integration, functional verification and duplication results”. Application Unit (AU) Car PC [1] 11p Antenna [5] UMTS Antenna [6] UMTS Device GPS Device [3] Cables Monitor [2] CAN Gateway [4] Communication Unit (CCU) CALU‐M2‐PCMCIA‐ P4‐M Car‐PC Bare bone: ‐ 2 GHz processor ‐ 1 GB of RAM ‐ 160 GB of Hard Drive RM3‐5500 3dBi gain Surface Mount Antenna c/w 30cm cable and standard straight connector MGMR‐925/1800 Magnetic Mount Antenna EU GSM & DCS‐1800 Generic UMTS Device BU353 USB GPS Receiver (Sirf 3 chipset) Generic cables to connect the antennas to the device CTF7 – 7’’ TFT LCD monitor Peak USB can gateway PRE‐DRIVE C2X suppliers. Details of the different communication units are described in sections 2.3.3.3, 2.3.3.5 and 2.3.3.4. Table 3: List of Hardware Components Deliverable D0.3 Version 1.0 42 Final Report
Page 1 and 2: Deliverable D0.3 Final Report Versi
Page 3 and 4: Legal disclaimer PRE-DRIVE C2X 9/29
Page 5 and 6: PRE-DRIVE C2X 9/29/2010 Table of co
Page 7 and 8: PRE-DRIVE C2X 9/29/2010 1 Managemen
Page 9 and 10: PRE-DRIVE C2X 9/29/2010 With the po
Page 11 and 12: PRE-DRIVE C2X 9/29/2010 2.1.5 WP500
Page 13 and 14: Final Report PRE-DRIVE C2X 29.9.201
Page 51: Final Report PRE-DRIVE C2X 29.9.201
Page 103 and 104:
Final Report PRE-DRIVE C2X 29.9.201
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
PRE-DRIVE C2X 29.09.2010 6 Report o
Page 127 and 128:
PRE-DRIVE C2X 29.09.2010 6.1.5 E: S
Page 129 and 130:
PRE-DRIVE C2X 29.09.2010 6.1.8 H: U
Page 131:
PRE-DRIVE C2X 29.09.2010 3. MEDICAL
show all

PRE-DRIVE C2X Deliverable D0.3 Final report_20100929.pdf

Create successful ePaper yourself

Delete template?

Save as template?