ETSI ETS 300 394-4-9 ed.1 (1999-06)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Prizemni snopovni radio (TETRA) - Specifikacija za preskušanje skladnosti - 4. del: Specifikacija za preskušanje protokola za neposredno obratovanje (DMO) ¬- 9. poddel: Abstraktni preskušalni niz (ATS) za prehod mobilne postaje (MS)Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 4: Protocol testing specification for Direct Mode Operation (DMO); Sub-part 9: Abstract Test Suite (ATS) for Mobile Station (MS) Gateway33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:ETS 300 394-4-9 Edition 1SIST ETS 300 394-4-9 E1:2003en01-december-2003SIST ETS 300 394-4-9 E1:2003SLOVENSKI
STANDARD



SIST ETS 300 394-4-9 E1:2003



EUROPEANETS 300 394-4-9TELECOMMUNICATIONJune 1999STANDARDSource: TETRAReference: DE/TETRA-02009-4-9ICS:33.020Key words:TETRA, protocol, radio, TTCNTerrestrial Trunked Radio (TETRA);Conformance testing specification;Part 4: Protocol testing specification forDirect Mode Operation (DMO);Sub-part 9: Abstract Test Suite (ATS)for Mobile Station (MS) GatewayETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEInternet: secretariat@etsi.fr - http://www.etsi.orgTel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1999. All rights reserved.SIST ETS 300 394-4-9 E1:2003



Page 2ETS 300 394-4-9: June 1999Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Standards Making Support Dept." at the address shown on the title page.SIST ETS 300 394-4-9 E1:2003



Page 3ETS 300 394-4-9: June 1999ContentsForeword.71Scope.92References.93Definitions and abbreviations.103.1TETRA definitions.103.2TETRA abbreviations.103.3ISO 9646 definitions.103.4ISO 9646 abbreviations.114Abstract Test Method (ATM).114.1ATM for the DM-MAC ATS.114.1.1Lower Tester (LT).124.1.2Upper Tester (UT).124.1.3Test Co-ordination Procedures (TCP).124.1.4Point of Control and Observation (PCO).124.2ATM for the layer 3 ATS.134.2.1Single PCO testing.134.2.1.1Lower Tester (LT).134.2.1.2Upper Tester (UT).134.2.1.3Test Co-ordination Procedures (TCP).134.2.1.4Point of Control and Observation (PCO).144.2.2Multiple PCO testing.144.2.2.1Lower Testers (LT).144.2.2.2Upper Tester (UT).144.2.2.3Test Co-ordination Procedures (TCP).144.2.2.4Point of Control and Observation (PCO).144.2.3Test configurations and use of concurrent TTCN.155ATS conventions.165.1Naming conventions.165.1.1Declarations part.165.1.1.1Test suite type and structured type definitions.165.1.1.2Test suite operations definitions.165.1.1.3Test suite parameter declarations.165.1.1.4Test case selection expression definitions.165.1.1.5Test suite constant declarations.175.1.1.6Test suite variable declarations.175.1.1.7Test case variable declarations.175.1.1.8PCO declarations.175.1.1.9Timer declarations.175.1.1.10ASP type definitions.175.1.1.11PDU type definitions.185.1.1.12Alias definitions.185.1.2Constraints part.185.1.3Dynamic part.195.1.3.1Test case identifier.195.1.3.2Test step identifier.195.1.3.3Default identifier.195.2TC and TP naming.19Annex A (normative):ATS for TETRA DMO MS-GW MAC layer.20A.1ATS for TETRA DMO MS-GW MAC protocol.20A.1.1The TTCN Graphical form (TTCN.GR).20SIST ETS 300 394-4-9 E1:2003



