SIST I-ETS 300 491-2 E1:2003

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Terminalska oprema (TE) – Preskušanje skladnosti prenosa datotek prek digitalnega omrežja z integriranimi storitvami (ISDN) – 2. del: ETS 300 075 Zgradba preskušalnega niza in nameni preskušanja (TSS&TP)Terminal Equipment (TE); Conformance testing for file transfer over the Integrated Services Digital Network (ISDN); Part 2: ETS 300 075 Test Suite Structure and Test Purposes (TSS&TP)35.180Terminalska in druga periferna oprema ITIT Terminal and other peripheral equipment33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:I-ETS 300 491-2 Edition 1SIST I-ETS 300 491-2 E1:2003en01-december-2003SIST I-ETS 300 491-2 E1:2003SLOVENSKI
STANDARD
INTERIMEUROPEANI-ETS 300 491-2TELECOMMUNICATIONSeptember 1996STANDARDSource: ETSI TC-TEReference: DI/TE-01060-2ICS:33.080, 35.180Key words:ISDN, file transferTerminal Equipment (TE);Conformance testing for file transfer overthe Integrated Services Digital Network (ISDN);Part 2: ETS 300 075 Test Suite Structureand Test Purposes (TSS&TP)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.SIST I-ETS 300 491-2 E1:2003

Page 2I-ETS 300 491-2: September 1996Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST I-ETS 300 491-2 E1:2003

Page 3I-ETS 300 491-2: September 1996ContentsForeword.71Scope.92Normative references.93Definitions and abbreviations.93.1Definitions.93.2Abbreviations.104Test suite overview.104.1Test Suite Structure (TSS).104.2Test groups.124.2.1Major roles.124.2.2Main test groups.124.2.2.1Basic Interconnection Test (IT).124.2.2.2Capability Tests (CA).134.2.2.3Valid Behaviour Tests (BV).134.2.2.4Invalid Behaviour Tests (BI).134.2.2.5Inopportune Behaviour Tests (BO).134.2.3Functional units test groups.134.3Test step structure.134.3.1State definitions.134.3.2Preambles.144.3.3Postambles.145Test Purposes presentation.145.1Introduction.145.2Test Purpose naming convention.145.3Test Purpose writing rules.155.3.1Initiator.155.3.2Acceptor.156Test Purposes.156.1IUT as a master.156.1.1M/Basic Interconnection Tests (IT).166.1.2M/Capability Tests (CA).166.1.2.1M/CA/Association.166.1.2.2M/CA/Access.166.1.2.3M/CA/Directory.176.1.2.4M/CA/Save.176.1.2.5M/CA/Load.176.1.2.6M/CA/Rename.176.1.2.7M/CA/Delete.176.1.2.8M/CA/File Transfer.186.1.2.9M/CA/Typed Data.186.1.3M/Valid Behaviour Tests (BV).186.1.3.1M/BV/Protocol Interactions.186.1.3.1.1M/BV/PI/Association.196.1.3.1.2M/BV/PI/Access.196.1.3.1.3M/BV/PI/Directory.196.1.3.1.4M/BV/PI/Save.196.1.3.1.5M/BV/PI/Load.206.1.3.1.6M/BV/PI/Rename.206.1.3.1.7M/BV/PI/Delete.206.1.3.1.8M/BV/PI/File Transfer.206.1.3.1.9M/BV/PI/Typed Data.22SIST I-ETS 300 491-2 E1:2003

