ETSI ETS 300 646-4 ed.1 (1998-03)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.OLþLFHSHFLILNDFLMHIntegrated Services Digital Network (ISDN); Signalling System No.7; Digital cellular telecommunications system (Phase 2); Application of ISDN User Part (ISUP) version 2 for the ISDN-Public Land Mobile Network (PLMN) signalling interface; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification33.020Telekomunikacije na splošnoTelecommunications in generalICS:Ta slovenski standard je istoveten z:ETS 300 646-4 Edition 13SIST ETS 300 646-4:1998en01-oktober-19983SIST ETS 300 646-4:1998SLOVENSKI
STANDARD



SIST ETS 300 646-4:1998



EUROPEANETS 300 646-4TELECOMMUNICATIONMarch 1998STANDARDSource: SPSReference: DE/SPS-01029-3ICS:33.020Key words:ISDN, SS7, ISUP, GSM, mobile, radio, PLMN, interworking, testing, ATS, PIXITIntegrated Services Digital Network (ISDN);Signalling System No.7;Digital cellular telecommunications system (Phase 2);Application of ISDN User Part (ISUP) version 2 for theISDN-Public Land Mobile Network (PLMN) signalling interface;Part 4: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT) proformaspecificationETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEInternet: secretariat@etsi.fr - http://www.etsi.fr - http://www.etsi.orgTel.: +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 1998. All rights reserved.SIST ETS 300 646-4:1998



Page 2ETS 300 646-4: March 1998Whilst 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 646-4:1998



Page 3ETS 300 646-4: March 1998ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.83.1Definitions.83.2Abbreviations.94Implementation under test and test methods.104.1Identification of the system and implementation under test.104.2ATM and testing configuration for ISUP version 2 for the ISDN-PLMN signallinginterface.104.2.1Gateway exchanges.114.2.2Master-slave aspects in the test configuration.125Conventions used within the ATS.125.1Test suite parameters, constants and variables.125.2Test case variables.135.3ASP constraints.135.4Timers.135.5Test suite operations.135.6Aliases.135.7Test case and step identifiers.135.8Constraints.145.9Dynamic behaviour.145.10Pre-test conditions.14Annex A (normative):ATS for ISUP version 2 for the ISDN-PLMN interface.15A.1The TTCN Graphical form (TTCN.GR).15A.2The TTCN Machine Processable form (TTCN.MP).15Annex B (normative):Partial PIXIT proforma for ISUP version 2 for the ISDN-PLMN interface.16B.1Identification summary.16B.2Abstract test suite summary.16B.3Test laboratory.16B.4Client identification.16B.5System Under Test (SUT).17B.6Ancillary protocols.17B.7Protocol information for ISUP.17B.7.1Protocol identification.17B.7.2IUT information - PIXIT proforma tables.17B.7.2.1General configuration.18B.7.2.2Parameter values.19B.7.2.3Timer values.19B.7.2.4Other information.19SIST ETS 300 646-4:1998



Page 4ETS 300 646-4: March 1998Annex C (normative):Protocol Conformance Test Report (PCTR) proforma for ISUP version 2 forthe ISDN-PLMN signalling interface.20C.1Identification summary.20C.1.1Protocol conformance test report.20C.1.2IUT identification.20C.1.3Testing environment.20C.1.4Limits and reservation.21C.1.5Comments.21C.2IUT conformance status.21C.3Static conformance summary.21C.4Dynamic conformance summary.21C.5Static conformance review report.22C.6Test campaign report.22C.7Observations.23History.24SIST ETS 300 646-4:1998



Page 5ETS 300 646-4: March 1998ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS is part 4 of a multi-part standard covering the application of Integrated Services Digital Network(ISDN) User Part (ISUP) version 2 for the ISDN-Public Land Mobile Network (PLMN) signalling interfaceas described below:Part 1:"Protocol specification (GSM 09.12)";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 3:"Test Suite Structure and Test Purposes (TSS&TP) specification";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information forTesting (PIXIT) proforma specification".Transposition datesDate of adoption of this ETS:6 March 1998Date of latest announcement of this ETS (doa):30 June 1998Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 December 1998Date of withdrawal of any conflicting National Standard (dow):31 December 1998SIST ETS 300 646-4:1998



Page 6ETS 300 646-4: March 1998Blank pageSIST ETS 300 646-4:1998



