EN 18052:2025/prA1

• Abstract:

  This document describes the key actors in the eCall chain of service provision in hybrid circuit switched/packet switched network; environments as:; 1) In-Vehicle System (IVS)/vehicle,; 2) Mobile Network Operator (MNO),; 3) Public Safety Answering Point (PSAP),; and to provide conformance tests for actor groups 1) – 3).; NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants, although they are the recipient of the service.; NOTE 2 Third party eCall systems (TPS-eCall) are not within the scope of this deliverable. This is because the core TPS-eCall; standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider.; NOTE 3 These conformance tests are partly based on the appropriate conformance tests from EN 16454 and CEN/prEN 17240.; This deliverable therefore adapts and revises Conformance Test Protocols (CTP) from EN 16454 and CEN/prEN 17240 for hybrid circuit switched/packet switched network environments.; This document complements EN 16454 and CEN/prEN 17240 and provides a suite of conformance tests for IVS equipment, MNOs and PSAPs, required to ensure and demonstrate compliance with CEN/prEN 17905.; The scope covers conformance testing of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.

• Status: Not Published
• Publication Date: 14-May-2028
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: CEN/TC 278 - Road transport and traffic telematics
• Drafting Committee: CEN/TC 278/WG 15 - eSafety
• Current Stage: 4020 - Submission to enquiry - Enquiry
• Start Date: 01-Oct-2026
• Due Date: 01-Feb-2027
• Completion Date: 01-Oct-2026
• Ref Project: SIST EN 18052:2026/oprA1:2026 - Intelligent transport systems - ESafety - ECall end to end conformance testing for eCall HLAP in hybrid circuit switched/packet switched network environments

• Amends: EN 18052:2025 - Intelligent transport systems - ESafety - ECall end to end conformance testing for eCall HLAP in hybrid circuit switched/packet switched network environments
• Effective Date: 11-Mar-2026

EN 18052:2025/prA1 is a CEN draft amendment to the European standard on eCall end-to-end conformance testing in hybrid circuit switched/packet switched network environments. It specifies conformance tests for the In-Vehicle System (IVS), Mobile Network Operator (MNO), and Public Safety Answering Point (PSAP) parts of the eCall chain, so engineers can verify how eCall behaves across domain selection, fallback, call-back, and message handling cases.

What does EN 18052:2025/prA1 specify?

EN 18052:2025/prA1 specifies how to test eCall HLAP behavior in hybrid network environments where both circuit switched and packet switched service are involved. The scope focuses on conformance testing for the IVS/vehicle, the MNO, and the PSAP, because these are the actors that make the service work in practice.

EN 18052:2025/prA1 excludes vehicle occupants from conformance testing and leaves TPS-eCall outside its scope. The document also states that the tests are for new engineering developments, products, and systems, not for checking individual vehicle installations or local site installations.

The amendment is organized as changes to the normative references, eCall timers, test applicability, and many conformance test protocols in Clauses 9 and 11. It revises test cases for IVS behavior, eCall-only IVS behavior, and PSAP behavior.

What are the key requirements of EN 18052:2025/prA1?

EN 18052:2025/prA1 mainly updates when tests apply, how the tester can interact with the system, and how hybrid-network eCall cases are checked. The practical effect is that labs and implementers need to re-read the affected test cases, because many pass conditions now depend on release alignment, supported capabilities, and the actual eCall domain path taken by the IVS.

Applicability and reference updates

• Clause 2 updates the normative references to ETSI TS 124 229 and ETSI TS 123 167 so that the release conditions reflect eCall over 4G and eCall over 5G. In practice, this keeps the test basis aligned with the radio and session behavior that the IVS is expected to support.
• Clause 8.4 revises the CTP test applicability note so that the release range for ETSI specifications is treated consistently, and the note now points to completed alignment work in ETSI/3GPP Release 19. This matters because a test may be applicable only when the IVS supports the relevant capability as defined for the release range in use.
• Several test cases use updated applicability logic tied to ETSI TS 124 229 behavior, including cases where PSAP call rejection or call failure already triggers the required domain behavior. In practice, testers must confirm the supported feature set before deciding whether a test is run or skipped.

IVS behavior in hybrid eCall cases

