ETSI ETS 300 497-2 ed.1 (1996-08)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.DGLMVNDDigital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Test Case Library (TCL); Part 2: Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Portable radio Termination (PT)33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:ETS 300 497-2 Edition 1SIST ETS 300 497-2:1999en01-julij-1999SIST ETS 300 497-2:1999SLOVENSKI
STANDARD
EUROPEANETS 300 497-2TELECOMMUNICATIONAugust 1996STANDARDSource: ETSI TC-RESReference: DE/RES-03026-2ICS:33.020, 33.060.50Key words:Abstract Test Suites, DECT, GAPRadio Equipment and Systems (RES);Digital Enhanced Cordless Telecommunications (DECT);Common Interface (CI) Test Case Library (TCL);Part 2: Abstract Test Suite (ATS) for Medium Access Control(MAC) layer - Portable radio Termination (PT)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 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 1996. All rights reserved.SIST ETS 300 497-2:1999

Page 2ETS 300 497-2: August 1996Whilst 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 Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 497-2:1999

Page 3ETS 300 497-2: August 1996ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.103.1Definitions.103.2DECT abbreviations.103.3ISO 9646 abbreviations.104Abstract Test Method (ATM).114.1Description of ATM.114.2Test strategy.125Untestable Test Purposes (TPs).136ATS conventions (only applicable for PTC LT_TC).136.1Naming conventions.136.1.1Declarations part.136.1.1.1General.136.1.1.2Test suite operations definition.136.1.1.3Test suite parameter declarations.146.1.1.4Test case selection expression definition.146.1.1.5Test suite constant declarations.146.1.1.6Test suite variable declarations.146.1.1.7Test case variable declarations.146.1.1.8Timer declarations.156.1.1.9ASP type definitions.156.1.1.10PDU type definitions.156.1.1.11CM type definitions.156.1.1.12Alias definitions.156.1.2Constraints part.166.1.2.1General.166.1.3Dynamic part.166.1.3.1General.166.1.3.2Test Case (TC) identifier.166.1.3.3Test step identifier.176.1.3.4Default identifier.176.1.3.5Label identifier.176.1.3.6ATS abbreviations.176.2Implementation conventions.176.2.1Declaration part.176.2.2Constraint part.186.2.3Dynamic part.18Annex A (normative):Abstract Test Suite (ATS), PTC LT_TC.19A.1The machine processable ATS (TTCN.MP).19A.2The graphical ATS (TTCN.GR).19Annex B (normative):Specification of PTC LT_MAC.131B.1General requirements.131SIST ETS 300 497-2:1999

Page 4ETS 300 497-2: August 1996B.2Additional requirements.131Annex C (normative):Partial PIXIT proforma for DECT MAC.133C.1Identification summary.133C.2ATS summary.133C.3Test laboratory.133C.4Client identification.133C.5SUT.134C.6Protocol layer information.134C.6.1Protocol identification.134C.6.2IUT information.134Annex D (normative):Protocol Conformance Test Report (PCTR) Proforma for DECT MAC.137D.1Identification summary.137D.1.1Protocol conformance test report.137D.1.2IUT identification.137D.1.3Testing environment.138D.1.4Limits and reservation.138D.1.5Comments.138D.2IUT Conformance status.138D.3Static conformance summary.138D.4Dynamic conformance summary.139D.5Static conformance review report.139D.6Test campaign report.139D.7Observations.140Annex E (informative):Bibliography.141History.142SIST ETS 300 497-2:1999

Page 5ETS 300 497-2: August 1996ForewordThis European Telecommunication Standard (ETS) has been produced by the Radio Equipment andSystems (RES) Technical Committee of the European Telecommunications Standards Institute (ETSI).The DECT Test Specification multipart ETS comprises nine parts, as follows:Part 1:"Part 1: Test Suite Structure (TSS) and Test Purposes (TP) for Medium Access Control(MAC) layer".Part 2:"Part 2: Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Portableradio Termination (PT)".Part 3:"Part 3: Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Fixed radioTermination (FT)".Part 4:"Part 4: Test Suite Structure (TSS) and Test Purposes (TP) - Data Link Control (DLC) layer".Part 5:"Part 5: Abstract Test Suite (ATS) - Data Link Control (DLC) layer".Part 6:"Part 6: Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer - Portableradio Termination (PT)".Part 7:"Part 7: Abstract Test Suite (ATS) for Network (NWK) layer - Portable radio Termination(PT)".Part 8:"Part 8: Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer - Fixedradio Termination (FT)".Part 9:"Part 9: Abstract Test Suite (ATS) for Network (NWK) layer - Fixed radio Termination (FT)".Transposition datesDate of adoption of this ETS:16 August 1996Date of latest announcement of this ETS (doa):30 November 1996Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 May 1997Date of withdrawal of any conflicting National Standard (dow):31 May 1997SIST ETS 300 497-2:1999