Page 7ETS 300 646-4: March 19981ScopeThis fourth part of ETS 300 646 provides the conformance test specification for the second version of theIntegrated Services Digital Network (ISDN) - Global System for Mobile communications (GSM) PublicLand Mobile Network (PLMN) signalling interface defined in ETS 300 646-1 [1] in compliance with therelevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-1 [6].This ETS contains the abstract test suite (ATS) for ISUP version 2 for the ISDN-PLMN interface, written inTree and Tabular Combined Notation (TTCN) as specified in ISO/IEC 9646-3 [8]. It is based onETS 300 646-3 [3] which specifies the Test Suite Structure and Test Purposes (TSS&TP).This ETS applies only to exchanges having implemented the ISUP version 2 protocol specification. It isapplicable for conformance testing of gateways in the fixed network or in the public land mobile networkas defined in the ISUP version 2 for the ISDN-PLMN interface specification ETS 300 646-1 [1]. This ETSdoes not deal with compatibility testing.The main text part of this ETS presents the requirements regarding the chosen test method and theconventions used within the ATS.The annexes present the ATS for ISUP version 2 for the ISDN-PLMN interface (available on electronicmedia), the partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma and theProtocol Conformance Test Report (PCTR) proforma.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 646-1 (1997): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; Digital cellular telecommunication systems (Phase 2); Applicationof the ISDN User Part (ISUP) version 2 for the ISDN-Public Land MobileNetwork (PLMN) signalling interface; Part 1: Protocol specification (GSM 09.12version 4.1.1)".[2]ETS 300 646-2: "Integrated Services Digital Network (ISDN); Signalling SystemNo.7; Digital cellular telecommunication systems (Phase 2); Application of theISDN User Part (ISUP) version 2 for the ISDN-Public Land Mobile Network(PLMN) signalling interface; Part 2: Protocol Implementation ConformanceStatement (PICS) proforma specification".[3]ETS 300 646-3: "Integrated Services Digital Network (ISDN); Signalling SystemNo.7; Digital cellular telecommunication systems (Phase 2); Application of theISDN User Part (ISUP) version 2 for the ISDN-Public Land Mobile Network(PLMN) signalling interface; Part 3: Test Suite Structure and Test Purposes(TSS&TP) specification".[4]ETS 300 406: "Methods for Testing and Specification (MTS); Protocol andprofile conformance testing specifications; Standardization methodology".[5]ETR 141: "Methods for Testing and Specification (MTS); Protocol and profileconformance testing specifications; The Tree and Tabular Combined Notation(TTCN) style guide".[6]ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 1: General concepts".[7]ISO/IEC 9646-2: "Information technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 2: Abstract Test Suitespecification".SIST ETS 300 646-4:1998



Page 8ETS 300 646-4: March 1998[8]ISO/IEC 9646-3: "Information technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 3: The Tree andTabular Combined Notation (TTCN)".[9]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, the following definitions apply:-terms defined in ETS 300 646-1 [1];-terms defined in ISO/IEC 9646-1 [6] and in ISO/IEC 9646-3 [8].In particular, the following terms apply:Abstract Test Case (ATC): A complete and independent specification of the actions required to achieve aspecific test purpose, defined at the level of abstraction of a particular Abstract Test Method, starting in astable testing state and ending in a stable testing state (see ISO/IEC 9646-1 [6], subclause 3.3.3).Abstract Test Method (ATM): The description of how an IUT is to be tested, given at an appropriate levelof abstraction to make the description independent of any particular realization of a Means of Testing, butwith enough detail to enable abstract test cases to be specified for this method (see ISO/IEC 9646-1 [6],subclause 3.3.5).Abstract Test Suite (ATS): A test suite composed of abstract test cases (see ISO/IEC 9646-1 [6],subclause 3.3.6).Implementation Under Test (IUT): An implementation of one or more OSI protocols in an adjacentuser/provider relationship, being part of a real open system which is to be studied by testing (seeISO/IEC 9646-1 [6], subclause 3.3.43).Means Of Testing (MOT): The combination of equipment and procedures that can perform thederivation, selection, parametrization and execution of test cases, in conformance with a referencestandardized ATS, and can produce a conformance log (see ISO/IEC 9646-1 [6], subclause 3.3.54).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 (seeISO/IEC 9646-1 [6], subclause 3.3.64).pre-test condition: A setting or state in the IUT which cannot be achieved by providing stimulus from thetest environment.Protocol Implementation Conformance Statement (PICS): A statement made by the supplier of aprotocol claimed to conform to a given specification, stating which capabilities have been implemented(see ISO/IEC 9646-1 [6], subclauses 3.3.39 and 3.3.80).PICS proforma: A document, in the form of a questionnaire, which when completed for animplementation or system becomes the PICS.Protocol Implementation eXtra Information for Testing (PIXIT): A statement made by a supplier orimplementor of an IUT (protocol) which contains or references all of the information related to the IUT andits testing environment, which will enable the test laboratory to run an appropriate test suite against theIUT (see ISO/IEC 9646-1 [6], subclauses 3.3.41 and 3.3.81).PIXIT proforma: A document, in the form of a questionnaire, which when completed for the IUT becomesthe PIXIT.SIST ETS 300 646-4:1998



