ETSI ETS 300 374-4 ed.1 (1997-12)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Inteligentno omrežje (IN) - Prvi nabor zmožnosti (CS1) inteligentnega omrežja - Jedrni aplikacijski protokol inteligentnega omrežja (INAP) - 4. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) - Proforma specifikacije za funkcijo komutacije storitev (SSF) in funkcijo posebnih virov (SRF)Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for Service Switching Function (SSF) and Specialized Resource Function (SRF)33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:ETS 300 374-4 Edition 1SIST ETS 300 374-4:1998en01-oktober-1998SIST ETS 300 374-4:1998SLOVENSKI
STANDARD
EUROPEANETS 300 374-4TELECOMMUNICATIONDecember 1997STANDARDSource: SPSReference: DE/SPS-03016-2ICS:33.020Key words:IN, CS1, INAP, ATS, PIXIT, testingIntelligent Network (IN);Intelligent Network Capability Set 1 (CS1);Core Intelligent Network Application Protocol (INAP);Part 4: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT) proformaspecification for Service Switching Function (SSF) andSpecialized Resource Function (SRF)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 374-4:1998

Page 2ETS 300 374-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 374-4:1998

Page 3ETS 300 374-4: December 1997ContentsForeword.91Scope.112Normative references.113Definitions and abbreviations.123.1Definitions.123.2Abbreviations.134Abstract test method and test configurations.144.1SUT and IUT.144.2SUT interfaces.144.3Lower Testers (LTs).144.4Upper Tester (UT).154.5Underlying SS7 protocols.154.6TCAP emulation in test system.154.7Points of Control and Observation (PCOs).154.8Co-ordination Points (CPs) and Co-ordination Messages (CMs).154.9Test configurations.154.9.1Test configuration for SSF testing.164.9.2Test configuration for SRF testing.164.10Single-Party Testing (SPyT).174.11Multi-Party Testing (MPyT).174.12Abstract test method.174.12.1Remote test method in SPyT context 1.174.12.2Remote test method in MPyT context 2 and context 3.184.12.3Remote test method in MPyT context 4.184.12.4Remote test method in SPyT context 5.194.12.5Remote test method in MPyT context 6.194.13Usage of test configurations and test context.204.13.1Use of the test context 1.204.13.2Use of the test context 2.204.13.3Use of the test context 3.204.13.4Use of the test context 2 or 3.204.13.5Use of the test context 4.214.13.6Use of test context 2, 3 or 4.214.13.7Use of the test context 5.214.13.8Use of the test context 6.214.14Testing sequence.214.14.1SSF testing sequence.224.14.2SRF testing sequence.225Abstract test suite convention.225.1Naming conventions.225.1.1Naming test groups and test subgroups.225.1.2Naming convention for Declaration part.235.1.2.1ASN1 type definitions.235.1.2.2TTCN ASPs.235.1.2.3ASN1 PDUs.235.1.2.4Test suite parameters.245.1.2.5Test suite constant declarations.245.1.2.6Test case selection expressions.245.1.2.7Test case variables.245.1.2.8Test suite operations.245.1.2.9Timers.245.1.3Naming conventions for Constraint part.25SIST ETS 300 374-4:1998