Page 4ETS 300 394-4-9: June 1999A.1.2The TTCN Machine Processable form (TTCN.MP).20A.2ATS for TETRA DMO MS-GW NWK protocol.20A.2.1The TTCN Graphical form (TTCN.GR).20A.2.2The TTCN Machine Processable form (TTCN.MP).20Annex B (normative):Partial PIXIT proforma for TETRA DMO MS-GW protocol.21B.1Partial PIXIT proforma for TETRA DMO MS-GW MAC layer protocol.21B.1.1Identification summary.21B.1.2ATS summary.21B.1.3Test laboratory.21B.1.4Client identification.21B.1.5SUT.22B.1.6Protocol layer information.22B.1.6.1Protocol identification.22B.1.6.2IUT information.22B.1.6.2.1Implicit send events.22B.1.6.2.2Parameter values.23B.2Partial PIXIT proforma for TETRA DMO MS-GW NWK layer protocol.23B.2.1Identification summary.23B.2.2ATS summary.24B.2.3Test laboratory.24B.2.4Client identification.24B.2.5SUT.24B.2.6Protocol layer information.25B.2.6.1Protocol identification.25B.2.6.2IUT information.25B.2.6.2.1Implicit send events.25B.2.6.2.2Parameter values.26Annex C (normative):Protocol Conformance Test Report (PCTR) proforma for TETRA DMO MS-GW protocol.28C.1PCTR proforma for TETRA DMO MS-GW MAC layer protocol.28C.1.1Identification summary.28C.1.1.1Protocol conformance test report.28C.1.1.2IUT identification.28C.1.1.3Testing environment.28C.1.1.4Limits and reservation.29C.1.1.5Comments.29C.1.2IUT conformance status.29C.1.3Static conformance summary.29C.1.4Dynamic conformance summary.30C.1.5Static conformance review report.30C.1.6Test campaign report.31C.1.7Observations.31C.2PCTR proforma for TETRA DMO MS-GW MAC layer protocol.32C.2.1Identification summary.32C.2.1.1Protocol conformance test report.32C.2.1.2IUT identification.32C.2.1.3Testing environment.32C.2.1.4Limits and reservation.32C.2.1.5Comments.33C.2.2IUT conformance status.33C.2.3Static conformance summary.33C.2.4Dynamic conformance summary.33C.2.5Static conformance review report.34C.2.6Test campaign report.35C.2.7Observations.36SIST ETS 300 394-4-9 E1:2003



Page 5ETS 300 394-4-9: June 1999Annex D (informative):Bibliography.37History.38SIST ETS 300 394-4-9 E1:2003



Page 6ETS 300 394-4-9: June 1999Blank pageSIST ETS 300 394-4-9 E1:2003



Page 7ETS 300 394-4-9: June 1999ForewordThis European Telecommunication Standard (ETS) has been produced by the Terrestrial Trunked Radio(TETRA) Project of the European Telecommunications Standards Institute (ETSI).This ETS consists of 4 parts as follows:Part 1:"Radio";Part 2:"Protocol testing specification for Voice plus Data (V+D)";Part 4:"Protocol testing specification for Direct Mode Operation (DMO)";Part 5:"Security".Transposition datesDate of adoption of this ETS:4 June 1999Date of latest announcement of this ETS (doa):30 September 1999Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 March 2000Date of withdrawal of any conflicting National Standard (dow):31 March 2000SIST ETS 300 394-4-9 E1:2003



Page 8ETS 300 394-4-9: June 1999Blank pageSIST ETS 300 394-4-9 E1:2003



Page 9ETS 300 394-4-9: June 19991ScopeThis ETS contains the Abstract Test Suites (ATS) to test the TETRA Direct Mode Operation (DMO) MSGateway protocol at layer 3, called Direct Mode Call Control (DMCC) and the MS-Gateway protocol atlayer 2, the Medium Access Control (MAC) protocol. The DMCC and MAC protocols are specified inETS 300 396-1 [1]and in ETS 300 396-5 [2]. The Test Suite Structure (TSS) and Test Purposes (TPs) forthese ATSs are defined in ETS 300 394-4-7 [4].The objective of these test specifications are to provide a basis for approval tests for TETRA equipmentgiving a high probability of air interface inter-operability between different manufacturer's TETRAequipment.The ISO standard for the methodology of conformance testing, ISO/IEC 9646-1 [5], ISO/IEC 9646-2 [6],ISO/IEC 9646-3 [7] and ISO/IEC 9646-5 [8], as well as the ETSI rules for conformance testing,ETS 300 406 [9] and ETR 141 [10] are used as a basis for the test methodology.Annex A provides the Tree and Tabular Combined Notation (TTCN) part of these two ATSs.Annex B provides the Partial Protocol Implementation eXtra Information for Testing (PIXIT) Proforma ofthis ATS.Annex C provides the Protocol Conformance Test Report (PCTR) Proforma of this ATS.2ReferencesThis ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 396-1 (1998): "Terrestrial Trunked Radio (TETRA); Technicalrequirements for Direct Mode Operation (DMO); Part 1: General networkdesign".[2]ETS 300 396-5: "Terrestrial Trunked Radio (TETRA); Technical requirementsfor Direct Mode Operation (DMO); Part 5: Gateways".[3]ETS 300 396-8-3: "Terrestrial Trunked Radio (TETRA); Direct Mode Operation(DMO); Part 8: PICS proforma; Sub-part 3: Direct Mode Gateway (DM-GATE)".[4]ETS 300 394-4-7: "Terrestrial Trunked Radio (TETRA); Conformance testingspecification; Part 4: Protocol testing specification for Direct Mode Operation(DMO); Sub-part 7: Test Suite Structure and Test Purposes (TSS&TP) forMobile Station Gateway".[5]ISO/IEC 9646-1 (1994): "Information technology; Open SystemsInterconnection; Conformance Testing Methodology and Framework; Part 1:General Concepts". (See also ITU-T Recommendation X.290 (1991)).[6]ISO/IEC 9646-2 (1994): "Information technology; Open SystemsInterconnection; Conformance Testing Methodology and Framework; Part 2:Abstract Test Suite Specification". (See also ITU-T Recommendation X.291(1991)).[7]ISO/IEC 9646-3 (1992): "Information technology; Open SystemsInterconnection; Conformance testing methodology and framework; Part 3: Thetree and tabular combined notation". (See also ITU-T Recommendation X.292(1992)).SIST ETS 300 394-4-9 E1:2003



