SIST ETS 300 494-3:1999

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile (GAP); Profile Test Specification (PTS); Part 3: Profile Specific Test Specification (PSTS) - Fixed radio Termination (FT)33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:ETS 300 494-3 E13SIST ETS 300 494-3:1999en01MDQXDU-19993SIST ETS 300 494-3:1999SLOVENSKI
STANDARD
EUROPEANETS 300 494-3TELECOMMUNICATIONAugust 1996STANDARDSource: ETSI TC-RESReference: DE/RES-03040-3ICS:33.020, 33.060.50Key words:DECT, GAP, testingRadio Equipment and Systems (RES);Digital Enhanced Cordless Telecommunications (DECT);Generic Access Profile (GAP);Profile Test Specification (PTS);Part 3: Profile Specific Test Specification (PSTS)- Fixed radio Termination (FT)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 494-3:1999

Page 2ETS 300 494-3: 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 494-3:1999

Page 3ETS 300 494-3: August 1996ContentsForeword.71Scope.92Normative references.93Definitions and abbreviations.123.1Definitions.123.2Abbreviations.124Relevant test cases list.134.1Network (NWK) layer.134.1.1Test suite structure.134.1.2Test case index.154.2Data Link Control (DLC) layer.194.2.1Test suite structure.194.2.2Test case index.204.3Medium Access Control (MAC) layer.214.3.1Test suite structure.224.3.2Test case index.244.4Physical (PH) layer.254.4.1Manufacturer declarations.254.4.2Normal Transmitted Power (NTP).254.4.2.1Verdict criteria for IUTs with an integral antenna.254.4.2.2Verdict criteria for IUTs with external antennaconnection(s).254.4.3RFP radio receiver sensitivity.254.4.4Radio receiver interference performance.264.4.5Receiver intermodulation performance.265Additional test cases list.265.1Test purposes.265.1.1NWK layer.265.1.2DLC layer.265.1.3MAC layer.265.1.4PH layer.265.2Test cases.265.2.1NWK layer.265.2.2DLC layer.265.2.3MAC layer.275.2.4PH layer.275.2.4.1Receiver sensitivity tolerance of transmitter deviationvariations.275.2.4.1.1Definition.275.2.4.1.2Test environment.275.2.4.1.3Method of measurement.275.2.4.1.4Verdict criteria.285.2.4.2Transmission of Z-field.285.2.4.2.1Definition.285.2.4.2.2Test environment.285.2.4.2.3Method of measurement.285.2.4.2.4Verdict criteria.28SIST ETS 300 494-3:1999

Page 4ETS 300 494-3: August 1996Annex A (normative):Profile Implementation eXtra Information for Testing (IXIT) proforma.29A.1General.29A.2Profile IXIT Requirements List (XRL).29A.2.1NWK layer protocol.29A.2.1.1Addresses.29A.2.1.2Parameter values.29A.2.1.3Timer values.29A.2.1.4Counters values.29A.2.1.5Protocol constants values.30A.2.1.6Control of Protocol Data Units (PDU) sending.30A.2.2DLC layer protocol.30A.2.2.1Addresses.30A.2.2.2Parameter values.30A.2.2.3Timer values.30A.2.2.4Counters values.30A.2.2.5Protocol constants values.31A.2.2.6Control of PDU sending.31A.2.3MAC layer protocol.31A.2.3.1Addresses.31A.2.3.2Parameter values.31A.2.3.3Timer values.31A.2.3.4Counters values.31A.2.3.5Protocol constants values.31A.2.3.6Control of PDU sending.32A.2.4PH layer protocol.32A.2.4.1Addresses.32A.2.4.2Parameter values.32A.2.4.3Timer values.32A.2.4.4Counters values.32A.2.4.5Protocol constants values.32A.2.4.6Control of PDU sending.32A.3Profile specific IXIT.32A.3.1NWK layer.32A.3.2DLC layer.32A.3.3MAC layer.33A.3.4PH layer.33A.3.5Configuration constraints.33Annex B (normative):Profile Conformance Test Report (PCTR) proforma.34B.1Identification summary.34B.1.1PCTR.34B.1.2Implementation Under Test (IUT).35B.1.3Testing environment.35B.1.4Limits and reservations.35B.1.5Comments.36B.2IUT conformance status.36B.3Static conformance summary.36B.4Dynamic conformance summary.36B.5Static conformance review report.37SIST ETS 300 494-3:1999

