SIST EN 300 497-5 V0.3.0:2003

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Test Case Library (TCL); Part 5: Abstract Test Suite (ATS) - Data Link Control (DLC) layer33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:EN 300 497-5 Version 0.3.0SIST EN 300 497-5 V0.3.0:2003en01-december-2003SIST EN 300 497-5 V0.3.0:2003SLOVENSKI
STANDARD
ETSIETSI EN 300 497-5 V0.3.0 (1999-10)2ReferenceREN/DECT-040131-5 (4lp90100.PDF)KeywordsATS, DECT, testing, layer 2, TTCNETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frIndividual copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: editor@etsi.frImportant noticeThis ETSI deliverable may be made available in more than one electronic version or in print. In any case of existing orperceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).In case of dispute, the reference should be the printing on ETSI printers of the PDF version kept on a specific networkdrive within ETSI Secretariat.Copyright 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-5 V0.3.0:2003

ETSIETSI EN 300 497-5 V0.3.0 (1999-10)3ContentsIntellectual Property Rights.5Foreword.51Scope.62References.63Definitions and abbreviations.73.1Definitions.73.2Abbreviations.74Abstract Test Method (ATM).85Untestable Test Purposes (TP).96ATS Conventions.96.1Naming conventions.96.1.1Declarations part.96.1.1.1Test suite type and structured type definitions.96.1.1.2Test suite operations definitions.96.1.1.3Test suite parameter declarations.106.1.1.4Test case selection expression definitions.106.1.1.5Test suite constant declarations.106.1.1.6Test suite variable declarations.106.1.1.7Test case variable declarations.106.1.1.8PCO declarations.106.1.1.9Timer declarations.116.1.1.10ASP type definitions.116.1.1.11PDU type definitions.116.1.1.12Alias definitions.116.1.2Constraints part.126.1.3Dynamic part.126.1.3.1Test Case identifier.126.1.3.2Test step identifier.126.1.3.3Default identifier.126.1.3.4General aspects.136.1.3.5ATS abbreviations.136.2Implementation conventions.136.2.1Declaration part.136.2.2Constraint part.146.2.3Dynamic part.146.2.4Documentation.14SIST EN 300 497-5 V0.3.0:2003

ETSIETSI EN 300 497-5 V0.3.0 (1999-10)47Test case and test purpose mapping.15Annex A (normative):ATS for DECT DLC.16A.1The TTCN Graphical form (TTCN.GR).16A.2The TTCN Machine Processable form (TTCN.MP).16Annex B (normative):Partial PIXIT proforma for DECT DLC.17B.1Identification summary.17B.2ATS summary.17B.3Test laboratory.17B.4Client identification.17B.5SUT.18B.6Protocol layer information.18B.6.1Protocol identification.18B.6.2IUT information.18B.6.2.1General configuration.18B.6.2.2Parameter values.19B.6.2.3Timer values.19B.6.2.4Network parameter values.19B.6.3Procedural Information.20B.6.3.1Class U procedural information.20B.6.3.2Class A procedural information.21B.6.3.3Paging procedural information.21B.6.3.4Class 0 procedural information.22B.6.3.5Class 1 procedural information.22Annex C (normative):Protocol Conformance Test Report (PCTR) proforma for DECTDLC.23C.1Identification summary.23C.1.1Protocol conformance test report.23C.1.2IUT identification.23C.1.3Testing environment.23C.1.4Limits and reservation.24C.1.5Comments.24C.2IUT conformance status.24C.3Static conformance summary.24C.4Dynamic conformance summary.25C.5Static conformance review report.25C.6Test campaign report.26C.7Observations.27Bibliography.28History.29SIST EN 300 497-5 V0.3.0:2003

ETSIETSI EN 300 497-5 V0.3.0 (1999-10)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 5 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:17 September 1999Date of latest announcement of the present document (doa):31 December 1999Date of latest publication of new National Standardor endorsement of the present document (dop/e):30 June 2000Date of withdrawal of any conflicting National Standard (dow):30 June 2000SIST EN 300 497-5 V0.3.0:2003

