SIST ETS 300 356-36:1999

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the International interface; Part 36: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for supplementary services33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)33.020Telekomunikacije na splošnoTelecommunications in generalICS:Ta slovenski standard je istoveten z:ETS 300 356-36 E13SIST ETS 300 356-36:199en01-GHFHPEHU-1993SIST ETS 300 356-36:199SLOVENSKI
STANDARD
EUROPEANETS 300 356-36TELECOMMUNICATIONMarch 1998STANDARDSource: SPSReference: DE/SPS-01028-3ICS:33.020Key words:ISDN, SS7, ISUP, supplementary service, testing, ATS, PIXITIntegrated Services Digital Network (ISDN);Signalling System No.7;ISDN User Part (ISUP) version 2 for the International interface;Part 36: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT) proformaspecification for supplementary servicesETSIEuropean 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 356-36:1999

Page 2ETS 300 356-36: 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 356-36:1999

Page 3ETS 300 356-36: March 1998ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.93.1Definitions.93.2Abbreviations.104Implementation under test and test methods.114.1Identification of the system and implementation under test.114.2ATM and testing configuration for ISUP version 2.124.2.1Intermediate exchanges.134.2.2Local exchanges.144.2.3Master-slave aspects in the test configuration.175Conventions used within the ATS.175.1Test suite parameters, constants and variables.175.2Test case variables.175.3ASP constraints.175.4Timers.185.5Test suite operations.185.6Aliases.185.7Test case and step identifiers.185.8Constraints.185.9Dynamic behaviour.195.10Pre-test conditions.19Annex A (normative):ATS for ISUP version 2 supplementary services.20A.1The TTCN Graphical form (TTCN.GR).20A.2The TTCN Machine Processable form (TTCN.MP).20Annex B (normative):Partial PIXIT proforma for ISUP version 2 supplementary services.21B.1Identification summary.21B.2Abstract test suite summary.21B.3Test laboratory.21B.4Client identification.21B.5System Under Test (SUT).22B.6Ancillary protocols.22B.7Protocol information for ISUP.22B.7.1Protocol identification.22B.7.2IUT information - PIXIT proforma tables.22B.7.2.1General configuration.23B.7.2.2Parameter values.24B.7.2.3Timer values.26B.7.2.4Other information.27SIST ETS 300 356-36:1999

Page 4ETS 300 356-36: March 1998Annex C (normative):Protocol Conformance Test Report (PCTR) proforma for ISUP version 2supplementary services.28C.1Identification summary.28C.1.1Protocol conformance test report.28C.1.2IUT identification.28C.1.3Testing environment.28C.1.4Limits and reservation.29C.1.5Comments.29C.2IUT conformance status.29C.3Static conformance summary.29C.4Dynamic conformance summary.29C.5Static conformance review report.30C.6Test campaign report.30C.7Observations.42History.43SIST ETS 300 356-36:1999

Page 5ETS 300 356-36: 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 36 of a multi-part standard covering the ISDN User Part (ISUP) version 2 for theinternational interface, as described below:Part 1:"Basic services";Part 2:"ISDN supplementary services";Part 3:"Calling Line Identification Presentation (CLIP) supplementary service";Part 4:"Calling Line Identification Restriction (CLIR) supplementary service";Part 5:"Connected Line Identification Presentation (COLP) supplementary service";Part 6:"Connected Line Identification Restriction (COLR) supplementary service";Part 7:"Terminal Portability (TP) supplementary service";Part 8:"User-to-User Signalling (UUS) supplementary service";Part 9:"Closed User Group (CUG) supplementary service";Part 10:"Subaddressing (SUB) supplementary service";Part 11:"Malicious Call Identification (MCID) supplementary service";Part 12:"Conference call, add-on (CONF) supplementary service";Part 14:"Explicit Call Transfer (ECT) supplementary service";Part 15:"Diversion supplementary services";Part 16:"Call Hold (HOLD) supplementary service";Part 17:"Call Waiting (CW) supplementary service";Part 18:"Completion of Calls to Busy Subscriber (CCBS) supplementary service";Part 19:"Three-Party (3PTY) supplementary service";Part 31:"Protocol Implementation Conformance Statement (PICS) proforma specification for basicservices";Part 32:"Test Suite Structure and Test Purposes (TSS&TP) specification for basic services";Part 33:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing(PIXIT) proforma specification for basic services";Part 34:"Protocol Implementation Conformance Statement (PICS) proforma specification forsupplementary services";Part 35:"Test Suite Structure and Test Purposes (TSS&TP) specification for supplementaryservices";Part 36:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information forTesting (PIXIT) proforma specification for supplementary services".NOTE:Part 13 has been withdrawn.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 356-36:1999