Page 5ETS 300 494-3: August 1996B.6Test campaign report.37B.6.1NWK layer.38B.6.2DLC layer.40B.6.3MAC layer.41B.6.4PH layer.41B.7Observations.42Annex C (normative):System Conformance Test Report (SCTR) proforma.43C.1Identification summary.43C.1.1SCTR.43C.1.2Test laboratory.43C.1.3Client.44C.1.4System Under Test (SUT).44C.1.5Profile.44C.1.6Nature of conformance testing.45C.1.7Limits and reservations.45C.1.8Record of agreement.45C.1.9Comments.45C.2System report summary.46C.2.1Profile testing summary for GAP NWK layer FT.46C.2.2Profile testing summary for GAP DLC layer FT.47C.2.3Profile testing summary for GAP MAC layer FT.48C.2.4Profile testing summary for GAP PH layer FT.49Annex D (normative):System Conformance Statement (SCS) proforma.50D.1Identification summary.50D.1.1SCS identification.50D.1.2IUT identification.50D.1.3Client identification.50D.1.4Supplier identification.51D.1.5Manufacturer identification.52D.1.6Protocols identification.52D.1.7Profile identification.52D.2Miscellaneous System Information.52D.2.1Configuration.52D.2.2Other information.53History.54SIST ETS 300 494-3:1999

Page 6ETS 300 494-3: August 1996Blank pageSIST ETS 300 494-3:1999

Page 7ETS 300 494-3: 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 General Access Profile (GAP) Profile Test Specification (PTS) comprises three parts:Part 1:"Summary";Part 2:"Profile Specific Test Specification (PSTS) Portable radio Termination (PT)";Part 3:"Profile Specific Test Specification (PSTS) 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 494-3:1999

Page 8ETS 300 494-3: August 1996Blank pageSIST ETS 300 494-3:1999

Page 9ETS 300 494-3: August 19961ScopeThis European Telecommunication Standard (ETS) contains the test specification for Digital EnhancedCordless Telecommunications (DECT) Generic Access Profile (GAP) Fixed Part (FP) applications.The main objective of the GAP test specification is to provide approval tests giving a high probability of airinterface inter-operability between different manufacturer's equipment in different environments (i.e.public, business and residential).The ISO standard for the methodology of conformance testing ISO/IES 9646 Parts 1 to 7 [9] to [15] isused as the basis for the test methodology, and as the basis for test case specification. This is consideredas unsuitable for PH layer testing instead verbal description is used.The test cases listed in this ETS have been derived from the ETS 300 497-1 [18]. In addition as far asPhysical layer is concerned I-ETS 300 176 [16] applies. Additional GAP specific test cases are includedwhere required. The Profile IXIT is based on the DECT CI PIXITs specified in ETS 300 497-1 [18].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 Technical Basis for Regulation only when incorporated in it by amendment or revision. Forundated references the latest edition of the publication referred to applies.[1]ETS 300 175-1: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 1:Overview".[2]ETS 300 175-2: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 2: PhysicalLayer".[3]ETS 300 175-3: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 3: MediumAccess Control (MAC) layer".[4]ETS 300 175-4: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 4: DataLink Control (DLC) layer".[5]ETS 300 175-5: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 5: Network(NWK) layer".[6]ETS 300 175-6: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 6:Identities and addressing".[7]ETS 300 175-7: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 7: Securityfeatures".[8]ETS 300 444 (1995): "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Generic Access Profile (GAP)”.[9]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)).SIST ETS 300 494-3:1999

