Each member will define based on these procedures more detailed ones taking into account features of the equipment deployed and especially available interfaces for logging of specific events. The description of the procedures assumes that the intended accuracy for timing is only on the level of seconds and not for fraction of seconds. This permits a comparability of the measured data on a European level to compare pears with pears and apples with apples only. In some cases it might be necessary to calibrate the measured data to allow a direct comparison of the achieved results. As a magnitude of data will be produced in all member states, templates are provided in Annex II with an overview about the excel sheets used for later evaluation and comparison of the test results. However it is not required nor recommended to collect in the member state data in a specific format nor with a specific application. It is only important to provide collected data on European level in a specific format to allow consolidation. The table below provides a mapping between KPI and applicable procedure. ID of KPI Name of KPI Applicable test procedure KPI_001a Number of automatically initiated eCalls Test procedure 1 KPI_001b Number of manually initiated eCalls Test procedure 1 KPI_002a Success rate of completed eCalls using 112 Test procedure 1 KPI_002b Success rate of completed eCalls using long number Test procedure 1 KPI_003 Success rate of received MSDs Test procedure 2 KPI_004 Success rate of correct MSDs Test procedure 3 KPI_005 Duration until MSD is presented in PSAP Test procedures 2 and 12 KPI_006 Success rate of established voice transmissions Test procedure 1 KPI_007a Duration of voice channel blocking Test procedures 5 and 12 KPI_007b Duration of voice channel blocking: automatic retransmission of MSD Test procedures 5 and 12 KPI_008 Time for call establishment Test procedure 12 KPI_009 Accuracy of position Test procedure 9 KPI_010 Number of usable satellites Test procedure 6 KPI_011 Geometric dilution of precision Test procedure 7
of the HDOP varies with geographic location only a little, VDOP value is changing a lot with geographic latitude. The latitude of ± 56 ° VDOP reaches its minimum and with latitude increasing VDOP significantly increases. This error increase at higher latitudes is due to the fact that after crossing the latitude, which is equal to the track inclination, already below the overhead satellites, culminating in increasingly lower elevations. Three-dimensional positioning error almost follows track of the dominant height error. Figure 9: Satellites position and movement over time Using simulation tools there is possible to model various geometric distribution of satellites typical example for different latitudes. There is possible to simulate conditions of high and low levels of DOP indicators. For each of the satellites there is possible to simulate the signal level, or to switch off the satellite which leads to a situation of broadcast only n satellites. The combination of these settings allows assembling many different test scenarios for testing GNSS signal reception, depending on the constellation of satellites. Figure 10: Display of received signal levels Figure 11: Display of setting concerning signal levels This feature can also be used to simulate a particular constellation of GNSS satellites in the defined period of time in the past. This includes re-induction (replay) of the situation that leads to the application or device error. This is possible for the GPS signal, which is governed by the so-called GPS weeks. For each GPS week almanac generated file that defines the current position of the GPS satellites. This information is freely available in the internet. This file is imported into the simulation software tools and the position of the satellite after that corresponds to the required time. GNSS signal emulation Process through the generation of GNSS signal in the simulator is in several steps (and is shown on the picture below): Operator in the simulation program sets the course (manually or pre-prepared set of positional data, such as NMEA data) and all parameters of the generated signal (e.g. number
L1 1 0 M ??? L2 1 1 M ??? Table 5: Overview of Greek laboratory test scenarios Code Location Number of vehicles involved Number of vehicles in roaming eCall initiation Number of tests H1 Attiki Odos Arterial Highway of Attiki 2 2 M 100 H2 E65 highway, Athens - Korinthos 2 2 M 100 U1 Urban roads, Athens city centre 2 2 M 100 R1 Rural road, Rafina – Oropos 2 2 M 100 Table 6: Overview of Greek real traffic test scenarios Preconditions: 1) Vehicle equipment IVS and communication to the PSAP Manual initiation of the eCall 2) Mobile network Dialling E112 3) PSAP 3GPP installed Decoding and visualizing MSD content possible Voice connection to the vehicle possible Test Procedure: The driver manually initiates an at various positions; in different traffic environments (see Table 4 above). At several selected locations along the road, representative of the area and with possible low GPS coverage, the driver stops the vehicle at the roadside and manually activates eCall. Log files are stored in the vehicle and in the PSAP and both the driver and the PSAP operator complete a subjective questionnaire containing a standardized value scale for the evaluation after the end of each eCall.