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

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 2: Profile Specific Test Specification (PSTS) - Portable radio Termination (PT)33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:ETS 300 494-2 E13SIST ETS 300 494-2:1999en01-MDQXDU-19993SIST ETS 300 494-2:1999SLOVENSKI
STANDARD
EUROPEANETS 300 494-2TELECOMMUNICATIONAugust 1996STANDARDSource: ETSI TC-RESReference: DE/RES-03040-2ICS: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 2: Profile Specific Test Specification (PSTS)- 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 494-2:1999

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

Page 3ETS 300 494-2: August 1996ContentsForeword.71Scope.92Normative references.93Definitions and abbreviations.113.1Definitions.113.2Abbreviations.124Relevant test cases list.124.1Network (NWK) layer.124.1.1Test Suite Structure (TSS).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.234.4PHysical (PH) layer.244.4.1Manufacturer declarations.244.4.2Normal Transmitted Power (NTP).244.4.2.1Verdict criteria for IUTs with an integral antenna.244.4.2.2Verdict criteria for IUTs with external antenna connection(s).244.4.3PP radio receiver sensitivity.244.4.4Radio receiver interference performance.254.4.5Receiver intermodulation performance.254.4.6User controlled volume control.255Additional test cases list.255.1Test purposes.255.1.1NWK layer.255.1.2DLC layer.255.1.3MAC layer.255.1.4PH layer.255.2Test cases.265.2.1NWK layer.265.2.2DLC layer.265.2.3MAC layer.265.2.4PH layer.265.2.4.1Receiver sensitivity tolerance of transmitter deviationvariations.265.2.4.1.1Definition.265.2.4.1.2Test environment.265.2.4.1.3Method of measurement.265.2.4.1.4Verdict criteria.275.2.4.2Receiver timing tolerance of a PT.275.2.4.2.1Definition.275.2.4.2.2Test environment.275.2.4.2.3Method of measurement, Part 1.275.2.4.2.4Method of measurement, Part 2.285.2.4.2.5Verdict criteria for part 1.285.2.4.2.6Verdict criteria for part 2.285.2.4.3Transmission of Z-field.285.2.4.3.1Definition.285.2.4.3.2Test environment.28SIST ETS 300 494-2:1999

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

Page 5ETS 300 494-2: August 1996B.6.2DLC layer.40B.6.3MAC layer.41B.6.4PH layer.42B.7Observations.42Annex C (normative):System Conformance Test Report proforma (SCTR).43C.1Identification summary.43C.1.1System Conformance Test Report (SCTR).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.46C.2System report summary.46C.2.1Profile testing summary for GAP NWK layer PT.46C.2.2Profile testing summary for GAP DLC layer PT.47C.2.3Profile testing summary for GAP MAC layer PT.48C.2.4Profile testing summary for GAP PH layer PT.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.51D.1.6Protocols identification.52D.1.7Profile identification.52D.2Miscellaneous system information.52D.2.1Configuration.52D.2.2Other information.52History.53SIST ETS 300 494-2:1999

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

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

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

