hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 4.2.8 Configuration 7: CF07 | ItsNodeB is in IUT's communication range is in AREA1 is close to the centre of AREA1 ItsNodeD is in IUT's communication range is in AREA1 is closer to ItsNodeB than IUT (Dist_R > Dist_F) Angle FSR formed by ItsNodeD, ItsNodeB and IUT is less than Angle_TH IUT is in AREA1 Figure 8: CF07 |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 4.3 Test architecture | The present document implements the general TTCN-3 test architecture described in ETSI EG 202 798 [i.9], clause 6.3.2 and clause 8.3.1. Figure 9 shows the TTCN-3 test architecture used for the GeoNetworking ATS. In single-component testcases (configuration CF01), the MTC is of type ItsNt and communicates with SUT over ... |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 4.4 Ports and ASPs (Abstract Services Primitives) | |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 4.4.1 Introduction | Two ports are used by the GeoNetworking ATS: • The geoNetworkingPort, of type GeoNetworkingPort. • The utPort of type UpperTesterPort. ITS TTCN-3 test execution ItsMtc (Sync component) ITS lower layers stack Upper tester transport ITS Test Adaptor SUT Adpt_Ctlr control port UTport control port External functions CODECS... |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 4.4.2 Primitives of the geoNetworkingPort | Two types of primitives are used in the geoNetworkingPort: • The geoNetworkingInd primitive used to receive messages of type GeoNetworkingPacket. • The geoNetworkingReq primitive used to send messages of type GeoNetworkingPacket. |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 4.4.3 Primitives of the utPort | This port uses two types of primitives: • The UtInitialize primitive used to initialize IUT. • The UtTrigger primitive used trigger upper layer events in IUT. |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 4.4.4 Primitives of the taPort | This port uses the following primitives to trigger special behaviour in Test adapter: • AcStartBeaconing: Test adapter shall start sending beacon messages for a simulated ITS node. • AcStopBeaconing: Test adapter shall stop sending beacon messages for a simulated ITS node. • AcStartPassBeaconing: Test adapter shall tra... |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 4.5 Executing CA tests in secured mode | All the GEONW tests, can be executed with security enabled or with security disabled. The choice of running the GEONW tests in secured or non-secured mode has no impact on the result of the GEONW tests because the test verdicts assess GEONW protocol behaviour only. The choice of running the GEONW tests in secured or no... |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 4.6 ETSI test adapter | All information of the ETSI test adapter is described in ETSI TR 103 099 [i.2]. |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 5 Untestable Test Purposes | Table 2 gives a list of TP, which are not implemented in the ATS due to the restriction of the chosen ATM. Table 2: Untestable TP Test purpose Reason None |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 6 ATS conventions | |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 6.1 Introduction | The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. The ATS conventions contain two clauses, the testing conventions an... |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 6.2 Testing conventions | |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 6.2.1 Testing states | |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 6.2.1.1 Initial state | All test cases start with the function f_prInitialState. This function brings the IUT in an "initialized" state by invoking the upper tester primitive UtInitialize. |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 6.2.1.2 Final state | All test cases end with the function f_poDefault. This function brings the IUT back in an "idle" state. As no specific actions are required for the idle state in the base standard, the function f_ poDefault does not invoke any action. As necessary, further actions may be included in the f_poDefault function. ETSI ETSI ... |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 6.3 Naming conventions | |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 6.3.1 Introduction | This test suite follows the naming convention guidelines provided in ETSI EG 202 798 [i.9]. |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 6.3.2 General guidelines | The naming convention is based on the following underlying principles: • in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 3) indicating the type of TTCN-3 element it represents; • suffixes should not be used except in those specific cases identified in table 2; • prefixes... |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 6.3.3 ITS specific TTCN-3 naming conventions | Next to such general naming conventions, table 4 shows specific naming conventions that apply to the ITS TTCN-3 test suite. Table 4: ITS specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier ITS Module Use upper-case initial letter Its"IUTname"_ ItsGeoNetworking_ Module contain... |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 6.3.4 Usage of Log statements | All TTCN-3 log statements use the following format using the same order: • Three asterisks. • The TTCN-3 test case or function identifier in which the log statement is defined. • One of the categories of log: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT. • Free text. • Three asterisks. EXAMPLE 1: log("*** TC_GEONW... |
9f74075e3c8636df9547f6b6c30bccb5 | 102 871-3 | 6.3.5 Test Case (TC) identifier | Table 5 shows the test case naming convention, which follows the same naming convention as the test purposes. Table 5: TC naming convention Identifier: TC_<root>_<gr>_<sgr>_<x>_<nn> <root> = root GEONW <gr> = group FDV Formatting and Data Validity PON Protocol Operation CAP Buffer Capacities <sgr> =sub-group BAH Basic ... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 1 Scope | The present document provides the Test Suite Structure and Test Purposes (TSS&TP) for the test specifications for the methods to ensure coexistence of cooperative ITS-G5 with TTT DSRC as specified in ETSI TS 102 792 [4] and ETSI EN 302 663 [1] in compliance with the relevant requirements and in accordance with the rele... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 2 References | |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 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... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 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... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 3 Definition of terms, symbols and abbreviations | |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 792 [4], ETSI EN 302 663 [1] and the following apply: Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [i.3]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [i.3]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [i.3]. Test Purpose... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: CenDsrcTollingZone data field of vehicle CAM containing protected zone information ProtectedCommunicationZone data field of roadside unit CAM containing protected zone information protectedZoneType distinguishes between temporary and non-temporary p... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 792 [4], ETSI EN 302 663 [1] and the following apply: ATS Abstract Test Suit CAM Cooperative Awareness Message CEN Comité Européen de Normalisation DSRC Dedicated Short Range Communication GPS Global Positioning System ICS Implementation C... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 4 Test configurations | |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 4.1 Overview | Test purposes of the present document address the mitigation techniques to avoid interference between European CEN Dedicated Short Range Communication (TTT DSRC) equipment and Intelligent Transport Systems (ITS) operating in the 5 GHz frequency range. The mitigation techniques are specified in ETSI TS 102 792 [4]. Mobi... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 4.2 TTT DSRC RF detector test configuration | The test configuration and test description for the TTT DSRC RF detector test is specified in clause 5.3.10.3.3 of ETSI EN 302 571 V2.1.1 [3]. |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 4.3 Geolocation simulator test configuration | For the test purposes that assess the correct detection of a tolling station by its geolocation, a GPS simulator is necessary. The GPS simulator is connected to the GPS antenna connector of the SUT and simulates the signals of GPS satellites characteristic for a certain geolocation. Alternatively the geolocation can be... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 4.4 CAM coexistence message test configuration | ETSI EN 302 637-2 [5] and ETSI TS 102 894-2 [6] specify the CAM data fields CenDsrcTollingZone for vehicle ITS-S (ICS 17) and ProtectedCommunicationZone for ITS-S of type road side unit (ICS 16), to disseminate the protected zone information. For a roadside unit the data element protectedZoneType is used to distinguish... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 4.5 TX power level test configuration | The test configuration and test description for the RF output power measurement is specified in clause 5.3.3 of ETSI EN 302 571 V2.1.1 [3]. |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 4.6 Unwanted emission test configuration | The test configuration and test description for the RF unwanted emissions measurement is specified in clause 5.3.4 of ETSI EN 302 571 V2.1.1 [3]. |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 4.7 Duty cycle test configuration | The time Ton is defined as the duration of a transmitted data packet. The time Toff is the time in between two transmissions. Ton can be determined by measuring the time while the transmit power level is above an appropriate threshold, while Toff is the time during which the transmit power level is below this threshold... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 4.8 Time synchronization test configuration | The test configuration for the time synchronization test consists of a tolling station that is synchronized with the SUT, so that the SUT is never transmitting when the toll system is transmitting or receiving. The transmission timing of the SUT can be assessed similar to the duty cycle test configuration specified in ... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5 Test Suite Structure (TSS) | |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.1 General | |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.1.1 Introduction | Test Purposes have been written for mitigation techniques to avoid interference between European Transport and Traffic Telematics Dedicated Short Range Communication (TTT DSRC) equipment and Intelligent Transport Systems (ITS) operating in the 5 GHz frequency range as defined in ETSI TS 102 792 [4] and ETSI EN 302 663 ... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.1.2 TP naming convention | TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. ETSI ETSI TS 102 916-2 V1.2.1 (2023-05) 9 Table 1: TP identifier naming convention scheme Identifier: <TP>_<scope>_<iut>_<nnn> <tp> = Test Purpose: fixed to "TP" <scop> = group MIT Test of mitigation method TRIG Test of coe... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.1.3 Test strategy | As the base standards ETSI TS 102 792 [4] and ETSI EN 302 663 [1] contain no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification ETSI TS 102 916-1 [2]. Radio conformance tests specified in ETSI EN 302 571 [3] are included in the present do... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2 Test Purposes | |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.0 Introduction | All PICS items referred to by their Implementation Conformance Statement (ICS) item number in this clause are as specified in ETSI TS 102 916-1 [2] unless indicated otherwise by another numbered reference. |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.1 Mitigation methods | |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.1.1 Mitigation method overview | ETSI TS 102 792 [4] specifies four mitigation methods for mobile ITS-S denominated as coexistence mode A, B, C, and D. The equipment manufacturer shall declare in ETSI TS 102 916-1 [2] the supported coexistence mode(s). Depending on the declared coexistence mode, the following clauses outline different test setups and ... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.1.2 Mitigation method prerequisites | For the mitigation method test purposes the SUT is assumed to be in a protected zone (see clause 5.1 and clause 5.2 in ETSI TS 102 792 V1.2.1 [4]). When the SUT is always operating in coexistence mode (ICS 3) the SUT is assumed to be always in the centre of the protected zone. ETSI ETSI TS 102 916-2 V1.2.1 (2023-05) 10... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.1.3 Coexistence mode A | If the equipment manufacturer declared in ETSI TS 102 916-1 [2] the support of coexistence mode A (ICS 8), then the test specification in this clause shall be applied when the preconditions are met. Coexistence mode A is only applicable when the antenna mounting distance is at least 1,5 m away from the intended TTT DSR... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.1.4 Coexistence mode B | If the equipment manufacturer declared in ETSI TS 102 916-1 [2] the support of coexistence mode B (ICS 9), then the test specification in this clause shall be applied when the preconditions are met. Identifier: TP_MIT_ALL_02 Summary: Coexistence mode B Configuration: Specified in clause 5.3.3 and clause 5.3.4 of ETSI E... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.1.5 Coexistence mode C | If the equipment manufacturer declared in ETSI TS 102 916-1 [2] the support of coexistence mode C (ICS 10), then the test specification in this clause shall be applied when the preconditions are met. Identifier: TP_MIT_ALL_03 Summary: Coexistence mode C Configuration: Specified in clause 4.7. Depending on the coexisten... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.1.6 Coexistence mode D | If the equipment manufacturer declared in ETSI TS 102 916-1 [2] the support of coexistence mode D (ICS 11), then the test specification in this clause shall be applied when the preconditions are met. ETSI ETSI TS 102 916-2 V1.2.1 (2023-05) 12 Identifier: TP_MIT_ALL_04 Summary: Coexistence mode D Configuration: Specifie... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.1.7 Combined power reduction and duty cycle restriction | If the equipment manufacturer declared in ETSI TS 102 916-1 [2], the use of a power reduction and/or a duty cycle restriction (ICS 4, ICS 5, or ICS 6) and the support of an alternative mitigation method (ICS 12) not covered by mitigation mode A, B, C, or D, then the test specification in this clause shall be applied wh... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.1.8 Synchronization of fixed ITS-S with a tolling station | If the equipment manufacturer declared in ETSI TS 102 916-1 [2] the use of a fixed ITS-G5 antenna (ICS 16) and the synchronization with a tolling station (ICS 7), then the test specification in this clause shall be applied when the preconditions are met. Identifier: TP_MIT_FIX_06 Summary: Fixed ITS-G5 station synchroni... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.2 Mitigation triggering | |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.2.1 Mitigation triggering overview | Outside a protected zone the DUT is usually operating in normal mode. ETSI ETSI TS 102 916-2 V1.2.1 (2023-05) 14 There are two possible triggering events that cause a mobile ITS-G5 station to switch to coexistence mode: 1) The radio detection of a tolling station. 2) The entering of a protected zone known from stored d... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.2.2 Radio detection | This test purpose assesses the correct functioning of the TTT DSRC radio detection, the transmission of protected zone information in the CAM, and the correct application of a mitigation method. TP_TRIG_ MOBILE_01 shall be applied when the equipment manufacturer declared in ETSI TS 102 916-1 [2] the use of a TTT DSRC r... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.2.3 Map based detection | This test purpose assesses the correct functioning of the TTT DSRC map based detection and the correct application of a mitigation method. TP_TRIG_ MOBILE_02 shall be applied when the equipment manufacturer declared in ETSI TS 102 916-1 [2] the use of a TTT DSRC map based detection (ICS 2). Identifier: TP_TRIG_ MOBILE_... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.2.4 Detection by temporary information from a vehicle CAM | This test purpose assesses the correct functioning of the TTT DSRC detection by reception of temporary protected zone information from a vehicle CAM and the correct application of a mitigation method. TP_TRIG_ MOBILE_03 shall be applied when the equipment manufacturer declared in ETSI TS 102 916-1 [2] the use of a TTT ... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.2.5 Detection by temporary information from an infrastructure CAM | This test purpose assesses the correct functioning of the TTT DSRC detection by reception of temporary protected zone information from an infrastructure CAM and the correct application of a mitigation method. ETSI ETSI TS 102 916-2 V1.2.1 (2023-05) 17 TP_TRIG_ MOBILE_04 shall be applied when the equipment manufacturer ... |
b51cf34c61e188bae647ce716a4aba2d | 102 916-2 | 5.2.2.6 Detection by permanent information from an infrastructure CAM | This test purpose assesses the correct functioning of the TTT DSRC detection by reception of permanent protected zone information from an infrastructure CAM and the correct application of a mitigation method. ETSI ETSI TS 102 916-2 V1.2.1 (2023-05) 18 TP_TRIG_ MOBILE_05 shall be applied when the equipment manufacturer ... |
3820b50ffcc415a072efb507057d98de | 102 871-1 | 1 Scope | The present document provides the Protocol Implementation Conformance Statement (PICS) pro forma for Conformance test specifications for ITS GeoNetworking as defined in ETSI TS 103 836-4-1 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.2]. |
3820b50ffcc415a072efb507057d98de | 102 871-1 | 2 References | |
3820b50ffcc415a072efb507057d98de | 102 871-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... |
3820b50ffcc415a072efb507057d98de | 102 871-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... |
3820b50ffcc415a072efb507057d98de | 102 871-1 | 3 Definition of terms, symbols and abbreviations | |
3820b50ffcc415a072efb507057d98de | 102 871-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 836-4-1 [1], ISO/IEC 9646-1 [i.1] and ISO/IEC 9646-7 [i.2] apply. |
3820b50ffcc415a072efb507057d98de | 102 871-1 | 3.2 Symbols | Void. |
3820b50ffcc415a072efb507057d98de | 102 871-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CBF Contention-Based Forwarding GAC Geographically-Scoped Anycast GBC Geographically-Scoped Broadcast GEONET GeoNetworking GUC Geo Unicast ICS Implementation Conformance Statement ITS Intelligent Transportation Systems ITS-G5 5 GHz wireless co... |
3820b50ffcc415a072efb507057d98de | 102 871-1 | 4 Conformance requirement concerning PICS | If it claims to conform to the present document, the actual PICS pro forma to be filled in by a supplier shall be technically equivalent to the text of the PICS pro forma given in annex A, and shall preserve the numbering, naming and ordering of the pro forma items. An ICS which conforms to the present document shall b... |
3820b50ffcc415a072efb507057d98de | 102 871-1 | 5 Mnemonics for PICS reference | To avoid an update of all related documents when the PICS document is changed, table 1 introduces mnemonic names and the correspondence with the PICS item number. ETSI ETSI TS 102 871-1 V2.1.1 (2026-01) 7 Table 1: Mnemonics for PICS reference Mnemonic PICS item PICS_GN_LOCAL_GN_ADDR A.15/1 PICS_GN_LOCAL_ADDR_CONF_METHO... |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for Geonetworking Basic Transport Protocol (BTP) as defined in ETSI EN 302 636-5-1 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.5]. The objective of the present document is to provide ... |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 2 References | |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 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... |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 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... |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 3 Definition of terms, symbols and abbreviations | |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 302 636-5-1 [1], ISO/IEC 9646-1 [i.2] and in ISO/IEC 9646-7 [i.5] apply. |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 3.2 Symbols | Void. |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ATM Abstract Test Metho ATS Abstract Test Suite BTP Basic Transport Protocols CAN Controller Area Network ITS Intelligent Transportation Systems IUT Implementation Under Test MTC Main Test Component PIXIT Partial Protocol Implementation Extra ... |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 4 Abstract Test Method (ATM) | |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 4.1 Abstract protocol tester | The abstract protocol tester used by this test suite is described in figure 1. The test system will simulate valid and invalid protocol behaviour, and will analyse the reaction of the IUT. ETSI ETSI TS 102 870-3 V1.2.1 (2022-03) 8 Figure 1: Abstract protocol tester - BTP |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 4.2 Test Configuration | This test suite uses a unique test configuration in order to cover the different test scenarios. In this configuration, the tester simulates one ITS station implementing the BTP protocol. |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 4.3 Test architecture | This test specification implements the general TTCN-3 test architecture described in ETSI EG 202 798 [i.1], clauses 6.3.2 and 8.3.1. Figure 2 shows the test architecture used in for the BTP ATS. The BTP test component requires using only the Main Test Component (MTC). The MTC communicates with the BTP SUT over the btpP... |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 4.4 Ports and ASPs (Abstract Services Primitives) | |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 4.4.1 General | Two ports are used by the BTP ATS: • The btpPort, of type BtpPort • The utPort of type UpperTesterPort |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 4.4.2 Primitives of the btpPort | Two types of primitives are used in the btpPort: • The BtpInd primitive used to receive messages of type BtpPdu • The BtpReq primitive used to send messages of type BtpPdu |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 4.4.3 Primitives of the utPort | This port uses two types of primitives: • The UtInitialize primitive used to initialise IUT • The UtTrigger primitive used trigger upper layer events in IUT ITS TTCN-3 test execution ItsNt (MTC) ITS lower layers stack Upper tester transport ITS Test Adaptor SUT Adpt_Ctlr control port UTport control port NT External fun... |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 5 Untestable Test Purposes | This clause gives a list of TP, which are not implemented in the ATS due to the chosen ATM or other restrictions. Table 1: Untestable TP Test purpose Reason None |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 6 ATS conventions | |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 6.1 Introduction | The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. The ATS conventions contain two clauses, the testing conventions an... |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 6.2 Testing conventions | |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 6.2.1 Testing states | |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 6.2.1.1 Initial state | All test cases start with the function f_prInitialState. This function brings the IUT in an "initialized" state by invoking the upper tester primitive UtInitialize. |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 6.2.1.2 Final state | All test cases end with the function f_poDefault. This function brings the IUT back in an "idle" state. As no specific actions are required for the idle state in the base standard, the function f_ poDefault does not invoke any action. As necessary, further actions may be included in the f_poDefault function. |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 6.3 Naming conventions | |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 6.3.1 Introduction | This test suite follows the naming convention guidelines provided in ETSI EG 202 798 [i.1]. |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 6.3.2 General guidelines | The naming convention is based on the following underlying principles: • in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 2) indicating the type of TTCN-3 element it represents; • suffixes should not be used except in those specific cases identified in table 2; ETSI ETSI ... |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 6.3.3 ITS specific TTCN-3 naming conventions | Next to such general naming conventions, the following table 3 shows specific naming conventions that apply to the ITS TTCN-3 test suite. ETSI ETSI TS 102 870-3 V1.2.1 (2022-03) 12 Table 3: ITS specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier ITS Module Use upper-case init... |
8f5e9b42435134a423ec61b0515717f7 | 102 870-3 | 6.3.4 Usage of Log statements | All TTCN-3 log statements use the following format using the same order: • Three asterisks • The TTCN-3 test case or function identifier in which the log statement is defined • One of the categories of log: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT • Free text • Three asterisks EXAMPLE 1: log("*** f_utInitializ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.