Page 6ETS 300 356-36: March 1998Blank pageSIST ETS 300 356-36:1999

Page 7ETS 300 356-36: March 19981ScopeThis thirty-sixth part of ETS 300 356 provides the conformance test specification for the ISDN User Part(ISUP) version 2 supplementary services defined in ETS 300 356-2 [2] to ETS 300 356-19 [18] incompliance with the relevant requirements and in accordance with the relevant guidance given inISO/IEC 9646-1 [23].This ETS contains the Abstract Test Suite (ATS) for ISUP version 2 supplementary services, written inTree and Tabular Combined Notation (TTCN) as specified in ISO/IEC 9646-3 [25]. It is based onETS 300 356-35 [20] which specifies the Test Suite Structure and Test Purposes (TSS&TP).This ETS applies only to exchanges having implemented the ISUP version 2 protocol specifications [2-18].It is applicable for conformance testing of all types of exchanges as specified in the ISUP version 2protocol specifications [2-18]. This ETS does 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 contain the ATS for ISUP version 2 supplementary services (available on electronic media),the partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma and the ProtocolConformance 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.An ETS is referenced where it (partly) overrides the corresponding ITU-T Recommendation or where acorresponding ITU-T Recommendation does not exist (yet). For convenience, the respective section of anITU-T Recommendation is referenced when it is not overridden by a corresponding ETS.[1]ETS 300 356-1 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 1: Basic services [ITU-T Recommendations Q.761 to Q.764 (1993),modified]".[2]ETS 300 356-2 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 2: ISDN supplementary services [ITU-T Recommendation Q.730 (1993),modified]".[3]ETS 300 356-3 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 3: Calling Line Identification Presentation (CLIP) supplementary service[ITU-T Recommendation Q.731, clause 3 (1993), modified]".[4]ETS 300 356-4 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 4: Calling Line Identification Restriction (CLIR) supplementary service[ITU-T Recommendation Q.731, clause 4 (1993), modified]".[5]ETS 300 356-5 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 5: Connected Line Identification Presentation (COLP) supplementaryservice [ITU-T Recommendation Q.731, clause 5 (1993), modified]".SIST ETS 300 356-36:1999

Page 8ETS 300 356-36: March 1998[6]ETS 300 356-6 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 6: Connected Line Identification Restriction (COLR) supplementary service[ITU-T Recommendation Q.731, clause 6 (1993), modified]".[7]ETS 300 356-7 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 7: Terminal Portability (TP) supplementary service [ITU-T RecommendationQ.733, clause 4 (1993), modified]".[8]ETS 300 356-8 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 8: User-to-User Signalling (UUS) supplementary service [ITU-TRecommendation Q.737, clause 1 (1993), modified]".[9]ETS 300 356-9 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 9: Closed User Group (CUG) supplementary service [ITU-TRecommendation Q.735, clause 1 (1993), modified]".[10]ETS 300 356-10 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 10: Subaddressing (SUB) supplementary service [CCITT RecommendationQ.731, section 8 (1992), modified]".[11]ETS 300 356-11 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 11: Malicious Call Identification (MCID) supplementary service".[12]ETS 300 356-12 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 12: Conference call, add-on (CONF) supplementary service [ITU-TRecommendation Q.734, clause 1 (1993), modified]".[13]ETS 300 356-14 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 14: Explicit Call Transfer (ECT) supplementary service".[14]ETS 300 356-15 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 15: Diversion supplementary services [ITU-T Recommendation Q.732,clauses 2 to 5 (1993), modified]".[15]ETS 300 356-16 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 16: Call Hold (HOLD) supplementary service [ITU-T RecommendationQ.733, clause 2 (1993), modified]".[16]ETS 300 356-17 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 17: Call Waiting (CW) supplementary service [CCITT RecommendationQ.733, section 1 (1992), modified]".[17]ETS 300 356-18 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 18: Completion of Calls to Busy Subscriber (CCBS) supplementaryservice".[18]ETS 300 356-19 (1995): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; ISDN User Part (ISUP) version 2 for the international interface;Part 19: Three party (3PTY) supplementary service [ITU-T RecommendationQ.734, clause 2 (1993), modified]".SIST ETS 300 356-36:1999