• Many IVS test cases in Clause 9.2 now allow the IVS to have completed or skipped network registration before the eCall. This is important because the conformance target is the eCall result, not whether registration happened in exactly one way.
• Several table updates delete the wording “or manual” from tester actions. That means the tests are being tightened around defined protocol behavior rather than manual intervention.
• Clause 9.2 includes multiple domain change and fallback scenarios, such as fallback to IMS emergency call in PS domain, fallback to emergency call in CS domain, and switching between PS and CS after eCall failure, rejection, or abnormal termination. These tests check whether the IVS can recover the call in the correct domain after a failure.
• Clause 9.2.18 sets a redial behavior after abnormal termination in PS domain, with a redial attempt expected within 2 minutes and a 5% admissible margin. In practice, this checks the IVS retry logic under a realistic network failure.
• Clause 9.2.34 and the related persistence cases check that the IVS remains registered after in-call domain handover or domain change. Clause 9.3.6 also tests registration persistence for an eCall-only IVS over a defined time window. These tests matter because the system must stay reachable long enough for emergency handling to continue.
• Clause 9.2.40 updates MSD transfer using in-band modem in PS domain after negative or missing AL-ACK. That tells implementers how the IVS should continue or stop sending MSD when the PSAP response is incomplete.

PSAP behavior and call-back handling

• Clause 11.2 adds and revises PSAP cases for logging the MSD transfer type in PS domain. This matters because the PSAP must record whether the MSD came by in-band modem.
• Clause 11.2.8 covers call-back to the vehicle after domain change to PS domain, and the updated wording allows the call-back to come from the same or a different MNO. In practice, PSAP systems must handle callback conditions without relying on one specific network path.
• Clauses 11.2.9 to 11.2.11 cover requests for a new MSD after call clear-down and domain change. The tests allow for failure, timeout, or success depending on the exact case, so PSAP behavior is checked against real call-clear-down timing and domain changes.
• Several PSAP-related table updates also require the tester to configure the PSAP test point to reject redial attempts or accept incoming calls in the specified cases. That means the PSAP side of the test is not passive - it actively drives the recovery scenario.

What terms does EN 18052:2025/prA1 define?

• Conformance Test Protocols (CTP) - The step-by-step test procedures used to verify eCall behavior in a specific scenario, including initial conditions, stimulus, expected behavior, and pass conditions.
• In-Vehicle System (IVS) - The vehicle-side eCall equipment being tested in most of the IVS clauses, including registration, call setup, fallback, and MSD handling.
• Mobile Network Operator (MNO) - The network test point used to observe and control registration, domain changes, and call handling on the circuit switched or packet switched side.
• Public Safety Answering Point (PSAP) - The emergency call center test point that answers calls, receives MSD, sends acknowledgements, and triggers callback or retry scenarios.
• eCall-only IVS - An IVS configuration that is limited to eCall behavior, with special test cases for registration, fallback, and retained connectivity.
• MSD - The data carried during the eCall exchange and checked, logged, retried, or acknowledged in the test cases.
• AL-ACK - The acknowledgement used in the eCall message exchange when the PSAP confirms the MSD handling step in the relevant test case.
• LL-ACK - The lower-level acknowledgement used in the in-band modem test sequences when MSD transfer is continued or stopped.

Who uses EN 18052:2025/prA1?

EN 18052:2025/prA1 is used by vehicle manufacturers, eCall equipment suppliers, telecom operators, PSAP operators, and test laboratories that need to prove conformance of eCall functions in hybrid network environments. It is also useful for quality managers and buyers who need to check whether a product or service has been tested against the right eCall scenarios.

In practice, users apply it to test IVS equipment, MNO service behavior, and PSAP handling for new engineering developments, products, and systems. It is a conformance-testing document, so it is used for verification and demonstration rather than for vehicle-by-vehicle installation checks.

What changed in EN 18052:2025/prA1 from the previous edition?

EN 18052:2025/prA1 is an amendment to EN 18052:2025. The changes listed in the document update the normative references, eCall timer wording, test applicability rules, and many test cases across IVS, eCall-only IVS, and PSAP scenarios.

The amendment also revises several tables so that the test logic matches current hybrid-network behavior, including domain selection, fallback between PS and CS domains, MSD handling, callback behavior, and logging of the MSD transfer type.

Which standards are used with EN 18052:2025/prA1?