Page 10ETS 300 494-3: August 1996[10]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)).[11]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)).[12]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)).[13]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)).[14]ISO/IEC 9646-6 (1991): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 6:Protocol profile test specification".[15]ISO/IEC 9646-7 (1991): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 7:Implementation conformance statement".[16]I-ETS 300 176: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Approval test specification".[17]ETS 300 476-1: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Common Interface (CI); ProtocolImplementation Conformance Statement (PICS) proforma; Part 1: Network(NWK) layer - Portable radio Termination (PT)".[18]ETS 300 497-1: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Common Interface (CI) Test CaseLibrary (TCL); Part 1: Test Suite Structure (TSS) and Test Purposes (TP) forMedium Access Control (MAC) layer".[19]ETS 300 497-2: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Common Interface (CI) Test CaseLibrary (TCL); Part 2: Abstract Test Suite (ATS) for Medium Access Control(MAC) layer - Portable radio Termination (PT)".[20]ETS 300 497-3: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Common Interface (CI) Test CaseLibrary (TCL); Part 3: Abstract Test Suite (ATS) for Medium Access Control(MAC) layer - Fixed radio Termination (FT)".[21]ETS 300 497-4: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Common Interface (CI) Test CaseLibrary (TCL); Part 4: Test Suite Structure (TSS) and Test Purposes (TP) - DataLink Control (DLC) layer".[22]ETS 300 497-5: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Common Interface (CI) Test CaseLibrary (TCL); Part 5: Abstract Test Suite (ATS) - Data Link Control (DLC)layer".SIST ETS 300 494-3:1999

Page 11ETS 300 494-3: August 1996[23]ETS 300 497-6: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Common Interface (CI) Test CaseLibrary (TCL); Part 6: Test Suite Structure (TSS) and Test Purposes (TP) -Network (NWK) layer - Portable radio Termination (PT)".[24]ETS 300 497-7: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Common Interface (CI) Test CaseLibrary (TCL); Part 7: Abstract Test Suite (ATS) for Network (NWK) layer -Portable radio Termination (PT)".[25]ETS 300 497-8: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Common Interface (CI) Test CaseLibrary (TCL); Part 8: Test Suite Structure (TSS) and Test Purposes (TP) -Network (NWK) layer - Fixed radio Termination (FT)".[26]ETS 300 497-9: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Common Interface (CI) Test CaseLibrary (TCL); Part 9: Abstract Test Suite (ATS) for Network (NWK) layer - Fixedradio Termination (FT)".[27]ETS 300 474-1: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Generic Access Profile (GAP); Profilerequirement list and profile specific Implementation Conformance Statement(ICS) proforma; Part 1: Portable radio Termination (PT)".[28]ETS 300 494-1: "Radio Equipment and Systems (RES); Digital EnhancedCordless Telecommunications (DECT); Generic Access Profile (GAP); ProfileTest Specification (PTS); Part 1: Summary".SIST ETS 300 494-3:1999

Page 12ETS 300 494-3: August 19963Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply:-terms defined in ISO/IEC 9646 Parts 1 to 7 [9] to [15];-definitions in ETS 300 175 Parts 1 to 7 [1] to [7];-definitions in ETS 300 444 [8].3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ACAuthentication CodeATSAbstract Test SuiteCCCall ControlCICommon InterfaceDCKDerived Cipher KeyDLCData Link ControlFTFixed radio TerminationGAPGeneric Access ProfileICSImplementation Conformance StatementIPUIInternational Portable User IdentityIUTImplementation Under TestIXITImplementation eXtra Information for TestingLCELink Control EntityLLMELower Layer Management EntityLLNLogical Link NumberMACMedium Access ControlMMMobility ManagementNLFNew Link FlagNWKNetworkPARKPortable Access Rights KeyPHPhysicalPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingPTPortable radio TerminationPSTSProfile Specific Test SpecificationPTSProfile Test SpecificationSARISecondary Access Rights IdentitySUTSystem Under TestTPUITemporary Portable User IdentityTSTest SystemTSS&TPTest Suite Structure & Test PurposesSIST ETS 300 494-3:1999

