ETSI EN 300 494-2 V1.2.1 (1999-08)

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

ETSIETSI EN 300 494-2 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.154.2.2Test case index.154.3Medium Access Control (MAC) layer.174.3.1Test suite structure.174.3.2Test case index.184.4Physical (PH) layer.184.4.1Manufacturer declarations.184.4.2Normal Transmitted Power (NTP).194.4.2.1Verdict criteria for IUTs with an integral antenna.194.4.2.2Verdict criteria for IUTs with external antenna connection(s).194.4.3PP radio receiver sensitivity.194.4.4Radio receiver interference performance.194.4.5Receiver intermodulation performance.194.4.6User controlled volume control.195Additional test cases list.205.1Test purposes.205.1.1NWK layer.205.1.2DLC layer.205.1.3MAC layer.205.1.4PH layer.205.2Test cases.205.2.1NWK layer.205.2.2DLC layer.205.2.3MAC layer.205.2.4PH layer.215.2.4.1Receiver sensitivity tolerance of transmitter deviation variations.215.2.4.1.1Definition.215.2.4.1.2Test environment.215.2.4.1.3Method of measurement.215.2.4.1.4Verdict criteria.215.2.4.2Receiver timing tolerance of a PT.225.2.4.2.1Definition.225.2.4.2.2Test environment.225.2.4.2.3Method of measurement, Part 1.225.2.4.2.4Method of measurement, Part 2.235.2.4.2.5Verdict criteria for part 1.235.2.4.2.6Verdict criteria for part 2.235.2.4.3Transmission of Z-field.235.2.4.3.1Definition.235.2.4.3.2Test environment.235.2.4.3.3Method of measurement.24SIST EN 300 494-2 V1.2.1:2003

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

ETSIETSI EN 300 494-2 V1.2.1 (1999-08)5Annex D (normative):System Conformance Statement (SCS) proforma.41D.1Identification summary.41D.1.1SCS identification.41D.1.2IUT identification.41D.1.3Client identification.41D.1.4Supplier identification.42D.1.5Manufacturer identification.42D.1.6Protocols identification.43D.1.7Profile identification.43D.2Miscellaneous system information.43D.2.1Configuration.43D.2.2Other information.44History.45SIST EN 300 494-2 V1.2.1:2003

ETSIETSI EN 300 494-2 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 2 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-2 V1.2.1:2003

ETSIETSI EN 300 494-2 V1.2.1 (1999-08)71ScopeThe present document contains the test specification for Digital Enhanced Cordless 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 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-2 V1.2.1:2003

ETSIETSI EN 300 494-2 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, Parts 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-2 V1.2.1:2003

ETSIETSI EN 300 494-2 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 SuiteBERBit Error RateCCCall ControlCICommon InterfaceDCKDerived Cipher KeyDLCData Link ControlEUTEquipment Under TestFTFixed radio TerminationGAPGeneric Access ProfileICSImplementation Conformance StatementIPUIInternational Portable User IdentityIUTImplementation Under TestIXITImplementation eXtra Information for TestingLCELink Control EntityLLMELower Layer Management EntityLTLower TesterMACMedium Access ControlMMMobility ManagementNLFNew Link FlagNWKNetworkPARKPortable Access Rights KeyPCTRProfile Conformance Test ReportPHPhysicalPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingPTPortable radio TerminationPSTSProfile Specific Test SpecificationPTSProfile Test SpecificationRFRadio FrequencyRFPRadio Fixed PartSARISecondary Access Rights IdentitySCSSystem Conformance StatementSCTRSystem Conformance Test ReportSIST EN 300 494-2 V1.2.1:2003

ETSIETSI EN 300 494-2 V1.2.1 (1999-08)10SUTSystem Under TestTPUITemporary Portable User IdentityTSTest System4Relevant test cases list4.1Network (NWK) layerThis subclause includes lists of the test groups, and abstract test cases relevant for GAP Profile Test Specification(PTS) - Network (NWK) layer Portable radio Termination (PT) derived from EN 300 497-7 [24].NOTE:References when necessary are given based on the particular test case name unique through all testspecification EN 300 497 [18] to [26].4.1.1Test Suite Structure (TSS)Table 1TSSSuite Name:nwk_ptStandards Ref:EN 300 444 [8]; EN 300 497-7 [24]Profile ICS Ref:ETS 300 474 [27]Profile IXIT Ref:EN 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 for possibleinterconnection 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 additional capabilitiesclaimed in the PROFILE ICS/PROFILE IXITPT/CC/BV/To test the CC entity of the IUT in response to syntactically and contextual correctbehaviour 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 service proceduresPT/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 proceduresPT/CC/BI/To check the behaviour of the CC entity of the IUT in response to invalid messagesPT/CC/TI/To verify that the IUT CC timers are with correct values and the IUT is reacting properlyto 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 for possibleinterconnection 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 additional capabilitiesclaimed in the PROFILE ICS/PROFILE IXITPT/MM/BV/To test the MM entity of the IUT in response to syntactically and contextual correctbehaviour 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 syntactically correctbut not allowed to occur in some phase of the MM proceduresSIST EN 300 494-2 V1.2.1:2003