Standard	What it contributes
ETSI TS 124 229	SIP and session behavior used in the eCall test applicability and call-handling cases, including release-based applicability for eCall over 4G and 5G.
ETSI TS 123 167	Session behavior used together with ETSI TS 124 229 in the updated applicability text.
EN 16454	One of the sources of conformance tests that this document adapts for hybrid circuit switched/packet switched network environments.
CEN/prEN 17240	Another source of conformance test protocols that are revised here for hybrid environments.
CEN/prEN 17905	The compliance target that the test suite is intended to help demonstrate.
EN 17184:2024+A1:2026	Referenced in a modified IVS test case for packet switched eCall behavior after fallback from PS to CS.
EN 16062:2025	Referenced in a modified IVS test case for circuit switched eCall behavior after PS-domain failure.
EN 16072:2025	Referenced in the same fallback test logic for CS-domain registration and eCall handling.
EN 15722	Used in the PSAP in-band modem cases for MSD format checking.

What does the EN 18052:2025/prA1 document contain?

EN 18052:2025/prA1 contains clause-by-clause modifications, not a new standalone test method. The main content is replacement text for Clause 2, Clause 8.3, Clause 8.4, and many conformance test tables in Clauses 9.2, 9.3, and 11.2.

The tables give the test point sequence, tester actions, SUT behavior, pass conditions, and the conditions under which a test is not applicable. They cover domain selection, call setup, MSD transfer, redial attempts, abnormal termination, PSAP callback, and registration persistence.

Several modified tables also define timed behaviors and conditional steps, such as waiting windows for redial, registration retention after handover, and MSD transfer using in-band modem. This makes the document useful for lab testing, product verification, and conformity assessment of hybrid eCall implementations.

SLOVENSKI STANDARD
01-december-2026
Inteligentni transportni sistemi - e-Varnost - Preskušanje skladnosti e-klica HLAP v
hibridnih omrežnih okoljih s komutiranim vezjem/paketno komutiranim omrežjem -
Dopolnilo A1
Intelligent transport systems - ESafety - ECall end to end conformance testing for eCall
HLAP in hybrid circuit switched/packet switched network environments
Intelligente Verkehrssysteme - eSicherheit - eCall-Ende-zu-Ende Konformitätsprüfungen
für übergeordnete eCall-Anwendungen in hybriden leitungs- / paketvermittelnden
Netzwerkumgebungen - Änderung 1
Systèmes de transport intelligents - eSécurité - Essais de conformité du système eCall
de bout en bout pour les systèmes IMS basés sur la commutation de paquets
Ta slovenski standard je istoveten z: EN 18052:2025/prA1
ICS:
03.220.20 Cestni transport Road transport
13.200 Preprečevanje nesreč in Accident and disaster control
katastrof
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

DRAFT
EUROPEAN STANDARD
EN 18052:2025
NORME EUROPÉENNE
EUROPÄISCHE NORM
prA1
October 2026
ICS 35.240.60
English Version
Intelligent transport systems - ESafety - ECall end to end
conformance testing for eCall HLAP in hybrid circuit
switched/packet switched network environments
Systèmes de transport intelligents - eSafety - Essais de Intelligente Verkehrssysteme - eSicherheit - eCall-
conformité du système eCall de bout en bout pour le Ende-zu-Ende Konformitätsprüfungen für
HLAP d'eCall dans les environnements réseaux übergeordnete eCall-Anwendungen in hybriden
hybrides à commutation de circuits et de paquets leitungs- / paketvermittelnden Netzwerkumgebungen
- Änderung 1
This draft amendment is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee CEN/TC 278.

This draft amendment A1, if approved, will modify the European Standard EN 18052:2025. If this draft becomes an amendment,
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for inclusion of
this amendment into the relevant national standard without any alteration.

This draft amendment was established by CEN in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.

EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2026 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 18052:2025/prA1:2026 E
worldwide for CEN national Members.