ETSIETSI EN 300 497-5 V0.3.0 (1999-10)61ScopeThe present document contains the Abstract Test Suite (ATS) to test the Digital Enhanced CordlessTelecommunications (DECT) Data Link Control (DLC) 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.The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [7], ISO/IEC 9646-2 [8],ISO/IEC 9646-3 [9] and ISO/IEC 9646-5 [10]) as well as the ETSI rules for conformance testing (ETS 300 406 [6] andETR 141 [13]) are used as basis for the test methodology.Test specifications for the Physical Layer (PHL), Medium Access Control (MAC) layer, and Network (NWK) layer areprovided in other the DECT standards.Annex A provides the Tree and Tabular Combined Notation (TTCN) part of this ATS.Annex B provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of this ATS.Annex C 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-3: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 3: Medium Access Control (MAC) layer".[3]EN 300 175-4: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 4: Data Link Control (DLC) layer".[4]EN 300 175-6: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 6: Identities and addressing".[5]EN 300 175-7: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 7: Security features".[6]ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile conformancetesting specifications; Standardization methodology".[7]ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testingmethodology and framework - Part 1: General concepts".[8]ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testingmethodology and framework - Part 2: Abstract Test Suite Specification".[9]ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testingmethodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".SIST EN 300 497-5 V0.3.0:2003

ETSIETSI EN 300 497-5 V0.3.0 (1999-10)7[10]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".[11]ISO/IEC 9646-6: "Information technology - Open Systems Interconnection - Conformance testingmethodology and framework - Part 6: Protocol Profile Test Specification".[12]ISO 7498: "Information Processing Systems - Open Systems Interconnection - Basic Referencemodel".[13]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 definitions given in ISO/IEC 9646-1 [7], ISO/IEC 9646-2 [8],ISO/IEC 9646-5 [10], ISO 7498 [12], EN 300 175-1 [1], EN 300 175-4 [3], EN 300 175-6 [4] and EN 300 175-7 [5]apply.3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:ASPAbstract Service PrimitiveBIInvalid BehaviourBOInopportune BehaviourBVValid BehaviourCACapability testsDECTDigital Enhanced Cordless TelecommunicationsDLCData Link ControlFPFixed PartFTFixed radio TerminationIUTImplementation Under TestLTLower TesterMACMedium Access ControlMSAPMAC Service Access PointNWKNetworkPCOPoint of Control and ObservationPDUProtocol Data UnitPHLPhysical LayerPICSProtocol Implementation Conformance StatementsPIXITProtocol Implementation Extra Information for TestingPMIDPortable Part MAC IdentityPPPortable PartPTPortable radio TerminationSAPService Access PointSUTSystem Under TestTCTest CaseTDMATime Division Multiple AccessTPTest PurposesUSAPUpper Service Access PointUTUpper TesterSIST EN 300 497-5 V0.3.0:2003

ETSIETSI EN 300 497-5 V0.3.0 (1999-10)84Abstract Test Method (ATM)This clause describes the ATM used for testing the DECT DLC protocol. It is the embedded variant of Remote Single(RSE) layer test method. The RSE test method has been selected, because:-this test method implies no specific requirements from the IUT;-the Upper Service Access Point (USAP) of the IUT cannot be directly observed;-the variety of the possible DECT implementations is a serious technical obstacle for the adoption of a differentATM;-this test method places the minimum limitations in the realization of conformance testing.The embedded variant of the remote test method provides sufficient control of the IUT DLC behaviour, through NWKlayer messages conveyed by DLC frames.Test SystemSUTUpperLayersIUTDECT DLC DECTNWK ?MAC ASPs!MAC ASPsLTDLC-PDUsin ASPs withMCEI and if necessary Service TypeMSAP -PCOFragmentationRecombinationSubset of Lc entityand FBx entitiesMAC-CO-DATA primitivesNWK-PDUsFor implicit test coordinationDECT PHL and radio communicationDECT MAC layerDECT MAC layerFigure 1: RS test Method embedded variantLT:A Lower Tester (LT) is located in a remote DECT test system. It controls and observes thebehaviour of the IUT.MSAP:MAC Service Access Point - A unique MSAP is defined at the DECT interface and used toexchange service data of the DLC protocol. To avoid the complexity of data fragmentation andrecombination testing, the Service Access Point (SAP) is defined below this functions of the DLClayer.PCO:The PCO for DLC layer testing is located on the MSAP. All test events at the PCO are specified interms of MAC Abstract Service Primitives (ASPs) and DLC layer Protocol Data Units (PDUs).Notional UT:No explicit upper tester (UT) exists in the system under test. Nevertheless, some network messagesare sent to the SUT for the need of the co-ordination procedures. The network layer of the SUT isused as a notional UT as defined in ISO 9646.SIST EN 300 497-5 V0.3.0:2003

