hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
736e9a98ef6bb5efb3f13fd4a94e7db6 | 103 410-11 | 6.2.6 Object properties | A list of the object properties defined into the SAREF4LIFT extension is reported in Table 6.2.6-1. For each object property, the name, the domain, the range, and its definition are reported. ETSI ETSI TS 103 410-11 V2.1.1 (2024-10) 18 Table 6.2.6-1: List of the object properties defined within the SAREF4LIFT extension... |
736e9a98ef6bb5efb3f13fd4a94e7db6 | 103 410-11 | 6.2.7 Datatype properties | A list of the datatype properties defined into the SAREF4LIFT extension is reported in Table 6.2.7-1. For each datatype property, the name, the domain, the range, and its definition are reported. Table 6.2.7-1: List of the datatype properties defined within the SAREF4LIFT extension Object property Domain Range Definiti... |
736e9a98ef6bb5efb3f13fd4a94e7db6 | 103 410-11 | 7 Instantiating SAREF4LIFT | This clause shows different examples of how to instantiate the SAREF4LIFT extension of SAREF. The example presented in Figure 7-1 demonstrates how to represent information from group name SLIdentification as described in ETSI TS 103 735 [i.2], clause 6.2a. There are two new global identifiers of respective smart lifts ... |
736e9a98ef6bb5efb3f13fd4a94e7db6 | 103 410-11 | 8 Discussion | In the present clause 8, several observations about the SAREF4LIFT ontology and its usage are mentioned. The hierarchies and individuals defined in the extension should not be considered exhaustive, the ontology currently represents those devices described in different relevant standards and directives. It might be nee... |
47b832e0a6f423090165006556899c0a | 103 410-10 | 1 Scope | The present document presents SAREF4WATR, an extension of SAREF for the Water domain. SAREF4WATR V2.1.1 is a major revision of SAREF4WATR, using updated reference ontology patterns [3] to solve the harmonization needs [i.9], with updated development framework and tools [i.10]. |
47b832e0a6f423090165006556899c0a | 103 410-10 | 2 References | |
47b832e0a6f423090165006556899c0a | 103 410-10 | 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... |
47b832e0a6f423090165006556899c0a | 103 410-10 | 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... |
47b832e0a6f423090165006556899c0a | 103 410-10 | 3 Definition of terms, symbols and abbreviations | |
47b832e0a6f423090165006556899c0a | 103 410-10 | 3.1 Terms | For the purposes of the present document, the following terms apply: ontology: formal specification of a conceptualization, used to explicit capture the semantics of a certain reality |
47b832e0a6f423090165006556899c0a | 103 410-10 | 3.2 Symbols | Void. |
47b832e0a6f423090165006556899c0a | 103 410-10 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: EC European Commission KPI Key Performance Indicator M-Bus Meter-Bus OWL-DL Web Ontology Language - Description Logics RDF Resource Description Framework RDF-S Resource Description Framework Schema SAREF Smart Applications REFerence ontology S... |
47b832e0a6f423090165006556899c0a | 103 410-10 | 4 SAREF4WATR ontology and semantics | |
47b832e0a6f423090165006556899c0a | 103 410-10 | 4.1 Introduction and overview | The present document is a technical specification of SAREF4WATR, an OWL-DL ontology that extends SAREF for the Water domain. SAREF4WATR V2.1.1 is a major revision of SAREF4WATR, using updated reference ontology patterns specified in ETSI TS 103 548 [3] to solve the harmonization needs identified in ETSI TR 103 781 [i.9... |
47b832e0a6f423090165006556899c0a | 103 410-10 | 4.2 SAREF4WATR | 4.2.1 General Overview An overview of the SAREF4WATR ontology is provided in Figures 1 and 2. For all the entities described in the present document, it is indicated whether they are defined in the SAREF4WATR extension or elsewhere by the prefix included before their identifier, i.e. if the element is defined in SAREF4... |
47b832e0a6f423090165006556899c0a | 103 410-10 | 4.3 Instantiating SAREF4WATR | This clause shows different examples of how to instantiate the SAREF4WATR extension of SAREF. The example presented in Figure 13 depicts a water meter (ex:Meter4837QW123). It can be described by a set of static properties either reused from SAREF (e.g. saref:hasModel) or from SAREF4WATR (e.g. s4watr:hasFirmwareVersion)... |
47b832e0a6f423090165006556899c0a | 103 410-10 | 4.4 Discussion | In the following paragraphs, several observations about the SAREF4WATER ontology and its usage are mentioned. The hierarchies and individuals defined in the extension should not be considered exhaustive, the ontology currently represents those devices described in different relevant standards and directives. It might b... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 1 Scope | The present document presents the SAREF4WEAR ontology, an extension of SAREF [1] for the Wearables domain. SAREF4WEAR V2.1.1 is a major revision of the SAREF4WEAR, using updated reference ontology patterns [2] to solve the harmonization needs [i.4], with updated development framework and tools [3]. |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 2 References | |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 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... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 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... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 3 Definition of terms, symbols and abbreviations | |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 3.1 Terms | For the purposes of the present document, the following terms apply: ontology: formal specification of a conceptualization, used to explicit capture the semantics of a certain reality |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 3.2 Symbols | Void. |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ETSI European Telecommunications Standards Institute GPS Global Positioning System OWL Ontology Web Language OWL-DL Ontology Web Language-Description Logics RDF Resource Description Framework RDF-S Resource Description Framework Schema SAREF S... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4 SAREF4WEAR ontology and semantics | |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.1 Introduction and overview | The present document is a technical specification of SAREF4WEAR, an extension of SAREF [1] for the Wearables domain. Clause 4.1 of the present document shortly introduces a high level view of the envisioned SAREF4WEAR semantic model and modular ontology, with the retained concepts (i.e. classes) and their relations. SA... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.2 SAREF4WEAR | |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.2.1 General Overview | Figure 1 presents the high level view of the envisioned model of SAREF4WEAR ontology. In Figure 1, classes directly imported from SAREF ontology are in light orange, classes directly imported from other SAREF extension ontologies are in green. While classes developed for SAREF4WEAR are in blue. ETSI ETSI TS 103 410-9 V... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.2.2 Feature of interest | The Feature of Interest module describes the different actors that can be equipped with a Wearable device, as presented in Figure 2. There are different types of actors: living organisms (s4wear:LivingOrganism) and software (s4wear:Software). There is also a wearer class (s4wear:Wearer) to describe those living organis... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.2.3 WearableDevice | This module defines the different type of wearables identified within the requirements described in the ETSI TR 103 510 [i.1]. SAREF4WEAR defines the s4wear:WearableDevice abstract concept representing a saref:Device having the capability of being wore by a s4wear:Wearer. As depicted in Figure 3, the s4wear:WearableDev... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.2.4 Function | This model specifies the functions that are considered relevant for the wearables domain. There are three new concepts that are subsumed by the saref:Function concept and it reuses other functions defined in SAREF, as presented in Figure 4: • saref:ActuatingFunction defines the possibility of a s4wear:WearableDevice de... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.2.5 Occurrence | In some cases, wearables will be able to detect occurrences (s4wear:Occurrence) taking place (s4wear:takesPlaceAt) in a location that is relevant to the wearer (geo:Feature). These occurrences can be related to the device detecting them through the s4wear:isDetectedBy property, as shown in Figure 5. In the context of a... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.2.6 Property | SAREF4WEAR includes a classification of the different properties that are relevant to the wearables domain, as shown in Figure 6. These properties are classified into Wearable (s4wear:WearableProperty), wearer (s4wear:WearerProperty), crowd (s4wear:CrowdProperty), and environment (s4wear:EnvironmentProperty) ones. Furt... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.2.7 Wearable component | This model describes some of the components that could be integrated into a s4wear:WearableDevice device. There are different types of components, as depicted in Figure 7: • a saref:Actuator component, reused from the SAREF ontology [1]; • a saref:Sensor component, reused from the SAREF ontology [1], and a s4wear:Texti... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.2.8 Object properties | In Table 2, there is the list of the object properties defined into the SAREF4WEAR extension. For each object property, there is a report of the name, the domain, the range, and its definition. ETSI ETSI TS 103 410-9 V2.1.1 (2024-07) 14 Table 2: List of the object properties defined within the SAREF4WEAR extension Obje... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.2.9 Datatype properties | In Table 3, there is the list of the datatype properties defined into the SAREF4WEAR extension. For each datatype property, there is a report of the name, the domain, the range, and its definition. Table 3: List of the datatype properties defined within the SAREF4WEAR extension Object property Domain Range Definition s... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.3 Instantiating SAREF4WEAR | This clause shows different examples of how to instantiate the SAREF4WEAR extension of SAREF. In a healthcare scenario the wearer is represented by a user equipped with Wearable devices in charge of monitoring healthy parameters (e.g. heart rate, body temperature, blood oxygenation, etc.) and to inform the user in real... |
b7b732c79a8dc14b5fe8e2773e6c661a | 103 410-9 | 4.4 Discussion | In the following, several observations about the SAREF4WEAR ontology and its usage are mentioned. The hierarchies and individuals defined in the extension should not be considered exhaustive, the ontology currently represents those devices described in different relevant standards and directives. It might be needed to ... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 1 Scope | The present document defines Interoperability Test Descriptions for the eCall High Level Application Protocol (HLAP). |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 2 References | |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 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... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 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... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 3 Definition of terms, symbols and abbreviations | |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 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, (TS12) from a vehicle, supplemented with a minimum... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 3.2 Symbols | Void. |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP Third Generation Partnership Project AL-ACK Application Layer - Acknowledgement (also called HL-ACK) ANSI-C American National Standard Programming Language C CEN Comité Européen de Normalisation CFG Configuration CLI Calling Line Identity... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 4 Conventions | |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 4.1 Interoperability test process | |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 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, when a successful functional verification may result from an incorrect behaviou... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 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 events are considered during the test execution: • A stimulus corresponds to an event that enforces an EUT to proceed with a specific protocol action, like s... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 4.1.3 Interoperable Functions Statement (IFS) | 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 will... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 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. |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 4.3 Test Description naming convention | Table 1: TD naming convention TD/<root>/<gr>/<nn> Identifier Description <root> = root applicability BAS Basic tests ADV Advanced tests PER Performance tests <gr> = group IVS eCall terminal PSAP PSAP eCall modem-server IVS or PSAP <nn> = sequential number 01 to 99 Sequential numbers |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 4.4 Test Summary | Test scenario with a detailed test description, are provided in the present document to provide guidance to the participants and to ensure consistent testing among the different test sessions and participants. The detailed test descriptions are in the clause 7. It is recommended to conduct all test cases for all techno... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 5 Test Bed Architecture | |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 5.1 Test site layout | The generic test bed used to carry out interoperability tests, is summarized in figure 1. In normal operation conditions, the IVS calls the 112 called party number and shall set the Emergency Category IE of the Emergency Setup message as defined in table 10.5.135d of ETSI TS 124 008 [2]. This call setting is then inter... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 5.2 PSAP modes | Figure 6 given by EN 16062 [4] shows the overall HLAP flow diagram. It depicts the PSAP PULL and PSAP PUSH implementation variants in one diagram and requires some additional explanation for a better understanding. In the PSAP PULL mode: In PSAP PULL mode, the PSAP starts sending SEND-MSD (START) messages immediately a... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 6 Test Configurations | |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 6.1 Basic Interoperability Test Configuration | Interoperability tests will be performed using the set-up shown in figure 2. Ancillary measurement and message logging equipment is 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. IVS, PLMN and PSAP can be either ... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 6.2 Optional Interoperability Test Configurations | |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 6.2.1 eCall_CFG_02 | With the interoperability test configuration eCall_CFG_02, a TELEPHONE (only) is used to simulated a PSAP that is either not equipped with a PSAP eCall modem-server or a PSAP eCall modem server that fails to respond to the incoming Initiation Tone from the IVS for any reason. Figure 3: eCall_CFG_02 - Optional interoper... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 6.2.2 eCall_CFG_03 | In the Interoperability test configuration eCall_CFG_03, a mobile phone is used instead of an IVS to simulate an emergency call from an IVS, that fails to transmit an eCall Initiation Signal or transmits an invalid Initiation Tone, or from a miss-routed mobile phone originated the emergency call. In all such cases, the... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 6.2.3 eCall_CFG_04 | In the Interoperability test configuration eCall_CFG_04, more than one IVS will repetitively call the same PSAP to simulate a real service. The PSAP shall be able to handle a certain number of parallel emergency calls and route them to a certain number of operator phones. Figure 5: eCall_CFG_04 - Optional interoperabil... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 6.2.4 eCall_CFG_05 | In the Interoperability test configuration eCall_CFG_05, the IVS device has the ability to call TPSP or 112 eCall service. If IVS is calling first the TPS then TPSP have the ability to forward the MSD data and call 112 eCall operator. Figure 6: eCall_CFG_05 - Optional interoperability/diagnostic testing configuration |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 6.3 Default pre-test conditions | The following default pre-test conditions apply to all tests unless otherwise stated in the test cases description: • Ignition is ON and IVS is in mobile network coverage. • MNO and PSAP test points are available. • IVS has all the information needed to compile the MSD. IVS 1 Public GSM/UMTS Network PSAP eCall modem- s... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 6.4 Interoperable Functions Statement (IFS) | Table 6: PSAP features Item Entity IFS_ID Status Support 1 PSAP supports sending directly SEND-MSD message without waiting for INITIATION message PSAP_PULL o.501 (see note) 2 PSAP supports waiting for INITIATION Message prior to sending the SEND-MSD message PSAP_PUSH o.501 (see note) 3 PSAP supports 2-way speech PSAP_s... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 6.5 Test Configuration parameters | Table 8: Parameters Item Entity Description Value 1 PSAP long number Called party number to be used to reach the selected PSAP |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7 eCall test scenarios | |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 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 field 'Applicability' and is expressed with IFS statements. The tests apply to IVS and PSAP as well as to IVS or PSAP simulators. In EN 16062 HLAP standard [i.2] the PU... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.1 Basic test scenarios | 7.1.1 MSD transmission/reception/acknowledgement with PSAP in Pull mode Interoperability Test Description Identifier: TD_BAS_01 Objective: To verify the eCall initiation with the PSAP sending a SEND-MSG message without waiting for the INITIATION message. Configuration: eCall_CFG_01 References: Clause 7.4.2 of EN 16062 ... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.1.3 Voice communication after receipt of AL-ACK | Interoperability Test Description Identifier: TD_BAS_03 Objective: To verify that following transmission of the MSD and receipt of an application layer acknowledgement (AL-ACK) from the PSAP, the IVS and PSAP audio interfaces are reconnected and that 2-way speech is possible between the IVS and PSAP. Configuration: eCa... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.1.4 Retransmission of MSD on request from PSAP | Interoperability Test Description Identifier: TD_BAS_04 Objective: To verify that the IVS is able to recognize and act upon a request from the PSAP, during an ongoing speech conversation, to send or re-send an updated MSD. Configuration: eCall_CFG_01 References: Clause 7.6.2 of EN 16062 [4] Applicability: PSAP_PULL AND... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.1.5 Voice Communication after retransmission of MSD | Interoperability Test Description Identifier: TD_BAS_05 Objective: To verify that following retransmission of the MSD and receipt of an application layer acknowledgement (AL-ACK) from the PSAP, the IVS and PSAP audio systems are reconnected and that 2-way speech is possible between the IVS and PSAP operator. Configurat... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.1.6 Clear-down/PSAP initiated network clear-down | Interoperability Test Description Identifier: TD_BAS_06 Objective: To verify that when the PSAP clears down the eCall, the IVS also clears down following receipt of the mobile network clear-down message. Configuration: eCall_CFG_01 References: Clause 7.9 of EN 16062 [4] Applicability: PSAP_PULL AND IVS_NW_clear-down Pr... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.1.7 Clear-down/PSAP initiated application layer AL-ACK clear-down | Interoperability Test Description Identifier: TD_BAS_07 Objective: To verify that following the positive acknowledgment of the first MSD with AL-ACK = 0, the PSAP can request the IVS to clear-down on receipt of the second MSD with an application layer AL-ACK clear-down message from the PSAP and the IVS clears-down. Con... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.1.8 Call Back/PSAP initiated call back to IVS and re-send MSD | Interoperability Test Description Identifier: TD_BAS_08 Objective: To verify that if an eCall has been successfully terminated by the PSAP, then the IVS shall allow a call-back into the vehicle and re-send a MSD on request of the PSAP. Configuration: eCall_CFG_01 References: Clauses 7.10, 7.6.3 of EN 16062 [4] Clause 7... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.1.10 MSD activation type indicator set to 'Automatic' | Interoperability Test Description Identifier: TD_BAS_10 Objective: To verify that the MSD received from the IVS contains the eCall initiation indicator for an automatic triggered eCall. Configuration: eCall_CFG_01 References: Clause 6.3.2 of EN 15722 [3] Applicability: PSAP_PULL AND IVS_auto_eCall Pre-test conditions: ... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.1.11 MSD activation type indicator set to 'Manual' | Interoperability Test Description Identifier: TD_BAS_11 Objective: To verify that the MSD received from the IVS contains the correct eCall initiation indicator for a manually triggered eCall. Configuration: eCall_CFG_01 References: Clause 6.3.2 of EN 15722 [3] Applicability: PSAP_PULL AND IVS_man_eCall Pre-test conditi... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.1.12 MSD call type indicator set to 'Test Call' | Interoperability Test Description Identifier: TD_BAS_12 Objective: To verify that the MSD received from the IVS contains the correct test eCall indicator for a test eCall. Configuration: eCall_CFG_01 References: Clause 6.3.2 of EN 15722 [3] Applicability: PSAP_PULL AND IVS_test_call Pre-test conditions: Default see cla... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.2 Advanced IVS test scenarios | |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.2.1 Auto redial following busy during call set-up | Interoperability Test Description Identifier: TD_ADV_IVS_01 Objective: To verify that if the initial call set-up attempt fails for reason: busy, network congestion or PSAP out-of-service, the IVS makes automatic repeat dialling attempts to establish an emergency call. Configuration: eCall_CFG_02 References: Clause 7.12... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.2.2 Auto redial following no-answer during call set-up | Interoperability Test Description Identifier: TD_ADV_IVS_02 Objective: To verify that if the initial call set-up attempt fails for reason: no answer, the IVS makes automatic repeat dialling attempts to establish an emergency call. Configuration: eCall_CFG_02 References: Clause 7.12.3 of EN 16062 [4] Applicability: IVS_... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.2.3 IVS configured for 'eCall only' service (restricted) | Interoperability Test Description Identifier: TD_ADV_IVS_03 Objective: To verify that following power-up/ignition ON, an IVS configured for 'eCall only' service, and test/configuration calls, does not attempt to register on any mobile network until an eCall or test/reconfiguration call is initiated. Configuration: eCal... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.2.4 eCall deactivated during TPS call | Interoperability Test Description Identifier: TD_ADV_IVS_04 Objective: To verify that there is only one system active at a time. The 112 eCall is deactivated as long as TPS system is active. Configuration: eCall_CFG_05 References: Commission Delegeated Regulation (EU) 2017/79 [10] (Annex IV, clause 2.3) Applicability: ... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.2.5 Fall-back to 112-based eCall when TPS is not functional | Interoperability Test Description Identifier: TD_ADV_IVS_05 Objective: To verify the fall-back to 112-based eCall when the TPS is triggered but is not functional. Configuration: eCall_CFG_05 References: Commission Delegated Regulation (EU) 2017/79 [10] (Annex IV, clause 2.4) Applicability: IVS_eCall_and_TPS Pre-test co... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.2.6 IVS privacy protection from PSAP call-back | Interoperability Test Description Identifier: TD_ADV_IVS_06 Objective: To verify that 112 eCall IVS system is not available for communication with the PSAP if the PSAP test point initiates the communication during normal operation when there is no accident. (Vehicle in normal driving mode). Configuration: eCall_CFG_01 ... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.3 Advanced PSAP test scenarios | 7.3.1 Un-mute PSAP audio when Initiation Signal not received within 5 s (T4 expired) Interoperability Test Description Identifier: TD_ADV_PSAP_01 Objective: Verify that PSAP audio is un-muted and call is routed to an operator within 5 s following receipt of answering call, if a valid Initiation Signal is not received a... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.3.2 PSAP handling of more than 1 eCall simultaneously | Interoperability Test Description Identifier: TD_ADV_PSAP_02 Objective: Verify that a PSAP (modem-server) system can receive and process more than 1 eCall simultaneously from different IVS devices. Configuration: eCall_CFG_01 References: Clause 7.1 of EN 16072 [5] Applicability: PSAP_PULL AND PSAP_simult_eCalls Pre-tes... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.3.3 PSAP correct MSD additional data decoding | Interoperability Test Description Identifier: TD_ADV_PSAP_03 Objective: Check the capability of MSD additional data decoding from PSAP side. Configuration: eCall_CFG_01 References: Clause 6.1.5 of EN 15722 [3] Clause 7.7.2 of EN 16072 [5] Applicability: PSAP_PULL AND PSAP_MSDv2 AND IVS_MSDv2 AND IVS_add_MSD_data Pre-te... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.4 Performance test scenarios | |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.4.0 Introduction | Test scenario TD_PER_PSAP_01 is checking the capability of a PSAP to handle parallel repetitive calls as in a real PSAP environment and it is only applicable if the PSAP is connected to a network providing more than one B channel for simultaneous calls. Other test scenarios from TD_PER_PSAP_02 to TD_PER_PSAP_06 are rel... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.4.2 KPI 1 Success rate of eCall | KPI 1 according to TS 17234 [11] describes the relationship between the numbers of initiated CS eCalls at a given period of time versus the number of successful completed eCalls while the 112 is used as telephone number for the emergency call: Unit: [%] Definition for KPI 1: "eCall success rate" = ("successful eCalls"/... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.4.3 KPI 2 Success rate of call backs using eCall | KPI 2 according to TS 17234 [11] refers to the number of successful call-backs from PSAP to IVS, compared with the number of attempted call-backs: Unit: [%] Definition for KPI 2: "success rate of call-backs" = ("successful call-backs"/"all initiated call-backs") × 100 "successful call-backs" = "initiated call-backs" – ... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.4.4 KPI 3 Success rate of correct MSDs | KPI 3 according to TS 17234 [11] describes the relationship between the numbers of initiated MSD transmissions versus the number of successfully presented MSD content at the operator's desk: Unit: [%] Definition for KPI 3: "MSD success rate" = ("successful MSD"/"all initiated MSDs") × 100 "successful MSDs" = "initiated... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.4.5 KPI 4 Success rate of correct re-transmitted MSDs | KPI 4 according to TS 17234 [11] describes the relationship between the numbers of initiated MSD transmissions using CS GSM/UMTS versus the number of successfully presented MSD content at the operator's desk for the case that the PSAP operator requests a new MSD from the IVS: Unit: [%] Definition for KPI 4: "resubmitte... |
c2cda151cf93231d5b798953d4ff60a7 | 103 428 | 7.4.6 KPI 5 Duration of voice channel blocking | KPI 5 TS 17234 [11] represents the time the transmission of MSD blocks the voice channel, it applies only to circuit switched GSM/UMTS 112-eCalls. The time the voice channel is blocked can be defined as the time between successful call setup ("connected" is reported by the network) and the opening of voice communicatio... |
819f32b0ea5df47c17e5f4c41f79b63d | 103 427 | 1 Scope | The present document is a transposition of Recommendation ITU-T Q.3960 [1] without modifications. |
819f32b0ea5df47c17e5f4c41f79b63d | 103 427 | 2 References | |
819f32b0ea5df47c17e5f4c41f79b63d | 103 427 | 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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.