Page 9ETS 300 646-4: March 1998System Under Test (SUT): The real open system in which the IUT resides (see ISO/IEC 9646-1 [6],subclause 3.3.103).user: The access protocol entity at the User side of the user-network interface where a T reference pointor coincident S and T reference point applies.3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ASPAbstract Service PrimitiveATCAbstract Test CaseATMAbstract Test MethodATSAbstract Test SuiteCICCircuit Identification CodeGMSCGateway MSCGSMGlobal System for Mobile communicationsIncGatewayIncoming fixed network gatewayIncGMSCIncoming GMSCISDNIntegrated Services Digital NetworkISUPISDN User PartIUTImplementation Under TestLTLower TesterMOTMeans Of TestingMSCMobile-service Switching CentreMSMobile StationMSISDNMobile Station ISDN numberMSRNMobile Station Roaming NumberMTCMain Test ComponentMTPMessage Transfer PartNNINetwork-network interfacePCOPoint of Control and ObservationPCTRProtocol Conformance Test ReportPTCParallel Test ComponentPDUProtocol Data UnitNINetwork IndicatorOutGatewayOutgoing fixed network gatewayOutGMSCOutgoing GMSCPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingPLMNPublic Land Mobile NetworkSCSSystem Conformance StatementSPSignalling PointSPCSignalling Point CodeSS7Signalling System No.7SUTSystem Under TestTCPTest Co-ordination ProceduresTSS&TPTest Suite Structure and Test PurposesTTCNTree and Tabular Combined NotationUNIUser-network interfaceUTUpper TesterVMSCVisited MSCSIST ETS 300 646-4:1998



Page 10ETS 300 646-4: March 19984Implementation under test and test methods4.1Identification of the system and implementation under testThe System Under Test (SUT) is a gateway exchange located either in the fixed (ISDN) network or in thePublic Land Mobile Network (PLMN). The Implementation Under Test (IUT) is the ISUP version 2implementation in this gateway exchange, as shown in figure 1.ISUP v2SUTIUTGateway exchangeISDN / PLMNinterfaceISUPISUPSUT - System Under TestISUP - ISDN User PartIUT - Implementation Under TestPLMN - Public Land Mobile NetworkISDN / PLMNinterfaceISDN - Integrated Services Digital NetworkFigure 1: Exchange as SUTAt least one of the shown ISUP signalling interfaces is a ISDN-PLMN signalling interface. The ISUPsignalling protocol can be observed on the SS7 link on the Network-Network Interface (NNI). The effectsof signalling procedures of ISUP can be observed on the circuits controlled by the ISUP on the NNI.From ETS 300 646-1 [1], two types of exchanges (or roles) can be identified (see figure 2).GMSCFixed networkPLMN networkGatewayISDN / PLMNinterfaceFigure 2: Roles of exchanges4.2ATM and testing configuration for ISUP version 2 for the ISDN-PLMN signalling interfaceThe Abstract Test Method (ATM) chosen for the ISUP version 2 for the ISDN-PLMN signalling interfacetesting specification is the distributed multi-party test method. The ATM is defined at an appropriate levelof abstraction so that the test cases may be specified appropriately, without adding restrictions to the IUT.The testing architecture is described in the following subclauses.The ATS is written in concurrent TTCN.SIST ETS 300 646-4:1998



