Abstract

Third edition of Conformance Test Specification (CTS) for voluntary testing to ETS 300 175: - adding test cases relevant for CAP testing to provide bases for development of the CAP Profile Test Specification; - making neccessary modifications based on the 3rd edition of ETS 300 175; - correcting errors.

Status
Published
Publication Date
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003
Mandate
T-292

Buy Documents

Standard

SIST EN 300 497-8 V0.3.2:2003

English language (33 pages)
Preview
Preview
e-Library read for
×1 day

SIST EN 300 497-8 V0.3.2:2003 is the Slovene adoption of the ETSI standard for Digital Enhanced Cordless Telecommunications (DECT) Common Interface (CI) test cases. It defines the Test Suite Structure (TSS) and Test Purposes (TP) for the Network (NWK) layer at the Fixed radio Termination (FT), so labs and suppliers can test FT behaviour in a consistent way. The document is meant for conformance and approval testing of DECT equipment.

What does SIST EN 300 497-8 V0.3.2:2003 specify?

SIST EN 300 497-8 V0.3.2:2003 specifies the test specification for DECT EN 300 175 parts 1 to 8, focused on the NWK layer at the FT. It gives the structure for the test library and the test purposes used to assess conformance, interoperability and profile-related behaviour.

The document is organized into:

  • Clause 1 - Scope
  • Clause 2 - References
  • Clause 3 - Definitions and abbreviations
  • Clause 4 - Test Suite Structure (TSS)
  • Clause 5 - Test Purposes (TP)
  • Bibliography and history

Clause 4 sets out the test groups and subgroups. Clause 5 defines the TP format, naming rules and the individual test purposes for the FT side of the NWK layer.

What are the key requirements of SIST EN 300 497-8 V0.3.2:2003?

The standard’s main purpose is to define how FT NWK conformance testing is structured. In practice, this tells a test lab what areas to cover and how each test purpose is identified and documented.

TSS organization and test group meaning

Clause 4 groups tests into protocol groups and main test groups. The protocol groups are Call Control (CC), Mobility Management (MM), Lower layer Management Entity (ME), Link Control (LC), Call Independent Supplementary Services (CISS), Connection Oriented Message Services (COMS) and Connectionless Message Services (CLMS). The main groups are IT, CA, BV, BI, BO and TI.

This matters because it shows which protocol area a test belongs to and whether the test is about interconnection, capability, correct behaviour, invalid input, inopportune events or timer handling.

Limited tests before deeper execution

Clause 4 explains that IT tests check whether the IUT has enough conformance for interconnection, while CA tests check the capabilities claimed in the PICS/PIXIT. In practice, these are the first checks before running the deeper behavioural tests.

Behavioural coverage in Clause 5

Clause 5 contains the TP for valid, invalid and inopportune behaviour across CC, MM, ME, LC, IS and CL. The TP cover call setup, call release, information transfer, location procedures, authentication, access rights, key allocation, ciphering, handover and link control.

For a reader, this means the standard is not a general overview - it provides concrete test purposes that can be turned into conformance test cases.

Timer and counter handling

The TI subgroup in CC, MM and LC checks that the IUT reacts correctly when timers expire or counters mismatch. This is important in practice because protocol state machines often fail at timeout edges rather than during normal operation.

TP naming and documentation rules

Clause 5.1 defines the TP format and naming convention. A TP identifier encodes the radio termination type, functional module, test type, subgroup and sequential number.

That structure matters because it lets users trace each test back to the affected feature, which is useful for implementation, lab reporting and defect tracking.

CAP-related additions

The scope states that this third edition adds test cases relevant for CAP testing, updates the specification to the third edition of ETS 300 175, and corrects errors. Several TP entries also reference CAP features and EN 300 824, especially for external handover and message waiting.

What terms does SIST EN 300 497-8 V0.3.2:2003 define?

  • IUT - Implementation Under Test, the DECT equipment or subsystem being checked.
  • PICS - Protocol Implementation Conformance Statement, the declared capabilities used to select tests.
  • PIXIT - Protocol Implementation Extra Information for Testing, extra test parameters provided by the implementer.
  • TP - Test Purpose, a statement of the objective, condition, stimulus and expected behaviour for one test.
  • TSS - Test Suite Structure, the hierarchy of groups and subgroups used to organize the tests.
  • FT - Fixed radio Termination, the fixed side of the DECT air interface under test.
  • NWK - Network layer, the protocol layer covered by this part of the TCL.

Who uses SIST EN 300 497-8 V0.3.2:2003?

DECT equipment manufacturers use this standard to build and verify FT implementations against the defined NWK test purposes. Conformance test laboratories use it to plan and execute approval tests in a repeatable way.

Quality managers and certification teams use it to check whether claimed features in the PICS/PIXIT are covered by the selected tests. Profile developers also use it as a basis for CAP-related test specification work.

What changed in SIST EN 300 497-8 V0.3.2:2003 from the previous edition?

This version adds test cases relevant for CAP testing, makes the changes needed for the third edition of ETS 300 175, and corrects errors. The history also shows the publication sequence from earlier ETS/EN versions to V0.3.2.

Which standards are used with SIST EN 300 497-8 V0.3.2:2003?

  • EN 300 175-1 to EN 300 175-8 - the DECT Common Interface base specification; these provide the protocol and feature definitions the tests are based on.
  • ETS 300 406 - the conformance testing methodology and standardization rules used as the testing basis.
  • EN 300 444 - Generic Access Profile (GAP); used in many TP references for call and mobility behaviour.
  • EN 300 824 - Cordless Terminal Mobility (CTM), CTM Access Profile (CAP); used for CAP-related test purposes.
  • ISO/IEC 9646-1 and ISO/IEC 9646-2 - the general conformance testing methodology and abstract test suite framework.

What does the SIST EN 300 497-8 V0.3.2:2003 document contain?

Clause 4 contains a TSS overview figure and the test group hierarchy for CC, MM, ME, LC, IS and CL. Clause 5 contains the TP definition rules, naming conventions and the individual TP entries, each with a reference, initial state, stimulus and expected behaviour.

The document also includes many detailed TP statements for specific procedures such as outgoing and incoming calls, authentication, location registration, access rights, cipher switching, external handover and link establishment or release. These entries are what a test system turns into executable conformance checks.

Buy Documents

Standard

SIST EN 300 497-8 V0.3.2:2003

English language (33 pages)
Preview
Preview
e-Library read for
×1 day

Get Certified

Connect with accredited certification bodies for this standard

ANCE

Mexican certification and testing association.

EMA Mexico Verified

Intertek Slovenia

Intertek testing, inspection, and certification services in Slovenia.

UKAS Slovenia Verified

LNE (Laboratoire National de Métrologie et d'Essais)

French national laboratory for metrology and testing.

COFRAC France Verified

Sponsored listings

Frequently Asked Questions

SIST EN 300 497-8 V0.3.2:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "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)". This standard covers: Third edition of Conformance Test Specification (CTS) for voluntary testing to ETS 300 175: - adding test cases relevant for CAP testing to provide bases for development of the CAP Profile Test Specification; - making neccessary modifications based on the 3rd edition of ETS 300 175; - correcting errors.

Third edition of Conformance Test Specification (CTS) for voluntary testing to ETS 300 175: - adding test cases relevant for CAP testing to provide bases for development of the CAP Profile Test Specification; - making neccessary modifications based on the 3rd edition of ETS 300 175; - correcting errors.

SIST EN 300 497-8 V0.3.2:2003 is classified under the following ICS (International Classification for Standards) categories: 33.070.30 - Digital Enhanced Cordless Telecommunications (DECT). The ICS classification helps identify the subject area and facilitates finding related standards.

SIST EN 300 497-8 V0.3.2:2003 is associated with the following European legislation: Standardization Mandates: T-292. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.

SIST EN 300 497-8 V0.3.2:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

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
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 purposes:TP/FT/CC/BV/CI-01EN 300 175-5 [5], subclause 9.3.1EN 300 444 [10], subclause 8.14Initial state: F-00Verify that the IUT is able to send the <> information element in case ofincoming call to the PT. This information element can either be in the {CC-SETUP} or insuccessive {CC-INFO} message.TP/FT/CC/BV/CI-02EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: F-02Verify that when the IUT receives a {CC-INFO} message with a <>information element containing keypad-info "12"H (goto pulse), the IUT from thatmoment on transfers dialling information to the network simulator, using pulse (decadic)dialling (feature N.23 in EN 300 444 [10]).TP/FT/CC/BV/CI-03EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: F-10Verify that when the IUT receives a {CC-INFO} message with a <>information element containing keypad-info "12"H (goto pulse), the IUT from thatmoment on transfers dialling information to the network simulator, using pulse (decadic)dialling (feature N.23 in EN 300 444 [10]).TP/FT/CC/BV/CI-04EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: F-02Verify that when the IUT receives a {CC-INFO} message with a <>information element containing keypad-info "05H" (dialling pause), it sends a diallingpause to the network simulator (feature N.7 in EN 300 444 [10]).TP/FT/CC/BV/CI-05EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: F-10Verify that when the IUT receives a {CC-INFO} message with a <>information element containing keypad-info "05H" (dialling pause), it sends a diallingpause to the network simulator (feature N.7 in EN 300 444 [10]).TP/FT/CC/BV/CI-06EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: F-02Verify that when the IUT receives a {CC-INFO} message with a <>information element containing keypad-info "14H" (goto DTMF, defined tone length),the IUT from that moment on transfers dialling information to the network simulator,using DTMF with defined tone length (feature N.6 in EN 300 444 [10]).TP/FT/CC/BV/CI-07EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: F-10Verify that when the IUT receives a {CC-INFO} message with a <>information element containing keypad-info "14H" (goto DTMF, defined tone length),the IUT from that moment on transfers dialling information to the network simulator,using DTMF with defined tone length (feature N.6 in EN 300 444 [10]).TP/FT/CC/BV/CI-08EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: F-02Verify that when the IUT receives a {CC-INFO} message with a <>information element containing keypad-info "16H" (goto DTMF, infinite tone length), theIUT from that moment on transfers dialling information to the network simulator, usingDTMF with infinite tone length (feature N.22 in EN 300 444 [10]).TP/FT/CC/BV/CI-09EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: F-10Verify that when the IUT receives a {CC-INFO} message with a <>information element containing keypad-info "16H" (goto DTMF, infinite tone length), theIUT from that moment on transfers dialling information to the network simulator, usingDTMF with infinite tone length (feature N.22 in EN 300 444 [10]).SIST EN 300 497-8 V0.3.2:2003

ETSIETSI EN 300 497-8 V0.3.2 (1999-09)16TP/FT/CC/BV/CI-10EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.10, table 20Initial state: F-10Verify that when the IUT receives a {CC-INFO} message with a <>information element containing the basic digits (0-9, star, hash mark), it transfers thisinformation correctly to the network simulator (feature N.4 in EN 300 444 [10]).5.2.3.4CC/BV/CR test purposesTest subgroup objectives:To check the IUT's behaviours to release an outgoing and incoming call.Test purposes:TP/FT/CC/BV/CR-01EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.7Initial state: F-02Verify that the IUT is able to perform an IUT initiated normal release.TP/FT/CC/BV/CR-02EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10],subclause 8.7Initial state: F-10Verify that the IUT is able to perform an IUT initiated normal release.TP/FT/CC/BV/CR-03EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.7Initial state: F-07Verify that the IUT is able to perform an IUT initiated normal release.TP/FT/CC/BV/CR-04EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.7Initial state: F-02Verify that the IUT, after part of dialling information is sent, is able to perform a PTinitiated normal release.TP/FT/CC/BV/CR-05EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.7Initial state: F-10Verify that the IUT is able to perform a PT initiated normal release.TP/FT/CC/BV/CR-06EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.7Initial state: F-07Verify that the IUT is able to perform a PT initiated normal release.TP/FT/CC/BV/CR-07EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.8, figure 24Initial state: F-07Verify that the IUT is able to perform a PT initiated abnormal release.TP/FT/CC/BV/CR-08EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.8, figure 24Initial state: F-10Verify that the IUT is able to perform a PT initiated abnormal release.TP/FT/CC/BV/CR-09EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.8, figure 24Initial state: F-06Verify that the IUT is able to perform a PT initiated abnormal release.TP/FT/CC/BV/CR-10EN 300 175-5 [5], subclause 14.2.7EN 300 444 [10], subclause 8.9Initial state: F-10Verify that the IUT is able to perform a PT initiated partial release.SIST EN 300 497-8 V0.3.2:2003

ETSIETSI EN 300 497-8 V0.3.2 (1999-09)17TP/FT/CC/BV/CR-50CAP/FT/NWK/15DECT/T (98) 17 p.15CAP feature N.1 (External handover - call release)EN 300 824 [11], subclause 9.1.4.2.2Initial state: F-10Verify that after completing the external handover call setup procedure, the IUT cansuccessfully perform the PT initiated normal CC release procedure.TP/FT/CC/BV/CR-51CAP/FT/NWK/16DECT/T (98) 17 p.15CAP feature N.1 (External handover - call release)EN 300 824 [11], subclause 9.1.4.2.2Initial state: F-10Verify that after completing the external handover call setup procedure, the IUT cansuccessfully perform the FT initiated normal CC release procedure.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.5.2.3.7CC/BV/RS test purposesTest subgroup objectives:To check the IUT's behaviour during any call related procedures.Test purposes:TP/FT/CC/BV/RS-07Existing validated GAP testDECT/T (98) 17 p.13GAP/CAP feature N.30EN 300 175-5 [5], subclause 10.3EN 300 444 [10], subclause 8.12, table 21EN 300 824 [11], subclause 7.7, table 3Initial state: F-00Verify the IUT is able to transmit the <> information element inthe {CC-SETUP} message providing the PP with the calling party number informationbefore accepting the call.SIST EN 300 497-8 V0.3.2:2003

ETSIETSI EN 300 497-8 V0.3.2 (1999-09)185.2.3.8CC/BV/HP test purposesTest subgroup objectives:To check the behaviour of the CC of the IUT during external handover.Test purposes:TP/FT/CC/BV/HP-50CAP/FT/NWK/01DECT/T (98) 17 p.13CAP feature N.1 (Handover candidate indication)EN 300 824 [11], subclause 9.1.1, table 6Initial state: F-00Verify that during the establishment of an outgoing call, the IUT transmits a valid<> information element in a CC message.TP/FT/CC/BV/HP-51CAP/FT/NWK/02DECT/T (98) 17 p.13CAP feature N.1 (Handover candidate indication)EN 300 824 [11], subclause 9.1.1, table 6Initial state: F-00Verify that during the establishment of an incoming call, the IUT transmits a valid <> information element in a CC message.TP/FT/CC/BV/HP-52CAP/FT/NWK/05DECT/T (98) 17 p.13CAP feature N.1 (Handover reference indication)EN 300 824 [11], subclause 9.1.3, table 7Initial state: F-00Verify that during the establishment of an outgoing call, the IUT transmits a valid<> information element in a CC message.TP/FT/CC/BV/HP-53CAP/FT/NWK/06DECT/T (98) 17 p.13CAP feature N.1 (Handover reference indication)EN 300 824 [11], subclause 9.1.3, table 7Initial state: F-00Verify that during the establishment of an incoming call, the IUT transmits a valid<> information element in a CC message.TP/FT/CC/BV/HP-54CAP/FT/NWK/07DECT/T (98) 17 p.14CAP feature N.1 (Handover candidate call setup)EN 300 824 [11], subclause 9.1.4, table 7Initial state: F-10Verify that the IUT is able to perform the external handover call setup procedure andsuccessfully establishes the U-plane on the new connection. The IUT has to provide in the external handover call setup.5.2.4CC/BO test purposesTest group objectives:To check the CC of the IUT in response to the messages that are syntactically correct but not allowed to occur in somestates of the CC procedures.Test purposes:TP/FT/CC/BO-01EN 300 175-5 [5], subclause 17.4.1EN 300 444 [10], subclause 6.9.4.Initial state: F-02Verify that the IUT ignores the unexpected message {CC-SETUP}TP/FT/CC/BO-02EN 300 175-5 [5], subclause 9.5.3EN 300 444 [10], subclause 8.7.2.1, figure 21.Initial state: F-19Verify that the IUT is able to react correctly on a release collision, in the sense thatupon reception of a {CC-RELEASE} message in state F-19, no {CC-RELEASE-COM}message is sent back, and the call is cleared.SIST EN 300 497-8 V0.3.2:2003

ETSIETSI EN 300 497-8 V0.3.2 (1999-09)195.2.5CC/BI test purposesTest group objectives:To check the Call Control module of the IUT in response to invalid messages.Test purposes:TP/FT/CC/BI-01EN 300 175-5 [5], subclause 17.6.1EN 300 444 [10], subclause 6.9.4Initial state: F-00Verify that the IUT sends a {CC-RELEASE-COM} message on receipt of a {CC-SETUP}message without a mandatory information elementTP/FT/CC/BI-02EN 300 175-5 [5], subclause 17.6.2EN 300 444 [10], subclause 6.9.4Initial state: F-00Verify that the IUT sends a {CC-RELEASE-COM} message on receipt of a {CC-SETUP}message containing a mandatory information element with invalid contentsTP/FT/CC/BI-03EN 300 175-5 [5], subclause 17.4.1EN 300 444 [10], subclause 6.9.4.Initial state: F-00Verify that the IUT ignores an unrecognized message, constructed and a {CC-SETUP}but with one bit different in the 5.2.6CC/TI test purposesTest group objectives:To verify that the IUT is reacting properly to an expiry of one of the timers or counters mismatch.Test purposes:TP/FT/CC/TI-01EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.3.2.3,Initial state: F-02Verify that the IUT, after having started timer F-, sends a {CC-RELEASE}message when the timer expires after the defined time. The {CC-RELEASE} messageshould arrive within the allowed margin time of ± 5 %TP/FT/CC/TI-02EN 300 175-5 [5], subclause 9.3.1.5EN 300 444 [10], subclause 8.3.2.3, figure 12Initial state: F-02Verify that the IUT is able to restart the timer F-, on receipt of a {CC-INFO}messageTP/FT/CC/TI-03EN 300 175-5 [5], subclause 9.5.1EN 300 444 [10], subclause 8.7.1.2Initial state: F-19Verify that the IUT, after having started timer F-, sends a{CC-RELEASE-COM} message when the timer expires after the defined time. The{CC-RELEASE-COM} message should arrive within the allowed margin time of ± 5 %TP/FT/CC/TI-04EN 300 175-5 [5], subclause 9.3.2EN 300 444 [10], subclause 8.12.1.1Initial state: F-06Verify that the IUT, after having started timer F-, sends a{CC-RELEASE-COM} message when the timer expires after the defined time. The{CC-RELEASE-COM} message should arrive within the allowed margin time of ± 5 %SIST EN 300 497-8 V0.3.2:2003

ETSIETSI EN 300 497-8 V0.3.2 (1999-09)205.3MM test purposesTest group objectives:To check the behaviour of the MM module of the IUT. Most test cases in this group are testing the MM while the CC isin null state or active state.Subgroups:-IT;-CA;-BV;-BO;-BI;-TI.5.3.1MM/IT test purposesThere are no test purposes defined for this group in the present document.5.3.2MM/CA test purposesThere are no test purposes defined for this group in the present document.5.3.3MM/BV test purposesSubgroups:-ID;-AU;-LO;-AR;-KA;-PR;-CH;-HP.5.3.3.1MM/BV/ID test purposesTest subgroup objectives:To check the IUT's valid behaviour of identity request procedure.Test purposes:TP/FT/MM/BV/ID-01EN 300 175-5 [5], subclause 13.2.1EN 300 444 [10], subclause 8.19Initial state: Selected in PIXITVerify that when the basic IUT initiated identity request procedure is invoked on the IUT,the IUT is able to perform this procedure correctly.SIST EN 300 497-8 V0.3.2:2003

ETSIETSI EN 300 497-8 V0.3.2 (1999-09)215.3.3.2MM/BV/AU test purposesTest subgroup objectives:To check the IUT's valid behaviour of the authentication procedure.Test purposes:TP/FT/MM/BV/AU-01EN 300 175-5 [5], subclause 13.3.1EN 300 444 [10], subclause 8.21Initial state: Selected in PIXITVerify that the IUT, after invocation, is able to perform the basic operation of theauthentication of PT procedure (PT has not stored ZAP value and service classinformation).TP/FT/MM/BV/AU-02EN 300 175-5 [5], subclause 13.3.1EN 300 444 [10], subclause 8.23, figure 49Initial state: Selected in PIXITVerify that the IUT, after invocation, is able to perform the basic operation of theprocedure incrementing the ZAP value, during the authentication of PT procedure(PT has stored ZAP value and service class information). PT will authenticate IUTbefore answering.TP/FT/MM/BV/AU-03EN 300 175-5 [5], subclause 13.3.2EN 300 444 [10], subclause 8.22Initial state: Selected in PIXITVerify that the IUT, after invocation, is able to perform the basic operation of theauthentication of user procedure (PT has not stored ZAP value and service classinformation).TP/FT/MM/BV/AU-04EN 300 175-5 [5], subclause 13.3.3EN 300 444 [10], subclause 8.20Initial State: F-10Verify that the IUT is able to perform the basic operation of the authentication of FTprocedure.TP/FT/MM/BV/AU-05EN 300 175-5 [5], subclause 13.3.3EN 300 444 [10], subclause 8.20.2.1, figure 45Initial State: F-00Verify that the IUT rejects authentication of FT procedure if an authentication key isspecified which is not supported by the FT.TP/FT/MM/BV/AU-06EN 300 175-5 [5], subclause 13.3.3EN 300 444 [10], subclause 8.20.2.1, figure 45Initial state: Selected in PIXITVerify that the IUT is capable to request storage of the DCK and successively use thestored DCK value for ciphering, when it is accepted by the PT.(PT has not stored ZAPvalue and service class information).SIST EN 300 497-8 V0.3.2:2003

ETSIETSI EN 300 497-8 V0.3.2 (1999-09)225.3.3.3MM/BV/LO test purposesTest subgroup objectives:To check the IUT's valid behaviour of
...