Commission Delegated Regulation (EU) 2017/79 of 12 September 2016 establishing detailed technical requirements and test procedures for the EC type-approval of motor vehicles with respect to their 112-based eCall in-vehicles systems, of 112-based eCall in-vehicle separate technical units and components and supplementing and amending Regulation (EU) 2015/758 of the European Parliament and of the Council with regard to the exemptions and applicable standards (Text with EEA relevance. )

2.2.5.   Cold start time to first fix test.

• 2.2.5.1. Prepare and turn on the eCall. By means of developer software, make sure that GNSS module is set to receive Galileo and GPS signals.

• 2.2.5.2. Delete all position, velocity, time, almanac and ephemeris data from the GNSS receiver.

• 2.2.5.3. Set up the simulator according to the simulator user guide. Initialize simulator script with the parameters, given in Table 2 for Galileo and GPS signals with signal level minus 130 dBm.

• 2.2.5.4. By means of a stopwatch, measure time interval between signal simulation start and the first navigation solution result.

• 2.2.5.5. Conduct test procedures according to 2.2.5.2 – 2.2.5.4 at least 10 times.

• 2.2.5.6. Calculate average time to first fix in cold start mode based on measurements for all eCall samples, provided for the test.

• 2.2.5.7. The test result is considered to be positive, if average values of time to first fix calculated as described in 2.2.5.6, do not exceed 60 seconds for signal level down to minus 130 dBm for all the simulated signals.

• 2.2.5.8. Repeat test procedure according to 2.2.5.1 – 2.2.5.5 with signal level minus 140 dBm.

• 2.2.5.9. The test result according to 2.2.5.8 is considered to be positive, if average values of time to first fix, calculated as described in 2.2.5.6 do not exceed 300 seconds for signal level down to minus 140 dBm for all the simulated signals.

2.2.6.   Test of re-acquisition time of tracking signals after block out of 60 seconds.

• 2.2.6.1. Prepare and turn on the eCall according to operational manual. By means of the developer software, make sure that GNSS receiver is set up to receive Galileo and GPS signals.

• 2.2.6.2. Set up the simulator according to the simulator user guide. Initialize simulator script with the parameters, given in Table 2 for Galileo and GPS signals with signal level minus 130 dBm.

• 2.2.6.3. Wait for 15 minutes and make sure the GNSS receiver has calculated eCall position.

• 2.2.6.4. Disconnect the GNSS antenna cable from the eCall and connect it again after time interval of 60 seconds. By means of stopwatch, determine time interval between cable connection moment and restoration of satellites tracking and calculation of the navigation solution.

• 2.2.6.5. Repeat test procedure according to 2.2.6.4 at least 10 times.

• 2.2.6.6. Calculate average value of re-acquisition time of satellite tracking signals by the eCall for all performed measurements and all eCall samples provided for the test.

• 2.2.6.7. The test result is considered to be positive, if average values of re-acquisition time after block out of 60 seconds measured as described in 2.2.6.6, do not exceed 20 seconds.

2.2.7.   Test of GNSS receiver sensitivity in cold start mode, tracking mode, and re-acquisition scenario.

• 2.2.7.1. Turn on the vector network analyser. Calibrate the vector network analyser according to its operational manual.

• 2.2.7.2. Set up the diagram according to Figure 4.

Figure 4

Diagram of path calibration

Image omitted; see official source

Text of image

Attenuator 2

0…110 dB

Low-noise amplifier

Attenuator 1

0…11 dB

Vector network analyzer

• 2.2.7.3. Set zero signal path attenuation on attenuators. Measure the frequency response for a given signal path in the E1/L1 band of Galileo/GPS, respectively. Record the average path transmission factor in [dB] in this frequency band.

• 2.2.7.4. Assemble the circuit shown in Figure 5.

Figure 5

Arrangement for evaluation of GNSS module sensitivity

Image omitted; see official source

Text of image

Signals simulator

eCall

