SIST ETS 300 347-4 E1:2003
(Main)V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network layer (AN side)
V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network layer (AN side)
Abstract Test Suite specification (ATS in TTCN) and protocol implementation extra information for testing (PIXIT) proforma V5.2 interface for support of Access Network with up to N interfaces each at 2048 kBit/s with concentration capability within the Access Network
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.2 za podporo dostopovnemu omrežju (AN) – 4. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma specifikacija za omrežno plast na strani dostopovnega omrežja (AN)
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.2 za podporo dostopovnemu omrežju (AN) – 4. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma specifikacija za omrežno plast na strani dostopovnega omrežja (AN)V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network layer (AN side)33.040.30Komutacijski in signalizacijski sistemSwitching and signalling systemsICS:Ta slovenski standard je istoveten z:ETS 300 347-4 E1SIST ETS 300 347-4 E1:en01-RNWREHU-SIST ETS 300 347-4 E1:SLOVENSKI
STANDARD
SIST ETS 300 347-4 E1:2003
DRAFTEUROPEANprETS 300 347-4TELECOMMUNICATIONDecember 1997STANDARDSource: SPSReference: DE/SPS-03003.4-5ICS:33.020Key words:V interface, V5 interface, AN, ATS, ISDN, layer 3, PIXIT, PSTN, testingSignalling Protocols and Switching (SPS);V interfaces at the digital Local Exchange (LE);V5.2 interface for the support of Access Network (AN);Part 4: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT) proformaspecification for the network layer (AN side)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 4 92 94 42 00 - Fax: +33 4 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 1997. All rights reserved.SIST ETS 300 347-4 E1:2003
Page 2Draft prETS 300 347-4: December 1997Whilst 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 ETS 300 347-4 E1:2003
Page 3Draft prETS 300 347-4: December 1997ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.83.1Definitions.83.2Abbreviations.84Abstract test method.94.1ATM.94.2NWK layer protocol testing.94.3Data link addresses.104.4Execution of TCs.104.4.1Handling of error indication.104.4.2TC execution sequence.105Untestable test purposes.115.1Control protocol.115.2PSTN protocol.125.3Link control protocol.135.4BCC protocol.135.5Protection protocol.146Abstract test suite conventions.146.1Naming conventions.146.1.1Declaration part.146.1.2Constraint part.156.1.3Dynamic part.156.1.3.1Test cases.156.1.3.2Test steps.166.1.3.3General aspects.166.1.4ATS abbreviations.166.2Implementation conventions.176.2.1Declaration part.176.2.2Constraint part.176.2.3Dynamic part.176.2.4Documentation.18Annex A (normative):Abstract Test Suite (ATS).19A.1The TTCN Graphical form (TTCN.GR).19A.2The TTCN Machine Processable form (TTCN.MP).19Annex B (normative):Partial PIXIT proforma.20B.1Introduction.20B.2PIXIT proforma.20B.2.1Identification summary.20B.2.2Abstract test suite summary.20B.2.3Test laboratory.20B.2.4Client.20B.2.5SUT.20SIST ETS 300 347-4 E1:2003
Page 4Draft prETS 300 347-4: December 1997B.2.6Protocol layer information.20B.2.6.1Protocol identification.20B.2.6.2IUT information.21Annex C (informative):Bibliography.31History.32SIST ETS 300 347-4 E1:2003
Page 5Draft prETS 300 347-4: December 1997ForewordThis draft European Telecommunication Standard (ETS) has been produced by the Signalling Protocolsand Switching (SPS) Technical Committee of the European Telecommunications Standards Institute(ETSI), and is now submitted for the Public Enquiry phase of the ETSI standards approval procedure.This ETS is part 4 of a multi-part standard covering the V5.2 interface as described below:Part 1:"V5.2 interface specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma";Part 3:"Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (ANside)";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information forTesting (PIXIT) proforma specification for the network layer (AN side)";Part 5:"Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (LEside)";Part 6:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma specification for the network layer (LE side)";Part 7:"Test Suite Structure and Test Purposes (TSS&TP) specification for the data link layer";Part 8:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma specification for the data link layer";Part 9:"Test specification for the physical layer".Proposed transposition datesDate of latest announcement of this ETS (doa):3 months after ETSI publicationDate of latest publication of new National Standardor endorsement of this ETS (dop/e):6 months after doaDate of withdrawal of any conflicting National Standard (dow):6 months after doaSIST ETS 300 347-4 E1:2003
Page 6Draft prETS 300 347-4: December 1997Blank pageSIST ETS 300 347-4 E1:2003
Page 7Draft prETS 300 347-4: December 19971ScopeThis fourth part of ETS 300 347 contains the Abstract Test Suite (ATS) as well as the Abstract TestMethod (ATM) and the partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma forthe Network layer (NWK) of the V5.2 interface and parts of the system management of the AccessNetwork (AN) side of a V5.2 interface.The objective of this ETS is to provide an ATS containing conformance tests which give a high probabilityof inter-operability of an AN and a Local Exchange (LE) from different manufacturers over the V5.2interface.ISO/IEC 9646-1 [7] and ISO/IEC 9646-2 [8] are used as the basis for the test methodology. The ATS isdefined using the Tree and Tabular Combined Notation (TTCN) according to ISO/IEC 9646-3 [9].The ATS in annex A describes a set of Test Cases (TCs) which are based on the Test Purposes (TPs)specified in ETS 300 347-3 [6] (which is an extension of ETS 300 324-3 [2]). The TCs provide theimplementation of the TPs and can be converted into an executable test suite by using available TTCNtranslators and the corresponding tools.Annex B provides the partial PIXIT proforma.Annex C lists the informative references.2Normative referencesThis ETS incorporates by dated and 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 ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 324-1 (1994) including amendment A1 (1996): "Signalling Protocolsand Switching (SPS); V interfaces at the digital Local Exchange (LE); V5.1interface for the support of Access Network (AN); Part 1: V5.1 interfacespecification".[2]ETS 300 324-3: "Signalling Protocols and Switching (SPS); V interfaces at thedigital Local Exchange (LE); V5.1 interface for the support of Access Network(AN); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification forthe network layer (AN side)".[3]ETS 300 324-4: "Signalling Protocols and Switching (SPS); V interfaces at thedigital Local Exchange (LE); V5.1 interface for the support of Access Network(AN); Part 4: Abstract Test Suite (ATS) and partial Protocol ImplementationeXtra Information for Testing (PIXIT) proforma specification for the networklayer (AN side)".[4]ETS 300 347-1 (1994) including amendment A1 (1997): "Signalling Protocolsand Switching (SPS); V interfaces at the digital Local Exchange (LE); V5.2interface for the support of Access Network (AN); Part 1: V5.2 interfacespecification".[5]ETS 300 347-2 (1994) including amendment A1 (1997): "Signalling Protocolsand Switching (SPS); V interfaces at the digital Local Exchange (LE); V5.2interface for the support of Access Network (AN); Part 2: ProtocolImplementation Conformance Statement (PICS) proforma".[6]ETS 300 347-3: "Signalling Protocols and Switching (SPS); V interfaces at thedigital Local Exchange (LE); V5.2 interface for the support of Access Network(AN); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification forthe network layer (AN side)".SIST ETS 300 347-4 E1:2003
Page 8Draft prETS 300 347-4: December 1997[7]ISO/IEC 9646-1: "Information Technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 1: General concepts".[8]ISO/IEC 9646-2: "Information Technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 2: Abstract test suitespecification".[9]ISO/IEC 9646-3: "Information Technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 3: The Tree andTabular Combined Notation (TTCN)".[10]ISO/IEC 9646-5: "Information Technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 5: Requirements ontest laboratories and clients for the conformance assessment process".3Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, all definitions given in ETS 300 324-4 [3] apply.3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ANAccess NetworkASPAbstract Service PrimitiveATCAbstract Test CaseATMAbstract Test MethodATSAbstract Test SuiteBCCBearer Channel ConnectionBIInvalid BehaviourBOInopportune BehaviourBVValid BehaviourCACApability testCTRLControlDLLData Link LayerDSAPData link SAPFEFunction ElementIEInformation ElementIEIInformation Element IdentifierISDNIntegrated Services Digital NetworkISDN-BAISDN-Basic AccessISDN-PRAISDN-Primary Rate AccessITbasic Interconnection TestIUTImplementation Under TestL3addrLayer 3 addressLCLine CircuitLT1Lower Tester 1MPHManagement Physical layerNWKNetwork LayerSIST ETS 300 347-4 E1:2003
Page 9Draft prETS 300 347-4: December 1997PCOPoint of Control and ObservationPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingREQRequestSAPService Access PointSUTSystem Under TestTPTest PurposesTSSTest Suite StructureTTCNTree and Tabular Combined NotationULUpper LayerUTUpper TesterV5DLaddrV5 Data Link address4Abstract test methodThis clause describes the Abstract Test Method (ATM) and the Point of Control and Observation (PCO)used to test the NWK of the V5.2 protocol for the AN components.4.1ATMPrincipally, the remote test method is used for V5.2 AN NWK conformance testing. Certain V5.2 AN NWKTPs need also part of the service and national functions. Therefore, the embedded variant of the remotetest method is applied.The national dependant information is defined in the PIXIT.4.2NWK layer protocol testingThe V5.2 implementations do not offer a direct access to the upper service boundary. The remote testmethod was chosen because any co-ordination procedures can only be expressed in an informal way.SUTV5 NWK PDUsService ProviderDLL & PHL layersLT1Control,BCC, LINK,Protection and
PSTNDL connection endpointsV5 Test SystemIUTV5-NWKDL-DATAPCO/DSAPUTFigure 1: Remote single layer test method applied to the V5.2 NWK layer testingLT1:A Lower Tester (LT1) is located in a remote V5.2 test system. It controls andobserves the behaviours of the IUT.DSAP:A unique Data link Service Access Point (DSAP) is defined at the V5.2 interfaceand commonly used for exchanging service data of the different network layerprotocol functional entities.SIST ETS 300 347-4 E1:2003
Page 10Draft prETS 300 347-4: December 1997PCO:The PCOs for NWK testing are located on the DSAP, PSAP, PSTN_ACCESSand PCM_ACCESS interfaces. All test events at the DSAP are specified interms of data link layer Abstract Service Primitives (ASPs) and network layerPDUs. All test events at the PSAP
are specified in terms of physical layerASPs. All test events at PSTN_ACCESS and PCM_ACCESS are defined asASPs.UT:No explicit Upper Tester (UT) exists in the test system. However, the SUTneeds to carry out some UL functions to achieve some effects of test co-ordination procedures. Designing ATS, the capability of the systemmanagement functions, such as controls of the IUT, its interactions with the Qinterface may be taken into account. The controls of the IUT will be implied orinformally expressed in the ATS, but no assumption shall be made regardingtheir feasibility or realization. Examples of such controls could be to provokerestarting IUT or blocking/unblocking procedures through Q interface.V5-NWK:To test the PSTN and ISDN protocols, a simulator shall be attached to relevantUser Port (UP).4.3Data link addressesWithin the DSAP, different V5DLaddr are used to identify each corresponding data link connection. Eachnetwork layer protocol functional entity can have only one data link connection, e.g. all PSTN signallinginformation shares one data link connection.Table 1 shows the allocated V5DLaddr used by protocol function entities.Table 1: V5DLaddrProtocolPSTNControlBCCProtectionLink ControlV5DLaddr817681778178817981804.4Execution of TCs4.4.1Handling of error indicationDuring the execution of the NWK ATS many error indications will be sent to the system management dueto the invalid and the inopportune TCs. It is up to the IUT supplier to take the necessary precautions toavoid any impact on the test result.4.4.2TC execution sequenceThe following test sequence shall be applied:The TC containing the start-up procedure shall always be the first TC executed. Also in any case wherethe IUT has to be restarted this TC shall be first executed.Protocol groups:CTRL Þ LINKÞ PROTECTIONÞ PSTNÞ BCC.Test groups:IT Þ CA Þ TI Þ BV Þ BO Þ BI.Interactions between the different test groups are not considered. It is up to the IUT supplier to take thenecessary precautions to avoid any impact on the test result.NOTE:This applies in particular to PORT CONTROL messages from ISDN ports while testingPSTN-related protocols and vice versa.SIST ETS 300 347-4 E1:2003
Page 11Draft prETS 300 347-4: December 19975Untestable test purposesThis clause gives a list of TPs which are not implemented in the ATS due to the chosen abstract testmethod or other restrictions.5.1Control protocolTable 2 lists TPs which are not covered by the ATS due to unknown reaction of the IUT after testing theTPs.Table 2: Untestable TPs (1)Test PurposeReference to ETS 300 324-3 [2]TP1324S1101Refer to subclause 5.2.3.2.2TP1324S1002Refer to subclause 5.2.3.2.2TP1324SM_06Refer to subclause 5.2.3.2.2TP1324SM_07Refer to subclause 5.2.3.2.2TP1325SM_03Refer to subclause 5.2.3.2.3TP1325S2207Refer to subclause 5.2.3.2.3TP1325S2208Refer to subclause 5.2.3.2.3TP1325S2209Refer to subclause 5.2.3.2.3TP1424S1101Refer to subclause 5.2.4.2.2TP1425SM_01Refer to subclause 5.2.4.2.3TP1425SM_02Refer to subclause 5.2.4.2.3TP1425SM_03Refer to subclause 5.2.4.2.3Test PurposeReference to ETS 300 347-3 [6]TP1326S2008Refer to subclause 5.2.3.2.4TP1326S2009Refer to subclause 5.2.3.2.4TP1326S2010Refer to subclause 5.2.3.2.4TP1426SM_02Refer to subclause 5.2.4.2.4TP1426SM_03Refer to subclause 5.2.4.2.4Table 3 lists TPs which are not covered by the ATS because it is not possible to provoke the generation ofthe necessary events.Table 3: Untestable TPs (2)Test PurposeReference to ETS 300 347-3 [6]TP1326SM_07Refer to subclause 5.2.3.2.4TP1326S2011Refer to subclause 5.2.3.2.4TP1326S2012Refer to subclause 5.2.3.2.4TP1426SM_01Refer to subclause 5.2.4.2.4SIST ETS 300 347-4 E1:2003
Page 12Draft prETS 300 347-4: December 19975.2PSTN protocolThe following test purposes are not implemented in the ATS due to unknown reaction of the IUT aftertesting the TPs.Table 4: Untestable TPs (3)Test PurposeReference to ETS 300 324-3 [2]TP23__S0_01Refer to subclause 5.3.3.1TP23__S0_02Refer to subclause 5.3.3.1TP23__S0_03Refer to subclause 5.3.3.1TP23__S0_04Refer to subclause 5.3.3.1TP23__S0_05Refer to subclause 5.3.3.1TP23__S0_06Refer to subclause 5.3.3.1TP23__S0_07Refer to subclause 5.3.3.1TP23__S2_10Refer to subclause 5.3.3.3TP23__S3_10Refer to subclause 5.3.3.4TP23__S4_10Refer to subclause 5.3.3.5TP23__S7_10Refer to subclause 5.3.3.8TP24__S0_01Refer to subclause 5.3.4.1TP24__S0_02Refer to subclause 5.3.4.1TP24__S0_03Refer to subclause 5.3.4.1TP24__S0_04Refer to subclause 5.3.4.1TP24__S0_05Refer to subclause 5.3.4.1TP24__S0_06Refer to subclause 5.3.4.1TP24__S0_07Refer to subclause 5.3.4.1TP24__S0_08Refer to subclause 5.3.4.1TP24__S2_03Refer to subclause 5.3.4.3TP24__S2_04Refer to subclause 5.3.4.3TP24__S3_04Refer to subclause 5.3.4.4TP24__S3_05Refer to subclause 5.3.4.4TP24__S4_05Refer to subclause 5.3.4.5TP24__S5_04Refer to subclause 5.3.4.6TP24__S5_05Refer to subclause 5.3.4.6TP24__S5_06Refer to subclause 5.3.4.6TP24__S7_02Refer to subclause 5.3.4.8Table 5 lists TPs which are not covered by the ATS because it is not possible to provoke the generation ofthe necessary events.Table 5: Untestable TPs (4)Test PurposeReference to ETS 300 324-3 [2]TP23__S1_08Refer to subclause 5.3.3.2TP23__S1_09Refer to subclause 5.3.3.2TP23__S3_09Refer to subclause 5.3.3.4TP23__S4_06Refer to subclause 5.3.3.5TP23__S4_09Refer to subclause 5.3.3.5TP23__S6_05Refer to subclause 5.3.3.7TP23__S7_11Refer to subclause 5.3.3.8SIST ETS 300 347-4 E1:2003
Page 13Draft prETS 300 347-4: December 19975.3Link control protocolThe following test purposes are not implemented in the ATS due to unknown reaction of the IUT aftertesting the TPs.Table 6: Untestable TPs (5)Test PurposeReference to ETS 300 347-3 [6]TP33_1SM_03Refer to subclause 5.4.3.1TP33_7S2001Refer to subclause 5.4.3.2TP33_7S1002Refer to subclause 5.4.3.2TP33_7S1103Refer to subclause 5.4.3.2TP33_7S2204Refer to subclause 5.4.3.2TP33_7S2105Refer to subclause 5.4.3.2TP33_7SM_11Refer to subclause 5.4.3.2TP33_7S1112Refer to subclause 5.4.3.2TP33_7S1113Refer to subclause 5.4.3.2TP33_7SM_16Refer to subclause 5.4.3.2TP33_7SM_17Refer to subclause 5.4.3.2TP33_7S2222Refer to subclause 5.4.3.2TP33_7SM_29Refer to subclause 5.4.3.2The following test purposes are not implemented in the ATS due to the untestable Sa7 Bit.Table 7: Untestable TPs (6)Test PurposeReference to ETS 300 347-3 [6]TP33_7S2125Refer to subclause 5.4.3.2TP33_7S2126Refer to subclause 5.4.3.25.4BCC protocolTable 8 lists TPs which are not covered by the ATS because it is not possible to provoke the generation ofthe necessary events.Table 8: Untestable TPs (7)Test PurposeReference to ETS 300 347-3 [6]TP43__SM_21Refer to subclause 5.5.3TP44__S1_02Refer to subclause 5.5.4TP44__S1_03Refer to subclause 5.5.4TP44__S1_04Refer to subclause 5.5.4TP45__S1_11Refer to subclause 5.5.5TP46__S1_01Refer to subclause 5.5.6TP46__S1_02Refer to subclause 5.5.6SIST ETS 300 347-4 E1:2003
Page 14Draft prETS 300 347-4: December 19975.5Protection protocolThe following test purposes are not implemented in the ATS due to unknown reaction of the IUT aftertesting the TPs.Table 9: Untestable TPs (8)Test PurposeReference to ETS 300 347-3 [6]TP53__SM_18Refer to subclause 5.6.3TP56__S0_02Refer to subclause 5.6.6TP56__S1_04Refer to subclause 5.6.6Table 10 lists TPs which are not covered by the ATS because it is not possible to provoke the generationof the necessary events.Table 10: Untestable TPs (9)Test PurposeReference to ETS 300 347-3 [6]TP53__SM_05Refer to subclause 5.6.3TP53__SM_06Refer to subclause 5.6.3TP53__SM_20Refer to subclause 5.6.36Abstract test suite conventionsThe ATS conventions are intended to give a better understanding of the ATS but they describe also theconventions made for the development of the ATS, thus for any later maintenance purposes or furtherdevelopment of the ATS the conventions described in this clause shall be considered.The ATS conventions contain two clauses, the naming conventions and the implementation conventions.The naming conventions describe the structure of the naming of all ATS elements. The implementationconventions describe the functional structure of the ATS.NOTE:To define the ATS, the guidelines given in ETS 300 406 and ETR 141 wereconsidered.6.1Naming conventions6.1.1Declaration partThe ID names of the following definitions are written in lowercase:-structured type definitions;-ASP type definitions;-PDU type definitions.The ID names of the following definitions are written in uppercase:-Test Suite Parameter Declarations;-Test Case Selection Expression Definitions;-Test Suite Constant Declarations;-Test Case Variable Declarations.ID names of PDUs and structured types commence with a protocol identifier to define which protocol theyare belonging to. The following identifiers are used:-control protocol:ctrle.g. crtl_common_control_ack;-PSTN signalling:pstne.g. pstn_signal_ack.SIST ETS 300 347-4 E1:2003
Page 15Draft prETS 300 347-4: December 1997ID names of PDUs and structured types which are used for invalid tests commence with "bi".EXAMPLE:bi_com_ctrl_two_mety.Complete names as defined in the specifications are used for ID names of declarations.EXAMPLE:ctrl_control_function_element.Test suite parameter ID names commence with TSP:-PICS are identified by adding the letter "C":TSPC_. (e.g.: TSPC_PSTN);-PIXIT are identified by adding the letter "X":TSPX_. (e.g.: TSPX_PORT_ADDRESS).If the test suite parameter is representing a system parameter or value, only the parameter name is used.EXAMPLE:MR (receive sequence number in signal message).Test suite operations commence with TSO.EXAMPLE:TSO_INTEGER_TO_OCTETSTRING.Test suite constant ID names commence with TSC.EXAMPLE:TSC_CFE_FE201_2_UNBL.If the constant is representing a system parameter or value, only the parameter name is used.EXAMPLE:N01.ID names of Timers commence with T. The same names as in the specification are used.EXAMPLE:T01.6.1.2Constraint partConstraint names commence with uppercase. The remaining part of the ID name is written in lowercase.ID names of elements concerning the same subject have equivalent names in the declaration and theconstraint part:Declaration part:ctrl_control_function_element;Constraint part:Ctrl_control_function_element.The name of the modified constraint describes the particularity of the modified constraint.EXAMPLE:Ctrl_cc_mand_only (common control message which contains only themandatory IEs).If formal parameter lists are used, the variable names are written in lowercase. The variable name is thesame as the name of the element it is representing.6.1.3Dynamic part6.1.3.1Test casesThe identifier of the TCs is constructed in the same way as for the TPs described in ETS 300 347-3 [6],subclause 5.1.1, with the exception that "TP" is replaced by "TC".TP identifier:TP1324S1106;TC identifier:TC1324S1106.SIST ETS 300 347-4 E1:2003
Page 16Draft prETS 300 347-4: December 19976.1.3.2Test stepsIn TCs, test steps as well as local trees are used. To allow an easy distinction, the following naming isapplied:local tree:LTS_[local_tree_name];test step:STEP_[test-step_name].6.1.3.3General aspectsAll verdict assignments are labelled. To allow an exact identification in which table the verdict wasassigned, the following name convention is applied:Btest BodyCSCheck State test stepsDDefaultEError handling test stepsPOPOstamblePRPReambleStest StepCombinations of labels are also possible.EXAMPLE:DPR --> label which is used in a default for preambles.6.1.4ATS abbreviationsThese abbreviations are used to shorten identifier names:addraddressactactivateaccaccessackacknowledgementallocallocationcaucausecccommon controlcfecontrol function elementcficontrol function identifierchanchannelcomcommoncplcompletectrlcontroldldata linkenqenquiryestestablishfuncfunctionindindicationinterfinterfacemandmandatorymetymessage typemodmodifiedparparameterpcport controlpdprotocol discriminatorperformperformanceprogprogressprprotection protocolprotprotocolprovprovisionedreprore-provisioningreqrequestrestrestartrspresponseupuser portvarvariantverifyverifyingvidvariant & interface IDSIST ETS 300 347-4 E1:2003
Page 17Draft prETS 300 347-4: December 19976.2Implementation conventions6.2.1Declaration partThe comment line of single element TTCN tables (e.g. test suite constants) is used to give a referencewhere the format and content of the element is described in the relevant protocol specifications. Anyparticularity of the element format or content is described in the comment line.The comment line in the header of multi-element TTCN tables (e.g. ASPs) is used to reference to theprotocol s
...
SLOVENSKI STANDARD
SIST ETS 300 347-4 E1:2003
01-december-2003
Vmesniki V pri digitalnih krajevnih centralah (LE) – Vmesnik V5.2 za podporo
dostopovnemu omrežju (AN) – 4. del: Abstraktni preskušalni niz (ATS) in delna
dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma
specifikacija za omrežno plast na strani dostopovnega omrežja (AN)
V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access
Network (AN); Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma specification for the network layer (AN
side)
Ta slovenski standard je istoveten z: ETS 300 347-4 Edition 1
ICS:
33.040.30 Komutacijski in signalizacijski Switching and signalling
sistem systems
SIST ETS 300 347-4 E1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ETS 300 347-4 E1:2003
---------------------- Page: 2 ----------------------
SIST ETS 300 347-4 E1:2003
EUROPEAN ETS 300 347-4
TELECOMMUNICATION April 1999
STANDARD
Source: SPS Reference: DE/SPS-09003.4-5
ICS: 33.020
Key words: V interface, V5 interface, PSTN, ISDN, AN, ATS, PIXIT, testing, layer 3, LE
V interfaces at the digital Local Exchange (LE);
V5.2 interface for the support of Access Network (AN);
Part 4: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma
specification for the network layer (AN side)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: secretariat@etsi.fr - http://www.etsi.org
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
Copyright Notification: No 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.
---------------------- Page: 3 ----------------------
SIST ETS 300 347-4 E1:2003
Page 2
ETS 300 347-4: April 1999
Whilst 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 Standards Making Support Dept." at the address shown on the title page.
---------------------- Page: 4 ----------------------
SIST ETS 300 347-4 E1:2003
Page 3
ETS 300 347-4: April 1999
Contents
Foreword . 5
1 Scope. 7
2 Normative references . 7
3 Definitions and abbreviations. 8
3.1 Definitions. 8
3.2 Abbreviations. 8
4 Abstract test method. 9
4.1 ATM. 9
4.2 NWK layer protocol testing. 9
4.3 Data link Addresses .10
4.4 Execution of TCs . 10
4.4.1 Handling of error indication . 10
4.4.2 TC execution sequence . 10
5 Untestable test purposes . 11
5.1 Control protocol . 11
5.2 PSTN protocol . 11
5.3 Link control protocol . 12
5.4 BCC Protocol. 13
5.5 Protection protocol. 13
6 Abstract test suite conventions . 13
6.1 Naming conventions. 14
6.1.1 Declaration part. 14
6.1.2 Constraint part . 15
6.1.3 Dynamic part. 15
6.1.3.1 Test cases. 15
6.1.3.2 Test steps. 15
6.1.3.3 General aspects . 15
6.1.4 ATS abbreviations. 16
6.2 Implementation conventions. 16
6.2.1 Declaration part. 16
6.2.2 Constraint part . 17
6.2.3 Dynamic part. 17
6.2.4 Documentation. 18
Annex A (normative): Abstract test suite for NWK testing . 19
A.1 The TTCN Graphical form (TTCN.GR). 19
A.2 The TTCN Machine Processable form (TTCN.MP). 19
Annex B (normative): Partial PIXIT proforma . 20
B.1 Introduction . 20
B.2 PIXIT proforma . 20
B.2.1 Identification summary . 20
B.2.2 Abstract test suite summary. 20
B.2.3 Test laboratory. 20
B.2.4 Client . 21
B.2.5 SUT . 21
---------------------- Page: 5 ----------------------
SIST ETS 300 347-4 E1:2003
Page 4
ETS 300 347-4: April 1999
B.2.6 Protocol layer information .22
B.2.6.1 Protocol identification .22
B.2.6.2 IUT information.22
Annex C (informative): Bibliography.32
History.33
---------------------- Page: 6 ----------------------
SIST ETS 300 347-4 E1:2003
Page 5
ETS 300 347-4: April 1999
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS is part 4 of a multi-part standard covering the V5.2 interface as described below:
Part 1: "V5.2 interface specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (AN
side)";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification for the network layer (AN side)";
Part 5: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network layer (LE
side)";
Part 6: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification for the network layer (LE side)";
Part 7: "Test Suite Structure and Test Purposes (TSS&TP) specification for the data link layer";
Part 8: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma specification for the data link layer";
Part 9: "Test specification for the physical layer".
Transposition dates
Date of adoption of this ETS: 26 March 1999
Date of latest announcement of this ETS (doa): 30 June 1999
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 December 1999
Date of withdrawal of any conflicting National Standard (dow): 31 December 1999
---------------------- Page: 7 ----------------------
SIST ETS 300 347-4 E1:2003
Page 6
ETS 300 347-4: April 1999
Blank page
---------------------- Page: 8 ----------------------
SIST ETS 300 347-4 E1:2003
Page 7
ETS 300 347-4: April 1999
1 Scope
This fourth part of ETS 300 347 contains the Abstract Test Suite (ATS) as well as the Abstract Test
Method (ATM) and the partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for
the Network layer (NWK) of the V5.2 interface and parts of the system management of the Access
Network (AN) side of a V5.2 interface.
The objective of this ETS is to provide an ATS containing conformance tests which give a high probability
of inter-operability of an AN and a Local Exchange (LE) from different manufacturers over the V5.2
interface.
ISO/IEC 9646-1 [7] and ISO/IEC 9646-2 [8] are used as the basis for the test methodology. The ATS is
defined using the Tree and Tabular Combined Notation (TTCN) according to ISO/IEC 9646-3 [9].
The ATS in annex A describes a set of Test Cases (TCs) which are based on the Test Purposes (TPs)
specified in ETS 300 347-3 [6] (which is an extension of ETS 300 324-3 [2]). The TCs provide the
implementation of the TPs and can be converted into an executable test suite by using available TTCN
translators and the corresponding tools.
Annex B provides the partial PIXIT proforma.
Annex C lists the informative references.
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 324-1 (1994) including amendment A1: "V interfaces at the digital
Local Exchange (LE); V5.1 interface for the support of Access Network (AN);
Part 1: V5.1 interface specification".
[2] ETS 300 324-3 (1999): "V interfaces at the digital Local Exchange (LE); V5.1
interface for the support of Access Network (AN); Part 3: Test Suite Structure
and Test Purposes (TSS&TP) specification for the network layer (AN side)".
[3] ETS 300 324-4 (1999): "V interfaces at the digital Local Exchange (LE); V5.1
interface for the support of Access Network (AN); Part 4: Abstract Test Suite
(ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the network layer (AN side)".
[4] ETS 300 347-1 (1994) including amendment A1: "V interfaces at the digital
Local Exchange (LE); V5.2 interface for the support of Access Network (AN);
Part 1: V5.2 interface specification".
[5] ETS 300 347-2 (1994): "V interfaces at the digital Local Exchange (LE); V5.2
interface for the support of Access Network (AN); Part 2: Protocol
Implementation Conformance Statement (PICS) proforma".
[6] ETS 300 347-3 (1999): "V interfaces at the digital Local Exchange (LE); V5.2
interface for the support of Access Network (AN); Part 3: Test Suite Structure
and Test Purposes (TSS&TP) specification for the network layer (AN side)".
[7] ISO/IEC 9646-1: "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 1: General concepts".
[8] ISO/IEC 9646-2: "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 2: Abstract test suite
specification".
---------------------- Page: 9 ----------------------
SIST ETS 300 347-4 E1:2003
Page 8
ETS 300 347-4: April 1999
[9] ISO/IEC 9646-3: "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 3: The Tree and
Tabular Combined Notation (TTCN)".
[10] ISO/IEC 9646-5: "Information Technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 5: Requirements on
test laboratories and clients for the conformance assessment process".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, all definitions given in ETS 300 324-4 [3] apply.
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AN Access Network
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BCC Bearer Channel Connection
BI Invalid Behaviour
BO Inopportune Behaviour
BV Valid Behaviour
CA CApability test
CTRL Control
DLL Data Link Layer
DSAP Data link SAP
FE Function Element
IE Information Element
IEI Information Element Identifier
ISDN Integrated Services Digital Network
ISDN-BA ISDN-Basic Access
IT basic Interconnection Test
IUT Implementation Under Test
L3addr Layer 3 address
LC Line Circuit
LT1 Lower Tester 1
MPH Management Physical layer
NWK Network Layer
PCO Point of Control and Observation
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
REQ Request
SAP Service Access Point
SUT System Under Test
TP Test Purposes
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UL Upper Layer
UT Upper Tester
V5DLaddr V5 Data Link address
---------------------- Page: 10 ----------------------
SIST ETS 300 347-4 E1:2003
Page 9
ETS 300 347-4: April 1999
4 Abstract test method
This clause describes the Abstract Test Method (ATM) and the Point of Control and Observation (PCO)
used to test the NWK of the V5.2 protocol for the AN components.
4.1 ATM
Principally, the remote test method is used for V5.2 AN NWK conformance testing. Certain V5.2 AN NWK
TPs need also part of the service and national functions. Therefore, the embedded variant of the remote
test method is applied.
The national dependant information is defined in the PIXIT.
4.2 NWK layer protocol testing
The V5.2 implementations do not offer a direct access to the upper service boundary. The remote test
method was chosen because any co-ordination procedures can only be expressed in an informal way.
SUT V 5 Test System
UT
LT1
V 5 NW K PD Us
IUT
PCO/DSAP
V5-NW K
DL-DATA
Control,BCC, LINK,
Service Provider
Protection and PSTN
DLL & PHL layers
DL connection endpoints
Figure 1: Remote single layer test method applied to the V5.2 NWK layer testing
LT1: A Lower Tester (LT1) is located in a remote V5.2 test system. It controls and
observes the behaviours of the IUT.
DSAP: A unique Data link Service Access Point (DSAP) is defined at the V5.2 interface
and commonly used for exchanging service data of the different network layer
protocol functional entities.
PCO: The PCOs for NWK testing are located on the DSAP, PSAP, PSTN_ACCESS
and PCM_ACCESS interfaces. All test events at the DSAP are specified in
terms of Data Link Layer (DLL) Abstract Service Primitives (ASPs) and network
layer PDUs. All test events at the PSAP are specified in terms of physical layer
ASPs. All test events at PSTN_ACCESS and PCM_ACCESS are defined as
ASPs.
UT: No explicit Upper Tester (UT) exists in the test system. However, the SUT
needs to carry out some UL functions to achieve some effects of test co-
ordination procedures. Designing ATS, the capability of the system
management functions, such as controls of the IUT, its interactions with the Q
interface may be taken into account. The controls of the IUT will be implied or
informally expressed in the ATS, but no assumption shall be made regarding
their feasibility or realization. Examples of such controls could be to provoke
restarting IUT or blocking/unblocking procedures through Q interface.
---------------------- Page: 11 ----------------------
SIST ETS 300 347-4 E1:2003
Page 10
ETS 300 347-4: April 1999
V5-NWK: To test the PSTN and ISDN protocols, a simulator shall be attached to relevant
User Port (UP).
4.3 Data link Addresses
Within the DSAP, different V5DLaddr are used to identify each corresponding data link connection. Each
network layer protocol functional entity can have only one data link connection, e.g. all PSTN signalling
information shares one data link connection.
Table 1 shows the allocated V5DLaddr used by protocol function entities.
Table 1: V5DLaddr
Protocol PSTN Control BCC Protection Link Control
V5DLaddr 8176 8177 8178 8179 8180
4.4 Execution of TCs
4.4.1 Handling of error indication
During the execution of the NWK ATS many error indications will be sent to the system management due
to the invalid and the inopportune TCs. It is up to the IUT supplier to take the necessary precautions to
avoid any impact on the test result.
4.4.2 TC execution sequence
The following test sequence shall be applied:
The TC containing the start-up procedure shall always be the first TC executed. Also in any case where
the IUT has to be restarted this TC shall be first executed.
Protocol groups: CTRL ⇒ LINK⇒ PROTECTION⇒ PSTN⇒ BCC.
Test groups: IT ⇒ CA ⇒ TI ⇒ BV ⇒ BO ⇒ BI.
Interactions between the different test groups are not considered. It is up to the IUT supplier to take the
necessary precautions to avoid any impact on the test result.
NOTE: This applies in particular to PORT CONTROL messages from ISDN ports while testing
PSTN-related protocols and vice versa.
---------------------- Page: 12 ----------------------
SIST ETS 300 347-4 E1:2003
Page 11
ETS 300 347-4: April 1999
5 Untestable test purposes
This clause gives a list of TPs which are not implemented in the ATS due to the chosen abstract test
method or other restrictions.
5.1 Control protocol
Table 2 lists TPs which are not covered by the ATS due to unknown reaction of the IUT after testing the
TPs.
Table 2: Untestable TPs
Test Purpose
TP1326S2008
TP1326S2009
TP1326S2010
TP1326S2011
TP1326S2012
TP1426SM_01
TP1426SM_02
TP1426SM_03
NOTE: Only V5.2 specific TPs are listed. See ETS 300 324-4 [3] also.
5.2 PSTN protocol
See ETS 300 324-4 [3].
---------------------- Page: 13 ----------------------
SIST ETS 300 347-4 E1:2003
Page 12
ETS 300 347-4: April 1999
5.3 Link control protocol
The following test purposes are not implemented in the ATS due to unknown reaction of the IUT after
testing the TPs.
Table 3: Untestable TPs
Test Purpose
TP31__SM_01
TP32__SM_01
TP33_1S1_01
TP33_1SM_03
TP33_7S1002
TP33_7S1103
TP33_7S1112
TP33_7S1113
TP33_7S2001
TP33_7S2105
TP33_7S2125
TP33_7S2126
TP33_7S2204
TP33_7S2222
TP33_7SM_11
TP33_7SM_16
TP33_7SM_17
TP33_7SM_29
---------------------- Page: 14 ----------------------
SIST ETS 300 347-4 E1:2003
Page 13
ETS 300 347-4: April 1999
5.4 BCC Protocol
Table 4 lists TPs which are not covered by the ATS
Table 4: Untestable TPs
Test Purpose
TP41__SM_01
TP43__SM_21
TP44__S1_02
TP44__S1_03
TP44__S1_04
TP46__S1_01
TP46__S1_02
5.5 Protection protocol
The following test purposes are not implemented in the ATS
Table 5: Untestable TPs
Test Purpose
TP51__SM_01
TP53__SM_05
TP53__SM_06
TP53__SM_18
TP53__SM_20
TP56__S0_02
TP56__S1_04
6 Abstract test suite conventions
The ATS conventions are intended to give a better understanding of the ATS but they describe also the
conventions made for the development of the ATS, thus for any later maintenance purposes or further
development of the ATS the conventions described in this clause shall be considered.
The ATS conventions contain two clauses, the naming conventions and the implementation conventions.
The naming conventions describe the structure of the naming of all ATS elements. The implementation
conventions describe the functional structure of the ATS.
NOTE: To define the ATS, the guidelines given in ETS 300 406 and ETR 141 were
considered.
---------------------- Page: 15 ----------------------
SIST ETS 300 347-4 E1:2003
Page 14
ETS 300 347-4: April 1999
6.1 Naming conventions
6.1.1 Declaration part
The ID names of the following definitions are written in lowercase:
- structured type definitions;
- ASP type definitions;
- PDU type definitions.
The ID names of the following definitions are written in uppercase:
- Test Suite Parameter Declarations;
- Test Case Selection Expression Definitions;
- Test Suite Constant Declarations;
- Test Case Variable Declarations.
ID names of PDUs and structured types commence with a protocol identifier to define which protocol they
are belonging to. The following identifiers are used:
- control protocol: ctrl e.g. crtl_common_control_ack;
- PSTN signalling: pstn e.g. pstn_signal_ack.
ID names of PDUs and structured types which are used for invalid tests commence with "bi".
EXAMPLE 1: bi_com_ctrl_two_mety.
Complete names as defined in the specifications are used for ID names of declarations.
EXAMPLE 2: ctrl_control_function_element.
Test suite parameter ID names commence with TSP:
- PICS are identified by adding the letter "C": TSPC_. (e.g.: TSPC_PSTN);
- PIXIT are identified by adding the letter "X": TSPX_. (e.g.: TSPX_PORT_ADDRESS).
If the test suite parameter is representing a system parameter or value, only the parameter name is used.
EXAMPLE 3: MR (receive sequence number in signal message).
Test suite operations commence with TSO.
EXAMPLE 4: TSO_INTEGER_TO_OCTETSTRING.
Test suite constant ID names commence with TSC.
EXAMPLE 5: TSC_CFE_FE201_2_UNBL.
If the constant is representing a system parameter or value, only the parameter name is used.
EXAMPLE 6: N01.
ID names of Timers commence with T. The same names as in the specification are used.
EXAMPLE 7: T01.
---------------------- Page: 16 ----------------------
SIST ETS 300 347-4 E1:2003
Page 15
ETS 300 347-4: April 1999
6.1.2 Constraint part
Constraint names commence with uppercase. The remaining part of the ID name is written in lowercase.
ID names of elements concerning the same subject have equivalent names in the declaration and the
constraint part:
- Declaration part: ctrl_control_function_element;
- Constraint part: Ctrl_control_function_element.
The name of the modified constraint describes the particularity of the modified constraint.
EXAMPLE: Ctrl_cc_mand_only (common control message which contains only the
mandatory IEs).
If formal parameter lists are used, the variable names are written in lowercase. The variable name is the
same as the name of the element it is representing.
6.1.3 Dynamic part
6.1.3.1 Test cases
The identifier of the TCs is constructed in the same way as for the TPs described in ETS 300 347-3 [6],
subclause 5.1.1, with the exception that "TP" is replaced by "TC".
- TP identifier: TP1324S1106;
- TC identifier: TC1324S1106.
6.1.3.2 Test steps
In TCs, test steps as well as local trees are used. To allow an easy distinction, the following naming is
applied:
- local tree: LTS_[local_tree_name];
- test step: STEP_[test-step_name].
6.1.3.3 General aspects
All verdict assignments are labelled. To allow an exact identification in which table the verdict was
assigned, the following name convention is applied:
B test Body
CS Check State test steps
D Default
E Error handling test steps
PO POstamble
PR PReamble
S test Step
Combinations of labels are also possible.
EXAMPLE: DPR --> label which is used in a default for preambles.
---------------------- Page: 17 ----------------------
SIST ETS 300 347-4 E1:2003
Page 16
ETS 300 347-4: April 1999
6.1.4 ATS abbreviations
These abbreviations are used to shorten identifier names:
addr address
act activate
acc access
ack acknowledgement
alloc allocation
cau cause
cc common control
cfe control function element
cfi control function identifier
chan channel
com common
cpl complete
ctrl control
dl data link
enq enquiry
est establish
func function
ind indication
interf interface
mand mandatory
mety message type
mod modified
par parameter
pc port control
pd protocol discriminator
perform performance
prog progress
pr protection protocol
prot protocol
prov provisioned
repro re-provisioning
req request
rest restart
rsp response
up user port
var variant
verify verifying
vid variant & interface ID
6.2 Implementation conventions
6.2.1 Declaration part
The comment line of single element TTCN tables (e.g. test suite constants) is used to give a reference
where the format and content of the element is described in the relevant protocol specifications. Any
particularity of the element format or content is described in the comment line.
The comment line in the header of multi-element TTCN tables (e.g. ASPs) is used to reference to the
protocol specification.
The detailed comments are used to describe any particularity of the table.
In the ASP and PDU declarations, the comments column is used to identify if an element is mandatory or
optional.
m: mandatory;
o: optional.
---------------------- Page: 18 ----------------------
SIST ETS 300 347-4 E1:2003
Page 17
ETS 300 347-4: April 1999
In the ASP and PDU declarations the comments column is further used to give information about the
element value, in particular if the element contains a fixed spare value.
In tables where structure types are used the information element and the relevant structured type have
always the same name, that allows to have the same structure as in the protocol standards is used to
document the relation between information elements in a table and their specific description in an other
clause of the protocol standard.
6.2.2 Constraint part
The ASPs and PDUs are defined in a way that all relevant element are parameterized. That improves the
transparency of the constraints in the dynamic part, as all values which are relevant for the test are always
present.
Generally the base constraint contains all possible parameters and the relevant formal parameter list
which goes with the base constraint. In case where a specific message IE is not used at all in the ATS, the
base constraint will not contain such an IE. The base constraints of the PSTN protocol contain all
mandatory IEs. The optional IEs are defined in one element of type OCTETSTRING. The actual value and
format of the optional IE has to be defined in the PIXITs according to the PSTN specifications which is
implemented in the IUT.
Modified constraints have the same parameter list as the base constraint. Not used elements of the
parameter list are set to a default value "ANY" in the dynamic part. The number of base constraints is
reduced to a minimum.
The comment line of a constraint contains always the reference to the used specifications. The detailed
comments sector is used to describe any particularity of the table.
6.2.3 Dynamic part
Some TCs need a particular initialization of the IUT environment conditions to run the actual test, e.g. for
testing re-provisioning procedures. Such message sequence can be quite complicated and long. In cases
where a Local Test Step (LTS) facilitates the TC structure, the preamble and the condition setting are
described in a LTS called LTS_pre_step. All LTS_pre_steps are described in the detailed comment part
of the TTCN table.
Some TCs need after the actual test a particular re-initialization of the IUT, e.g. after re-provisioning. Such
message sequence can be quite complicated and long. In cases where a Local Test Step (LTS) facilitates
the TC
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.