Page 4I-ETS 300 491-2: September 19966.1.3.2M/BV/Parameter Variations.226.1.3.2.1M/BV/PV/File Transfer.226.1.3.3M/BV/Parameter Combinations.236.1.3.3.1M/BV/PC/File Transfer.236.1.3.4M/BV/Inopportune Event.236.1.3.4.1M/BV/IE/Association.236.1.3.4.2M/BV/IE/Access.246.1.3.4.3M/BV/IE/Save.246.1.3.4.4M/BV/IE/Load.246.1.3.4.5M/BV/IE/Typed Data.246.1.3.5M/BV/Timer Variations.256.1.3.5.1M/BV/TI/Access.256.1.3.5.2M/BV/TI/Directory.256.1.3.5.3M/BV/TI/File Transfer.256.1.4M/Invalid Behaviour Tests (BI).266.1.4.1M/BI/Parameter Variations.266.1.4.1.1M/BI/PV/Association.266.1.4.1.2M/BI/PV/Access.276.1.4.1.3M/BI/PV/Directory.276.1.4.1.4M/BI/PV/Save.276.1.4.1.5M/BI/PV/Load.286.1.4.1.6M/BI/PV/Rename.286.1.4.1.7M/BI/PV/Delete.286.1.4.1.8M/BI/PV/File Transfer.296.1.4.1.9M/BI/PV/Typed Data.306.1.4.2M/BI/Parameter Combinations.306.1.4.2.1M/BI/PC/File Transfer.306.1.5M/Inopportune Behaviour Tests (BO).306.1.5.1M/BO/Inopportune Event.306.1.5.1.1M/BO/IE/Association.316.1.5.1.2M/BO/IE/Access.316.1.5.1.3M/BO/IE/Directory.326.1.5.1.4M/BO/IE/Save.326.1.5.1.5M/BO/IE/Load.326.1.5.1.6M/BO/IE/Rename.336.1.5.1.7M/BO/IE/Delete.336.1.5.1.8M/BO/IE/File Transfer.336.2IUT as a Slave.346.2.1S/Basic Interconnection Tests (IT).346.2.2S/Capability Tests (CA).346.2.2.1S/CA/Association.346.2.2.2S/CA/Access.356.2.2.3S/CA/Directory.356.2.2.4S/CA/Save.356.2.2.5S/CA/Load.356.2.2.6S/CA/Rename.366.2.2.7S/CA/Delete.366.2.2.8S/CA/File Transfer.366.2.2.9S/CA/Typed Data.366.2.3S/Valid Behaviour Tests (BV).376.2.3.1S/BV/Protocol Interactions.376.2.3.1.1S/BV/PI/Association.376.2.3.1.2S/BV/PI/File Transfer.376.2.3.1.3S/BV/PI/Typed Data.386.2.3.2S/BV/Parameter Variations.396.2.3.2.1S/BV/PV/Access.396.2.3.2.2S/BV/PV/Directory.396.2.3.2.3S/BV/PV/Save.406.2.3.2.4S/BV/PV/Load.406.2.3.2.5S/BV/PV/Rename.406.2.3.2.6S/BV/PV/Delete.406.2.3.2.7S/BV/PV/File Transfer.416.2.3.3S/BV/Parameter Combinations.41SIST I-ETS 300 491-2 E1:2003

Page 5I-ETS 300 491-2: September 19966.2.3.3.1S/BV/PC/Association.426.2.3.3.2S/BV/PC/Directory.426.2.3.3.3S/BV/PC/Save.426.2.3.3.4S/BV/PC/Load.426.2.3.3.5S/BV/PC/Rename.436.2.3.3.6S/BV/PC/Delete.436.2.3.3.7S/BV/PC/File Transfer.436.2.3.4S/BV/Inopportune Event.436.2.3.4.1S/BV/IE/Association.446.2.3.4.2S/BV/IE/Access.446.2.3.4.3S/BV/IE/Save.446.2.3.4.4S/BV/IE/Load.446.2.4S/Invalid Behaviour Tests (BI).446.2.4.1S/BI/Parameter Variations.456.2.4.1.1S/BI/PV/Association.456.2.4.1.2S/BI/PV/Access.456.2.4.1.3S/BI/PV/Directory.466.2.4.1.4S/BI/PV/Save.466.2.4.1.5S/BI/PV/Load.466.2.4.1.6S/BI/PV/Rename.476.2.4.1.7S/BI/PV/Delete.476.2.4.1.8S/BI/PV/File Transfer.476.2.4.1.9S/BI/PV/Typed Data.486.2.4.2S/BI/Parameter Combinations.496.2.4.2.1S/BI/PC/File Transfer.496.2.5S/Inopportune Behaviour Tests (BO).496.2.5.1S/BO/Inopportune Event.496.2.5.1.1S/BO/IE/Association.496.2.5.1.2S/BO/IE/Access.506.2.5.1.3S/BO/IE/Save.506.2.5.1.4S/BO/IE/Load.516.2.5.1.5S/BO/IE/File Transfer.51Annex A (informative):Test Identifier acronyms.52History.53SIST I-ETS 300 491-2 E1:2003

Page 6I-ETS 300 491-2: September 1996Blank pageSIST I-ETS 300 491-2 E1:2003

Page 7I-ETS 300 491-2: September 1996ForewordPart 2 of this Interim European Telecommunication Standard (I-ETS) has been produced by the TerminalEquipment (TE) Technical Committee of the European Telecommunications Standards Institute (ETSI).An ETSI standard may be given I-ETS status either because it is regarded as a provisional solution aheadof a more advanced standard, or because it is immature and requires a "trial period". The life of an I-ETSis limited to three years after which it can be converted into an ETS, have it's life extended for a furthertwo years, be replaced by a new version, or be withdrawn.This is the second part of an I-ETS which comprise three parts as follows:"Terminal Equipment (TE); Conformance testing for file transfer over the Integrated Services DigitalNetwork (ISDN):Part 1:ETS 300 075 Protocol Implementation Conformance Statement (PICS) proforma;Part 2:ETS 300 075 Test Suite Structure and Test Purposes (TSS&TP);Part 3:Conformance testing for ETS 300 075 restricted by ETS 300 383 - Abstract Testsuite (ATS)".Proposed announcement dateDate of adoption of this I-ETS:30 August 1996Date of latest announcement of this I-ETS (doa):31 December 1996SIST I-ETS 300 491-2 E1:2003

