SIST EN 301 490-1 V1.1.2:2005

• Abstract:

  TSS&TP for Call transfer.

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Mandate: T-326
• Ref Project: ETSI EN 301 490-1 V1.1.2 (2000-12) - Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Call transfer supplementary service for the VPN b service entry point; Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification

SIST EN 301 490-1 V1.1.2:2005 is the Slovenian adoption of EN 301 490-1 V1.1.2. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for the Call transfer supplementary service in the Private Integrated Services Network (PISN) inter-exchange signalling protocol. The document is written for people who need conformance tests for the VPN "b" service entry point, especially implementers, test labs and service providers working with PISN signalling equipment.

What does SIST EN 301 490-1 V1.1.2:2005 specify?

SIST EN 301 490-1 V1.1.2:2005 defines the test framework for Call transfer supplementary service conformance testing. It covers only VPN scenarios at the "b" service entry point and uses ISO/IEC 9646 as the testing methodology basis.

Clause / part	What it covers
Clause 1	Scope
Clause 2	References
Clause 3	Definitions and abbreviations
Clause 4	Test Suite Structure (TSS)
Clause 5	Test Purposes (TP)
Clause 6	Compliance
Clause 7	Requirements for a comprehensive testing service

Clause 4 groups the signalling procedures for transfer by join and transfer by rerouteing at the Transferring PINX, Primary PINX and Secondary PINX, plus subsequent actions and protocol interactions with other supplementary services and ANFs. Clause 5 turns those groups into named test purposes. Clauses 6 and 7 state what a compliant Abstract Test Suite (ATS) must contain and what a comprehensive testing service must use.

What are the key requirements of SIST EN 301 490-1 V1.1.2:2005?

The most important requirement is that the test purposes are based on EN 300 261 and only cover externally observable behaviour of the Implementation Under Test (IUT). In practice, this means the document is for conformance checking of real signalling behaviour, not internal design choices.

Test purpose structure and selection

Clause 5.1 sets the TP naming convention, the structure of each TP and the test strategy. Test purposes are numbered within each group, and optional TPs are controlled by selection criteria linked to the Protocol Implementation Conformance Statement (PICS). For a tester, this means the PICS decides which cases apply to a given product.

Transfer by join

Clauses 5.2.1.1, 5.2.1.3 and 5.2.1.5 define the join procedures at the Transferring, Primary and Secondary PINX. The TPs check that the IUT sends the expected FACILITY messages, handles callTransferComplete and callTransferActive APDUs, and moves between CT-Idle and CT-Await-Answer-From-UserC states as required. Practically, this verifies that a transfer can be completed by joining the two calls and that status information is forwarded correctly.

Transfer by rerouteing

Clauses 5.2.1.2, 5.2.1.4 and 5.2.1.6 cover rerouteing. These tests involve callTransferIdentify, callTransferInitiate and callTransferAbandon APDUs, plus timers T1, T2, T3 and T4. In practice, this checks the setup of a new connection to the Secondary PINX, the handling of timeouts and errors, and the correct clearing of calls when transfer cannot continue.

Later actions and interactions

Clause 5.2.1.7 covers later callTransferUpdate and subaddressTransfer behaviour, while clause 5.2.1.8 covers interactions with other supplementary services and ANFs. That matters because a product may have to forward or reject other service interactions correctly while a transfer is in progress.

Compliance

Clause 6 says a compliant ATS must match the TP set, use the same naming conventions, keep the TP-PICS relationship, and comply with ISO/IEC 9646-2. Clause 7 states that a comprehensive testing service must use the Remote test method from ISO/IEC 9646-2 for equipment claiming conformance to I-ETS 300808.

What terms does SIST EN 301 490-1 V1.1.2:2005 define?

• Abstract Test Suite (ATS) - the set of test cases built from the TPs to check conformance.
• Implementation Under Test (IUT) - the equipment or protocol implementation being tested.
• Protocol Implementation Conformance Statement (PICS) - the statement used to select which test cases apply.
• Test Purpose (TP) - a single stated test objective for one observable behaviour.
• Private Integrated Services Network (PISN) - the private network environment for which the signalling is specified.
• Private Integrated Services Network eXchange (PINX) - the exchange node used in the PISN signalling model.
• Call Transfer Supplementary Service (SS-CT) - the supplementary service that moves an established call from one path or user to another.
• Virtual Private Network (VPN) - the service context for which the tests are limited at the "b" service entry point.