Page 13ETS 300 494-3: August 19964Relevant test cases list4.1Network (NWK) layerThis subclause includes lists of the test groups and abstract test cases relevant for GAP PTS - NWK layerFixed Termination (FT) derived from ETS 300 497-9 [26].The page number referenced is the relative page number in the corresponding ETS where the particularitem can be found.NOTE:As ETS 300 497-1 [18] is draft, and some changes are likely due to the results of thePublic Enquiry (PE) phase, page numbers reflecting the exact place in that ETS wherea test case is to be found are not included in this ETS. They shall be added in a laterstage. References when necessary shall be made based on the particular test casename unique through all test specification ETS 300 497-1 [18].4.1.1Test suite structureTable 1Test Suite StructureSuite Name:nwk_ftStandards Ref:ETS 300 444 [8]; ETS 300 497-9 [26]Profile ICS Ref:ETS 300 474 [27]Profile IXIT Ref:ETS 300 494-3Test Method:remoteComments:Test Group ReferenceTest Group ObjectiveFT/To check the behaviour of the NWK layer of the FT(IUT)FT/CC/To check the IUT CC-state machine behaviourFT/CC/IT/To check that the IUT CC-state machine provides sufficient conformance forpossible interconnection without trying to perform thorough testingFT/CC/CA/Limited testing that the observable capabilities of the CC entity of the IUT are inaccordance with the static conformance requirements and the additionalcapabilities claimed in the PROFILE ICS/PROFILE IXITFT/CC/BV/To tests the CC entity of the IUT in response to syntactically and contextualcorrect behaviour of the test systemFT/CC/BV/OC/To check the IUT's behaviours to setup an outgoing callFT/CC/BV/IC/To check the IUT's behaviours to setup an incoming callFT/CC/BV/CI/To check the IUT's behaviour in information transfer proceduresFT/CC/BV/CR/To check the IUT's behaviours to release an outgoing/incoming callFT/CC/BO/To check the behaviour of the CC entity of the IUT in response to the messagesthat are syntactically correct but not allowed to occur in some states of the CCproceduresFT/CC/BI/To check the behaviour of the CC entity of the IUT in response to invalidmessagesFT/CC/TI/To verify that the IUT CC timers are with correct values and the IUT is reactingproperly to the expiry of a timerFT/MM/To check the behaviour of the Mobility Management entity of the IUTFT/MM/IT/To check that the MM entity of the IUT provides sufficient conformance forpossible interconnection without trying to perform thorough testingFT/MM/CA/Limited testing that the observable capabilities of the MM entity of the IUT are inaccordance with the static conformance requirements and the additionalcapabilities claimed in the PROFILE ICS/PROFILE IXITFT/MM/BV/To tests the MM entity of the IUT in response to syntactically and contextualcorrect behaviour of the test systemFT/MM/BV/ID/To check the IUT's behaviour concerning identity proceduresFT/MM/BV/AU/To check the IUT's behaviour concerning the authentication procedures(continued)SIST ETS 300 494-3:1999