Contents Page
European foreword . 5
1 Modifications to Clause 2, “Normative references” . 6
2 Modifications to 8.3, “eCall timers” . 6
3 Modifications to 8.4, “CTP Test Applicability” . 6
4 Modification to 9.2.3, “CTP 1.1.2.1 Domain selection skipped and IVS remains registered in
CS domain - IVS” . 7
5 Modifications to 9.2.5, “CTP 1.1.2.3 Domain selection performed and eCall initiated in CS
domain - IVS” . 7
6 Modification to 9.2.7, “CTP 1.1.2.5 Domain selection performed and eCall initiated in PS
domain in different RAT - IVS” . 7
7 Modifications to 9.2.8, “CTP 1.1.6.1 eCall successful in CS domain - IVS” . 7
8 Modifications to 9.2.9, “CTP 1.1.6.2 eCall successful in CS domain in limited service state -
IVS” . 7
9 Modification to 9.2.11, “CTP 1.1.10.1 Domain change and fallback to IMS emergency call in
PS domain after network registration and eCall failed and after unsuccessful re-attempt in
CS domain - IVS” . 8
10 Modifications to 9.2.12, “CTP 1.1.10.2 Domain change and fallback to IMS emergency call in
PS domain after eCall failed and after unsuccessful re-attempt in CS domain - IVS” . 8
11 Modification to 9.2.13, “CTP 1.1.10.3 Fallback to IMS emergency call in PS domain after
missing AL-ACK for initial MSD - IVS” . 9
12 Modifications to 9.2.14, “CTP 1.1.10.4 Domain change and fallback to IMS emergency call in
PS domain after eCall is dropped before the MSD is acknowledged and after unsuccessful
re-attempt in CS domain - IVS” . 9
13 Modifications to 9.2.15, “CTP 1.1.10.5 Fallback to emergency call in CS domain - IVS” . 10
14 Modifications to 9.2.16, “CTP 1.1.10.6 Domain change to PS domain after network
registration and eCall failed in CS domain - IVS” . 10
15 Modifications to 9.2.17, “CTP 1.1.10.7 Domain change to PS domain after eCall failed in CS
domain - IVS” . 11
16 Modifications to 9.2.18, “CTP 1.1.10.8 Domain change to CS domain after eCall failed in PS
domain - IVS” . 12
17 Modifications to 9.2.19, “CTP 1.1.10.9 Domain change to CS domain after eCall failed and
after unsuccessful re-attempt in PS domain - IVS” . 13
18 Modifications to 9.2.20, “CTP 1.1.10.10 Domain change and fallback to eCall (emergency
call) in CS domain after eCall failed in PS domain - IVS” . 14
19 Modifications to 9.2.21, “CTP 1.1.10.11 Domain change and fallback to eCall (emergency
call) in CS domain after eCall failed and after unsuccessful re-attempt in PS domain - IVS”
............................................................................................................................................................................. 14
20 Modification to 9.2.22, “CTP 1.1.10.12 Domain change to PS domain after eCall is dropped
before the MSD is acknowledged and after unsuccessful re-attempt in CS domain - IVS” . 15
21 Modifications to 9.2.23, “CTP 1.1.10.13 Domain change to PS domain and MSD transfer
using in-band modem after eCall is dropped before the MSD is acknowledged and after
unsuccessful re-attempt in CS domain - IVS” . 15
22 Modifications to 9.2.24, “CTP 1.1.10.14 Domain change to CS domain after eCall is rejected
and MSD acknowledged in PS domain - IVS” . 16
23 Modifications to 9.2.25, “CTP 1.1.10.15 No Call reattempt or domain change to CS domain
after eCall is rejected and MSD acknowledged in PS domain - IVS” . 17
24 Modifications to 9.2.26, “CTP 1.1.10.16 Domain change to CS domain after eCall is rejected
and negative AL-ACK and unsuccessful re-attempt in PS domain - IVS” . 17
25 Modifications to 9.2.27, “CTP 1.1.10.17 Domain change to CS domain after eCall is rejected
and negative AL-ACK in PS domain - IVS” . 17
26 Modifications to 9.2.28, “CTP 1.1.10.18 Domain change to CS domain after eCall is rejected
and missing AL-ACK and unsuccessful re-attempt in PS domain - IVS” . 18
27 Modifications to 9.2.29, “CTP 1.1.10.19 Domain change to CS domain after eCall is rejected
and missing AL-ACK in PS domain - IVS” . 18
28 Modifications to 9.2.30, “CTP 1.1.10.20 Domain change to CS domain after eCall is not
answered and unsuccessful re-attempt in PS domain - IVS” . 19
29 Modifications to 9.2.31, “CTP 1.1.10.21 Domain change to CS domain after eCall is not
answered in PS domain - IVS” . 19
30 Modifications to 9.2.32, “CTP 1.1.10.22 Domain change to CS domain after eCall is dropped
before the MSD is acknowledged and after unsuccessful re-attempt in PS domain - IVS” . 20
31 Modifications to 9.2.33, “CTP 1.1.10.23 Domain change to CS domain after eCall is dropped
before the MSD is acknowledged in PS domain - IVS” . 20
32 Modifications to 9.2.34, “CTP 1.1.15.1 New/updated MSD after in-call domain handover -
IVS” . 21
33 Modifications to 9.2.36, “CTP 1.1.17.2 Call-back allowed after domain change to PS domain
- IVS” . 21
34 Modifications to 9.2.37, “CTP 1.1.17.3 Remain registered for ≥ 1 hr after in-call domain
handover - IVS” . 22
35 Modifications to 9.2.38, “CTP 1.1.17.4 Remain registered for ≥ 1 hr after domain change to
CS domain - IVS” . 22
36 Modifications to 9.2.39, “CTP 1.1.17.5 Remain registered for ≥ 1 hr after domain change to
PS domain - IVS” . 23
37 Modifications to 9.2.40, “CTP 1.1.18.1 MSD transfer using in-band modem in PS domain
after negative AL-ACK for initial MSD - IVS” . 25
38 Modifications to 9.2.40, “CTP 1.1.18.2 MSD transfer using in-band modem in PS domain
after missing AL-ACK for initial MSD - IVS” . 26
39 Modification to 9.3.3, “CTP 1.2.10.1 Domain change to CS domain after eCall is rejected and
MSD acknowledged in limited service state in PS domain - eCall-only IVS” . 26
40 Modifications to 9.3.4, “CTP 1.2.10.2 Domain change to CS domain after network
registration and eCall failed in PS domain - eCall-only IVS”. 26
41 Modifications to 9.3.5, “CTP 1.2.10.3 Domain change to CS domain after network
registration and eCall failed and after unsuccessful re-attempt in PS domain - eCall-only
IVS” . 27
42 Modifications to 9.3.6, “CTP 1.2.17.1 Remain registered for ≥ 1 hr ≤ 12 hr after in-call
domain handover - eCall-only IVS” . 27
43 Modifications to 11.2.4, “CTP 3.1.10.3 Logging of MSD transfer type (in-band modem) of
eCall in PS domain - PSAP” . 28
44 Modifications to 11.2.8, “CTP 3.1.15.3 Call-back to vehicle after domain change to PS
domain - PSAP” . 28
45 Modifications to 11.2.9, “CTP 3.1.16.1 Request new MSD failed after call clear-down and
domain change to CS domain - PSAP” . 28
46 Modifications to 11.2.10, “CTP 3.1.16.2 Request new MSD failed after call clear-down and
domain change to PS domain - PSAP” . 28
47 Modifications to 11.2.11, “CTP 3.1.16. Request new MSD after call clear-down and domain
change to CS domain - PSAP” . 29
48 Modification to multiple affected clauses (e.g. 9.2.3, 9.2.4, 9.2.5, etc.) . 29
European foreword
This document (EN 18052:2025/prA1:2026) has been prepared by Technical Committee CEN/TC 278
“Intelligent transport systems”, the secretariat of which is held by NEN.
This document is currently submitted to the CEN Enquiry.
1 Modifications to Clause 2, “Normative references”
Replace:
EN 17184:2024 (…)
with:
EN 17184:2024+A1:2026 (…)
Replace:
ETSI TS 124 229 (Release “16”), Digital (…) Stage 3 (3GPP TS 24.229 Release “16”)
with:
ETSI TS 124 229 (Release “14 or later for eCall over 4G; Release 16 or later for eCall over 5G”), Digital (…)
Stage 3 (3GPP TS 24.229 Release “14 or later for eCall over 4G; Release 16 or later for eCall over 5G”)

