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)

REN/DECT-040131-8

Digitalne izboljšane brezvrvične telekomunikacije (DECT) – Skupni vmesnik (CI) –Knjižnica preskušalnih primerov (TCL) – 8. del: Zgradba preskušalnega niza (TSS) in nameni preskušanja (TP) – Omrežna plast (NWK) – Fiksna radijska zaključitev (FT)

General Information

Status
Published
Publication Date
06-Sep-1999
Technical Committee
Current Stage
12 - Completion
Due Date
30-Aug-1999
Completion Date
07-Sep-1999
Mandate

Buy Standard

Standard
EN 300 497-8 V0.3.2:2003
English language
33 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.)7Digital 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)33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:EN 300 497-8 Version 0.3.2SIST EN 300 497-8 V0.3.2:2003en01-december-2003SIST EN 300 497-8 V0.3.2:2003SLOVENSKI
STANDARD



SIST EN 300 497-8 V0.3.2:2003



ETSI EN 300 497-8 V0.3.2 (1999-09)European Standard (Telecommunications series)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)SIST EN 300 497-8 V0.3.2:2003



ETSIETSI EN 300 497-8 V0.3.2 (1999-09)2ReferenceREN/DECT-040131-8 (4lq0011c.PDF)KeywordsDECT, network, FT, testing, TSS&TPETSIPostal 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-8 V0.3.2:2003



ETSIETSI EN 300 497-8 V0.3.2 (1999-09)3ContentsIntellectual Property Rights.5Foreword.51Scope.62References.63Definitions and abbreviations.73.1Definitions.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 (TP).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.145.2.3.3CC/BV/CI test purposes.155.2.3.4CC/BV/CR test purposes.165.2.3.5CC/BV/SC test purposes.175.2.3.6CC/BV/PM test purposes.175.2.3.7CC/BV/RS test purposes.175.2.3.8CC/BV/HP test purposes.185.2.4CC/BO test purposes.185.2.5CC/BI test purposes.195.2.6CC/TI test purposes.195.3MM test purposes.205.3.1MM/IT test purposes.205.3.2MM/CA test purposes.205.3.3MM/BV test purposes.205.3.3.1MM/BV/ID test purposes.205.3.3.2MM/BV/AU test purposes.215.3.3.3MM/BV/LO test purposes.225.3.3.4MM/BV/AR test purposes.23SIST EN 300 497-8 V0.3.2:2003



ETSIETSI EN 300 497-8 V0.3.2 (1999-09)45.3.3.5MM/BV/KA test purposes.235.3.3.6MM/BV/PR test purposes.245.3.3.7MM/BV/CH test purposes.245.3.3.8MM/BV/HP test purposes.255.3.4MM/BO test purposes.265.3.5MM/BI test purposes.265.3.6MM/TI test purposes.275.4ME test purposes.275.4.1ME/BV test purposes.285.4.2ME/BO test purposes.285.5LC test purposes.285.5.1LC/BV test purposes.285.5.1.1LC/BV/LE test purposes.295.5.1.2LC/BV/LR test purposes.295.5.1.3LC/BV/LS test purposes.295.5.1.4LC/BV/CL test purposes.305.5.2LC/BI test purposes.305.5.3LC/TI test purposes.305.6IS test purposes.305.6AIS/BV test purposes.315.7MO test purposes.315.8CL test purposes.315.9CL/BV test purposes.31Bibliography.32History.33SIST EN 300 497-8 V0.3.2:2003