Power supply

Personal Computer

Low-noise amplifier

Attenuator 2

0…110 dB

Attenuator 1

0…11 dB

• 2.2.7.5. Prepare and turn on eCall according to operational manual. By means of developer software make sure that GNSS receiver is set to receive Galileo and GPS signals. Clear the GNSS receiver RAM such that the ‘cold’ start mode of the GNSS receiver of the eCall is achieved. Check that the position, velocity and time information is reset.

• 2.2.7.6. Prepare GNSS signals simulator according to its operation manual. Start Galileo and GPS signals simulation script, with parameters given in Table 2. Set output power level of the simulator to minus 144 dBm.

• 2.2.7.7. By means of a stopwatch, measure time interval between signal simulation start and the first navigation solution result.

• 2.2.7.8. Set the signal path attenuation on attenuators such that the signal on eCall antenna input is equal to minus 155 dBm.

• 2.2.7.9. By means of a stopwatch, verify that the eCall still provides navigation solution for at least 600 seconds.

• 2.2.7.10. Set the signal path attenuation on attenuators such that the signal on eCall antenna input is equal to minus 150 dBm.

• 2.2.7.11. Disconnect the GNSS antenna cable from the eCall and connect it again after time interval of 20 seconds.

• 2.2.7.12. By means of stopwatch, determine time interval between cable connection moment and restoration of satellites tracking and calculation of the navigation solution.

• 2.2.7.13. The test result is considered to be positive in case:

• — the value of time to first fix in ‘cold’ start mode, as measured in 2.2.7.7, do not exceed 3 600 seconds at signal level on the antenna input of the eCall of minus 144 dBm in all the eCall samples;

• — the GNSS navigation solution is available for at least 600 seconds at signal level on the antenna input of the eCall of minus 155 dBm as measured in 2.2.7.9 in all the eCall samples;

• — and re-acquisition of GNSS signals and calculation of the navigation solution at signal level on the antenna input of the eCall of minus 150 dBm is possible and time interval measured in 2.2.7.12 does not exceed 60 seconds in all the eCall samples.

ANNEX VII

In-vehicle system self-test

1. Requirements

• 1.1. The following requirements apply to vehicles with eCall in-vehicle system installed, STUs and (optionally for) components.

• 1.2. Performance requirements

• 1.2.1. The eCall system shall carry out a self-test at each system power-up.

• 1.2.2. The self-test function shall monitor at least the technical items listed in the Table.

• 1.2.3. A warning in form of either a visual tell-tale or a warning message in a common space shall be provided in case a failure is detected by the self-test function.

• 1.2.3.1. It shall remain activated while the failure is present.

• 1.2.3.2. It may be cancelled temporarily, but shall be repeated whenever the ignition or vehicle master control switch is being activated.

• 1.3. Documentation requirements

• 1.3.1. The manufacturer shall provide the technical service and the type-approval authority with documentation in accordance with the Table, which shall contain for each item the technical principle applied to monitor the item.

Table

Template of information for self-test function

Item	Technical principle applied for monitoring
eCall ECU is in working order (e.g. no internal hardware failure, processor/memory is ready, logic function in expected default state)
Mobile network antenna is connected
Mobile network communication device is in working order (no internal hardware failure, responsive)
GNSS antenna is connected
GNSS receiver is in working order (no internal hardware failure, output within expected range)
Crash control unit is connected
No communication failures (bus connection failures) of relevant components in this table
SIM is present (this item only applies if a removable SIM is used)
Power source is connected
Power source has sufficient charge (threshold at the discretion of the manufacturer)

2. Test procedure

2.1.   Self-test function verification test

• 2.1.1. The following test shall be performed, separately for each of the items listed in the Table, on the vehicle with an eCall in-vehicle system installed in accordance with Article 5, on the STU in accordance with Article 7 or on the component, that is made part of a complete system for the purpose of the test, in accordance with Article 6.