Page 14ETS 300 494-3: August 1996Table 1 (concluded)Test Suite StructureFT/MM/BV/LO/To check the IUT's behaviour concerning the location proceduresFT/MM/BV/AR/To check the IUT's behaviour concerning the access rights proceduresFT/MM/BV/KA/To check the IUT's behaviour concerning the key allocation procedureFT/MM/BV/CH/To check the IUT's behaviour concerning the ciphering related proceduresFT/MM/BO/To check the IUT behaviour in response to the messages that are syntacticallycorrect but not allowed to occur in some phase of the MM proceduresFT/MM/BI/To check the IUT in response to invalid MM messagesFT/MM/TI/To verify that the IUT MM timers are with correct values and the IUT is reactingproperly to the expiry of a timerFT/ME/To check the behaviour of the LLME of the IUTFT/ME/IT/To check that LLME of the IUT provides sufficient conformance for possibleinterconnection without trying to perform thorough testingFT/ME/CA/Limited testing that the observable capabilities of the LLME of the IUT are inaccordance with the static conformance requirements and the additionalcapabilities claimed in the PROFILE ICS/PROFILE IXITFT/ME/BV/To tests the LLME of the IUT in response to syntactically and contextual correctbehaviour of the test systemFT/ME/BO/To check the IUT behaviour in response to the messages that are syntacticallycorrect but not allowed to occur in some phase of the LLME managedproceduresFT/LC/To check the behaviour of the LCE of the IUTFT/LC/IT/To check that LCE of the IUT provides sufficient conformance for possibleinterconnection without trying to perform thorough testingFT/LC/CA/Limited testing that the observable capabilities of the LCE of the IUT are inaccordance with the static conformance requirements and the additionalcapabilities claimed in the PROFILE ICS/PROFILE IXITFT/LC/BV/To tests the LCE of the IUT in response to syntactically and contextual correctbehaviour of the test systemFT/LC/BV/LE/To check the IUT's behaviour concerning the connection oriented linkestablishment proceduresFT/LC/BV/LR/To check the IUT's behaviour concerning the connection oriented link releaseproceduresFT/LC/BI/To check the IUT in response to invalid LCE messagesFT/LC/TI/To verify that the IUT LCE timers are with correct values and the IUT is reactingproperly to the expiry of a timerDetailed Comments:1.The sub-sub-groups with identifiers FT/xx/IT/ and FT/xx/CA/ do not include their own test cases butonly list an appropriate selection of tests from the relevant sub-group with identifier FT/xx/.SIST ETS 300 494-3:1999

Page 15ETS 300 494-3: August 19964.1.2Test case indexTable 2Test Case IndexTest GroupReferenceTest Case IdDescriptionFT/CC/BV/OC/TC_FT_CC_BV_OC_01Outgoing normal call; F-00 to F-10; piece-wise diallingTC_FT_CC_BV_OC_06Internal call. (There is no test case defined inETS 300 497-9 [26] due to difficulties of predicting theIUT behaviour)FT/CC/BV/IC/TC_FT_CC_BV_IC_01Incoming call; F-00, F-06, F-07 to F-10FT/CC/BV/CI/TC_FT_CC_BV_CI_01Incoming call; <> either in {SS-SETUP} or in{CC-INFO}TC_FT_CC_BV_CI_02Outgoing normal call; F-02; {CC-INFO], <>, "Go to pulse" handlingTC_FT_CC_BV_CI_04Outgoing normal call; F-02; {CC-INFO], <>, "dialling pause" handlingTC_FT_CC_BV_CI_05Outgoing normal call; F-10; {CC-INFO], <>, "Dialling pause" handlingTC_FT_CC_BV_CI_06Outgoing normal call; F-02; {CC-INFO], <>, "Go to DTMF defined tone length" handlingTC_FT_CC_BV_CI_07Outgoing normal call; F-10; {CC-INFO], <>, "Go to DTMF defined tone length" handlingTC_FT_CC_BV_CI_08Outgoing normal call; F-02; {CC-INFO], <>, "Go to DTMF infinite tone length" handlingTC_FT_CC_BV_CI_09Outgoing normal call; F-10; {CC-INFO], <>, "Go to DTMF infinite tone length" handlingTC_FT_CC_BV_CI_10Outgoing normal call; F-10; {CC-INFO], <>, "0-9, star, hash mark" handlingTC_FT_CC_BV_CI_11Internal call. (There is no test case defined inETS 300 497-9 [26] due to difficulties of predicting theIUT behaviour)TC_FT_CC_BV_CI_12FT handling <>. (There is no testcase defined in ETS 300 497-9 [26] due to difficulties ofpredicting the IUT behaviour)FT/CC/BV/CR/TC_FT_CC_BV_CR_01Outgoing normal call; F-02; IUT initiated normal releaseTC_FT_CC_BV_CR_02F-10; IUT initiated normal releaseTC_FT_CC_BV_CR_03Incoming call; F-07; IUT initiated normal releaseTC_FT_CC_BV_CR_04Outgoing call; F-02; PT initiated normal releaseTC_FT_CC_BV_CR_05F-10; PT initiated normal releaseTC_FT_CC_BV_CR_06Incoming call; F-07; PT initiated normal releaseTC_FT_CC_BV_CR_07Incoming call; F-07; PT initiated abnormal releaseTC_FT_CC_BV_CR_08F-10; PT initiated abnormal releaseTC_FT_CC_BV_CR_09Incoming call; F-06; PT initiated abnormal releaseTC_FT_CC_BV_CR_10F-10; PT initiated partial releaseTC_FT_CC_BV_CR_11F-10; FT initiated partial releaseFT/CC/RS/TC_FT_CC_RS_01Register recall. (There is no test case defined inETS 300 497-9 [26] due to difficulties of predicting theIUT behaviour)TC_FT_CC_RS_07Incoming call; T-00; {CC-SETUP}, <> provision (CLIP support)FT/CC/BO/TC_FT_CC_BO_01F-10; unexpected {CC-ALERTING}(continued)SIST ETS 300 494-3:1999