Replace:
“ETSI TS 123 167 (Release “16”), Universal (…) sessions (3GPP TS 23.167 Release “16”)
with:
“ETSI TS 123 167 (Release “14 or later for eCall over 4G; Release 16 or later for eCall over 5G”), Universal
(…) sessions (3GPP TS 23.167 Release “14 or later for eCall over 4G; Release 16 or later for eCall over
5G”)
2 Modifications to 8.3, “eCall timers”
Replace (5x):
EN 17184:2024 (…)
with:
EN 17184:2024+A1:2026 (…)
3 Modifications to 8.4, “CTP Test Applicability”
Delete:
“To allow for possible future change in ETSI specifications (e.g. Release 19), any ETSI specification
included as part of test applicability shall refer to the latest Release 16 version of the specification. If the
definition of a capability changes in a later version (e.g. Release 19) of the ETSI specification such that an
IVS that supports the later version (e.g. Release 19) of the ETSI specification does not support the
capability as defined in Release 16, then the capability shall be considered to be not supported.”.

Replace the current NOTE:
NOTE “The Technical Committee” CEN/TC 278/WG 15 (…) the “current” requirements in ETSI specifications
“(Release 16 and later)” and asked ETSI and 3GPP for alignment. Those alignments “are currently planned” in
ETSI/3GPP Release 19.
with the following:
NOTE CEN/TC 278/WG 15 (…) the requirements in ETSI specifications “in Release 14 to Release 18” and asked
ETSI and 3GPP for alignment. Those alignments “have been completed” in ETSI/3GPP Release 19.
4 Modification to 9.2.3, “CTP 1.1.2.1 Domain selection skipped and IVS remains
registered in CS domain - IVS”
th
In Table 7, 14 row, under column ‘Tester action’, delete:
“ or manual”.
5 Modifications to 9.2.5, “CTP 1.1.2.3 Domain selection performed and eCall
initiated in CS domain - IVS”
th
In Table 9, 14 row, under column ‘Tester action’, delete:
“ or manual”.
th
In Table 9, 15 row, under column ‘Tester action’, replace:
IVS shall perform domain selection and “shall register” on the circuit switched network
with:
IVS shall perform domain selection and “the IVS may have completed or skipped the network
registration” on the circuit switched network

