SIST EN 301 140-3-1:2001

Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for Service Switching Function (SSF); Sub-part 1: Basic capability set of CS-1 including CS-2 complements

TSS&TP for DE/SPS-03038-1 & 2

Inteligentno omrežje (IN) - Aplikacijski del inteligentnega omrežja (INAP) - Nabor zmožnosti 2 (CS2) - 3. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) - Specifikacija za funkcijo preklapljanja storitev (SSF) - 1. podpoglavje: Osnovni nabor zmožnosti CS-1, vključno s komponentami CS-2

General Information

• 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-3-1 V1.1.3 (2000-05) - Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for Service Switching Function (SSF); Sub-part 1: Basic capability set of CS-1 including CS-2 complements

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.UHVNXãDQMDIntelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification 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-3-1 Version 1.1.3SIST EN 301 140-3-1:2001en01-september-2001SIST EN 301 140-3-1:2001SLOVENSKI
STANDARD



SIST EN 301 140-3-1:2001



ETSIEN301140-3-1V1.1.3(2000-05)EuropeanStandard(Telecommunicationsseries)IntelligentNetwork(IN);IntelligentNetworkApplicationProtocol(INAP);CapabilitySet2(CS2);Part3:TestSuiteStructureandTestPurposes(TSS&TP)specificationforServiceSwitchingFunction(SSF);Sub-part1:BasiccapabilitysetofCS-1includingCS-2complementsSIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)2ReferenceDEN/SPS-03038-3-1KeywordsCS1,CS2,IN,INAP,TSS&TP,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-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)3ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitionsandabbreviations.63.1Definitions.63.2Abbreviations.74TestPurposegeneralities.74.1Introduction.74.2Groupingoftestpurposesperelementaryprocedures.74.3Sourceoftestpurposedefinitions.84.4MethodusedfordevelopingTPs.84.4.1UseofMSCsgeneratedbytheSDLmodelofCoreINAPCS-2.84.4.2TCAPadapterprimitives.84.4.3GenerationofcorrespondingTestCases.84.5MethodusedforTPdescription.94.5.1TextandMSCs.94.5.2Testcategories.94.5.3Testpurposenamingconvention.104.5.4Preamblesandtheirnamingconventions.104.5.5HowtointerprettheparametersandtheirvaluesasusedintheMSCs.115Functionalconfigurationsundertest.125.1SSFbasicfunctions.125.2SSFadditionalfunctions.136TSSandTPsforCS-1andCS-2basiccapabilities.146.1Preamblesandpostamblesused.146.1.1ListofpreamblesandpostamblesforCS1.146.1.2Preambledescriptions.156.1.2.1O_OSpreamble.156.1.2.2O_S2Ppreamble.166.1.2.3T_OSpreamble.176.1.2.4T_S2Ppreamble.186.1.3Postambledescriptions.196.1.3.1SigConA_Releasepostamble.196.1.3.2SigConA_Release_thenBpostamble.196.1.3.3ReleaseCallApostamble.206.1.3.4ReleaseICApostamble.206.1.3.5ReleaseCallAB_cause_00postamble.216.1.3.6ReleaseCallAB_cause_0Fpostamble.226.1.3.7SigConB_Releasepostamble.236.1.3.8SigConB_Release_cause_0Dpostamble.236.1.3.9SigConA_Release_thenB_cause10postamble.246.1.3.10ReleaseCallBpostamble.256.1.3.11ReleaseCallA2postamble.266.2Basicprocedures.266.2.1Listofprocedures.266.2.2Definitionsoftheprocedures.276.3Structureofthetestsuite(TSS)forthebasiccapabilities.286.4TestPurposes(TP)description.306.4.1ServiceFilteringprocedure.306.4.2ActivityTestprocedure.406.4.3ApplyChargingprocedure.44SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)46.4.4CallGapprocedure.576.4.5CallInformationprocedure.816.4.6Cancelprocedure.966.4.7CollectInformationprocedure.1066.4.8Connectprocedure.1116.4.9Continueprocedure.1266.4.10FurnishChargingInformationprocedure.1296.4.11InitialDPprocedure.1336.4.12InitiateCallAttemptprocedure.1426.4.13ReleaseCallprocedure.1526.4.14RequestReportBCSMEventprocedure.1576.4.15SendChargingInformationprocedure.2226.4.16RequestNotificationChargingEventprocedure.223AnnexA(informative):Descriptionofvariousfunctionalconfigurations.230AnnexB(normative):ParametervaluesusedinMSCsforCOREINAPprimitives.247AnnexC(normative):ParametervaluesusedinMSCsforTCAPprimitives.249Bibliography.250History.251SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-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).Thepresentdocumentispart3,sub-part1ofamulti-partENcoveringtheIntelligentNetwork(IN);IntelligentNetworkApplicationProtocol(INAP);CapabilitySet2(CS2),asidentifiedbelow:Part1:"Protocolspecification";Part2:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part3:"TestSuiteStructureandTestPurposes(TSS&TP)specificationforServiceSwitchingFunction(SSF)";Sub-part1:"BasiccapabilitysetofCS-1includingCS-2complements";Sub-part2:"CallPartyHandling(CPH)";Sub-part3:"SpecializedResourceFunctions(SRF)";Part4:"AbstractTestSuite(ATS)specificationandPartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaforServiceSwitchingFunction(SSF)";Part5:"DistributedFunctionalPlane(DFP)[ITU-TRecommendationQ.1224(1997),modified]".NationaltranspositiondatesDateofadoptionofthisEN:28April2000DateoflatestannouncementofthisEN(doa):31July2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31January2001DateofwithdrawalofanyconflictingNationalStandard(dow):31January2001SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)61ScopeThepresentdocumentprovidestheTestSuiteStructureandTestPurposes(TSS&TP)fortestingoftheServiceSwitchingFunction(SSF)andtheSpecializedResourceFunction(SRF)oftheIntelligentNetworkApplicationProtocol(INAP)ofIntelligentNetwork(IN)CapabilitySet2(CS2)accordingtoEN301140-1[1].Thepresentdocumentrelatestothebasiccapabilityset,whichcoverstheCS-1operations,plustheCS-2additionsrelatedtotheseoperations,mainlyduetothetestoftheCS-2additionalparametersorfunctionalities.ThepresentdocumentiscompletedbyotherpartsconstitutingtheCS-2CoreINAPspecifications.InthepresentversionoftheTPdescriptionincludedintables,referencestospecificationrequirementsandreferencestoPICSinthe"conditionforselection"arenotincluded,excepttomentionwhenitisaCS-2addition.ISO/IEC9646-1[3]andISO/IEC9646-2[4]areusedasthebasisforthetestmethodology.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]ETSIEN301140-4(V1.1):"IntelligentNetwork(IN);IntelligentNetworkApplicationProtocol(INAP);CapabilitySet2(CS2);Part4:AbstractTestSuite(ATS)specificationandPartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaforServiceSwitchingFunction(SSF)".[3]ISO/IEC9646-1:"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[4]ISO/IEC9646-2:"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part2:Abstracttestsuitespecification".[5]ETSIETS300374-1:"IntelligentNetwork(IN);IntelligentNetworkCapabilitySet1(CS1);CoreIntelligentNetworkApplicationProtocol(INAP);Part1:Protocolspecification".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:-termsdefinedinEN301140-1[1];-termsdefinedinISO/IEC9646-1[3]andinISO/IEC9646-2[4].SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)7Inparticular,thefollowingtermsdefinedinISO/IEC9646-1[3]apply:-AbstractTestSuite(ATS);-ImplementationUnderTest(IUT);-SystemUnderTest(SUT);-ProtocolImplementationConformanceStatement(PICS).3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ATSAbstractTestSuiteBIInvalidBehaviourtestsBOInopportuneBehaviourtestsBVValidBehaviourtestsCACapabilitytestsCSCallSegmentCSCapabilitySetEDP-REventDetectionPoint-RequestFSMFiniteStateMachineINIntelligentNetworkINAPIntelligentNetworkApplicationProtocolIPIntelligentPeripheraliSinitiatingSSFiSSPinitiatingSSPIUTImplementationUnderTestMSCMessageSequenceChartPDUProtocolDataUnitPICSProtocolImplementationConformanceStatementSCFServiceControlFunctionSCPServiceControlPointSDFServiceDataFunctionSDLSpecificationandDescriptionLanguageSRFSpecializedResourceFunctionSSFServiceSwitchingFunctionSSPServiceSwitchingPointSUTSystemUnderTestTCAPTransactionCapabilitiesApplicationPartTPTestPurposeTSSTestSuiteStructure4TestPurposegeneralities4.1IntroductionATPisdefinedforoneorseveralconformancerequirementstobetested.EachTPwillresultinatestcasekeepingthesamename,specifiedintheATS.4.2GroupingoftestpurposesperelementaryproceduresTheTestPurposesaregroupedbyelementaryprocedures.AproceduregroupselementaryINAPoperationswhichitispossibletotesttogether.Foreachelementaryprocedure,aredefined:howtoinvokeit;andwhatarethepossiblereturnresultsandreturnerror(s)attheINAPinterface.SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)8NOTE:SomehavenoresultsatallatthisINAPinterface.Inthesecases,andtohavea"visible"result,thePCOwillbeatthesignallingcontrolinterface.4.3SourceoftestpurposedefinitionsThetestpurposesarebasedontherequirementdocumentedinEN301140-1[1].4.4MethodusedfordevelopingTPs4.4.1UseofMSCsgeneratedbytheSDLmodelofCoreINAPCS-2TheSDLmodelofINAPCS-2isspecifiedwithobjectorientedSDL(SDL’92)andspecifiesthebehaviouroftheSSF.TheCS-2specificationinheritstheCS-1andspecifiesthewholeofCS-1andCS-2.TheSDLspecificationisthenormativespecificationoftheINAPbehaviourandiscontainedinannexAofEN301140-1[1].TheSDLmodelspecifiespreciselyandunambiguouslythebehaviourofandtheinterworkingbetweenthedifferentfunctionalentitiesoftheSSF.TheexternalinterfacesoftheSDLmodelaretwosignallingcontrolinterfaces(SigConAandSigConB)carryingabstractprimitives,andtheINAPinterfacestotheSCF.MappingsareprovidedfromSigConAandSigConBtoDSS.1andISUP.ThebehaviouroftheSDLmodelthusresemblesanSSP,andcanbeusedforserviceemulationandthedevelopmentoftestpurposesandtestcases.MSCsdeliveredbythisSDLmodelareusedintheTPdefinitionandareprovidedinadditiontothedescriptivetext.Thedevelopmentofthetestpurposes(TP)isdoneintwosteps:a)thedescriptivetextiscreatedtogetherwitharoughMSCdefinedbyhand.ItillustratesthebasicbehaviourinMSC-likeformwhichisexpectedfromtheIUT.TheroughMSCdoesnotcontainalltheconstraintsindetail.Thedescriptionmakesreferencetoapreambleandapostamble;b)adetailedMSCisdevelopedbysimulation:1)systemlevelMSCforAutolink(thetoolusedtoautomaticallygeneratetheTTCNtestcasesbasedontheMSCsandtheSDLmodel);2)MSCfordocumentationoftheTPs.ThereasonfordevelopingthedetailedMSCbysimulationisthatitcanbedonestepbystepwhiletheSDLmodelpromptsthedeveloperforthecorrectoptionsandparameters.TheMSCsidentifythedifferententities(SSF,SCF,SigConAandB)involvedinagivenconfigurationandshowsthedifferentcomponentsusedforatest,intermoftheIUT(representingtheSSFforinstance)andthetesters(representingtheSCFandtheSigConA,BorC).4.4.2TCAPadapterprimitivesInadditiontoshowingtheINAPprotocol,andinordertoeasetheimplementationofthetestsuite,theMSCsshowtheTCAPadapterprimitivessuchasTCbegin,TCcontinue,TCinvokeandTCendandshowusingstandardabbreviationstheINAPoperationswhichareembeddedintheTCAPprimitive,togetherwiththeoperationarguments.4.4.3GenerationofcorrespondingTestCasesUsingComputerAidedTestGenerationtechniques,TTCNtestcasescanbeautomaticallygeneratedfromtheSDLmodel.ItisalsopossibletoverifymanuallydevelopedtestcasesagainsttheSDLmodel.TheclearseparationofCS-1andCS-2intheSDLmodelmakesitpossibletouseitforbothCS-1andCS-2testcasedevelopment.SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)94.5MethodusedforTPdescription4.5.1TextandMSCsIngeneral,aTPisdescribedusingtextpresentedinatablefollowedbyanMSC.ThetabledescribingeachTPisasfollows:Table1a(TPname,alsocorrespondingtestcasename)TestPurpose:RequirementRef:SelectionCond:Testpreamble:TestdescriptionPasscriteria:TestpostambleInadditiontotheTPnameandareferencetothespecificationrequirement,thetablecontainsashorttitleofthetestpurpose,theconditiontoselectandrunthistestcase(expressionintermsofPICSreferences),thenameofthetestpreamble,informationonthetestbodyincludingforinstancedetailsonparameterswhichdonotappearinthecompanionMSC,thepasscriteriaforasuccessfultestandthenameofthetestpostamble.TheMSCwhichfollowstheTPdescriptiondescribesthetestbody,asthepreamblesandpostamblesaremostlydefinedbyasinglelineintheMSC.4.5.2TestcategoriesCapabilitytests(CA)CapabilitytestingprovidesalimitedtestingtoascertainthecapabilitiesstatedinthePICScanbeobserved.ValidBehaviourtests(BV)Predefinedstatetransitionsareconsideredasvalid.ThetestpurposesinthevalidbehaviourtestsubgroupcoverasfarasreasonabletheverificationofthenormalandexceptionalproceduresofthevariousFiniteStateMachines(FSMs),i.e.avalidbehaviourtestisatestwherethemessagesequenceandthemessagecontentsisconsideredasvalid.InvalidBehaviourtests(BI)ThistestsubgroupisintendedtoverifythattheIUTisabletoreactproperlyhavingreceivedaninvalidProtocolDataUnit(PDU).AninvalidPDUisdefinedasasyntacticallyincorrectmessage.InopportuneBehaviourtests(BO)ThistestgroupisintendedtoverifythattheIUTisabletoreactproperlyinthecaseaninopportuneprotocoleventoccurring.Suchaneventissyntacticallycorrectbutoccurswhenitisnotexpected,e.g.acorrectlycodedoperationisreceivedinawrongstate(theIUTmayrespondbysendingerrorUnexpectedComponentSequence).SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)104.5.3TestpurposenamingconventionTheidentifieroftheTPisbuiltaccordingtotheschemeintable1b.Table1b:TPidentifiernamingconventionschemeIdentifier:IN2_____IN2indicatesINCapabilitySet1and2(CS-1beinginCS-2)=interface:ASSF-SCFinterfaceBSSF-SRFinterfaceCSCF-SCFinterface=commonsetBASICBasicsetforCS-1complementedforCS-2CPHCallPartyHandlingfromCapabilitySet2CTMCordlessTerminalPortabilityfromCapabilitySet2=procedurenamelikeSFServiceFiltering=testcategory:CACapabilitytestsBVValidBehaviourtestsBIInvalidBehaviourtestsBOInopportuneBehaviourtests=sequentialnumber:(01-99)Exampleoftestpurposeandtestcasename:IN2_A_BASIC_SF_BV_024.5.4PreamblesandtheirnamingconventionsPreamblesareusedtobringtheIUTfromtheinitialstatetothestatewherethetesttakesplace.IntheCS-2scheme,thesetofthepreamblesformsatree,whichmeansthatinordertoreachthestatecreatedbypreambleP3,itisnecessarytoexecutepreambleP1followedbypreamblesP2thenP3.Thenamingconventionusedreflectsthedescriptionoftheconnectionviewsetbyexecutingthepreamble,intermsofnatureofthelegsperCallSegment(CS),startingfromthestablelegsthentheonesonholdthentheonesintransfer,withtheindicationofthenumberoflegs,whilethefirstletterindicateshowthisconfigurationwasinitiated.Thegeneralformis:a_[stableLegsPartyoronHold(legs)ortransfer(legs)forCallSegment1]_[idemforCallSegment2]_[idemforCallSegment3]where:aisletter:OforOriginating(outgoingcallforauser);TforTerminating(incomingcallforauser);IforInitiateCallAttempt(initiatedfromthenetwork).SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)11Thestatenamesandtheirabbreviationsusedare:Null1Party1POriginatingSet-upOSTerminatingSet-upTSTerminating1PartySet-upT1PStable1PartyS1PStable2PartyS2PTransfer(no.ofpassivelegs)TF(x)OnHold(no.ofpassivelegs)OH(x)StableMultiParty(no.ofpassivelegs)S(x)PTheterm"null"standsfor"none"asinpreambleO_NULL_S2P_OH3.TherecanbetwosetofCSswiththesamenatureoflegspresentatthesametime,asinthepreamblenameO_S2P_OH2_OH3.4.5.5HowtointerprettheparametersandtheirvaluesasusedintheMSCsTheMSCsshowtheexchangesofPDUsoftheTCAPprotocol,aswellastheCoreINAPprotocol.PDUsofbothprotocolsuseparameters.ThelistoftheparametersfortheCoreINAPprotocolisgiveninreferenceETS300374-1[5].ThelistofparametersfortheTCAPprotocolisrecalledhereforeachTCAPprimitives.Notethatonlymandatoryparametersareused.TCAPprimitivesfromSCFtoTCAP:TC_InvokeReq(InvokeID,DialogueID,Class,OperationCode,Timeout);TC_BeginReq(DialogueID,OriginatingAddress);TC_ContinueReq(DialogueID,OriginatingAddress);TC_EndReq(DialogueID,Termination);TC_AbortReq(DialogueID).TCAPprimitivesfromTCAPtoSCF:TC_InvokeInd(InvokeID,DialogueID,Class,OperationCode,LastComponent);TC_BeginInd(DialogueID,OriginatingAddress,ComponentPresent);TC_ContinueInd(DialogueID,OriginatingAddress,ComponentPresent);TC_EndInd(DialogueID,Termination,ComponentPresent);TC_AbortInd(DialogueID);TC_ErrorInd(InvokeID,DialogueID,ErrorCode,LastComponent);TC_ReturnResultInd(InvokeID,DialogueID,LastComponent,OperationCode,OperationArg);SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)12TC_RejectInd(InvokeID,DialogueID).Thevaluesoftheseparametersareeithermandatoryandimposedbythespecifications,ortheyareinformativeonlyandchosenarbitrarilyinrangescompatiblewiththespecifications.Thelistoftheinformativeparameters,forwhichavalueistobeassignedinparticularfortheexecutionofatestsuite,isincludedinthePIXITproforma.SeereferenceEN301140-4[2].AnnexBandAnnexCofthepresentdocumentcontainacopyofthePIXITproformaparametertablesofrespectivelytheCoreINAPandtheTCAPprotocols.TheseproformatablesarefilledupandcontaintheparametervaluesusedforthedefinitionoftheMSCsandTPs.ThepreambleT_OS(andallpreamblesandtestcaseswhichusethispreamble)containsreferencetoanASPMgt_SetTriggerTable.Thisdoesnotexistintheprotocol,butintheSDLmodelitidentifieswhichTriggerDetectionpointsneedtobesetbeforecommencingthetestcase.5Functionalconfigurationsundertest5.1SSFbasicfunctionsSCPSSPIPNon-integratedSRFSCFSSFCCFSRFSDFSCPwithsingleSSPFigure1:Configuration1:IUT=SSF(non-integratedwithSRF)SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)13SCPSSPIntegratedSRFSCFSSFCCFSRFSDFSCPwithsingleSSPFigure2:Configuration2:IUT=SSF(integratedwithSRF)5.2SSFadditionalfunctionsSCPinitiatingSSPIPIntegratedSRFSCFSSFCCFSRFSSFCCFassistingSSPSDFSSPAssist/Hand-off(assistingSSPwithrelay)Figure3:Configuration3:IUT=SSFofassistingSSP(integratedSRF)SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)14SCPinitiatingSSPIPNon-integratedSRFSCFSSFCCFSRFSSFCCFassistingSSPSDFSSPAssist/Hand-off(assistingSSPwithrelay)Figure4:Configuration4:IUT=SSFofassistingSSP(nonintegratedSRF)SCPinitiatingSSPIPNon-integratedSRFIntegratedSRFSCFSSFCCFSRFSSFCCFassistingSSPSDFSSPAssist/Hand-off(assistingSSPwithrelay)Figure5:Configuration5:IUT=SSFofinitiatingSSP6TSSandTPsforCS-1andCS-2basiccapabilities6.1Preamblesandpostamblesused6.1.1ListofpreamblesandpostamblesforCS1HereisalistofpreamblesusedintheBasicCS-1andCS-2capabilitiespart:O_OS;O_S2P;T_OS;SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)15T_S2P.HereisalistofpostamblesusedintheBasicCS-1andCS-2capabilitiespart:SigConA_Release;SigConA_Release_thenB;ReleaseCallA;ReleaseICA;ReleaseCallAB_cause_00;ReleaseCallAB_cause_0F;SigConB_Release.MorepreamblesandpostamblesaredefinedforthecompleteCS-2.Seeclause7.6.1.2Preambledescriptions6.1.2.1O_OSpreambleThispreambleisusedtobringtheIUTfromtheidleorNullstatetothe1partystate.MSC O_OSSCFCS2_SSFSigCon_ASigCon_BSetupInd{ callRef 1, calledPartyNumber ’2000’H, callingPartyNumber ’1000’H }TC_BeginInd51, oSSF, TRUETC_InvokeInd101, 51, IDP, TRUE, iDPArg : { serviceKey 1, calledPartyNumber ’2000’H, callingPartyNumber ’1000’H, eventTypeBCSM analysedInformation, createdCallSegmentAssociation 1 }SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)166.1.2.2O_S2PpreambleThispreambleisusedtobringtheIUTfromtheidleorNullstatetothe2partystate.MSC O_S2PSCFCS2_SSFSigCon_ASigCon_BSetupInd{ callRef 1, calledPartyNumber ’2000’H, callingPartyNumber ’1000’H }TC_BeginInd51, oSSF, TRUETC_InvokeInd101, 51, IDP, TRUE, iDPArg : { serviceKey 1, calledPartyNumber ’2000’H, callingPartyNumber ’1000’H, eventTypeBCSM analysedInformation, createdCallSegmentAssociation 1 }TC_InvokeReq1, 51, 2, RRB, short, rRBArg : { bcsmEvents { { eventTypeBCSM oDisconnect, monitorMode interrupted, legID sendingSideID : ’02’H } } }TC_InvokeReq2, 51, 2, CON, short, cONArg : { destinationRoutingAddress { ’2001’H }, callingPartyNumber ’1000’H }TC_ContinueReq51, oSCFSetupReq{ callRef 2, calledPartyNumber ’2001’H, callingPartyNumber ’1000’H }SIST EN 301 140-3-1:2001



ETSIETSIEN301140-3-1V1.1.3(2000-05)176.1.2.3T_OSpreambleMSC T_OSSCFCS2_SSFSigCon_ASigCon_BMgt_SetTriggerTable{ { legID ’01’H, serviceKey 1, eventTypeBCSM analysedInformation, monitorMode transparent } }Mgt_SetTriggerTable{ { legID ’01’H, serviceKey 1, eventTypeBCSM termAttemptAuthorized, monitorMode interrupted } }SetupInd{ callRef 1, calledPartyNumber ’2002’H, callingPartyNumber ’1000’H }TC_BeginInd51, oSSF, TRUETC_InvokeInd101, 51, IDP, TRUE, iDPArg : { serviceKey 1, calledPartyNumber ’2002’H, callingPartyNumber ’1000’H, eventTypeBCSM termAttemptAuthorized, createdCallSegmentAssociation 1 }SIST EN 301 140-3-1:2
...