Page 10ETS 300 394-4-9: June 1999[8]ISO/IEC 9646-5 (1994): "Information technology; Open SystemsInterconnection; Conformance testing methodology and framework; Part 5:Requirements on test laboratories and clients for the conformance assessmentprocess". (See also ITU-T Recommendation X.292 (1992)).[9]ETS 300 406: "Methods for Testing and Specification (MTS); Protocol andprofile conformance testing specifications; Standardization methodology".[10]ETR 141 (1994): "Methods for Testing and Specification (MTS); Protocol andprofile conformance testing specifications; The Tree and Tabular CombinedNotation (TTCN) style guide".3Definitions and abbreviations3.1TETRA definitionsFor the purposes of this ETS, the definitions given in ETS 300 396-5 [2] apply.3.2TETRA abbreviationsFor the purposes of this ETS the following TETRA abbreviations apply:DMCCDirect Mode Call ControlDMMMDirect Mode Mobility ManagementMACMedium Access ControlMSMobile StationMS-GWMobile Station GatewayNWKNetworkSDSShort Data ServiceSDUService Data Unit3.3ISO 9646 definitionsFor the purposes of this ETS the following ISO/IEC 9646-1 [5] definitions apply:Abstract Test Suite (ATS)Abstract Test Method (ATM)Implementation Conformance Statement (ICS)Implementation Under Test (IUT)Implementation eXtra Information for Testing (IXIT)Lower Tester (LT)PICS proformaPIXIT proformaPoint of Control and Observation (PCO)Protocol Implementation Conformance Statement (PICS)Protocol Implementation eXtra Information for Testing (PIXIT)Service Access Point (SAP)Single Party Testing (SPyT)System Under Test (SUT)Upper Tester (UT)For the purposes of this ETS the following ISO/IEC 9646-3 [7] definitions apply:TTCN.GRTTCN.MPFor the purposes of this ETS the following ISO/IEC 9646-5 [8] definitions apply:Protocol Conformance Test Report (PCTR)PCTR proformaSIST ETS 300 394-4-9 E1:2003