Page 11ETS 300 646-4: March 19984.2.1Gateway exchangesThe configuration proposed for testing the gateway exchanges is shown in figure 3. In order to test theprotocol and functionality of gateway exchanges one needs to consider the incoming and outgoing side ofthe SUT.SP ASP BIUTLTNetwork service providerTCPCABLABLTISUP linkCircuitsLTLTPhysical aspectsCircuitsISUP linkNetwork service providerSP CCACLACIUT - Implementation Under TestLT - Lower TesterTCP - Test Coordination ProceduresSP - Signalling PointLAB - PCO for signalling link ABPCO - Point of Control and ObservationCAB - PCO for AB circuitsLAC - PCO for signalling link ACCAC - PCO for AC circuitsFigure 3: ISUP test method for gateway exchangesThe IUT is observed and controlled from two ISUP links with associated circuits. The Points of Controland Observation (PCO) are labelled LAB and CAB on one side, and LAC and CAC on the other.The LAB and LAC PCOs are used by the Lower Testers (LT) for controlling the ISUP signalling link,whereas the CAB and CAC PCOs are used by the lower testers for observing circuit related events, suchas connectivity, echo control check, alerting tone, etc.The ISUP PDUs to be sent and observed on the LAB PCO side allow for PDU constraints to be specifiedand coded down to the bit-level.NOTE:The underlying network service provider is the Message Transfer Part (MTP) protocolas specified in ITU-T Recommendations Q.701-Q.707/ETS 300 008.SIST ETS 300 646-4:1998



Page 12ETS 300 646-4: March 1998Figure 4 shows the actual used configuration for gateway exchanges, with a Main Test Component(MTC), responsible for the A-B interface and a slave Parallel Testing Component (PTC), responsible forthe C-A interface.Network service providerCABLABTCPPTCNetwork service providerSP CCACLACISUPsignalling,circuitsIUTSP BMTCISUPsignalling,circuitsSP AIUT - Implementation Under TestMTC - Main Test ComponentPCO - Point of Control and ObservationPTC - Parallel Test ComponentSP - Signalling PointLAB - PCO for signalling link ABCAB - Circuit PCO on AB interfaceLAC - PCO for signalling link ACCAC - Circuit PCO on AC interfaceFigure 4: ISUP test configuration for gateway exchangesFor some test cases, when the SUT is a GMSC, but the tested functionality is that of a VMSC, the paralleltest component also describes the behaviour on the PLMN access.The Test Co-ordination Procedures (TCP) allow for communication between the testers. The testcomponents are mostly implicitly co-ordinated (asynchronously); the TCPs are only used when it isnecessary to obtain the verdict from the parallel test component.4.2.2Master-slave aspects in the test configurationFigure 4 shows the logical test components of the adopted test configuration. The main test component islocated on the right side of the IUT, whereas on the left side there is the parallel test component.The right side main test component may be international or national ISUP and is configurable so that anytwo of these may be run, based on the answers given to PIXIT questions.The left side parallel test component may also be international or national ISUP. At test execution exactlyone combination will be chosen, based on the information provided in the PIXIT proforma.The message flow in the test cases is designed in such a way that the verdict is assigned based onobserving the behaviour on the MTC side. The left side will in this case mainly act as a slavestimulus/responder. There are, however, test cases where the expected behaviour of both sides is neededto assign the verdict.5Conventions used within the ATSThe abbreviations are consistently used within the ATS written in TTCN and are useful for understandingand/or maintaining the coding detail level.5.1Test suite parameters, constants and variablesMost test suite parameters are named using the pattern:TSP_XxxMost test suite variables are named using the pattern:TSV_XxxAll test suite constants are named using the pattern:TSC_XxxSIST ETS 300 646-4:1998