Page 8I-ETS 300 491-2: September 1996Blank pageSIST I-ETS 300 491-2 E1:2003

Page 9I-ETS 300 491-2: September 19961ScopePart 2 of this Interim European Telecommunication Standard (I-ETS) specifies the Test Suite Structureand Test Purposes (TSS&TP) for the Telesoftware Data Unit (TDU) layer protocol requirements of ETS300 075 [1], restricted to the test specification for simple file transfer over the ISDN. Only the protocolexchanges aspects are described here, i.e. no Test Purpose concerning the telesoftware application andits specific parameters values is specified here.The ISO/IEC standard for the methodology of conformance testing (ISO/IEC 9646-1 [2],ISO/IEC 9646-2 [3] and ISO/IEC 9646-3 [4]) is used as a basis for the test methodology.2Normative referencesPart 2 of this I-ETS incorporates by dated or undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this this part of the I-ETS only when incorporated in it by amendment or revision. For undatedreferences the latest edition of the publication referred to applies.[1]ETS 300 075 (1994): "Terminal Equipment (TE); Processable data, Filetransfer".[2]ISO/IEC 9646-1 (1994): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 1:General concepts".[3]ISO/IEC 9646-2 (1994): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 2:Abstract Test Suite specification".[4]ISO/IEC 9646-3 (1992): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 3:Tree and Tabular Combined Notation (TTCN)".[5]ETS 300 383 (1995): "Integrated Service Digital Network (ISDN); File transferover the ISDN-EUROFILE transfer profile".3Definitions and abbreviations3.1DefinitionsFor the purposes of this part of the I-ETS, the following definitions apply:Abstract Test Suite (ATS): A test suite composed of abstract test cases (ISO/IEC 9646-1 [2]).Implementation Under Test (IUT): An implementation of one or more Open Systems Interconnection(OSI) protocols in an adjacent user/provider relationship, being the part of a real open system which is tobe studied by testing (ISO/IEC 9646-1 [2]).Lower Tester (LT): The representation in ISO/IEC 9646-1 [2] of the means of providing, during testexecution, indirect control and observation of the lower service boundary of the IUT via the underlyingservice-provider (ISO/IEC 9646-1 [2]).NOTE:The underlying service-provider is immediately beneath the (lowest) protocol which isthe focus of testing. It may use one or more OSI layers, or only the Physical medium.SIST I-ETS 300 491-2 E1:2003

Page 10I-ETS 300 491-2: September 1996master: The entity which controls the dialogue.PICS proforma: A profile RL plus the set of ICS proformas which when completed for a system and takentogether with the profile RL become a profile ICS [ISO/IEC 9646-1 [2]].PIXIT proforma: A profile XRL plus the set of IXIT proformas which when completed for an SUT andtaken together with the profile XRL become a profile IXIT [ISO/IEC 9646-1 [2]].Point Of Control and Observation (PCO): A point within a testing environment where the occurrence oftest events is to be controlled and observed, as defined in an Abstract Test Method [ISO/IEC 9646-1 [2]].Protocol Implementation Conformance Statement (PICS): An ICS for an implementation or systemclaimed to conform to a given protocol specification [ISO/IEC 9646-1 [2]].Protocol Implementation Extra Information For Testing (PIXIT): An IXIT related to testing forconformance to a given protocol specification [ISO/IEC 9646-1 [2]].slave: The entity which performs the operations requested by the Master.System Under Test (SUT): The real open system in which the IUT resides [ISO/IEC 9646-1 [2]].Upper Tester (UT): The representation in ISO/IEC 9646-1 [2] of means of providing, during testexecution, control and observation of the upper service boundary of the IUT as defined by the chosenAbstract Test Method [ISO/IEC 9646-1 [2]].3.2AbbreviationsFor the purposes of this part of the I-ETS, the following abbreviations apply:ATSAbstract Test SuiteISDNIntegrated Services Digital NetworkIUTImplementation Under TestLTLower TesterOSIOpen Systems InterconnectionPCOPoint of Control and ObservationPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingSUTSystem Under TestTDUTelesoftware Data UnitTETerminal EquipmentTLVType, Length and ValueTSSTest Suite StructureTSS&TPTest Suite Structure and Test PurposesTTCNTree and Tabular Combined NotationUTUpper Tester4Test suite overview4.1Test Suite Structure (TSS)The Test Suite Structure (TSS) complies, in general, with ISO/IEC 9646-2 [3]. It is restricted to the use ofETS 300 075 [1] for the EUROFILE transfer profile (ETS 300 383 [5]; e.g. T_Protocol testing inSymmetrical Service).The test suite consists of test groups and test cases. Each test case has a narrowly defined purpose.Within the test suite nested test groups are used to provide a logical ordering of the test cases.Figure 1 shows the TSS for TDU testing. The test suite is hierarchically structured, and is composed of 4levels in the tree structure.SIST I-ETS 300 491-2 E1:2003

