ETSI EN 300 497-6 V0.3.2 (1999-09)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.37Digital 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)33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:EN 300 497-6 Version 0.3.2SIST EN 300 497-6 V0.3.2:2003en01-december-2003SIST EN 300 497-6 V0.3.2:2003SLOVENSKI
STANDARD
ETSIETSI EN 300 497-6 V0.3.2 (1999-09)2ReferenceREN/DECT-040131-6 (4lpi011c.PDF)KeywordsDECT, terminal, testing, TSS&TP, networkETSIPostal 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 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)3ContentsIntellectual Property Rights.5Foreword.51Scope.62References.63Definitions and abbreviations.73.1DECT definitions.73.2Abbreviations.74Test Suite Structure (TSS).94.1TSS overview.94.2Test groups.104.2.1Protocol groups.104.2.1.1Call Control (CC).104.2.1.2Mobility Management (MM).104.2.1.3Lower layer Management Entity (ME).104.2.1.4Link Control (LC).104.2.1.5Call Independent Supplementary Services (CISS).104.2.1.6Connection Oriented Message Services (COMS).104.2.1.7Connectionless Message Services (CLMS).104.2.2Main test groups.104.2.2.1Basic InTerconnection tests (IT).104.2.2.2Capability tests (CA).104.2.2.3Valid Behaviour tests (BV).104.2.2.4Invalid Behaviour tests (BI).114.2.2.5InOpportune Behaviour tests (BO).114.2.2.6TImer expiry and counter mismatch tests (TI).115Test Purposes (TPs).115.1Introduction.115.1.1TP definition conventions.115.1.2References.115.1.3TP naming conventions.125.2CC test purposes.125.2.1CC/IT test purposes.135.2.2CC/CA test purposes.135.2.3CC/BV test purposes.135.2.3.1CC/BV/OC test purposes.145.2.3.2CC/BV/IC test purposes.155.2.3.3CC/BV/CI test purposes.165.2.3.4CC/BV/CR test purposes.185.2.3.5CC/BV/SC test purposes.185.2.3.6CC/BV/PM test purposes.185.2.3.7CC/BV/RS test purposes.195.2.3.8CC/BV/HP test purposes.195.2.4CC/BO test purposes.225.2.5CC/BI test purposes.225.2.6CC/TI test purposes.235.3MM test purposes.235.3.1MM/IT test purposes.235.3.2MM/CA test purposes.235.3.3MM/BV test purposes.245.3.3.1MM/BV/ID test purposes.245.3.3.2MM/BV/AU test purposes.255.3.3.3MM/BV/LO test purposes.265.3.3.4MM/BV/AR test purposes.28SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)45.3.3.5MM/BV/KA test purposes.295.3.3.6MM/BV/PR test purposes.295.3.3.7MM/BV/CH test purposes.305.3.4MM/BO test purposes.315.3.5MM/BI test purposes.315.3.6MM/TI test purposes.325.4ME test purposes.325.4.1ME/BV test purposes.325.4.2ME/BO test purposes.335.5LC test purposes.345.5.1LC/BV test purposes.345.5.1.1LC/BV/LE test purposes.345.5.1.2LC/BV/LR test purposes.345.5.1.3LC/BV/LS test purposes.355.5.1.4LC/BV/LL test purposes.355.5.2LC/BI test purposes.355.5.3LC/TI test purposes.365.6IS test purposes.365.6AIS/BV test purposes.365.7MO test purposes.375.8CL test purposes.375.9CL/BV test purposes.37Bibliography.38History.39SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)5Intellectual 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 6 of a multi-part EN covering the Common Interface (CI) Test Case Library (TCL), asidentified below:Part 1:"Test Suite Structure (TSS) and Test Purposes (TP) for Medium Access Control (MAC) layer";Part 2:"Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Portable radio Termination (PT)";Part 3:"Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Fixed radio Termination (FT)";Part 4:"Test Suite Structure (TSS) and Test Purposes (TP) - Data Link Control (DLC) layer";Part 5:"Abstract Test Suite (ATS) - Data Link Control (DLC) layer";Part 6:"Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer - Portable radioTermination (PT)";Part 7:"Abstract Test Suite (ATS) for Network (NWK) layer - Portable radio Termination (PT)";Part 8:"Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer - Fixed radio Termination(FT)";Part 9:"Abstract Test Suite (ATS) for Network (NWK) layer - Fixed radio Termination (FT)".National transposition datesDate of adoption of this EN:27 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 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)61ScopeThe present document contains the test specification for the Digital Enhanced Cordless Telecommunications (DECT)(EN 300 175 parts 1 to 8 [1] to [8]).The objective of this test specification is to provide a basis for approval tests for DECT equipment giving a highprobability of air interface inter-operability between different manufacturer's DECT equipment. This test specificationdefines the Test Suite Structure (TSS) and Test Purposes (TP) for testing of the Network (NWK) layer at the Portableradio Termination (PT).The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [12]) as well as the ETSI rules forconformance testing (ETS 300 406 [9]) are used as a basis for the test methodology.Test specifications for the Physical layer (PHL) are provided in other DECT standards.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 175-8: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 8: Speech coding and transmission".[9]ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and profile conformancetesting specifications; Standardization methodology".[10]EN 300 444: "Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile(GAP)".[11]EN 300 824: "Digital Enhanced Cordless Telecommunications (DECT), Cordless TerminalMobility (CTM); CTM Access Profile (CAP)".SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)7[12]ISO/IEC 9646-1: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 1: General concepts".[13]ISO/IEC 9646-2: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 2: Abstract Test Suite Specification".3Definitions and abbreviations3.1DECT definitionsFor the purposes of the present document, the terms and definitions given in ISO/IEC 9646-1 [12],ISO/IEC 9646-2 [13], EN 300 175-1 [1], EN 300 175-5 [5], EN 300 175-6 [6] and EN 300 175-7 [7] apply.3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:ACAuthentication CodeARAccess RightsAUAuthenticationBIInvalid BehaviourBOInopportune BehaviourBVValid BehaviourCACapabilityCCCall ControlCHCipheringCICall InformationCISSCall Independent Supplementary ServicesCLMSConnectionless Message ServicesCOMSConnection Oriented Message ServicesCRCall ReleaseDECTDigital Enhanced Cordless TelecommunicationsFTFixed radio TerminationHPHandover ProcedureICIncoming CallIDIdentificationIPUIInternational Portable User IdentityIUTImplementation Under TestKAKey AllocationLCLink ControlLEconnection oriented Link EstablishmentLLconnectionless Link controlLOLocationLRconnection oriented Link ReleaseLSconnection oriented Link Suspend and resumeMEManagement EntityMMMobility ManagementMOConnection Oriented Message ServicesNWKNetwork layerOCOutgoing CallPARKPortable Access Rights KeyPDUProtocol Data UnitPHLPhysical layerPICSProtocol Implementation Conformance StatementSIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)8PIXITProtocol Implementation Extra Information for TestingPMPacket ModePRParameter RetrievalPTPortable radio TerminationRSCall Related Supplementary ServicesSCService ChangeTPTest PurposeTSSTest Suite StructureUAKUser Authentication KeySIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)94Test Suite Structure (TSS)4.1TSS overviewCCLCICCICRSCBVBIITBVBITIBVBVTIISCLLRLSRSBOTIBIBVMOBVLLLEAUPRKACACABOMMLOPMPTMEBOOCITIDARCHHPFigure 1: TSSSIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)104.2Test groups4.2.1Protocol groups4.2.1.1Call Control (CC)Reference: EN 300 175-5 [5], subclause 5.2, clause 9 and subclause 15.7.4.2.1.2Mobility Management (MM)Reference: EN 300 175-5 [5], subclause 5.6 and clause 13.4.2.1.3Lower layer Management Entity (ME)Reference: EN 300 175-5 [5], clause 15.4.2.1.4Link Control (LC)Reference: EN 300 175-5 [5], subclause 5.7 and clause 14.4.2.1.5Call Independent Supplementary Services (CISS)Reference: EN 300 175-5 [5], subclauses 5.3 and 10.4.2.2.4.2.1.6Connection Oriented Message Services (COMS)Reference: EN 300 175-5 [5], subclause 5.4 and clause 11.4.2.1.7Connectionless Message Services (CLMS)Reference: EN 300 175-5 [5], subclause 5.5 and clause 12.4.2.2Main test groups4.2.2.1Basic InTerconnection tests (IT)IT tests provide limited testing of an Implementation Under Test (IUT) in order to establish that there is sufficientconformance for possible interconnection without trying to perform thorough testing. In particular, only those test caseswill be executed which will assure the sufficient interconnection between the IUT of the NWK layer and the test systemexists, so that the rest of the test cases can then be put into execution.4.2.2.2Capability tests (CA)CA tests provide limited testing that the observable capabilities of the IUT are in accordance with the static conformancerequirements and the additional capabilities claimed in the Protocol Implementation Conformance Statement / ProtocolImplementation Extra Information for Testing (PICS / PIXIT). In particular, this test group can be regarded as a set ofspot checks for all the capabilities of the IUT stated in the PICS / PIXIT. Scope of the test group is the observablecapabilities of the IUT with respect to NWK layer connection, call control, and the mobility management.4.2.2.3Valid Behaviour tests (BV)BV group tests an IUT in response to valid behaviour of the test system. "Valid" means that a test event is syntacticallyand contextually correct. All test cases in the valid behaviour group are intended to verify as thoroughly as possible thevarious functions of the protocol.SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)114.2.2.4Invalid Behaviour tests (BI)BI group is intended to verify that the IUT is able to react properly in case an invalid protocol data unit (message)occurring. Invalid Protocol Data Unit (PDU) here means syntactically or semantically invalid test events generated bythe test system. A syntactically or semantically invalid test event regardless of the current state is not allowed.4.2.2.5InOpportune Behaviour tests (BO)BO test group is intended to verify that the IUT is able to react properly in case an inopportune test event occurring.Such an event is syntactically correct, but occurs when it is not allowed.4.2.2.6TImer expiry and counter mismatch tests (TI)Different timers and counters are defined to supervise the various state transitions. This test subgroup is intended toverify that the IUT is reacting properly to an expiry of one of the timers or counters mismatch.5Test Purposes (TPs)Each test case is allocated directly under a defined TP.5.1Introduction5.1.1TP definition conventionsThe TPs are defined following particular rules as shown in table 1.Table 1: TP definition rulesTP Id according to theTP naming conventionsReferenceInitial conditionStimulusExpected behaviourTP Id:Reference:Condition:Stimulus:Expected behaviour:The TP Id is a unique identifier it shall be specified according to the TP namingconventions defined in the subclause below.The reference should contain the references of the subject to be validated by the actual TP(specification reference, clause, paragraph).The condition defines in which initial state the IUT has to be to apply the actual TP.The stimulus defines the test event to which the TP is related.Definition of the events that are expected from the IUT to conform to the base specification.5.1.2ReferencesSubclause 5.1.2 defines the use of references given in the TPs. The structure provides the interrelationship with:-the source EN giving the clause / subclause reference; and-the profile EN giving the clause / subclause reference.SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)125.1.3TP naming conventionsThe identifier of the TP is built according to table 2.Table 2: TP naming conventionTP///// = type of radio terminationPTPortable radio Termination = functional moduleCCCall ControlMMMobility ManagementMELower Layer Management EntityLCLink Control EntityISCall Independent Supplementary ServicesMOConnection Oriented Message ServiceCLConnectionless Message Servicex= Type of testingITBasic Interconnection TestsCACapability TestsBVValid Behaviour TestsBOInopportune Behaviour TestsBIInvalid Behaviour TestsTITimer expiry and counter mismatch testss= test subgroupOCOutgoing Call establishmentICIncoming Call establishmentCICall InformationCRCall ReleaseSCService ChangePMPacket ModeRSCall Related Supplementary servicesHPHandover ProcedureIDIdentificationAUAuthenticationLOLocationARAccess RightsKAKey AllocationPRParameter RetrievalCHCipheringLEConnection oriented Link EstablishmentLRConnection oriented Link ReleaseLSConnection oriented Link Suspend and resumeLLConnectionLess Link Control = sequential number(01-99)Test Purpose Number5.2CC test purposesTest group objectives:To check the behaviour of the CC module of the IUT.SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)13Subgroups:-IT;-CA;-BV;-BO;-BI;-TI;-HP.5.2.1CC/IT test purposesThere are no test purposes defined for this group in the present document.5.2.2CC/CA test purposesThere are no test purposes defined for this group in the present document.5.2.3CC/BV test purposesSubgroups:-OC;-IC;-CI;-CR;-SC;-PM;-RS.SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)145.2.3.1CC/BV/OC test purposesTest subgroup objectives:To check the IUT's behaviours to setup an outgoing call.Test purposes:TP/PT/CC/BV/OC-01EN 300 175-5 [5], subclause 9.1 - subclause 9.2 - subclause 9.3.1EN 300 444 [10], subclause 8.1, figure 1Initial state: T-00Verify that the IUT is able to perform a CC-state transition from the T-00 state to T-10state via T-01, T-02, T-03 and T-04 for an outgoing normal call set-up using piece-wisemethod to transfer dialling information in state T-02.TP/PT/CC/BV/OC-02EN 300 175-5 [5], subclause 9.1 - subclause 9.2 - subclause 9.3.1EN 300 444 [10], subclause 8.1, figure 2Initial state: T-00Verify that the IUT is able to perform a CC-state transition from the T-00 state to T-10state via T-01 for an outgoing normal call set-up using piece-wise method to transferdialling information in state T-10.TP/PT/CC/BV/OC-03EN 300 175-5 [5], subclause 9.1 - subclause 9.2 - subclause 9.3.1EN 300 444 [10], subclause 8.1, figure 3Initial state: T-00Verify that the IUT is able to perform a CC-state transition from the T-00 state to T-10state via T-01 and T-02 for an outgoing normal call set-up using piece-wise method totransfer dialling information in states T-02 and T-10.TP/PT/CC/BV/OC-04EN 300 175-5 [5], subclause 9.3.1.4 - subclause 9.3.1.5,EN 300 444 [10], subclause 8.3, figure 9, table 11Initial state: T-01Verify that the IUT is able to connect the U-plane on receipt of the {CC-SETUP-ACK}message with the information element <> containing"in-band information or appropriate pattern now available".TP/PT/CC/BV/OC-06Previously existing TCL testDECT/T (98) 17, page 6CAP feature N.2EN 300 824 [11], subclause 9.2, table 9 - subclause 14.6Initial state: T-00LT simulates one FT the IUT has no subscription to. The LT shall transmit the extendedhigher layer capabilities bit a40 set to 1 prior to IUT locking. IUT may be or may be notlocked. Verify that the IUT is able, prior to subscription, to perform a CC-state transitionfrom the T-00 state to T-10 state for an outgoing emergency call set-up.TP/PT/CC/BV/OC-07Previously existing TCL testDECT/T (98) 17, page 6CAP feature N.2EN 300 824 [11], subclause 9.2, table 10Initial state: T-00The LT shall transmit the extended higher layer capabilities bit a40 set to 1 prior to IUTlocking. Verify that the IUT is able, when it has subscription record in FT, to perform aCC-state transition from the T-00 state to T-10 state for an outgoing emergency callset-up.TP/PT/CC/BV/OC-50TP/PT/CC/BV/OC-06aDECT/T (98) 17, page 6CAP feature N.2EN 300 824 [11], subclause 9.2, table 9 - subclause 14.6Initial state: T-00LT simulates one FT the IUT has no subscription to. The LT shall transmit the extendedhigher layer capabilities bit a40 set to 0 prior to IUT locking. Verify that the IUT does notinitiate, prior to subscription, emergency call set-up.SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)155.2.3.2CC/BV/IC test purposesTest subgroup objectives:To check the IUT's behaviours to setup an incoming call.Test purposes:TP/PT/CC/BV/IC-01EN 300 175-5 [5], subclause 9.1 - subclause 9.2 - subclause 9.3.2EN 300 444 [10], subclause 8.11, figure 28Initial state: T-00Verify that the IUT is able to process an incoming call via the states T-06, T-07 and -08to the state T-10, on receipt of the information element <> in the {C-INFO}messageTP/PT/CC/BV/IC-02EN 300 175-5 [5], subclause 9.1 - subclause 9.2 - subclause 9.3.2EN 300 444 [10], subclause 8.11, figure 29Initial state: T-00Verify that the IUT is able to process an incoming call via the states T-06, T-07 and -08to the state T-10. The information element <> is in the {CC-SETUP}message.TP/PT/CC/BV/IC-03EN 300 175-5 [5], subclause 9.3.2.4EN 300 444 [10], subclause 8.12Initial state: T-00Verify that the IUT in case of incoming call, is able to connect the U-plane on receipt ofthe {CC-SETUP} message with the information element <>containing "in-band information or appropriate pattern now available".TP/PT/CC/BV/IC-04EN 300 175-5 [5], subclause 9.3.2.4EN 300 444 [10], subclause 8.14Initial state: T-00Verify that the IUT in case of incoming call, is able to connect the U-plane on receipt ofa {CC-INFO} message with the information element <>containing "in-band information or appropriate pattern now available".SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)165.2.3.3CC/BV/CI test purposesTest subgroup objectives:To check the IUT's behaviours for information transfer.Test purposes:TP/PT/CC/BV/CI-01EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.13Initial state: T-06Verify that the IUT is able to alert the user of an incoming call, when the informationelement <> is present in the {CC-SETUP} message.TP/PT/CC/BV/CI-02EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: T-02Verify that the IUT, after the user has invoked pulse (decadic) dialling, sends a{CC-INFO} message with a <> information element containingkeypad-info '12H' (goto pulse).(feature N.23 in EN 300 444 [10])TP/PT/CC/BV/CI-03EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: T-10Verify that the IUT, after the user has invoked pulse (decadic) dialling, sends a{CC-INFO} message with a <> information element containingkeypad-info '12H' (goto pulse).(feature N.23 in EN 300 444 [10])TP/PT/CC/BV/CI-04EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: T-02Verify that the IUT, after the user has invoked dialling pause, sends a {CC-INFO}message with a <> information element containing keypad-info '05H'(dialling pause).(feature N.7 in EN 300 444 [10])TP/PT/CC/BV/CI-05EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: T-10Verify that the IUT, after the user has invoked dialling pause, sends a {CC-INFO}message with a <> information element containing keypad-info '05H'(dialling pause).(feature N.7 in EN 300 444 [10])TP/PT/CC/BV/CI-06EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: T-02Verify that the IUT, after the user has invoked DTMF dialling with defined tone length,sends a {CC-INFO} message with a <> information elementcontaining keypad-info '14H' (goto DTMF, defined tone length).(feature N.6 in EN 300 444 [10])TP/PT/CC/BV/CI-07EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: T-10Verify that the IUT, after the user has invoked DTMF dialling with defined tone length,sends a {CC-INFO} message with a <> information elementcontaining keypad-info '14H' (goto DTMF, defined tone length).(feature N.6 in EN 300 444 [10])TP/PT/CC/BV/CI-08EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: T-02Verify that the IUT, after the user has invoked DTMF dialling with defined tone length,sends a {CC-INFO} message with a <> information elementcontaining keypad-info '16H' (goto DTMF, infinite tone length).(feature N.22 in EN 300 444 [10])SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)17TP/PT/CC/BV/CI-09EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: T-10Verify that the IUT, after the user has invoked DTMF dialling with defined tone length,sends a {CC-INFO} message with a <> information elementcontaining keypad-info '16H' (goto DTMF, infinite tone length).(feature N.22 in EN 300 444 [10])TP/PT/CC/BV/CI-10EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: T-02Verify that the IUT, after the user has invoked the sending of the basic digits (0-9, star,hash mark), sends one or more {CC-INFO} messages with <>information elements containing the basic digits.(feature N.4 in EN 300 444 [10])TP/PT/CC/BV/CI-11EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.18, table 30, table 31Initial state: T-00Verify that the IUT, after the user has invoked an internal call, performs one of thepossible internal call setups, as described in EN 300 444 [10], subclause 8.18, table 30and 31.PT can either send internal call specification in the CC-SETUP PDU, or in the CC-INFOPDU later onTP/PT/CC/BV/CI-12Existing validated GAP testDECT/T (98) 17, page 7GAP/CAP feature N.3EN 300 444 [10], subclause 8.16, table 27EN 300 824 [11], subclause 9.3, table 11Initial state: T-10Verify that the IUT, on reception of <> information elements,containing standard characters in {CC-INFO} messages, is able to show thesecharacters on the display.TP/PT/CC/BV/CI-13Existing validated GAP testDECT/T (98) 17, page 7GAP/CAP feature N.3EN 300 444 [10], subclause 8.16, table 27EN 300 824 [11], subclause 9.3, table 11Initial state: T-10Verify that the IUT, on reception of <> information elements,containing control characters in {CC-INFO} messages, is able to understand and reactupon these characters.TP/PT/CC/BV/CI-14EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: T-10Verify that the IUT, after invocation of 'register recall', is able to activate the featureregister recall in a {CC-INFO} message.SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)185.2.3.4CC/BV/CR test purposesTest subgroup objectives:To check the IUT's behaviour to release an outgoing and incoming call.Test purposes:TP/PT/CC/BV/CR-01EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.3.2.4Initial state: T-02Verify that the IUT is able to process a FT initiated normal release.TP/PT/CC/BV/CR-02EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.7Initial state: T-03Verify that the IUT is able to process a FT initiated normal release.TP/PT/CC/BV/CR-03EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.7Initial state: T-04Verify that the IUT is able to process a FT initiated normal release.TP/PT/CC/BV/CR-04EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.7Initial state: T-08Verify that the IUT is able to process a FT initiated normal release.TP/PT/CC/BV/CR-05EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.7Initial state: T-10Verify that the IUT is able to process a FT initiated normal release.TP/PT/CC/BV/CR-06EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.7Initial state: T-10Verify that the IUT is able to process an IUT initiated normal release.TP/PT/CC/BV/CR-07EN 300 175-5 [5], subclause 9.5.2EN 300 444 [10], subclause 8.2.2.3Initial state: T-01Verify that the IUT is able to process a FT initiated abnormal release.TP/PT/CC/BV/CR-08EN 300 175-5 [5], subclause 9.5.2EN 300 444 [10], subclause 8.3.2.2Initial state: T-02Verify that the IUT is able to process a FT initiated abnormal release.TP/PT/CC/BV/CR-09EN 300 175-5 [5], subclause 9.5.2EN 300 444 [10], subclause 8.8Initial state: T-10Verify that the IUT is able to process a FT initiated abnormal release.TP/PT/CC/BV/CR-10EN 300 175-5 [5], subclause 14.2.7EN 300 444 [10], subclause 8.9Initial state: T-10Verify that the IUT is able to process a FT initiated partial release.TP/PT/CC/BV/CR-11EN 300 175-5 [5], subclause 14.2.7EN 300 444 [10], subclause 8.9Initial state: T-10Verify that the IUT is able to process an IUT initiated partial release.5.2.3.5CC/BV/SC test purposesThere are no test purposes defined for this group in the present document.5.2.3.6CC/BV/PM test purposesThere are no test purposes defined for this group in the present document.SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)195.2.3.7CC/BV/RS test purposesTest subgroup objectives:To check the IUT's behaviour during any call related procedures.Test purposes:TP/PT/CC/BV/RS-01Existing validated GAP testDECT/T (98) 17, page 3EN 300 444 [10], subclause 8.12, table 21EN 300 824 [11], subclause 7.7, table 3Initial state: T-00Verify that the IUT shows the calling party number correctly on receipt of calling partynumber indication before accepting a call.(feature N.30 in EN 300 444 [10]5.2.3.8CC/BV/HP test purposesTest subgroup objectives:To check the IUT's behaviour during external handover.Test purposes:TP/PT/CC/BV/HP-50CAP/PT/NWK/01.1DECT/T (98) 17, page 3CAP feature N.1 (Handover candidate indication)EN 300 824 [11], subclause 9.1.1.1Initial state: T-00Verify that the IUT is able to perform the external handover call setup procedure. Theexternal handover information will have been provided to the IUT in<> and <> information elements in aCC-SETUP-ACK message during establishment of the outgoing call.TP/PT/CC/BV/HP-51CAP/PT/NWK/01.2DECT/T (98) 17, page 3CAP feature N.1 (Handover candidate indication)EN 300 824 [11], subclause 9.1.1.1Initial state: T-00Verify that the IUT is able to perform the external handover call setup procedure. Theexternal handover information will have been provided to the IUT in<> and <> information elements in a CC-INFOmessage during establishment of the outgoing call.TP/PT/CC/BV/HP-52CAP/PT/NWK/01.3DECT/T (98) 17, page 3CAP feature N.1 (Handover candidate indication)EN 300 824 [11], subclause 9.1.1.1Initial state: T-00Verify that the IUT is able to perform the external handover call setup procedure. Theexternal handover information will have been provided to the IUT in<> and <> information elements in aCC-CONNECT message during establishment of the outgoing call.TP/PT/CC/BV/HP-53CAP/PT/NWK/02.1DECT/T (98) 17, page 3CAP feature N.1 (Handover candidate indication)EN 300 824 [11], subclause 9.1.1.1Initial state: T-00Verify that the IUT is able to perform the external handover call setup procedure. Theexternal handover information will have been provided to the IUT in<> and <> information elements in aCC-SETUP message during establishment of the incoming call.TP/PT/CC/BV/HP-54CAP/PT/NWK/02.2DECT/T (98) 17, page 4CAP feature N.1 (Handover candidate indication)EN 300 824 [11], subclause 9.1.1.1Initial state: T-00Verify that the IUT is able to perform the external handover call setup procedure. Theexternal handover information will have been provided to the IUT in<> and <> information elements in a CC-INFOmessage during establishment of the incoming call.TP/PT/CC/BV/HP-55CAP/PT/NWK/03DECT/T (98) 17, page 4CAP feature N.1 (Handover candidate retrieval)EN 300 824 [11], subclause 9.1.1.2, table 6Initial state: T-10Verify that the IUT requests external handover parameters any time during an incomingcall if the <> information element provided during call setup had theOID value set to "1". Verify that the IUT is subsequently able to successfully completethe external handover call setup procedure.SIST EN 300 497-6 V0.3.2:2003

ETSIETSI EN 300 497-6 V0.3.2 (1999-09)20TP/PT/CC/BV/HP-56CAP/PT/NWK/04DECT/T (98) 17, page 4CAP feature N.1 (Handover reference retrieval)EN 300 824 [11], subclause 9.1.3.2Initial state: T-10Verify that the IUT applies the handover reference retrieval procedure as soon aspossible after establishment of an incoming call (only in CC active) where the<> information element was not supplied. Verify that the IUT issubsequently able to successfully complete the external handover call setup procedure.TP/PT/CC/BV/HP-57CAP/PT/NWK/04.2DECT/T (98) 17, page 4CAP feature N.1 (Failure of the PP handover reference retrieval attempt)EN 300 824 [11], subclause 9.1.3.2.1Initial state: T-10Verify that the IUT starts the handover reference retrieval procedure as soon aspossible after establishment of an incoming call (only in CC active) where the<> information element was not supplied. Verify that the IUTconsider the handover reference retrieval procedure as failed upon receipt of aMM_INFO_REJECT and that after such failure the IUT does not attempt to carry out theexternal handover call setup procedure.TP/PT/CC/BV/HP-58CAP/PT/NWK/04.4DECT/T (98) 17, page 4CAP feature N.1 (Failure of the PP handover reference retrieval attempt)EN 300 824 [11], subclause 9.1.3.2.1Initial state: T-10Verify that the IUT starts the handover reference retrieval procedure as soon aspossible after establishment of an incoming call (only in CC active) where the<> information element was not supplied. Verify that the IUTconsider the Handover reference retrieval procedure as failed upon expiry of and that after such failure the IUT does not attempt to carry out theexternal handover call setup procedure.TP/PT/CC/BV/HP-59CAP/PT/NWK/05DECT/T (98) 17, page 4CAP feature N.1 (Handover candidate call setup)EN 300 824 [11], subclause 9.1.4, table 8Initial state: T-10Verify that the IUT is able to perform the external handover call setup procedure andsuccessfully establishes the U-plane on the new connection.TP/PT/CC/BV/HP-60CAP/PT/NWK/06DECT/T (98) 17, page 4CAP feature N.1 (Handover call setup - abnormal link release)EN 300 824 [11], subclause 9.1.4.2.1Initial state: T-10Verify that the IUT is able to complete the external handover call setup proceduresuccessfully when an abnormal link release occurs on the FP-1 link.TP/PT/CC/BV/HP-61CAP/PT/NWK/07DECT/T (98) 17, page 5CAP feature N.1 (Handover call setup N400)EN 300 175-5 [5], subclause 15.7.4.5EN 300 824 [11], subclause 9.1.4Initial state: T-10Verify that, during the external handover call setup procedure, after call setup iscomplete on FP-2, the IUT releases the FP-1 link using a {CC-RELEASE} messagecontaining a <> indicating "external handover release" if timer N400expires.TP/PT/CC/BV/HP-62CAP/PT/NWK/07.2DECT/T (98) 17, page 5CAP feature N.1 (Handover call setup - normal call release on FP-2 leg)EN 300 824 [11], subclause 9.1.4.2.2Initial state: T-10Verify that, after handover has been accepted and
...