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

More documents

Recommendations

Info

Final Report PRE-DRIVE C2X 29.9.2010 The work done in the first three parts of WP2000 is documented in Deliverable D2.1 “Description of user needs and requirements, and evaluation of existing tools”. 2.2.2.4 Overall simulation tool set architecture Parallel to these efforts, the work on the “Overall simulation tool set architecture” was carried out. The work was performed by several partners, again with great experience in this field. Mostly, the interfaces of available tools were described in accordance with the required data flows for the comprehensive tool set. This work is documented in the deliverable D2.2 “Description of overall simulation system architecture”. Work on the implementation and adaption of the available tools started in parallel to the architecture activities. Apart from the work in the parallel activities dealing with communication, traffic and environmental models, some general issues were addressed. A scheme was defined based on the different levels of detail that are required for the various types of application of the tool set. Since the level of detail will vary largely depending on the spatial and temporal size of a scenario of interest, the overall tool set must be able to adequately treat such levels. Some examples were defined, reaching from the detailed analysis of an intersection in a time-critical application (e.g. a safety relevant use case) up to the determination of C2X effects on a large scale. 2.2.2.5 Simulation of communication, simulation of traffic and safety effects, simulation of environmental effect from traffic The detailed work here comprises software adapting, creation and/or adaptation of interfaces and also the investigation of new approaches (e.g. statistical approach for communication simulation). In WP2500 “Simulation of communication”, the various relevant communication modes (e.g. DSRC, LTE) were introduced into the simulation modules. In WP2600 “Simulation of traffic and safety effects”, the software was adapted and also simulation scenarios were defined. WP2700 “Simulation of environmental effects” worked mainly on improving emission data; the focus was on the official data used in the Handbook of Emission Factors (HBEFA). This resulted in a data basis which is compliant with all sources relevant for assessment of traffic related emissions. All in all, the work was targeted towards the application of the simulation tools for the defined use cases. Two aspects were agreed to be of special interest: showing the ability to simulate the use cases and also providing input to the final event of the project. The major part of the work went into WP 2500 “Simulation of communication”, where implementation and analysis of communication technology based on IEEE 802.11p in different simulators (e.g. NS-2, OPNET) were done. Such simulation applications were performed for different scenarios (urban and motorway) to test and validate the simulation toolset and the simulations, which are part of it. This also provided insights into the communication behavior (e.g. about antennas). In WP2600, some of the simulations took place as well as the set-up of realistic scenarios for the test and the later validation of the integrated tool. Integration work between WP2500 and WP2600 mainly included VSimRTI to couple the simulators, which also means that the respective interfaces were created. The Deliverable D0.3 Version 1.0 7 Final Report
Final Report PRE-DRIVE C2X 29.9.2010 major simulators used for these tasks were SUMO, VISSIM on the traffic side and NS-2 and a MatLab simulation (IMEC) for the communication side. In WP2700, preparatory steps for the validation were carried out, along with the testing and cross-check of different models (TUG and TNO). 2.2.2.6 Integration and validation In a last step of work within WP2000, the combined simulators were used for different applications. On the one hand, use cases were evaluated and on the other hand, simulations provided input data for the test bench in WP3000. To this end, suitable scenarios were defined, implemented and then served as input to establish the effects of C2X use cases. The results of the work done in parts 4 to 8 of work package WP2000 is documented in Deliverable D2.3 “Description of communication, traffic and environmental models and their integration and validation”. 2.2.3 WP3000 Prototyping/ integration This work package aimed at the prototypical realisation of the common European architecture for vehicle-to-vehicle and vehicle-to-infrastructure communication as specified in WP1000 for system demonstration and functional verification. The first objective to be reached by WP3000 was to identify the hard- and software components necessary for the envisaged PRE-DRIVE C2X system prototype and to create the respective specifications. Deliverable D3.1 “Detailed selection procedure description of hardware and software components and related specifications of the selected ones” describes the selection procedure for these components and gives corresponding specifications for the implementation of the PRE-DRIVE C2X architecture. This procedure includes, as a first step, the investigation of already existing systems, demonstrators and components that were developed within previous or ongoing activities for their applicability in PRE-DRIVE C2X. The procedure was then extended with an analysis of their interoperability and potential for re-use that significantly speeded up the development of suitable prototypes for PRE-DRIVE C2X. Moreover, it identified and specified those components that are not yet available. In fact, other than previous projects in the domain of vehicular communications, PRE- DRIVE C2X demonstrated not only safety-related use cases based on C2Xcommunication, but also exhibited non-safety use cases (e.g. Backend Services) and validated the technology and its applications by including dedicated testing components. The results of this selection procedure showed that, while various basic components were already available, their integration and interoperability could not be granted automatically. In addition, components for the testing, for the backend service integration and for the system management were still missing and they needed to be developed from scratch. Furthermore, the HMI Device Provider Application, needed to interact with OEM proprietary HMIs, was not available. Finally effort had to be spent to extend the network card software interfaces and to develop common interfaces for data transport, networking, security as well as facility-related components. Deliverable D0.3 Version 1.0 8 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 17: Final Report PRE-DRIVE C2X 29.9.201
Page 69 and 70:
Final Report PRE-DRIVE C2X 29.9.201
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?