Page 4ETS 300 374-4: December 19975.1.3.1TTCN ASP constraints.255.1.3.2ASN1 PDU constraints.255.1.4Naming conventions for Dynamic part.265.1.4.1Test cases.265.1.4.2Test steps and test step groups.265.2Conventions for design of the ATS.265.2.1Test group and test case selections.275.2.2TTCN ASP definitions in declaration part.275.2.2.1Dialogue handling ASPs.275.2.2.2Component handling ASPs.275.2.3ASN.1 PDU definitions.27Annex A (normative):Partial PIXIT proforma.28A.1Identification summary.28A.2Abstract test suite summary.28A.3Test laboratory.29A.3.1Test laboratory identification.29A.3.2Accreditation status of the test service.29A.3.3Manager of test laboratory.29A.3.4Contact person of test laboratory.29A.3.5Means of testing.30A.3.6Instructions for completion.30A.4Client.31A.4.1Client identification.31A.4.2Client test manager.31A.4.3Client contact person.31A.4.4Test facilities required.32A.5System under test.32A.5.1SUT information.32A.5.2Limitations of the SUT.33A.5.3Environmental conditions.33A.6Ancillary protocols.33A.6.1Ancillary protocols 1.34A.6.2Ancillary protocols 2.34A.6.3Ancillary protocols 3.34A.6.4Ancillary protocols 4.34A.7Protocol layer information for core INAP CS 1.35A.7.1Protocol identification.35A.7.2IUT information.35A.7.2.1Addresses.35A.7.2.2Parameter values.35A.7.2.2.1Parameter TSPX_aChBillingChargingCharacteristics_1.36A.7.2.2.2Parameter TSPX_aChBillingChargingCharacteristics.36A.7.2.2.3Parameter TSPX_acExtensions.37A.7.2.2.4Parameter TSPX_ariCorrelationID.37A.7.2.2.5Parameter TSPX_asfDuration.38A.7.2.2.6Parameter TSPX_asfServiceKey.38A.7.2.2.7Parameter TSPX_asfCalledAddress.38A.7.2.2.8Parameter TSPX_asfCallingAddress.39A.7.2.2.9Parameter TSPX_asfLocationNumber.39A.7.2.2.10Parameter TSPX_asfExtensions.40A.7.2.2.11Parameter TSPX_filteredCallTreatment.41A.7.2.2.12Parameter TSPX_filteringCharacteristics.41A.7.2.2.13Parameter TSPX_filteringTimeOut.42A.7.2.2.14Parameter TSPX_filteringCriteria.42A.7.2.2.15Parameter TSPX_SFBillingChargingChar.43SIST ETS 300 374-4:1998