Page 16ETS 300 494-3: August 1996Table 2 (continued)Test Case IndexTest GroupReferenceTest Case IdDescriptionTC_FT_CC_BO_02F-19; receipt of {CC-RELEASE}; release collisionshandlingFT/CC/BI/TC_FT_CC_BI_01F-00; {CC-SETUP} mandatory I.E. missing; answerupon with {CC-RELEASE-COM]TC_FT_CC_BI_02F-00; {CC-SETUP} wrong mandatory I.E.; answer uponwith {CC-RELEASE-COM]TC_FT_CC_BI_03F-00; {CC-SETUP}-like message, non {CC-SETUP}unrecognised message type; ignoreTC_FT_CC_BI_04F-00; to short message to contain the complete<>; ignoreFT/CC/TI/TC_FT_CC_TI_01Outgoing call; F-02; timer F- expiry (± 5 %margin); IUT sends {CC-RELEASE}TC_FT_CC_TI_02Outgoing call; F-02; restart of timer F- onreceipt of {CC-INFO}TC_FT_CC_TI_03Outgoing call; F-19; timer F- expiry (± 5 %margin); IUT sends {CC-RELEASE-COM}TC_FT_CC_TI_04Outgoing call; F-06; timer F- expiry (± 5 %margin); IUT sends {CC-RELEASE-COM}FT/MM/BV/ID/TC_FT_MM_BV_ID_01Identity request procedure; IUT initiatedFT/MM/BV/AU/TC_FT_MM_BV_AU_01Authentication of PT; PT has no stored ZAP value andservice class infoTC_FT_MM_BV_AU_02Authentication of PT; ZAP increment; PT has storedZAP value and service class info; PT authenticates FTbefore answeringTC_FT_MM_BV_AU_03Authentication of user; PT has no stored ZAP valueand service class infoTC_FT_MM_BV_AU_04Authentication of FTTC_FT_MM_BV_AU_05Authentication of FT; Unsupported key requested; IUTrejectsTC_FT_MM_BV_AU_06Authentication of PT; store DCK ; PT has no storedZAP value and service class infoFT/MM/BV/LO/TC_FT_MM_BV_LO_01Location registration; a38=1 at locking and at thebeginning of the procedure; request with IPUITC_FT_MM_BV_LO_02Location registration; a38=1 at locking and at thebeginning of the procedure; request with unknown IPUI;rejectTC_FT_MM_BV_LO_03Location registration; a38=1 at locking and at thebeginning of the procedure; request with IPUI; IUTassigns TPUITC_FT_MM_BV_LO_05Location update; a38=1 at locking; {MM-INFO-SUGGEST};TC_FT_MM_BV_LO_06Location registration; a38=1 at locking; a38=0 at thebeginning of the procedure; request with IPUIFT/MM/BV/AR/TC_FT_MM_BV_AR_01Obtain access rights; both sides use AC indication; IUTsends the whole PARKTC_FT_MM_BV_AR_02Obtain access rights; service class assignTC_FT_MM_BV_AR_03Terminate access rights; IUT(FT) initiated; PTauthenticates FTTC_FT_MM_BV_AR_06Obtain access rights; both sides use UAK indication;IUT sends the whole PARKTC_FT_MM_BV_AR_07Obtain access rights; ZAP value assignFT/MM/BV/KA/TC_FT_MM_BV_KA_01Key allocate; IUT initiated(continued)SIST ETS 300 494-3:1999