ETSIETSI EN 300 497-8 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 8 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 radio Termination(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 radioTermination (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-8 V0.3.2:2003



ETSIETSI EN 300 497-8 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 Fixed radioTermination (FT).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-8 V0.3.2:2003



ETSIETSI EN 300 497-8 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.1DefinitionsFor 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 ControlCICall 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 resumeLTLower TesterMEManagement EntityMMMobility ManagementMOConnection Oriented Message ServicesNWKNetwork layerOCOutgoing CallPARKPortable Access Rights KeyPDUProtocol Data UnitPHLPhysical layerPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation Extra Information for TestingPMPacket ModePRParameter RetrievalSIST EN 300 497-8 V0.3.2:2003



ETSIETSI EN 300 497-8 V0.3.2 (1999-09)8PTPortable radio terminationRSCall Related Supplementary ServicesSCService ChangeTPTest PurposesTSSTest Suite StructureTTCNTree and Tabular Combined NotationUAKUser Authentication KeySIST EN 300 497-8 V0.3.2:2003



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



ETSIETSI EN 300 497-8 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, clause 13 and subclause 15.7.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-8 V0.3.2:2003



ETSIETSI EN 300 497-8 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 (TP)Each test case is allocated directly under a defined TP.5.1Introduction5.1.1TP definition conventionsThe TP are defined following particular rules as shown in table 1.Table 1: TP definition rulesTP Id according to the TPnaming 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.2ReferencesThis subclause defines the use of references given in the TP. 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-8 V0.3.2:2003



ETSIETSI EN 300 497-8 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 terminationFTFixed 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.Subgroups:-IT;-CA;-BV;-BO;-BI;-TI.SIST EN 300 497-8 V0.3.2:2003



ETSIETSI EN 300 497-8 V0.3.2 (1999-09)135.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;-HP.SIST EN 300 497-8 V0.3.2:2003



ETSIETSI EN 300 497-8 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/FT/CC/BV/OC-01EN 300 175-5 [5], subclause 9.3.1.4 - subclause 9.3.1.6EN 300 444 [10], subclause 8.1, figure 1Initial state: F-00Verify that the IUT is able to perform a CC-state transition from state F-00 to state F-10for an outgoing normal call, using the piece-wise method to transfer dialling information.TP/FT/CC/BV/OC-02EN 300 175-5 [5], subclause 9.3.1.4 - subclause 9.3.1.6Initial state: F-00Verify that the IUT is able to perform a CC-state transition from state F-00 to state F-10for an outgoing normal call set-up with en-block dialling in {CC-SETUP} message.TP/FT/CC/BV/OC-03Existing TCL testDECT/T (98) 17 p.14CAP feature N.2EN 300 175-5 [5], subclause 9.3.1EN 300 824 [11], subclause 7.2, table 1Initial state: F-00Verify that the IUT is able, prior to subscription, to perform a CC-state transition fromstate F-00 to state F-10 for an outgoing emergency call set-up.TP/FT/CC/BV/OC-04Existing TCL testDECT/T (98) 17 p.14CAP feature N.2EN 300 175-5 [5], subclause 9.3.1EN 300 824 [11], subclause 7.2, table 1Initial state: F-00Verify that the IUT is able, when it has a subscription record for the requesting PT, toperform a CC-state transition from the F-00 state to F-10 state for an outgoingemergency call set-up.TP/FT/CC/BV/OC-05EN 300 175-5 [5], subclause 9.3.1Initial state: F-00Verify that the IUT is able, prior to subscription, to perform a CC-state transition fromstate F-00 to state F-10 for an outgoing emergency call set-up with piece-wise dialling.TP/FT/CC/BV/OC-06CAP/FT/NWK/xyDECT/T (98) 17 p.15GAP/CAP feature M.13EN 300 175-3 [3], subclause 11.3.2EN 300 175-6 [6], subclause 5.6Initial state: F-00Verify that the IUT can correctly establish a following outgoing call from the LT when theLT has use SARI as the means to lock to the IUT.TP/FT/CC/BV/OC-50CAP/FT/NWK/xxDECT/T (98) 17 p.15CAP feature M.1EN 300 824 [11], subclause 11.3Initial state: F-00Verify that the IUT can correctly establish a following outgoing call from the LT when theLT has use TARI as the means to lock to the IUT.5.2.3.2CC/BV/IC test purposesTest subgroup objectives:To check the IUT's behaviours to setup an incoming call.Test purposes:TP/FT/CC/BV/IC-01EN 300 175-5 [5], subclause 9.3.2EN 300 444 [10], subclause 8.11, figure 28Initial state: F-00Verify that the IUT is able to perform an incoming call via the states F-06 and F-07 tothe state F-10.TP/FT/CC/BV/IC-02EN 300 175-5 [5], subclause 9.3.2Initial state: F-00Verify that the IUT is able to perform an incoming call via state F-06 directly to the stateF-10.SIST EN 300 497-8 V0.3.2:2003



ETSIETSI EN 300 497-8 V0.3.2 (1999-09)155.2.3.3CC/BV/CI test purposesTest subgroup objectives:To check the IUT's behaviours for information transfer.Test
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.