ANNEX IVSupplementary provisions
ANNEX IV Co-existence of third party services (TPS) with the 112-based eCall in-vehicle systems 1. Requirements 1.1. The following requirements apply to 112-based eCall in-vehicle systems, STUs and (optionally for) components that shall be used in conjunction with a TPS eCall in-vehicle system. 1.2. Performance requirements 1.2.1. The 112-based system shall be deactivated as long as the TPS system is active and does function. 1.2.2. The 112-based system shall be automatically triggered in the event that the TPS system is triggered but does not function. 1.3. Documentation requirements 1.3.1. The manufacturer shall provide the technical service with an explanation of the design provisions built into the TPS system to ensure automatic triggering of the 112-based system (‘fall-back procedure’) in the event that the TPS system does not function. This documentation shall describe the principles of the changeover mechanism. 1.3.2. The documentation shall be supported by an analysis which shows, in overall terms, any hardware or software failure conditions that would result in an inability of the TPS system to perform a successful call and how the TPS system will behave on the occurrence of these. This may be based on a Failure Mode and Effect Analysis (FMEA), a Fault Tree Analysis (FTA) or any appropriate similar process as agreed between the technical service and the manufacturer. The chosen analytical approach(es) shall be established and maintained by the manufacturer and shall be made open for inspection by the technical service at the time of the type-approval. 2. Test procedure 2.1. Purpose of the TPS co-existence test procedure The purpose of this test procedure is to verify for eCall in-vehicle systems that shall be used in conjunction with a TPS eCall in-vehicle system, that there is only one system active at a time and that the 112-based system is triggered automatically in the event that the TPS system does not function. 2.2. The following tests shall be performed either on a vehicle with an eCall in-vehicle system installed or on a representative arrangement of parts. 2.3. The deactivation of the 112-based system while the TPS system is active shall be verified by performing a manually triggered test call. 2.3.1. Before performing the test call, ensure: (a) that one of the connection procedures defined in point 2.7 of Annex I to this Regulation, as agreed between the technical service and the manufacturer, will be applied for any test call; (b) that the dedicated PSAP test point is available to receive an eCall emitted by the 112-based system; (c) that the TPSP test point is available to receive a call emitted by the TPS system; (d) that a false eCall to a genuine PSAP cannot be made over the live network; and (e) that the vehicle ignition or master control switch is activated. 2.3.2. Perform a test call by applying a manual trigger of the TPS system (push mode). 2.3.3. Verify: (a) that a call was established with the TPSP test point by a record of the TPSP test point showing that it did receive a call initiation signal or by a successful voice connection to the TPSP test point; and (b) that no eCall was attempted or established with the PSAP test point by a record of the PSAP test point showing that it did not receive an eCall initiation signal. 2.3.4. Clear down the test call using the appropriate PSAP test point command (e.g. hang up). 2.3.5. If the call attempt of the TPS system fails during the test, the test procedure may be repeated. 2.4. The fall-back procedure shall be verified by performing a manually triggered test call to a dedicated PSAP test point in a condition where the TPS system does not function. 2.4.1. Modify the TPS system to simulate a failure, selected at the discretion of the type-approval authority that shall result in a fall-back procedure based on the documentation provided by the manufacturer. 2.4.2. Before performing the test call, ensure: (a) that one of the connection procedures defined in point 2.7 of Annex I to this Regulation, as agreed between the technical service and the manufacturer, will be applied for any test call; (b) that the dedicated PSAP test point is available to receive an eCall emitted by the 112-based system; (c) that a false eCall to a genuine PSAP cannot be made over the live network; and (d) that the vehicle ignition or master control switch is activated. 2.4.3. Perform a test call by applying a manual trigger of the TPS system (push mode). 2.4.4. Verify that an eCall was established by the 112-based system by a record of the PSAP test point showing that it did receive an eCall initiation signal. 2.4.5. Clear down the test call using the appropriate PSAP test point command (e.g. hang up). 2.5. Connection procedures The connection procedures defined in point 2.7 of Annex I to this Regulation shall apply.