Page 11I-ETS 300 491-2: September 1996Basic InterconnectionTests (IT)Capability Tests (CA)see fig. 2Master (M)Valid Behaviour Tests (BV)see fig. 3Invalid Behaviour Tests (BI)see fig. 4Inopportune Behaviour Tests (BO)see fig. 5Processable Data FileTransfer Test SuiteBasic InterconnectionTests (IT)Capability Tests (CA)see fig. 2Slave (S)Valid Behaviour Tests (BV)see fig. 3Invalid Behaviour Tests (BI)see fig. 4Inopportune Behaviour Tests (BO)see fig. 6Figure 1: ETS 300 075 Test Suite StructureCapability Tests (CA)Functional Unitssee figure 7Figure 2: Capability test group structureProtocol Interactions (PI)Functional Unitssee fig. 7Valid Behaviour TestsParameter Variations (PV)Functional Unitssee fig. 7(BV)Parameter Combinations (PC)Functional Unitssee fig. 7Timer Variations (TI)Functional Unitssee fig. 7Figure 3: Valid Behaviour Test Group StructureProtocol Interactions (PI)Functional Unitssee fig. 7Invalid BehaviourParameter Variations (PV)Functional Unitssee fig. 7Tests (BI)Parameter Combinations (PC)Functional Unitssee fig. 7Figure 4: Invalid Behaviour Test Group StructureSIST I-ETS 300 491-2 E1:2003

Page 12I-ETS 300 491-2: September 1996Inopportune Events (IE)Inopportune BehaviourTests (BO) of InitiatorProtocol Interactions (PI)Figure 5: Inopportune Behaviour Test Group Structure (Initiator)Inopportune Event (IE)Inopportune BehaviourParameter Variations (PV)Functional Unitssee fig. 7Tests (BO) - ResponderParameter Combinations (PC)Functional Unitssee fig. 7Figure 6: Inopportune Behaviour Test Group Structure (Responder)Association (AS)Access (AC)Directory (DI)Save (SA)FunctionalLoad (LO)UnitsRename (RE)Delete (DE)File transfer (FT)Typed-data (TD)Figure 7: Functional units4.2Test groupsAt the highest level, the TSS consists of the roles, which determine the set of services.4.2.1Major rolesThe Master is the entity which controls the dialogue. The Slave is the entity which performs the operationsrequested by the Master.4.2.2Main test groups4.2.2.1Basic Interconnection Test (IT)The IT test should contain a basic set of Test Purposes which assures that there is a sufficientconformance for interconnection and that the chosen parameters are valid for the configuration.The IT group may have no additional structure.SIST I-ETS 300 491-2 E1:2003

Page 13I-ETS 300 491-2: September 19964.2.2.2Capability Tests (CA)The tests in this group are intended to check that the observable external static capabilities of theimplementation are valid with respect to the static conformance requirements expressed in the PICS ofthe IUT.4.2.2.3Valid Behaviour Tests (BV)All tests in the valid behaviour group are intended to verify, as thoroughly as possible, the variousfunctions of the protocol. This test group is further divided into tests that check the IUT's response to:-Protocol Interactions;-Parameter Variations;-Parameter Combinations;-Timer Variations.4.2.2.4Invalid Behaviour Tests (BI)This test group is intended to verify that the IUT is able to react properly having received an invalidProtocol Data Unit (PDU). Invalid PDU here means a syntactically invalid PDU. This test group is furtherdivided into tests that check the IUT's response to:-Protocol Interactions;-Parameter Variations;-Parameter Combinations.4.2.2.5Inopportune Behaviour Tests (BO)This test group is intended to check that the IUT is able to react properly, in case an inopportune protocolevent occurs. This test group is further divided into tests that check the IUT's response to:-Inopportune Event;-Protocol Interactions;-Parameter Variations;-Parameter Combinations.4.2.3Functional units test groupsThese test groups are:-ASAssociation;-ACAccess;-DIDirectory;-SASave;-LOLoad;-RERename;-DEDelete;-FTFile Transfer;-TDTyped-Data.4.3Test step structure4.3.1State definitionsThe following definitions of states correspond to different states entered by the IUT:IDLE:Physical connection established, no regime established.States for Association regime management:ASSOCIATE_PD:Associate pending, wait for association response PDU;ASSOCIATE:Associate regime established.SIST I-ETS 300 491-2 E1:2003

