ETSI EN 300 497-3 V0.3.2 (1999-09)

Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Test Case Library (TCL); Part 3: Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Fixed radio Termination (FT)

REN/DECT-040131-3

Digitalne izboljšane brezvrvične telekomunikacije (DECT) – Skupni vmesnik (CI) – Knjižnica preskušalnih primerov (TCL) – 3. del: Abstraktni preskušalni niz (ATS) za krmiljenje dostopa do plasti prenosnega medija (MAC) – Fiksna radijska zaključitev (FT)

General Information

• Status: Published
• Publication Date: 06-Sep-1999
• Technical Committee: DECT 4 - DECT Testing aspects
• Current Stage: 12 - Completion
• Due Date: 30-Aug-1999
• Completion Date: 07-Sep-1999
• Mandate: T-292
• Ref Project: SIST EN 300 497-3 V0.3.2:2003 - Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Test Case Library (TCL); Part 3: Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Fixed radio Termination (FT)

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.LMVNDDigital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Test Case Library (TCL); Part 3: Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Fixed radio Termination (FT)33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:EN 300 497-3 Version 0.3.2SIST EN 300 497-3 V0.3.2:2003en01-december-2003SIST EN 300 497-3 V0.3.2:2003SLOVENSKI
STANDARD



SIST EN 300 497-3 V0.3.2:2003



ETSI EN 300 497-3 V0.3.2 (1999-09)European Standard (Telecommunications series)Digital Enhanced Cordless Telecommunications (DECT);Common Interface (CI); Test Case Library (TCL);Part 3: Abstract Test Suite (ATS) for Medium Access Control(MAC) layer - Fixed radio Termination (FT)SIST EN 300 497-3 V0.3.2:2003



ETSIETSI EN 300 497-3 V0.3.2 (1999-09)2ReferenceREN/DECT-040131-3 (4lor011c.PDF)KeywordsDECT, MAC, testing, terminal, ATS, TTCNETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: [phone]
Fax: [phone]Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/[e-mail] copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: [e-mail] NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1999.All rights reserved.SIST EN 300 497-3 V0.3.2:2003



ETSIETSI EN 300 497-3 V0.3.2 (1999-09)3ContentsIntellectual Property Rights.5Foreword.51Scope.62References.63Definitions and abbreviations.73.1Definitions.73.2Abbreviations.74Abstract Test Method (ATM).84.1Description of ATM.84.2Test strategy.95Untestable Test Purposes (TPs).106ATS Conventions (only applicable for PTC LT_TC).106.1Naming conventions.106.1.1Declarations part.106.1.1.1General.106.1.1.2Test suite operations definition.116.1.1.3Test suite parameter declarations.116.1.1.4Test case selection expression definition.116.1.1.5Test suite constant declarations.116.1.1.6Test suite variable declarations.116.1.1.7Test case variable declarations.116.1.1.8Timer declarations.126.1.1.9ASP type definitions.126.1.1.10PDU type definitions.126.1.1.11Co-ordination Message (CM) type definitions.126.1.1.12Alias definitions.126.1.2Constraints part.126.1.2AGeneral.126.1.3Dynamic part.136.1.3.1General.136.1.3.2Test Case identifier.136.1.3.3Test step identifier.136.1.3.4Default identifier.136.1.3.5Label identifier.136.1.3.6ATS abbreviations.146.2Implementation conventions.146.2.1Declaration part.146.2.2Constraint part.156.2.3Dynamic part.15SIST EN 300 497-3 V0.3.2:2003



ETSIETSI EN 300 497-3 V0.3.2 (1999-09)4Annex A (normative):Abstract test suite (ATS), PTC LT_TC.16A.1The TTCN Graphical form (TTCN.GR).16A.2The TTCN Machine Processable form (TTCN.MP).16Annex B (normative):Specification of PTC LT_MAC.17B.1General requirements.17B.2Additional requirements.17Annex C (normative):Partial PIXIT proforma for DECT MAC.18C.1Identification summary.18C.2ATS summary.18C.3Test laboratory.18C.4Client identification.18C.5SUT.19C.6Protocol layer information.19C.6.1Protocol identification.19C.6.2IUT information.19Annex D (normative):Protocol Conformance Test Report (PCTR) Proforma For DECTMAC.21D.1Identification summary.21D.1.1Protocol conformance test report.21D.1.2IUT identification.21D.1.3Testing environment.21D.1.4Limits and reservation.22D.1.5Comments.22D.2IUT Conformance status.22D.3Static conformance summary.22D.4Dynamic conformance summary.23D.5Static conformance review report.23D.6Test campaign report.24D.7Observations.24Bibliography.25History.26SIST EN 300 497-3 V0.3.2:2003



