hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
615998d1ca83294bf09c70d936c0b900 | 103 420 | 8.3.2.1 flag_ec3_extension_type_a | The element flag_ec3_extension_type_a is a flag that, if set to true, indicates the enhanced AC-3 extension as defined in the present document. |
615998d1ca83294bf09c70d936c0b900 | 103 420 | 8.3.2.2 complexity_index_type_a | The element complexity_index_type_a is an unsigned integer that indicates the decoding complexity of the enhanced AC-3 extension defined in the present document. The value of this field shall be equal to the total number of bed objects, ISF objects and dynamic objects indicated by the parameters in the program_assignme... |
5c910b57fa53246963c67d3fdbd03bde | 103 443-1 | 1 Scope | The present document presents the engineering and operational requirements for the application of IPv6 transition technologies as defined by ETSI TS 101 569-1 [1] (IPv6 Transition Requirements) implemented within an integrated broadband cable network end to end across its network domains. The present document is part 1... |
5c910b57fa53246963c67d3fdbd03bde | 103 443-1 | 2 References | |
5c910b57fa53246963c67d3fdbd03bde | 103 443-1 | 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... |
5c910b57fa53246963c67d3fdbd03bde | 103 443-1 | 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... |
5c910b57fa53246963c67d3fdbd03bde | 103 443-1 | 3 Definitions and abbreviations | |
5c910b57fa53246963c67d3fdbd03bde | 103 443-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: 4in6: encapsulation of IPv4 packets within IPv6 packet format NAT44: network address translation from an IPv4 address to another IPv4 address P Router: label switching router acting as a transit router in the core network of an MPLS ne... |
5c910b57fa53246963c67d3fdbd03bde | 103 443-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 6RD IPv6 Rapid Deployment AFTR Address Family Transition Router BR Border Relay CIDR Classless Inter-Domain Routing CLAT Customer-side transLATor CM Cable Modem CMTS Cable Modem Termination System CPE Customer Premise Equipment DHCP Dynamic Ho... |
5c910b57fa53246963c67d3fdbd03bde | 103 443-1 | 4 General Considerations | It should be noted that Cable broadband access networks may vary in build and design with some network characteristics that may be vendor equipment specific. Consequently there may be aspects to the engineering and operation of the IPv6 transition technology that are dependent on the network build and vendor specific e... |
5c910b57fa53246963c67d3fdbd03bde | 103 443-1 | 5 IPv6 Transition Technologies Overview | Cable network operators are having to adopt IPv6 as the IPv4 addresses become depleted in all registries in order to maintain continuity of services. However, cable operators have extensive investment in the build of their cable networks and consequently need to consider the integration of IPv6 in a pragmatic way withi... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 1 Scope | The present document specifies the Pan-European eCall end to end and in-band modem conformance testing. This is a complete test specification. The following information can be found in the present document: • the overall test structure; • the test configurations; • the conformance requirement and reference to the core ... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 2 References | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 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... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 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... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 3 Definition of terms, symbols and abbreviations | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 3.1 Terms | Void. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 3.2 Symbols | Void. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK ACKnowledgement AL Application Layer AL-ACK Application Layer - ACKnowledgement AMR-NB Adaptive Multirate codec - Narrow Band AMR-WB Adaptive Multirate codec - Wide Band AT ATtention CAN Controller Area Network CCFT Call Cleardown Fallback... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 4 Glossary | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 4.1 Intention of the glossary | For eCall there exists several specifications that use different wording. The main intention of the glossary is to provide background information on the formulations used in the present document, especially in figures 5.2.3-1 to 5.2.3-3, and to prevent ambiguities. The expressions are used throughout the whole document... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 4.2 General | PE eCall capable IVS PE eCall capable IVS are devices that comprise commercial UE functionality as well as eCall service. PE eCall only IVS PE eCall only IVS support only eCall service. PE eCall IVS The expression PE eCall IVS comprises both kind of devices: PE eCall capable IVS and PE eCall only IVS. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 4.3 States | IGNITION OFF The vehicle ignition is switched off, i.e. the vehicle battery does not supply the IVS module with power. The IVS module is unpowered. Self-test The self-test is ongoing within the IVS. IGNITION ON eCall INACTIVE/IDLE, registered This is the normal state of the IVS during vehicle operation when no eCall ha... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 4.4 Decisions | eCall only? Y: The DUT is a PE eCall only IVS. N: The DUT is a PE eCall capable IVS. PSAP PULL-mode? Y: SEND MSD before initiation signal started. N: SEND MSD after initiation signal started. The CEN specifications leave the possibility to the PSAP to send an early SEND MSD. CEN decision to shortcut LL ACK Y: Not a val... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 4.5 Procedures | Network registration The messages exchanged between the IVS and the MNO/PSAP/tester during network registration depend on the Radio Access Technology (RAT) applied. After successful completion of the procedure the device is registered. Call setup Procedure for call establishment on mobile network level. No in-band mode... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 4.6 Tester input/output, internal tester actions/trigger | Vehicle power on The vehicle ignition is turned on. The vehicle power switching is not directly related to the power supply of the PE eCall IVS. Please refer to "Vehicle power off". Self-test indication OK After successful completion of the self-test the PE eCall IVS shall provide an indication to the user which is not... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5 Overview | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.1 Test definition methodology | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.1.1 Derivation of Test Case Descriptions from CEN EN 16454 | Some of the test cases contained in CEN EN 16454 [1] have been implemented in ETSI TS 103 321 [i.1]. The implementation was done in TTCN-3. As a result of this activity it has become evident that the test cases are specified in a way which makes difficult to employ these test cases for certification. On the one hand th... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.1.2 Structure of Test Case Descriptions | The test case descriptions consist of the following parts: • Test Purposes • Conformance Requirement, in any case including a reference to the TC in [1] • Test Description Consisting of: • Pre-Test Description • Test Sequence • Specific message contents |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.1.3 Test Purposes | Defined in the test case section according to [i.3]. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.1.4 Pre-Test Conditions | Defined in the test case section according to [i.3]. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.1.5 Test Sequence | Defined in the test case section according to [i.3]. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.1.6 Final conditions | In order to clean up at the end of test cases, refer to clause 6.3. ETSI ETSI TS 103 412 V1.3.1 (2020-03) 18 |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2 Abstract Test Architecture | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.0 Preface | The entities involved in the testing are to be identified and the messages exchanged between them are to be specified. Different architectures will be needed to deal with the test objects which appear in [1]. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.1 Overview | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.1.1 IVS Testing | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.1.1.1 Test Model IVS | Presently the assumed test model is provided in figure 5.2.1.1.1-1. Figure 5.2.1.1.1-1: IVS Test Model |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.1.1.2 Interface descriptions | Not only the interfaces external to the tester are provided, but also the internal interfaces are modelled here. Distinction between internal and external interfaces is to be discussed. Doing so should allow not to forget anything. Interface IVS - MNO: • Non-transparent messages: having significance for the communicati... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.1.2 PSAP Testing | For further study. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.2 Interface Specifications | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.2.1 IVS Testing | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.2.1.0 Preface | IVS and Tester share 3 interfaces which are handled by different sub-functionalities in the Tester (figure 5.2.1.1.1-1): • IVS and Upper Tester • IVS and MNO • IVS and GNSS Simulator ETSI ETSI TS 103 412 V1.3.1 (2020-03) 20 |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.2.1.1 IVS and Upper Tester | The following MMI commands are used. Table 5.2.2.1.1-1: MMI commands Command Parameters Name Value "CHECK SELF TEST INDICATION OK" (none) "CANCEL ECALL" (none) "CALLBACK IVS" (none) "CHECK_IVS_AUDIO_MUTED" (none) "CHECK_IVS_AUDIO_UNMUTED" (none) "CHECK_ENTERTAINMENT_AUDIO_MUTED" (none) "CHECK_ENTERTAINMENT_AUDIO_UNMUTE... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.2.1.2 IVS and MNO | Two types of messages are transported across this interface: • Signalling messages required to connect the IVS to the network and get the IVS registered. These messages shall be as defined in the specification, ETSI TS 124 008 [11]. • The connection between MNO and PSAP is realized inside the tester. As this interface ... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.2.1.3 IVS and GNSS Simulator | This functionality is optional and not employed for the time being. Therefore the message exchange across this interface is not yet defined. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.2.2 MNO Testing | For further study. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.2.3 PSAP Testing | For further study. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.2.4 TPS-eCall Testing | For further study. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.2.3 State diagram | Derived from CEN EN 16454 [1]. Subsequent state diagram is related to the Permanent Reference Document of the Technical Specification Group RAN WG5 from the 3GPP RAN5 PRD 13 [i.3]. ETSI ETSI TS 103 412 V1.3.1 (2020-03) 22 Figure 5.2.3-1: State diagram - part 1 ETSI ETSI TS 103 412 V1.3.1 (2020-03) 23 Figure 5.2.3-2: St... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.3 Specification in TTCN | The present document is a prose text specification for Pan-European eCall end to end and in-band modem conformance testing derived from CEN EN 16454 [1]. It does not contain any TTCN-3 but can be used as a basis for future TTCN-3 development. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.4 Capabilities | PE eCall IVS can support different capabilities which effect the test case applicability: • PE eCall capable IVS vs. PE eCall only IVS • GSM only IVS vs. GSM and UMTS IVS • IVS including back-up battery vs. IVS not including back-up battery • exchangeable or reconfigurable SIM/USIM vs. embedded and non-configurable SIM... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.5 Test Case Selection | For further study. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.6 Test Configuration Parameters | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.6.1 eCall Type Suffix | The following eCall types can be triggered (see clause 6.1.2.2): • Automatic eCall • Manual eCall • Test eCall • Reconfiguration Call NOTE: Reconfiguration Call is not used by the test sequences in the present document. The applicable preambles for a test case are specified in the "Pre-test conditions" section. Several... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.7 TTCN Implementation | The TTCN Implementation allows to check for consistency and completeness of the description. It can be used as basis for a subsequent implementation. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 5.8 Execution Guidelines | If derivates of CEN TCs allow to select different TCs then there should be clear rules under which circumstance which derived test is allowable. Such guidelines may differ when a certification test is to be run and when some "field" test is to be performed. The hooks are to be provided in the TTCN. ETSI ETSI TS 103 412... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6 Generic Procedures | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.0 Preface | All signalling and protocol tests shall use the reference environments specified in ETSI TS 136 508 [10]. Where a test requires an environment that is different, this is specified in the test itself. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.1 General | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.1.1 General assumptions | The following assumptions are made concerning the initial conditions (prerequisites). Preambles rely on these assumptions being fulfilled. They may therefore add further conditions or specify conditions in more detail, or exceptionally state which restrictions are to be applied. Prerequisites: • MNO and PSAP Test Point... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.1.2 Generic procedures | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.1.2.0 Preface | These procedures serve as building blocks which can be used in preambles, test bodies and postambles. ETSI ETSI TS 103 412 V1.3.1 (2020-03) 27 |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.1.2.1 Procedure for network registration | UMTS: Step Procedure Message Sequence TP Verdict I - T Message 1 RRC Connection establishment. The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to: Registration. - - - - 2 --> LOCATION UPDATING REQUEST - - 3 <-- LOCATION UPDATING ACCEPT - - 4 --> TMSI REALLOCATION ... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.1.2.2 Procedure for eCall establishment | The procedure is parametrized with the type of eCall. Possible values: • automatic eCall • manual eCall • test eCall • reconfiguration eCall ETSI ETSI TS 103 412 V1.3.1 (2020-03) 28 UMTS: Sequence for automatic or manual eCall Step Procedure Message Sequence TP Verdict I - T Message 1 Steps of Preamble 1 - - - - 2 UE i... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.1.2.3 Procedure for eCall in progress | Step Procedure Message Sequence TP Verdict I - T Message 1 UE is made to establish an eCall of the requested type in accordance with manufacturer's instructions (see note) - - - - 2 eCall indicator - initiation --> PUSH-REQ 3 PSAP requests MSD <-- SEND MSD - - 4 IVS sends MSD --> MSD TX - - 5 PSAP is not able to decode... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.1.2.4 Procedure for eCall release (PSAP initiated) | Step Procedure Message Sequence TP Verdict I - T Message 1 <-- DISCONNECT - - 2 --> RELEASE - - 3 <-- RELEASE COMPLETE - - 4 <-- CHANNEL RELEASE - - 5 RRC Connection release - - - - |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.1.2.5 Procedure for eCall release (IVS initiated, preceding AL-ACK call clear down) | Step Procedure Message Sequence TP Verdict I - T Message 1 --> DISCONNECT - - 2 <-- RELEASE - - 3 --> RELEASE COMPLETE - - 4 --> CHANNEL RELEASE - - 5 RRC Connection release - - - - |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.1.2.6 Procedure for PSAP callback | UMTS: Step Procedure Message Sequence TP Verdict I - T Message 1 Paging <-- - - - 2 PAGING RESPONSE --> - - - 3 <-- AUTHENTICATION REQUEST - - 4 --> AUTHENTICATION RESPONSE - - 5 SS starts RRC security procedure - - 6 <-- SETUP - - 7 --> CALL CONFIRMED - - 8 --> ALERTING - - 9 --> CONNECT - - 10 <-- CONNECT ACKNOWLEDGE... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.1.2.7 Procedure for call rejection | The procedure is parametrized with the type of eCall. Possible values: • automatic eCall • manual eCall • test eCall • reconfiguration eCall UMTS: Sequence for automatic or manual eCall Step Procedure Message Sequence TP Verdict I - T Message 1 Steps of Preamble 1 - - - - 2 UE is made to initiate an eCall of the reques... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.2 Preambles | Preamble 1 for PE eCall capable IVS Testing: Pre-test conditions System Simulator: • 1 cell, default parameters (GERAN: ETSI TS 151 010-1 [9], UMTS: ETSI TS 134 123-1 [2]). ETSI ETSI TS 103 412 V1.3.1 (2020-03) 33 IVS: • The IVS is equipped with a USIM containing default values except for those listed below. USIM field... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.3 Postambles | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.3.0 Preface | In order to reach the initial state for testing the IVS needs to be de-registered and the vehicle power has to be turned down. See state IGNITION OFF in the state diagram in clause 5.2.3. As the IVS behaviour at the end of an emergency call differs considerably between a PE eCall capable IVS and a PE eCall only IVS dif... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.3.1 Postambles for eCall capable devices | A. Long variant: • If a test has a call set up this call is cleared down according to the procedure in clause 6.1.2.4. Expiry of T9 is expected. • The IVS is de-registered by the Tester sending a DETACH message. • The IVS is powered down by the Tester sending a "Vehicle power off". B. Short variant: • If a test has a c... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.3.2 Postambles for eCall only devices | A. Long variant: • If a test has a call set up this call is cleared down according to the procedure in clause 6.1.2.4. • Expiry of T9 is expected. • The Tester waits for the deregistration of the UE. This will happen within 12 hours after the call release. • The IVS is powered down by the Tester sending a "Vehicle powe... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 6.3.3 Special case: Limited Service Condition | In case the Limited Service Condition has been established by inserting a special USIM the postamble as described above needs to be completed by inserting a USIM which does not have a Forbidden PLMN registered. In case the Limited Service Condition has been established by performing an appropriate protocol sequence the... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7 Test Cases | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1 In-vehicle equipment and system (IVS) | 7.1.1 Conformance tests for in-vehicle user equipment for Pan European eCall 7.1.1.1 CTP 1.1.0.1 Conformance to ETSI TS 102 936-1 and ETSI TS 102 936-2 - PE eCall IVS The tests shall be performed at the system level with the behaviour, inputs and outputs as defined in ETSI TS 102 936-1 [3] and ETSI TS 102 936-2 [4], or... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.2a CTP 1.1.0.2 Test for conformance to valid SIM/USIM - PE eCall capable IVS | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.2a.1 Test Purpose (TP) | (1) with { IVS in mobile network coverage and the ignition is OFF } ensure that { when { vehicle Power ON } then { network registration } } |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.2a.2 Test applicability | This test case applies to PE eCall capable IVS. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.2a.3 Conformance requirements | The conformance requirements of CEN EN 16062 [6], clause 7.1.2 paragraph 2; clause 7.12.2 shall apply for this TC. The test shall complete CEN EN 16454 [1] CTP 1.1.0.2. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.2a.4 Test description | 7.1.1.2a.4.1 Pre-test conditions Ignition OFF. ETSI ETSI TS 103 412 V1.3.1 (2020-03) 38 7.1.1.2a.4.2 Test procedure sequence Table 7.1.1.2a.4.2-1: Main behaviour Step Procedure Message Sequence TP Verdict I - T Message 1 Vehicle Power ON - - - - 2 Self-test - - - - 3 Steps of the generic procedure for network registrat... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.2b CTP 1.1.0.2 Test for conformance to valid SIM/USIM - PE eCall only IVS | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.2b.1 Test Purpose (TP) | (1) with { IVS in mobile network coverage and the ignition is ON } ensure that { when { manual eCall triggered } then { network registration } } |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.2b.2 Test applicability | This test case applies to PE eCall only IVS. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.2b.3 Conformance requirements | The conformance requirements of CEN EN 16062 [6], clause 7.1.2 paragraph 2; clause 7.12.2 shall apply for this TC. The test shall complete CEN EN 16454 [1] CTP 1.1.0.2. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.2b.4 Test description | 7.1.1.2b.4.1 Pre-test conditions Preamble 1: Ignition ON. 7.1.1.2b.4.2 Test procedure sequence Table 7.1.1.2b.4.2-1: Main behaviour Step Procedure Message Sequence TP Verdict I - T Message 1 Trigger manual eCall - - - - 2 Steps of the generic procedure for network registration (clause 6.1.2.1) are performed - - 1 P 7.1... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.3.1 Test Purpose (TP) | (1) with { ignition OFF and the IVS is in mobile network coverage } ensure that { when { automatic eCall triggered } then { start timer Tp1 with no HMI alert is provided and IVS automatic eCall is not initiated until expiration of Tp1 } } |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.3.2 Test applicability | This test case applies to all types of PE eCall IVS. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.3.3 Conformance requirements | The conformance requirements of CEN EN 16072 [8], clause 7.10.1 paragraph 4 shall apply for this TC. The test shall complete CEN EN 16454 [1] CTP 1.1.0.3. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.3.4 Test description | 7.1.1.3.4.1 Pre-test conditions Ignition OFF. 7.1.1.3.4.2 Test procedure sequence Table 7.1.1.3.4.2-1: Main behaviour Step Procedure Message Sequence TP Verdict I - T Message 1 Trigger automatic eCall - - - - 2 Start non-reaction timer Tp1 - - - - - EXCEPTION: Steps 3a1 to 3a2 describe behaviour that depends on the tes... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.4 CTP 1.1.1.1 Power on and self test - PE eCall IVS | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.4.1 Test Purpose (TP) | (1) with { ignition OFF and no mobile coverage required } ensure that { when { vehicle Power ON and IVS performs self-test } then { self-test of IVS is successful and no faults are indicated } } |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.4.2 Test applicability | This test case applies to all types of PE eCall IVS. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.4.3 Conformance requirements | The conformance requirements of CEN EN 16062 [6], clause 7.1.5 shall apply for this TC. The test shall complete CEN EN 16454 [1] CTP 1.1.1.1. |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.4.4 Test description | 7.1.1.4.4.1 Pre-test conditions Ignition OFF; no mobile network coverage required. 7.1.1.4.4.2 Test procedure sequence Table 7.1.1.4.4.2-1: Main behaviour Step Procedure Message Sequence TP Verdict I - T Message 1 Vehicle Power ON - - - - 2 IVS performs self-test - - - - - EXCEPTION: Steps 3a1 to 3a2 describe behaviour... |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.5 CTP 1.1.2.1 eCall automatically activated - PE eCall IVS | |
25496abe4432c36f845a6284ed8c24b1 | 103 412 | 7.1.1.5.1 Test Purpose (TP) | (1) with { ignition ON and IVS in mobile network coverage } ensure that { when { automatic eCall triggered } then { Visual or audible indication provided and eCall successfully established } } ETSI ETSI TS 103 412 V1.3.1 (2020-03) 41 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.