Page 14I-ETS 300 491-2: September 19964.3.2PreamblesSome of the specific Test Purposes described below require a preamble to ensure the IUT is in thecorrect state. When requiring a preamble, the test refers to a state which is already defined by a test case.4.3.3PostamblesAfter each test the IUT is brought back to the initial state, using an Abort Request.5Test Purposes presentation5.1IntroductionClause 5 contains the naming conventions and the writing rules for TDU testing. The first part of thisclause describes the naming convention of the Test Purposes referring to the groups to which theybelong, and the second part shows the pattern for the content of Test Purposes, depending on whetherthe IUT is the master or the slave.5.2Test Purpose naming conventionThe identifier of the Test Purpose naming convention takes the following form where each item of thereference name is composed as shown in the table below:Table 1: Test Purpose naming conventionsPattern:TC where:roleMSMasterSlave:category (main test group)12345IT, Basic Interconnection TestsCA, Capability testsBV, Valid Behaviour TestsBO, Inopportune Behaviour TestsBI, Invalid Behaviour Tests:functional aspectIVCETPI, Protocol InteractionPV, Parameter VariationsPC, Parameter CombinationsIE, Inopportune EventTI, Timer Variations:functional units123456789AS, ASsociation establishmentAC, ACcess establishmentDI, File DIrectorySA, SAve fileLO, LOad fileRE, REname fileDE, DElete fileFT, File TRansferTD, Typed-Data:sequential number(00-99)EXAMPLE:TCM3V107 is the number of test case 7, for the Master, to test the validbehaviour of the IUT, with parameter variations, during association phase.SIST I-ETS 300 491-2 E1:2003

Page 15I-ETS 300 491-2: September 19965.3Test Purpose writing rules5.3.1InitiatorTable 2: Test Purpose writing rules for the initiatorStructureValuesEnsure that the IUT in state in order to a containing aa) parameter encoded asand[repeat if necessary the parameters back to a)]then on from the tester a with the IUT Associate Idle, Access regime establishedestablish association regimesends, saves, does, etc.using.Associate request, Access requestapplication name, user data12, !K, .receivingAssociate Response, .appropriate parametersenters state, remains in state, terminates, .Association regime established5.3.2AcceptorTable 3: Test Purpose writing rules for the acceptorStructureValuesEnsure that the IUT in state on receiving a a containing aa) parameter encoded asand[repeat if necessary the parameters back to a)]and [remains in the same stateorenters state]Associate Idle, Access regime establishedassociation requestsends, saves, does, etc.using.Associate response posresult, .12, !K, .Association regime established6Test Purposes6.1IUT as a masterTest group objective:This test group is to test the action of an IUT when it acts as the Master.Subgroups:ITBasic Interconnection Tests;CACapability Tests;BVValid Behaviour Tests;BIInvalid Behaviour Tests;BOInopportune Behaviour Tests.SIST I-ETS 300 491-2 E1:2003

Page 16I-ETS 300 491-2: September 19966.1.1M/Basic Interconnection Tests (IT)No basic interconnection tests are explicitly identified for the testing of ETS 300 075 [1]. If tests arerequired, the following Test Purpose may be used: TCM2_101 - M/CA/AS.6.1.2M/Capability Tests (CA)Test group objective:To test functional capability of the IUT. It is structured according to functionalunits. The purpose of these tests is to establish whether a functional unit isavailable and, if so, a representative sample of each of the service elements isexercised.Subgroups:ASAssociation;ACAccess;DIDirectory;SASave;LOLoad;RERename;DEDelete;FTFile Transfer;TDTyped Data.6.1.2.1M/CA/AssociationTest group objective:Checking the capability of the IUT to:-enter association regime;-release association regime.Test Purposes (M/CA/AS):TCM2_101Ensure that the IUT in state idle, in order to establish association regime, sendsa T_ASSOCIATE Request, then on receiving from the tester a T_ASSOCIATEResponse Positive with appropriate parameters the IUT enters Associationregime (Ref. ETS 300 075 [1], subclause 4.1.3).TCM2_102Ensure that the IUT in state Association regime established, in order to releasethe association regime, sends a T_RELEASE request, then on receiving fromthe tester a T_RELEASE Response Positive with appropriate parameters theIUT returns to state idle (Ref. ETS 300 075 [1], subclause 4.1.3).6.1.2.2M/CA/AccessTest group objective:Checking the capability of the IUT to:-enter access regime;-terminate access regime.Test Purposes (M/CA/AC):TCM2_201Ensure that the IUT in state Association regime established, in order to establishaccess regime, sends a T_ACCESS Request, then on receiving from the testera T_ACCESS Response Positive with appropriate parameters the IUT entersAccess regime (Ref. ETS 300 075 [1], subclause 4.1.4).TCM2_202Ensure that the IUT in state Access regime established, in order to release theaccess regime, sends a T_END_ACCESS Request, then on receiving from thetester a T_END_ACCESS Response Positive with appropriate parameters theIUT returns to state Association regime established (Ref. ETS 300 075 [1],subclause 4.1.4).SIST I-ETS 300 491-2 E1:2003