ETSIETSI EN 300 497-3 V0.3.2 (1999-09)5Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server(http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Project Digital Enhanced CordlessTelecommunications (DECT).The present document is part 3 of a multi-part EN covering the Common Interface (CI) Test Case Library (TCL), asidentified below:Part 1:"Test Suite Structure (TSS) and Test Purposes (TP) for Medium Access Control (MAC) layer";Part 2:"Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Portable radio Termination (PT)";Part 3:"Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Fixed radio Termination(FT)";Part 4:"Test Suite Structure (TSS) and Test Purposes (TP) - Data Link Control (DLC) layer";Part 5:"Abstract Test Suite (ATS) - Data Link Control (DLC) layer";Part 6:"Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer - Portable radio Termination(PT)";Part 7:"Abstract Test Suite (ATS) for Network (NWK) layer - Portable radio Termination (PT)";Part 8:"Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer - Fixed radio Termination(FT)";Part 9:"Abstract Test Suite (ATS) for Network (NWK) layer - Fixed radio Termination (FT)".National transposition datesDate of adoption of this EN:27 August 1999Date of latest announcement of this EN (doa):30 November 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 May 2000Date of withdrawal of any conflicting National Standard (dow):31 May 2000SIST EN 300 497-3 V0.3.2:2003



ETSIETSI EN 300 497-3 V0.3.2 (1999-09)61ScopeThe present document contains the Abstract Test Suite (ATS) to test the DECT FP MAC layer.The objective of this test specification is to provide a basis for approval tests for DECT equipment giving a highprobability of air interface inter-operability between different manufacturer's DECT equipment. This part contains theATS specification for testing of the MAC layer at the FT.The ISO standard for the methodology of conformance testing (ISO/IEC 9646 Parts 1 to 7 [10] to [16]) as well as theETSI rules for conformance testing (ETS 300 406 [7]) are used as basis for the test methodology.Test specifications for the Physical Layer (PHL) are provided in other DECT standards.Annex A provides the Tree and Tabular Combined Notation (TTCN) part of this ATS.Annex B provides the specification of the parallel test component LT_MAC.Annex C provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of this ATS.Annex D provides the Protocol Conformance Test Report (PCTR) Proforma of this ATS.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.·References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.·For a specific reference, subsequent revisions do not apply.·For a non-specific reference, the latest version applies.·A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]EN 300 175-1: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 1: Overview".[2]EN 300 175-2: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 2: Physical Layer (PHL)".[3]EN 300 175-3: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 3: Medium Access Control (MAC) layer".[4]EN 300 175-4: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 4: Data Link Control (DLC) layer".[5]EN 300 175-6: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 6: Identities and addressing".[6]EN 300 175-8: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 8: Speech coding and transmission".[7]ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile conformancetesting specifications; Standardization methodology".[8]ETS 300 474 Parts 1 and 2: "Digital Enhanced Cordless Telecommunications (DECT); GenericAccess Profile (GAP); Profile requirement list and profile specific Implementation ConformanceStatement (ICS) proforma; Part 1: Portable radio Termination (PT) and Part 2: Fixed radioTermination (FT)".SIST EN 300 497-3 V0.3.2:2003



ETSIETSI EN 300 497-3 V0.3.2 (1999-09)7[9]EN 300 497-1: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI)Test Case Library (TCL); Part 1: Test Suite Structure (TSS) and Test Purposes (TP) for MediumAccess Control (MAC) layer".[10]ISO/IEC 9646-1: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 1: General concepts".[11]ISO/IEC 9646-2: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 2: Abstract Test Suite Specification".[12]ISO/IEC 9646-3: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 3: The Tree and Tabular Combined Notation (TTCN)".[13]ISO/IEC 9646-4: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 4: Test realization".[14]ISO/IEC 9646-5: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 5: Requirements on test laboratories and clients for theconformance assessment process".[15]ISO/IEC 9646-6: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 6: Protocol profile test specification".[16]ISO/IEC 9646-7: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 7: Implementation Conformance Statements".[17]ETR 141: "Methods for Testing and Specification (MTS); Protocol and profile conformancetesting specifications; The Tree and Tabular Combined Notation (TTCN) style guide".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the terms and definitions given in ISO/IEC 9646-1 [10] and EN 300 175-1 [1]apply.3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:ASPAbstract Service PrimitiveATMAbstract Test MethodATSAbstract Test SuiteBIInvalid BehaviourBVValid BehaviourCACapability testsCICommon InterfaceCMCo-ordination MessageCPCo-ordination PointDECTDigital Enhanced Cordless TelecommunicationsDLCData Link ControlFTFixed radio TerminationIUTImplementation Under TestLTLower TesterMACMedium Access ControlMTCMain Test ComponentNWKNetworkPCOPoint of Control and ObservationPDUProtocol Data UnitSIST EN 300 497-3 V0.3.2:2003



