hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.1.10.2 Description | Interoperability Test Description Identifier LOC_RFH_01 Test Objective Verify the standard-compliant location refresh from the originating device (VoIP) to the control centre (PSAP) using SIP methods UPDATE or INVITE Configuration VoIP References ETSI TS 103 479 [1] Applicability UE (SIP-1, SIP-2, SIP-4, RTP-1, RTP-2) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, SIP-4, RTP-1, RTP-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • UE configured to register with SIP Proxy/Registrar • UE has location information (value) available • SIP Proxy trigger points for emergency call routing (to BCF) • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query the ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus SIP dialog established 2 check PIDF/LO (LbV) received at PSAP 3 check Call connected and location displayed 4 verify In_dialog UPDATE or INVITE received 5 verify PIDF/LO (LbV) UPDATE received at PSAP 6 verify Call still connected and new location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 42 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.1.10.3 Message Sequence Chart | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.1.11 Location-Refresh (IMS) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.1.11.1 General | Identifier: LOC_RFH_02 This test is intended to verify the standard-compliant location refresh from the originating device (UE) to the control centre (PSAP) using SIP methods UPDATE or INVITE. This test shall use the configuration as described in clause 5.3 IMS of the present document. ETSI ETSI TS 103 480 V1.1.1 (2026-03) 43 The originating network infrastructure shall support location-by-value, which transmits geodetic (e.g. point, circle, polygon) in a PIDF-LO as defined in ETSI TS 103 479 [1]. NOTE 1: This scenario can be combined with the test description according to clause 7.1.2 in a single test run. NOTE 2: For NG eCall tests, it is assumed that the IVS provides a PIDF/LO in a SIP UPDATE or INVITE to refresh the location. Other methods for requesting location updates via MSD are outside the scope of the present document. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.1.11.2 Description | Interoperability Test Description Identifier LOC_RFH_02 Test Objective Verify the standard-compliant location refresh from the originating device (VoIP) to the control centre (PSAP) using SIP methods UPDATE or INVITE Configuration IMS References ETSI TS 103 479 [1], ETSI TS 123 167 [2], ETSI TS 123 333 [3] Applicability UE (SIP-1, SIP-2, SIP-4, RTP-1, RTP-2) IMS (Le, Mm, Mb) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, SIP-4, RTP-1, RTP-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • UE configured to register with SIP Proxy/Registrar • UE has location information (value) available • SIP Proxy trigger points for emergency call routing (to BCF) • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query the ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus SIP dialog established 2 check PIDF/LO (LbV) received at PSAP 3 check Call connected and location displayed 4 verify In_dialog UPDATE or INVITE received 5 verify PIDF/LO (LbV) UPDATE received at PSAP 6 verify Call still connected and new location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 44 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.1.11.3 Message Sequence Chart | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2 Multimedia | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.1 Audio (VoIP) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.1.1 General | Identifier: MME_AUD_01 ETSI ETSI TS 103 480 V1.1.1 (2026-03) 45 This test is intended to verify the standard-compliant transmission of audio from the originating network (VoIP) to the control centre (PSAP) transmitted via RTP. This test shall use the configuration as described in clause 5.2 VoIP of the present document. In the case an UE does not support either LbV or LbR, the location information can also be determined via LIS and a UE identity (tel or sip URI) from the ESRP. Optionally, LIS* and ESRP* can be operated outside the ESInet for this purpose. The originating network infrastructure shall support proper audio codecs as defined in ETSI TS 103 479 [1]. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.1.2 Description | Interoperability Test Description Identifier MME_AUD_01 Test Objective Verify the standard-compliant transmission of audio (a) from the originating network (VoIP) to the control centre (PSAP) transmitted via RTP Configuration VoIP References ETSI TS 103 479 [1] Applicability UE (SIP-1, SIP-2, RTP-1, RTP-2) LIS (HELD-1, HELD-2) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2, HELD-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2, HELD-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • UE configured to register with SIP Proxy/Registrar • UE has location information (reference) available • SIP Proxy trigger points for emergency call routing (to BCF) • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query LIS and ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials emergency number (e.g. 112) 2 check Dialog creating INVITE (a) received at BCF 3 check Dialog creating INVITE (a) received at ESRP 4 check ESRP queries location information (by identity) 5 check LoST request received at ECRF 6 check ESRP emergency call routing based on location 7 check Dialog creating INVITE (a) received at PSAP 8 check SIP dialog established 9 verify Call (a) connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 46 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.1.3 Message Sequence Chart | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.2 Audio (IMS) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.2.1 General | Identifier: MME_AUD_02 ETSI ETSI TS 103 480 V1.1.1 (2026-03) 47 This test is intended to verify the standard-compliant transmission of audio from the originating network (IMS) to the control centre (PSAP) transmitted via RTP. This test shall use the configuration as described in clause 5.3 IMS of the present document. The originating network infrastructure shall support proper audio codecs as defined in ETSI TS 103 479 [1]. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.2.2 Description | Interoperability Test Description Identifier MME_AUD_02 Test Objective Verify the standard-compliant transmission of audio (a) from the originating network (IMS) to the control centre (PSAP) transmitted via RTP Configuration IMS References ETSI TS 103 479 [1], ETSI TS 123 167 [2], ETSI TS 123 333 [3] Applicability IMS (Le, Mm, Mb) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • ECSCF trigger points for emergency call routing • LRF has location information (value) available • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query the ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials test emergency number 2 check Dialog creating INVITE (a) received at BCF 3 check Dialog creating INVITE (a) received at ESRP 4 check LoST request received at ECRF 5 check ESRP emergency call routing based on location 6 check Dialog creating INVITE (a) received at PSAP 7 check SIP dialog established 8 verify Call (a) connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 48 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.2.3 Message Sequence Chart | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.3 Audio (PSTN/PABX) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.3.1 General | Identifier: MME_AUD_03 ETSI ETSI TS 103 480 V1.1.1 (2026-03) 49 This test is intended to verify the standard-compliant transmission of audio from the originating network (PSTN/PABX) to the control centre (PSAP) transmitted via RTP. This test shall use the configuration as described in clause 5.4 VoIP of the present document. The originating network infrastructure shall support proper audio codecs as defined in ETSI TS 103 479 [1]. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.3.2 Description | Interoperability Test Description Identifier MME_AUD_03 Test Objective Verify the standard-compliant transmission of audio (a) from the originating network (PSTN/PABX) to the control centre (PSAP) transmitted via RTP Configuration PSTN/PABX References ETSI TS 103 479 [1] Applicability LNG (SIP-1, SIP-2, RTP-1, RTP-2, HELD-2) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2, HELD-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2, HELD-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • LNG trigger points for emergency call routing • LNG has location information (value) available • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query LIS and ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials test emergency number 2 check Dialog creating INVITE (a) received at BCF 3 check Dialog creating INVITE (a) received at ESRP 4 check ESRP dereferences location information 5 check LoST request received at ECRF 6 check ESRP emergency call routing based on location 7 check Dialog creating INVITE (a) received at PSAP 8 check SIP dialog established 9 verify Call connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 50 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.3.3 Message Sequence Chart | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.4 Video (VoIP) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.4.1 General | Identifier: MME_VID_01 This test is intended to verify the standard-compliant transmission of audio and video from the originating network (VoIP) to the control centre (PSAP) transmitted via RTP. ETSI ETSI TS 103 480 V1.1.1 (2026-03) 51 This test shall use the configuration as described in clause 5.2 VoIP of the present document. In the case an UE does not support either LbV or LbR, the location information can also be determined via LIS and a UE identity (tel or sip URI) from the ESRP. Optionally, LIS* and ESRP* can be operated outside the ESInet for this purpose. The originating network infrastructure shall support proper audio and video codecs as defined in ETSI TS 103 479 [1]. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.4.2 Description | Interoperability Test Description Identifier MME_VID_01 Test Objective Verify the standard-compliant transmission of audio (a) and video (v) from the originating network (VoIP) to the control centre (PSAP) transmitted via RTP Configuration VoIP References ETSI TS 103 479 [1] Applicability UE (SIP-1, SIP-2, RTP-1, RTP-2) LIS (HELD-1, HELD-2) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2, HELD-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2, HELD-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • UE configured to register with SIP Proxy/Registrar • UE has location information (reference) available • SIP Proxy trigger points for emergency call routing (to BCF) • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query LIS and ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials emergency number (e.g. 112) 2 check Dialog creating INVITE (a/v) received at BCF 3 check Dialog creating INVITE (a/v) received at ESRP 4 check ESRP queries location information (by identity) 5 check LoST request received at ECRF 6 check ESRP emergency call routing based on location 7 check Dialog creating INVITE (a/v) received at PSAP 8 check SIP dialog established 9 verify Call (a/v) connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 52 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.4.3 Message Sequence Chart | ETSI ETSI TS 103 480 V1.1.1 (2026-03) 53 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.5 Video (IMS) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.5.1 General | Identifier: MME_VID_02 This test is intended to verify the standard-compliant transmission of audio and video from the originating network (IMS) to the control centre (PSAP) transmitted via RTP. This test shall use the configuration as described in clause 5.3 IMS of the present document. The originating network infrastructure shall support proper audio and video codecs as defined in ETSI TS 103 479 [1]. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.5.2 Description | Interoperability Test Description Identifier MME_VID_02 Test Objective Verify the standard-compliant transmission of audio (a) and video (v) from the originating network (IMS) to the control centre (PSAP) transmitted via RTP Configuration IMS References ETSI TS 103 479 [1], ETSI TS 123 167 [2], ETSI TS 123 333 [3] Applicability IMS (Le, Mm, Mb) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • ECSCF trigger points for emergency call routing • LRF has location information (value) available • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query the ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials test emergency number 2 check Dialog creating INVITE (a/v) received at BCF 3 check Dialog creating INVITE (a/v) received at ESRP 4 check LoST request received at ECRF 5 check ESRP emergency call routing based on location 6 check Dialog creating INVITE (a/v) received at PSAP 7 check SIP dialog established 8 verify Call (a/v) connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 54 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.5.3 Message Sequence Chart | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.6 Real-time Text (VoIP) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.6.1 General | Identifier: MME_RTT_01 This test is intended to verify the standard-compliant transmission of real-time text from the originating network (VoIP) to the control centre (PSAP) transmitted via RTP. ETSI ETSI TS 103 480 V1.1.1 (2026-03) 55 This test shall use the configuration as described in clause 5.2 VoIP of the present document. In the case an UE does not support either LbV or LbR, the location information can also be determined via LIS and a UE identity (tel or sip URI) from the ESRP. Optionally, LIS* and ESRP* can be operated outside the ESInet for this purpose. The originating network infrastructure shall support proper text encoding as defined in ETSI TS 103 479 [1]. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.6.2 Description | Interoperability Test Description Identifier MME_RTT_01 Test Objective Verify the standard-compliant transmission of audio (a) and real-time text (t) from the originating network (VoIP) to the control centre (PSAP) transmitted via RTP Configuration VoIP References ETSI TS 103 479 [1] Applicability UE (SIP-1, SIP-2, RTP-1, RTP-2) LIS (HELD-1, HELD-2) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2, HELD-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2, HELD-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • UE configured to register with SIP Proxy/Registrar • UE has location information (reference) available • SIP Proxy trigger points for emergency call routing (to BCF) • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query the ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials emergency number (e.g. 112) 2 check Dialog creating INVITE (a/t) received at BCF 3 check Dialog creating INVITE (a/t) received at ESRP 4 check ESRP queries location information (by identity) 5 check LoST request received at ECRF 6 check ESRP emergency call routing based on location 7 check Dialog creating INVITE (a/t) received at PSAP 8 check SIP dialog established 9 verify Call (a/t) connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 56 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.6.3 Message Sequence Chart | ETSI ETSI TS 103 480 V1.1.1 (2026-03) 57 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.7 Real-time Text (IMS) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.7.1 General | Identifier: MME_RTT_02 This test is intended to verify the standard-compliant transmission of real-time text from the originating network (IMS) to the control centre (PSAP) transmitted via RTP. This test shall use the configuration as described in clause 5.2 VoIP of the present document. In the case an UE does not support either LbV or LbR, the location information can also be determined via LIS and a UE identity (tel or sip URI) from the ESRP. Optionally, LIS* and ESRP* can be operated outside the ESInet for this purpose. The originating network infrastructure shall support proper text encoding as defined in ETSI TS 103 479 [1]. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.7.2 Description | Interoperability Test Description Identifier MME_RTT_02 Test Objective Verify the standard-compliant transmission of audio (a) and real-time text (t) from the originating network (IMS) to the control centre (PSAP) transmitted via RTP Configuration IMS References ETSI TS 103 479 [1], ETSI TS 123 167 [2], ETSI TS 123 333 [3] Applicability IMS (Le, Mm, Mb) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • ECSCF trigger points for emergency call routing • LRF has location information (value) available • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query the ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials test emergency number 2 check Dialog creating INVITE (a/t) received at BCF 3 check Dialog creating INVITE (a/t) received at ESRP 4 check LoST request received at ECRF 5 check ESRP emergency call routing based on location 6 check Dialog creating INVITE (a/t) received at PSAP 7 check SIP dialog established 8 verify Call (a/t) connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 58 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.7.3 Message Sequence Chart | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.8 Total Conversation (VoIP) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.8.1 General | Identifier: MME_TOC_01 This test is intended to verify the standard-compliant transmission of audio, video and real-time text from the originating network (VoIP) to the control centre (PSAP) transmitted via RTP. ETSI ETSI TS 103 480 V1.1.1 (2026-03) 59 This test shall use the configuration as described in clause 5.2 VoIP of the present document. In the case an UE does not support either LbV or LbR, the location information can also be determined via LIS and a UE identity (tel or sip URI) from the ESRP. Optionally, LIS* and ESRP* can be operated outside the ESInet for this purpose. The originating network infrastructure shall support proper audio, video codec and text encoding as defined in ETSI TS 103 479 [1]. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.8.2 Description | Interoperability Test Description Identifier MME_TOC_01 Test Objective Verify the standard-compliant transmission of audio (a), video (v) and real-time text (t) from the originating network (VoIP) to the control centre (PSAP) transmitted via RTP Configuration VoIP References ETSI TS 103 479 [1] Applicability UE (SIP-1, SIP-2, RTP-1, RTP-2) LIS (HELD-1, HELD-2) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2, HELD-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2, HELD-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • UE configured to register with SIP Proxy/Registrar • UE has location information (reference) available • SIP Proxy trigger points for emergency call routing (to BCF) • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query LIS and ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials emergency number (e.g. 112) 2 check Dialog creating INVITE (a/v/t) received at BCF 3 check Dialog creating INVITE (a/v/t) received at ESRP 4 check ESRP queries location information (by identity) 5 check LoST request received at ECRF 6 check ESRP emergency call routing based on location 7 check Dialog creating INVITE (a/v/t) received at PSAP 8 check SIP dialog established 9 verify Call (a/v/t) connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 60 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.8.3 Message Sequence Chart | ETSI ETSI TS 103 480 V1.1.1 (2026-03) 61 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.9 Total Conversation (IMS) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.9.1 General | Identifier: MME_TOC_02 This test is intended to verify the standard-compliant transmission of audio, video and real-time text from the originating network (IMS) to the control centre (PSAP) transmitted via RTP. This test shall use the configuration as described in clause 5.3 IMS of the present document. The originating network infrastructure shall support proper audio, video codec and text encoding as defined in ETSI TS 103 479 [1]. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.9.2 Description | Interoperability Test Description Identifier MME_TOC_02 Test Objective Verify the standard-compliant transmission of audio (a), video (v) and real-time text (t) from the originating network (IMS) to the control centre (PSAP) transmitted via RTP Configuration IMS References ETSI TS 103 479 [1], ETSI TS 123 167 [2], ETSI TS 123 333 [3] Applicability IMS (Le, Mm, Mb) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • ECSCF trigger points for emergency call routing • LRF has location information (value) available • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query the ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials test emergency number 2 check Dialog creating INVITE (a/v/t) received at BCF 3 check Dialog creating INVITE (a/v/t) received at ESRP 4 check LoST request received at ECRF 5 check ESRP emergency call routing based on location 6 check Dialog creating INVITE (a/v/t) received at PSAP 7 check SIP dialog established 8 verify Call (a/v/t) connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 62 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.2.9.3 Message Sequence Chart | ETSI ETSI TS 103 480 V1.1.1 (2026-03) 63 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.3 Policy | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.3.1 Time and Date (VoIP, IMS, PSTN/PABX) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.3.1.1 General | Identifier: POL_TAD_01 This test is intended to verify standard-compliant policy routing of emergency calls originating from different networks (VoIP, IMS, PSTN/PABX) and forwarded to a control centre (PSAP) based on location and date and/or time conditions. This test shall use the configuration as described in clauses 5.2 VoIP, 5.3 IMS, and 5.4 PSTN/PABX of the present document. In the case an UE does not support either LbV or LbR, the location information can also be determined via LIS and a UE identity (tel or sip URI) from the ESRP. Optionally, LIS* and ESRP* can be operated outside the ESInet for this purpose. The originating network infrastructure shall support proper audio codecs as defined in ETSI TS 103 479 [1]. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.3.1.2 Description | Interoperability Test Description Identifier POL_TAD_01 Test Objective Verify standard-compliant policy routing of emergency calls originating from different networks (VoIP, IMS, PSTN/PABX) and forwarded to a control centre (PSAP) based on location and date and/or time conditions Configuration VoIP, IMS, PSTN/PABX References ETSI TS 103 479 [1] Applicability UE (SIP-1, SIP-2, RTP-1, RTP-2)|IMS (Le, Mm, Mb)|LNG ([UE] + HELD-2) LIS (HELD-1, HELD-2) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2, HELD-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2, HELD-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • UE configured to register with SIP Proxy/Registrar • UE has location information (reference) available • SIP Proxy trigger points for emergency call routing (to BCF) • BCF trigger points for emergency call routing (to ESRP) • PRF configured with proper ruleset (date/time condition) • ESRP trigger points for emergency call routing • ESRP configured to query LIS and ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials emergency number 2 check Dialog creating INVITE received at BCF 3 check Dialog creating INVITE received at ESRP 4 check ESRP queries location information (by identity) 5 check LoST request received at ECRF 6 check PRF applies specific rule 7 check ESRP emergency call routing based on condition 8 check Dialog creating INVITE received at PSAP 9 check SIP dialog established 10 verify Call connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 64 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.3.1.3 Message Sequence Chart | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.3.2 SIP Header (VoIP, IMS, PSTN/PABX) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.3.2.1 General | Identifier: POL_SIP_01 ETSI ETSI TS 103 480 V1.1.1 (2026-03) 65 This test is intended to verify standard-compliant policy routing of emergency calls originating from different networks (VoIP, IMS, PSTN/PABX) and forwarded to a control centre (PSAP) based on location and certain SIP header value conditions (e.g. SIP From header value). This test shall use the configuration as described in clauses 5.2 VoIP, 5.3 IMS, and 5.4 PSTN/PABX of the present document. In the case an UE does not support either LbV or LbR, the location information can also be determined via LIS and a UE identity (tel or sip URI) from the ESRP. Optionally, LIS* and ESRP* can be operated outside the ESInet for this purpose. The originating network infrastructure shall support proper audio codecs as defined in ETSI TS 103 479 [1]. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.3.2.2 Description | Interoperability Test Description Identifier POL_SIP_01 Test Objective Verify standard-compliant policy routing of emergency calls originating from different networks (VoIP, IMS, PSTN/PABX) and forwarded to a control centre (PSAP) based on location and certain SIP header value conditions Configuration VoIP, IMS, PSTN/PABX References ETSI TS 103 479 [1] Applicability UE (SIP-1, SIP-2, RTP-1, RTP-2)|IMS (Le, Mm, Mb)|LNG ([UE] + HELD-2) LIS (HELD-1, HELD-2) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2, HELD-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2, HELD-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • UE configured to register with SIP Proxy/Registrar • UE has location information (reference) available • SIP Proxy trigger points for emergency call routing (to BCF) • BCF trigger points for emergency call routing (to ESRP) • PRF configured with proper ruleset (SIP header value condition) • ESRP trigger points for emergency call routing • ESRP configured to query LIS and ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials emergency number 2 check Dialog creating INVITE received at BCF 3 check Dialog creating INVITE received at ESRP 4 check ESRP queries location information (by identity) 5 check LoST request received at ECRF 6 check PRF applies specific rule 7 check ESRP emergency call routing based on condition 8 check Dialog creating INVITE received at PSAP 9 check SIP dialog established 10 verify Call connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 66 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.3.2.3 Message Sequence Chart | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4 Lost Hierarchy | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4.1 Iteration (ESRP) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4.1.1 General | Identifier: LST_ITE01 ETSI ETSI TS 103 480 V1.1.1 (2026-03) 67 This test is intended to verify the standard-compliant handling of LoST Redirect responses and iterative LoST querying on the ESRP. This test shall use the configuration as described in clause 5.2 VoIP of the present document. The originating network infrastructure shall support proper audio codecs as defined in ETSI TS 103 479 [1]. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4.1.2 Description | Interoperability Test Description Identifier LST_ITE_01 Test Objective Verify the standard-compliant handling of LoST Redirect responses and iterative LoST querying on the ESRP. Configuration VoIP References ETSI TS 103 479 [1] Applicability UE (SIP-1, SIP-2, RTP-1, RTP-2) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • UE configured to register with SIP Proxy/Registrar • UE has location information (value) available • SIP Proxy trigger points for emergency call routing (to BCF) • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query the ECRF_A • ECRF_A configured with no mapping and ECRF_B as the higher level ECRF • ECRF_B configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials emergency number (e.g. 112) 2 check Dialog creating INVITE (LbV) received at BCF 3 check Dialog creating INVITE (LbV) received at ESRP 4 check LoST request received at ECRF_A 5 check LoST request received at ECRF_B (from ESRP) 6 check ESRP emergency call routing based on location 7 check Dialog creating INVITE (LbV) received at PSAP 8 check SIP dialog established 9 verify PIDF/LO (LbV) received at PSAP 10 verify Call connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 68 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4.1.3 Message Sequence Chart | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4.2 Recursion (ESRP) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4.2.1 General | Identifier: LST_REC_01 This test is intended to verify the standard-compliant recursive handling of LoST requests on the ECRF. This test shall use the configuration as described in clause 5.2 VoIP of the present document. The originating network infrastructure shall support proper audio codecs as defined in ETSI TS 103 479 [1]. ETSI ETSI TS 103 480 V1.1.1 (2026-03) 69 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4.2.2 Description | Interoperability Test Description Identifier LST_REC_01 Test Objective Verify the standard-compliant recursive handling of LoST requests on the ECRF. Configuration VoIP References ETSI TS 103 479 [1] Applicability UE (SIP-1, SIP-2, RTP-1, RTP-2) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • UE configured to register with SIP Proxy/Registrar • UE has location information (value) available • SIP Proxy trigger points for emergency call routing (to BCF) • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query the ECRF_A • ECRF_A configured with no mapping and ECRF_B as the higher level ECRF • ECRF_B configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials emergency number (e.g. 112) 2 check Dialog creating INVITE (LbV) received at BCF 3 check Dialog creating INVITE (LbV) received at ESRP 4 Check LoST request received at ECRF_A 5 Check LoST request received at ECRF_B (from ECRF_A) 6 check ESRP emergency call routing based on location 7 check Dialog creating INVITE (LbV) received at PSAP 8 check SIP dialog established 9 verify PIDF/LO (LbV) received at PSAP 10 verify Call connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 70 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4.2.3 Message Sequence Chart | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4.3 Recursion (ECRF) with FG | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4.3.1 General | Identifier: LST_REC_02 This test is intended to verify the standard-compliant recursive handling of LoST requests on the ECRF when it receives a LoST redirect from a FG. This test shall use the configuration as described in clause 5.2 VoIP of the present document. The originating network infrastructure shall support proper audio codecs as defined in ETSI TS 103 479 [1]. ETSI ETSI TS 103 480 V1.1.1 (2026-03) 71 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4.3.2 Description | Interoperability Test Description Identifier LST_REC_02 Test Objective Verify the standard-compliant recursive handling of LoST requests on the ECRF. Configuration VoIP References ETSI TS 103 479 [1] Applicability UE (SIP-1, SIP-2, RTP-1, RTP-2) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • UE configured to register with SIP Proxy/Registrar • UE has location information (value) available • SIP Proxy trigger points for emergency call routing (to BCF) • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query the ECRF_A • ECRF_A configured with no mapping and and FG as Forest Guide • FG configured to return a redirect to ECRF_B • ECRF_B configured with correct mapping Test Sequence Step Type Description 1 stimulus User dials emergency number (e.g. 112) 2 check Dialog creating INVITE (LbV) received at BCF 3 check Dialog creating INVITE (LbV) received at ESRP 4 check LoST request received at ECRF_A 5 check LoST request received at FG (from ECRF_A) 6 check LoST request received at ECRF_B (from ECRF_A) 7 check ESRP emergency call routing based on location 8 check Dialog creating INVITE (LbV) received at PSAP 9 check SIP dialog established 10 verify PIDF/LO (LbV) received at PSAP 11 verify Call connected and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 72 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.4.3.3 Message Sequence Chart | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.5 Messaging | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.5.1 Basic Chat (VoIP) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.5.1.1 General | Identifier: MSG_LMP_01 This test is intended to verify the standard-compliant transmission of lightweight chat messages from the originating network (VoIP) to the control centre (PSAP) using LMPE. This test shall use the configuration as described in clause 5.2 VoIP of the present document. The originating network infrastructure and the PSAP shall support LMPE as defined in ETSI TS 103 698 [5]. ETSI ETSI TS 103 480 V1.1.1 (2026-03) 73 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.5.1.2 Description | Interoperability Test Description Identifier MSG_LMP_01 Test Objective Verify the standard-compliant transmission of lightweight chat messages from the originating network (VoIP) to the control centre (PSAP) Configuration VoIP References ETSI TS 103 479 [1], ETSI TS 103 698 [5] Applicability UE (SIP-1, SIP-2, IM-2) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, IM-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • UE configured to register with SIP Proxy/Registrar • UE has location information (value) available • SIP Proxy trigger points for emergency call routing (to BCF) • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query the ECRF • ECRF configured with correct mapping • UE and PSAP support LMPE Test Sequence Step Type Description 1 stimulus User dials emergency number 2 check Initial SIP MESSAGE (LbV) received at BCF (start) 3 check Initial SIP MESSAGE (LbV) received at ESRP (start) 4 check LoST request received at ECRF 5 check ESRP emergency call routing based on location 6 check Initial SIP MESSAGE (LbV) received at PSAP (start) 7 check PSAP responds with SIP MESSAGE (Reply-To, start) 8 verify PIDF/LO (LbV) received at PSAP 9 verify Chat connected (in-chat) and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 74 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.5.1.3 Message Sequence Chart | ETSI ETSI TS 103 480 V1.1.1 (2026-03) 75 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.6 NG eCall | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.6.1 Basic Communication (IMS) | |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.6.1.1 General | Identifier: ECL_BAS_01 This test is intended to verify the standard-compliant transmission of MSD data and audio from the IVS via the originating network (IMS) to the control centre (PSAP) transmitted via SIP and RTP. This test shall use the configuration as described in clause 5.3 IMS of the present document. The originating network infrastructure shall support proper audio codecs as defined in ETSI TS 103 479 [1]. NOTE: For NG eCall tests, it is assumed that the IVS provides a PIDF/LO in the INVITE to be used for routing purposes. In the case a PIDF/LO is missing, other mechanisms such as policy routing rules in the ESRP can be used to forward to the correct PSAP. |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.6.2.2 Description | Interoperability Test Description Identifier ECL_BAS_01 Test Objective Verify that the IVS is able to initiate a manual eCall containing MSD and the correct eCall initiation indicator for a manually triggered eCall Configuration IMS References ETSI TS 103 479 [1], ETSI TS 123 167 [2], ETSI TS 123 333 [3], ETSI TS 103 683 [7] Applicability IMS (Le, Mm, Mb) BCF (SIP-1, SIP-2, RTP-1, RTP-2) ESRP (SIP-1, SIP-2, LOST-1, LOST-2) ECRF (LOST-1, LOST-2) PSAP (SIP-1, SIP-2, RTP-1, RTP-2) Pre-test conditions • IP connectivity among all elements of the specific scenario • ECSCF trigger points for emergency call routing • LRF has location information (value) available • BCF trigger points for emergency call routing (to ESRP) • ESRP trigger points for emergency call routing • ESRP configured to query the ECRF • ECRF configured with correct mapping Test Sequence Step Type Description 1 stimulus IVS initiates a manual eCall 2 check Dialog creating INVITE (a) received at BCF 3 check Dialog creating INVITE (a) received at ESRP 4 check LoST request received at ECRF 5 check ESRP emergency call routing based on location 6 check Dialog creating INVITE (a) received at PSAP 7 check SIP dialog established 8 verify Call (a) connected, MSD and location displayed ETSI ETSI TS 103 480 V1.1.1 (2026-03) 76 |
86e6986b6aeb2d19cc290d2a4e077b24 | 103 480 | 7.6.2.3 Message Sequence Chart | ETSI ETSI TS 103 480 V1.1.1 (2026-03) 77 Annex A (normative): Interoperable Functions Statement (IFS) A.1 Entities Table A.1: Entities Item Which entity do you support? Status Support 1 UE 2 IMS 3 UC 4 LNG (PIF) 5 LNG (NIF) 6 LNG (LIF) 7 BCF 8 LIS 9 ESRP 10 ECRF 11 FG 12 BRIDGE 13 PSAP A.2 UE Features Table A.2: UE features Item Feature ID Ref Status Support 1 Does the UE support SIP? UE_SIP [1] 2 Does the UE support RTP? UE_RTP [1] 3 Does the UE support G.711? UE_G711 [1] 4 Does the UE support H.264? UE_H264 [1] 5 Does the UE support Real-time Text? UE_RTT [1] 6 Does the UE support PIDF/LO? UE_PFL [1] 7 Does the UE support service URNs? UE_URN [1] 8 Does the UE support AML (HTTP)? UE_AMLH [1] 9 Does the UE support AML (SMS)? UE_AMLS [1] 10 Does the UE support AML (DATA SMS)? UE_AMLD [1] 11 Does the UE support LMPE? UE_LMPE [5] A.3 IMS Features Table A.3: IMS features Item Feature ID Ref Status Support 1 Does the IMS support SIP? IMS_SIP [1] 2 Does the IMS support RTP? IMS_RTP [1] 3 Does the IMS support G.711? IMS_G711 [1] 4 Does the IMS support H.264? IMS_H264 [1] 5 Does the IMS support Real-time Text? IMS_RTT [1] 6 Does the IMS support HELD? IMS_HELD [1] 7 Does the IMS support NG specific SIP Header? IMS_NGS [1] 8 Does the IMS support PIDF/LO? IMS_PFL [1] 9 Does the IMS support service URNs? IMS_URN [1] ETSI ETSI TS 103 480 V1.1.1 (2026-03) 78 A.4 LNG (PIF) Features Table A.4: PIF features Item Feature ID Ref Status Support 1 Does the PIF support SIP? PIF_SIP [1] 2 Does the PIF support RTP? PIF_RTP [1] 3 Does the PIF support G.711? PIF_G711 [1] A.5 LNG (NIF) Features Table A.5: NIF features Item Feature ID Ref Status Support 1 Does the NIF support SIP? NIF_SIP [1] 2 Does the NIF support RTP? NIF_RTP [1] 3 Does the NIF support G.711? NIF_G711 [1] 4 Does the NIF support NG specific SIP Header? NIF_NGS [1] 5 Does the NIF support service URNs? NIF_URN [1] A.6 LNG (LIF) Features Table A.6: LIF features Item Feature ID Ref Status Support 1 Does the LIF support PIDF/LO? LIF_PFL [1] 2 Does the LIF support HELD? LIF_HELD [1] A.7 BCF Features Table A.7: BCF features Item Feature ID Ref Status Support 1 Does the BCF support SIP? BCF_SIP [1] 2 Does the BCF support RTP? BCF_RTP [1] 3 Does the BCF support G.711? BCF_G711 [1] 4 Does the BCF support H.264? BCF_H264 [1] 5 Does the BCF support HELD? BCF_HELD [1] 6 Does the BCF support NG specific SIP Header? BCF_NGS [1] 7 Does the BCF support PIDF/LO? BCF_PFL [1] 8 Does the BCF support service URNs? BCF_URN [1] 9 Does the BCF support Real-time Text? BCF_RTT [1] 10 Does the BCF support emergency call transfer? BCF_ECT [1] ETSI ETSI TS 103 480 V1.1.1 (2026-03) 79 A.8 LIS Features Table A.8: LIS features Item Feature ID Ref Status Support 1 Does the LIS support HELD? LIS_HELD [1] 2 Does the LIS support SIP SUBSCRIBE/NOTIFY location update? LIS_SIPLO [1] 3 Does the LIS support PIDF/LO? LIS_PFL [1] 4 Does the LIS support AML (HTTP)? LIS_AMLH [1] 5 Does the LIS support AML (SMS)? LIS_AMLS [1] 6 Does the LIS support AML (DATA SMS)? LIS_AMLD [1] A.9 ESRP Features Table A.9: ESRP features Item Feature ID Ref Status Support 1 Does the ESRP support SIP? ESRP_SIP [1] 2 Does the ESRP support SIP SUBSCRIBE/NOTIFY location update? ESRP_SIPLO [1] 3 Does the ESRP support SIP SUBSCRIBE/NOTIFY queue events? ESRP_SIPQU [1] 4 Does the ESRP support HELD? ESRP_HELD [1] 5 Does the ESRP support dequeue registration? ESRP_DEQU [1] 6 Does the ESRP support LoST? ESRP_LOST [1] 7 Does the ESRP support policy routing function? ESRP_PRF [1] 8 Does the ESRP support PIDF/LO? ESRP_PFL [1] 9 Does the ESRP support service URNs? ESRP_URN [1] 10 Does the ESRP support LoST iteration/redirection? ESRP_LRE [1] A.10 ECRF Features Table A.10: ECRF features Item Feature ID Ref Status Support 1 Does the ECRF support LoST? ECRF_LOST [1] 2 Does the ECRF support PIDF/LO? ECRF_PFL [1] 3 Does the ECRF support service URNs? ECRF_URN [1] 4 Does the ECRF support LoST recursion? ECRF_LRE [1] 5 Does the ECRF support LoST iteration? ECRF_LIT [1] 6 Does the ECRF support location validation? ECRF_VAL [1] A.11 BRIDGE Features Table A.11: BRIDGE features Item Feature ID Ref Status Support 1 Does the PSAP emergency call transfer? BRIDGE_ECT [1] ETSI ETSI TS 103 480 V1.1.1 (2026-03) 80 A.12 PSAP Features Table A.12: PSAP features Item Feature ID Ref Status Support 1 Does the PSAP support SIP? PSAP_SIP [1] 2 Does the PSAP support RTP? PSAP_RTP [1] 3 Does the PSAP support G.711? PSAP_G711 [1] 4 Does the PSAP support H.264? PSAP_H264 [1] 5 Does the PSAP support Real-time Text? PSAP_RTT [1] 6 Does the PSAP support SIP SUBSCRIBE/NOTIFY location update? PSAP_SIPLO [1] 7 Does the PSAP support SIP SUBSCRIBE/NOTIFY queue events? PSAP_SIPQU [1] 8 Does the PSAP support HELD? PSAP_HELD [1] 9 Does the PSAP support PIDF/LO? PSAP_PFL [1] 10 Does the PSAP support dequeue registration? PSAP_DEQU [1] 11 Does the PSAP support service URNs? PSAP_URN [1] 12 Does the PSAP emergency call transfer? PSAP_ECT [1] 13 Does the PSAP support LMPE? PSAP_LMPE [5] ETSI ETSI TS 103 480 V1.1.1 (2026-03) 81 Annex B (informative): Change history Date Version Information about changes January 2026 1.0.1 Initial version of the stable draft ETSI ETSI TS 103 480 V1.1.1 (2026-03) 82 History Version Date Status V1.1.1 March 2026 Publication |
1e77440904685da89cefd2bd994bd735 | 119 462 | 1 Scope | The present document provides an overview and analysis of the interfaces enabling interactions between the European Digital Identity Wallet (EUDIW) and trust service providers, including those related to electronic signing. In particular, the present document: • Describes the functional models and potential interface patterns between EUDIWs and trust service providers, covering scenarios where trust service providers issue certificates or attestations of attributes, as well as scenarios where they act as relying parties. • Outlines architectural considerations and interface components relevant to the creation of electronic signatures, especially where the trust service provider manages or operates the signature creation device. • Presents representative use cases demonstrating how the EUDIWs may be applied in trust service contexts such as electronic signatures, electronic seals, certificate issuance, and issuance of electronic attestation of attributes. • Identifies areas where existing interface specifications may support EUDIW-trust service integration, and highlights aspects that require harmonised specifications to ensure secure and interoperable implementations. The present document aims to inform ongoing and future standardization by providing a structured foundation for interface design between EUDIWs and trust services, supporting a consistent and trustworthy ecosystem. |
1e77440904685da89cefd2bd994bd735 | 119 462 | 2 References | |
1e77440904685da89cefd2bd994bd735 | 119 462 | 2.1 Normative references | Normative references are not applicable in the present document. |
1e77440904685da89cefd2bd994bd735 | 119 462 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. [i.2] Regulation (EU) 2024/1183 of the European Parliament and of the Council of 11 April 2024 amending Regulation (EU) No 910/2014 as regards establishing the European Digital Identity Framework. [i.3] Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive) (Text with EEA relevance). [i.4] Architecture and Reference Framework (ARF) EU Digital Identity Network 2.6.0. ETSI ETSI TR 119 462 V1.1.1 (2026-03) 8 [i.5] Commission Implementing Regulation 2024/2977 of 28 November 2024 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards person identification data and electronic attestations of attributes issued to European Digital Identity Wallets. [i.6] Commission Implementing Regulation (EU) 2024/2979 of 28 November 2024 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the integrity and core functionalities of European Digital Identity Wallets. [i.7] Commission Implementing Regulation 2024/2980 of 28 November 2024 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards notifications to the Commission concerning the European Digital Identity Wallet ecosystem. [i.8] Commission Implementing Regulation 2024/2982 of 28 November 2024 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards protocols and interfaces to be supported by the European Digital Identity Framework. [i.9] Commission Implementing Regulation 2025/848 of 6 May 2025 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the registration of wallet-relying parties. [i.10] ETSI EN 319 401: "Electronic Signatures and Trust Infrastructures (ESI); General Policy Requirements for Trust Service Providers". [i.11] ETSI EN 319 411-1: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 1: General requirements". [i.12] ETSI TS 119 431-1: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for trust service providers; Part 1: TSP services operating a remote QSCD/SCDev". [i.13] ETSI TS 119 431-2: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for trust service providers; Part 2: TSP service components supporting AdES digital signature creation". [i.14] ETSI TS 119 471: "Electronic Signatures and Trust Infrastructures (ESI); Policy and Security requirements for Providers of Electronic Attestation of Attributes Services". [i.15] ETSI TS 119 432: "Electronic Signatures and Infrastructures (ESI); Protocols for remote digital signature creation". [i.16] ETSI EN 319 102-1: "Electronic Signatures and Trust Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation". [i.17] ETSI EN 319 411-2: Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 2: Requirements for trust service providers issuing EU qualified certificates". [i.18] EN 419 241-1: "Trustworthy Systems Supporting Server Signing - Part 1: General System Security Requirements", (produced by CEN). [i.19] ISO/IEC 18013-5: Personal identification --- ISO-compliant driving licence - Part 5: Mobile driving licence (mDL) application. [i.20] ETSI TS 119 412-6: "Electronic Signatures and Trust Infrastructures (ESI); Certificate Profiles; Part 6: Certificate profile requirements for PID, Wallet, EAA, QEAA, and PSBEAA providers". [i.21] ISO/IEC 23220-3: "Cards and security devices for personal identification — Building blocks for identity management via mobile devices". [i.22] SD-JWT-based Verifiable Credentials (SD-JWT VC). [i.23] CTAP: "Client to Authenticator Protocol (CTAP) Proposed Standard", July 14, 2025. NOTE: Also available at https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical- specifications/issues/365. ETSI ETSI TR 119 462 V1.1.1 (2026-03) 9 [i.24] HAIP - OpenID4VC High Assurance Interoperability Profile, OpenID Foundation. [i.25] OpenID4VCI - OpenID for Verifiable Credential Issuance, OpenID Foundation. [i.26] OpenID4VP - OpenID for Verifiable Presentations, OpenID Foundation. [i.27] ETSI EN 319 132-1: "Electronic Signatures and Trust Infrastructures (ESI); XAdES digital signatures; Part 1: Building blocks and XAdES baseline signatures". [i.28] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures". [i.29] ETSI EN 319 142-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures". [i.30] ETSI TS 119 182-1: "Electronic Signatures and Trust Infrastructures (ESI); JAdES digital signatures; Part 1: Building blocks and JAdES baseline signatures". [i.31] ETSI EN 319 162-1: "Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC); Part 1: Building blocks and ASiC baseline containers". [i.32] CSC API V2.2: "Cloud Signature Consortium Architectures and protocols for remote signature applications.". [i.33] OASIS: "PKCS #11 Cryptographic Token Interface Base Specification Version 3.1". [i.34] ETSI TS 119 475: "Electronic Signatures and Trust Infrastructures (ESI); Relying party attributes supporting EUDI Wallet user's authorization decisions". [i.35] ETSI TS 119 411-8: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 8: Access Certificate Policy for EUDI Wallet Relying Parties". [i.36] W3C®: "Digital Credential", Working Draft 13 January 2026. [i.37] W3C®: "Verifiable Credential Data Model v2.0". [i.38] ETSI EN 319 162-2: "Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC); Part 2: Additional ASiC containers". [i.39] ETSI TS 119 101: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for applications for signature creation and signature validation". [i.40] ETSI TS 119 461: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for trust service components providing identity proofing of trust service subjects". [i.41] ETSI TS 119 472-1: "Electronic Signatures and Trust Infrastructures (ESI); Profiles for Electronic Attestation of Attributes; Part 1: General requirements". [i.42] ETSI TS 119 472-2: "Electronic Signatures and Trust Infrastructures (ESI); Profiles for Electronic Attestation of Attributes; Part 2: Profiles for EAA/PID Presentations to Relying Party". [i.43] ETSI TS 119 472-3: "Electronic Signatures and Trust Infrastructures (ESI); Profiles for Electronic Attestation of Attributes; Part 3: Profiles for issuance of EAA or PID". [i.44] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". [i.45] ETSI TS 119 479-3: "Electronic Signatures and Trust Infrastructures (ESI); Technological Solutions for the EU Digital Identity Framework; Part 3: Support for EAA within AdES signatures". ETSI ETSI TR 119 462 V1.1.1 (2026-03) 10 |
1e77440904685da89cefd2bd994bd735 | 119 462 | 3 Definition of terms, symbols and abbreviations | |
1e77440904685da89cefd2bd994bd735 | 119 462 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 119 401 [i.10], ETSI TS 119 431-1 [i.12], ETSI TS 119 431-2 [i.13], ETSI TS 119 471 [i.14] and the following apply: Certification Authority (CA): authority trusted by one or more users to create and assign certificates NOTE: See ETSI TS 319 411-1 [i.11]. |
1e77440904685da89cefd2bd994bd735 | 119 462 | 3.2 Symbols | Void. |
1e77440904685da89cefd2bd994bd735 | 119 462 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 119 401 [i.10], ETSI TS 119 431-1 [i.12], ETSI TS 119 432-2 [i.13], ETSI TS 119 471 [i.14] apply. |
1e77440904685da89cefd2bd994bd735 | 119 462 | 4 General concepts | |
1e77440904685da89cefd2bd994bd735 | 119 462 | 4.1 Digital Identity Wallet | |
1e77440904685da89cefd2bd994bd735 | 119 462 | 4.1.1 European Digital Identity Wallet | The European Digital Identity Wallet (EUDIW) is an electronic identification means issued under an EU-recognized scheme that enables a natural or legal person to securely manage their identity data and interact with trust service ecosystems in both online and offline environments. Under Article 5a(4)(a) of the eIDAS Regulation [i.1], the EUDIW empowers the user to: • securely request, obtain, select, combine, store, delete, share and present, under their sole control, Person Identification Data (PID) and Electronic Attestations Of Attributes (EAA); • authenticate to relying parties, including for access to public and private sector services, with support for selective disclosure of personal data; • and to sign using Qualified Electronic Signatures (QES) or seal using qualified electronic seals (QSealS). The EUDIW operates in interaction with Trust Service Providers (TSPs) for: • Identity proofing; • Electronic attribute issuance; • Remote signature/seal creation. a) Interaction with TSPs for Identity Proofing The EUDIW enables users to initiate secure sessions with TSPs that verify the user's identity in accordance with eIDAS Regulation [i.1], Article 24 and identity proofing standards [i.40]. After verification, the identity data is securely bound to the EUDIW and can be reused as a trusted basis for further trust services, including electronic attestations, signatures, and delivery. ETSI ETSI TR 119 462 V1.1.1 (2026-03) 11 b) Interaction with TSPs for Issuance of Electronic Attestations of Attributes The EUDIW provides a secure and authenticated interface for obtaining Electronic Attestations of Attributes (EAA) from TSPs, including Qualified Trust Service Providers (QTSPs), non-qualified Electronic Attestation of Attribute Service Providers (EAASPs) and Public Sector Electronic Attestations of Attributes (PUB-EAAs). c) Interaction with Signature Creation Service Providers (SCSPs) for QES/QSealS To support qualified electronic signatures or seals, the EUDIW integrates with Signature Creation Service Providers (SCSPs), which may be QTSPs operating remote Qualified Signature Creation Devices (QSCDs). |
1e77440904685da89cefd2bd994bd735 | 119 462 | 4.1.2 Digital Identity Wallet basic architectural components | The architecture of the EUDIW is based on the layered and modular structure described in the ARF [i.4]. This framework defines the main functional and technical components required to ensure interoperability, user control, trust, and privacy in the cross-border use of the EUDIW. The ARF [i.4] distinguishes between EUDIW ecosystem actors, EUDIW core components, and supporting services. The main architectural components of the EUDIW are: • Wallet Unit (WU): the software and secure hardware components (e.g. WSCD) installed on the user's device, responsible for storing, managing, and presenting PID and EAAs. • Wallet Secure Cryptographic Device (WSCD): a certified secure component that performs sensitive cryptographic operations and protects signature and seal keys. • Wallet Secure Cryptographic Application (WSCA): application logic managing access to the WSCD and enabling signing/sealing operations. • PID Provider: the entity responsible for verifying the identity of the user and issuing the PID in accordance with the eIDAS framework. • EAA Providers: electronic attestation of attributes trust services as defined in ETSI TS 119 471 [i.14]. • Signature Creation Service Provider (SCSP): signature creation service as defined in ETSI TS 119 431-2 [i.13]. • Presentation and Access Interfaces: APIs and user interfaces allowing the user to present PID and EAAs to relying parties in both online and offline contexts, supporting selective disclosure and consent-based sharing. |
1e77440904685da89cefd2bd994bd735 | 119 462 | 4.2 Wallet interfaces | |
1e77440904685da89cefd2bd994bd735 | 119 462 | 4.2.1 Interfaces defined in eIDAS Regulation | The present clause describes interfaces between the EUDIW and external actors, as directly established in the eIDAS Regulation [i.1]. The listed interfaces have been derived from a structured review of the legal requirements set out in Article 5a(4) and 5a(5), which define the core functionalities of the EUDIW, including interactions with trust service providers and relying parties. The purpose of this analysis is to identify the interfaces that are directly relevant to TSPs, including providers of identity, electronic attestation of attributes, and qualified electronic signatures and seals. The ARF [i.4] is referenced to map each legal provision to its corresponding technical and architectural realization. ETSI ETSI TR 119 462 V1.1.1 (2026-03) 12 Table 1: Interfaces and their descriptions defined in eIDAS Description of the Interface Requirement from the Regulation Reference to the Regulation Article [i.1] Reference to the ARF [i.4] EUDIW ← TSP (PID/EAA Issuance) EUDIW supports issuance interface for PID, (Q)EAAs or qualified and non-qualified certificates. Art 5a(5)(a)(i) 4.6.5, 6.6.2, Annex A.2.3 Topic 10 EUDIW ← RP (Request/Validation) RP requests/validates PID and EAA. Art 5a(5)(a)(ii) 6.6.3.6 EUDIW → RP (Presentation/Sharing) EUDIW supports presentation of PID/EAA/selectively disclosure data. Art 5a(5)(a)(iii) 6.6.3, Annex A.2.3.1 (OIA_01, OIA_05-06) EUDIW → UI (Trust Mark and Consent) EUDIW displays EU Trust Mark and allow consent for data sharing. Art 5a(5)(a)(iv) 6.5.3.6, Annex A.2.3 Topic 19 (DASH_09(b)) EUDIW ← Onboarding Source EUDIW supports secure onboarding with high assurance eID. Art 5a(5)(a)(v) 6.6.2.6, Annex A.2.3 Topic 10 (ISSU_05) EUDIW → EUDIW (P2P Exchange) EUDIW allows secure P2P data sharing. Art 5a(5)(a)(vi) 6.6.4, Annex A.2.3 Topic 30 EUDIW → RP (RP Authentication) EUDIW authenticates and validates RP before data sharing. Art 5a(5)(a)(vii-viii) 6.6.3.2 EUDIW → RP/Authorities (Erasure Requests) EUDIW allows users to submit erasure requests and reports to authorities. Art 5a(5)(a)(ix-x) 6.6.3.13, Annex A.2.3 Topic 48 EUDIW → Signature/Seal Provider EUDIW supports creation of QES/QSeal. Art 5a(a)(xi) 2.4, 3.9, Annex A.2.3 Topic 16 EUDIW ← User Verifies the authenticity and validity of EUDIW and RP Art 5a(8)(a) 6.5.2.2 NOTE: The direction of the arrow in the table above indicates the party initiating communication. |
1e77440904685da89cefd2bd994bd735 | 119 462 | 4.2.2 Interfaces defined in Commission Implementing Regulations (CIRs) | The present clause describes interfaces between the EUDIW and external systems or actors as established in secondary legislation - specifically, the Commission Implementing Regulations (CIRs) [i.5], [i.6], [i.7], [i.8], [i.9], issued under the revised eIDAS Regulation [i.1]. These CIRs define mandatory technical and procedural specifications for EUDIW operations, including credential issuance, cryptographic binding, trust mark handling, transaction logging, and revocation notifications. The included interfaces have been selected based on their importance to trust service providers, including Qualified Trust Service Providers (QTSPs), Signature Creation Service Providers (SCSPs), and Electronic Attestation of Attribute Service Providers (EAASPs). Where applicable, each interface is referenced to both its legal basis and its corresponding technical definition in the ARF [i.4]. ETSI ETSI TR 119 462 V1.1.1 (2026-03) 13 Table 2: Interfaces and their descriptions defined in CIRs Description of the Interface Requirement from the Regulation Reference to the CIR Article Reference to the ARF [i.4] EUDIW ← PID/EAA Provider Issue PID/EAA securely to EUDIW with revocation support. CIR 2024/2977 [i.5] Art 3-5 [i.7] 6.6.2, 6.6.5.4, Annex 2 Topics 7, 10 EUDIW → PID/EAA Provider Provide EUDIW Unit Attestation to issuer before credential issuance. CIR 2024/2977 [i.5] Art 3 6.6.2.3.1, Topic 9, 10 (ISSU_30) EUDIW ↔ WSCD Use secure cryptographic hardware for key protection and signing. CIR 2024/2979 [i.6] Art 4-6 4.3.2, 4.5 EUDIW ↔ RP Authenticate RP, support selective disclosure, consent, offline sharing. CIR 2024/2982 [i.8] Art 5, CIR 2024/2979 [i.6] Art 8-10 4.2.4, 6.6.3.2, 6.6.4, Topic 1 (OIA_07), 6, 9 (WUA_17) EUDIW Logging Log all user transactions with RP/TSP and allow export. CIR 2024/2979 [i.6] Art 9 Annex 2 Topic 19 EUDIW Disclosure Control Enforce embedded disclosure policies and user control. CIR 2024/2979 [i.6] Art 10 6.6.2.7, Annex 2 Topic 43 EUDIW ↔ QES/QSeal Engines Enable user to generate qualified signatures and seals. CIR 2024/2979 [i.6] Art 11-12 2.4, 4.3.3, Topic 16 EUDIW ← RP Verify RP registration and attribute request match. CIR 2025/848 [i.9], CIR 2024/2982 [i.8] Art 3 6.4.2, 6.4.3, Annex 2 Topic 6, 44 EUDIW ← Intermediaries Display intermediary and RP, enforce transparency. CIR 2025/848 [i.9], CIR 2024/2982 [i.8] Art 3 3.11, 6.6.3.4, 6.6.3.5, Annex 2 Topic 6, 52 NOTE: The direction of the arrow in the table above indicates who is the actor initiating communication. |
1e77440904685da89cefd2bd994bd735 | 119 462 | 4.2.3 Interfaces defined in ARF | The present clause consolidates interface definitions between the EUDIW and the actors as described in the ARF [i.4]. These interfaces may not be fully reflected in the eIDAS Regulation [i.1] or its implementing acts, but they form an essential part of the operational architecture of the EUDIW. The interfaces listed here result from a targeted analysis of the ARF [i.4], specifically those that are critical for trust service providers-including identity proofing, attribute issuance, qualified signature creation, relying party authentication, and revocation checking. Each interface entry includes a reference to the corresponding section or requirement set within the ARF and applicable supporting standards (e.g. ETSI TS 119 431-1 [i.12], ISO 18013-5 [i.19]). ETSI ETSI TR 119 462 V1.1.1 (2026-03) 14 Table 3: Interfaces and their descriptions defined in ARF Interface Name Description External Actor Standards/References Request & Receive PID Interface for identity proofing: EUDIW requests Person Identification Data from the PID Provider PID Provider • ARF (3.4, Annex 2 Topic 10 (B), Annex 3.1) [i.4]; • CIR 2024/2977 [i.5]; • CIR 2024/2982 [i.8]; • ISO 18013‑5 [i.19]; • SD‑JWT VC [i.22]; • W3C Digital Credentials API [i.36]; • OpenID4VCI [i.25]. Request & Receive EAA/QEAA Interface for attestation attributes: EUDIW requests EAAs from EAASP (qualified/non‑qualified) (Q)EAA Provider • ARF (3.6, 3.8, Annex 2 Topic 10 (C), Topic 12) [i.4]; • CIR 2024/2977 [i.5]; • ISO 18013‑5 [i.19]; • SD‑JWT VC [i.22]; • W3C VCDM (for EAA) [i.37]; • W3C Digital Credentials API [i.36]; • OpenID4VCI [i.25]. Request & Receive PuB‑EAA Similar to above, but for public-sector-issued EAAs from authentic sources (PUB‑EAA Providers) Public‑body EAASP • ARF (3.7, 3.10, Annex 2 Topic 10, Topic 12) [i.4]; • CIR 2024/2977 [i.5]; • CIR 2024/2982 [i.8]; • ISO 18013‑5 [i.19]; • SD‑JWT VC [i.22]; • W3C VCDM (for EAA) [i.37]; • W3C Digital Credentials API [i.36]; • OpenID4VCI [i.25]. Signature/Seal Creation Request Interface for invoking Qualified Signature Creation via WSCD or remote QSCD operated by a SCSP Qualified SCSP/QTSP • ARF (3.9, Annex 2 Topic 16) [i.4]; • CSC API [i.32]; • ETSI EN 319 142-1 (PAdES) [i.29]; • ETSI EN 319 132-1 (XAdES) [i.27]; • ETSI TS 119 182-1 (JAdES) [i.30]; • ETSI EN 319 122-1 (CAdES) [i.28]; • ETSI EN 319 162-1/-2 (ASiC) [i.31] [i.38]; • ETSI TS 119 101 [i.39]; • EN 419 241-1 [i.18]; • ETSI TS 119 431‑1 [i.12]; • ETSI TS 119 431‑2 [i.13]. Relying Party Authentication & Consent EUDIW authenticates relying party, displays request, collects user consent Relying Party (Service Provider) • ARF (6.6.3.2, 6.6.3.3, 6.6.3.5, Annex 2 Topic 6) [i.4]; • ISO 18013‑5 [i.19]; • OpenID4VP [i.26]. Revocation and Validity Checking Check and update status of issued PIDs or EAAs via revocation or validation services Revocation/Validation Services • ARF (6.6.3.7, Annex 2 Topic 7) [i.4]; • ETSI EN 319 411-1 [i.11]; • ETSI EN 319 411-2 [i.17]. The ARF [i.4] also defines the following interfaces: Wallet Provider Interface, User Interface, Secure Cryptographic Interface, and the WSCA-to-WSCD interface. The present document does not provide specifications for those interfaces. ETSI ETSI TR 119 462 V1.1.1 (2026-03) 15 |
1e77440904685da89cefd2bd994bd735 | 119 462 | 4.3 Wallet interfaces for trust services | TSPs operating under the eIDAS Regulation [i.1] and its implementing acts are key actors in the European Digital Identity Framework. Their interactions with the EUDIW meet a set of functional, legal, and technical requirements that ensure security, user control, privacy, and cross-border interoperability. These apply to: • Electronic Attestation of Attribute Providers (EAASPs), including Qualified EAASPs and Public Sector EAA issuers (PUB-EAAs), • Certificate Issuers, including Qualified Trust Service Providers (QTSPs) issuing qualified certificates for electronic signatures or seals, • Remote Signature Creation Service Providers (SCSPs), • Registered Electronic Delivery Service Providers (REDS), • and other TSPs interfacing with EUDIW. Table 4: EUDIW TSP interface identified requirements Requirement Description Source or requirement in ARF [i.4] User Identification TSPs reliably identify the EUDIW holder using PID and/or EAA-based identity attributes. 6.6.2 PID or attestation issuance, 6.6.3 PID or attestation presentation to Relying Party, User Consent All issuance, signing, or delivery actions are based on explicit user consent, which is collected and presented through the EUDIW interface. 5.6.2 (transactional data), 6.6.3.5 (Wallet Unit obtains User approval for presenting selected attributes), Annex 2 Topic 6 (B). Interoperable and Secure Interfaces TSPs support standardized interaction protocols (listed in the present document) to enable secure and privacy-respecting exchanges with the EUDIW. Interface endpoints are required to support mutual authentication, selective disclosure, and device binding mechanisms. 4.4.3.4 (profiling OpenID4VP [i.26] in remote flows), 5.6.1 (attestation presentation: ISO/IEC 18013-5 [i.19] & OpenID4VP [i.26]), 5.6.2 (transactional data), 5.3.2-5.3.4 (attestation formats & proofs), Annex 2 Topic 1. Validation of EUDIW and Device Before issuing credentials or initiating services, TSPs verify the integrity and authenticity of the EUDIW through mechanisms such as Wallet Unit Attestation (WUA). Where applicable, attestations and certificates are bound to a Wallet Secure Cryptographic Device (WSCD). 6.6.2.3 (PID Provider or Attestation Provider validates the Wallet Unit), 6.6.2.4 (PID Provider or Attestation Provider verifies that WUA is not revoked), Annex 2 Topic 9, Annex 2 Topic 10 (ISSU_30). EAA Delivery and Cryptographic Binding EAAs and certificates are delivered securely to the EUDIW, ensuring binding to the user and/or device using cryptographic references. Transactional services ensure that delivery metadata, timestamps, and integrity proofs are traceable and bound to verified identities. 6.6.2.3.3 Verifies that PID key or device-bound attestation key is protected by the WSCD, 5.6.2 (transactional data), 6.6.2.6 (User activates the PID). Revocation and Status Management TSPs provide real-time or asynchronous mechanisms for revocation, suspension, or status verification of issued EAAs and certificates. EUDIW queries these services securely and reliably. 6.6.5.4 PID or Attestation Revocation, Annex 2 Topic 7 - Attestation revocation and revocation checking. ETSI ETSI TR 119 462 V1.1.1 (2026-03) 16 Requirement Description Source or requirement in ARF [i.4] Audit, Logging, and Notifications Interactions with the EUDIW are logged and made auditable. Where applicable, TSPs report events (e.g. issuance, revocation, breaches) to authorities or registries in accordance with CIR 2024/2980 and 2025/848. 6.6.3.13 (Wallet Unit enables the User to report suspicious requests by a Relying Party and to request a Relying Party to erase personal data); Annex 2 Topic 19, CIR 2024/2979 [i.6] Art. 9 (transaction logs by wallet instances); Notifications framework in CIR 2024/2980 (ecosystem notifications) [i.7]. Trust Framework Participation TSPs are listed in national or European-level trust lists. 3.5 (Trusted List Provider), 6.3.2.2-6.3.2.4 (access & registration certificates; trusted lists); 6.4.2-6.4.3 (RP registration/suspension); Annex 2 Topic 31. Table 5 provides an overview of the primary interfaces defined for interaction between the EUDIW and different types of TSPs. These include providers of EAAs, certificates, remote signature creation, and other services supporting qualified trust operations under the eIDAS [i.1] framework. The listed interfaces were identified through analysis of the EUDIW interface model described in the ARF [i.4], the eIDAS [i.1] Regulation and its Implementing Acts, and relevant ETSI standards. Each interface reflects a functional connection point necessary for compliant service delivery, secure user interaction, and support for digital transactions involving identity or signature services. Table 5. Interfaces for interaction between the EUDIW and TSPs Identifier Name Description References in the present document Reference to standards supporting interface IN_RP_1 Online authentication interface Interface for TSP acting as RP to request and receive Personal Identification Data (PID) and EAA in the process of identity validation or request for specific attributes. Clause 5.2 ETSI TS 119 461 [i.40], ETSI TS 119 472-1 [i.41], ETSI TS 119 472-2 [i.42]. IN_RP_2 Interface for request for signature Interface for RP to initialize the signing process. Primarily allows RP to receive information about online SCA and authentication information. Clause 5.3 ETSI TS 119 472-1 [i.41], ETSI TS 119 472-2 [i.42], ETSI TS 119 432 [i.15], ETSI EN 319 102-1 [i.16] Including Transaction Data Authorization IN_TSP_1 New attributes EAA handover interface Interface for TSP issuing EAA in the process of EAA handover. Clause 6.4 ETSI TS 119 472-3 [i.43]. IN_TSP_2 Interface for remote signature creation Interface enabling the creation of the electronic signature with the EUDIW when signature is created by a remote signature service. Clause 7.4 ETSI EN 319 102-1 [i.16], ETSI TS 119 431-2 [i.13], ETSI TS 119 432 [i.15]. ETSI ETSI TR 119 462 V1.1.1 (2026-03) 17 Identifier Name Description References in the present document Reference to standards supporting interface IN_TSP_3 Interface for new certificate handover Interface for handover of the signature certificate. Registration and identity proofing of the certificate subject may use the IN_RP_1 interface. Clause 7.5 ETSI TS 119 432 [i.15]. IN_QSCD_LOCAL Interface for local signature creation Interface enabling the creation of the electronic signature with the EUDIW when keys are stored on the local QSCD. Clause 7.4 OUT OF SCOPE IN_SCA Interface for handling signature creation process Interface enabling functionality of providing signing attributes and a certificate to the Signature Creation Application. Clause 7.3 ETSI EN 319 102-1 [i.16]. |
1e77440904685da89cefd2bd994bd735 | 119 462 | 4.4 Wallet interfaces for signature creation | The present clause describes the use of the EUDIW to support the creation of Qualified Electronic Signatures (QES) and Qualified Electronic Seals (QSeals). Signature creation can be performed using either: • a local Qualified Signature Creation Device (QSCD) integrated into the EUDIW environment; or • a remote QSCD operated by a Qualified Trust Service Provider (QTSP). The EUDIW interface enables users to securely initiate and authorize the creation of digital signatures, in compliance with eIDAS and ETSI standards. It provides consistent interaction mechanisms with the Signature Creation Application (SCA), whether it is embedded in the EUDIW or hosted externally. EUDIW providers are expected to: • support secure and privacy-preserving user authentication to signature services.; • ensure that a qualified certificate bound to a QSCD is obtained and linked to the user; • enable SCA to sign any data provided by the user; • support signature format PAdES [i.29]; • optional support signature formats XadES [i.27], CAdES [i.28], JAdES [i.30], and ASiC [i.31]. Signature initiation involves user awareness and consent. The EUDIW allows users to preview signing context (e.g. document hash, transaction metadata), approve the action, and receive confirmation of signature creation. It is also required to support signature history tracking and transparency features to enable users' control. Multiple models of signature integration are supported: • full integration of SCA within the EUDIW; • redirection to an external remote SCA operated by a QTSP; • use of the EUDIW as SIC in the process of SAD generation following SCAL2 requirements from EN 419 241 [i.18], clause 5.10; • use of the EUDIW as an authentication component following SCAL2 requirements from EN 419 241 [i.18], clause 5.10. The present document takes into account the following standards specifying Signature Creation interface requirements: ETSI TS 119 431-1 [i.12], ETSI TS 119 431-2 [i.13], ETSI TS 119 432 [i.15], ETSI EN 319 102-1 [i.16], ETSI EN 319 411-1 [i.11], ETSI EN 319 411-2 [i.17], CSC API V2.2 [i.32]. ETSI ETSI TR 119 462 V1.1.1 (2026-03) 18 |
1e77440904685da89cefd2bd994bd735 | 119 462 | 5 Interface for authentication and identification | |
1e77440904685da89cefd2bd994bd735 | 119 462 | 5.1 Identity proofing | When issuing a Qualified Certificate or a Qualified Electronic Attestation of Attributes for a trust service, a Qualified Trust Service Provider verifies the identity and, if applicable, any specific attributes of the natural or legal person to whom the qualified certificate or the qualified electronic attestation of the attribute is issued. Supporting standards: Standard Description ETSI TS 119 461 [i.40]. Requirements for TSPs for the identity proofing process ETSI TS 119 472-1 [i.41]. EAA Profile |
1e77440904685da89cefd2bd994bd735 | 119 462 | 5.2 Interface for online identification and authentication | The interface for online identification and authentication enables requests and receives Personal Identification Data (PID) and Electronic Attestation of Attributes (EAA) during the identity validation process or when requesting specific attributes. The interface enables a Relying Party (RP) - which may also be a Trust Service Provider (TSP) - to request and receive PID, and/or EAAs from the EUDIW, for identity validation, attribute-based access control, or service provisioning. This interface supports online interactions, where the RP actively engages the EUDIW user in a data presentation session and receives a structured response. According to the ARF [i.4], this interface is governed by the Presentation Phase, especially in: Section 6.6.3: PID or attestation presentation to Relying Party, Annex 2 - Topic 1: Accessing Online Services with a Wallet Unit (OIA_04- OIA_07), Annex 2 - Topic 6: High-Level Requirements for Relying Party Authentication and Attribute Requests (Req. RPA_01-RPA_07, RPA_09-RPA_11): defining how the request is structured, secured, and consented. The core pattern includes: • Request: The RP sends an authenticated presentation request to the EUDIW. • Authentication: The EUDIW authenticates the RP Instance, ensuring the User is correctly informed about the Relying Party's identity. • Consent: The EUDIW displays the request to the user, including the purpose, legal basis, data categories, and RP identity. • Presentation: Upon user approval, the EUDIW prepares and returns the requested PID or attributes, respecting selective disclosure rules. ARF [i.4] specifies OpenID4VP [i.26] as the preferred protocol for implementing this interface: • Based on OAuth 2.0 Authorization Framework RFC 6749 [i.44] • Adapted to support Verifiable Credentials (SD-JWT VC [i.22], ISO mDL [i.19]) • Enabling secure binding between the RP, the data request, and the resulting presentation. Key Components: • Presentation Request: Structured JSON object signed by the RP or transmitted via URI. • Verifiable Presentation: JWT or SD-JWT VC response containing selectively disclosed claims. • Response Binding: The EUDIW signs the response or uses cryptographic proof to ensure authenticity and user control. ETSI ETSI TR 119 462 V1.1.1 (2026-03) 19 Reference: [i.4] ARF - Annex 2, Topic 1 Accessing Online Services with a Wallet Unit: OIA_03a - OIA_04 specifying the protocols for the presentation interface. Security and Privacy Measures • Mutual Authentication: WRP authenticates itself using a WRP certificate: access and registration (cf. CIR 2025/848 [i.9]). • User Consent: EUDIW is required to always obtain explicit user consent before presenting any data. • Selective Disclosure: The EUDIW supports attribute-level granularity using SD-JWT or mDL containers. • Audit and Logging: All presentations will be logged within the EUDIW for user traceability (CIR 2024/2979 [i.6]). Supporting standards: Standard Description ETSI TS 119 472-1 [i.41] EAA Profile ETSI TS 119 472-2 [i.42] EAA/PID Presentation to relying party OpenID4VP [i.26] EAA/PID Presentation to relying party ETSI TS 119 411-8 [i.35] Relying Party Access Certificates ETSI TS 119 475 [i.34] Relying Party Registration Certificates |
1e77440904685da89cefd2bd994bd735 | 119 462 | 5.3 Interface for request for signature | The interface allows a Relying Party (RP)-typically a service provider requiring a legally binding transaction-to initiate a digital signature request by the user via the EUDIW. This interface is used to transfer the signature request parameters, authenticate the user, and facilitate a secure process redirect to the Signature Creation Application (SCA). This interface does not perform the signature itself but initiates the signature workflow. The interface is functionally dependent on the mechanisms described in clause 5.2: • reuses the OpenID4VP [i.26] based request structure to deliver the transaction context (e.g. document hash, signing intent); • follows the same authentication and consent process, ensuring that the RP is properly identified and authorized; • builds on the secure presentation layer used for PID/EAA. In effect, the interface extends the interface specified in clause 5.2 by adding signature-specific elements, such as: • Signature metadata (e.g. hash to be signed, document ID) • Signature policy references (e.g. AdES type, legal value) • Optional request for qualified signature creation via remote or local QSCD Depending on the deployment model, this interface may also pass the signed metadata to an external SCA (e.g. operated by QTSP), or activate EUDIW's internal SCA module with appropriate binding to the WSCD or remote QSCD. ETSI ETSI TR 119 462 V1.1.1 (2026-03) 20 Supporting standards: Standard Description ETSI TS 119 472-2 [i.42] EAA/PID Presentation to relying party (including transaction data) OpenID4VP [i.26] EAA/PID Presentation to relying party (including transaction data) ETSI TS 119 432 [i.15] Protocols for remote digital signature creation, including delegation to Signature Creation Application (SCA) ETSI EN 319 102-1 [i.16] General requirements for AdES and QES creation, including user intent and consent. CSC API [i.32] Remote signature creation API |
1e77440904685da89cefd2bd994bd735 | 119 462 | 6 Interface for EAA issuance | |
1e77440904685da89cefd2bd994bd735 | 119 462 | 6.1 Interface description | The interface between European Digital Identity Wallets (EUDIW) and Trust Service Providers (TSPs) issuing Electronic Attestations of Attributes (EAAs) relies on the OpenID for Verifiable Credential Issuance (OpenID4VCI) [i.25] protocol profiled for high assurance. In particular, the issuance profile builds on OpenID4VC-HAIP [i.24] and extends it to meet EUDIW ecosystem requirements, including the use of Wallet Unit Attestation (WUA), metadata carried by the Issuer, and binding of issued EAAs to wallet-controlled keys. The interface requires signed Issuer Metadata and supports discovery of credential formats, embedded disclosure policy pointers, reuse policies, and the inclusion of access and registration certificates for the PID/EAA Provider. These elements enable the EUDIW to authenticate the issuer, obtain policy signals, and conduct the issuance flow using either the Authorization Code Flow or the Pre-Authorized Code Flow defined by OpenID4VCI [i.25]. The profile and interface for EAA issuance are specified in the ETSI TS 119 472-3 [i.43]. The formats for EAAs are specified in ETSI TS 119 472-1 [i.41]. Normative building blocks include: • Issuer Metadata (signed JWS) with credential configuration, access certificate chain, and optional registration certificate. • EAA issuance flows and request/response requirements (Credential Offer, Pushed Authorization Request, Token Request, Credential Request/Response, Notification). • Support for EAA formats, including profiles not natively covered by OpenID4VCI [i.25] (e.g. X.509 Attribute Certificate-based EAA). Related trust service and credential requirements are provided in ETSI TS 119 471 (EAASP policy/security) [i.14], ETSI EN 319 411-1 [i.11] and ETSI EN 319 411-2 [i.17] (certification policies), ETSI TS 119 411-8 (Access Certificates) [i.35], ETSI TS 119 475 (Registration Certificates/RP attributes) [i.34], and ISO/IEC 23220-3 (EUDIW issuance phase) [i.21]. |
1e77440904685da89cefd2bd994bd735 | 119 462 | 6.2 Wallet user identification | User identification and any prerequisite enrolment or attribute validation are performed in accordance with clause 5 of the present document. The TSP may leverage attributes previously issued to the user and, where necessary, obtain additional attributes from authoritative sources. If needed for identification or authorization of the holder, the TSP may use presentations via clauses 5.1 and 5.2 of the interface before proceeding with issuance. Supporting standards: Clauses 5.1 and 5.2 provide information about supporting standards. ETSI ETSI TR 119 462 V1.1.1 (2026-03) 21 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.