Page 17I-ETS 300 491-2: September 19966.1.2.3M/CA/DirectoryTest group objective:Checking the capability of the IUT to send a Directory request without filetransfer.Test Purposes (M/CA/DI):TCM2_301Ensure that the IUT in state Access regime established, in order to request thefile directory of the tester, sends a T_DIRECTORY Request, then on receivingfrom the tester a T_DIRECTORY Response Positive with appropriateparameters the IUT enters Transfer regime as a receiver (Ref. ETS 300 075 [1],subclause 4.1.4.3.1).6.1.2.4M/CA/SaveTest group objective:Checking the capability of the IUT to send a Save request without file transfer.Test Purposes (M/CA/SA):TCM2_401Ensure that the IUT in state Access regime established, in order to save a file,sends a T_SAVE Request, then on receiving from the tester a T_SAVEResponse Positive with appropriate parameters the IUT enters Transfer regimeas a sender (Ref. ETS 300 075 [1], subclause 4.1.4.5.1).6.1.2.5M/CA/LoadTest group objective:Checking the capability of the IUT to send a Load request without file transfer.Test Purposes (M/CA/LO):TCM2_501Ensure that the IUT in state Access regime established, in order to load a file,sends a T_LOAD Request, then on receiving from the tester a T_LOADResponse Positive with appropriate parameters the IUT enters Transfer regimeas a receiver (Ref. ETS 300 075 [1], subclause 4.1.4.4.1).6.1.2.6M/CA/RenameTest group objective:Checking the capability of the IUT to send a Rename request.Test Purposes (M/CA/RE):TCM2_601Ensure that the IUT in state Access regime established, in order to rename afile, sends a T_RENAME Request, then on receiving from the tester aT_RENAME Response Positive with appropriate parameters the IUT remains instate Access regime established (Ref. ETS 300 075 [1], subclause 4.1.4.6.1).6.1.2.7M/CA/DeleteTest group objective:Checking the capability of the IUT to send a Delete request.Test Purposes (M/CA/DE):TCM2_701Ensure that the IUT in state Access regime established, in order to delete a file,sends a T_DELETE Request, then on receiving from the tester a T_DELETEResponse Positive with appropriate parameters the IUT remains in state Accessregime established (Ref. ETS 300 075 [1], subclause 4.1.4.7.1).SIST I-ETS 300 491-2 E1:2003

Page 18I-ETS 300 491-2: September 19966.1.2.8M/CA/File TransferTest group objective:Checking the capability of the IUT to:-send data by a Write request with no confirmation requested;-send data by a Write request with confirmation requested;-receive correctly a confirmed Write request.Test Purposes (M/CA/FT):TCM2_801Ensure that the IUT in state Transfer regime established, in order to transfer afile, sends a T_WRITE Request containing an explicit confirmation parameterencoded as no confirmation requested, remains in state Transfer regimeestablished (Ref. ETS 300 075 [1], subclause 4.1.5).TCM2_802Ensure that the IUT in state Transfer regime established, in order to transfer afile, sends a T_WRITE Request containing an explicit confirmation parameterencoded as confirmation requested; then on receiving from the tester aT_WRITE Response Positive the IUT remains in state Transfer regimeestablished (Ref. ETS 300 075 [1], subclause 6.2.12.2).TCM2_803Ensure that the IUT in state transfer regime established -IUT as a receiver-, onreceiving from the tester a T_WRITE Request containing explicit confirmationparameter encoded as confirmation requested, sends a T_WRITE ResponsePositive and remains in state transfer regime established (Ref. ETS 300 075 [1],subclause 4.1.5).6.1.2.9M/CA/Typed DataTest group objective:Checking the capability of the IUT to send a message to the tester.Test Purposes (M/CA/TD):TCM2_901Ensure that the IUT in state Access regime established, in order to transferinformation, sends a T_TYPED_DATA Request, and remains in state Accessregime established (Ref. ETS 300 075 [1], subclause 6.2.11).6.1.3M/Valid Behaviour Tests (BV)Test group objective:Checking the following conformance areas for the Master.Subgroups:PIProtocol Interactions;PVParameter Variations;PCParameter Combinations;IEInopportune Event.6.1.3.1M/BV/Protocol InteractionsTest group objective:Checking the valid behaviour subgrouped by functional units.Subgroups:ASAssociation;ACAccess;DIDirectory;SASave;LOLoad;RERename;DEDelete;FTFile Transfer;TDTyped Data.SIST I-ETS 300 491-2 E1:2003