ETSIETSI EN 300 497-3 V0.3.2 (1999-09)8PHLPhysical LayerPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation Extra Information for TestingPTPortable radio TerminationPTCParallel Test ComponentSAPService Access PointSARISecondary Access Rights IdentitySUTSystem Under TestTPTest PurposeTSSTest Suite StructureTTCNTree and Tabular Combined NotationUTUpper Tester4Abstract Test Method (ATM)Clause 4 describes the ATM used to test the DECT MAC layer protocol at the Fixed radio Termination (FT).4.1Description of ATMPTCLT_TCPTCLT_MACMain Test Component(MTC)IUT(MAC)PCOMAC-PDUsUpperlayersDLC-PDUsMAC-ASPsDLC-PDUsPHL Service providerLower TesterUpper TesterTest SystemSystem Under TestCoordinationmessagesPHL-ASPswith frame numberCP_TCCP_MACFigure 1: Remote test method, embedded variantA single-party testing concept is used, which consists of the following abstract testing functions:PCO:the Point of Control and Observation (PCO) for MAC Layer testing is located at the D-ServiceAccess Point (D-SAP) between the MAC layer and the Physical layer. All test events at the PCOare specified in terms of Physical Layer Abstract Service Primitives (PHL-ASPs) (frame numberparameter added).SIST EN 300 497-3 V0.3.2:2003



ETSIETSI EN 300 497-3 V0.3.2 (1999-09)9CP_TC:Co-ordination Point Test Case (CP_TC) is located between the Main Test Component (MTC) andParallel Test Component (PTC) LT_TC in the test system. It is used for passing co-ordinationmessages between these two testing functions.CP_MAC:Co-ordination Point MAC (CP_MAC) is located between the MTC and PTC LT_MAC in the testsystem. It is equivalent to the PCO used for Data Link Control (DLC) layer testing in part 6 of thepresent document. All co-ordination messages at this CP are specified in terms of MAC-ASPs andDLC Protocol Data Units (DLC-PDUs).PTC LT_TC:the Lower Tester Parallel Test Component LT_TC (PTC LT_TC) is located in the test system. Itmakes restricted use of the PCO by only observing the test events in both directions. It assignspreliminary verdicts (the MTC assigns the final verdict).NOTE:This restricted use of the PCO is a non-ISO/IEC 9646-2 [11] application of the PCO.PTC LT_MAC:the Lower Tester Parallel Test Component LT_MAC (PTC LT_MAC) is located in the test system.It provides indirect control and observation of the Implementation Under Test (IUT) during testexecution, via the underlying service-provider. It does not assign any verdicts.MTC:the Main Test Component (MTC) is located in the test system. It is responsible for creating andterminating the PTCs, managing the co-ordination points CP_TC and CP_MAC, and computationof the final test case verdict.Upper layers:no explicit Upper Tester (UT) exists in the test system. However, the System Under Test (SUT)(upper layers) needs to carry out some UT functions to achieve some effects of test co-ordinationprocedures.The primitives used at the PCO (physical SAP - DSAP) are defined according to EN 300 175-2 [2], clause 7 andassociated subclauses.The co-ordination messages used at CP_MAC co-ordination point are abstract primitives including protocol data unitsand frames. The abstract primitives (MAC ASPs) are defined according to EN 300 175-3 [3], clause 8 and associatedsubclauses. Two abstract primitives for starting and stopping the synchronization between the main test component andthe parallel test component LT_MAC are added for the needs of the tester. The protocol data units (DLC C-plane PDUs)are defined according to EN 300 175-4 [4], clause 7 and associated subclauses. The frames (DLC U-plane frames) aredefined according to EN 300 175-4 [4], clause 12 and associated subclauses.4.2Test strategyThe ATM defined in subclause 4.1 requires the use of concurrent TTCN, which is specified in Amendment 1 ofISO/IEC 9646-3 [12]. The parallel test components PTC_TC and PTC_MAC is, however, seen as two independententities. This means that there is no communication or synchronization between the two PTCs during the test.PTC_TC is specified in TTCN (annex A). Since PTC_TC is only observing at the PCO, this ATS does not contain anysend statements. Once the Test Purposes (TP) are fulfilled, the PTC_TC terminates, i.e. there are no postambles, unlessrequired by the TP. No explicit co-ordination messages is exchanged at CP_TC. To simplify the TTCN test cases, theunderlying service provider has been assigned the task of frame numbering. Consequently, a frame parameter has beenadded to some of the PHL-ASPs.The requirements for PTC_MAC (annex B) are specified using ETS 300 474 [8].SIST EN 300 497-3 V0.3.2:2003