Page 9ETS 300 494-2: August 19961ScopeThis European Telecommunication Standard (ETS) contains the test specification for Digital EnhancedCordless Telecommunications (DECT) Generic Access Profile (GAP) Portable Part (PP) 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/IEC 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 the physical layer testing, and therefore text description is used.The test cases listed in this ETS have been derived from the DECT Common Interface (CI) Test CaseLibrary (TCL) [47]. In addition as far as physical layer is concerned I-ETS 300 176 [16] applies. AdditionalGAP specific test cases are included where required. The Profile IXIT is based on the DECT CI PIXITsspecified in ETS 300 497 [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-2:1999

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

Page 11ETS 300 494-2: 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".3Definitions 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 pr ETS 300 444 [8].SIST ETS 300 494-2:1999

Page 12ETS 300 494-2: August 19963.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 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 System4Relevant test cases list4.1Network (NWK) layerThis subclause includes lists of the test groups, abstract test cases and test steps relevant for GAP ProfileTest Specification (PTS) - Network (NWK) layer Portable radio Termination (PT) derived fromETS 300 497-7 [24].The page number referenced is the relative page number in the corresponding ETS where the particularitem can be found.NOTE:As ETS 300 497 [18] is a draft ETS, and some changes are likely due to the results ofthe Public Enquiry (PE) phase, page numbers reflecting the exact place in that ETSwhere a test case is to be found are not included in this ETS. They will be added in at alater stage. References when necessary are given based on the particular test casename unique through all test specification ETS 300 497 [18].SIST ETS 300 494-2:1999

Page 13ETS 300 494-2: August 19964.1.1Test Suite Structure (TSS)Table 1TSSSuite Name:nwk_ptStandards Ref:ETS 300 444 [8]; ETS 300 497-7 [24]Profile ICS Ref:ETS 300 474-1 [27]Profile IXIT Ref:ETS 300 494-2Test Method:remoteComments:Test Group ReferenceTest Group ObjectivePT/To check the behaviour of the NWK layer of the PT(IUT)PT/CC/To check the IUT CC-state machine behaviourPT/CC/IT/To check that the IUT CC-state machine provides sufficient conformance forpossible interconnection without trying to perform thorough testingPT/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 IXITPT/CC/BV/To tests the CC entity of the IUT in response to syntactically and contextualcorrect behaviour of the test systemPT/CC/BV/OC/To check the IUT's behaviours to setup an outgoing callPT/CC/BV/IC/To check the IUT's behaviours to setup an incoming callPT/CC/BV/CI/To check the IUT's behaviour in information transfer proceduresPT/CC/BV/CR/To check the IUT's behaviours to release an outgoing/incoming callPT/CC/BV/RS/To check the IUT's behaviour during call related supplementary serviceproceduresPT/CC/BO/To check the behaviour of the CC entity of the IUT in response to themessages that are syntactically correct but not allowed to occur in some statesof the CC proceduresPT/CC/BI/To check the behaviour of the CC entity of the IUT in response to invalidmessagesPT/CC/TI/To verify that the IUT CC timers are with correct values and the IUT is reactingproperly to the expiry of a timerPT/MM/To check the behaviour of the Mobility Management (MM) entity of the IUTPT/MM/IT/To check that the MM entity of the IUT provides sufficient conformance forpossible interconnection without trying to perform thorough testingPT/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 IXITPT/MM/BV/To tests the MM entity of the IUT in response to syntactically and contextualcorrect behaviour of the test systemPT/MM/BV/ID/To check the IUT's behaviour concerning identity proceduresPT/MM/BV/AU/To check the IUT's behaviour concerning the authentication proceduresPT/MM/BV/LO/To check the IUT's behaviour concerning the location proceduresPT/MM/BV/AR/To check the IUT's behaviour concerning the access rights proceduresPT/MM/BV/KA/To check the IUT's behaviour concerning the key allocation procedurePT/MM/BV/CH/To check the IUT's behaviour concerning the ciphering related proceduresPT/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 proceduresPT/MM/BI/To check the IUT in response to invalid MM messagesPT/MM/TI/To verify that the IUT MM timers are with correct values and the IUT is reactingproperly to the expiry of a timer(continued)SIST ETS 300 494-2:1999

Page 14ETS 300 494-2: August 1996Table 1 (concluded)TSSPT/ME/To check the behaviour of the LLME of the IUTPT/ME/IT/To check that LLME of the IUT provides sufficient conformance for possibleinterconnection without trying to perform thorough testingPT/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 IXITPT/ME/BV/To tests the LLME of the IUT in response to syntactically and contextual correctbehaviour of the test systemPT/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 managedproceduresPT/LC/To check the behaviour of the LCE of the IUTPT/LC/IT/To check that LCE of the IUT provides sufficient conformance for possibleinterconnection without trying to perform thorough testingPT/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 IXITPT/LC/BV/To tests the LCE of the IUT in response to syntactically and contextual correctbehaviour of the test systemPT/LC/BV/LE/To check the IUT's behaviour concerning the connection oriented linkestablishment proceduresPT/LC/BV/LR/To check the IUT's behaviour concerning the connection oriented link releaseproceduresPT/LC/BI/To check the IUT in response to invalid LCE messagesPT/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 PT/xx/IT/ and PT/xx/CA/ do not include their own test casesbut only list an appropriate selection of tests from the relevant sub-group with identifier PT/xx/.SIST ETS 300 494-2:1999

Page 15ETS 300 494-2: August 19964.1.2Test case indexTable 2Test Case IndexTest GroupReferenceTest Case IdDescriptionPT/CC/BV/OC/TC_PT_CC_BV_OC_01Outgoing call; T-00, T-01, T-02, T-03, T-04, T-10; piecewise dialling in T-02TC_PT_CC_BV_OC_02Outgoing call; states T-00, T-01, T-10; piece wisedialling in T-10TC_PT_CC_BV_OC_03Outgoing call; states T-00, T-01, T-02, T-10; piece wisedialling in T-02TC_PT_CC_BV_OC_04Outgoing call; U-plane connection upon <> in {CC-SETUP-ACK}PT/CC/BV/IC/TC_PT_CC_BV_IC_01Incoming call; T-01, T-06, T-07, T-08, T-10;<> in T-07TC_PT_CC_BV_IC_02Incoming call; T-01, T-06, T-07, T-08, T-10;<> in {CC-SETUP}PT/CC/BV/CI/TC_PT_CC_BV_CI_01Alerting the user; Incoming call; <> in {CC-SETUP}TC_PT_CC_BV_CI_02Go to pulse invocation in T-02; Outgoing callTC_PT_CC_BV_CI_03Go to pulse invocation in T-10; Outgoing callTC_PT_CC_BV_CI_04Dialling pause indication in T-02; Outgoing callTC_PT_CC_BV_CI_05Dialling pause indication in T-10; Outgoing callTC_PT_CC_BV_CI_06Go to DTMF invocation in T-02; defined tone length;Outgoing callTC_PT_CC_BV_CI_07Go to DTMF invocation in T-10; defined tone length;Outgoing callTC_PT_CC_BV_CI_08Go to DTMF invocation in T-02; infinite tone length;Outgoing callTC_PT_CC_BV_CI_09Go to DTMF invocation in T-10; infinite tone length;Outgoing callTC_PT_CC_BV_CI_10Outgoing normal call; T-02; {CC-INFO], sending <>, "0-9, star, hash mark"TC_PT_CC_BV_CI_11Internal callTC_PT_CC_BV_CI_12T-10; {CC-INFO}, <> standardcharacters handlingTC_PT_CC_BV_CI_13T-10; {CC-INFO}, <> control charactershandlingTC_PT_CC_BV_CI_14T-10; invocation of "Register recall"; {CC-INFO},<>PT/CC/BV/CR/TC_PT_CC_BV_CR_01Outgoing normal call; T-02; FT initiated normal releaseTC_PT_CC_BV_CR_02Outgoing normal call; T-03; FT initiated normal releaseTC_PT_CC_BV_CR_03Outgoing normal call; T-04; FT initiated normal releaseTC_PT_CC_BV_CR_04Incoming call; T-08; FT initiated normal releaseTC_PT_CC_BV_CR_05T-10; FT initiated normal releaseTC_PT_CC_BV_CR_06T-10; IUT initiated normal releaseTC_PT_CC_BV_CR_07T-01; FT initiated abnormal releaseTC_PT_CC_BV_CR_08T-02; FT initiated abnormal releaseTC_PT_CC_BV_CR_09T-10; FT initiated abnormal releaseTC_PT_CC_BV_CR_10T-10; FT initiated partial releaseTC_PT_CC_BV_CR_11T-10; IUT initiated partial releasePT/CC/BV/RS/TC_PT_CC_BV_RS_01T-00; Incoming call; {CC-SETUP} with <>; CLIP handling(continued)SIST ETS 300 494-2:1999

Page 16ETS 300 494-2: August 1996Table 2 (continued)Test Case IndexPT/CC/BO/TC_PT_CC_BO_01T-08; unexpected message {CC-CALL-PROC}; ignoreTC_PT_CC_BO_02T-19; receipt of {CC-RELEASE}; release collision; clearthe callPT/CC/BI/TC_PT_CC_BI_01T-00; {CC-SETUP} mandatory I.E. missing; answerupon with {CC-RELEASE-COM]TC_PT_CC_BI_02T-00; {CC-SETUP} wrong mandatory I.E.; answer uponwith {CC-RELEASE-COM]TC_PT_CC_BI_03T-00; {CC-SETUP}-like message, non {CC-SETUP}unrecognised message type; ignoreTC_PT_CC_BI_04T-00; to short message to contain the complete<>; ignorePT/CC/TI/TC_PT_CC_TI_01T-19; timer P- expiry (± 5% margin); IUT sends{CC-RELEASE-COM}TC_PT_CC_TI_02Outgoing call; T-01; timer P- expiry (± 5%margin); IUT sends {CC-RELEASE-COM}TC_PT_CC_TI_03T-01; restarts P- upon {CC-NOTIFY}TC_PT_CC_TI_04Outgoing call; T-08; timer P- expiry (± 5%margin); IUT sends {CC-RELEASE}PT/MM/BV/ID/TC_PT_MM_BV_ID_01Identity request; IPUI type requested; active IPUIreturnedTC_PT_MM_BV_ID_02Identity request; unavailable id. type requested; noidentity in the replyTC_PT_MM_BV_ID_08Identity request; PARK requested; active PARKreturnedPT/MM/BV/AU/TC_PT_MM_BV_AU_01Authentication of PT; IUT(PT) has no stored ZAP valueand service class infoTC_PT_MM_BV_AU_02Authentication of PT; unacceptable algorithmrequested; rejectTC_PT_MM_BV_AU_03Authentication of PT; IUT(PT) has stored ZAP value;IUT includes ZAP value in the replayTC_PT_MM_BV_AU_04Authentication of PT; ZAP increment handlingTC_PT_MM_BV_AU_05Authentication of PT; ZAP increment handling;unsuccessful authentication of FT; ZAP is notincrementedTC_PT_MM_BV_AU_06Authentication of PT; storage of DCK handlingTC_PT_MM_BV_AU_07Authentication of userTC_PT_MM_BV_AU_08Authentication of FT; IUT initiatedTC_PT_MM_BV_AU_09Authentication of PT; IUT(PT) has stored service classinfo; IUT includes service class info in the replayPT/MM/BV/LO/TC_PT_MM_BV_LO_01Location registration after obtain access rights; a44 anda38=1 at locking; no TPUI assignmentTC_PT_MM_BV_LO_02Location registration after obtain access rights; a44 anda38=1 at locking; TPUI assignmentTC_PT_MM_BV_LO_03Location registration after obtain access rights; a44=1and a38=0 at locking; IUT does not perform locationregistrationTC_PT_MM_BV_LO_04Location registration; no CC activities; location areachanges; a38=1 at locking and at the beginning of theprocedure; no TPUI assignmentTC_PT_MM_BV_LO_05No CC activities; power off; power on; Locationregistration requestTC_PT_MM_BV_LO_06Location registration; unacceptable TPUI assignment;reject(continued)SIST ETS 300 494-2:1999

Page 17ETS 300 494-2: August 1996Table 2 (continued)Test Case IndexTC_PT_MM_BV_LO_07Location registration; entering new location area; IUTdeletes old TPUITC_PT_MM_BV_LO_08Location update suggested by FT; Location registrationinitiated by IUT; a38=1 at locking and at the beginningof the procedureTC_PT_MM_BV_LO_09Location update suggested by FT; Location registrationinitiated by IUT; a38=1 at locking, a38=0 at thebeginning of the procedurePT/MM/BV/AR/TC_PT_MM_BV_AR_01Obtain access rights; a44=1; both sides use ACTC_PT_MM_BV_AR_03Obtain access rights; a44=0; IUT does not initiateobtain access rights procedureTC_PT_MM_BV_AR_05Terminate access rights; FT initiated; IUT(PT) mayauthenticate FTTC_PT_MM_BV_AR_06Terminate access rights; FT initiated; IUT(PT)authenticates FT; authentication fails; terminationrejectedTC_PT_MM_BV_AR_09Obtain access rights; FT assigns ZAP field; IUT storesitTC_PT_MM_BV_AR_10Obtain access rights; FT assigns service class; IUTstores itPT/MM/BV/KA/TC_PT_MM_BV_KA_01Key allocationTC_PT_MM_BV_KA_02Key allocation; <> unacceptable; rejectTC_PT_MM_BV_KA_03Key allocation; implicit authentication of FT fails; key isnot allocatedPT/MM/BV/CH/TC_PT_MM_BV_CH_01Cipher switching; IUT(PT) initiated; "cipher-off" to"cipher-on"TC_PT_MM_BV_CH_02Cipher switching; IUT(PT) initiated; "cipher-on" to"cipher-off"TC_PT_MM_BV_CH_03Cipher switching; FT initiated; "cipher-off" to "cipher-on"TC_PT_MM_BV_CH_04Cipher switching; FT initiated; "cipher-on" to "cipher-off"TC_PT_MM_BV_CH_05Cipher switching; FT initiated; "cipher-off" to "cipher-on";unacceptable algorithm or key; rejectPT/MM/BO/TC_PT_MM_BO_01Location registration request; receipt of {ACCESS-RIGHTS-ACCEPT}; unexpected, ignorePT/MM/BI/TC_PT_MM_BI_01Unrecognised message type; ignoreTC_PT_MM_BI_02"Cipher off"; {CIPHER-REQUEST}, with invalid<>; rejectTC_PT_MM_BI_03Authentication of PT; {AUTH-REQUEST} missing<>; rejectTC_PT_MM_BI_04Obtain access rights; {ACCESS-RIGHTS-ACCEPT},wrong <>; ignorePT/MM/TI/TC_PT_MM_TI_01Key allocation; timer P- expiry (± 5%margin)TC_PT_MM_TI_02Authentication of FT; timer P- expiry (±5% margin)TC_PT_MM_TI_03Location registration; timer P- expiry (±5% margin)TC_PT_MM_TI_04Obtain access rights; timer P- expiry (±5% margin)TC_PT_MM_TI_05Cipher switching; IUT(PT) initiated; timer P- expiry (± 5% margin)PT/ME/BV/TC_PT_ME_BV_01Outgoing call; T-01; Authentication of IUT(PT)performed before answering the setup request(continued)SIST ETS 300 494-2:1999

Page 18ETS 300 494-2: August 1996Table 2 (concluded)Test Case IndexTC_PT_ME_BV_02Cipher switching IUT(PT) initiated; Locate update;location registration initiation after "cipher off"TC_PT_ME_BV_03Obtain access rights; Interrupted by Authentication ofuserTC_PT_ME_BV_04Obtain access rights; Interrupted by Authentication ofIUT(PT)TC_PT_ME_BV_05Outgoing call and authentication of IUT(PT) in parallelTest Case IndexTC_PT_ME_BV_06Outgoing call and cipher switching FT initiated inparallelTC_PT_ME_BV_07Outgoing call; T-01; Cipher switching FT initiatedperformed before answering the setup requestTC_PT_ME_BV_08Outgoing call; T-01; Authentication of user performedbefore answering the setup request; {CC-NOTIFY}restart timer handlingTC_PT_ME_BV_09Cipher on; Store DCK; new DCK not used in the currentcipheringTC_PT_ME_BV_10T-10; a38=1; location area changes; locationregistration request during the call or in T-00TC_PT_ME_BV_11Outgoing call; T-01; Terminate access rights FTinitiated performed before answering the setup requestTC_PT_ME_BV_12T-10; link fails; IUT clears the callTC_PT_ME_BV_13Obtain access rights interrupted by key allocationPT/ME/BO/TC_PT_ME_BO_01Authentication of FT interrupted by {AUTH-REQUEST}from FT; ignorePT/LC/BV/LE/TC_PT_LC_BV_LE_01Direct link establishment; IUT initiatedTC_PT_LC_BV_LE_02Indirect FT initiated link establishmentPT/LC/BV/LR/TC_PT_LC_BV_LR_01Link exists; MM entity ceases to use the link; no otherentity uses the link; IUT maintains the link timeTC_PT_LC_BV_LR_02Link exists; CC entity ceases to use the link; no otherentity uses the link; normal releaseTC_PT_LC_BV_LR_03Link exists; CC entity ceases to use the link; partialrelease agreed; no other entity uses the link; IUTmaintains the link timePT/LC/BI/TC_PT_LC_BI_01Protocol discriminator value error - unsupportedservice; IUT ignoresTC_PT_LC_BI_03{IDENTITY-REQUEST} with illegal transaction id.;ignoreTC_PT_LC_BI_04Obtain access rights; {ACCESS-RIGHTS-ACCEPT}with transaction id. flag '0'; ignorePT/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] du to difficulties of qualifying theIUT behaviour)TC_PT_LC_TI_02MM ceases to use the link; no other entity uses the link;timer expiry (± 5% margin)Detailed Comments:1.The PT is the IUT.SIST ETS 300 494-2:1999

Page 19ETS 300 494-2: August 19964.2Data Link Control (DLC) layerThis subclause includes a list of the abstract test cases relevant for GAP PTS - DLC layer 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-1 [27]Profile IXIT Ref:ETS 300 494-2Test 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'sClass A acknowledged transfer operation are in accordance with the staticconformance requirements and the additional capabilities claimed in thePICS/PIXITDLC/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
...