Page 17ETS 300 494-3: August 1996Table 2 (continued)Test Case IndexTest GroupReferenceTest Case IdDescriptionTC_FT_MM_BV_KA_02Key allocate; IUT initiated; "implicit PT authentication"failure; IUT rejectsTC_FT_MM_BV_KA_03Key allocate; IUT initiated; PT rejects; IUT keeps ACFT/MM/BV/CH/TC_FT_MM_BV_CH_01Cipher switching; PT initiated; "cipher-off" to "cipher-on"TC_FT_MM_BV_CH_02Cipher switching; PT initiated; "cipher-on" to "cipher-off"TC_FT_MM_BV_CH_03Cipher switching; IUT(FT) initiated; "cipher-off" to"cipher-on"TC_FT_MM_BV_CH_04Cipher switching; IUT(FT) initiated; "cipher-on" to"cipher-off"TC_FT_MM_BV_CH_05Cipher switching; PT initiated with "unsupported cipherkey"; IUT rejectsFT/MM/BO/TC_FT_MM_BO_01Cipher switching; IUT(FT) initiated; ignoringunexpected {IDENTITY-REPLY}FT/MM/BI/TC_FT_MM_BI_01Identity request; PT sends unrecognised message; IUTignoresTC_FT_MM_BI_02Obtain access rights; {ACCESS-RIGHTS-REQUEST}missing <>; IUT sends {ACCESS-RIGHTS-REJECT}TC_FT_MM_BI_03Obtain access rights; {ACCESS-RIGHTS-REQUEST}with <> exceeding the max. allowed length;IUT sends {ACCESS-RIGHTS-REJECT}FT/MM/TI/TC_FT_MM_TI_01Identity request; timer F- expiry (± 5 %margin)TC_FT_MM_TI_02Authentication of PT; timer F- expiry (±5 % margin)TC_FT_MM_TI_03Authentication of user; timer F- expiry (±5 % margin)TC_FT_MM_TI_04Terminate access rights; IUT(FT) initiated; timer F- expiry (± 5 % margin)TC_FT_MM_TI_05Key allocation; timer F- expiry (± 5 %margin)TC_FT_MM_TI_06Cipher switching; IUT(FT) initiated; timer F- expiry (± 5
% margin)TC_FT_MM_TI_07Location registration with TPUI assignment; timer F- expiry (± 5 % margin)FT/ME/BV/TC_FT_ME_BV_01Incoming call and authentication of FT handled inparallelTC_FT_ME_BV_02Authentication of user interrupted by Authentication ofFTTC_FT_ME_BV_03CC call and location registration in parallelFT/ME/BO/TC_FT_ME_BO_01Authentication of PT; Ignore of {LOCATE-REQUEST}(lower priority)(continued)SIST ETS 300 494-3:1999

Page 18ETS 300 494-3: August 1996Table 2 (concluded)Test Case IndexTest GroupReferenceTest Case IdDescriptionFT/LC/BV/LE/TC_FT_LC_BV_LE_01Indirect IUT(FT) link establishment procedure; correctPT answerTC_FT_LC_BV_LE_02Indirect IUT(FT) link establishment procedure; {LCE-PAGE-RESPONSE} with mismatching IPUI; IUT rejectsand release the linkTC_FT_LC_BV_LE_03Direct PT initiated link establishment procedureFT/LC/BV/LR/TC_FT_LC_BV_LR_01Link exists; PT initiated "normal" link releaseTC_FT_LC_BV_LR_02Link exists; MM entity ceases to use the link; no otherentity uses the link; IUT maintains the link timeTC_FT_LC_BV_LR_03Link exists; CC call is terminated; FT initiated linkreleaseTC_FT_LC_BV_LR_04Link exists; CC entity ceases to use the link partialrelease agreed; no other entity uses the link; IUTmaintains the link timeFT/LC/BI/TC_FT_LC_BI_01Protocol discriminator value error -unsupported service;IUT ignoresTC_FT_LC_BI_04{AUTH-REQUEST} with illegal transaction id.; ignoreTC_FT_LC_BI_05Identity request procedure; {IDENTITY-REPLY} withtransaction id. flag='0'; ignoreTC_FT_LC_BI_07F-10; link fails; IUT clears the callFT/LC/TI/TC_FT_LC_TI_01Link exists; normal link release is requested; timer expiry. (There is no test case defined inETS 300 497-9 [26] due to difficulties of predicting theIUT behaviour)TC_FT_LC_TI_02MM ceases to use the link; no other entity uses the link;timer expiry (± 5 % margin)TC_FT_LC_TI_03Indirect IUT(FT) initiated link establishment; no answer;timer expiry (± 5 % margin)Detailed Comments:1.The FT is the IUT.SIST ETS 300 494-3:1999