ETSIETSI EN 300 497-3 V0.3.2 (1999-09)10The Main Test Component (MTC) creates the two PTCs (using CREATE operation), stimulates the PTC_MAC (usingMAC ASPs at CP_MAC) and then waits for the two PTCs to terminate (using the DONE event). The final verdict iscomputed as follows:-a PASS is assigned if PTC_TC returns a PASS verdict and the expected event is received from PTC_MAC atCP_MAC;-a FAIL verdict is assigned if PTC_TC returns a FAIL verdict independently of what is received from PTC_MACat CP_MAC;-an INCONC verdict is assigned if PTC_TC returns an INCONC verdict and the expected event is received fromPTC_MAC at CP_MAC; or returns a PASS verdict and an unexpected event is received from PTC_MAC atCP_MAC.5Untestable Test Purposes (TPs)Clause 5 gives a list of TPs which are not implemented in the ATS for PTC LT_TC (annex A) due to the chosen abstracttest method or other restrictions.Table 1: Untestable TPsTest purposeReasonTP/PG/BV-00No procedure can be defined to verify that the FT manages correctly the paging Extended Flagwhen it transmit pages.6ATS Conventions (only applicable for PTC LT_TC)The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventionsmade for the development of the ATS. These conventions shall be considered during any later maintenance or furtherdevelopment of the ATS.The ATS conventions contain two clauses, the naming conventions and the implementation conventions. The namingconventions describe the structure of the naming of all ATS elements. The implementation conventions describe thefunctional structure of the ATS.To define the ATS, the guidelines of the documents ETS 300 406 [7] and ETR 141 [17] were considered.6.1Naming conventions6.1.1Declarations partSubclause 6.1.1 describes the naming conventions chosen for the elements of the ATS declarations part.6.1.1.1GeneralThe following general rules apply for name giving in the declarations part. All type definitions (Simple type definitions,Structured type definitions, ASP type definitions and Protocol Data Unit (PDU) type definitions) shall be written inuppercase.All element names (Structured type definition), parameter names (ASP type definition) and field names (PDU typedefinition) shall be written in lowercase.Predefined types (e.g. BITSTRING[8]) are never used in structured type definitions, ASP type definitions or PDU typedefinitions. Simple types are used instead.SIST EN 300 497-3 V0.3.2:2003



ETSIETSI EN 300 497-3 V0.3.2 (1999-09)11All declarations in the test suite are listed in alphabetical order. A different order of listing should be used for onlymaintenance reason.6.1.1.2Test suite operations definitionThe test suite operation identifiers are composed of substrings in lowercase letters, except for standard prefix "TSO_".Each substring is separated by an underscore character ("_").EXAMPLE:TSO_substring.6.1.1.3Test suite parameter declarationsThe test suite parameter identifiers are composed of substrings in lowercase letters, except for the standard prefix"TSP_". Each substring is separated by an underscore character ("_").EXAMPLE 1:TSP_t_wait.If the test suite parameter references a Protocol Implementation Conformance Statement (PICS) item, the letter "C" isadded to the standard prefix.EXAMPLE 2:TSPC_extended_rf_carriers.If the test suite parameter references a PIXIT item, the letter "X" is added to the standard prefix.EXAMPLE 3:TSPX_pmid.Complete names as defined in the specifications are used.6.1.1.4Test case selection expression definitionThe test case selection expression identifiers are composed of substrings in lowercase letters, beginning with the prefix"TCS_". Each substring is separated by an underscore character ("_").6.1.1.5Test suite constant declarationsThe test suite constant identifiers are composed of substrings in lowercase letters, except for the prefix "TSC_". Eachsubstring is separated by an underscore character ("_").If the test suite constant represents a system parameter, the complete name defined in the protocol standard is used.EXAMPLE:TSC_n200.6.1.1.6Test suite variable declarationsThe test suite variable identifiers are composed of substrings in lowercase letters, except for the prefix "TSV_". Eachsubstring is separated by an underscore character ("_").Complete names as defined in the protocol standard are used.6.1.1.7Test case variable declarationsThe test case variable identifiers are composed of substrings in lowercase letters, except for the prefix "TCV_". Eachsubstring is separated by an underscore character ("_").Complete names as defined in the protocol standard are used.SIST EN 300 497-3 V0.3.2:2003



ETSIETSI EN 300 497-3 V0.3.2 (1999-09)126.1.1.8Timer declarationsTwo type of timers can be identified:1)standardized:-those defined in the protocol standard, e.g. T201. They use exactly the same name as in the standard;-as there is a tolerance margin accepted for these timers, three values are needed:-the maximum value allowed, which will use the suffix "_max";-the minimum value allowed, which will use the suffix "_min";-the value actually implemented, with no suffix.EXAMPLE 1:T201_max, T201_min, and T201.2)not standardized:-those not defined in the protocol standard, i.e. for execution use, e.g. a timer waiting for a response. Thesetimers begin with the prefix "T_", followed by a string in lowercase letters.EXAMPLE 2:T_resp represents a timer for controll
...