Page 19I-ETS 300 491-2: September 19966.1.3.1.1M/BV/PI/AssociationTest group objective:Checking the valid behaviour of the IUT:-on association regime establishment refusal;-on a correct association release from the slave.Test Purposes (M/BV/PI/AS):TCM3I101 Ensure that the IUT in state Idle, in order to establish association regime, sendsa T_ASSOCIATE Request; then on receiving from the tester a T_ASSOCIATEResponse Negative with appropriate parameters, the IUT shall not establish theassociation regime (Ref. ETS 300 075 [1], subclause 6.2.1.2).TCM3I102Ensure that the IUT in association regime established, on receiving from thetester a T_RELEASE Request with appropriate parameters, sends aT_RELEASE Response Positive and terminates association regime(Ref. ETS 300 075 [1], subclause 6.2.2.3).6.1.3.1.2M/BV/PI/AccessTest group objective:Checking the valid behaviour of the IUT:-on access regime establishment refusal;-on reception of five successive negative acknowledgements to accessestablishment request.Test Purposes (M/BV/PI/AC):TCM3I201Ensure that the IUT in state association regime established, in order to establishaccess regime, sends a T_ACCESS Request; then on receiving from the testera T_ACCESS Response Negative with appropriate parameters, the IUT remainsin state association regime established (Ref. ETS 300 075 [1], subclause6.2.2.2).TCM3I202Ensure that the IUT in state association regime established, in order to establishaccess regime, sends five successive T_ACCESS Request; then on receivingfrom the tester the fifth T_ACCESS Response Negative, the IUT terminatesassociation regime (Ref. ETS 300 075 [1], subclause 6.3.3).6.1.3.1.3M/BV/PI/DirectoryTest group objective:Checking the valid behaviour of the IUT on Directory request refusal;Test Purposes (M/BV/PI/DI):TCM3I301Ensure that the IUT in state access regime established, in order to request thefile directory of the tester, sends a T_DIRECTORY Request; then on receivingfrom the tester a T_DIRECTORY Response Negative with appropriateparameters, the IUT returns to state access regime established(Ref. ETS 300 075 [1], subclause 6.2.6.2).6.1.3.1.4M/BV/PI/SaveTest group objective:Checking the valid behaviour of the IUT:-on save request refusal;-on reception of five successive acknowledgements to save requests.SIST I-ETS 300 491-2 E1:2003

Page 20I-ETS 300 491-2: September 1996Test Purposes (M/BV/PI/SA):TCM3I401Ensure that the IUT in state access regime established, in order to request a filesaving, sends a T_SAVE Request; then on receiving from the tester a T_SAVEResponse Negative with appropriate parameters, the IUT returns to stateaccess regime established (Ref. ETS 300 075 [1], subclause 6.2.8.2).TCM3I402Ensure that the IUT in state access regime established, in order to request a filesaving, sends five successive T_SAVE Request; then on receiving from thetester the fifth T_SAVE Response Negative, the IUT shall terminate associationregime (Ref. ETS 300 075 [1], subclause 6.3.2).6.1.3.1.5M/BV/PI/LoadTest group objective:Checking the valid behaviour of the IUT:-on load request refusal;-on reception of five successive acknowledgements to load requests.Test Purposes (M/BV/PI/LO):TCM3I501Ensure that the IUT in state access regime established, in order to request a fileloading, sends a T_LOAD Request; then on receiving from the tester a T_LOADResponse Negative with appropriate parameters, the IUT returns to stateaccess regime established (Ref. ETS 300 075 [1], subclause 6.2.7.2).TCM3I502Ensure that the IUT in state access regime established, in order to request a fileloading, sends five successive T_LOAD Request; then on receiving from thetester the fifth T_LOAD Response Negative, the IUT shall terminate associationregime (Ref. ETS 300 075 [1], subclause 6.3.2).6.1.3.1.6M/BV/PI/RenameTest group objective:Checking the valid behaviour of the IUT on Rename request refusal.Test Purposes (M/BV/PI/RE):TCM3I601Ensure that the IUT in state access regime established, in order to rename afile, sends a T_RENAME Request; then on receiving from the tester aT_RENAME Response Negative with appropriate parameters, the IUT returns tostate access regime established (Ref. ETS 300 075 [1], subclause 6.2.9.2).6.1.3.1.7M/BV/PI/DeleteTest group objective:Checking the valid behaviour of the IUT on Delete request refusal.Test Purposes (M/BV/PI/DE):TCM3I701Ensure that the IUT in state access regime established, in order to delete a file,sends a T_DELETE Request; then on receiving from the tester a T_DELETEResponse Negative with appropriate parameters, the IUT returns to stateaccess regime established (Ref. ETS 300 075 [1], subclause 6.2.10.2).6.1.3.1.8M/BV/PI/File TransferTest group objective:Checking that the IUT, on file transfer, is able to:-receive a file correctly with no confirmation requested;-receive a file correctly without confirmation requested;-send a file completely and correctly;-resume file transfer from the correct recovery point;-abandon transfer on repeated negative acknowledges;SIST I-ETS 300 491-2 E1:2003