ETSIETSI EN 300 494-2 V1.2.1 (1999-08)11TSSSuite Name:nwk_ptStandards Ref:EN 300 444 [8]; EN 300 497-7 [24]Profile ICS Ref:ETS 300 474 [27]Profile IXIT Ref:EN 300 494-2Test Method:remoteComments:Test Group ReferenceTest Group ObjectivePT/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 reacting properlyto the expiry of a timerPT/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 additional capabilitiesclaimed in the PROFILE ICS/PROFILE IXITPT/ME/BV/To test 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 syntactically correctbut not allowed to occur in some phase of the LLME managed proceduresPT/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 in accordancewith the static conformance requirements and the additional capabilities claimed in thePROFILE ICS/PROFILE IXITPT/LC/BV/To test the LCE of the IUT in response to syntactically and contextual correct behaviourof the test systemPT/LC/BV/LE/To check the IUT's behaviour concerning the connection oriented link establishmentproceduresPT/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:The sub-sub-groups with identifiers PT/xx/IT/ and PT/xx/CA/ do not include their own test cases but only list anappropriate selection of tests from the relevant sub-group with identifier PT/xx/.4.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; piece wisedialling in T-02TC_PT_CC_BV_OC_02Outgoing call; states T-00, T-01, T-10; piece wise dialling inT-10TC_PT_CC_BV_OC_03Outgoing call; states T-00, T-01, T-02, T-10; piece wisedialling in T-02 and T-10TC_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; <> inT-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 callSIST EN 300 494-2 V1.2.1:2003