th
In Table 9, 15 row, under column ‘Pass condition’, delete:
“Domain selection was performed and IVS registered on the circuit switched network”.
6 Modification to 9.2.7, “CTP 1.1.2.5 Domain selection performed and eCall
initiated in PS domain in different RAT - IVS”
th
In Table 11, 14 row, under column ‘Tester action’, delete:
“ or manual”.
7 Modifications to 9.2.8, “CTP 1.1.6.1 eCall successful in CS domain - IVS”
th
In Table 12, 11 row, under column ‘Tester action’, replace:
“Check that the IVS completed” the network registration on the circuit switched network
with:
“IVS may have completed or skipped” the network registration on the circuit switched network

th
In Table 12, 11 row, under column ‘Pass condition’, delete:
“IVS registration was completed on the circuit switched network”.
8 Modifications to 9.2.9, “CTP 1.1.6.2 eCall successful in CS domain in limited
service state - IVS”
th
In Table 13, 12 row, under column ‘Tester action’, replace:
“Check that the IVS completed” the network registration on the circuit switched network
with:
“The IVS may have attempted or skipped” the network registration on the circuit switched network

th
In Table 13, 12 row, under column ‘Pass condition’, delete:
“Recognise network registration attempt on circuit switched network”.

th
In Table 13, 13 row, under column ‘Tester action’, add:
“, if attempted by the IVS”.
9 Modification to 9.2.11, “CTP 1.1.10.1 Domain change and fallback to IMS
emergency call in PS domain after network registration and eCall failed and after
unsuccessful re-attempt in CS domain - IVS”
th nd
In Table 15, 8 row, 2 column, replace (2x):
…(Release “16”)…
with:
…(“in” Release “14 to Release 19”)…

th
In Table 15, 18 row, replace (2x):
...after eCall was “dropped”
with:
...after eCall was “rejected”.
10 Modifications to 9.2.12, “CTP 1.1.10.2 Domain change and fallback to IMS
emergency call in PS domain after eCall failed and after unsuccessful re-attempt
in CS domain - IVS”
th nd
In Table 16, 8 row, 2 column, replace (2x):
…(Release “16”)…
with:
…(“in” Release “14 to Release 19”)…

th
In Table 16, 12 row, under column ‘Tester action’, replace:
“Check that the IVS completed” the network registration on the circuit switched network
with:
“The IVS may have attempted or skipped” the network registration on the circuit switched network

th
row, under column ‘Pass condition’, delete:
In Table 16, 12
“IVS registration was completed on the circuit switched network”.

