SIST EN 301 490-1 V1.1.2:2005
(Main)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
General Information
- Abstract
TSS&TP for Call transfer.
- Status
- Published
- Publication Date
- 31-Dec-2004
- 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
Overview
SIST EN 301 490-1 V1.1.2:2005 defines the Test Suite Structure and Test Purposes (TSS&TP) for the Call Transfer Supplementary Service within the Inter-exchange Signalling Protocol of Private Integrated Services Networks (PISN). Focused on the Virtual Private Network (VPN) “b” service entry point, this standard provides a framework for ensuring the interoperability and conformance of call transfer features across different PISN implementations. Developed in alignment with European and international standardization methodologies, it references best practices for telecommunication protocol testing and is critical for organizations aiming to implement or validate VPN call transfer functions in multi-vendor or integrated network environments.
Key Topics
- Test Suite Structure (TSS): Outlines the organization and hierarchy of test groups and test cases, covering scenarios such as transfer by join or by reroute across different PISN exchanges (PINX).
- Test Purposes (TP): Details the objectives of each test, focusing on externally observable behavior of the Implementation Under Test (IUT) for conformity with functional requirements.
- Naming Conventions: Test cases are systematically identified using a clear format, supporting traceability and easy reference.
- VPN “b” Interface Focus: Ensures that conformance is validated specifically at the VPN “b” entry point, in accordance with referenced PISN and VPN standards.
- Conformance Methodology: Utilizes principles and practices from ISO/IEC 9646, providing a robust conceptual and practical foundation for protocol conformance testing.
- Interoperability Assurance: Supports both network-side and user-side call state mapping, improving consistency and reliability in real-world deployments.
- Mandatory and Optional Requirements: Specifies which test scenarios are compulsory according to configuration options documented in the Protocol Implementation Conformance Statement (PICS).
Applications
SIST EN 301 490-1 V1.1.2:2005 offers significant value to telecommunications vendors, network service providers, and testing labs by:
- Enhancing Interoperability: Ensures that PISN call transfer capabilities are implemented consistently, supporting smooth communication across multi-vendor networks and integrated business systems.
- Reducing Implementation Risk: Defines essential test scenarios, helping organizations identify protocol deviations and integration issues early in the deployment cycle.
- Supporting Certification and Compliance: Provides a structured TSS and TP framework that is recognized across Europe, aiding certification and regulatory processes for telecommunication equipment.
- Guiding Product Development: Enables manufacturers and software developers to align their call transfer implementations with established best practices, ensuring compatibility and scalability.
- Facilitating Maintenance and Upgrades: Makes it easier to validate ongoing conformance during network upgrades or when introducing new supplementary services to the VPN environment.
Related Standards
The content and methodology of SIST EN 301 490-1 V1.1.2:2005 are closely aligned with the following standards:
- EN 300 261: Definition of the Call Transfer Supplementary Service for PISN.
- ISO/IEC 9646: International standards for conformance testing methodology and framework.
- EN 301 060-1: Specification of basic call control enhancements at the VPN “b” service entry point.
- ETS 300 239: Protocols supporting supplementary services in PISN environments.
- ETS 300 406: Methods for protocol and profile conformance testing.
For organizations working on PISN solutions, adherence to this standard helps ensure their offerings meet established requirements for reliability, interoperability, and quality in advanced network services.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 301 490-1 V1.1.2:2005 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "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". This standard covers: TSS&TP for Call transfer.
TSS&TP for Call transfer.
SIST EN 301 490-1 V1.1.2:2005 is classified under the following ICS (International Classification for Standards) categories: 33.040.35 - Telephone networks. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 301 490-1 V1.1.2:2005 is associated with the following European legislation: Standardization Mandates: T-326. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.
SIST EN 301 490-1 V1.1.2:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
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.:+33492944200Fax:+33493654716SiretN°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:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.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
...