ETSIETSI EN 300 494-2 V1.2.1 (1999-08)12Test Case IndexTest GroupReferenceTest Case IdDescriptionTC_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; OutgoingcallTC_PT_CC_BV_CI_09Go to DTMF invocation in T-10; infinite tone length; OutgoingcallTC_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}, <> standard charactershandlingTC_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 handlingPT/CC/BO/TC_PT_CC_BO_01T-03; unexpected message {CC-CALL-PROC}; ignoreTC_PT_CC_BO_02T-19; receipt of {CC-RELEASE}; release collision; clear thecallPT/CC/BI/TC_PT_CC_BI_01T-00; {CC-SETUP} mandatory I.E. missing; answer upon with{CC-RELEASE-COM]TC_PT_CC_BI_02T-00; {CC-SETUP} wrong mandatory I.E.; answer upon with{CC-RELEASE-COM]TC_PT_CC_BI_03T-00; {CC-SETUP}-like message, non {CC-SETUP}unrecognized message type; ignorePT/CC/TI/TC_PT_CC_TI_01T-19; timer P- expiry (-10 % margin); IUT sends{CC-RELEASE-COM}TC_PT_CC_TI_02Outgoing call; T-01; timer P- expiry (-10 % 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 (-10 % margin);IUT sends {CC-RELEASE}PT/MM/BV/ID/TC_PT_MM_BV_ID_01Identity request; IPUI type requested; active IPUI returnedTC_PT_MM_BV_ID_02Identity request; unavailable id. type requested; no identity inthe replyTC_PT_MM_BV_ID_08Identity request; PARK requested; active PARK returnedPT/MM/BV/AU/TC_PT_MM_BV_AU_01Authentication of PT; IUT(PT) has no stored ZAP value andservice class infoTC_PT_MM_BV_AU_02Authentication of PT; unacceptable algorithm requested;rejectTC_PT_MM_BV_AU_03Authentication of PT; IUT(PT) has stored ZAP value; IUTincludes 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; unsuccessfulauthentication of FT; ZAP is not incrementedTC_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 initiatedSIST EN 300 494-2 V1.2.1:2003

ETSIETSI EN 300 494-2 V1.2.1 (1999-08)13Test Case IndexTest GroupReferenceTest Case IdDescriptionTC_PT_MM_BV_AU_09Authentication of PT; IUT(PT) has stored service class info;IUT includes service class info in the replyPT/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=1 anda38=0 at locking; IUT does not perform location registrationTC_PT_MM_BV_LO_04Location registration; no CC activities; location area changes;a38=1 at locking and at the beginning of the procedure; noTPUI assignmentTC_PT_MM_BV_LO_05No CC activities; power off; power on; Location registrationrequestTC_PT_MM_BV_LO_06Location registration; unacceptable TPUI assignment; rejectTC_PT_MM_BV_LO_07Location registration; entering new location area; IUT deletesold TPUI - no TPUI in identity reply sent from IUTTC_PT_MM_BV_LO_08Location update suggested by FT; Location registrationinitiated by IUT; a38=1 at locking and at the beginning of theprocedureTC_PT_MM_BV_LO_09Location update suggested by FT; Location registrationinitiated by IUT; a38=1 at locking, a38=0 at the beginning ofthe procedureTC_PT_MM_BV_LO_10Verify that the IUT can correctly perform location registrationand a following outgoing call when it uses SARI as themeans to lock to the LTPT/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 initiate obtainaccess 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) authenticatesFT; authentication fails; termination rejectedTC_PT_MM_BV_AR_09Obtain access rights; FT assigns ZAP field; IUT stores itTC_PT_MM_BV_AR_10Obtain access rights; FT assigns service class; IUT stores 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 is notallocatedPT/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; rejectTC_PT_MM_BV_CH_08Cipher switching; IUT (PT) initiated; "cipher-off" to "cipher-on"fails; release of linkTC_PT_MM_BV_CH_09Cipher switching; IUT (PT) initiated; "cipher-off" to"cipher-on"; successful inter-cell bearer handoverTC_PT_MM_BV_CH_10Cipher switching; IUT (PT) initiated; "cipher-off" to"cipher-on"; successful intra-cell bearer handoverTC_PT_MM_BV_CH_11Cipher switching; IUT (PT) initiated; "cipher-off" to"cipher-on"; "cipher-on" to "cipher-off" fails; release of linkTC_PT_MM_BV_CH_12Cipher switching; FT initiated; "cipher-off" to "cipher-on" fails;release of linkTC_PT_MM_BV_CH_13Cipher switching; FT initiated; "cipher-off" to "cipher-on";successful inter-cell bearer handoverTC_PT_MM_BV_CH_14Cipher switching; FT initiated; "cipher-off" to "cipher-on";successful intra-cell bearer handoverTC_PT_MM_BV_CH_15Cipher switching; FT initiated; "cipher-off" to "cipher-on";"cipher-on" to "cipher-off" fails; release of linkPT/MM/BO/TC_PT_MM_BO_01Location registration request; receipt of{ACCES-RIGHT-ACCEPT}; unexpected, ignorePT/MM/BI/TC_PT_MM_BI_01Unrecognized message type; ignoreSIST EN 300 494-2 V1.2.1:2003

ETSIETSI EN 300 494-2 V1.2.1 (1999-08)14Test Case IndexTest GroupReferenceTest Case IdDescriptionTC_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_03Location registration; just before timer P-expiry (-10 % margin)TC_PT_MM_TI_04Obtain access rights; just before timer P-expiry (-10 % margin)TC_PT_MM_TI_05Cipher switching; IUT(PT) initiated; timer P-expiry (-10 % margin)PT/ME/BV/TC_PT_ME_BV_01Outgoing call; T-01; Authentication of IUT(PT) performedbefore answering the setup requestTC_PT_ME_BV_03Obtain access rights; Interrupted by Authentication of userTC_PT_ME_BV_04Obtain access rights; Interrupted by Authentication ofIUT(PT)TC_PT_ME_BV_05Outgoing call and authentication of IUT(PT) in parallelTC_PT_ME_BV_06Outgoing call and cipher switching FT initiated in parallelTC_PT_ME_BV_07Outgoing call; T-01; Cipher switching FT initiated performedbefore answering the setup requestTC_PT_ME_BV_09Cipher on; Store DCK; new DCK not used in the currentcipheringTC_PT_ME_BV_10T-10; a38=1; location area changes; location registrationrequest during the call or in T-00TC_PT_ME_BV_11Outgoing call; T-01; Terminate access rights FT initiatedperformed 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} fromFT; 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 other entityuses the link; IUT maintains the link timeTC_PT_LC_BV_LR_02Link exists; CC entity ceases to use the link; no other entityuses the link; normal releaseTC_PT_LC_BV_LR_03Link exists; CC entity ceases to use the link; partial releaseagreed; no other entity uses the link; IUT maintains the link timePT/LC/B
...