Page 9ETS 300 356-36: March 1998[19]ETS 300 356-34: "Integrated Services Digital Network (ISDN); Signalling SystemNo.7; ISDN User Part (ISUP) version 2 for the international interface; Part 34:Protocol Implementation Conformance Statement (PICS) proforma specificationfor supplementary services".[20]ETS 300 356-35: "Integrated Services Digital Network (ISDN); Signalling SystemNo.7; ISDN User Part (ISUP) version 2 for the international interface; Part 35:Test Suite Structure and Test Purposes (TSS&TP) specification forsupplementary services".[21]ETS 300 406: "Methods for Testing and Specification (MTS); Protocol andprofile conformance testing specifications; Standardization methodology".[22]ETR 141: "Methods for Testing and Specification (MTS); Protocol and profileconformance testing specifications; The Tree and Tabular Combined Notation(TTCN) style guide".[23]ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 1: General concepts".[24]ISO/IEC 9646-2: "Information technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 2: Abstract Test Suitespecification".[25]ISO/IEC 9646-3: "Information technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 3: The Tree andTabular Combined Notation (TTCN)".[26]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 the ISUP version 2 reference specifications [1-18];-terms defined in ISO/IEC 9646-1 [23] and in ISO/IEC 9646-3 [25].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 [23], 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 [23],subclause 3.3.5).Abstract Test Suite (ATS): A test suite composed of abstract test cases (see ISO/IEC 9646-1 [23],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 [23], 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 [23], subclause 3.3.54).SIST ETS 300 356-36:1999