Page 5ETS 300 374-4: December 1997A.7.2.2.16Parameter TSPX_asfFilteringInterval.43A.7.2.2.17Parameter TSPX_asfInformationToSend.44A.7.2.2.18Parameter TSPX_asfMaximumNumberOfCounters.44A.7.2.2.19Parameter TSPX_asfNumberOfCalls.45A.7.2.2.20Parameter TSPX_asfStopTime.45A.7.2.2.21Parameter TSPX_asfStartTime.45A.7.2.2.22Parameter TSPX_cgExtensions.46A.7.2.2.23Parameter TSPX_cgDuration.46A.7.2.2.24Parameter TSPX_gapInterval.47A.7.2.2.25Parameter TSPX_gapCriteria.47A.7.2.2.26Parameter TSPX_gapTreatment.48A.7.2.2.27Parameter TSPX_cgServiceKey.48A.7.2.2.28Parameter TSPX_cgInformationToSend.49A.7.2.2.29Parameter TSPX_cgLocationNumber.49A.7.2.2.30Parameter TSPX_cgReleaseCause.50A.7.2.2.31Parameter TSPX_cgControlType.50A.7.2.2.32Parameter TSPX_cgCallingAddressValue.50A.7.2.2.33Parameter TSPX_cirqExtensions.51A.7.2.2.34Parameter TSPX_conCorrelationID.51A.7.2.2.35Parameter TSPX_conDestinationRoutingAddress.52A.7.2.2.36Parameter TSPX_conServiceInteractionIndicators.52A.7.2.2.37Parameter TSPX_conExtensions.53A.7.2.2.38Parameter TSPX_conAlertingPattern.53A.7.2.2.39Parameter TSPX_conCallingPartysCategory.54A.7.2.2.40Parameter TSPX_conCallingPartyNumber.54A.7.2.2.41Parameter TSPX_conOriginalCalledPartyID.54A.7.2.2.42Parameter TSPX_conRedirectingPartyID.55A.7.2.2.43Parameter TSPX_conRedirectionInformation.55A.7.2.2.44Parameter TSPX_conRouteList.55A.7.2.2.45Parameter TSPX_conScfID.56A.7.2.2.46Parameter TSPX_ctrExtensions.56A.7.2.2.47Parameter TSPX_ctrIPRoutingAddress.57A.7.2.2.48Parameter TSPX_ctrResourceAddress.57A.7.2.2.49Parameter TSPX_ctrServiceInteractionIndicators.57A.7.2.2.50Parameter TSPX_etcAssistingSSPIPRoutingAddress.58A.7.2.2.51Parameter TSPX_etcCorrelationID.58A.7.2.2.52Parameter TSPX_etcExtensions.59A.7.2.2.53Parameter TSPX_etcServiceInteractionIndicators.59A.7.2.2.54Parameter TSPX_etcScfID.60A.7.2.2.55Parameter TSPX_FCIBillingChargingCharacteristics.60A.7.2.2.56Parameter TSPX_icaDestinationRoutingAddress.60A.7.2.2.57Parameter TSPX_icaExtensions.61A.7.2.2.58Parameter TSPX_icaAlertingPattern.61A.7.2.2.59Parameter TSPX_icaCallingPartyNumber.62A.7.2.2.60Parameter TSPX_icaServiceInteractionIndicators.62A.7.2.2.61Parameter TSPX_paDate.62A.7.2.2.62Parameter TSPX_paDisplayInformation.63A.7.2.2.63Parameter TSPX_paDuration.63A.7.2.2.64Parameter TSPX_paElementaryMessageID.63A.7.2.2.65Parameter TSPX_paElementaryMessageID_1.64A.7.2.2.66Parameter TSPX_paElementaryMessageID_2.64A.7.2.2.67Parameter TSPX_paElementaryMessageID_3.64A.7.2.2.68Parameter TSPX_paExtensions.65A.7.2.2.69Parameter TSPX_paInformationToSend.65A.7.2.2.70Parameter TSPX_paInteger.66A.7.2.2.71Parameter TSPX_paInterval.66A.7.2.2.72Parameter TSPX_paNumber.66A.7.2.2.73Parameter TSPX_paNumberOfRepetitions.67A.7.2.2.74Parameter TSPX_paPrice.67A.7.2.2.75Parameter TSPX_paText.67A.7.2.2.76Parameter TSPX_paTime.68A.7.2.2.77Parameter TSPX_paToneID.68A.7.2.2.78Parameter TSPX_pcDisplayInformation.68SIST ETS 300 374-4:1998

Page 6ETS 300 374-4: December 1997A.7.2.2.79Parameter TSPX_pcElementaryMessageID.69A.7.2.2.80Parameter TSPX_pcExtensions.69A.7.2.2.81Parameter TSPX_pcFirstDigitTimeOut.70A.7.2.2.82Parameter TSPX_pcInterDigitTimeOut.70A.7.2.2.83Parameter TSPX_pcMaximumDigits.70A.7.2.2.84Parameter TSPX_pcMinimumDigits.71A.7.2.2.85Parameter TSPX_pcToneID.71A.7.2.2.86Parameter TSPX_rncEventTypeCharging.71A.7.2.2.87Parameter TSPX_rrbExtensions.72A.7.2.2.88Parameter TSPX_rrbApplicationTimer.72A.7.2.2.89Parameter TSPX_rtExtensions.73A.7.2.2.90Parameter TSPX_rtTimerValue.73A.7.2.2.91Parameter TSPX_sCIBillingChargingCharacteristics.74A.7.2.2.92Parameter TSPX_sciExtensions.74A.7.2.3Test suite timer values.75A.8Control or observation via the non-INAP interfaces.75A.8.1Mechanism for control via the non-INAP interfaces.76A.8.1.1Detection of assisting request.76A.8.1.2Detection of assisting request_srf.77A.8.1.3Detection of bearer channel disconnect.77A.8.1.4Detection of handoff request.78A.8.1.5Detection of charging event.78A.8.1.6Detection of calling party abandon.79A.8.1.7Detection of calling party disconnect.79A.8.1.8Detection of charging report condition.80A.8.1.9Detection of call release.80A.8.1.10Detection of EDP_N.81A.8.1.11Detection of EDP_R.82A.8.1.12Detection of Originating trigger.83A.8.1.13Detection of release indication.83A.8.1.14Detection of Trigger Detection Point.84A.8.1.15Detection of Terminating trigger.85A.8.2Mechanism of observation via the non-INAP interfaces.86A.8.2.1Observation of SSF returning to idle state.86A.8.2.2Observation of SRF returning to idle state.86Annex B (normative):Protocol Conformance Test Report (PCTR) proforma.87B.1Identification summary.87B.1.1Protocol Conformance Test Report (PCTR).87B.1.2IUT identification.87B.1.3Testing environment.88B.1.4Limits and reservation.88B.1.5Comments.88B.2IUT conformance status.89B.3Static conformance summary.89B.4Dynamic conformance summary.89B.5Static conformance review report.90B.6Test campaign report.90B.7Observations.98SIST ETS 300 374-4:1998