Page 11ETS 300 394-4-9: June 19993.4ISO 9646 abbreviationsFor the purposes of this ETS the following ISO/IEC 9646-1 [5] abbreviations apply:ASPAbstract Service PrimitiveATMAbstract Test MethodATSAbstract Test SuiteIUTImplementation Under TestLTLower TesterMTCMain Test ComponentPCOPoint of Control and ObservationPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementsPIXITProtocol Implementation eXtra Information for TestingPTCParallel Test ComponentSAPService Access PointSPyTSingle Party TestingSUTSystem Under TestTCTest CaseTPTest PurposeTTCNTree and Tabular Combined NotationTSSTest Suite StructureUTUpper TesterFor the purposes of this ETS the following ISO/IEC 9646-5 [8] abbreviations apply:PCTRProtocol Conformance Test Report4Abstract Test Method (ATM)In the present document the following naming convention is taken: the Network layer covers the DirectMode Call Control (DMCC) and the Direct Mode Mobility Management (DMMM) protocol.4.1ATM for the DM-MAC ATSThis subclause describes the ATM used for testing the DM-MAC layer protocol of an MS-GW. It is theembedded variant of the remote test method used in Single Party Testing (SPyT) context, as defined inISO/IEC 9646-2 [6], clause 11. This test method has been selected, because:-this test method implies no specific requirements from the Implementation Under Test (IUT);-the upper Service Access Point (SAP) of the IUT cannot be directly observed;-the variety of the possible TETRA implementations is a serious technical obstacle for the adoptionof a different ATM;-this test method places minimum limitations in the realization of conformance testing.SIST ETS 300 394-4-9 E1:2003



Page 12ETS 300 394-4-9: June 1999The selected test method is illustrated in figure 1.Test systemSUTUpperlayersIUTNWK- PDUsTETRA physical layer and radio communicationUTASPsNetworkDM-MACTCP LT
layerlayerFigure 1: Remote SPyT test method for TETRA DMO MAC layer4.1.1Lower Tester (LT)A LT is located in a remote TETRA test system. It controls and observes the behaviour of the IUT.4.1.2Upper Tester (UT)There is no explicit UT in the remote test method, but the layers above inside the System Under Test(SUT) are used implicitly for testing the DM-MAC layer.4.1.3Test Co-ordination Procedures (TCP)The implicit send events defined by the provider of an implementation in annex B serve the purpose of theTCP. They are used as an input to the IUT communicating with the UT to initiate test events at the DMOMAC layer.4.1.4Point of Control and Observation (PCO)All test events at the PCO carrying service user data are specified in terms of MAC layer PDUs. Only fewAbstract Service Primitives (ASPs) are defined for control or observation purposes. The mapping of theMAC PDUs into the physical layer frame structure is left to the test implementation.SIST ETS 300 394-4-9 E1:2003



Page 13ETS 300 394-4-9: June 19994.2ATM for the layer 3 ATSThis subclause describes the different ATMs used for testing the Network Layer protocol. The selectedmethod is the remote method, as defined in ISO/IEC 9646-2 [6], clause 11.The remote test method has been selected, because:-this test method implies no specific requirements from the Implementation Under Test (IUT);-the upper Service Access Point (SAP) of the IUT cannot be directly observed;-the variety of the possible TETRA implementations is a serious technical obstacle for the adoptionof a different ATM;-this test method places minimum limitations in the realization of conformance testing.Since the protocol defines the operation of a MS-GW via gateway, only one interface is used. The protocolalso defines cases where the MS-GW is pre-empting an other DM-MS which is master of a call viaGateway; in these cases two interfaces need to be tested simultaneously. This implies that two testingmethods shall be used: the remote single-party test method (with one PCO) and the remote multi-partytest method with two PCOs.4.2.1Single PCO testingThe selected test method is illustrated in figure 2.Test systemSUTUpperlayersIUTNWK- PDUsTETRA physical layer and radio communicationUTPCOASPsNetworkDM-MAC layerDM-MAC layerTCP LT
layerFigure 2: Remote single party test method for TETRA MS-GW NWK protocol4.2.1.1Lower Tester (LT)A LT is located in a remote TETRA test system. It controls and observes the behaviour of the IUT.4.2.1.2Upper Tester (UT)There is no explicit UT in the remote test method, but the TETRA MS-GW NWK layer and the layersabove inside the System Under Test (SUT) are used implicitly for testing the DMCC layer.4.2.1.3Test Co-ordination Procedures (TCP)The implicit send events defined by the provider of an implementation in annex B serve the purpose of theTCP. They are used as an input to the IUT communicating with the UT to initiate test events at the NWKprotocol layer.SIST ETS 300 394-4-9 E1:2003