Page 6ETS 300 497-2: August 1996Blank pageSIST ETS 300 497-2:1999

Page 7ETS 300 497-2: August 19961ScopeThis European Telecommunication Standard (ETS) contains the Abstract Test Suite (ATS) to test theDECT Portable Part (PP) Medium Access Control (MAC) layer.The objective of this test specification is to provide a basis for approval tests for DECT equipment giving ahigh probability of air interface inter-operability between different manufacturer's DECT equipment. Thistest specification contains the ATS specification for testing of the MAC layer at the PT.The ISO standard for the methodology of conformance testing (ISO/IEC 9646 [21] to [27]) as well as theETSI rules for conformance testing in ETS 300 406 [29] are used as the basis for the test methodology.Test specifications for the Physical Layer (PHL) are provided in other DECT ETSs.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 ofthis ATS.Annex D provides the Protocol Conformance Test Report (PCTR) Proforma of this ATS.2Normative referencesThis ETS incorporates, by dated or 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 175-1 (1992): "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common interface; Part 1: Overview".[2]ETS 300 175-2 (1992): "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common interface; Part 2: Physicallayer".[3]ETS 300 175-3 (1992): "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common interface; Part 3: Mediumaccess control layer".[4]ETS 300 175-4 (1992): "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common interface; Part 4: Data linkcontrol layer".[5]ETS 300 175-5 (1992): "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common interface; Part 5: Networklayer".[6]ETS 300 175-6 (1992): "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common interface; Part 6: Identitiesand addressing".[7]ETS 300 175-7 (1992): "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common interface; Part 7: Securityfeatures".[8]ETS 300 175-8 (1992): "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common interface; Part 8: Speechcoding and transmission".SIST ETS 300 497-2:1999

Page 8ETS 300 497-2: August 1996[9]ETS 300 175-9 (1992): "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common interface; Part 9: Publicaccess profile".[10]ETS 300 444: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Generic Access Profile (GAP)”.[11]ETS 300 370: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications/Global System for Mobile communications(DECT/GSM) inter-working profile; Access and mapping (Protocol/proceduredescription for 3,1 kHz speech service)".[12]ETS 300 434: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT) and Integrated Services Digital Network(ISDN) inter-working for end system configuration".[13]ETS 300 331: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); DECT Authentication Module (DAM)".[14]CCITT Recommendation G.726 (1991): "40, 32, 24, 16 kbit/s adaptivedifferential pulse code modulation (ADPCM)".[15.20]Reserved values.[21]ISO/IEC 9646-1 (1991): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 1:General concepts". (See also CCITT Recommendation X.290 (1991)).[22]ISO/IEC 9646-2 (1991): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 2:Abstract test suite specification". (See also CCITT Recommendation X.291(1991)).[23]ISO/IEC 9646-3 (1991): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 3:The tree and tabular combined notation". (See also CCITT RecommendationX.292 (1992)).[24]ISO/IEC 9646-4 (1991): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 4:Test realisation". (See also CCITT Recommendation X.292 (1992)).[25]ISO/IEC 9646-5 (1991): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 5:Requirements on test laboratories and clients for the conformance assessmentprocess". (See also CCITT Recommendation X.292 (1992)).[26]ISO/IEC 9646-6 (1991): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 6:Protocol profile test specification".[27]ISO/IEC 9646-7 (1991): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 7:Implementation conformance statement".[28]ISO 7498: "Information Processing Systems - Open Systems Interconnection -Basic Reference model".[29]ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocoland profile conformance testing specifications; Standardization methodology".SIST ETS 300 497-2:1999