Page 13ETS 300 646-4: March 19985.2Test case variablesMost test case variables are named using the pattern:TCV_Xxx5.3ASP constraintsThe naming scheme for ASP constraints is:PDU_XY_more_specificwhere PDU indicates the PDU type included, XY indicates the direction and more_specific (if any)describes the constraint with abbreviated naming convention.EXAMPLE:IAM_BA_CgPN (IAM sent from SP B to SP A, with a calling party numberincluded).5.4TimersAll timers are named using the pattern:Tname[min or max]EXAMPLE:TearlyACMmin (waiting before sending early ACM timer).5.5Test suite operationsMost names for test suite operations follow the scheme:TSO_TestSuiteOperationNameThe TSO functions are specified using the syntax of C programming language or pseudo code.5.6AliasesAliases are extensively used instead of cumbersome names for ASP primitives (like MTPTRANSFER_IND).They are named using the scheme:S_XXXfor the sending of an ISUP message XXX which resolves to the MTPTRANSFER_REQ primitiveR_XXXfor the receipt of an ISUP message XXX which is resolved to the MTPTRANSFER_IND primitive5.7Test case and step identifiersThe general naming convention for the test cases is:IPB_{X}_Nfor the basic call; orIPS_{X}_Nfor the supplementary services.where X is either V (valid stimulus) or I (inopportune stimulus) and N is a sequence number.The general naming convention for the dispatcher test steps is:BC_N or SS_Nwhere N is the same sequence number as the test case to which it relates.Some generic steps with appropriate names, e.g. to complete the call-setup (+S_ACM_etc_BA,+R_ACM_etc_AC) are also used.SIST ETS 300 646-4:1998



Page 14ETS 300 646-4: March 19985.8ConstraintsThe constraints visible on the test case level are all ASP constraints. The ASPs are chained to PDUconstraints every time an ISUP message is involved. This allows for a higher level of abstraction on thetest case level and hides the information in the ASP constraint part. In order to reduce the number ofconstraints, a technique where a default constraint is manipulated/modified on the send line is used. Thisalso has the advantage of increasing readability. In the case of access ASPs, no further PDU constraintsare defined.5.9Dynamic behaviourThe general scheme of running a test case can be described shortly as follows:Firstly, the control is given to the main test component, which starts executing. This main test componentcontrols and observes the IUT on the AB signalling link.Secondly after possibly initializing some data the main test component creates the corresponding paralleltest component. This component is the slave process and it is located in a separate test step. It isdispatched using a parameter derived from the role of the exchange to be tested. For each test case theconcurrent "slave" parallel test component is created.The main (right) and the parallel (left) test components will then co-operate, most of the timeasynchronously driven by the received messages, until the test purpose is achieved and the verdict is set.The behaviour description is kept on an abstract level, hiding whenever it is possible programming detailsin the underlying test steps. Test steps are used whenever this saves code without decreasing thereadability of the test case.The comment fields are extensively used. The message sequence chart for the chosen testingconfiguration is provided at test case level to quickly give an overview of the expected behaviour.5.10Pre-test conditionsFor each test it is assumed that the circuits are unblocked from both sides and idle. If a particular testcase needs special pre-test conditions, these are presented in the description part of the test case.SIST ETS 300 646-4:1998



Page 15ETS 300 646-4: March 1998Annex A (normative):ATS for ISUP version 2 for the ISDN-PLMN interfaceThis ATS has been produced using the Tree and Tabular Combined Notation (TTCN) according toISO/IEC 9646-3 [8].The ATS was developed on a separate TTCN software tool and therefore the TTCN tables are notcompletely referenced in the contents table. The ATS itself contains a test suite overview part whichprovides additional information and references.A.1The TTCN Graphical form (TTCN.GR)The TTCN.GR representation of this ATS is contained in a PDF file (pls.PDF contained in archive6464_e1.LZH) which accompanies this ETS.A.2The TTCN Machine Processable form (TTCN.MP)The TTCN.MP representation corresponding to this ATS is contained in an ASCII file (pls.MP contained inarchive 6464_e1.LZH) which accompanies this ETS.NOTE:According to ISO/IEC 9646-3 [8], in case of a conflict in interpretation of theoperational semantics of TTCN.GR and TTCN.MP, the operational semantics of theTTCN.GR representation takes precedence.SIST ETS 300 646-4:1998



Page 16ETS 300 646-4: March 1998Annex B (normative):Partial PIXIT proforma for ISUP version 2 for the ISDN-PLMN interfaceNotwithstanding the provisions of the copyright clause related to the text of this ETS, ETSI grants thatusers of this ETS may freely reproduce the partial PIXIT proforma in this annex so that it can be used forits intended purposes and may further publish the completed PIXIT.B.1Identification summaryPIXIT number:Test laboratory name:Date of issue:Issued to:B.2Abstract test suite summaryProtocol specification:ETS 300 646-1ATS specification:ISUP_v2_ISDN_PLMNAbstract
...