th
In Table 16, 16 row, replace (2x):
...after eCall was “dropped”
with:
...after eCall was “rejected”.
11 Modification to 9.2.13, “CTP 1.1.10.3 Fallback to IMS emergency call in PS
domain after missing AL-ACK for initial MSD - IVS”
th nd
In Table 17, 8 row, 2 column, replace:
…(Release “16”)…
with:
…(“in” Release “14 to Release 19”)…
12 Modifications to 9.2.14, “CTP 1.1.10.4 Domain change and fallback to IMS
emergency call in PS domain after eCall is dropped before the MSD is
acknowledged and after unsuccessful re-attempt in CS domain - IVS”
th nd
In Table 18, 8 row, 2 column, delete:
…“the IVS supports the parts of Annex H.6 in ETSI TS 123 167 (Release 16), where the IVS performs
domain selection following an eCall failure in a CS network or”…

th nd
In Table 18, 8 row, 2 column, replace:
…(Release “16”)…
with:
…(“in” Release “14 to Release 19”)…

th
In Table 18, 12 row, under column ‘Tester action’, replace:
“Check that the IVS completed” the network registration on the circuit switched network
with:
“The IVS may have attempted or skipped” the network registration on the circuit switched network

th
In Table 18, 12 row, under column ‘Pass condition’, delete:
“IVS registration was completed on the circuit switched network”.

th
In Table 18, 16 row, under column ‘Tester action’, replace:
...and reject the redial attempt(s)...
with:
...and “configure the PSAP test point to” reject the redial attempt(s)...

th
In Table 18, 17 row, replace (2x):
...after eCall was “dropped”
with:
...after eCall was “terminated abnormally”.
13 Modifications to 9.2.15, “CTP 1.1.10.5 Fallback to emergency call in CS domain
- IVS”
th
In Table 19, 12 row, under column ‘Tester action’, replace:
“Check that the IVS completed” the network registration on the circuit switched network
with:
“The IVS may have attempted or skipped” the network registration on the circuit switched network

th
In Table 19, 12 row, under column ‘Pass condition’, delete:
“IVS registration was completed on the circuit switched network”.
14 Modifications to 9.2.16, “CTP 1.1.10.6 Domain change to PS domain after
network registration and eCall failed in CS domain - IVS”
th nd
In Table 20, 6 row, 2 column, replace:
EN 17184:2024 (…)
with:
EN 17184:2024+A1:2026 (…)
th nd
row, 2 column, replace (2x):
In Table 20, 6
…(Release “16”)…
with:
…(Release “14 to Release 19”)…

th nd
In Table 20, 8 row, 2 column, replace (2x):
…(Release “16”)…
with:
…(“in” Release “14 to Release 19”)…

th
row, under column ‘Tester action’, replace:
In Table 20, 13
“Check that the IVS attempts” the network registration on circuit switched network
with:
“The IVS may have attempted or skipped” the network registration on “the” circuit switched network

th
In Table 20, 13 row, under column ‘Pass condition’, delete:
“Recognise network registration attempt on circuit switched network”.

th
In Table 20, 14 row, under column ‘Tester action’, add:
“, if attempted by the IVS”.
15 Modifications to 9.2.17, “CTP 1.1.10.7 Domain change to PS domain after eCall
failed in CS domain - IVS”
th nd
In Table 21, 6 row, 2 column, replace:
EN 17184:2024 (…)
with:
EN 17184:2024+A1:2026 (…)
th nd
In Table 21, 6 row, 2 column, replace (2x):
…(Release “16”)…
with:
…(Release “14 to Release 19”)…

th nd
In Table 21, 8 row, 2 column, replace (2x):
…(Release “16”)…
with:
…(“in” Release “14 to Release 19”)…

th
In Table 21, 12 row, under column ‘Tester action’, replace:
“Check that the IVS attempts” the network registration on circuit switched network
with:
“The IVS may have attempted or skipped” the network registration on “the” circuit switched network

th
In Table 21, 12 row, under column ‘Pass condition’, delete:
“IVS registration was completed on the circuit switched network”.
16 Modifications to 9.2.18, “CTP 1.1.10.8 Domain change to CS domain after eCall
failed in PS domain - IVS”
Replace Table 22 with the following:
“
SUT reference ‘In-Vehicle System’
CTP/IVS/ECI/1.1.10.8 Verify that the IVS attempts eCall in CS doma
...