PRE-DRIVE C2X Deliverable D0.3 Final report_20100929.pdf
PRE-DRIVE C2X Deliverable D0.3 Final report_20100929.pdf
PRE-DRIVE C2X Deliverable D0.3 Final report_20100929.pdf
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Final</strong> Report <strong>PRE</strong>-<strong>DRIVE</strong> <strong>C2X</strong> 29.9.2010<br />
<br />
D1.3: “Refinement and extension of the security architecture”<br />
D1.4: “Consolidated system and security architecture with input from the<br />
COMeSafety system architecture specification (version 2.0)”<br />
D1.5: “<strong>Final</strong> refinement of D1.4 with input from the COMeSafety system<br />
architecture specification (version 3.0)”<br />
These deliverables were elaborated and consolidated with the European ITS<br />
architecture for cooperative systems from COMeSafety. The results have been the<br />
basis for the work in WP3000.<br />
Moreover, the results have been significant input to standardisation documents in<br />
ETSI.<br />
Figure 12 shows how the cooperative systems and the ITS architecture activities fit<br />
together and how the results will be integrated in the ETSI standardisation process.<br />
<strong>PRE</strong>-<strong>DRIVE</strong> <strong>C2X</strong> as member of the COMeSafety Architecture Task Force<br />
cooperated amongst others with COMeSafety, COOPERS, SAFESPOT, CVIS and<br />
E-FRAME. Within WP1000 <strong>PRE</strong>-<strong>DRIVE</strong> <strong>C2X</strong> contributed to a common European<br />
ITS Communication Architecture.<br />
Figure 12: Overview how the cooperative systems and ITS architecture activities fit together<br />
All results of WP1000 are described in the deliverables mentioned above. In the<br />
following only some major aspects of the system architecture work are highlighted.<br />
First the system domains have been identified and described. Figure 13 represents<br />
the highest level of abstraction of the ITS architecture and thus it is provider<br />
independent. The ITS architecture can be used in different scenarios to adapt to<br />
different economic and regulatory conditions, facilitating a gradual introduction of<br />
ITS. Basically, a deployment scenario is a sub-set of the overall architecture created<br />
by a combination of the different sub-domains.<br />
<strong>Deliverable</strong> <strong>D0.3</strong> Version 1.0 24<br />
<strong>Final</strong> Report