Who uses SIST EN 301 490-1 V1.1.2:2005?

SIST EN 301 490-1 V1.1.2:2005 is used by protocol implementers, conformance test designers, test laboratories and quality teams working with PISN inter-exchange signalling. It is also relevant to organisations that provide a comprehensive testing service for network equipment and need a defined test basis for Call transfer. Buyers and technical reviewers can use it to check whether a supplier is offering testing against the right PISN VPN service entry point.

What changed in SIST EN 301 490-1 V1.1.2:2005 from the previous edition?

SIST EN 301 490-1 V1.1.2:2005 follows V1.1.1 January 2000. The history in the document also records V1.1.2 as voted in October 2000 and published in December 2000.

Which standards are used with SIST EN 301 490-1 V1.1.2:2005?

• EN 300 261 - the base Call transfer supplementary service specification that the TPs are built from.
• ETS 300 239 - supplies the generic functional protocol and APDU-related definitions used in the test cases.
• EN 300 172 - provides circuit-mode basic service behaviour referenced in the definitions.
• ETS 300 260 - provides functional models and information flows for Call transfer.
• EN 301 060-1 - defines the VPN "b" service entry point.
• ISO/IEC 9646-1, -2 and -3 - provide the conformance testing methodology, ATS framework and TTCN notation.
• ISO/IEC 11579-1 - provides the PISN reference configuration terms such as PISN and PINX.
• ETS 300 406 - gives the testing and specification methodology used to generate the TPs.

What does the SIST EN 301 490-1 V1.1.2:2005 document contain?

The document contains a TSS table, TP naming rules, and a TP structure template that shows how each test purpose is written. It then lists the detailed TPs for call transfer by join and by rerouteing, including normal flows, error responses, timer expiry and clearing cases. It also contains interaction tests with other supplementary services and ANFs, which is useful when building a real conformance test campaign rather than a simple feature check.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.±6SHFLILNDFLMDPrivate Integrated Services Network (PISN); Inter-exchange signalling protocol; Call transfer supplementary service for the VPN b service entry point; Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 490-1 Version 1.1.2SIST EN 301 490-1 V1.1.2:2005en01-januar-2005SIST EN 301 490-1 V1.1.2:2005SLOVENSKI
STANDARD
ETSIEN301490-1V1.1.2(2000-12)EuropeanStandard(Telecommunicationsseries)PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;CalltransfersupplementaryservicefortheVPN"b"serviceentrypoint;Part1:TestSuiteStructureandTestPurposes(TSS&TP)specificationSIST EN 301 490-1 V1.1.2:2005

ETSIETSIEN301490-1V1.1.2(2000-12)2ReferenceDEN/SPAN-05190-2KeywordsPISN,QSIG,VPN,CT,supplemetaryservice,TSS&TPETSI650RoutedesLuciolesF-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 490-1 V1.1.2:2005

ETSIETSIEN301490-1V1.1.2(2000-12)3ContentsIntellectualPropertyRights.4Foreword.41Scope.52References.53Definitionsandabbreviations.63.1Definitions.63.2Abbreviations.74TestSuiteStructure(TSS).85TestPurposes(TP).85.1Introduction.85.1.1TPnamingconvention.85.1.2SourceofTPdefinition.85.1.3TPstructure.95.1.4Teststrategy.95.2TPsforSS-CT.95.2.1SS-CTsignallingprocedures.105.2.1.1ActionsfortransferbyjoinattheTransferringPINX.105.2.1.2ActionsfortransferbyrerouteingattheTransferringPINX.125.2.1.3ActionsfortransferbyjoinatthePrimaryPINX.165.2.1.4ActionsfortransferbyrerouteingatthePrimaryPINX.165.2.1.5ActionsfortransferbyjoinattheSecondaryPINX.185.2.1.6ActionsfortransferbyrerouteingattheSecondaryPINX.185.2.1.7SubsequentactionsatthePrimaryandtheSecondaryPINX.205.2.1.8ProtocolinteractionsbetweenSS-CTandothersupplementaryservicesandANFs.216Compliance.227Requirementsforacomprehensivetestingservice.22Bibliography.23History.24SIST EN 301 490-1 V1.1.2:2005