Page 19ETS 300 494-3: August 19964.2Data Link Control (DLC) layerThis subclause includes list of the abstract test cases relevant for GAP PTS - DLC layer FT derived fromETS 300 497-5 [22].The page number referenced is the relative page number in the corresponding ETS where the particularitem can be found.4.2.1Test suite structureTable 3Test Suite StructureSuite Name:DLCStandards Ref:ETS 300 444 [8]; ETS 300 497-5 [22]Profile ICS Ref:ETS 300 474 [27]Profile IXIT Ref:ETS 300 494-3Test Method:remoteComments:Test Group ReferenceTest Group ObjectiveDLC/Verify the correct implementation of the FT (IUT) DLC layerDLC/C_Plane/Verify the correct implementation of the C-plane data link servicesDLC/C_Plane/ClassA/Verify the correct implementation of the LAPC's Class A acknowledged transferoperationDLC/C_Plane/ClassA/CA/Limited testing that the observable capabilities of the IUT concerning theLAPC's Class A acknowledged transfer operation are in accordance with thestatic conformance requirements and the additional capabilities claimed in thePROFILE ICS/PROFILE IXITDLC/C_Plane/ClassA/BV/To tests the behaviour of the IUT in response to syntactically and contextualcorrect behaviour of the test systemDLC/C_Plane/ClassA/BI/To check the behaviour of the of the IUT in response to invalid framesDLC/C_Plane/Lb/Verify the correct implementation of the Lb (C-plane broadcast control) entityDLC/C_Plane/Lb/CA/Limited testing that the observable capabilities of the IUT concerning the Lb(C-plane broadcast control) entity are in accordance with the staticconformance requirements and the additional capabilities claimed in thePROFILE ICS/PROFILE IXITDLC/U_Plane/Verify the correct implementation of the U-plane servicesDLC/U_Plane/Class0/Verify the correct implementation of the Class 0 transmission classDLC/U_Plane/Class0/CA/Limited testing that the observable capabilities of the IUT concerning the Class0 transmission class service are in accordance with the static conformancerequirements and the additional capabilities claimed in the PROFILEICS/PROFILE IXITDetailed Comments:SIST ETS 300 494-3:1999

Page 20ETS 300 494-3: August 19964.2.2Test case indexTable 4Test Case IndexTest GroupReferenceTest Case IdDescriptionDLC/C_Plane/ClassA/CA/TC_A_CA_005I-Frame acknowledgement within timer TC_A_CA_006re-transmission of an I-Frame N250 timesTC_A_CA_007refusal of a Class B link establishment RR response framewith the reserved LLN value "Class A operation" and NLFbit set to "1"; Class A established stateTC_A_CA_008Class A establishment request; responding and enteringinto Class A established stateDLC/C_Plane/ClassA/BV/TC_A_BV_002I-Frame acknowledgement; sending RR response framewith correct N(R)TC_A_BV_003I-Frame acknowledgement; accepting an I-Framecommand with correct N(S) and N(R) values as anacknowledgement.TC_A_BV_004re-establishment request acceptance; Class A establishedstateTC_A_BV_005timer re transmission phase; acceptance of a RR responseframe with correct N(R) value as an acknowledgementTC_A_BV_006timer re transmission phase; acceptanc
...