Figure 1: Relationship of timing issues Overview of KPIs The following table gives an overview which part of the eCall-system will be evaluated via a KPI in which country as committed by the Member States within the DoW (X = will be tested, (X) = will be tested if possible, -- = will not be tested) or between member states for cross border respective ERA GLONASS tests. The table describes all KPIs which are applicable in any of the participating member states. Every member state has selected those KPIs which are appropriate for each single Member State to be evaluated according to their original planning and resource calculation for the HeERO project. Member States, where KPI is evaluated I
Terminal control functions Annex – Member States test characteristics Croatia In General The primary aim of the Croatian eCall Pilot is to test and validate the eCall performance and operation throughout the eCall chain, from both technological and Standard Operation Procedures' (SOPs) aspects. The Croatian eCall testing scenarios comprises the following testing scenario groups: eCall components and chain laboratory testing and verification (T&V) scenarios eCall communication performance and operation testing and verification (T&V) scenarios in real network eCall SOPs testing and verification (T&V) scenarios position estimation for eCall testing and verification (T&V) scenarios Detailed description of testing scenarios expected to be deployed within the Croatian eCall Pilot is given in the tables below. Figure 3: Croatian test scenarios Testing environment The over-all chain will be tested in the Ericsson Nicola Tesla (ENT) eCall laboratory. The necessary pre-requisite is the full component compliance with the eCall standards. The eCall initiation will be performed according the particular scenario set-up, as outlined earlier in this document. All Group 1 KPIs (KPI1 - KPI5) will be measured and observed simultaneously during the T&V procedure. Measurement procedures for the related KPIs are outlined below. They apply to planned scenarios L1 - L7.
ID number (incremental counter) of the eCall Manual/automatic trigger activation T0_IVS – incident detected T1_IVS – IVS start sending the eCall MSD contents Transmission attempts T2_IVS – channel is active and driver and operator communication established T3_IVS – Voice connection is ended eCall communication OK/NOK TELECOM OPERATOR T0_MNO – the eCall reaches the 112 telecom operator network T1_MNO – the eCall flag is managed PSAP VARESE T0_PSAP – the eCall reaches the PSAP T1_PSAP – the MSD reaches the PSAP T2_PSAP – the processed MSD is being presented to the PSAP Operator T3_PSAP – voice channel is active and operator can communicate with the driver T4_PSAP – VIN has been decoded with EUCARIS tool T5_PSAP – the PSAP alerts (is ready to alert) the emergency agencies KPI- Analysis on MSD transmission time: Minimum, Maximum and Average transmission time for the MSD correctly received at PSAP Distribution of the MSD transmission time Number of non-successful MSD transmission attempt (longer than [20 sec] maximum) Start time for MSD transmission: when the IVS starts to send the SYNC signal End time: when the CRC has been detected as correct by the PSAP modem