ETSIETSIEN301490-1V1.1.2(2000-12)4IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).Thepresentdocumentispart1ofamulti-partdeliverablecoveringthePrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;CalltransfersupplementaryservicefortheVPN"b"serviceentrypoint,asidentifiedbelow:Part1:"TestSuiteStructureandTestPurposes(TSS&TP)specification";Part2:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proforma".NationaltranspositiondatesDateofadoptionofthisEN:01December2000DateoflatestannouncementofthisEN(doa):31March2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):30September2001DateofwithdrawalofanyconflictingNationalStandard(dow):30September2001SIST EN 301 490-1 V1.1.2:2005

ETSIETSIEN301490-1V1.1.2(2000-12)51ScopeThepresentdocumentspecifiestheTestSuiteStructureandTestPurposes(TSS&TP)fortheCallTransfersupplementaryserviceoftheInter-exchangesignallingprotocolforPrivateIntegratedServicesNetworks(PISN).TheobjectiveofthisTSSandTPsspecificationistoprovideconformancetestswhichgiveagreaterprobabilityofinter-operability.TheTSSandTPsspecificationcoverstheproceduresdescribedinEN300261[3].TheISOstandardforthemethodologyofconformancetesting(ISO/IEC9646-1[4],ISO/IEC9646-2[5]andISO/IEC9646-3[6])isusedasbasisforthetestmethodology.TheTestSuiteStructureandTestPurposesspecifiedinthisstandardareonlyintendedforVPNscenariosatthe"b"serviceentrypoint.TheVPN"b"serviceentrypointisdefinedinEN301060-1[9]andETR172[15].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN300172(V1.4):"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Circuit-modebasicservices[ISO/IEC11572(1996)modified]".[2]ETSIETS300239:"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Genericfunctionalprotocolforthesupportofsupplementaryservices[ISO/IEC11582(1995),modified]".[3]ETSIEN300261:"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Calltransfersupplementaryservice[ISO/IEC13869(1995)modified]".[4]ISO/IEC9646-1(1994):"Informationtechnology;OpenSystemsInterconnection;Conformancetestingmethodologyandframework;Part1:Generalconcepts".[5]ISO/IEC9646-2(1994):"Informationtechnology;OpenSystemsInterconnection;Conformancetestingmethodologyandframework;Part2:Abstracttestsuitespecification".[6]ISO/IEC9646-3:"Informationtechnology;OpenSystemsInterconnection;Conformancetestingmethodologyandframework;Part3:TheTreeandTabularCombinedNotation(TTCN)".[7]ITU-TRecommendationI.112(1993):"VocabularyoftermsforISDNs".[8]ITU-TRecommendationI.210(1993):"PrinciplesoftelecommunicationservicessupportedbyanISDNandthemeanstodescribethem".[9]ETSIEN301060-1(V1.2.2):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Basiccallcontrol;Enhancementatthe".b"serviceentrypointforVirtualPrivateNetwork(VPN)applications;Part1:Protocolspecification".[10]ETSIETS300260:"PrivateIntegratedServicesNetwork(PISN);Specification,functionalmodelsandinformationflows;Calltransfersupplementaryservice".SIST EN 301 490-1 V1.1.2:2005