ETSIETSI EN 300 497-5 V0.3.0 (1999-10)9The MSAP primitives are defined according to EN 300 175-3 [2] clause 8 and associated subclauses.5Untestable Test Purposes (TP)Due to the ATMs chosen for this ATS or other restrictions, the test purposes in table 1 have been identified as being inthe untestable category, and therefore have not been derived into final test case:Table 1: Untestable TPTest purposeReasonTPUV_000No procedure can be defined to determine if, after receiving the first UI frame, the IUTconsiders the class U link as established. It is an internal state of the DLC layer of the IUT.TPUV_001No procedure can be defined to determine if, after receiving an upward release, the IUTconsiders the class U link as released. It is an internal state of the DLC layer of the IUT.TPLC_002Prioritized queuing of broadcast message between normal and expedited data is not testable. Itis very difficult to define a procedure in the IUT to force it, to transmit normal and expediteddata in a sufficient short time. It is, also, very difficult for the tester to transmit normal andexpedited data in sufficient short time and to define a procedure to verify the correct order ofthe reception in the IUT.6ATS ConventionsThis clause describes the conventions applied to define the ATS and gives the naming conventions chosen for thedifferent elements of the ATS.The ATS conventions are intended to give a better understanding of the ATS but they describe also the conventionsmade for the development of the ATS, thus for any later maintenance purposes or further development of the ATS theconventions described in this clause shall be considered.The ATS conventions contain two subclauses, 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.6.1Naming conventions6.1.1Declarations partThis subclause describes the naming conventions chosen for the elements of the ATS declarations part.6.1.1.1Test suite type and structured type definitionsThe test suite type and test suite structured type identifiers describe the information elements, and are written inuppercase:EXAMPLE:PROTOCOL_DISCRIMINATOR simple type.FILLSTRING structured type.6.1.1.2Test suite operations definitionsThe test suite operation identifiers are composed of string in lowercase letters starting by the uppercase string "TSO_".EXAMPLE:TSO_compute _checksum.SIST EN 300 497-5 V0.3.0:2003

ETSIETSI EN 300 497-5 V0.3.0 (1999-10)106.1.1.3Test suite parameter declarationsThe test suite parameter identifiers are composed of string in lowercase letters starting by the uppercase string "TSP_".EXAMPLE 1:TSP_window_size.If the test suite parameter references a PICS item, the letter "C" is added to the standard prefix.EXAMPLE 2:TSPC_pics_item_s23.If the test suite parameter references a PIXIT item, the letter "X" is added to the standard prefix.EXAMPLE 3:TSPX_pixit_item_2.Complete names as defined in the specifications are used.6.1.1.4Test case selection expression definitionsThe naming conventions for the test case selection expression definitions use free text starting with an uppercase letter.The name of the expression shall explain clearly the selection rule. The test case selection expressions are logicalcombinations of the test suite parameters definitions.Certain test cases are selected only when the IUT is a FT part or a PT part. Therefore, to cover all test cases applicableto the implementation, it is necessary to change the relevant test suite parameter for running the desired test cases.6.1.1.5Test suite constant declarationsThe test suite constant identifiers are composed of string in lowercase letters starting by the uppercase string "TSC_".EXAMPLE:TSC_retry.Complete names as defined in the specifications are used.6.1.1.6Test suite variable declarationsThe test suite variable identifiers are composed of string in lowercase letters starting by the uppercase string "TSV_".EXAMPLE 1:TSV_count.Exception: If the test suite variable represents a system parameter or value, the name defined in the specifications isused.EXAMPLE 2:VR,VS.6.1.1.7Test case variable declarationsThe test case variable identifiers are composed of string in lowercase letters starting by the uppercase string "TCV_".EXAMPLE:TCV_cr_value.6.1.1.8PCO declarationsThe point of control and observation identifiers are composed of two or four capital letters, beginning with "L", as thereare only LTs.EXAMPLE:LMAC represents a PCO on MAC interface as LT in the test equipment.LDLC represents a PCO on DLC interface as LT in the test equipment.SIST EN 300 497-5 V0.3.0:2003