Page 9ETS 300 497-2: August 1996[30]91/263/EEC: "Council Directive of 29 April 1991 on the approximation of thelaws of the Member states concerning telecommunications terminal equipment,including the mutual recognition of their conformity. (Terminal Directive)".[31.40]Reserved values.[41]I-ETS 300 176: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Approval test specification".[42]TBR 6: "Radio Equipment and Systems (RES); Digital European CordlessTelecommunications (DECT); General terminal attachment requirements".[43]TBR 10: "Radio Equipment and Systems (RES); Digital European CordlessTelecommunications (DECT); General terminal attachment requirements:Telephony applications".[44]TBR 11 (1992): "Radio Equipment and Systems (RES); Attachmentrequirements for terminal equipment for Digital European CordlessTelecommunications (DECT) Public Access Profile (PAP) applications".[45]ETS 300 323 (1994): "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Public Access Profile (PAP) testspecification".[46]ETS 300 476: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Common Interface (CI); ProtocolImplementation Conformance Statement (PICS) proforma".[47]ETS 300 497: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Common Interface (CI) Test CaseLibrary (TCL)".[48]ETS 300 474: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Generic Access Profile (GAP); Profilerequirement list and profile specific Implementation Conformance Statement(ICS) proforma".[49]ETS 300 494: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Generic Access Profile (GAP); ProfileTest Specification (PTS)".[50]TBR 22: "Radio Equipment and Systems (RES); Attachment requirements forterminal equipment for Digital Enhanced Cordless Telecommunications (DECT)Generic Access Profile (GAP) applications".SIST ETS 300 497-2:1999

Page 10ETS 300 497-2: August 19963Definitions and abbreviations3.1DefinitionsFor the purposes of this part of this ETS, the definitions given in ISO/IEC 9646-1 [21] and ETSIETS 300 175-1 [1] apply.3.2DECT abbreviationsFor the purpose of this part of this ETS, the following abbreviations apply:ACAuthentication CodeCCCall ControlCICommon InterfaceCLMSConnectionless Message Services (CL)CMCo-ordination MessageCOMSConnection Oriented Message Services (CO)CTSConformance Testing ServicesDECTDigital Enhanced Cordless TelecommunicationDLCData Link ControlDSAADECT Standard Authentication AlgorithmDSCADECT Standard Cipher Algorithm 1ISOInternational Organisation for StandardisationFTFixed radio TerminationIPUIInternational Portable User IdentityIPEIInternational Portable Equipment IdentityIWUInterworking UnitLCLink Control entityMACMedium Access ControlMEManagement EntityMMMobility ManagementNWKNetworkPAPPublic Access ProfilePARKPortable Access Rights KeyPHLPhysical LayerPTPortable radio TerminationRPNRadio Fixed Part NumberSAPService Access PointSARISecondary Access Rights IdentitySDUService Data UnitUAKUser Authentication Key3.3ISO 9646 abbreviationsFor the purposes of this ETS, the following ISO abbreviations apply:ASPAbstract Service PrimitiveATMAbstract Test MethodATSAbstract Test SuiteBIInvalid BehaviourBOInopportune BehaviourBVValid BehaviourCACapability testsCPCo-ordination PointIUTImplementation Under TestLTLower TesterMTCMain Test ComponentPCOPoint of Control and ObservationPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementsPIXITProtocol Implementation eXtra Information for TestingPTCParallel Test ComponentSUTSystem Under TestSIST ETS 300 497-2:1999

Page 11ETS 300 497-2: August 1996TPTest PurposeTSSTest Suite StructureTTCNTree and Tabular Combined NotationUTUpper Tester4Abstract Test Method (ATM)This clause describes the ATM used to test the DECT MAC layer protocol at the Portable radioTermination (PT).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 PCO for MAC Layer testing is located at the D-SAP between the MAC layerand the Physical layer. All test events at the PCO are specified in terms of PHL-ASPs (frame number parameter added).CP_TC:Co-ordination Point Test Case (CP_TC) is located between the MTC and PTCLT_TC in the test system. It is used for passing co-ordination messagesbetween these two testing functions.CP_MAC:Co-ordination Point MAC (CP_MAC) is located between the MTC and PTCLT_MAC in the test system. It is equivalent to the PCO used for DLC layertesting in part 6 of this ETS. All co-ordination messages at this CP are specifiedin terms of MAC-ASPs and DLC-PDUs.SIST ETS 300 497-2:1999