• 2.1.2. Simulate a malfunction of the eCall system by introducing a critical failure monitored by the self-test function according to the technical documentation provided by the manufacturer. The manufacturer shall provide a list of the checks and a description of how to trigger them.

• 2.1.3. Power the eCall system up (e.g. by switching the ignition ‘on’ or activating the vehicle's master control switch, as applicable) and verify that the malfunction indicator illuminates shortly afterwards.

• 2.1.4. Power the eCall system down (e.g. by switching the ignition ‘off’ or deactivating the vehicle's master control switch, as applicable) and restore it to normal operation.

• 2.1.5. Power the eCall system up and verify that the malfunction indicator does not illuminate or extinguishes shortly after illuminating initially.  For the failures which cannot be simulated or injected by the technical service, the manufactures shall provide a documentation describing the test procedure and the test results to the technical service.

3. Modification of type of 112-based eCall in-vehicle system or STU

• 3.1. When the manufacturer submits an application for revision or extension of an existing type-approval for the purpose of including an alternative GNSS antenna, electronic control unit, mobile network antenna and/or power source components, no retesting of 112-based eCall in-vehicle system components shall be required for the purpose of fulfilling the requirements of this Annex, provided that those type-approved components possess at least the same functional features and that they are covered by this Annex in accordance with Article 6(3).

4. Technical requirements to enable periodic roadworthiness tests

4.1.   Purpose

The purpose shall be to verify the following features of the eCall system:

• (a) its correct operational status, by visual observation of the failure warning signal status following the activation of the vehicle master control switch and any bulb check. Where the failure warning signal is only displayed in a common space (the area on which two or more information functions or symbols may be displayed, but not simultaneously), it must be checked first that the common space is functional prior to the failure warning signal status check;

• (b) the correct accuracy of the Minimum Set of Data (by generating and reading current MSD), the correct function and condition of the eCall components and the backup-battery (if applicable), by the use of an electronic vehicle interface;

• (c) the software integrity, by external verification of version information, hash values and system configurations against reference data;

• (d) the correct functionality of the voice communication, by performing an audio echo and speaker test using the vehicle interface.

4.2.   Requirements

• 4.2.1.The 112-based eCall in-vehicle system shall be able to provide the information to perform the methods of testing specified in Section 3, point 7.13, of Annex I to Directive 2014/45/EU using the electronic vehicle interface.

• 4.2.2.The manufacturer shall make available the technical information, which shall contain the instructions for reading out the information or performing the checks related to each item specified in Section 3, point 7.13, of Annex I to Directive 2014/45/EU.

4.3.   Test procedure

• 4.3.1.It shall be verified that the information related to each item specified in Section 3, point 7.13 of Annex I to Directive 2014/45/EU, can be read out from the eCall system using the electronic vehicle interface according to the instructions of the manufacturer.

• 4.3.2.It shall be verified that an echo and speaker test can be performed to check the correct functionality of the voice communication via the vehicle interface.

ANNEX VIII

Technical requirements and test procedures related to privacy and data protection

PART I

Procedure for verifying the lack of traceability of an eCall in-vehicle system or STU

1. Purpose

• 1.1. This test procedure is to ensure that a 112-based eCall in-vehicle system or STU is not traceable and is not subject to any constant tracking in its normal operational status.

2. Requirements

• 2.1. The 112-based eCall in-vehicle system or STU is not available for communication with the PSAP or at least does not automatically respond if the PSAP initiates the communication after expiry of the eCall timer T9 (1 hour).

3. Test conditions

• 3.1. The following tests shall be performed on a representative arrangement of parts (without a vehicle body).

• 3.2. Before performing the test, ensure that:

• (a) one of the connection procedures specified in point 2.7 of Annex I, as agreed between the technical service and the manufacturer, will be applied for any test eCall;

• (b) the dedicated PSAP test point is available to receive an eCall emitted by the 112-based system;

• (c) the vehicle ignition or master control switch is activated;

• (d) any TPS or added-value service system is disabled.

4. Test method

• 4.1. Perform a test eCall by applying a manual trigger of the system.

• 4.2. Verify that a call was established with the PSAP test point by a record of the PSAP test point showing that it received a call or by a successful voice connection to the PSAP test point.

• 4.3. Clear down the eCall using the appropriate PSAP test point command (e.g. hang up).

• 4.4. Leave the 112-based eCall IVS switched on and wait for at least 63 min (1 hour + 5 % margin according to EN 16454 and EN 17240).

• 4.5. Via the PSAP test point, attempt to connect to the 112-based eCall IVS.

5. Assessment

• 5.1.The requirement is determined to have been passed if the 112-based eCall in-vehicle system is neither available for communication with the PSAP nor automatically responds to the call when the PSAP test point attempts to connect after expiry of the eCall timer T9 (1 hour).

• 5.2.The establishment of connection with the 112-based eCall IVS or the automatic answering to the call when the PSAP test point initiates the communication constitute a failure.

PART II

Procedure for verifying the length of time an eCall log file is stored by the eCall in-vehicle system or STU

1. Purpose

• 1.1. This test procedure aims to ensure that personal data processed pursuant to Regulation (EU) 2015/758 is not retained by the eCall in-vehicle system longer than necessary for the purpose of handling the emergency situation and is fully deleted as soon as no longer necessary for that purpose.

• 1.2. This is to demonstrate the automatic deletion by proving that eCall log files are not kept beyond 13 hours from the point of initiating an eCall.

2. Requirements

• 2.1. When interrogated, the eCall in-vehicle system or STU shall not maintain any record of an eCall in its memory beyond 13 hours from the point of initiating an eCall.

3. Test conditions

• 3.1. The Technical Service shall be facilitated to have access to the part of the system where the eCall log files are stored in the IVS.

• 3.2. The following test shall be performed on a representative arrangement of parts.

• 3.3. Before performing the test, ensure that:

• (a) one of the connection procedures defined in point 2.7 of Annex I, as agreed between the technical service and the manufacturer, will be applied for any test eCall;

• (b) the dedicated PSAP test point is available to receive an eCall emitted by the 112-based system;

• (c) the vehicle ignition or master control switch is activated; and

• (d) any TPS or added-value service system is disabled.

4. Test Method

• 4.1. Perform an eCall by applying a manual trigger of the system.

• 4.2. Verify that a call was established with the PSAP test point by a record of the PSAP test point showing that it received a call or by a successful voice connection to the PSAP test point.

• 4.3. Clear down the eCall using the appropriate PSAP test point command (e.g. hang up).

• 4.4. 13 hours after an eCall has been placed, the technical service tester shall be facilitated with access to where the eCall log files are stored in the IVS. This will involve the potential to download from the IVS any log files so that they can be viewed by the tester.

5. Assessment

• 5.1. The requirement is determined to have been passed if no log files are present in the eCall in-vehicle system memory.

• 5.2. The presence of a log file pertaining to an eCall that has occurred more than 13 hours ago constitutes a failure.

PART III

Procedure for verifying the automatic and continuous removal of data in the internal memory of an eCall in-vehicle system or STU

1. Purpose

• 1.1. This test procedure aims to ensure that personal data is only used for the purpose of handling the emergency situation and is automatically and continuously removed from the internal memory of the eCall in-vehicle system or STU.

• 1.2. This is to be proved by demonstrating that in the internal memory of the 112 based eCall in-vehicle system or STU, maximum of last three locations of the vehicle are retained.

2. Requirements

• 2.1. When interrogated, the eCall in-vehicle system or STU shall not maintain more than three recent locations of the vehicle.

3. Test conditions

• 3.1. The technical service shall be facilitated to have access to the part of the system where the vehicle location data are stored in the IVS internal memory.

• 3.2. The following test shall be performed on a representative arrangement of parts.

• 3.3. Before performing the test, ensure that:

• (a) one of the connection procedures defined in point 2.7 of Annex I, as agreed between the technical service and the manufacturer, will be applied for any test eCall;

• (b) the dedicated PSAP test point is available to receive an eCall emitted by the 112-based system;

• (c) the vehicle ignition or master control switch is activated; and

• (d) any TPS or added-value service system is disabled.

4. Test Method

• 4.1. Perform an eCall by applying a manual trigger of the system.

• 4.2. Verify that a call was established with the PSAP test point by a record of the PSAP test point showing that it received a call or by a successful voice connection to the PSAP test point.

• 4.3. Clear down the eCall using the appropriate PSAP test point command (e.g. hang up).

• 4.4. The technical service tester shall be facilitated with access to where the vehicle location data are stored in the IVS internal memory. This will involve the potential to download from the IVS any stored locations so that they can be viewed by the tester.

5. Assessment

• 5.1. The requirement is determined to have been passed if maximum of last three locations are present in the eCall in-vehicle system memory.

• 5.2. The presence of more than three locations constitutes a failure.

PART IV

Procedure for verifying the non- exchange of personal data between an eCall in-vehicle system or STU and third party services systems

1. Purpose

• 1.1. This test procedure shall ensure that the 112-based eCall in-vehicle system or STU and any additional system functionality providing TPS eCall or an added-value service are designed in such a way that no exchange of personal data between them is possible at any time.

2. Requirements

• 2.1. The following requirements apply to eCall in-vehicle systems or STUs that shall be used in conjunction with a TPS eCall in-vehicle system functionality.

• 2.2. Performance requirements

• 2.2.1. There is no exchange of personal data between the 112-based eCall in-vehicle system or STU and any additional system functionality providing TPS eCall or an added-value service.

• 2.2.2. Following an eCall made via the 112-based eCall in-vehicle system or STU, no log of this eCall shall be recorded in the memory of the TPS eCall or added-value service system.

3. Test conditions

• 3.1. The following tests shall be performed either on a vehicle with an eCall in-vehicle system installed or on a representative arrangement of parts.

• 3.2. The TPS system shall be disabled for the duration of the eCall.

• 3.2.1. Before performing the test, ensure that:

• (a) one of the connection procedures defined in point 2.7 of Annex I, as agreed between the technical service and the manufacturer, will be applied for any test eCall;

• (b) the dedicated PSAP test point is available to receive an eCall emitted by the 112-based system;

• (c) the vehicle ignition or master control switch is activated; and

• (d) any TPS or added-value service system is disabled.

• 3.2.2. Perform a test call by applying a manual trigger of the system (push mode) with the TPS disabled.

• 3.2.3. Verify that a call was established with the PSAP test point by a record of the PSAP test point showing that it received a call initiation signal or by a successful voice connection to the PSAP test point.

• 3.2.4. Clear down the test call using the appropriate PSAP test point command (e.g. hang up).

• 3.2.5. If the call attempt of the 112-based system fails during the test, the test procedure may be repeated.

• 3.3. The lack of a log file in the TPS system shall be verified via access to the part of the system where eCall log files are stored.

• 3.3.1. The Technical Service tester shall be facilitated with access to where the eCall log files are stored in the IVS. This will involve the potential to download from the IVS any log files so that they can be viewed by the tester.

• 3.3.2. The requirement is determined to have been passed if no log files are present in the TPS system in-vehicle system memory.

• 3.3.3. The presence of a log file in the TPS system pertaining to an eCall that has occurred via the 112-based system constitutes a failure.

4. Test method

• 4.1.Perform a test eCall by applying a manual trigger of the system.

• 4.2.Verify that a call was established with the PSAP test point by a record of the PSAP test point showing that it received a call or by a successful voice connection to the PSAP test point.

• 4.3.Clear down the eCall using the appropriate PSAP test point command (e.g. hang up).

• 4.4.If the call attempt of the 112-based system fails during the test, the test procedure may be repeated.

• 4.5.The technical service tester shall be facilitated with access to where the eCall log files are stored in the IVS. This will involve the potential to download from the IVS any log files so that they can be viewed by the tester.

• 4.6.The lack of a log file in the TPS system shall be verified via access to the part of the system where eCall log files are stored.

5. Assessment

• 5.1.The requirement is determined to have been passed if no log files are present in the TPS system in-vehicle system memory.

• 5.2.The presence of a log file in the TPS system pertaining to an eCall that has occurred via the 112-based system constitutes a failure.

ANNEX IX

Classes of vehicles referred to in Article 2

Armoured vehicles of categories M1 and N1, as defined in point 5.2 of Part A of Annex II to Directive 2007/46/EC, equipped with armoured security glazing class BR 7 according to the classification under European standard EN 1063:2000 (Test and Classification for Ballistic Security Glazing) and with body parts complying with European standard EN 1522:1999 (Bullet Resistance in Windows, Doors, Shutters and Blinds), where those vehicles, due to their special purpose, cannot meet the requirements of Regulation (EU) 2015/758 and of this Regulation.

ANNEX X

Test procedure for the verification of the performance of the back-up power supply

1. Purpose

The purpose of this test is to make sure that the eCall in-vehicle system or eCall STU is capable to communicate for the period specified in point 2.

2. Requirements

The eCall system or eCall STU shall be operable for a period of at least 5 minutes in voice communication mode followed by 60 minutes in call-back mode (idle mode, registered in the network) followed by another period of at least 5 minutes in voice communication mode.

3. Test conditions

The following verification test shall be performed on an eCall STU that has been subjected to the high-severity deceleration test according to Annex I.

If the eCall STU does not include the microphone(s) and speaker(s) for the eCall system, then representative microphone(s) and speaker(s) shall be added to the test setup in order to execute the test from this Annex.

3.1.   Test method

• 3.1.1.Perform an eCall by applying a manual trigger of the system.

• 3.1.2.Verify that a call was established with the PSAP test point by a record of the PSAP test point showing that it received the call or by a successful voice connection to the PSAP test point.

• 3.1.3.Disconnect the main power source.

• 3.1.4.Read out any text for at least 5 minutes at the PSAP test point.

• 3.1.5.Clear down the eCall using the appropriate PSAP test point command (e.g. hang up).

• 3.1.6.Wait for 56 minutes after the call was ended.

• 3.1.7.Initiate a call from the PSAP test point to the eCall in-vehicle system.

• 3.1.8.If the call is automatically accepted, read out any text for at least 5 minutes at the PSAP test point, otherwise the test is finished.

3.2.   Assessment

• 3.2.1.The requirement is determined to have been passed if the eCall STU is capable to communicate for the required period, as specified in point 2.

• 3.2.2.The incapacity of the 112-based eCall in-vehicle system to communicate for the period referred to in point 2 constitutes a failure.

[^E0001]: Commission Implementing Regulation (EU) 2017/78 of 15 July 2016 establishing administrative provisions for the EC type-approval of motor vehicles with respect to their 112-based eCall in-vehicle systems and uniform conditions for the implementation of Regulation (EU) 2015/758 of the European Parliament and of the Council with regard to the privacy and data protection of users of such systems (see page 26 of this Official Journal).

[^E0002]: Regulation (EU) No 1025/2012 of the European Parliament and of the Council of 25 October 2012 on European standardisation, amending Council Directives 89/686/EEC and 93/15/EEC and Directives 94/9/EC, 94/25/EC, 95/16/EC, 97/23/EC, 98/34/EC, 2004/22/EC, 2007/23/EC, 2009/23/EC and 2009/105/EC of the European Parliament and of the Council and repealing Council Decision 87/95/EEC and Decision No 1673/2006/EC of the European Parliament and of the Council (OJ L 316, 14.11.2012, p. 12).’