ETSIETSIEN301490-1V1.1.2(2000-12)6[11]ETSIEN300171:"PrivateIntegratedServicesNetwork(PISN);Specification,functionalmodelsandinformationflows;Controlaspectsofcircuit-modebasicservices[ISO/IEC11574(1994)modified]".[12]ETSIETS300238:"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Nameidentificationsupplementaryservices[ISO/IEC13868(1995)modified]".[13]ISO/IEC11579-1:"Informationtechnology;Telecommunicationsandinformationexchangebetweensystems;Privateintegratedservicesnetwork;Part1:ReferenceconfigurationforPISNExchanges(PINX)".[14]ETSII-ETS300808:"PrivateIntegratedServicesNetwork(PISN);CordlessTerminalMobility(CTM);Inter-exchangesignallingprotocol;Cordlessterminaloutgoingcalladditionalnetworkfeature".[15]ETSIETR172:"BusinessTeleCommunications(BTC);VirtualPrivateNetworking(VPN);Servicesandnetworkingaspects;Standardizationrequirementsandworkitems".[16]ETS300406(1995):"MethodsforTestingandSpecification(MTS);Protocolandprofileconformancetestingspecifications;Standardizationmethodology".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:AbstractTestSuite(ATS):refertoISO/IEC9646-1[4]ImplementationUnderTest(IUT):refertoISO/IEC9646-1[4]ProtocolImplementationConformanceStatement(PICS):refertoISO/IEC9646-1[4]PICSproforma:refertoISO/IEC9646-1[4]TestPurpose(TP):refertoISO/IEC9646-1[4]alerting:seeEN300261[3]answered:seeEN300261[3]ApplicationProtocolDataUnit(APDU):seeETS300239[2]basicservice:seeITU-TRecommendationI.210[8]gatewayPINX:seeEN300172[1]interpretationAPDU:seeETS300239[2]originatingPINX:seeETS300239[2]primarycall:seeETS300260[10]private:seeISO/IEC11579-1[13]PrivateIntegratedServicesNetwork(PISN):seeISO/IEC11579-1[13]PrivateIntegratedServicesNetworkExchange(PINX):seeISO/IEC11579-1[13]publicISDN:seeISO/IEC11579-1[13]secondarycall:seeEN300261[3]signalling:seeITU-TRecommendationI.112[7]SIST EN 301 490-1 V1.1.2:2005

ETSIETSIEN301490-1V1.1.2(2000-12)7supplementaryservice:seeITU-TRecommendationI.210[8]supplementaryservicescontrolentity:seeETS300239[2]telecommunicationnetwork:seeISO/IEC11579-1[13]terminal:seeISO/IEC11579-1[13]terminatingPINX:seeETS300239[2]transferbyjoin:seeEN300261[3]transferbyrerouteing:seeEN300261[3]transitPINX:seeETS300239[2]user:seeEN300171[11]userA:seeEN300261[3]userB:seeEN300261[3]userC:seeEN300261[3]3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:APDUApplicationProtocolDataUnitATSAbstractTestSuiteISDNIntegratedServicesDigitalNetworkIUTImplementationUnderTestPICSProtocolImplementationConformanceStatementPINXPrivateIntegratedServicesNetworkeXchangePISNPrivateIntegratedServicesNetworkSS-CTCallTransferSupplementaryServiceTPTestPurposeTSSTestSuiteStructureVPNVirtualPrivateNetworkSIST EN 301 490-1 V1.1.2:2005

ETSIETSIEN301490-1V1.1.2(2000-12)84TestSuiteStructure(TSS)SignallingproceduresattheVPNbinterfaceGroupActionsfortransferbyjoinattheTransferringPINXTrans01ActionsfortransferbyrerouteingattheTransferringPINXTrans02ActionsfortransferbyjoinatthePrimaryPINXPrimr01ActionsfortransferbyrerouteingatthePrimaryPINXPrimr02ActionsfortransferbyjoinattheSecondaryPINXSecnd01ActionsfortransferbyrerouteingattheSecondaryPINXSecnd02SubsequentactionsatthePrimaryandtheSecondaryPINXSubsq01ProtocolinteractionsbetweenSS-CTandothersupplementaryservicesandANFsInter015TestPurposes(TP)5.1IntroductionForeachtestrequirementaTPisdefined.5.1.1TPnamingconventionTPsarenumbered,startingat001,withineachgroup.GroupsareorganizedaccordingtotheTSS.Additionalreferencesareaddedtoidentifytheactualtestsuiteandwhetheritappliestothenetworkortheuser(seetable1).Table1:TPidentifiernamingconventionschemeIdentifier:__=supplementaryservice:"CT"=groupupto8digitfieldrepresentinggroupreferenceaccordingtoTSS=sequentialnumber(001-999)5.1.2SourceofTPdefinitionTheTPsarebasedonEN300261[3].SIST EN 301 490-1 V1.1.2:2005