Page 7ETS 300 374-4: December 1997Annex C (normative):Abstract test suite.99C.1The TTCN Graphical form (TTCN.GR).99C.2The TTCN Machine Processable form (TTCN.MP).99History.100SIST ETS 300 374-4:1998

Page 8ETS 300 374-4: December 1997Blank pageSIST ETS 300 374-4:1998

Page 9ETS 300 374-4: December 1997ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocol andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS is part 4 of a multi-part standard covering the Capability Set 1 (CS1) core Intelligent NetworkProtocol (INAP) as described below:Part 1:"Protocol specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 3:"Test Suite Structure and Test Purposes (TSS&TP) specification for Service SwitchingFunction (SSF) and Specialized Resource Function (SRF)";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information forTesting (PIXIT) proforma specification for SSF and SRF";Part 5:"Protocol specification for the Service Control Function (SCF) - Service Data Function (SDF)interface";Part 6:"PICS proforma specification for the SCF-SDF interface".Transposition datesDate of adoption:5 December 1997Date of latest announcement of this ETS (doa):31 March 1998Date of latest publication of new National Standardor endorsement of this ETS (dop/e):30 September 1998Date of withdrawal of any conflicting National Standard (dow):30 September 1998SIST ETS 300 374-4:1998

Page 10ETS 300 374-4: December 1997Blank pageSIST ETS 300 374-4:1998

Page 11ETS 300 374-4: December 19971ScopeThis fourth part of ETS 300 374 provides the Abstract Test Suite (ATS), the Abstract Test Method (ATM),ATS conventions, the partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma andthe Protocol Conformance Testing Report (PCTR) proforma for the Service Switching Function (SSF) andthe Specialized Resource Function (SRF) of the core Intelligent Network Application Protocol (INAP) ofIntelligent Network (IN) Capability Set 1 (CS1) according to ETS 300 374-1 [1].The objective of the ETS is to provide a standardized ATS for SSF and SRF conformance tests which givea reasonable probability of inter-operability between IN components from different manufacturers over thecore INAP interfaces.Annex A provides a partial PIXIT proforma.Annex B includes a PCTR proforma.Annex C provides an ATS for SSF and SRF. The specification of the Test Cases (TCs) in the ATS isbased on the dynamic conformance requirements specified in ETS 300 374-3 [3]. The TCs provide theimplementation of the TPs in TTCN.ISO/IEC 9646, parts 1 to 5 [4 to 8] and ETS 300 406 [9] are used as the basis for the test methodology.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 374-1 (1994): "Intelligent Network (IN); Intelligent Network CapabilitySet 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 1:Protocol specification".[2]ETS 300 374-2 (1996): "Intelligent Network (IN); Intelligent Network CapabilitySet 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 2:Protocol Implementation Conformance Statement (PICS) proformaspecification".[3]ETS 300 374-3 (1997): "Intelligent Network (IN); Intelligent Network CapabilitySet 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 3: TestSuite Structure and Test Purposes (TSS&TP) specification for Service SwitchingFunction (SSF) and Specialized Resource Function (SRF)".[4]ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 1: General concepts".[5]ISO/IEC 9646-2: "Information technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 2: Abstract Test SuiteSpecification".[6]ISO/IEC 9646-3: "Information technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 3: The Tree andTabular Combined Notation (TTCN)".[7]ISO/IEC 9646-4: "Information technology - Open Systems Interconnection -Conformance testing methodology and framework - Part 4: Test realization".[8]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".SIST ETS 300 374-4:1998

