hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
179c56242535c70e283548bec0bde828 | 103 720 | 12.2.3 Cell categories and service types | Cell categories specified in ETSI TS 136 304 [19] are not applicable to ROM devices as described. Specifically, a suitable cell has the following requirement: "The cell is a part of at least one TA that is not part of the list of 'forbidden tracking areas for roaming' ETSI TS 123 401 [i.4], which belongs to a PLMN that... |
179c56242535c70e283548bec0bde828 | 103 720 | 12.2.4 Out-of-coverage and out-of-service indication | 3GPP specifications provide standardized mechanisms for the UE for: - monitoring and maintaining the radio link quality ETSI TS 136 133 [15]; and - selecting a PLMN, including indications to the upper layers when no PLMN is available ETSI TS 123 122 [4]. ROM devices cannot implement these mechanisms. The Access Stratum... |
179c56242535c70e283548bec0bde828 | 103 720 | 12.2.5 Sleep mechanism | Conventional UEs employ sleep mechanisms in idle mode by selectively shutting off radio receiver and/or transmitter components in order to extend battery life. The sleep mechanism of the traditional UE is not applicable to ROM device because: - The DRX cycle-based sleep mechanism ETSI TS 136 304 [19] in the Access Stra... |
179c56242535c70e283548bec0bde828 | 103 720 | 12.3 MBMS Client | Implementation guidelines for MBMS Clients are provided in ETSI TS 126 347 [9], clause 6.4. The MBMS Client handles the out-of-service and out-of-coverage indications from the Access Stratum. The action of the MBMS Client upon receiving the indication is implementation-specific (e.g. inform the application, suspend/ de... |
179c56242535c70e283548bec0bde828 | 103 720 | 12.4 MBMS-Aware Application | This aspect is for further study. |
179c56242535c70e283548bec0bde828 | 103 720 | 12.5 LTE-based 5G Broadcast Emergency Alerts Receiver | Based on the architecture in figure 5.15.1-1, the receiver functions for public warning systems and emergency alerts may be implemented independently of the 5G Broadcast Receiver functions. This is shown in figure 12.5-1 below. While such a receiver is not in the primary scope of the present document, it may be a valid... |
179c56242535c70e283548bec0bde828 | 103 720 | 12.6 Public Warning System message handling | Details of handling URLs in emergency alerts and public warning messages are for further study. ETSI ETSI TS 103 720 V1.2.1 (2023-06) 61 Annex A (informative): Change History Date Version Information about changes 2020-01-07 0.0.1 Initial Draft 2020-09-11 0.0.2 Updates from initial review 2020-09-17 0.1.0 Improved draf... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 1 Scope | The present document specifies external encodings for AES. The external encodings specified in the present document can also be applied to other block ciphers; in particular, they can be applied to any block cipher with a block size of either 64 or 128 bits. The present document does not define clear-box transformation... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 2 References | |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 2.1 Normative 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. Referenced documents which a... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 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 i... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 3 Definition of terms, symbols and abbreviations | |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 3.1 Terms | For the purposes of the present document, the following terms apply: bit: binary digit having a value of zero or one block cipher: function that maps a plaintext to a ciphertext using a cipher key cipher key: secret cryptographic key, used as input to a block cipher ciphertext: sequence of bits that is the output of a ... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: ⊕ Addition of two bits, addition of two vectors. ˑ Multiplication of two bits, multiplication of a bit with a vector, multiplication of a vector with a matrix, multiplication of two matrices. || Concatenation of two vectors. |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AES Advanced Encryption Standard DCA Differential Computation Analysis DFA Differential Fault Analysis RNG Random Number Generator ETSI ETSI TS 103 718 V1.1.1 (2020-10) 7 |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 4 Preliminaries | |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 4.1 Basic mathematical concepts | |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 4.1.1 Bits, vectors, and matrices | The addition of two bits is defined as: 0 ⊕ 0 = 0, 0 ⊕ 1 = 1, 1 ⊕ 0 = 1, and 1 ⊕ 1 = 0. The multiplication of two bits is defined as: 0 ˑ 0 = 0, 0 ˑ 1 = 0, 1 ˑ 0 = 0, and 1 ˑ 1 = 1. An m-bit vector is a sequence of m bits. EXAMPLE 1: (1, 0, 1, 1) is a 4-bit vector. The bits of an m-bit vector are numbered 1 to m from l... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 4.1.2 Concatenation, addition, and linear combination of vectors | The concatenation of the m-bit vector (a1, a2, …, am) and the k-bit vector (b1, b2, …, bk) is defined as: (a1, a2, …, am) || (b1, b2, …, bk) = (a1, a2, …, am, b1, b2, …, bk). EXAMPLE 1: The concatenation of the 3-bit vector (0, 1, 0) and the 4-bit vector (1, 1, 1, 1) is a 7-bit vector and equals (0, 1, 0, 1, 1, 1, 1). ... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 4.1.3 Vector - matrix and matrix - matrix multiplication | If X = (x1, x2, …, xm) is an m-bit vector and if the entries of the m × m matrix A are denoted as ai,j with 1 ≤ i, j ≤ m (see also clause 4.1.1), then the product of X and A is defined as: XˑA = x1ˑ(a1,1, a1,2, …, a1,m) ⊕ x2ˑ(a2,1, a2,2, …, a2,m) ⊕ … ⊕ xmˑ(am,1, am,2, …, am,m). EXAMPLE 1: 1 1 1 0 1 0 1 0 0 (1, 1, 0) ˑ ... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 4.2 Block ciphers | A block cipher is an encryption function EK that maps an n-bit plaintext to an n-bit ciphertext. The parameter n is referred to as the block size, and in the present document, its value is either 64 or 128 (in the case of AES, n = 128). A plaintext and a ciphertext are denoted by P and C respectively. The encryption fu... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 4.3 External encodings | In the present document an external encoding is a function that maps an n-bit input vector to an n-bit output vector. There are two types of external encoding: 1) The first type is referred to as an input encoding and is denoted by FK1; 2) The second type is referred to as an output encoding and is denoted by GK2. Both... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 5 External encodings specification | |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 5.1 Basic functions | The external encodings specified in the present document use two types of function. The first type of function maps an 8-bit input vector to an 8-bit output vector. The function is parameterized by the external encoding key K' (which is either K1 or K2, depending on the type of external encoding) and the function is in... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 5.2 Input encoding | If the n bits of the vector X input to the input encoding FK1 are denoted by xi for i = 1, 2, …, n, and if the 8-bit vector Xj is defined as Xj = (x8j-7, x8j-6, x8j-5, x8j-4, x8j-3, x8j-2, x8j-1, x8j) for j = 1, 2, …, n/8, then FK1 shall be as follows: FK1 (X) = HK1 (TK1(1) (X1) || TK1(2) (X2) || … || TK1(n/8) (Xn/8)) ... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 5.3 Output encoding | Let X denote the n-bit input vector of the output encoding GK2 and define the n-bit vector Z as Z = HK2 (X) = XˑAK2 ⊕ bK2. If the n bits of Z are denoted by zi for i = 1, 2, …, n, and if the 8-bit vector Zj is defined as Zj = (z8j-7, z8j-6, z8j-5, z8j-4, z8j-3, z8j-2, z8j-1, z8j) for j = 1, 2, …, n/8, then GK2 shall be... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 5.4 Key sizes | It is assumed that each function TK'(i) with 1 ≤ i ≤ n/8 is represented by a look-up table and that HK' is represented by an n × n invertible matrix AK' and an n-bit vector bK' (see clause 5.1). The external encoding key K' is defined by the contents of these look-up tables, the contents of AK', and the contents of bK'... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 6 Life cycle of an external encoding key | |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 6.1 Example system | Clear-box implementation generator External encoding key generator RNG 3 RNG 2 Clear-box execution environment Non-clear-box execution environment Obfuscated implementation of the block cipher with external encodings Input and/or output encoding key Obfuscated cipher key RNG 1 Cipher key Cipher key Cipher key Input and... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 6.2 Key generation and key distribution | The key generation stage shown in Figure 5 uses RNG 1 to generate cipher keys, and it uses RNG 2 and an external encoding key generator to generate external encoding keys. • The confidentiality of an external encoding key shall be protected during its generation. EXAMPLE 1: Physical security measures, for instance offe... |
95394400b62d39c6ce9bc8338b2355e7 | 103 718 | 6.3 Key storage and key use | The obfuscated implementation of the block cipher, including the obfuscated external encoding keys, is stored and used in the clear-box environment. In addition, in the example system shown in Figure 5, the input and/or output encoding keys are stored and used in the non-clear-box execution environment. • The confident... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 1 Scope | The present document defines Interoperability Test Descriptions for the NG eCall High Level Application Protocol (HLAP). |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 2 References | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 2.1 Normative 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. Referenced documents which a... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 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 i... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 3 Definition of terms, symbols and abbreviations | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 3.1 Terms | For the purposes of the present document, the following terms apply: base specification: specification of a protocol, telecommunication service, interface, abstract syntax, encoding rules, or information object eCall: manually or automatically initiated emergency call, from a vehicle, supplemented with a Minimum Set of... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 3.2 Symbols | Void. |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP Third Generation Partnership Project ACK ACKnowledgement CEN Comité Européen de Normalisation CFG ConFiGuration CS Circuit Switched CSCF Call Session Control Function ECL eCall Over IMS support E-CSCF Emergency CSCF EMS IMS Emergency Serv... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 4 Conventions | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 4.1 Interoperability test process | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 4.1.1 Principles | The goal of interoperability tests is to check that devices resulting from protocol implementations are able to work together and provide the functionalities provided by the protocols. As necessary, one message may be checked during a test, for instance, when a successful functional verification may result from an inco... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 4.1.2 The test description proforma | The test descriptions are provided in proforma tables following the format described in ETSI EG 202 798 [i.3] and ETSI ETR 266 [i.1]. The following different test event types are considered during the test execution: • A stimulus corresponds to an event that enforces an EUT to proceed with a specific protocol action, l... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 4.1.3 Interoperable Functions Statement | The "Interoperable Functions Statement" (IFS) identifies the standardized functions of an EUT. These functions can be mandatory, optional or conditional (depending on other functions), and depend on the role played by the EUT. The IFS can also be used as a pro-forma by a vendor to identify the functions that its EUT wi... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 4.2 Tooling | Message monitoring solutions, including audio recording and event logging, where supported, may be used to facilitate the resolution of any interoperability and/or performance issues that may be encountered during interoperability testing. |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 4.3 Test Description naming convention | Table 1: TD naming convention TD_<root>_[gr]_<nn> <root> = root applicability BAS Basic test ADV Advanced test [gr] = group IVS IVS eCall terminal PSAP PSAP eCall server IVS or PSAP <nn> = sequential number 01 to 99 Sequential numbers |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 4.4 Test Summary | The detailed test descriptions are defined in clause 7. It is recommended to conduct all test cases supported by PSAP and IVS. Some of the test cases require a fallback to CS (legacy) eCall. The interoperability test cases for CS domain are specified in ETSI TS 103 428 [9]. The test scenarios of the present document ar... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 4.5 Overview of Related IVS Tests | Table 7 provides an overview of related IVS tests. The tests on the left verify the IVS behaviour in case of a hybrid network environment (including the CS and PS domain) based on the current ETSI requirements, while the tests on the right side verify the IVS behaviour in case of a PS-only environment based on the upda... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 5 Test Bed Architecture | 5.1 Test site layout The generic test bed used to carry out interoperability tests, is summarized in the below Figure 1. ETSI ETSI TS 103 683 V2.1.1 (2023-02) 14 Figure 1: Architecture In normal operation conditions, the NG IVS establishes an NG eCall via the correct URN. This call setting is then interpreted by the mo... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 6 Test Configurations | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 6.0 Introduction | The following clauses define multiple test configurations, which reflect the cases A and D from Table H.2 in ETSI TS 123 167 [2]. |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 6.1 Home Interoperability Test Configuration | Interoperability tests will be performed using the setup shown in Figure 5. The HPLMN shall indicate support of Voice over IMS (VoIMS), IMS Emergency Services (EMS) and eCall Over IMS (ECL). Ancillary measurement and message logging devices are not shown but may be used, with the agreement of the participants, to help ... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 6.3 Visited Interoperability Test Configuration | This configuration is used to represent a roaming scenario. Interoperability tests will be performed using the setup shown in Figure 7. Ancillary measurement and message logging devices are not shown but may be used, with the agreement of the participants, to help identify the likely cause of any interoperability test ... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 6.4 Multiple IVS Interoperability Test Configuration | In the Interoperability test configuration NG_eCall_CFG_04, more than one NG IVS will repetitively call the same NG PSAP to simulate a real service, as shown in Figure 8. The NG PSAP shall be able to handle a certain number of parallel emergency calls and route them to a certain number of operator phones. Figure 8: NG_... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 6.7 Home Interoperability Test Configuration with ESInet | Interoperability tests will be performed using the setup shown in Figure 11. The HPLMN shall indicate support of Voice over IMS (VoIMS), IMS Emergency Services (EMS) and eCall Over IMS (ECL). Ancillary measurement and message logging devices are not shown but may be used, with the agreement of the participants, to help... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 6.8 Visited Interoperability Test Configuration with ESInet | This configuration is used to represent a roaming scenario. Interoperability tests will be performed using the setup shown in Figure 12. Ancillary measurement and message logging devices are not shown but may be used, with the agreement of the participants, to help identify the likely cause of any interoperability test... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 6.9 Home Interoperability Test Configuration with TPSP | Interoperability tests will be performed using the setup shown in Figure 9. Ancillary measurement and message logging devices are not shown but may be used, with the agreement of the participants, to help identify the likely cause of any interoperability test failures that may arise. Audio interface HMI NG PSAP HPLMN (... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 6.10 Default pre-test conditions | The following default pre-test conditions apply to all tests unless otherwise stated in the test cases description: 1) Ignition is ON, and NG IVS is in mobile network coverage 2) NG MNO and NG PSAP test points are available 3) NG IVS registered to the PLMN (HPLMN or VPLMN) 4) NG IVS has all the information needed to co... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 6.11 Interoperable Functions Statement (IFS) | All IFS items referred to in this clause are specified in TS 17184:2022 [4] unless indicated otherwise by another numbered reference. Table 9: PSAP features Item Entity IFS_ID Reference Status Support 1 PSAP supports IMS-eCall PSAP_ims_eCall 7.1.3 m 2 PSAP supports legacy CS in-band eCall PSAP_legacy_eCall prEN 17905:2... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7 NG eCall test scenarios/descriptions | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.0 Introduction | The tests defined in the present document shall be performed according to the test applicability. The test applicability is defined in each test in the 'Applicability' field and is expressed with IFS statements. The tests apply to IVS and PSAP as well as to IVS and PSAP simulators. Following test descriptions are cover... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1 Basic test scenarios | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.1 Initiation of manual eCall | Interoperability Test Description Identifier: TD_BAS_01 Objective: Verify that the IVS is able to initiate a manual eCall containing an INVITE request indicating service URN value. Verify that the received MSD contains the correct eCall initiation indicator for a manually triggered eCall. Configuration: NG_eCall_CFG_01... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.2 Initiation of automatic eCall | Interoperability Test Description Identifier: TD_BAS_02 Objective: Verify that the IVS is able to initiate an automatic eCall containing an INVITE request indicating service URN value. Verify that the received MSD contains the eCall initiation indicator for an automatic triggered eCall. Configuration: NG_eCall_CFG_01 o... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.3 Initiation of test eCall | Interoperability Test Description Identifier: TD_BAS_03 Objective: Verify that the IVS is able to initiate a test eCall containing INVITE request indicating service URN value "urn:service:test.sos.ecall". Verify that the received MSD contains the correct test eCall indicator for a test eCall (see note). Configuration: ... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.4 MSD transfer to PSAP supporting IMS eCall | Interoperability Test Description Identifier: TD_BAS_04 Objective: Verify that the IVS is able to transfer the MSD (in an INVITE request) to a PSAP supporting IMS eCall. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clause 7.5 of TS 17184:2022 [4] Applicability: IVS_ims_eCall AND PSAP_ims_eCall Pre-test... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.5 MSD transfer to PSAP supporting IMS eCall in a roaming scenario | Interoperability Test Description Identifier: TD_BAS_05 Objective: Verify that the IVS is able to transfer the MSD (in an INVITE request) to a PSAP supporting IMS eCall in a roaming scenario. Configuration: NG_eCall_CFG_03 or NG_eCall_CFG_08 References: Clauses 7.4.3.2 and 7.5 of TS 17184:2022 [4] Applicability: IVS_im... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.6 PSAP initiated callback to IVS | Interoperability Test Description Identifier: TD_BAS_06 Objective: Verify that if an eCall has been successfully terminated by the PSAP, then the IVS shall answer a PSAP callback. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clauses 7.7.3 and 7.11 of TS 17184:2022 [4] Clause 7.17.3 of EN 16072:2022 [7]... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.7 PSAP initiated call clear-down | Interoperability Test Description Identifier: TD_BAS_07 Objective: Verify that when the PSAP clears down the call, the IVS also clears down the call following receipt of a BYE request. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clause 7.10 of TS 17184:2022 [4] Applicability: IVS_ims_eCall AND PSAP_im... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.8 IVS initiated call clear-down not allowed | Interoperability Test Description Identifier: TD_BAS_08 Objective: Verify that when the eCall was established an IVS initiated call clear-down is not allowed before expiry of timer T2. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clause 7.4.7 and Annex A of TS 17184:2022 [4] Clauses 7.10.3 and 7.11 of ... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.9 Verification of audio interfaces of IVS and PSAP | Interoperability Test Description Identifier: TD_BAS_09 Objective: Verify that the PSAP sends an acknowledgement (in the final response to the INVITE), if MSD check is successful. Verify that the IVS and PSAP audio interfaces are connected and 2-way speech is possible between the IVS and PSAP. Configuration: NG_eCall_C... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.10 MSD update on request from PSAP | Interoperability Test Description Identifier: TD_BAS_10 Objective: Verify that the IVS is able to recognize and act upon a request from the PSAP, during ongoing eCall, to send an updated MSD. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clause 7.7.2 of TS 17184:2022 [4] Applicability: IVS_ims_eCall AND... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.11 Void | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.12 Void | 7.1.13 Format of encoded and decoded MSD in accordance with EN 15722:2015 Interoperability Test Description Identifier: TD_BAS_13 Objective: Verify that the IVS formats the MSD in accordance with EN 15722:2015 [10] and encodes it correctly, and that the PSAP decodes and displays the MSD correctly. Configuration: NG_eCa... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.14 Void | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.1.15 Negative acknowledgement for the initial MSD | Interoperability Test Description Identifier: TD_BAS_15 Objective: Verify that the IVS does no attempt to re-send the MSD after it received a negative acknowledgement for the initial MSD. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clause 7.6.3 of TS 17184:2022 [4] Applicability: IVS_ims_eCall AND PSA... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.2 Advanced test scenarios | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.2.1 MSD transfer to PSAP supporting IMS eCall over IPv4 | Interoperability Test Description Identifier: TD_ADV_01 Objective: Verify that the IVS is able to transfer the MSD (in an INVITE request) to a PSAP supporting IMS eCall, if IVS and PSAP are connected over IPv4. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clauses 7.1.2 and 7.1.3 of TS 17184:2022 [4] Ap... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.2.2 MSD transfer to PSAP supporting IMS eCall over IPv6 | Interoperability Test Description Identifier: TD_ADV_02 Objective: Verify that the IVS is able to transfer the MSD (in an INVITE request) to a PSAP supporting IMS eCall, if IVS and PSAP are connected over IPv6. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clauses 7.1.2 and 7.1.3 of TS 17184:2022 [4] Ap... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.2.3 Void | ETSI ETSI TS 103 683 V2.1.1 (2023-02) 32 |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.2.4 MSD transfer to PSAP not supporting IMS eCall | Interoperability Test Description Identifier: TD_ADV_04 Objective: Verify that the IVS is able to transfer the MSD via in-band modem to a PSAP not supporting IMS eCall. Configuration: NG_eCall_CFG_02 References: Clause 7.8 of TS 17184:2022 [4] Clause 7.5.3 of prEN 17905:2022 [13] Clause 5.1.6.11.2 (2nd numbered list/it... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.2.5 IMS eCall establishment with IMS emergency registration | Interoperability Test Description Identifier: TD_ADV_05 Objective: Verify that the IVS is able to initiate an IMS emergency session with IMS emergency registration. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clause 7.4.4 of TS 17184:2022 [4] Clause 7.2 of ETSI TS 123 167 [2] Clause 5.2.2.3 of ETSI TS... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.2.6 IMS eCall establishment without IMS emergency registration | Interoperability Test Description Identifier: TD_ADV_06 Objective: Verify that the IVS is able to initiate an IMS emergency session without IMS emergency registration and includes the "anonymous user" indication in the emergency session establishment if GIBA is not supported. Configuration: NG_eCall_CFG_01 or NG_eCall_... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.2.11 MSD update during PSAP initiated callback | Interoperability Test Description Identifier: TD_ADV_11 Objective: Verify that the IVS answers a PSAP callback and may send an MSD update on request of the PSAP. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clauses 7.7.3 and 7.11 of TS 17184:2022 [4] Clause 7.17.3 of EN 16072:2022 [7] Applicability: IV... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.3 Advanced IVS test scenarios | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.3.1 Fallback to legacy eCall following busy during call setup | Interoperability Test Description Identifier: TD_ADV_IVS_01 Objective: Verify that the IVS is able to fallback to legacy eCall after the IVS receives a 486 (Busy Here), 600 (Busy Everywhere) or 603 (Decline) response with a positive acknowledgement for the MSD to the INVITE request. Configuration: NG_eCall_CFG_02 Refer... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.3.3 Fallback to legacy eCall following no-answer during call setup | Interoperability Test Description Identifier: TD_ADV_IVS_03 Objective: Verify that the IVS is able to fallback to legacy eCall, if there is no-answer (e.g. 200 OK INVITE response) from the PSAP except optional 100 (Trying) or 180 (Ringing). Configuration: NG_eCall_CFG_02 References: Clauses 7.4.5 and 7.13.3.3 of TS 171... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.3.4 Dropped eCall after MSD has been acknowledged | Interoperability Test Description Identifier: TD_ADV_IVS_04 Objective: Verify that the IVS does not attempt to establish a new eCall, if the IMS eCall dropped after the eCall has been successfully established and the MSD has been acknowledged. Verify that the IVS answers a PSAP callback. Configuration: NG_eCall_CFG_01 ... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.3.5 Dropped eCall before call has been established - reattempt to CS | Interoperability Test Description Identifier: TD_ADV_IVS_05 Objective: Verify that the IVS attempts a new eCall in CS domain, if the IMS eCall dropped before the call has been established. Configuration: NG_eCall_CFG_02 References: Clauses 7.4.5, 7.4.8 and 7.13.4.1 of TS 17184:2022 [4] Clause 7.4.4.4.3 of prEN 17905:20... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.3.6 IVS configured for 'eCall only' service (restricted) | Interoperability Test Description Identifier: TD_ADV_IVS_06 Objective: Verify that the IVS does not attempt network registration until an eCall is initiated, if configured for 'eCall only' service. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clauses 7.1.4 and 7.2.2 of TS 17184:2022 [4] Clause 10.7 of ... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.3.9 Termination of manually triggered eCall by vehicle occupant | Interoperability Test Description Identifier: TD_ADV_IVS_09 Objective: Verify that the vehicle occupant is able to abort a manually triggered eCall before expiry of timer T1. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clause 7.4.7 and Table A.1 of TS 17184:2022 [4] Clause 7.10.3 of EN 16072:2022 [7] ... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.3.11 Ongoing eCall shall not be disconnected if new trigger is received | Interoperability Test Description Identifier: TD_ADV_IVS_11 Objective: Verify that the IVS does not attempt to establish a new eCall on new trigger during ongoing eCall, if the eCall has been successfully established and the MSD has been acknowledged before. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References:... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.3.12 No fallback to legacy eCall following busy during call setup | Interoperability Test Description Identifier: TD_ADV_IVS_12 Objective: Verify that the IVS remains registered in the mobile network (unless in limited service state) after the IVS receives a 486 (Busy Here), 600 (Busy Everywhere) or 603 (Decline) response with a positive acknowledgement for the MSD to the INVITE reques... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.3.14 Dropped eCall after call has been established - reattempt to PS | Interoperability Test Description Identifier: TD_ADV_IVS_14 Objective: Verify that the IVS attempts a new eCall in PS domain, if the IMS eCall dropped after the eCall has been successfully established and the MSD has not been acknowledged. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clauses 7.4.5, 7.4... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.3.15 Dropped eCall before call has been established - reattempt to PS | Interoperability Test Description Identifier: TD_ADV_IVS_15 Objective: Verify that the IVS attempts a new eCall in PS domain for a period no more than 2 minutes after the initial triggering, if the IMS eCall dropped before the call has been established. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clau... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.3.17 Reattempt of eCall following no-answer during call setup | Interoperability Test Description Identifier: TD_ADV_IVS_17 Objective: Verify that the IVS reattempts the eCall, if there is no-answer (e.g. 200 OK INVITE response) from the PSAP except optional 100 (Trying) or 180 (Ringing). Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clause 7.4.8 of TS 17184:2022 [4... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.4 Advanced PSAP test scenarios | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.4.1 PSAP handling of more than one eCall simultaneously | Interoperability Test Description Identifier: TD_ADV_PSAP_01 Objective: Verify that a PSAP is able to receive and process more than one eCall simultaneously from different IVS devices. Configuration: NG_eCall_CFG_04 References: Clause 7.1 of EN 16072:2022 [7] Applicability: IVS_ims_eCall AND PSAP_ims_eCall AND PSAP_sim... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.4.2 PSAP correct MSD additional data decoding | Interoperability Test Description Identifier: TD_ADV_PSAP_02 Objective: Verify that the PSAP is able to decode optional additional MSD data. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clause 7.7.2 of EN 16072:2022 [7] Clause 5.1.5 of EN 15722:2020 [12] Applicability: IVS_ims_eCall AND PSAP_ims_eCall ... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.4.3 Rerouting to another PSAP/emergency control centre | Interoperability Test Description Identifier: TD_ADV_PSAP_03 Objective: Verify that the PSAP is able to reroute the eCall to another PSAP/emergency control centre, in order to transfer the MSD and establish a voice connection with another PSAP. Configuration: NG_eCall_CFG_05 References: Clause 7.12 of TS 17184:2022 [4]... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.