ETSIETSIEN301490-1V1.1.2(2000-12)95.1.3TPstructureEachTPhasbeenwritteninamannerwhichisconsistentwithallotherTPs.TheintentionofthisistomaketheTPsmorereadableandcheckable.Aparticularstructurehasbeenusedandthisisillustratedintable2.ThistableshouldbereadinconjunctionwithanyTP,i.e.useaTPasanexampletofullyunderstandthetable.Table2:StructureofasingleTPforCTTPpartTextExampleHeadertabseetable1tabsubclause0.0.0StimulusEnsurethattheIUTintheorstate3orCT-Idle,etc.seebelowformessagestructurereceivingaXXXXmessageortorequesta.Reactionsends,saves,does,etc.usingenblocsending,.iftheactionissendingseebelowformessagestructure,etc.andremainsinthesamestateorandentersstateMessagestructuremessagecontainingaSETUP,FACILITY,CONNECT,.a)informationelementwithb)aencodedasorincludingandbacktoaorb,Bearercapability,Facility,.SelectionSelectioncriteriareferenceSupportofSS-CTbyjoin.PICS:A1NOTE1:Inordertousethesamestructureasforthetestgroupselection,theselectioncriteriaisindicatedatthebottomofthetestpurpose.NOTE2:Unlessspecifiedthemessagesarevalidandcontainatleastthemandatoryinformationelementsandpossiblyoptionalinformationelements,theinformationelementsarevalidandcontainatleastthemandatoryparametersandpossiblyoptionalparameters.5.1.4TeststrategyAsthebasestandardEN300261[3]containsnoexplicitrequirementsfortesting,theTPsweregeneratedasaresultofananalysisofthebasestandardandthecorrespondingPICSproforma.TheTPsareonlybasedonconformancerequirementsrelatedtotheexternallyobservablebehaviouroftheIUT,andarelimitedtoconceivablesituationstowhicharealimplementationislikelytobefaced(ETS300406[16]).Allthetestpurposesaremandatoryunlesstheyhaveaselectioncriteria.Optionaltestpurposes(withselectioncriteria),areapplicableaccordingtotheconfigurationoptionsoftheIUT.TheconfigurationoptionsshallbecoveredbyaPICSitem.5.2TPsforSS-CTAllPICSitemsreferredtointhissubclauseareasspecifiedinETS300261[3]unlessindicatedotherwisebyanothernumberedreference.Unlessspecified:-OnlytherequirementsfromthepointofviewoftheVPN"b"serviceentrypointareconsidered.ThisimpliesthattheinteractionswithothernetworksareoutofscopeofthisspecificationandcausesthatthecorrespondingTestPurposesarenotincludedinthisspecification.-Themessagesindicatedarevalidandcontainatleastthemandatoryinformationelementsandpossiblyoptionalinformationelements.SIST EN 301 490-1 V1.1.2:2005

ETSIETSIEN301490-1V1.1.2(2000-12)10-Theinformationelementsindicatedarevalidandcontainatleastthemandatoryparametersandpossiblyoptionalparameters.Thefollowingwordingconventionwasdefinedtomakethetestpurposesmorereadable:-Whenamessageistobesentorreceivedonacallindependentsignallingconnection,themessagenameshallbefollowedbya'(sc)',e.g.CONNECT(sc)meansthattheCONNECTmessageisconveyedonacallindependentsignallingconnection.-InordertodifferentiatebetweenthecallstatesofthetwobasiccallsTransferringPINX-PrimaryPINXandTransferringPINX-SecondaryPINXthefollowingnamingconventionisintroduced:Callstatesforabasiccall,whichisestablishedbetweentheTransferringPINXandthePrimaryPINXarecalledprimarycallstates,callstatesforabasiccall,whichisestablishedbetweentheTransferringPINXandtheSecondaryPINXarecalledsecondarycallstates.-AllthetestpurposesarevalidforbothuserandnetworksideoftheVPNbinterface.Inordertosimplifythetextandtomakethetestpurposesmorereadable,onlytheUsersideCallstates(Ux)areindicatedinthetestpurposes.ForthenetworksideoftheVPNbinterface,themappingtablebelowindicateswhichnetworkcallstate(Ny)correspondstotheusercallstateusedinthetestpurpose.EquivalentcallstatemeanstherethatthesamemessageflowappliesfromtheIUTpointofview(e.g.:IUTsendsaSETUPmessagegivesthecallstateU01orN06).UsersidecallstateequivalentnetworksidecallstateU04N07U07N04U10N10EXAMPLE:EnsurethattheIUTinthecallstateU04…isequivalenttothefollowingnetworksidetestpurpose:EnsurethattheIUTinthecallstateN07…5.2.1SS-CTsignallingprocedures5.2.1.1ActionsfortransferbyjoinattheTransferringPINXCT_Trans01_001subclause6.5.1EnsurethattheIUTinthestateCT-Idle,onreceiptofavalidcallTransferInvokerequestfromUserAandtransferisnotallowed(primarycallstateisnotU10orsecondarycallstateisnotU10orsecondarycallstateisnotU04orinvalidrequestorbecauseoffailure),doesnottakeanyaction,remainstheCT-Idlestate.CT_Trans01_002subclause6.5.1.1EnsurethattheIUTinthestateCT-Idle,onreceiptofavalidcallTransferInvokerequestfromUserAandtransferisallowed(primarycallstateisU10andsecondarycallstateisU10andUserCisinanISDN)andnotrerouteing(usingtransferbyjoin),sendsaFACILITYmessagecontainingacallTransferCompleteinvokeAPDUtoPrimaryPINXwiththedataelementendDesignationandoptionallyredirectionNumber,redirectionNameandbasicCallInfoElementsintheargument,sendsaFACILITYmessagecontainingacallTransferCompleteinvokeAPDUtoSecondaryPINXwiththedataelementendDesignationandoptionallyredirectionNumber,redirectionNameandbasicCallInfoElementsintheargument,enterstheCT-Idlestate.SIST EN 301 490-1 V1.1.2:2005