Page 12ETS 300 374-4: December 1997[9]ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocoland profile conformance testing specifications; Standardization methodology".[10]ETS 300 287 (1993): "Integrated Services Digital Network (ISDN); SignallingSystem No.7; Transaction Capabilities Application Part (TCAP) version 2".[11]ITU-T Recommendation Q.771 (1993): "Specification of signalling system No.7;Functional description of transaction capabilities".[12]ITU-T Recommendation Q.772 (1993): "Specification of signalling system No.7;Transaction capabilities information element definitions".[13]ITU-T Recommendation Q.773 (1993): "Specification of signalling system No.7;Transaction capabilities formats and encoding".[14]ITU-T Recommendation Q.774 (1993): "Specification of signalling system No.7;Transaction capabilities procedures".[15]ITU-T Recommendation Q.775 (1993): "Specification of signalling system No.7;Guidelines for using transaction capabilities".[16]ISO/IEC 9545 (1989): "Information technology - Open Systems Interconnection -Application layer structure".[17]ETS 300 008: "Integrated Service Digital Network (ISDN); Signalling SystemNo.7; Message Transfer Part (MTP) to support international interconnection".[18]ETS 300 009: "Integrated Service Digital Network (ISDN); Signalling SystemNo.7; Signalling Connection Control Part (SCCP) [connectionless service] tosupport international interconnection".3Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply, together with those given inETS 300 374-1 [1] and ETS 300 374-3 [3]:Abstract Test Case (ATC): Refer to ISO/IEC 9646-1 [4].NOTE:In this ETS, the commonly used term TC is applied in the same way as ATC.Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [4].Client (of a test laboratory): Refer to ISO/IEC 9646-1 [4].dynamic conformance requirements: Refer to ISO/IEC 9646-1 [4].Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [4].IN component: A physical component of the intelligent network which has one of the following form: aSCP, a SSP, an IP or a SDP.INAP interface: An interface of an IN component at which the core INAP applies. An INAP interface iseither a SCF-SSF, or a SCF-SRF, or a SCF-SDF interface.Lower Tester (LT): Refer to ISO/IEC 9646-1 [4].Multi-Party Testing (MPyT) context: Refer to ISO/IEC 9646-1 [4].non-INAP interface: An interface an IN component has, is not the one of the core INAP interfaces.SIST ETS 300 374-4:1998