Page 14ETS 300 394-4-9: June 19994.2.1.4Point of Control and Observation (PCO)The PCO is located inside the protocol.All test events at the PCO carrying service user data is specified in terms of PDUs. The mapping of thePDUs to possible Medium Access Control (MAC) layer service primitives is left to the test implementation.4.2.2Multiple PCO testingThe selected test method is illustrated in figure 3.SUTIUTNWK- PDUsTETRA physical layer and radio communicationPCO1NetworkDM-MAC layer LT1
PCO2 LT2
DM-MAC layerNWK- PDUsDM-MAC layerLOWER TESTER CONTROL FUNCTIONTest systemCP1CP2layerASPsASPsUpper layersUTTCPTCPFigure 3: Remote multi party test method for TETRA MS-GW NWK protocol4.2.2.1Lower Testers (LT)Two LT: LT1 and LT2 are located in a remote TETRA test system. They observe the behaviour of the IUT.They are controlled and synchronized by the lower tester control function.4.2.2.2Upper Tester (UT)There is no explicit UT in the remote test method, but the layers above inside the System Under Test(SUT) are used implicitly for testing the DMCC layer.4.2.2.3Test Co-ordination Procedures (TCP)The implicit send events defined by the provider of an implementation in annex B serve the purpose of theTCP. They are used as an input to the IUT communicating with the UT to initiate test events at the NWKprotocol layer.4.2.2.4Point of Control and Observation (PCO)The PCOs are located inside the protocol.All test events at the PCOs carrying service user data are specified in terms of PDUs. The mapping of thePDUs to possible Medium Access Control (MAC) layer service primitives is left to the test implementation.SIST ETS 300 394-4-9 E1:2003



Page 15ETS 300 394-4-9: June 19994.2.3 Test configurations and use of concurrent TTCNAs this ATS covers both single-party testing using non-concurrent TTCN, and multi-party testing usingconcurrent TTCN, the notation chosen for the complete ATS is concurrent TTCN syntax. Therefore, testscomponents are defined to describe the two configurations: the "single_party" configuration and the"multi_party" configuration, as shown in figures 4 and 5.The single_party configuration is used in case of single-party testing, i.e. for the protocol between theMS-GW and the gateway. Only one test component, which is the Main Test Component (MTC)MTC_SINGLE, connected to the IUT via the PCO LNWK, is needed is this case.MTC_SINGLEIUTLNWKFigure 4: Single_party configurationThe Multi_party configuration is used when an other DM-MS is needed to check the protocol, i.e. to testpre-emption when an other DM-MS is master. In this case, three components are needed, these are theMTC MTC_GATE_MS, and two parallel Test Components (PTCs) PTC_GATE and PTC_MS, which areconnected to the MTC via the two co-ordination points CP_GATE and CP_MS. PTC_GATE and PTC_MSare further connected to the IUT via the two PCOs LNWK and LNWK_MS.MTC_GATE_MSIUTLNWKCP_GATECP_MSPTC_GATEPTC_MSLNWK_MSFigure 5: Multi_party configurationSIST ETS 300 394-4-9 E1:2003



Page 16ETS 300 394-4-9: June 19995ATS conventionsThis clause describes the conventions applied to define the two ATSs and gives the naming conventionschosen for the different elements of the ATSs.The ATS conventions are intended to give a better understanding of the ATS but they describe also theconventions made for the development of the ATS, thus for any later maintenance purposes or furtherdevelopment of the ATS, the conventions described in this clause shall be considered.5.1Naming conventions5.1.1Declarations partThis subclause describes the naming conventions chosen for the elements of the ATS declarations part.5.1.1.1Test suite type and structured type definitionsThe test suite type and test suite structured type identifiers describe the information elements, and eachwhole word included in the name is written in lowercase starting by an uppercase letter:EXAMPLE:Priority_Level_Typesimple type;SSI_Typesimple type;ITSI_Typestructured type.In the case an abbreviation is included in the declaration name, there is an underscore ("_") before and/orafter it, separating it from the rest of the identifier. This rule with abbreviations apply to all the namingconventions in the whole test suite.5.1.1.2Test suite operations definitionsThe test suite operation identifiers are composed of strings in uppercase letters starting by the uppercasestring "TSO_". The different strings in the definition are separated with underscores.EXAMPLE:TSO_ACTIVE_IND_CALL_OCCUPATION_GATE_MS.5.1.1.3Test suite parameter declarationsThe test suite parameter identifiers are composed of strings in uppercase letters starting by the uppercasestring "PIC_" or "PIX_" and separated by underscores.If the test suite parameter references a PICS item, the prefix "PIC_" is used.EXAMPLE 1:PIC_CIRCUIT_MODE_CALL.If the test suite parameter references a PIXIT item, the prefix "PIX_" is used.E
...