ETSIETSIEN301490-1V1.1.2(2000-12)11CT_Trans01_003subclause6.5.1.1EnsurethattheIUTinthestateCT-Idle,onreceiptofavalidcallTransferInvokerequestfromUserAandtransferisallowed(primarycallstateisU10andsecondarycallstateisU10andUserCisinanISDN)andnotrerouteing(usingtransferbyjoin),sendsaFACILITYmessagecontainingacallTransferCompleteinvokeAPDUtoPrimaryPINXwiththedataelementendDesignationanddataelementcallStatuswithvaluealertingandoptionallyredirectionNumber,redirectionNameandbasicCallInfoElementsintheargument,sendsaFACILITYmessagecontainingacallTransferCompleteinvokeAPDUtoSecondaryPINXwiththedataelementendDesignationandoptionallyredirectionNumber,redirectionNameandbasicCallInfoElementsintheargument,enterstheCT-Await-Answer-From-UserCstate.CT_Trans01_004subclause6.5.1.1EnsurethattheIUT,intheprimarycallstateU10andintheCT-Await-Answer-From-UserCstate,receivingaFACILITYmessagecontainingacallTransferUpdateinvokeAPDUfromPrimaryPINX,,sendsacallTransferUpdateinvokeAPDUcorrespondingofthereceivedFACILITYmessagetoSecondaryPINX,remainsintheCT-Await-Answer-From-UserCstate.Selection:IUTsupportssendingofcallTransferUpdateinvokeAPDU.PICS:D5.CT_Trans01_005subclause6.5.1.1EnsurethattheIUT,inthesecondarycallstateU10,receivingaFACILITYmessagecontainingacallTransferUpdateinvokeAPDUfromSecondaryPINX,sendsacallTransferUpdateinvokeAPDUcorrespondingofthereceivedFACILITYmessagetoPrimaryPINX,remainsintheCT-Await-Answer-From-UserCstate.Selection:IUTsupportssendingofcallTransferUpdateinvokeAPDU.PICS:D5.CT_Trans01_006subclause6.5.1.1EnsurethattheIUT,intheprimarycallstateU10andintheCT-Await-Answer-From-UserCstate,receivingaFACILITYmessagecontainingasubadressesTransferinvokeAPDUfromPrimaryPINX,sendsasubadressesTransferinvokeAPDUcorrespondingofthereceivedFACILITYmessagetoSecondaryPINX,remainsintheCT-Await-Answer-From-UserCstate.Selection:IUTsupportssendingofsubaddressTransferinvokeAPDU.PICS:D7.CT_Trans01_007subclause6.5.1.1EnsurethattheIUT,inthesecondarycallstateU10,receivingaFACILITYmessagecontainingasubadressesTransferinvokeAPDUfromSecondaryPINX,sendsasubadressesTransferinvokeAPDUcorrespondingofthereceivedFACILITYmessagetoPrimaryPINX,remainsintheCT-Await-Answer-From-UserCstate.CT_Trans01_008subclause6.5.1.1EnsurethattheIUT,inthesecondarycallstateU04andintheCT-Await-Answer-From-UserCstate,receivingaCONNECTmessagefromtheSecondaryPINX,sendsaFACILITYmessagecontainingacallTransferActiveinvokeAPDUtoPrimaryPINXwiththedataelementbasicCallInfoElementsoptionallyincluded,associatesprimaryandsecondarycall,enterstheCT-Idlestate.CT_Trans01_009subclause6.5.1.1EnsurethattheIUT,inthesecondarycallstateU04andintheCT-Await-Answer-From-UserCstate,receivingaCONNECTmessagefromtheSecondaryPINXcontainingFacilityinformationelementwithaconnectedNameinvokeAPDUasdefinedinETS300238[12],sendsaFACILITYmessagecontainingacallTransferActiveinvokeAPDUtoPrimaryPINXwiththedataelementbasicCallInfoElementsand/orconnectedNameoptionallyincluded,associatesprimaryandsecondarycall,enterstheCT-Idlestate.CT_Trans01_010subclause6.5.1.1EnsurethattheIUT,intheprimarycallstateU10andintheCT-Await-Answer-From-UserCstate,receivingaNOTIFYmessagefromPrimaryPINX,sendsaNOTIFYmessagecontainingallNotificationindicatorinformationelementsreceivedtowardstheSecondaryPINX,enterstheCT-Await-Answer-From-UserCstate.SIST EN 301 490-1 V1.1.2:2005

ETSIETSIEN301490-1V1.1.2(2000-12)12CT_Trans01_011subclause6.5.1.1EnsurethattheIUT,inthesecondarycallstateU04andintheCT-Await-Answer-From-UserCstate,receivingaNOTIFYmessagefromSecondaryPINX,sendsaNOTIFYmessagecontainingallNotificationindicatorinformationelementsreceivedtowardsthePrimaryPINX,enterstheCT-Await-Answer-From-UserCstate.CT_Trans01_012subclause6.5.1.1EnsurethattheIUT,intheprimarycallstateU10andintheCT-Await-Answer-From-UserCstate,receivingacallclearingfromPrimaryPINX,sendsacallclearingtowardstheSecondaryPINXenterstheCT-Idlestate.CT_Trans01_0013subclause6.5.1.1EnsurethattheIUT,inthesecondarycallstateU04andintheCT-Await-Answer-From-UserCstate,receivingacallclearingfromSecondaryPINX,sendsacallclearingtowardsthePrimaryPINXenterstheCT-Idlestate.5.2.1.2ActionsfortransferbyrerouteingattheTransferringPINXSelection:IUTsupportsSS-CTbyrerouteing.PICS:A2.CT_Trans02_001subclause6.5.1.3EnsurethattheIUTinthestateCT-Idle,receivingofavalidcallTransferInvokerequestfromUserAandtransferisallowed(primarycallstateisU10andsecondarycallstateisU04andUserCisinanISDN)andusingtransferbyrerouteing,sendsaFACILITYmessagecontainingacallTransferIdentifyinvokeAPDUonsecondarycall,startstimerT1,enterstheCT-Await-Identify-Responsestate.CT_Trans02_002subclause6.5.1.3EnsurethattheIUT,inthesecondarycallstateU04andintheCT-Await-Identify-Responsestate,receivingaFACILITYmessagecontainingcallTransferIdentifyreturnresultAPDUfromtheSecondaryPINXwiththedataelementcallIdentityandrerouteingNumberintheargument,sendsaFACILITYmessagecontainingcallTransferInitiateinvokeAPDUtoPrimaryPINXwiththedataelementcallIdentityandrerouteingNumberreceived,startstimerT3,enterstheCT-Await-Initiate-Responsestate.CT_Trans02_003subclause6.5.1.3EnsurethattheIUT,inprimarycallstateU10andintheCT-Await-Identify-Responsestate,receivingacallclearingfromPrimaryPINX,clearssecondarycall,enterstheCT-Idlestate.CT_Trans02_004subclause6.5.1.3EnsurethattheIUT,inthesecondarycallstateU04andintheCT-Await-Identify-Responsestate,receivingacallclearingfromSecondaryPINX,clearsprimarycall,enterstheCT-Idlestate.CT_Trans02_005subclause6.5.1.3EnsurethattheIUT,intheprimarycallstateU10andintheCT-Await-Initiate-Responsestate,receivingacallclearingfromPrimaryPINX,clearssecondarycall,enterstheCT-Idlestate.CT_Trans02_006subclause6.5.1.3EnsurethattheIUT,inthesecondarycallstateU04andintheCT-Await-Initiate-Responsestate,receivingacallclearingfromSecondaryPINX,clearsprimarycall,enterstheCT-Idlestate.SIST EN 301 490-1 V1.1.2:2005

ETSIETSIEN301490-1V1.1.2(2000-12)13CT_Trans02_007subclause6.5.1.3EnsurethattheIUT,intheprimarycallstateU10andintheCT-Await-Initiate-Responsestate,receivingaDISCONNECTmessagefromPrimaryPINXwithacallTransferInitiatereturnresultAPDU,continuescallclearingofprimarycall,clearssecondarycall,enterstheCT-Idlestate.CT_Trans02_008subclause6.5.1.4EnsurethattheIUT,inthesecondarycallstateU04andintheCT-Await-Identify-Responsestate,receivingaFACILITYmessagecontainingcallTransferIdentifyreturnerrorAPDUfromtheSecondaryPINX,andcalltransfermaynotbereinitiatedusingtransferbyjoinprocedures,doesnottakeanyaction,enterstheCT-Idlestate.CT_Trans02_009subclause6.5.1.4EnsurethattheIUT,inthesecondarycallstateU04andintheCT-Await-Identify-Responsestate,receivingaFACILITYmessagecontainingcallTransferIdentifyrejectAPDUfromtheSecondaryPINX,andcalltransfermaynotbereinitiatedusingtransferbyjoinprocedures,doesnottakeanyaction,enterstheCT-Idlestate.CT_Trans02_010subclause6.5.1.4EnsurethattheIUT,inthesecondarycallstateU10andintheCT-Await-Identify-Responsestate,receivingaFACILITYmessagecontainingcallTransferIdentifyreturnerrorAPDUfromtheSecondaryPINX,andcalltransfermaybereinitiatedusingtransferbyjoinprocedures,sendsaFACILITYmessagecontainingacallTransferCompleteinvokeAPDUtoPrimaryPINXwiththedataelementendDesignationandoptionallyredirectionNumber,redirectionNameandbasicCallInfoElementsintheargument,sendsaFACILITYmessagecontainingacallTransferCompleteinvokeAPDUtoSecondaryPINXwiththedataelementendDesignationandoptionallyredirectionNumber,redirectionNameandbasicCallInfoElementsintheargument,enterstheCT-Idlestate.CT_Trans02_011subclause6.5.1.4EnsurethattheIUT,inthesecondarycallstateU04andintheCT-Await-Identify-Responsestate,receivingaFACILITYmessagecontainingcallTransferIdentifyreturnerrorAPDUfromtheSecondaryPINX,andcalltransfermaybereinitiatedusingtransferbyjoinprocedures,sendsaFACILITYmessagecontainingacallTransferCompleteinvokeAPDUtoPrimaryPINXwiththedataelementendDesignationanddataelementcallStatuswithvaluealertingandoptionallyredirectionNumber,redirectionNameandbasicCallInfoElementsintheargument,sendsaFACILITYmessagecontainingacallTransferCompleteinvokeAPDUtoSecondaryPINXwiththedataelementendDesignationandoptionallyredirectionNumber,redirectionNameandbasicCallInfoElementsintheargument,enterstheCT-Await-Answer-From-UserCstate.CT_Trans02_012subclause6.5.1.4EnsurethattheIUT,inthesecondarycallstateU10andintheCT-Await-Identify-Responsestate,receivingaFACILITYmessagecontainingcallTransferIdentifyrejectAPDUfromtheSecondaryPINX,andcalltransfermaybereinitiatedusingtransferbyjoinprocedures,sendsaFACILITYme
...