Page 13ETS 300 374-4: December 1997PCTR proforma: Refer to ISO/IEC 9646-1 [4].PICS proforma: Refer to ISO/IEC 9646-1 [4].PIXIT proforma: Refer to ISO/IEC 9646-1 [4].Point Of Control And Observation (PCO): Refer to ISO/IEC 9646-1 [4].Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [4].Protocol Implementation eXtra Information For Testing (PIXIT): Refer to ISO/IEC 9646-1 [4].remote test method: Refer to ISO/IEC 9646-1 [4].Single-Party Testing (SPyT) context: Refer to ISO/IEC 9646-1 [4].System Under Test (SUT): Refer to ISO/IEC 9646-1 [4].test event: Refer to ISO/IEC 9646-1 [4].test laboratory: Refer to ISO/IEC 9646-1 [4].Test Purpose (TP): Refer to ISO/IEC 9646-1 [4].test system: Refer to ISO/IEC 9646-1 [4].3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:aCSCF Assist with relay handlingaSAssisting SSFASEApplication Service ElementASPAbstract Service PrimitivesATMAbstract Test MethodATCAbstract Test CaseATSAbstract Test SuitebCBasic SCFBIInvalid BehaviourBOInopportune BehaviourbStests for SSP basic functionsBVValid BehaviourCACapability testscDNon-integrated SDFcIIP with direct path to SCPCMCo-ordination MessageCPCo-ordination PointdCSCF-SDF handlingFEFunctional EntityFSMFinite State MachineIEInformation ElementiSInitiating SSFISUPISDN User PartITbasic Interconnection TestsIUTImplementation Under TestLTLower TesterMPyTMulti-Party TestingMTPMessage Transfer PartpCSCF direct path IP handlingPCOPoint of Control and ObservationPCTRProtocol Conformance Test ReportPDUProtocol Data UnitSIST ETS 300 374-4:1998

Page 14ETS 300 374-4: December 1997PICSProtocol Implementation Conformance StatementsPIXITProtocol Implementation eXtra Information for TestingPTSProfile Test SpecificationrCSCF-SSF relay handlingrSSSF relaySAPService Access PointSCCPSignalling Connection Control PartSPyTSingle-Party TestingSS7Signalling System No.7SUTSystem Under TestTCTest CaseTCAPTransaction Capabilities Application PartTPTest PurposeTSSTest Suite StructureTTCNTree and Tabular Combined NotationULUpper LayerUTUpper Tester4Abstract test method and test configurationsThis clause describes the testing architecture, the Abstract Test Method (ATM), the test configurations,different testing context and the Point of Control and Observation (PCO) used in the ATS.For the core INAP conformance testing the remote test method is selected primarily due to its minimalimpact on an Implementation Under Test (IUT). It is not possible in this test method to observe and controlthe upper service boundary of the IUT.4.1SUT and IUTA SUT in this ETS is generally a SSP or an IP which has a core INAP interface to a SCP.Based on the application layer structure of ETS 300 374-1 [1] (see ISO/IEC 9545 [16]), an IUT of the coreINAP is an implementation of an application entity, which is:-either a SSF within a SSP;-or a SSF with an integrated SRF within a SSP;-or a SRF within an IP.An IUT uses the TCAP services to establish, maintain and end application associations. A test casesimulates the behaviours of a SCF to test the IUT.4.2SUT interfacesA SUT is a network component which has one core INAP interface and more then one non-INAPinterfaces. The ATS designed simulates the SCF behaviours at the core INAP interface. However, at thenon-INAP interfaces different protocols such as ISUP, B-ISUP, TUP or DSS1 may be available dependingupon the network configuration. These non-INAP interfaces are used in the ATS as a second or thirdauxiliary interface for testing. Some kind of control or observation function is needed for the execution oftesting via one of these interfaces. However, the ATS is designed to test the core INAP interface. It is notsuitable to be used for an interworking test between the core INAP and the other protocols.4.3Lower Testers (LTs)LTs constitute a major part of a core INAP test system. Depending on the test configuration more thanone LT can be needed in test cases. There is always a main LT in the test system which is in use in alltest cases. It controls and observes the behaviours of the IUT via the core INAP interface. In most testcases a second parallel LT, and in some test cases even a third parallel LT, is needed. The role of theparallel LTs is to provoke at the IUT some core INAP procedures needed for testing or to make somesimple observations via a non-INAP interface.SIST ETS 300 374-4:1998

Page 15ETS 300 374-4: December 19974.4Upper Tester (UT)No explicit UT is needed in a core INAP test system.4.5Underlying SS7 protocolsAlthough ETS 300 374-1 [1] allows either the TCAP or the ROSE/Q.932 to be as underlying protocol forthe core INAP application associations, ETS 300 374-3 [3] and the ATS of the core INAP are designed byusing TCAP as one of the mandatory Association Service Elements (ASEs). It requires that any kind ofSUT implements the ITU-T/ETSI SS7 protocol stack including MTP (see ETS 300 008 [17]),connectionless SCCP (see ETS 300 009 [18]) and TCAP (see ETS 300 287 [10]) as underlying protocols.The ATS is designed in such a way that it accepts the TCAP in both the 1988 (blue book) and 1993 (whitebook) version. No test case has been implemented in TTCN for testing the AC negotiation.4.6TCAP emulation in test systemThe main LT uses the SS7 MTP and connectionless SCCP as underlying protocols in the core INAP testsystem for the signalling transportation and connection control. The test system contains also a TCAPsoftware emulator. Within the core INAP test system, the TCAP ASPs constitute a major part of theinterface between the TCAP emulator and the main LT.4.7Points of Control and Observation (PCOs)A PCO is available for each LT. The PCO models two first-in first-out (FIFO) queues for all test events.The service upper boundary of a TCAP emulator in the test system is defined as the main PCO whichapplies to the main LT at the INAP interface. The main PCO is identical to the TCSAP between the TCcomponent sublayer and a TC user. The address of the main PCO is identical to theoriginating/destination address in the TC primitives by using connectionless SCCP address. Anycombination of SCCP address types is allowed for testing. The test events at the main PCO are specifiedin terms of sending or receiving TC primitives or firing a monitoring timer.A second or third PCO is used for the second or third, parallel LT. Depending upon the protocol used atthe non-INAP interface, they are:-either identical to the MTP SAP at the upper service boundary of the MTP level 3 for the ISUP,B-ISUP or TUP protocol;-or identical to the DSAP at the upper service boundary of the data link Layer (DLL or L2) for theprotocol DSS1.The second or third PCO can be of the same type, e.g. DSAP, but they have different addresses.4.8Co-ordination Points (CPs) and Co-ordination Messages (CMs)Between the main LT and each parallel LT there is a CP. The main LT exchanges CMs with each parallelLT. The main LT uses co-ordination points and co-ordination messages to control and to synchronize theparallel LTs. In this ETS each parallel LT has only one CP available. The semantics of the CPs are similarto PCOs.4.9Test configurationsThe test configuration for testing SSF is different from the test configuration for testing SRF.SIST ETS 300 374-4:1998

Page 16ETS 300 374-4: December 19974.9.1Test configuration for SSF testingFigure 1 shows the test configuration for testing the SSF. The SUT is a SSP which can be:-a SSP alone;-a SSP with an integrated IP;-a SSP with an attached IP;-an initiating SSP;-an assisting SSP.SUTDPOBCSMTBCSMLT1LT2LT3PCO1PCO2PCO3SSFCP12CP13Figure 1: Test configuration for testing SSFIn figure 1, three LTs are used. LT1 is the main LT. LT2 and LT3 are the parallel LTs. PCO1 is a mainPCO at the INAP interface. PCO2 is at a non-INAP interface for the call originating signalling, while PCO3is at the second non-INAP interface for call terminating signalling. LT1 simulates a SCP, while LT2 andLT3 stimulates some network events at the non-INAP interfaces, necessary for the testing. Four types oftesting context are used for testing the SSF:Testing context 1:single LT1;Testing context 2:LT1 and LT2;Testing context 3:LT1 and LT3;Testing context 4:LT1, LT2 and LT3.CP12 is the co-ordination point between LT1 and LT2. CP13 is the co-ordination point between LT1 andLT3.4.9.2Test configuration for SRF testingFigure 2 shows the test configuration for testing the SRF. The SUT is an IP which has an INAP interfaceto the SCP. The SUT can be:-an IP connected directly to a SSP;-an IP connected to a SSP via intermediate exchange.SUTLT5PCO5SRFCP45LT4PCO4Figure 2: Test configuration for testing SRFIn figure 2, two LTs are used. LT4 is the main LT, while LT5 is the parallel LT. LT4 simulates a SCP. LT5simulates a SSP to provoke some events necessary for the testing. PCO4 is the main PCO at the INAPinterface. PCO5 is at a non-INAP interface.SIST ETS 300 374-4:1998

Page 17ETS 300 374-4: December 1997According to the test configuration two types testing context are used in the ATS for testing SRF:Testing context 5:single LT4;Testing context 6:LT4 and LT5.CP45 is the co-ordination point between LT4 and LT5.4.10Single-Party Testing (SPyT)In a Single Party Testing (SPyT) context, only the main PCO exists in the test system. To test SSF, orSRF, a small part of test cases are specified in a SPyT context. The IUT is required by the test purposesto communicate with the main LT (LT1 for the SSF testing, LT4 for the SRF testing). The test casesrunning in the main LT simulate the behaviours of the SCF, as a peer entity of the IUT.4.11Multi-Party Testing (MPyT)In a Multi-Party Testing (MPyT) context two or three PCOs are used. Each PCO is controlled andobserved by one LT. The IUT is required by the test purposes to communicate with LTs. The main LTsimulates the SCF behaviours while the second, parallel LT and/or the third parallel LT simulate(s) theprovocation or observation functions via the non-INAP interface(s), e.g. via an interface at the originatingcall signalling side (OBCSM) or an interface at the terminating call signalling side (TBCSM) of a SSP.The co-ordination of the LTs activities is needed. It is realized in the ATS through the specific co-ordination messages. The main LT requests a parallel LT to provoke a procedure or observe someresults. The parallel LT answers with a result indicating whether a provocation/observation requested bythe main LT has succeeded. The parallel LT does not assign any test verdict. A verdict is always assignedby the main LT. The MPyT context implies to use the concurrent TTCN in the design of the ATS. Thedesign follows two facts in the SSF and SRF testing:-no concurrent requirement on LTs:There is no real concurrence between the main LT and the parallel LTs. If two parallel LTs appearin a same test case, no co-ordination is needed between them.-the parallel LTs do not assign any prerequisite verdict:Only the main LT assigns the verdict in each test case.4.12Abstract test methodThe remote test method is used in the core INAP ATS. According to the test purposes, six different typesof test context exist in the ATS. Contexts 1 to 4 apply to SSF testing, while contexts 5 and 6 are used forSRF testing.4.12.1Remote test method in SPyT context 1SUTLT1TCAPSCCPMTP 1-3PCO1IUTFigure 3: Remote test method in SPyT context 1Figure 3 shows the remote test method in the SPyT context 1. PCO1 is at the core INAP interface of thetest system. A small part of the test cases for testing the SSF are designed under this test context.SIST ETS 300 374-4:1998

Page 18ETS 300 374-4: December 19974.12.2Remote test method in MPyT context 2 and context 3Figure 4 shows a remote test method in the MPyT context 2 and context 3. These two types of the testcontext are used in most test cases for testing the SSF. A main LT, LT1, and a parallel LT, LT2 incontext 2 or LT3 in context 3 are used in the test configuration. In figure 4:-the protocol Ln or Lm is either NWK (L3) of DSS1, or one of ISUP, B-ISUP or TUP of SS7;-the protocol Ln-1 or Lm-1 is either DLL (L2) of DSS1, or MTP level 3 of SS7;-the protocol Ln-2 or Lm-2 is either PHL (L1) of DSS1, or MTP level 1-2 of SS7.The protocol stacks (Ln, Ln-1, Ln-2) and (Lm, Lm-1, Lm-2) can be of different type.IUTSUTLT1TCAPSCCPMTP 1-3PCO1LT3PCO3coordinationLmm-1Lm-2LCP13CP12IUTSUTLT1TCAPSCCPMTP 1-3PCO1LT2PCO2n-2Ln-1LLncoordinationFigure 4: Remote test method in MPyT context 2 and 34.12.3Remote test method in MPyT context 4PCO3coordinationLT3m
...