Page 12ETS 300 497-2: August 1996PTC LT_TC:the Lower Tester Parallel Test Component LT_TC (PTC LT_TC) is located inthe test system. It makes restricted use of the PCO by only observing the testevents in both directions. It assigns preliminary verdicts (the MTC assigns thefinal verdict).NOTE:This restricted use of the PCO is a non-ISO 9646-2 [22] application of the PCO.PTC LT_MAC:The Lower Tester Parallel Test Component LT_MAC (PTC LT_MAC) is locatedin the test system. It provides indirect control and observation of the IUT duringtest execution, via the underlying service-provider. It does not assign anyverdicts.MTC:The Main Test Component (MTC) is located in the test system. It is responsiblefor creating and terminating the PTCs, managing the co-ordination pointsCP_TC and CP_MAC, and computation of the final test case verdict.Upper layers:No explicit upper tester (UT) exists in the test system. However, the SUT (upperlayers) needs to carry out some UT functions to achieve some effects of test co-ordination procedures.The primitives used at the PCO (physical SAP - DSAP) are defined according to ETS 300 175-2 [2] clause7 and associated subclauses.The co-ordination messages used at CP_MAC co-ordination point are abstract primitives includingprotocol data units and frames. The abstract primitives (MAC ASPs) are defined according toETS 300 175-3 [3] clause 8 and associated subclauses. Two abstract primitives for starting and stoppingthe synchronisation between the main test component and the parallel test component LT_MAC areadded for the needs of the tester. The protocol data units (DLC C-plane PDUs) are defined according toETS 300 175-4 [4] clause 7 and associated subclauses. The frames (DLC U-plane frames) are definedaccording to ETS 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 Amendment1 of ISO 9646-3 [23]. The parallel test components PTC_TC and PTC_MAC are, however, seen as twoindependent entities. This means that there is no communication or synchronisation between the twoPTCs during the test.PTC_TC is specified in TTCN (see annex A). Since PTC_TC is only observing at the PCO, this ATS doesnot contain any send statements. Once the test purpose (TP) is fulfilled, the PTC_TC terminates, i.e. thereare no post ambles, unless required by the TP. No explicit co-ordination messages is exchanged atCP_TC. To simplify the TTCN test cases, the underlying service provider has been assigned the task offrame numbering. Consequently, a frame parameter has been added to some of the PHL-ASPs.The requirements for PTC_MAC (see annex B) are specified using ETS 300 474 [48].The Main Test Component (MTC) creates the two PTCs (using CREATE operation), stimulates thePTC_MAC (using MAC ASPs at CP_MAC) and then waits for the two PTCs to terminate (using the DONEevent). The final verdict is computed as follows:-a PASS is assigned if PTC_TC returns a PASS verdict and the expected event is received fromPTC_MAC at CP_MAC;-a FAIL verdict is assigned if PTC_TC returns a FAIL verdict independently of what is received fromPTC_MAC at CP_MAC;-an INCONC verdict is assigned if:PTC_TC returns an INCONC verdict and the expected event isreceived from PTC_MAC at CP_MAC, or returns a PASS verdict and an unexpected event isreceived from PTC_MAC at CP_MAC.SIST ETS 300 497-2:1999

Page 13ETS 300 497-2: August 19965Untestable Test Purposes (TPs)This clause gives a list of TPs which are not implemented in the ATS for PTC LT_TC (see annex A) dueto the chosen ATM or other restrictions.Table 1: Untestable TPsTest purposeReasonTP/DB/BV-00It is not possible to distinguish, without confusion, if the PT is unlocked or crashed.TP/DB/BV-02It is no possible to distinguish, without confusion, if the PT is unlocked or crashed.TP/PG/BV-00No procedure can be defined to verify that the FT manages correctly the pagingExtended Flag when 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 theconventions made for the development of the ATS. These conventions shall be considered during anylater maintenance or further development of the ATS.The ATS conventions contain two clauses, the naming conventions and the implementation conventions.The naming conventions describe the structure of the naming of all ATS elements. The implementationconventions describe the functional structure of the ATS.To define the ATS, the guidelines of the documents ETS 300 406 [29] and ETR 141 were considered.6.1Naming conventions6.1.1Declarations partThis subclause describes the naming conventions chosen for the elements of the ATS declarations part.6.1.1.1GeneralThe following general rules apply for the name giving in the declarations part. All type definitions (simpletype definitions, structured type definitions, ASP type definitions and PDU type definitions) shall be writtenin uppercase.All element names (structured type definition), parameter names (ASP type definition) and field names(PDU type definition) shall be written in lowercase.Predefined types (e.g. BITSTRING[8]) are never used in structured type definitions, ASP type definitionsor PDU type definitions. Simple types are used instead.All declarations in the test suite are listed in alphabetical order. A different order of listing should be usedfor only maintenance reasons.6.1.1.2Test suite operations definitionThe test suite operation identifiers are composed of substrings in lowercase letters, except for standardprefix "TSO_". Each substring is separated by an underscore character ("_").EXAMPLE:TSO_substringSIST ETS 300 497-2:1999