ETSIETSI EN 300 497-5 V0.3.0 (1999-10)116.1.1.9Timer declarationsTwo kinds of timers can be distinguished:1)standardized:Those defined in the standard, e.g. DL_04, use exactly the same name as in the standard, beginning with a capital"T".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:TDL_04_max, TDL_04_min, and TDL_04.2)not standardized:Those not defined in the standard, i.e. for execution use, e. g. a timer waiting for a response. These timers beginwith the prefix "T_", followed by a string in lowercase letters.EXAMPLE 2:T_resp represents a timer for controlling the response time of the IUT.6.1.1.10ASP type definitionsThe identifier of an ASP uses exactly the nearest name as the name defined in the specifications. It is written inuppercases, finishing by an underscore character ("_"), and three capital letters indicating whether it is a request, anindication, a response or a confirmation primitive.EXAMPLE:DL_RELEASE_REQ for an ASP containing a layer 3 release request passed to layer 2;MAC_DATA_REQ for an ASP containing a layer 2b PDU passed to layer 2a.6.1.1.11PDU type definitionsThe identifier of a PDU is given in a string in uppercase letters, which represents the layer message.EXAMPLE 1:RR for the Receive Ready layer 2 message;DISCONNECT for the DISCONNECT layer 3 message.Where the message is a composite word, an underscore character ("_") appears in the string.EXAMPLE 2:RELEASE_COMPLETE is the RELEASE COMPLETE layer 3 message.6.1.1.12Alias definitionsThese are used to make the sending and receiving of PDUs within ASPs more understandable when writing the dynamicpart of the test suite. This is done by giving the ASP an alias. The alias name indicates the PDU carried by the ASP andwhether it is sent or received by the tester.No alias are used in the test suite.SIST EN 300 497-5 V0.3.0:2003

ETSIETSI EN 300 497-5 V0.3.0 (1999-10)126.1.2Constraints partThis subclause describes the naming conventions chosen for the elements of the ATS constraints part.Constraint identifiers commence with uppercase. The remaining part of the Id name is written in lowercase.Identifier names of elements concerning the same subject have equivalent names in the declaration and the constraintpart:-Declaration Part:CC_SETUP;-Constraint Part:Cc_setup.The name of the modified constraint describes the particularity of the modified constraint:EXAMPLE:Cc_setup_mand_only (modified Cc_setup with only the mandatory Information Elements).If formal parameter lists are used, the variable names are written in lowercase. The variable name is the same as thename of the element it is representing.6.1.3Dynamic partThis subclause describes the naming conventions chosen for the elements of the ATS dynamic part.6.1.3.1Test Case identifierThe identifier of a test case is built according to table 2.Table 2: Test Case (TC) naming conventionIdentifier: TC--x-= functional moduleUControl plane Class U servicesAControl plane Class A servicesBControl plane Class B servicesLControl plane Broadcast services0User plane transmission Class 01User plane transmission Class 12User plane transmission Class 23User plane transmission Class 3x= Type of testingCACA, Capability testsBVBV, Valid Behaviour testsBOBO, Inopportune Behaviour testsBIBI, Invalid Behaviour tests= sequential number(000-999)test case Number6.1.3.2Test step identifierThe test step identifier is built with a string of lowercase letters leaded by a string of capital letter and joined by anunderscore character. The first string indicates the main function of the test step; e.g. PR for preamble, PO forpostamble, LTS for local tree name and STP for general step. The second string indicates the meaning of the step.EXAMPLES:PR_name;PO_name;LTS_name;STP_name.6.1.3.3Default identifierThe Default identifiers begin with the prefix "DF_", followed by a string in lowercase letters.SIST EN 300 497-5 V0.3.0:2003

ETSIETSI EN 300 497-5 V0.3.0 (1999-10)136.1.3.4General aspectsAll verdict assignments are labelled. To allow an exact identification in which table the verdict was assigned, thefollowing name convention is applied:TBtest Body;DFDefault;EHError handling test steps;POPOstamble;PRPReamble;TStest step.6.1.3.5ATS abbreviationsThese abbreviations are used to shorten identifier names:addraddress;ackacknowledgement;caucause;cccall control;chnchannel;estestablish;indindication;metymessage type;modmodified;parparameter;pdprotocol discriminator;reqrequest;rspresponse.6.2Implementation conventions6.2.1Declaration partThe comment line of single element TTCN tables (e.g. test suite constants) is used to give a reference where the formatand content of the element is described in the relevant protocol specifications. Any particularity of the element format orcontent is described in the comment line.The comment line in the header of multi element TTCN tables (e.g. ASPs) is used to reference to the protocolspecification.The detailed comments are used to describe any par
...