Page 21I-ETS 300 491-2: September 1996-restart file transfer from the beginning;-give up file transfer on transfer reject;-perform a recovery with a Load request;-perform a recovery with a Save request;-receive a file with empty file content;-abandon transfer after expiration of application response timer;-receive a file correctly with last block empty.Test Purposes (M/BV/PI/FT):TCM3I801Ensure that the IUT in state transfer regime established -IUT as a receiver-, onreceiving from the tester a sequence of T_WRITE Request containing anexplicit confirmation parameter encoded as no confirmation requested and aT_WRITE_END Request, receives the file completely and correctly, and returnsto state access regime established (Ref. ETS 300 075 [1], subclause 6.2.12.3).TCM3I802Ensure that the IUT in state transfer regime established -IUT as a receiver-, onreceiving from the tester a sequence of T_WRITE Request containing anexplicit confirmation parameter encoded as confirmation requested and aT_WRITE_END Request, responds with the expected valid PDU sequence. TheIUT shall receive the file completely and correctly, and return to state accessregime established (Ref. ETS 300 075 [1], subclause 6.2.12.3).TCM3I803Ensure that the IUT in state transfer regime established -IUT as a sender-, inorder to transfer a file, sends a sequence of T_WRITE Request and aT_WRITE_END Request, then on receiving from the tester the valid PDUsequence, if relevant, the IUT returns to state access regime established. Checkthat the file was transmitted completely and correctly (Ref. ETS 300 075 [1],subclause 6.2.12.3).TCM3I804Ensure that the IUT in state transfer regime established -IUT as a sender-, inorder to transfer a file, sends a T_WRITE Request; then on receiving from thetester a T_WRITE Response Negative with appropriate parameters, the IUTshall resume the transfer from the last acknowledged block(Ref. ETS 300 075 [1], subclause 6.2.12.2).TCM3I805Ensure that the IUT in state transfer regime established -IUT as a sender-, inorder to transfer a file, sends five successive T_WRITE Request; then onreceiving from the tester the fifth T_WRITE Response Negative, the IUT shallsend a T_P_EXCEPTION Request and return to state access regimeestablished or terminate association regime (Ref. ETS 300 075 [1],subclause 6.3.2).TCM3I806Ensure that the IUT in state transfer regime established -IUT as a sender-, inorder to transfer a file, sends a T_WRITE Request; then on receiving from thetester a T_U_EXCEPTION_REPORT Request containing reason parameterencoded as READ RESTART, the IUT shall restart the mass transfer from thebeginning (Ref. ETS 300 075 [1], subclause 6.3.2).TCM3I807Ensure that the IUT in state transfer regime established -IUT as a sender-, inorder to transfer a file, sends a T_WRITE Request; then on receiving from thetester a T_U_EXCEPTION_REPORT Request containing reason parameterencoded as TRANSFER REJECT, the IUT shall give up file transfer and returnto state access regime established (Ref. ETS 300 075 [1], subclause 6.3.2).TCM3I808Ensure that the IUT is able to perform a recovery after a mass transfer abandonfrom the tester while the IUT is transferring the file. Check that the IUT shallsend a T_SAVE Request with correct designation and recovery number in orderto send the file correctly from the recovery point (Ref. ETS 300 075 [1],subclause 4.1.2.4.2).SIST I-ETS 300 491-2 E1:2003

Page 22I-ETS 300 491-2: September 1996TCM3I809Ensure that the IUT is able to perform a recovery after a mass transfer abandonfrom the tester while transferring the file. Check that the IUT shall send aT_LOAD Request with correct designation and recovery number in order toreceive the file correctly from the recovery point (Ref. ETS 300 075 [1],subclause 4.1.2.4.2).TCM3I810Ensure that the IUT is able to receive a file correctly, on receiving a filecontaining only a header (file content empty). Check that the IUT receives thefile completely and correctly and returns to access regime established(Ref. ETS 300 075 [1], subclause 7.3).TCM3I811Ensure that the IUT in state transfer regime established -IUT as a receiver-, onreceiving from the tester a sequence of T_WRITE Request and aT_WRITE_END Request containing an empty user data field, responds with theexpected valid PDU sequence. The IUT shall receive the file completely andcorrectly, and return to state access regime established (Ref. ETS 300 075 [1],subclause 4.1.5.1.3).6.1.3.1.9M/BV/PI/Typed DataTest group objective:Checking the valid behaviour of the IUT while sending a message.Test Pur
...