Page 14ETS 300 497-2: August 19966.1.1.3Test suite parameter declarationsThe test suite parameter identifiers are composed of substrings in lowercase letters, except for thestandard prefix "TSP_". Each substring is separated by an underscore character ("_").EXAMPLE 1:TSP_t_waitIf the test suite parameter references a PICS item, the letter "C" is added to the standard prefix.EXAMPLE 2:TSPC_extended_rf_carriersIf the test suite parameter references a PIXIT item, the letter "X" is added to the standard prefix.EXAMPLE 3:TSPX_pmid6.1.1.4Test case selection expression definitionThe test case selection expression identifiers are composed of substrings in lowercase letters, beginningwith 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_". Each substring is separated by an underscore character ("_").If the test suite constant represents a system parameter, the complete name defined in the protocol ETSis used.EXAMPLE:TSC_n2006.1.1.6Test suite variable declarationsThe test suite variable identifiers are composed of substrings in lowercase letters, except for the prefix"TSV_". Each substring is separated by an underscore character ("_").Complete names as defined in the protocol ETS 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_". Each substring is separated by an underscore character ("_").Complete names as defined in the protocol ETS are used.SIST ETS 300 497-2:1999

Page 15ETS 300 497-2: August 19966.1.1.8Timer declarationsTwo types of timers can be identified:1)standardised:-those defined in the protocol ETS, e.g. T201. They use exactly the same name as in theETS.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 standardised:-those not defined in the protocol ETS, i.e. for execution use, e.g. a timer waiting for aresponse. These timers begin with 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.9ASP type definitionsThe general conventions in subclause 6.1.1.1 applies.The identifier of an ASP type uses the same name as the name defined in the protocol ETS.EXAMPLE:PL_TX_REQ for an ASP containing a MAC layer PDU to the peer MAC layer(the IUT).6.1.1.10PDU type definitionsThe general conventions in subclause 6.1.1.1 applies.The PDU type identifier shall identify the related structure or type as defined in the protocol ETS.EXAMPLE:A_MT_BASIC_CONNECTION_CONTROL6.1.1.11CM type definitionsThe CM types are copied from the ASP types in ETS 300 497-5 [47] without modifications.6.1.1.12Alias definitionsAlias definitions are not used.SIST ETS 300 497-2:1999

Page 16ETS 300 497-2: August 19966.1.2Constraints partThis subclause describes the naming conventions chosen for the elements of the ATS constraints part.6.1.2.1GeneralConstraints shall be written with the first letter in uppercase, and the rest in lowercase.The first part of the constraint declaration identifier name is equivalent to the corresponding type identifierused in the declaration part. The second part of the name describes the content of this constraint.EXAMPLE:Declaration part:HEADER_FIELDConstraint part:Header_field_nt_no_bAll constraints shall be listed in alphabetical order. If a different order of listing is maintained, the reasonfor doing so shall be specified.6.1.3Dynamic partThis subclause describes the naming conventions used for the elements of the ATS dynamic part.6.1.3.1GeneralAll test cases shall be listed in the order in which they appear in the TSS and TP document.6.1.3.2Test Case (TC) identifierThe identifier of the test case is built in the same way as for the test purpose described inETS 300 497-1 [47], subclause 5.1.1, with the exception that "TP" is replaced by "TC_PT" ("PT" forPortable radio Termination). The identifier of a TC is built according to table 2.Table 2: TC naming conventionIdentifier:TC_PT___
=
functional moduleDBDown link BroadcastPGPaging servicesNBNon Continuous BroadcastDCDown link ConnectionlessUCUplink ConnectionlessBSBearer setupCMConnection modificationBHBearer handoverBRBearer releaseDTData transferLMLayer ManagementTMTest Messagesx
=
Type of testingCACapability TestsBVValid Behaviour TestsBIInvalid Behaviour Tests
=
sequential number(00-99)Test purpose NumberEXAMPLE:TP identifier:TP/BS/CA-00TC identifier:TC_PT_BS_CA_00SIST ETS 300 497-2:1999

Page 17ETS 300 497-2: August 19966.1.3.3Test step identifierThe test step identifier is built of substrings in lowercase letters, preceded by a string of uppercase letters.The substrings are joined by underscore characters. The first substring indicates the main function of thetest step; e.g. PR for preamble, PO for postamble, LTS for local tree and STP for general test step. Thesecond substring indicates the purpose of the step.EXAMPLE:PO_release_bearer6.1.3.4Default identifierThe default identifiers begin with the prefix "DF_", followed by a string in lowercase letters.6.1.3.5Label identifierThe identifiers in the label column is built according to table 3:Table 3: Naming convention for verdict assignment identifierIdentifier: