SIST EN 300 494-3 V1.2.1:2003

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.7Digital 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:EN 300 494-3 Version 1.2.1SIST EN 300 494-3 V1.2.1:2003en01-december-2003SIST EN 300 494-3 V1.2.1:2003SLOVENSKI
STANDARD
ETSIETSI EN 300 494-3 V1.2.1 (1999-08)2ReferenceREN/DECT-040143-3 (4kor0ioo.PDF)KeywordsATS, DECT, FT, GAP, PTS, testingETSIPostal 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.frCopyright 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 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)3ContentsIntellectual Property Rights.6Foreword.61Scope.72References.73Definitions and abbreviations.93.1Definitions.93.2Abbreviations.94Relevant test cases list.104.1Network (NWK) layer.104.1.1Test suite structure (TSS).104.1.2Test case index.114.2Data Link Control (DLC) layer.144.2.1Test suite structure.144.2.2Test case index.154.3Medium Access Control (MAC) layer.164.3.1Test suite structure.164.3.2Test case index.174.4Physical (PH) layer.174.4.1Manufacturer declarations.174.4.2Normal Transmitted Power (NTP).184.4.2.1Verdict criteria for IUTs with an integral antenna.184.4.2.2Verdict criteria for IUTs with external antenna connection(s).184.4.3RFP radio receiver sensitivity.184.4.4Radio receiver interference performance.184.4.5Receiver intermodulation performance.185Additional test cases list.185.1Test purposes.185.1.1NWK layer.185.1.2DLC layer.195.1.3MAC layer.195.1.4PH layer.195.2Test cases.195.2.1NWK layer.195.2.2DLC layer.195.2.3MAC layer.195.2.4PH layer.195.2.4.1Receiver sensitivity tolerance of transmitter deviation variations.195.2.4.1.1Definition.195.2.4.1.2Test environment.205.2.4.1.3Method of measurement.205.2.4.1.4Verdict criteria.205.2.4.2Transmission of Z-field.205.2.4.2.1Definition.205.2.4.2.2Test environment.205.2.4.2.3Method of measurement.215.2.4.2.4Verdict criteria.21Annex A (normative):Profile Implementation eXtra Information for Testing (PIXIT)proforma.22A.1General.22A.2Profile IXIT Requirements List (XRL).22A.2.1NWK layer protocol.22SIST EN 300 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)4A.2.2DLC layer protocol.22A.2.3MAC layer protocol.22A.2.4PH layer protocol.22A.3Profile specific IXIT.22A.3.1NWK layer.22A.3.2DLC layer.22A.3.3MAC layer.22A.3.4PH layer.23A.3.5Configuration constraints.23Annex B (normative):Profile Conformance Test Report (PCTR) proforma.24B.1Identification summary.24B.1.1Profile CTR.24B.1.2Implementation Under Test (IUT).24B.1.3Testing environment.25B.1.4Limits and reservations.25B.1.5Comments.25B.2IUT conformance status.25B.3Static conformance summary.26B.4Dynamic conformance summary.26B.5Static conformance review report.26B.6Test campaign report.27B.6.1NWK layer.27B.6.2DLC layer.29B.6.3MAC layer.29B.6.4PH layer.30B.7Observations.30Annex C (normative):System Conformance Test Report (SCTR) proforma.31C.1Identification summary.31C.1.1System Conformance Test Report (SCTR).31C.1.2Test laboratory.31C.1.3Client.32C.1.4System Under Test (SUT).32C.1.5Profile.32C.1.6Nature of conformance testing.33C.1.7Limits and reservations.33C.1.8Record of agreement.33C.1.9Comments.33C.2System report summary.34C.2.1Profile testing summary for GAP NWK layer FT.34C.2.2Profile testing summary for GAP DLC layer FT.35C.2.3Profile testing summary for GAP MAC layer FT.36C.2.4Profile testing summary for GAP PH layer FT.37Annex D (normative):System Conformance Statement (SCS) proforma.38D.1Identification summary.38D.1.1SCS identification.38D.1.2IUT identification.38D.1.3Client identification.38D.1.4Supplier identification.39D.1.5Manufacturer identification.39D.1.6Protocols identification.40D.1.7Profile identification.40SIST EN 300 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)5D.2Miscellaneous system information.40D.2.1Configuration.40D.2.2Other information.41History.42SIST EN 300 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)6Intellectual 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 Generic Access Profile (GAP) as identified below: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)".National transposition datesDate of adoption of this EN:6 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 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)71ScopeThe present document contains the test specification for Digital Enhanced Cordless 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 air interfaceinter-operability between different manufacturer's equipment in different environments (i.e. public, business andresidential).The ISO standard for the methodology of conformance testing ISO/IEC 9646 Parts 1 to 7 [9] to [15] is used as the basisfor the test methodology, and as the basis for the test case specification. This is considered to be unsuitable for Physicallayer testing, and therefore a text description is used.The test cases listed in the present document have been derived from the DECT Common Interface (CI) Test CaseLibrary (TCL) [18] to [26]. In addition as far as the Physical layer is concerned EN 300 176 [16] applies. AdditionalGAP specific test cases are included where required. The Profile IXIT is based on the DECT CI PIXITs specified inEN 300 497 [18] to [26].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-5: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 5: Network (NWK) layer".[6]EN 300 175-6: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 6: Identities and addressing".[7]EN 300 175-7: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 7: Security features".[8]EN 300 444: "Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile(GAP)".[9]ISO/IEC 9646-1: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 1: General concepts".SIST EN 300 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)8[10]ISO/IEC 9646-2: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 2: Abstract test suite specification".[11]ISO/IEC 9646-3: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 3: The Tree and Tabular Combined Notation (TTCN)".[12]ISO/IEC 9646-4: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 4: Test realization".[13]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".[14]ISO/IEC 9646-6: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 6: Protocol Profile Test Specification".[15]ISO/IEC 9646-7: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 7: Implementation Conformance Statements".[16]EN 300 176: "Digital Enhanced Cordless Telecommunications (DECT); Approval testspecification".[17]ETS 300 476, part 1 to 7: "Digital Enhanced Cordless Telecommunications (DECT); CommonInterface (CI); Protocol Implementation Conformance Statement (PICS) proforma".[18]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".[19]EN 300 497-2: "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)".[20]EN 300 497-3: "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)".[21]EN 300 497-4: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI)Test Case Library (TCL); Part 4: Test Suite Structure (TSS) and Test Purposes (TP) - Data LinkControl (DLC) layer".[22]EN 300 497-5: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI)Test Case Library (TCL); Part 5: Abstract Test Suite (ATS) - Data Link Control (DLC) layer".[23]EN 300 497-6: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI)Test Case Library (TCL); Part 6: Test Suite Structure (TSS) and Test Purposes (TP) - Network(NWK) layer - Portable radio Termination (PT)".[24]EN 300 497-7: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI)Test Case Library (TCL); Part 7: Abstract Test Suite (ATS) for Network (NWK) layer - Portableradio Termination (PT)".[25]EN 300 497-8: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI)Test Case Library (TCL); Part 8: Test Suite Structure (TSS) and Test Purposes (TP) - Network(NWK) layer - Fixed radio Termination (FT)".[26]EN 300 497-9: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI)Test Case Library (TCL); Part 9: Abstract Test Suite (ATS) for Network (NWK) layer - Fixedradio Termination (FT)".[27]ETS 300 474-1: "Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile(GAP); Profile requirement list and profile specific Implementation Conformance Statement (ICS)proforma; Part 1: Portable radio Termination (PT)".SIST EN 300 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)9[27A]ETS 300 474-2: "Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile(GAP); Profile requirement list and profile specific Implementation Conformance Statement (ICS)proforma; Part 2: Fixed radio Termination (FT)".[28]EN 300 494-1: "Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile(GAP); Profile Test Specification (PTS); Part 1: Summary".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following terms and definitions apply:-terms defined in ISO/IEC 9646 Parts 1 to 7 [9] to [15];-definitions in EN 300 175 Parts 1 to 7 [1] to [7];-definitions in EN 300 444 [8].3.2AbbreviationsFor the purposes of the present document, 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 EntityMACMedium 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 SystemSIST EN 300 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)104Relevant test cases list4.1Network (NWK) layerThis subclause includes lists of the test groups and abstract test cases relevant for GAP Profile Test Specification (PTS);NWK layer Fixed Termination (FT) derived from EN 300 497-9 [26].NOTE:References when necessary shall be made based on the particular test case name unique through all testspecification EN 300 497 [18] to [26].4.1.1Test suite structure (TSS)Table 1Test Suite StructureSuite Name:nwk_ftStandards Ref:EN 300 444 [8]; EN 300 497-9 [26]Profile ICS Ref:ETS 300 474 [27]Profile IXIT Ref:EN 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 for possibleinterconnection 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 additional capabilitiesclaimed in the PROFILE ICS/PROFILE IXITFT/CC/BV/To test the CC entity of the IUT in response to syntactically and contextual correctbehaviour 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/RSTo check the IUT's behaviour during call related supplementary service proceduresFT/CC/BO/To check the behaviour of the CC entity of the IUT in response to the messages thatare syntactically correct but not allowed to occur in some states of the CC proceduresFT/CC/BI/To check the behaviour of the CC entity of the IUT in response to invalid messagesFT/CC/TI/To verify that the IUT CC timers are with correct values and the IUT is reacting properlyto 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 for possibleinterconnection 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 additional capabilitiesclaimed in the PROFILE ICS/PROFILE IXITFT/MM/BV/To test the MM entity of the IUT in response to syntactically and contextual correctbehaviour 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 proceduresFT/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 syntactically correctbut not allowed to occur in some phase of the MM proceduresFT/MM/BI/To check the IUT in response to invalid MM messagesSIST EN 300 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)11Test Suite StructureSuite Name:nwk_ftStandards Ref:EN 300 444 [8]; EN 300 497-9 [26]Profile ICS Ref:ETS 300 474 [27]Profile IXIT Ref:EN 300 494-3Test Method:remoteComments:Test Group ReferenceTest Group ObjectiveFT/MM/TI/To verify that the IUT MM timers are with correct values and the IUT is reacting properlyto 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 additional capabilitiesclaimed in the PROFILE ICS/PROFILE IXITFT/ME/BV/To test the LLME of the IUT in response to syntactically and contextual correctbehaviour of the test systemFT/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 in accordancewith the static conformance requirements and the additional capabilities claimed in thePROFILE ICS/PROFILE IXITFT/LC/BV/To test the LCE of the IUT in response to syntactically and contextual correct behaviourof the test systemFT/LC/BV/LE/To check the IUT's behaviour concerning the connection oriented link establishmentproceduresFT/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:The sub-sub-groups with identifiers FT/xx/IT/ and FT/xx/CA/ do not include their own test cases but only list anappropriate selection of tests from the relevant sub-group with identifier FT/xx/.4.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_06Verify that the IUT can correctly establish a followingoutgoing call from the LT when the LT has use SARI as themeans to lock to the IUTFT/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 {CC-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_03Outgoing normal call; F-10; {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" handlingSIST EN 300 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)12Test Case IndexTest GroupReferenceTest Case IdDescriptionTC_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" handlingFT/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 releaseFT/CC/RSTC_FT_CC_RS_07Incoming call; T-00; {CC-SETUP}, <>provision (CLIP support)FT/CC/BO/TC_FT_CC_BO_01F-02; unexpected {CC-SETUP}TC_FT_CC_BO_02F-19; receipt of {CC-RELEASE}; release collisions handlingFT/CC/BI/TC_FT_CC_BI_01F-00; {CC-SETUP} mandatory I.E. missing; answer uponwith {CC-RELEASE-COM]TC_FT_CC_BI_02F-00; {CC-SETUP} wrong mandatory I.E.; answer upon with{CC-RELEASE-COM]TC_FT_CC_BI_03F-00; {CC-SETUP}-like message, non {CC-SETUP}unrecognized message type; ignoreFT/CC/TI/TC_FT_CC_TI_01Outgoing call; F-02; timer F- expiry (-10 %margin);IUT sends {CC-RELEASE}TC_FT_CC_TI_02Outgoing call; F-02; restart of timer F- on receipt of{CC-INFO}TC_FT_CC_TI_03Outgoing call; F-19; timer F- expiry (-10 %margin);IUT sends {CC-RELEASE-COM}TC_FT_CC_TI_04Outgoing call; F-06; timer F- expiry (-10 %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 stored ZAPvalue and service class info; PT authenticates FT beforeansweringTC_FT_MM_BV_AU_03Authentication of user; PT has no stored ZAP value andservice 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 stored ZAPvalue and service class infoFT/MM/BV/LO/TC_FT_MM_BV_LO_01Location registration; a38=1 at locking and at the beginningof the procedure; request with IPUITC_FT_MM_BV_LO_02Location registration; a38=1 at locking and at the beginningof the procedure; request with unknown IPUI; rejectTC_FT_MM_BV_LO_03Location registration; a38=1 at locking and at the beginningof the procedure; request with IPUI; IUT assigns TPUITC_FT_MM_BV_LO_05Location update; a38=1 at locking; Location reg started upon1st {MM-INFO-SUGGEST}TC_FT_MM_BV_LO_06Location registration; a38=1 at locking; a38=0 at thebeginning of the procedure; request with IPUITC_FT_MM_BV_LO_07Location update; a38=1 at locking; Location reg started upon2nd {MM-INFO-SUGGEST}FT/MM/BV/AR/TC_FT_MM_BV_AR_01Obtain access rights; both sides use AC indication; IUTsends the whole PARKSIST EN 300 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)13Test Case IndexTest GroupReferenceTest Case IdDescriptionTC_FT_MM_BV_AR_02Obtain access rights; service class assignTC_FT_MM_BV_AR_03Terminate access rights; IUT(FT) initiated; PT authenticatesFTTC_FT_MM_BV_AR_06Obtain access rights; both sides use UAK indication; IUTsends the whole PARKTC_FT_MM_BV_AR_07Obtain access rights; ZAP value assignFT/MM/BV/KA/TC_FT_MM_BV_KA_01Key allocate; IUT initiatedTC_FT_MM_BV_KA_02Key allocate; IUT initiated; "implicit PT authentication" failure;IUT rejectsFT/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 cipher key";IUT rejectsTC_FT_MM_BV_CH_08Cipher switching; IUT(FT) initiated; "cipher-off" to "cipher-on"failsTC_FT_MM_BV_CH_09Cipher switching; PT initiated; "cipher-off" to "cipher-on" failsTC_FT_MM_BV_CH_10Cipher switching; PT initiated; "cipher-off" to "cipher-on" andintercell handoverTC_FT_MM_BV_CH_11Cipher switching; PT initiated; "cipher-off" to "cipher-on" andintracell handoverTC_FT_MM_BV_CH_12Cipher switching; IUT(FT) initiated; "cipher-off" to "cipher-on"and intercell handoverTC_FT_MM_BV_CH_13Cipher switching; PT initiated; "cipher-on" to "cipher-off" failsTC_FT_MM_BV_CH_14Cipher switching; IUT(FT) initiated; "cipher-off" to "cipher-on"and intracell handoverTC_FT_MM_BV_CH_15Cipher switching; IUT(FT) initiated; "cipher-on" to "cipher-off"failsFT/MM/BO/TC_FT_MM_BO_01Cipher switching; IUT(FT) initiated; ignoring unexpected{IDENTITY-REPLY}FT/MM/BITC_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; IUTsends {ACCESS-RIGHTS-REJECT}FT/MM/TI/TC_FT_MM_TI_01Identity request; timer F- expiry (-10 % margin)TC_FT_MM_TI_02Authentication of PT; timer F- expiry (-10 %margin)TC_FT_MM_TI_03Authentication of user; timer F- expiry (-10 %margin)TC_FT_MM_TI_04Terminate access rights; IUT(FT) initiated; timerF- expiry (-10 % margin)TC_FT_MM_TI_05Key allocation; timer F- expiry (-10 % margin)TC_FT_MM_TI_06Cipher switching; IUT(FT) initiated; timer F-expiry (margin: -20 %)TC_FT_MM_TI_07Location registration with TPUI assignment; timerF- expiry (+5 % margin)FT/ME/BV/TC_FT_ME_BV_01Incoming call and authentication of FT handled in parallelTC_FT_ME_BV_02Authentication of user interrupted by Authentication of FTTC_FT_ME_BV_03CC call and location registration in parallelFT/LC/BV/LE/TC_FT_LC_BV_LE_01Indirect IUT(FT) link establishment procedure; correct PTanswerTC_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 other entityuses the link; IUT maintains the link timeTC_FT_LC_BV_LR_03Link exists; CC call is terminated; FT initiated link releaseSIST EN 300 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)14Test Case IndexTest GroupReferenceTest Case IdDescriptionTC_FT_LC_BV_LR_04Link exists; CC entity ceases to use the link partial releaseagreed; no other entity uses the link; IUT maintains the link timeFT/LC/BI/TC_FT_LC_BI_01Protocol discriminator value error -unsupported service; IUTignoresTC_FT_LC_BI_04{AUTH-REQUEST} with illegal transaction id.; ignoreTC_FT_LC_BI_07F-10; link fails; IUT clears the callFT/LC/TI/TC_FT_LC_TI_02MM ceases to use the link; no other entity uses the link; timer expiry (allowed period: (TSPX_lce_02-1000) ms to10500 ms)Detailed Comments:The FT is the IUT.4.2Data Link Control (DLC) layerThis subclause includes lists of the test groups and the abstract test cases relevant for GAP PTS - DLC layer FT derivedfrom EN 300 497-5 [22].4.2.1Test suite structureTable 3Test Suite StructureSuite Name:DLCStandards Ref:EN 300 444 [8]; EN 300 497-5 [22]Profile ICS Ref:ETS 300 474 [27]Profile IXIT Ref:EN 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 the LAPC's ClassA acknowledged transfer operation are in accordance with the static conformancerequirements and the additional capabilities claimed in the PROFILE ICS/PROFILE IXITDLC/C_Plane/ClassA/BV/To test the behaviour of the IUT in response to syntactically and contextual correctbehaviour 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-planebroadcast control) entity are in accordance with the static conformance requirementsand the additional capabilities claimed in the PROFILE 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 Class 0transmission class service are in accordance with the static conformance requirementsand the additional capabilities claimed in the PROFILE ICS/PROFILE IXITDetailed Comments:SIST EN 300 494-3 V1.2.1:2003

ETSIETSI EN 300 494-3 V1.2.1 (1999-08)154.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 frame withthe reserved LLN value "Class A operation" and NLF bit set to"1"; Class A established stateTC_A_CA_008Class A establishment request; responding and entering intoClass A established stateDLC/C_Plane/ClassA/BV/TC_A_BV_002I-Frame acknowledgement; sending RR response frame withcorrect N(R)TC_A_BV_003I-Frame acknowledgement; accepting an I-Frame command withcorrect N(S) and N(R) values as an acknowledgement.TC_A_BV_005timer re transmission phase; acceptance of a RR response framewith correct N(R) value as an acknowledgementTC_A_BV_006timer re transmission phase; acceptance of an I-Frame commandwith correct N(S) and N(R) values as an acknowledgementTC_A_BV_007connection handover; PT initiated intracellTC_A_BV_008connection handover; PT initiated intercellDLC/C_Plane/ClassA/BI/TC_A_BI_004information transfer phase; discarding RR response frame, LLNindicates B-class, invalid N(R);
...