Page 10ETS 300 356-36: March 1998Point 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 [23], 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 [23], 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 [23], 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.System Under Test (SUT): The real open system in which the IUT resides (see ISO/IEC 9646-1 [23],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:3PTYThree-PartyASEApplication Service EntityASPAbstract Service PrimitiveATCAbstract Test CaseATMAbstract Test MethodATSAbstract Test SuiteCCBSCompletion of Calls to Busy SubscriberCDIVCall DiversionCFBCall Forwarding BusyCFNRCall Forwarding No ReplyCFUCall Forwarding UnconditionalCICCircuit Identification CodeCLIPCalling Line Identification PresentationCLIRCalling Line Identification RestrictionCntrlEControlling ExchangeCOLPConnected Line Identification PresentationCOLRConnected Line Identification RestrictionCONFConference call, add-onCUGClosed User GroupCWCall WaitingDLEDestination Local ExchangeDSS1Digital Subscriber Signalling System No. oneECTExplicit Call TransferHOLDCall HoldIncIEIncoming International ExchangeIntermEIntermediate ExchangeISCInternational Switching CentreISDNIntegrated Services Digital NetworkISUPISDN User PartITEInternational Transit ExchangeIUTImplementation Under TestSIST ETS 300 356-36:1999

Page 11ETS 300 356-36: March 1998IWorkEInterworking ExchangeLAPDLink Access Protocol for the D-channelLTLower TesterMCIDMalicious Call IdentificationMOTMeans Of TestingMTCMain Test ComponentMTPMessage Transfer PartNNINetwork-Network InterfaceNTENational Transit ExchangeOLEOriginating Local ExchangeOutIEOutgoing International ExchangePCOPoint of Control and ObservationPCTRProtocol Conformance Test ReportPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingPTCParallel Test ComponentSCSSystem Conformance StatementSPSignalling PointSPCSignalling Point CodeSS7Signalling System No.7SUBSubaddressingSUTSystem Under TestTCPTest Co-ordination ProceduresTSS&TPTest Suite Structure and Test PurposesTTCNTree and Tabular Combined NotationUNIUser-Network InterfaceUUSUser-to-User SignallingUUSnUUS service n (n = 1.3)4Implementation under test and test methods4.1Identification of the system and implementation under testThe System Under Test (SUT) is an exchange. The Implementation Under Test (IUT) is the ISUPversion 2 implementation in this exchange, mainly the part responsible for the supplementary servicesfunctionality, as shown in figure 1.ISUP v2SUTIUTExchangeAccesssupplementaryservicesISUPISUPSUT - System Under TestISUP - ISDN User PartIUT - Implementation Under TestFigure 1: Exchange as SUTThe ISUP signalling protocol can be observed on the SS7 link on the Network-Network Interface (NNI).The effects of signalling procedures of ISUP can be observed on the circuits controlled by the ISUP on theNNI.The ISUP implementation will in some exchanges have to interwork with the Access signalling system onthe User-Network Interface (UNI) and involve call handling in order to establish end-to-end connections.SIST ETS 300 356-36:1999

Page 12ETS 300 356-36: March 1998From ETS 300 356-1 [1], several types of exchanges (or roles) can be identified (see figure 2).OLEDLETransitNTEGatewayOutIETransitITEGatewayIncIEAccessAccessnationalnetworknationalnetworkinternationalnetworkintermediatelocallocalOLE - Originating Local ExchangeNTE - National
Transit ExchangeOutIE - Outgoing International ExchangeITE - International
Transit ExchangeIncIE - Incoming International ExchangeDLE - Destination Local ExchangeFigure 2: Roles of exchangesThe exchanges can be divided in two main groups according to their functionality: local exchanges, wherecalls originate and terminate, and intermediate exchanges, with transit functionality. Local exchanges arenational, i.e. belong to a national network. Intermediate exchanges are national or international. Theinternational intermediate exchanges which permit access to the international network are the gatewayexchanges (incoming and outgoing), also called International Switching Centres (ISCs). A particularity forsome supplementary services, e.g. call diversion services, is that a local exchange is not onlyoriginator/terminator of the call but also mediator between two far-end local exchanges.The roles of the exchanges are summarized in table 1.Table 1: Roles of exchangesLocalIntermediate exchangeexchangeNationalInternationalOriginating Local ExchangeOLETransit ExchangeNTEITEIncoming/Gateway ExchangeIncIEOutgoing/Gateway ExchangeOutIEDestination Local ExchangeDLE4.2ATM and testing configuration for ISUP version 2The Abstract Test Method (ATM) chosen for the ISUP version 2 supplementary services testingspecification is the distributed multi-party test method. The ATM is defined at an appropriate level ofabstraction so that the test cases may be specified appropriately, without adding restrictions to the IUT.The testing architectures are described in the following subclauses.The ATS is written in concurrent TTCN.SIST ETS 300 356-36:1999

Page 13ETS 300 356-36: March 19984.2.1Intermediate exchangesThe configuration proposed for testing intermediate exchanges is shown in figure 3. In order to test theprotocol and functionality of transit and gateway exchanges one needs to consider the incoming andoutgoing side of the 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 intermediate 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 356-36:1999

Page 14ETS 300 356-36: March 1998Figure 4 shows the actual used configuration for intermediate 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 intermediate exchangesThe 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.2Local exchangesWhen testing a local exchange as specified in the reference standard, it is difficult, if not impossible, toobserve only ISUP PDUs, if functionality such as connectivity, tones and announcements etc. associatedwith protocol events is to be considered and used to assign verdicts. The reference standard often refersto actions or events initiated by or to be observed by the calling or called user.A Point of Control of Observation (PCO) from ISUP (IUT) to the access side is needed, e.g. for stimulatingthe local exchange to originate a call (send an IAM). Another PCO is needed to check connectivity orgenerated tones by the local exchange.There is no exposed interface from ISUP (the IUT) towards the access side. For practical testingpurposes the natural choice is the access interface. It is therefore reasonable to make use of the accessinterface (e.g. the user access interface DSS1) as a PCO and to use existing naming conventions for theAbstract Service Primitives (ASPs) to be used on this PCO.SIST ETS 300 356-36:1999

Page 15ETS 300 356-36: March 1998Figure 5 presents a multi-party testing configuration for local exchanges. In this figure each tester has asingle PCO. The PCO for the access uses the underlying access service provider (e.g. LAPD, in case ofDSS1) for observing access events and stimulating the ISUP via the access. The ISUP implementation(IUT) cannot be tested without involving the User-Network Interface (UNI).SP ASP BIUTLTNetwork service providerCABLABLTISUP linkCircuitsTCPLTCall handlingACHAccess service providerLTAnnouncementstones, etc.Physical aspectsAPHUNIIUT - Implementation Under TestLT - Lower TesterTCP - Test Coordination ProceduresUNI - User-network interfaceSP - Signalling PointLAB - PCO for AB signalling linkCAB - Circuit PCO on AB interfaceACH - Access signalling PCO - (D-channel)APH - Access physical circuit PCO - (B-channel)Figure 5: ISUP test method for originating / destination exchangesOn the right side there are two PCOs as in the test configuration presented in the previous subclause. TheLAB PCO is used by the LT controlling the ISUP signalling link, whereas the CAB PCO is used by anotherLT controlling the traffic channels (for observing circuit related events, such as connectivity, 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.On the access side there are two PCOs and two LTs similar to the ones on network side. The ACH PCOis used to observe and control the Call Handling events, whereas the APH is used to control and observephysical aspects (e.g. tones and announcements).The access PDUs to be sent and observed on the ACH PCO are chosen at an appropriate level ofabstraction. For the access ASPs DSS1-like primitive names have been used, whereas access PDUconstraints have not been coded to the bit level. The access aspects cannot be left out for localexchanges, widening in this respect to some extent the scope of the ISUP testing.SIST ETS 300 356-36:1999

Page 16ETS 300 356-36: March 1998Figure 6 shows the actual used configuration for local exchanges, with a Master Testing Component(MTC), responsible for the A-B interface and a slave Parallel Testing Component (PTC), responsible forthe UNI access interface. The maintenance PCO is integrated in the MTC, for simplifying reasons.Network service providerCABLABTCPPTCIUTSP BMTCISUPsignalling,circuitsACHAccess service providerCall handlingAPHUNISP AIUT - Implementation Under TestMTC - Main Test ComponentPTC - Parallel Test ComponentTCP - Test Coordination ProceduresLAB - PCO for the AB signalling linkCAB - Circuit PCO for the AB interfaceACH - Access call handling
PCO
(D-channel)APH - Access physical circuit PCO
(B-channel)Figure 6: ISUP test configuration for local exchangesThere are test cases for local exchanges for some supplementary services where a mixed configuration isused. This configuration is presented in figure 7 and it may be deduced from the configurations presentedin figures 4 and 6.TCPNetwork service providerNetwork service providerCACCABLACLABTCPPTCPTCIUTSP CSP BMTCISUPsignalling,circuitsISUPsignalling,circuitsACHAccess service providerCall handlingAPHSP AIUT - Implementation Under TestMTC - Main Test ComponentPTC - Parallel Test ComponentTCP - Test Coordination ProceduresLAB - PCO for the AB signalling linkCAB - Circuit PCO for the AB interfaceLAB - PCO for the AC signalling linkCAB - Circuit PCO for the AC interfaceACH - Access call handling
PCO
(D-channel)APH - Access physical circuit PCO
(B-channel)UNIFigure 7: ISUP mixed test configuration for local exchangesIn this configuration the main test component located on the right side supervises two parallel testcomponents: one ISUP PTC and one access PTC. The local exchange in this case is the exchangeserving the user who activated the supplementary service.SIST ETS 300 356-36:1999

Page 17ETS 300 356-36: March 19984.2.3Master-slave aspects in the test configurationFigures 4, 6 and 7 show the logical test components of the adopted test configuration. The main testcomponent is located on the right side of the IUT, whereas on the left side there are different parallel testcomponents: ISUP (figure 4), access (figure 6) or both (figure 7).The ATS is written so that the appropriate configuration is chosen - depending on the exchange’s role tobe tested.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 be of any kind: it may be international or national ISUP, anaccess signalling system or a non-ISUP user part. At test execution exactly one of these configurationswill be chosen, based on the information provided in the PICS and PIXIT.For the gateway exchanges it is assumed by default that the call is set up from the left PTC to the rightMTC. So for outgoing international exchange the national network is located on the left side and theinternational network on the right side. For incoming international exchanges the international network islocated on the left side and the national network on the right side.The message flow in the test cases is designed in such a way that the verdict is assigned based onobserving the behaviour on the right side. The left side will in this case mainly act as a slavestimulus/acceptor. 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_Xxx5.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).SIST ETS 300 356-36:1999

Page 18ETS 300 356-36: March 19985.4TimersAll timers are named using the pattern:Tname[_min or _max]EXAMPLE:T7_min (waiting for ACM timer);TCFNR_max (call forwarding on no reply 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 primitive;R_XXXfor the receipt of an ISUP message XXX which is resolved to the MTPTRANSFER_IND primitive.5.7Test case and step identifiersThe general naming convention for the test cases is:ISS{_TC}_X_N_n{_n}{_a}where:TCdesignates ASE specific test cases (optional, used only for CCBS);X is either V - valid stimulus or I - inopportune stimulus;Nis the sequence number of the supplementary service;1st nis a sequence number used within the supplementary service;2nd nis an additional used number (optional, for UUS only); andais a lowercase letter to distinguish between tests in case of variants deriving from the sametest purpose.The general naming convention for the dispatcher test steps is:SS_N_n_{a}where N and n are the same as the test case to which they relate.Some generic steps with appropriate names, e.g. to complete the call-set-up (+S_ACM_etc_BA,+R_ACM_etc_AC) are also used.5.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.SIST ETS 300 356-36:1999

Page 19ETS 300 356-36: March 19985.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(s), either ISUP, or access, or both is (are) created. Forexample if the test configuration requires only an ISUP tester on the left side, then the ISUP parallel testcomponent is created, and so on.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. Often functionally related test steps are grouped together using local trees.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 description part of that test case.SIST ETS 300 356-36:1999

Page 20ETS 300 356-36: March 1998Annex A (normative):ATS for ISUP version 2 supplementary servicesThis ATS has been produced using the Tree and Tabular Combined Notation (TTCN) according toISO/IEC 9646-3 [25].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 (rsl.PDF contained in archive356{_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 (rsl.MP contained inarchive 356{_e1.LZH) which accompanies this ETS.NOTE:According to ISO/IEC 9646-3 [25], 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 356-36:1999

Page 21ETS 300 356-36: March 1998Annex B (normative):Partial PIXIT proforma for ISUP version 2supplementary servicesNotwithstanding 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 356ATS specification:ISUP_v2_suppl_servicesAbstract test method:Distributed multi-party test methodB.3Test laboratoryTest laboratory identification:Test laboratory manager:Test laboratory contact:Means of testing:Instructions for completion:B.4Client identificationClient identification:Client test manager:Test facilities required:SIST ETS 300 356-36:1999

Page 22ETS 300 356-36: March 1998B.5System Under Test (SUT)Name:Version:SCS number:Machine configuration:Operating system identification:IUT identification:PICS reference for IUT:Limitations of the SUT:Environmental conditions:B.6Ancillary protocolsProtocolnameVersion numberPICS referencePIXIT referencePCTR referenceMTPAccessprotocolB.7Protocol information for ISUPB.7.1Protocol identificationName:ISDN User Part (ISUP) version 2Version:PICS references:NOTE:The PICS reference should reference a completed PICS which is conformant with thePICS proforma contained in ETS 300 356-34.B.7.2IUT information - PIXIT proforma tablesThe PIXIT information requested in the following tables is needed to provide the necessary information forthe execution of the testing campaign. It is assumed that one exchange role is tested at one time. Theanswers to some PIXIT questions are related to an individual role. A typical example is the nature ofaddres
...