Cross-Tests

For InterCor, the cross-tests were held as part of coordinated events called 'TESTFEST'.

Four TESTFESTs and one 'pre-TESTFEST' took place during the project:

  • • a TESTFEST in Dordrecht, the Netherlands (03-06 July 2017) to validate the ITS-G5 specifications
  • • a TESTFEST in Reims, France (23-26 April 2018) to validate the PKI specifications
  • • a pre-TESTFEST in Helmond, Netherlands (13-14 June 2018) focusing on GLOSA with hybrid communication
  • • a TESTFEST in London/Chatham, UK (8-11 October 2018) on hybrid communication
  • • a final TESTFEST in Antwerp, Belgium (25-28 March 2019), on the cross-border interoperability of C-ITS services with the "Connecting European Corridors conference" held after the TESTFEST.

Spotlight on TESTFEST#2: PKI - Reims, France, 23-26 April 2018

Presentation of the test site:

Thanks to the availability of InterCor's common PKI specifications (InterCor_A2.1c_v2), TESTFEST#2 PKI-Security took place in April 2018 at the University of Reims (URCA) and on the SANEF network. This was the first large-scale and successful security interoperability testing event organised for C-ITS on a European scale adhering to security standards and addressing both PKI and data message security interoperability. The event attracted a large number of external participants (23 participants from 10 countries), including members of other European projects and consortia such as C-Roads, SCOOP@F, CORRIDOR and the C2C consortium, thus enabling large-scale testing on a European scale.

Description of the scenarios and test cases:

The test context included five security test scenarios, several road events, various ITS-G5 equipment and a large number of PKIs. 12 RSU and 21 OBUo using ITS-G5 ETSI standards with different PKIs (interoperability with 9 PKIs) were tested.

Sequence of events:

Five scenarios were defined to test interoperability:

  1. 1. Verification of the signature of a message received from a foreign SSTI and signed with a valid AT;
  2. 2. Verification of the signature of a message received from a foreign TTISS and signed with an AT issued by a revoked foreign AA;
  3. 3. Verification of the signature of a message received from a foreign TSSI and signed with a valid AT, but an expired foreign Common InterCor_CRL;
  4. 4. Verification of the signature of a message received from a foreign TTISS and signed with an AT issued by an unapproved foreign ACR;
  5. 5. Verification of the signature of a message received from a foreign TSSI and signed by a valid AT with a new updated InterCor_CRL.

For the purposes of the test, URCA developed a tablet application to evaluate the events displayed on the vehicle HMI for each scenario. This application asked participants to indicate whether or not they had observed an event on the HMI throughout the road test. All the participants' responses were then collected in the test centre in order to produce statistics.

Presentation and validation of test results:

The tests carried out over 4 days can be considered as the first contribution to the validation process of InterCor's common PKI specifications as well as the European trust model defined in the EC certification policy. The involvement of 23 participants and 9 available PKIs during the test phase enabled large-scale testing of interoperability between InterCor and non-InterCor PKIs. Several tools were used to analyse the results and their relevance. Due to the large number of participants, certain difficulties arose, such as non-harmonised security implementations or the unavailability of relevant security data for the analysis. The tests also highlighted some major technical issues that were addressed later in the project to ensure interoperability (harmonisation of certificate signing and verification and management of multiple certificate revocation lists).

The recommendations from TESTFEST#2 highlight the importance of using security logs with relevant security KPIs and of carefully defining the methodology for analysing the results for TESTFEST#4. TESTFEST#2 also highlighted the need to implement security logs for all participants.