Search Legislation

Advanced Search

Commission Delegated Regulation (EU) 2017/79Show full title

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)

Help about what version

What Version

Help about UK-EU Regulation

Legislation originating from the EU

When the UK left the EU, legislation.gov.uk published EU legislation that had been published by the EU up to IP completion day (31 December 2020 11.00 p.m.). On legislation.gov.uk, these items of legislation are kept up-to-date with any amendments made by the UK since then.

Close

This item of legislation originated from the EU

Legislation.gov.uk publishes the UK version. EUR-Lex publishes the EU version. The EU Exit Web Archive holds a snapshot of EUR-Lex’s version from IP completion day (31 December 2020 11.00 p.m.).

Status:

This is the original version as it was originally adopted in the EU.
This legislation may since have been updated - see the latest available (revised) version

  1. Introductory Text

  2. Article 1.Subject matter

  3. Article 2.Classes of vehicles exempted from the requirement to be equipped with a 112-based eCall in-vehicle system

  4. Article 3.Multi-stage approval of special purpose vehicles

  5. Article 4.Definitions

  6. Article 5.Requirements and test procedures for EC type-approval of motor vehicles with regard to the installation of 112-based eCall in-vehicle systems

  7. Article 6.Requirements and test procedures for EC type-approval of 112-based eCall in-vehicle system components

  8. Article 7.Requirements and test procedures for EC type-approval of 112-based eCall in-vehicle STUs

  9. Article 8.Obligations of the Member States

  10. Article 9.Amendments to Regulation (EU) 2015/758

  11. Article 10.Entry into force and application

  12. Signature

    1. TABLE OF CONTENTS

    2. ANNEX I

      Technical requirements and procedures for testing the resistance of eCall in-vehicle systems to severe crashes (high-severity deceleration test)

      1. 1. Requirements

        1. 1.1. Performance requirements

          1. 1.1.1. The high-severity deceleration test of eCall in-vehicle systems, STUs and...

          2. 1.1.2. MSD emission and encoding: The eCall system or representative arrangement...

          3. 1.1.3. Incident time determination: The eCall system or representative arrangement shall...

          4. 1.1.4. Position determination: The eCall system or representative arrangement shall be...

          5. 1.1.5. Mobile network connectivity: The eCall system or representative arrangement shall...

      2. 2. Test procedure

        1. 2.1. Purpose of the high-severity deceleration test procedure

        2. 2.2. The following tests shall be performed on a representative arrangement...

          1. 2.2.1. A representative arrangement shall include all parts required by the...

          2. 2.2.2. This shall include the control module and the power source...

          3. 2.2.3. This shall include the external antenna for mobile communication.

          4. 2.2.4. The wiring harness may be represented only by the relevant...

        3. 2.3. Deceleration/acceleration procedure

          1. 2.3.1. The following conditions shall apply:

          2. 2.3.2. The tested parts shall be connected to the test fixture...

          3. 2.3.3. If additional brackets or fixtures are used as part of...

          4. 2.3.4. The eCall system shall be decelerated or accelerated in compliance...

          5. 2.3.5. The test pulse shall be within the minimum and maximum...

          6. 2.3.6. The parts referred to in point 2.2 shall be tested...

          7. 2.3.7. Description of the test pulse

            1. Figure Minimum and maximum curve of the test pulse (pulse corridor)...

        4. 2.4. Verification procedure

          1. 2.4.1. Verify that no cable connectors were unplugged during the event....

          2. 2.4.2. The performance requirements shall be verified by performing a test...

          3. 2.4.3. Before performing the test call, ensure that:

          4. 2.4.4. Perform a test call (push mode) by applying a trigger...

          5. 2.4.5. Verify each of the following items:

          6. 2.4.6. Clear down the test call using the appropriate PSAP test...

        5. 2.5. Positioning test procedure

          1. 2.5.1. The sustained functionality of the GNSS components shall be verified...

          2. 2.5.2. The ‘IVS location’ (φIVS, λIVS) shall be: The location contained...

          3. 2.5.3. The ‘true location’ (φtrue, λtrue) shall be:

          4. 2.5.4. The deviation between IVS location and true location, dIVS shall...

          5. 2.5.5. The positioning test procedure may be repeated if the eCall...

        6. 2.6. Antenna test procedure

          1. 2.6.1. If the connection procedure applied for the test call did...

          2. 2.6.2. Measure the voltage standing wave ratio,, of the external mobile...

            1. 2.6.2.1. The measurement shall be performed with a power meter, antenna...

            2. 2.6.2.2. If a power meter is used, shall be calculated using...

          3. 2.6.3. Verify that satisfies the specifications prescribed by the manufacturer for...

        7. 2.7. Connection procedures

          1. 2.7.1. Simulated Mobile Network Procedure

            1. 2.7.1.1. It shall be ensured that a TS12 call emitted by...

            2. 2.7.1.2. The dedicated PSAP test point during the test procedures shall...

            3. 2.7.1.3. If applicable, it shall be ensured that a TS11 call...

            4. 2.7.1.4. The TPSP test point shall be a dedicated TPSP answering...

            5. 2.7.1.5. Mobile network coverage of at least – 99 dBm or...

          2. 2.7.2. Public Mobile Network Procedure

            1. 2.7.2.1. It shall be ensured that a TS11 call to a...

            2. 2.7.2.2. The dedicated PSAP test point during the test procedures shall...

            3. 2.7.2.3. If applicable, it shall be ensured that a TS11 call...

            4. 2.7.2.4. The TPSP test point shall be a dedicated TPSP answering...

            5. 2.7.2.5. Mobile network coverage of at least – 99 dBm or...

          3. 2.7.3. Wired Transmission Procedure

            1. 2.7.3.1. It shall be ensured that a TS12 call emitted by...

            2. 2.7.3.2. The dedicated PSAP test point during the test procedures shall...

            3. 2.7.3.3. If applicable, it shall be ensured that a TS11 call...

            4. 2.7.3.4. The TPSP test point shall be a dedicated TPSP answering...

        8. 2.8. Verification procedures for components

          1. 2.8.1. These procedures shall apply for the purposes of type-approval of...

            1. 2.8.1.1. These procedures shall apply after the individual parts are subjected...

          2. 2.8.2. Control module including its connectors and wire harness as described...

            1. 2.8.2.1. Verify that no cable connectors are unplugged during the event....

            2. 2.8.2.2. The performance requirements shall be verified by performing a test...

            3. 2.8.2.3. Before performing the test call, ensure that:

            4. 2.8.2.4. Perform a test call (push mode) by applying a trigger...

            5. 2.8.2.5. Verify each of the following items:

            6. 2.8.2.6. Clear down the test call using the appropriate PSAP test...

          3. 2.8.3. Mobile network antenna including its connectors and wire harness as...

            1. 2.8.3.1. Verify that no cable connectors were unplugged during the event....

            2. 2.8.3.2. Measure the voltage standing wave ratio, VSWR, of the external...

            3. 2.8.3.3. The measurement shall be performed with a power meter, antenna...

            4. 2.8.3.4. If a power meter is used, VSWR shall be calculated...

            5. 2.8.3.5. Verify that VSWR satisfies the specifications prescribed by the manufacturer...

          4. 2.8.4. Power supply (if not part of the control module) including...

            1. 2.8.4.1. Verify that no cable connectors are unplugged during the event....

            2. 2.8.4.2. Measure if the voltage corresponds to the manufacturer's specification.

    3. ANNEX II

      Full-scale impact test assessment

      1. 1. Requirements

        1. 1.1. Performance requirements

          1. 1.1.1. The full-scale impact assessment of vehicles with eCall in-vehicle systems...

          2. 1.1.2. Automatic triggering: The eCall system shall automatically initiate an eCall...

          3. 1.1.3. Call status indication: The eCall system shall inform the occupants...

          4. 1.1.4. MSD emission and encoding: The eCall system shall be able...

          5. 1.1.5. Vehicle-specific data determination: The eCall system shall be able to...

          6. 1.1.6. Position determination: The eCall system shall be able to determine...

      2. 2. Test procedure

        1. 2.1. Purpose of the full-scale impact test procedure

        2. 2.2. The following tests shall be performed on a vehicle with...

        3. 2.3. Impact test procedure

          1. 2.3.1. Impact tests shall be carried out in accordance with the...

          2. 2.3.2. The test conditions defined in UN Regulation No 94 or...

          3. 2.3.3. Before performing the impact tests, ensure that:

        4. 2.4. Verification procedure

          1. 2.4.1. The performance requirements shall be verified by performing a test...

          2. 2.4.2. Perform a test call (push mode) by applying an automatic...

          3. 2.4.3. Verify each of the following items in at least one...

          4. 2.4.4. Clear down the test call using the appropriate PSAP test...

          5. 2.4.5. If the automatic test call could not be performed successfully...

          6. 2.4.6. If the test call was performed with the vehicle connected...

        5. 2.5. Positioning test procedure

        6. 2.6. Antenna test procedure

          1. 2.6.1. If the connection procedure applied for the test call did...

        7. 2.7. Connection procedures

    4. ANNEX III

      Crash resistance of audio equipment

      1. 1. Requirements

        1. 1.1. Performance requirements

          1. 1.1.1. The assessment of the crash resistance of the eCall audio...

          2. 1.1.2. Reconnection of audio equipment: The eCall system shall reconnect the...

          3. 1.1.3. Voice communication: The eCall system shall allow hands-free voice communication...

      2. 2. Test procedure

        1. 2.1. Purpose of the audio equipment crash resistance test procedure

        2. 2.2. The following verification test shall be performed on a vehicle...

        3. 2.3. Overview of test procedure

          1. 2.3.1. The sustained functionality of the audio equipment shall be verified...

          2. 2.3.2. Two test engineers, positioned in the vehicle (near-end tester) and...

          3. 2.3.3. The testers are required to assess whether they were able...

        4. 2.4. Arrangement of testers

          1. 2.4.1. The test shall be performed in a quiet environment, with...

          2. 2.4.2. The near-end tester shall be positioned so that his head...

          3. 2.4.3. The far-end tester shall be positioned away from the vehicle...

        5. 2.5. Test setup

          1. 2.5.1. Before performing the test call, ensure that:

          2. 2.5.2. Where it is possible to adapt the volume setting, the...

          3. 2.5.3. If possible, no mobile networks that have an influence on...

        6. 2.6. Test call

          1. 2.6.1. Perform a test call (push mode) by applying a manual...

          2. 2.6.2. Exchange of test messages

            1. 2.6.2.1. Receive direction

              1. 2.6.2.1.1. The far-end tester shall select and read one sentence pair...

              2. 2.6.2.1.2. The near-end tester shall assess whether the voice transmission in...

              3. 2.6.2.1.3. If required for the assessment, the near-end tester can request...

            2. 2.6.2.2. Send direction

              1. 2.6.2.2.1. The near-end tester shall select and, resting in his original...

              2. 2.6.2.2.2. The far-end tester shall assess whether the voice transmission in...

              3. 2.6.2.2.3. If required for the assessment, the far-end tester can request...

          3. 2.6.3. Clear down the test call using the appropriate PSAP test...

          4. 2.6.4. If the requirements cannot be fulfilled due to impairments introduced...

        7. 2.7. Connection procedures

          1. 2.7.1. The connection procedures defined in point 2.7 of Annex I...

      3. Appendix

        Test sentences

        1. 1. The following test sentence pairs, as defined in ITU-T P.501,...

        2. 2. Test sentence pairs in the language most commonly spoken by...

        3. 3. Test sentence pairs

          1. 3.1. Dutch

          2. 3.2. English

          3. 3.3. Finnish

          4. 3.4. French

          5. 3.5. German

          6. 3.6. Italian

          7. 3.7. Polish

          8. 3.8. Spanish

    5. ANNEX IV

      Co-existence of third party services (TPS) with the 112-based eCall in-vehicle systems

      1. 1. Requirements

        1. 1.1. The following requirements apply to 112-based eCall in-vehicle systems, STUs...

        2. 1.2. Performance requirements

          1. 1.2.1. The 112-based system shall be deactivated as long as the...

          2. 1.2.2. The 112-based system shall be automatically triggered in the event...

        3. 1.3. Documentation requirements

          1. 1.3.1. The manufacturer shall provide the technical service with an explanation...

          2. 1.3.2. The documentation shall be supported by an analysis which shows,...

      2. 2. Test procedure

        1. 2.1. Purpose of the TPS co-existence test procedure

        2. 2.2. The following tests shall be performed either on a vehicle...

        3. 2.3. The deactivation of the 112-based system while the TPS system...

          1. 2.3.1. Before performing the test call, ensure:

          2. 2.3.2. Perform a test call by applying a manual trigger of...

          3. 2.3.3. Verify:

          4. 2.3.4. Clear down the test call using the appropriate PSAP test...

          5. 2.3.5. If the call attempt of the TPS system fails during...

        4. 2.4. The fall-back procedure shall be verified by performing a manually...

          1. 2.4.1. Modify the TPS system to simulate a failure, selected at...

          2. 2.4.2. Before performing the test call, ensure:

          3. 2.4.3. Perform a test call by applying a manual trigger of...

          4. 2.4.4. Verify that an eCall was established by the 112-based system...

          5. 2.4.5. Clear down the test call using the appropriate PSAP test...

        5. 2.5. Connection procedures

    6. ANNEX V

      Automatic triggering mechanism

      1. 1. Requirements

        1. 1.1. The following requirements apply to vehicles with eCall in-vehicle systems...

        2. 1.2. Documentation requirements

          1. 1.2.1. The manufacturer shall provide a statement which affirms that the...

          2. 1.2.2. The manufacturer shall choose the collision typology and severity and...

          3. 1.2.3. The manufacturer shall provide the type-approval authority with an explanation...

            1. 1.2.3.1. Documentation that shows, to the satisfaction of the type-approval authority,...

            2. 1.2.3.2. Documentation that shows, to the satisfaction of the type-approval authority,...

            3. 1.2.3.3. Airbag control unit specification drawings, specification data notes, sensitivity drawings,...

            4. 1.2.3.4. The extended documentation package shall remain strictly confidential. It may...

    7. ANNEX VI

      Technical requirements for compatibility of eCall in-vehicle systems with the positioning services provided by the Galileo and the EGNOS systems

      1. 1. Requirements

        1. 1.1. Compatibility requirements

          1. 1.1.1. The ‘Galileo system compatibility’ shall be: the reception and processing...

          2. 1.1.2. The ‘EGNOS system compatibility’ shall be: the reception of the...

          3. 1.1.3. The compatibility of the eCall in-vehicle systems with the positioning...

          4. 1.1.4. The testing procedures in section 2.2 can be performed either...

        2. 1.2. Performance requirements

          1. 1.2.1. The GNSS receiver shall be able to output the navigation...

          2. 1.2.2. The GNSS receiver being a part of the eCall shall...

          3. 1.2.3. The GNSS receiver being a part of the eCall shall...

          4. 1.2.4. The GNSS receiver being a part of the eCall shall...

          5. 1.2.5. Horizontal position error shall not exceed:

          6. 1.2.6. The specified requirements for accuracy shall be provided:

          7. 1.2.7. Cold start time to first fix shall not exceed

          8. 1.2.8. GNSS signal re-acquisition time after block out of 60 seconds...

          9. 1.2.9. Sensitivity at receiver input shall be:

          10. 1.2.10. The GNSS receiver shall be able to obtain a position...

      2. 2. Test methods

        1. 2.1. Test conditions

          1. 2.1.1. The test object is the eCall, which includes a GNSS...

          2. 2.1.2. The number of the eCall test samples shall be at...

          3. 2.1.3. The eCall is provided for the test with the installed...

          4. 2.1.4. The attached documents shall contain the following data:

          5. 2.1.5. Tests are carried out in normal climatic conditions in accordance...

          6. 2.1.6. Tests of the eCall in respect of its GNSS receiver...

          7. 2.1.7. Unless otherwise specified, GNSS signal simulation shall follow ‘Open sky’...

          8. 2.1.8. Open Sky plot — Attenuation:

        2. 2.2. Test procedures

          1. 2.2.1. NMEA-0183 messages output test.

            1. 2.2.1.1. Make connections according to Figure 2.

            2. 2.2.1.2. Prepare and turn on the eCall. By means of operation...

            3. 2.2.1.3. Set up the simulator according to the simulator user guide....

            4. 2.2.1.4. By means of corresponding serial interface, set the connection between...

            5. 2.2.1.5. Test results are considered successful if navigation information via NMEA-0183...

            6. 2.2.1.6. The test of NMEA-0183 messages output and the assessment of...

          2. 2.2.2. Assessment of positioning accuracy in autonomous static mode.

            1. 2.2.2.1. Make connections according to Figure 2.

            2. 2.2.2.2. Prepare and turn on the eCall. By means of developer...

            3. 2.2.2.3. Set up the simulator in accordance with its operational manual....

            4. 2.2.2.4. Set up the recording of NMEA-0183 messages after receiving the...

            5. 2.2.2.5. Upon receiving the navigation solution set up recording of NMEA-0183...

            6. 2.2.2.6. Extract coordinates: latitude (B) and longitude (L) contained in GGA...

            7. 2.2.2.7. Calculate the systematic inaccuracy of coordinate's determination on stationary intervals...

            8. 2.2.2.8. Similarly calculate the systematic inaccuracy of L (longitude) coordinate.

            9. 2.2.2.9. Calculate standard deviation (SD) value according to formula (3) for...

            10. 2.2.2.10. Similarly calculate the SD value for L (longitude) coordinate.

            11. 2.2.2.11. Convert calculated coordinates and SD values of latitude and longitude...

            12. 2.2.2.12. For latitude:

            13. 2.2.2.13. For longitude:

            14. 2.2.2.14. Calculate horizontal position error according to formula (6):

            15. 2.2.2.15. Repeat test procedures according to 2.2.2.3 – 2.2.2.14 for GNSS...

            16. 2.2.2.16. Repeat test procedures according to 2.2.2.3 – 2.2.2.14 only for...

            17. 2.2.2.17. Repeat test procedures according to 2.2.2.3 – 2.2.2.16 with other...

            18. 2.2.2.18. Determine average values according to (6) obtained for all tested...

            19. 2.2.2.19. Tests results are considered satisfactory if horizontal position errors as...

          3. 2.2.3. Assessment of positioning accuracy in autonomous dynamic mode.

            1. 2.2.3.1. Repeat test procedures described in section 2.2.2, but 2.2.2.15 –...

            2. 2.2.3.2. Determine average values according to (6) obtained for all tested...

            3. 2.2.3.3. Tests results are considered satisfactory if horizontal position errors obtained...

          4. 2.2.4. Movement in shadow areas, areas of intermittent reception of navigation...

            1. 2.2.4.1. Repeat test procedures described in section 2.2.3 for simulation script...

            2. 2.2.4.2. Urban canyon plot- Attenuation:

            3. 2.2.4.3. Tests results are considered satisfactory if horizontal position errors obtained...

          5. 2.2.5. Cold start time to first fix test.

            1. 2.2.5.1. Prepare and turn on the eCall. By means of developer...

            2. 2.2.5.2. Delete all position, velocity, time, almanac and ephemeris data from...

            3. 2.2.5.3. Set up the simulator according to the simulator user guide....

            4. 2.2.5.4. By means of a stopwatch, measure time interval between signal...

            5. 2.2.5.5. Conduct test procedures according to 2.2.5.2 – 2.2.5.4 at least...

            6. 2.2.5.6. Calculate average time to first fix in cold start mode...

            7. 2.2.5.7. The test result is considered to be positive, if average...

            8. 2.2.5.8. Repeat test procedure according to 2.2.5.1 – 2.2.5.5 with signal...

            9. 2.2.5.9. The test result according to 2.2.5.8 is considered to be...

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

            1. 2.2.6.1. Prepare and turn on the eCall according to operational manual....

            2. 2.2.6.2. Set up the simulator according to the simulator user guide....

            3. 2.2.6.3. Wait for 15 minutes and make sure the GNSS receiver...

            4. 2.2.6.4. Disconnect the GNSS antenna cable from the eCall and connect...

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

            6. 2.2.6.6. Calculate average value of re-acquisition time of satellite tracking signals...

            7. 2.2.6.7. The test result is considered to be positive, if average...

          7. 2.2.7. Test of GNSS receiver sensitivity in cold start mode, tracking...

            1. 2.2.7.1. Turn on the vector network analyser. Calibrate the vector network...

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

            3. 2.2.7.3. Set zero signal path attenuation on attenuators. Measure the frequency...

            4. 2.2.7.4. Assemble the circuit shown in Figure 5.

            5. 2.2.7.5. Prepare and turn on eCall according to operational manual. By...

            6. 2.2.7.6. Prepare GNSS signals simulator according to its operation manual. Start...

            7. 2.2.7.7. By means of a stopwatch, measure time interval between signal...

            8. 2.2.7.8. Set the signal path attenuation on attenuators such that the...

            9. 2.2.7.9. By means of a stopwatch, verify that the eCall still...

            10. 2.2.7.10. Set the signal path attenuation on attenuators such that the...

            11. 2.2.7.11. Disconnect the GNSS antenna cable from the eCall and connect...

            12. 2.2.7.12. By means of stopwatch, determine time interval between cable connection...

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

    8. ANNEX VII

      In-vehicle system self-test

      1. 1. Requirements

        1. 1.1. The following requirements apply to vehicles with eCall in-vehicle system...

        2. 1.2. Performance requirements

          1. 1.2.1. The eCall system shall carry out a self-test at each...

          2. 1.2.2. The self-test function shall monitor at least the technical items...

          3. 1.2.3. A warning in form of either a visual tell-tale or...

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

            2. 1.2.3.2. It may be cancelled temporarily, but shall be repeated whenever...

        3. 1.3. Documentation requirements

          1. 1.3.1. The manufacturer shall provide the type-approval authorities with documentation in...

      2. 2. Test procedure

        1. 2.1. Self-test function verification test

          1. 2.1.1. The following test shall be performed on the vehicle with...

          2. 2.1.2. Simulate a malfunction of the eCall system by introducing a...

          3. 2.1.3. Power the eCall system up (e.g. by switching the ignition...

          4. 2.1.4. Power the eCall system down (e.g. by switching the ignition...

          5. 2.1.5. Power the eCall system up and verify that the malfunction...

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

        1. 3.1. When the manufacturer submits an application for revision or extension...

    9. ANNEX VIII

      Technical requirements and test procedures related to privacy and data protection

      1. PART I Procedure for verifying the lack of traceability of an eCall in-vehicle system or STU

        1. 1. Purpose

          1. 1.1. This test procedure is to ensure that a 112-based eCall...

        2. 2. Requirements

          1. 2.1. The 112-based eCall in-vehicle system or STU is not available...

          2. 2.2. Failure to establish the connection can be attributed to the...

        3. 3. Test procedure

          1. 3.1. The following tests shall be performed on a representative arrangement...

          2. 3.2. This test shall be performed after successful connection of the...

            1. 3.2.1. The initial emergency call must have been ‘cleared down’ and...

            2. 3.2.2. Before performing the test, ensure that:

            3. 3.2.3. Leave the 112-based eCall IVS powered.

            4. 3.2.4. Via the PSAP test point, attempt to connect to the...

        4. 4. Assessment

          1. 4.1. The requirement is determined to have been passed if the...

          2. 4.2. The establishment of connection with the 112-based eCall IVS when...

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

        1. 1. Purpose

          1. 1.1. This test procedure aims to ensure that personal data processed...

          2. 1.2. This is to demonstrate the automatic deletion by proving that...

        2. 2. Requirements

          1. 2.1. When interrogated, the eCall in-vehicle system or STU shall not...

        3. 3. Test conditions

          1. 3.1. The Technical Service shall be facilitated to have access to...

          2. 3.2. The following test shall be performed on a representative arrangement...

        4. 4. Test Method

          1. 4.1. The tests as described in point 2.7 of Annex I...

          2. 4.2. 13 hours after a test call has been placed, the...

        5. 5. Assessment

          1. 5.1. The requirement is determined to have been passed if no...

          2. 5.2. The presence of a log file pertaining to an eCall...

      3. 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. 1. Purpose

          1. 1.1. This test procedure aims to ensure that personal data is...

          2. 1.2. This is to be proved by demonstrating that in the...

        2. 2. Requirements

          1. 2.1. When interrogated, the eCall in-vehicle system or STU shall not...

        3. 3. Test conditions

          1. 3.1. The Technical Service shall be facilitated to have access to...

          2. 3.2. The following test shall be performed on a representative arrangement...

        4. 4. Test Method

          1. 4.1. The Technical Service tester shall be facilitated with access to...

        5. 5. Assessment

          1. 5.1. The requirement is determined to have been passed if maximum...

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

      4. 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. 1. Purpose

          1. 1.1. This test procedure shall ensure that the 112-based eCall in-vehicle...

        2. 2. Requirements

          1. 2.1. The following requirements apply to eCall in-vehicle systems or STUs...

          2. 2.2. Performance requirements

            1. 2.2.1. There is no exchange of personal data between the 112-based...

            2. 2.2.2. Following an eCall made via the 112-based eCall in-vehicle system...

        3. 3. Test procedure

          1. 3.1. The following tests shall be performed either on a vehicle...

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

            1. 3.2.1. Before performing the test call, ensure that:

            2. 3.2.2. Perform a test call by applying a manual trigger of...

            3. 3.2.3. Verify that a call was established with the PSAP test...

            4. 3.2.4. Clear down the test call using the appropriate PSAP test...

            5. 3.2.5. If the call attempt of the 112-based system fails during...

          3. 3.3. The lack of a log file in the TPS system...

            1. 3.3.1. The Technical Service tester shall be facilitated with access to...

            2. 3.3.2. The requirement is determined to have been passed if no...

            3. 3.3.3. The presence of a log file in the TPS system...

          4. 3.4. Connection procedures

    10. ANNEX IX

      Classes of vehicles referred to in Article 2

      1. Armoured vehicles of categories M1 and N1, as defined in...

Back to top

Options/Help

Print Options

You have chosen to open the Whole Regulation

The Whole Regulation you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.

Would you like to continue?

You have chosen to open Schedules only

The Schedules you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.

Would you like to continue?

Close

Legislation is available in different versions:

Latest Available (revised):The latest available updated version of the legislation incorporating changes made by subsequent legislation and applied by our editorial team. Changes we have not yet applied to the text, can be found in the ‘Changes to Legislation’ area.

Original (As adopted by EU): The original version of the legislation as it stood when it was first adopted in the EU. No changes have been applied to the text.

Close

Opening Options

Different options to open legislation in order to view more content on screen at once

Close

More Resources

Access essential accompanying documents and information for this legislation item from this tab. Dependent on the legislation item being viewed this may include:

  • the original print PDF of the as adopted version that was used for the EU Official Journal
  • lists of changes made by and/or affecting this legislation item
  • all formats of all associated documents
  • correction slips
  • links to related legislation and further information resources
Close

More Resources

Use this menu to access essential accompanying documents and information for this legislation item. Dependent on the legislation item being viewed this may include:

  • the original print PDF of the as adopted version that was used for the print copy
  • correction slips

Click 'View More' or select 'More Resources' tab for additional information including:

  • lists of changes made by and/or affecting this legislation item
  • confers power and blanket amendment details
  • all formats of all associated documents
  • links to related legislation and further information resources

The data on this page is available in the alternative data formats listed: