SIST EN 301 140-4-1:2001

• Abstract:

  ATS & Partial PIXIT proforma for DE/SPS-03038-1 & 2 & 3

• Status: Published
• Publication Date: 31-Aug-2001
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Sep-2001
• Due Date: 01-Sep-2001
• Completion Date: 01-Sep-2001
• Mandate: BC-T-338
• Ref Project: ETSI EN 301 140-4-1 V1.1.3 (2000-05) - Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 4: Abstract Test Suite (ATS) specification and Partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for Service Switching Function (SSF); Sub-part 1: Basic capability set of CS-1 including CS-2 complements

SIST EN 301 140-4-1:2001 is an ETSI European Standard published by SIST for Intelligent Network (IN) and Intelligent Network Application Protocol (INAP) Capability Set 2 (CS2). It specifies the Abstract Test Suite (ATS) specification and the Partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the Service Switching Function (SSF), for the basic capability set of CS-1 including CS-2 complements. Engineers and test laboratories use it to build and run conformance tests for SSF-related INAP implementations and to complete the associated PIXIT and PCTR forms.

What does SIST EN 301 140-4-1:2001 specify?

SIST EN 301 140-4-1:2001 defines the ATS for testing the Service Switching Function (SSF) and the Specialized Resource Function (SRF) of core INAP according to EN 301 140-1. In this part, the CS2 material that deals with CS-1 functions is covered.

The document is organized around the test specification and the accompanying proformas:

• Clause 4 describes the test architecture.
• Clause 5 sets ATS conventions.
• Clause 6 gives implementation conventions.
• Clause 7 explains ATS generalities.
• Annex A contains the ATS in TTCN form.
• Annex B contains the Partial PIXIT proforma.
• Annex C contains the PCTR proforma.

Annex	What it covers
Annex A	ATS for CS1 INAP, including TTCN.GR and TTCN.MP representations
Annex B	Partial PIXIT proforma for the INAP CS1 layer
Annex C	Protocol Conformance Test Report (PCTR) proforma for the CORE INAP CS1 protocol layer

What are the key requirements of SIST EN 301 140-4-1:2001?

SIST EN 301 140-4-1:2001 uses the embedded variant of the remote test method in a multi-party testing context. This matters because the IUT is not directly driven like a simple single-point test, so the test setup must coordinate several test roles and observation points.

Clause 4 defines a multi-party, single-layer architecture with one IUT and several Lower Testers (LTs). For SSF-SCF testing, LT1 acts as the main tester, LT2 is used when SRF-INAP is required, and LT3 handles end-user actions and observations. In practice, this tells the test designer how to split protocol control and signaling behavior across components.

Clause 4 also defines the Points of Control and Observation (PCOs). PCO_1 and PCO_2 carry core INAP traffic, while PCO_3_1 and PCO_3_2 represent the signaling-control interfaces. This matters because conformance tests have to observe both INAP behavior and the related signaling behavior.

The ATS uses TCAP primitives at the core INAP interfaces. The document lists dialogue-handling and component-handling primitives, and it maps the generic signaling interface at PCO_3_1 and PCO_3_2 to real protocols such as ISUP and DSS1. This means the same ATS can be used with different exchange configurations while keeping the INAP checks consistent.

Clause 5 sets naming and coding rules for the ATS content. It specifies how test suite types, operations, parameters, variables, timers, and ASPs are named, and it uses By Reference ASN.1 definitions and constants. For users, this keeps the TTCN suite aligned with the protocol specification and easier to maintain.

Clause 6 states that the test system is assumed to provide fully functional underlying TCAP and MTP-3/ISDN support. Clause 6.1 also gives a one-to-one mapping between TC and TP identifiers. In practice, implementers need to make sure the lower layers are available before using the ATS.

Clause 7 explains that the ATS was produced with SDL, ASN.1, and TTCN methods, and that test cases were generated from the protocol model and test purposes. It also notes that all test cases are selected by default for the test campaign. This helps readers understand that the suite is model-based and intended for broad conformance checking.

What terms does SIST EN 301 140-4-1:2001 define?

• Abstract Test Suite (ATS) - the structured set of TTCN test cases used to assess protocol conformance.
• Partial Protocol Implementation eXtra Information for Testing (PIXIT) - implementation-specific information needed to run the tests correctly.
• Protocol Conformance Test Report (PCTR) - the report form used to record conformance assessment results.
• Service Switching Function (SSF) - the network function under test in the SSF-related configurations.
• Service Control Function (SCF) - the function that interacts with SSF over core INAP in the test architecture.
• Specialized Resource Function (SRF) - the resource function included in the test configurations when required.
• Point of Control and Observation (PCO) - the interface where the test system controls and observes protocol behavior.

Who uses SIST EN 301 140-4-1:2001?

Test laboratories use SIST EN 301 140-4-1:2001 to prepare ATS-based conformance testing, fill in PIXIT data, and complete PCTR reporting. Test managers and clients use the PIXIT and PCTR proformas to document the test environment, the implementation under test, and the results.

Protocol engineers and exchange implementers use it when validating SSF, SCF, SRF, Local Exchange (LE), or Transit Exchange (TE) behavior against INAP CS2. It is also relevant to teams that coordinate signaling behavior with INAP testing across DSS1, ISUP, or related lower-layer protocols.

Which standards are used with SIST EN 301 140-4-1:2001?

SIST EN 301 140-4-1:2001 relies on EN 301 140-1 for the CS2 protocol specification and on EN 301 140-2 for the PICS proforma. It also references ETS 300 374-1 for CS1 core INAP and ITU-T Recommendation Q.771 for TCAP functional description.

For testing methodology, it uses ISO/IEC 9646-1, 9646-2, 9646-3, 9646-5, and 9646-6, plus ETS 300 406. ITU-T Recommendation Q.1224 is named for the Distributed Functional Plane for IN Capability Set 2.

What does the SIST EN 301 140-4-1:2001 document contain?

The document contains a TTCN-based ATS in both graphical and machine-processable forms, plus the supporting test architecture and naming conventions. Annex A points to the TTCN.GR and TTCN.MP representations that accompany the standard.

Annex B provides a PIXIT proforma with sections for identification, ATS summary, test laboratory details, client identification, SUT details, protocol-layer information, implicit send events, core INAP parameter values, and TCAP parameter values. Annex C provides a PCTR proforma with identification, IUT status, static and dynamic conformance summaries, a test campaign report, and observations.

The body of the standard also includes figures for multi-party test configurations, interface models, and test coordination, as well as tables for TCAP primitives and signaling-interface mapping. These parts tell the user how the ATS is structured and how test behavior is coordinated in practice.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 4: Abstract Test Suite (ATS) specification and Partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for Service Switching Function (SSF); Sub-part 1: Basic capability set of CS-1 including CS-2 complements33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 140-4-1 Version 1.1.3SIST EN 301 140-4-1:2001en01-september-2001SIST EN 301 140-4-1:2001SLOVENSKI
STANDARD
ETSIEN301140-4-1V1.1.3(2000-05)EuropeanStandard(Telecommunicationsseries)IntelligentNetwork(IN);IntelligentNetworkApplicationProtocol(INAP);CapabilitySet2(CS2);Part4:AbstractTestSuite(ATS)specificationandPartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaforServiceSwitchingFunction(SSF);Sub-part1:BasiccapabilitysetofCS-1includingCS-2complementsSIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)2ReferenceDEN/SPS-03038-4-1KeywordsIN,CS1,CS2,INAP,ATS,PIXIT,SSFETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:[phone]Fax:[phone]SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)3ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitionsandabbreviations.73.1Definitions.73.2Abbreviations.73.3ISO9646abbreviations.83.4ISO9646definitions.84Testarchitecture.84.1AbstractTestMethod(ATM).84.2Overallconfiguration.84.3TestofSSF-SCFinterfaceusingINAP.94.4TestofSCF-SCFinterfaceusingINAP.104.5Pointsofcontrolandobservation(PCOs).104.6Testsystem.104.7Functionalconfigurations.114.7.1SSF-SCFinterface.114.7.2SCF-SCFinterface.124.7.3Referencetoproductimplementation.124.8Protocolprimitives.134.8.1ProtocolprimitivesatPCO_1andPCO_2.134.8.2ProtocolprimitivesatPCO_3_1andPCO_3_2.145ATSconventions.145.1Namingconventions.145.1.1Declarationspart.145.1.1.1TestsuitetypeandstructuredtypedefinitionsByReference.145.1.1.2Testsuiteoperationsdefinitions.155.1.1.3Testsuiteparameterdeclarations.155.1.1.4Testcaseselectionexpressiondefinitions.155.1.1.5TestsuiteconstantdeclarationsByReference.155.1.1.6Testsuitevariabledeclarations.155.1.1.7Testcasevariabledeclarations.155.1.1.8Timerdeclarations.155.1.1.9ASPtypedefinitions.165.1.1.10Aliasdefinitions.165.1.2Constraintspart.165.1.3Dynamicpart.165.1.3.1Testcaseidentifier.175.1.3.2Teststepidentifier.175.1.3.3Preambleidentifier.175.1.3.4Postambleidentifier.175.1.3.5Defaultidentifier.176Implementationconventions.186.1TCandTPmapping.187ATSgeneralities.187.1ATSdesign.187.1.1Methodology.187.2TestConfiguration.197.2.1Example.217.3ATSrestrictions.21SIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)4AnnexA(normative):ATSforCS1INAP(subsetoftheINAPCS2).22A.1TheTTCNGraphicalform(TTCN.GR).22A.2TheTTCNMachineProcessableform(TTCN.MP).22AnnexB(normative):PartialPIXITproformaforINAPCS1layer.23B.1Identificationsummary.23B.2ATSsummary.23B.3Testlaboratory.23B.4Clientidentification.23B.5SUT.24B.6Protocollayerinformation.24B.6.1Protocolidentification.24B.6.2IUTinformation.24B.6.2.1Implicitsendevents.24B.6.2.2CoreINAPParametervalues.25B.6.2.3TCAPParametervalues.26AnnexC(normative):ProtocolConformanceTestReport(PCTR)proformaforCOREINAPCS1protocollayer.27C.1Identificationsummary.27C.1.1Protocolconformancetestreport.27C.1.2IUTidentification.27C.1.3Testingenvironment.27C.1.4Limitsandreservation.28C.1.5Comments.28C.2IUTconformancestatus.28C.3Staticconformancesummary.28C.4Dynamicconformancesummary.29C.5Staticconformancereviewreport.29C.6Testcampaignreport.30C.7Observations.32History.33SIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)5IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinSR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinSR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).Thepresentdocumentispart4,sub-part1ofamulti-partENcoveringtheIntelligentNetworkApplicationProtocol(INAP)capabilityset2,asidentifiedbelow:Part1:"Protocolspecification";Part2:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part3:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforServiceSwitchingFunction(SSF)";Part4:"AbstractTestSuite(ATS)specificationandPartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaforServiceSwitchingFunction(SSF)";Sub-part1:"BasiccapabilitysetofCS-1includingCS-2complements";Sub-part2:"CallPartyHandling(CPH)";Sub-part3:"SpecializedResourceFunctions(SRF)";Part5:"DistributedFunctionalPlane(DFP)[ITU-TRecommendationQ.1224(1997),modified]".NationaltranspositiondatesDateofadoptionofthisEN:28April2000DateoflatestannouncementofthisEN(doa):31July2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31January2001DateofwithdrawalofanyconflictingNationalStandard(dow):31January2001SIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)61ScopeThepresentdocumentprovidestheAbstractTestSuite(ATS)fortestingoftheServiceSwitchingFunction(SSF)andtheSpecializedResourceFunction(SRF)ofthecoreIntelligentNetworkApplicationProtocol(INAP)accordingtoEN301140-1[1].Inthisspecificpart4-1,thepartofCapabilitySet2(CS2)dealingwithCS1functionsiscovered.AnnexAprovidestheTreeandTabularCombinedNotation(TTCN).AnnexBprovidesthePartialProtocolImplementationeXtraInformationforTesting(PIXIT)Proforma.AnnexCprovidestheProtocolConformanceTestReport(PCTR)Proforma.TheISOstandardforthemethodologyofconformancetesting,ISO/IEC9646-1[4],ISO/IEC9646-2[5],ISO/IEC9646-3[6]andISO/IEC9646-5[7],aswellastheETSIrulesforconformancetesting,ETS300406[9]areusedasabasisforthetestmethodology.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN301140-1(V1.3):"IntelligentNetwork(IN);IntelligentNetworkApplicationProtocol(INAP);CapabilitySet2(CS2);Part1:Protocolspecification".[2]ETSIETS300374-1:"IntelligentNetwork(IN);IntelligentNetworkCapabilitySet1(CS1);CoreIntelligentNetworkApplicationProtocol(INAP);Part1:Protocolspecification".[3]ITU-TRecommendationQ.771:"Functionaldescriptionoftransactioncapabilities".[4]ISO/IEC9646-1:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:GeneralConcepts".(SeealsoCCITTRecommendationX.290).[5]ISO/IEC9646-2:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:AbstractTestSuiteSpecification".(SeealsoCCITTRecommendationX.291(1991)).[6]ISO/IEC9646-3:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part3:TheTreeandTabularCombinedNotation(TTCN)".(SeealsoCCITTRecommendationX.292(1992)).[7]ISO/IEC9646-5:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part5:Requirementsontestlaboratoriesandclientsfortheconformanceassessmentprocess".(SeealsoCCITTRecommendationX.292(1992)).[8]ISO/IEC9646-6:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part6:Protocolprofiletestspecification".[9]ETSIETS300406:"MethodsforTestingandSpecification(MTS);Protocolandprofileconformancetestingspecifications;Standardizationmethodology".SIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)7[10]ITU-TRecommendationQ.1224(1997):"DistributedfunctionalplaneforintelligentnetworkCapabilitySet2".[11]ETSIEN301140-2:"IntelligentNetwork(IN);IntelligentNetworkApplicationProtocol(INAP);CapabilitySet2(CS2);Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thetermsanddefinitionsgiveninEN301140-1[1]apply.3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:BIInvalidBehaviourtestsBOInopportuneBehaviourtestsBVValidBehaviourtestsCACapabilitytestsCPCo-ordinationPointCSCapabilitySetINIntelligentNetworkINAPIntelligentNetworkApplicationProtocolIUTImplementationUnderTestMSCMessageSequenceChartMTCMasterTestComponentPDUProtocolDataUnitPTCParallelTestComponentSCFServiceControlFunctionSCPServiceControlPointSDLSystemDescriptionLanguageSRFSpecializedResourceFunctionSSFServiceSwitchingFunctionSSPServiceSwitchingPointSUTSystemUnderTestTCAPTransactionCapabilitiesApplicationPartTDPTriggerDetectionPointSIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)83.3ISO9646abbreviationsForthepurposesofthepresentdocumentthefollowingISO/IEC9646-1[4]abbreviationsapply:ASPAbstractServicePrimitiveATMAbstractTestMethodATSAbstractTestSuiteICSImplementationConformanceStatementIUTImplementationUnderTestIXITImplementationeXtraInformationforTestingLTLowerTesterNWKNetworkLayerPCOPointofControlandObservationPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementPIXITProtocolImplementationeXtraInformationforTestingSAPServiceAccessPointSPyTSinglePartyTestingSUTSystemUnderTestTCTestCaseTPTestPurposeTSSTestSuiteStructureTTCNTreeandTabularCombinedNotationUTUpperTester3.4ISO9646definitionsForthepurposesofthepresentdocumentthefollowingISO/IEC9646-3[6]definitionsapply:TTCN.GRTTCN.MPForthepurposesofthepresentdocumentthefollowingISO/IEC9646-5[7]definitionsapply:ProtocolConformanceTestReport(PCTR)PCTRproforma4Testarchitecture4.1AbstractTestMethod(ATM)ThisclausedescribestheATMusedfortestingtheINAPprotocol.ItistheembeddedvariantoftheremotetestmethodusedinMultyPartyTesting(MPyT)context,asdefinedinISO/IEC9646-2[5].Thistestmethodhasbeenselected,because:-thistestmethodimpliesnospecificrequirementsfromtheImplementationUnderTest(IUT);-theupperServiceAccessPoint(SAP)oftheIUTcannotbedirectlyobserved;-thistestmethodplacesminimumlimitationsintherealizationofconformancetesting.4.2OverallconfigurationFigure1describesthetestarchitecturewhichwillbeusedforthedefinitionoftheATS.Asingletestarchitecturecoversalltestingconfigurationrequirements.SIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)9Figure1:Multi-party,single-layertestingcontext:oneIUTand4typesofLTsFigure1showsthemulti-party,singlelayertestingcontext.Thesamearchitecturecanbeusedfortestingseveralinterfaces.TherolesofIUTandLTschangeaccordingtotheprotocoltobetestedintheIUT.Table1givesthenatureoftheIUTandLTsaccordingtotheprotocolundertest.Table1:possibletestingconfigurationsTestConfigTestedInterfaceIUTLT1LT2LT3_1LT3_2FunctionalConfiguration1SSF-SCFSSFSCFSRFSigconASigconBA2SSF-SCFSSFSCF-SigconASigconBB3SCF-SCFSCFSSFSCFSigconASigconBC4.3TestofSSF-SCFinterfaceusingINAPThetestprogramcontainstheprogramofthemainLT1maintesteraswellastheco-ordinationpointstoco-ordinatethetaskswiththeothertestersLT2andLT3.IUT:istheSSF-INAP.LT1:testprogramistheSCF.LT2:testprogramistheSRF-INAPwhenrequired.LT3:informaltestprogramforactionsandobservationatthesignallingcontrolpoints,toplaytheroleofendusersA,BandCforinstance.ThereareasmanyLT3asrequiredbythetestconfiguration(LT3_1,LT3_2,.)accordingtothenumberofendusersA,BandCinvolvedinaservicescenarioforinstance,usingdifferenttypesofprotocols).Pm:containstheprotocolsusedbelowtheINAPbetweenSCPandSSP,alsobetweenSSPandSRF.Theycouldbee.g.TCAP,SCCPandMTPofSS7etc.Pn:containstheprotocolsusedbelowtheLT3_1betweentheIUTandtheSignallingcontrolpoint.ItcouldbetheDSS1protocolsorISUPSS7protocol(inthecaseofhavingatransitexchange).SIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)10Pz:containstheusedprotocolsbelowtheLT3_2betweentheIUTandtheSignallingcontrolpoint.ItcouldbetheDSS1protocolsorISUPSS7protocol(inthecaseofhavingatransitexchange).4.4TestofSCF-SCFinterfaceusingINAPThetestprogramcontainstheprogramofthemainLT1maintesteraswellastheco-ordinationpointstoco-ordinatethetaskswiththeothertestersLT2andLT3.IUT:istheSCF-INAPundertest.LT1:testprogramistheSSF.LT2:testprogramistheSecondSCF.LT3:informaltestprogramforactionsandobservationatthesignallingcontrolpoints,toplaytheroleofendusersA,BandCforinstance.ThereareasmanyLT3asrequiredbythetestconfiguration(LT3_1,LT3_2,.)accordingtothenumberofendusersA,BandCinvolvedinaservicescenarioforinstance,usingdifferenttypesofprotocols).Pm:containstheprotocolsusedbelowtheINAPbetweenSCPandSSP,alsobetweenSSPandSRF.Theycouldbee.g.TCAP,SCCPandMTPofSS7etc.Pn:containstheprotocolsusedbelowtheLT3_1betweentheIUTandtheSignallingcontrolpoint.ItcouldbetheDSS1protocolsorISUPSS7protocol(inthecaseofhavingatransitexchange).Pz:containstheusedprotocolsbelowtheLT3_2betweentheIUTandtheSignallingcontrolpoint.ItcouldbetheDSS1protocolsorISUPSS7protocol(inthecaseofhavingatransitexchange).4.5Pointsofcontrolandobservation(PCOs)PCO-Declarations.PCO_1:ThisPCOisatthecoreINAPinterfacebetweenSSPandSCP.ThelowerlayerprotocolisPm.Itcouldbee.g.TCAP.PCO_2:ThisPCOisatthecoreINAPinterfacebetweenSSPandSRF.ThelowerlayerprotocolisPm.Itcouldbee.g.TCAP,ISUP,B-ISUP,TUPortheNWKofDSS1.PCO_3_1:ThisPCOisattheinterfacebetweenSSPandSignallingControlA.ThelowerlayerprotocolisPn.Itcouldbee.g.ISUP,B-ISUP,TUPortheNWKofDSS1.PCO_3_2:ThisPCOisattheinterfacebetweenSSPandSignallingControlB.ThelowerlayerprotocolisPz.Itcouldbee.g.ISUP,B-ISUP,TUPortheNWKofDSS1.4.6TestsystemItisexpectedthatthetestsystemsupportstheprotocolsPm,Pm-1,Pm-2andtheprotocolsforPnandPz.ItisexpectedthatthetestsystemsupportsthePCORequirementsofPCO_1,PCO_2,PCO_3_1andPCO_3_n.SIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)114.7Functionalconfigurations4.7.1SSF-SCFinterfaceSCPSSPIPNon-integratedSRFSCFSSFCCFSRFSDFFigure2:SCPwithsingleSSPConfigurationA:IUT=SSF(nonintegratedwithSRF)SCPSSPIntegratedSRFSCFSSFCCFSRFSDFFigure3:SCPwithsingleSSPConfigurationB:IUT=SSF(integratedwithSRF)SIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)124.7.2SCF-SCFinterfaceSCPSSPIntegratedSRFSCFSSFCCFSRFSDFFigure4:SCPtoSCPConfigurationC:IUT=SCFFigure5:VoidFigure6:Void4.7.3ReferencetoproductimplementationTheSUTcaneitherbeaLocalExchange(LE)oraTransitExchange(TE).Theexactnumberoftesters(LT3aloneorLT3_1andLT3_2)willdependuponthetypeofexchangeandtheconfigurationoftheexchange,asexplainedbythefollowingexamplesofimplementation.Figure7:ConfigurationwithLocalExchangeasSUTFigure7showsaconfigurationwheretheSUTisaLocalExchange.Inthiscase,signallingofacallmaybedoneeitherwithDSS1andISUP(AandBinvolved)oronlywithDSS1(AandCinvolved).SIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)13Figure8:ConfigurationwithTransitExchangeasSUTFigure8showsaconfigurationwheretheSUTisaTransitExchange.Inthiscase,signallingusesISUPprotocolonly.4.8Protocolprimitives4.8.1ProtocolprimitivesatPCO_1andPCO_2ThetransmissionofINAPmessagesattheinterfacebetweenSCFandSSForSSFandSRFusesTCAPprimitives.TheLT1,LT2communicatewiththelowerprotocolsviatheSAPswiththeTCAP-primitivesshownintables2and3accordingtoclause10ofETS300374-1[2]andITU-TRecommendationQ.771[3].Table2PrimitivesfordialoguehandlingAbstractServicePrimitiveTypeTC_BEGINRequestorIndicationTC_CONTINUERequestorIndicationTC_ENDRequestorIndicationTC_U_ABORTaRequestorIndicationTC_U_ABORTbRequestorIndicationTC_P_ABORTaIndicationTC_P_ABORTbIndicationTC-NOTICEIndicationTable3PrimitivesforcomponentshandlingAbstractServicePrimitiveTypeTC_INVOKERequestorIndicationTC_U_ERRORRequestorIndicationTC_U_REJECTRequestorIndicationTC_L_REJECTIndicationTC_R_REJECTIndicationTC_U_CANCELRequestorIndicationTCAPisincludedintheSDLmodelofCS2INAP.SIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)144.8.2ProtocolprimitivesatPCO_3_1andPCO_3_2Inordertobeprotocolindependent,asetofprimitivesisdefinedatthisinterface,andthenexttableisanexampleofthemappingbetweenthisgenericinterfaceandthepossiblesignallingprotocolslikeISUPandDSS1.Herefollowsthelistoftheseprimitivesforthegenericinterfaceandatablegivingthemappingofthegenericprimitivesintorealprotocols.Table4MappingtablefortheinterfacebetweenSSPandsignallingcontrolpointPCO_3-1or3-2interfaceprimitivesTypeifISUPusedifDSS1usedifotherprotocolsusedSetupIndicationRequestResponseConfirmIAMANMSetupAnswer?ReleaseRequestIndicationREL/RLCDisconnect?SubsequentAddressRequestIndicationSAMInformation?AddressEndRequestIndicationSAMInformation?CallProgressRequestIndicationACM,CPGProgress,Alerting?ServiceFeatureRequestIndication?Facility??NetworkSuspendRequestIndicationSUSPEND--?NetworkResumeRequestIndicationRESUME--?5ATSconventionsThisclausedescribestheconventionsappliedtodefinetheATSandgivesthenamingconventionschosenforthedifferentelementsoftheATS.TheATSconventionsareintendedtogiveabetterunderstandingoftheATSbuttheydescribealsotheconventionsmadeforthedevelopmentoftheATS,thusforanylatermaintenancepurposesorfurtherdevelopmentoftheATS,theconventionsdescribedinthisclauseshallbeconsidered.5.1Namingconventions5.1.1DeclarationspartThissubclausedescribesthenamingconventionschosenfortheelementsoftheATSdeclarationspart.5.1.1.1TestsuitetypeandstructuredtypedefinitionsByReferenceInordertoavoidmisalignmentproblemswiththestandard,allthetypesusedinthisATShavebeendefinedbyreference.ThesameASN.1filescontainingthestandardtypedefinitionshavebeenusedasmodulescontainingthereferencedtypedefinitions.EXAMPLE:TypeNameTypeReferenceModuleIdentifierCallResultCallResultINCS2datatypesWhereanabbreviationisincludedinthedeclarationname,thereisanunderscore("_")beforeand/orafterit,separatingitfromtherestoftheidentifier.Thisrulewithabbreviationsappliestoallthenamingconventionsinthewholetestsuite.SIST EN 301 140-4-1:2001

ETSIETSIEN301140-4-1V1.1.3(2000-05)155.1.1.2TestsuiteoperationsdefinitionsThetestsuiteoperationidentifiersarecomposedofstringsinuppercaselettersstartingwiththeuppercasestring"TSO_".Thedifferentstringsinthedefinitionareseparatedwithunderscores.5.1.1.3TestsuiteparameterdeclarationsThetestsuiteparameteridentifiersarecomposedofstringsinuppercaselettersstartingbytheuppercasestring"PIC_"or"PIX_"andseparatedbyunderscores.IfthetestsuiteparameterreferencesaPICSitem,theprefix"PIC_"isused.IfthetestsuiteparameterreferencesaPIXITitem,theprefix"PIX_"isused.EXAMPLE:PIX_CalledPartyNumber1Completenamesasdefinedinthespecificationsareused.5.1.1.4TestcaseselectionexpressiondefinitionsThenamingcon
...