SIST EN 301 491-1 V1.1.2:2005

• Abstract:

  TSS&TP for Call offer.

• 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 491-1 V1.1.2 (2000-11) - Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Call offer supplementary service; Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification

SIST EN 301 491-1 V1.1.2:2005 is the Slovenian adoption of ETSI EN 301 491-1 V1.1.2 for the Private Integrated Services Network (PISN) Call offer supplementary service. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for conformance testing of the inter-exchange signalling protocol, with a focus on implementations used at the VPN "b" service entry point.

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

SIST EN 301 491-1 V1.1.2:2005 defines the test structure and the individual test purposes for Call offer in PISN signalling. The aim is to give conformance tests that improve the probability of interoperability between implementations.

The document is organized into clauses for scope, references, definitions and abbreviations, Test Suite Structure (TSS), Test Purposes (TP), compliance, and requirements for a comprehensive testing service. It is part 1 of a multi-part standard, and Part 2 provides the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma.

The scope is limited to VPN scenarios at the "b" service entry point. Interworking with Public ISDNs is outside the scope described for this entry point.

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

Clause 5 is the core of the document. It turns the Call offer service into named, structured test purposes that can be selected from a Protocol Implementation Conformance Statement (PICS) and turned into executable conformance tests.

Test purpose structure and naming

Clause 5.1 defines a consistent TP naming convention and a common TP structure. Each TP is numbered within its group, and the group is tied to the TSS. In practice, this helps testers map a specific test to a specific service function and to the PICS item that enables it.

Test strategy

Clause 5.1.4 states that the TPs are derived from EN 300 362 and are based on externally observable behaviour. They are limited to situations that a real implementation is likely to face. This matters because the test set is aimed at practical interoperability, not abstract edge cases.

Signalling procedures for SS-CO

Clause 5.2.1 covers Call offer signalling at the originating and terminating Private Integrated Services Network eXchange (PINX), with and without path retention. The test purposes check message handling such as SETUP, FACILITY, PROGRESS, ALERTING, CONNECT, DISCONNECT, and NOTIFY, plus timer behaviour such as T1 and PRT1. In practice, this is what verifies that a PINX handles call offer correctly when a call is offered to a busy user, accepted, rejected, or times out.

Path retention behaviour

The path retention procedures in clause 5.2.1 check the additional signalling needed when Call offer is requested with retained path. They use Path Retain and Service Available APDUs and the callOffer bit in the service list. For implementers, this means the retained-call state and the later call offer request must work together correctly.

Interaction with other supplementary services

Clause 5.2.3 covers interactions with Call Transfer (CT), Call Forwarding Unconditional (CFU), Call Forwarding Busy (CFB), Do Not Disturb Override (DNDO), and Call Intrusion (CI). These test purposes use PICS and PIXIT selections because the expected behaviour depends on which combined services an implementation supports. This is important for systems that provide more than one supplementary service on the same PINX.

Compliance and testing service

Clause 6 says a compliant ATS must match the specified test purposes, use the same naming conventions, maintain the PICS relationship, and follow ISO/IEC 9646-2. Clause 7 adds that any organization claiming a comprehensive testing service must use the Remote test method from ISO/IEC 9646-2. In practice, this links the standard directly to how conformance testing is built and delivered.

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

• Abstract Test Suite (ATS) - the structured set of test cases used to verify conformance.
• Implementation Under Test (IUT) - the equipment or software being checked against the standard.
• Protocol Implementation Conformance Statement (PICS) - the statement used to select relevant test cases.
• Test Purpose (TP) - one stated verification objective for a specific requirement or behaviour.
• Private Integrated Services Network eXchange (PINX) - the exchange node used in the PISN environment.
• Virtual Private Network (VPN) - the application context for the "b" service entry point covered here.
• Application Protocol Data Unit (APDU) - the signalling data unit carried in the Facility information element.

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

SIST EN 301 491-1 V1.1.2:2005 is used by conformance test laboratories, PISN and PINX equipment vendors, network operators, and quality managers who need to verify Call offer behaviour. It is also useful for buyer-side technical review when checking whether a product has test coverage for Call offer and related supplementary services.

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

• EN 300 362 - the base Call offer supplementary service specification that the TPs are based on.
• ETS 300 239 - provides the generic functional protocol for supplementary services and related APDU definitions.
• EN 300 172 - provides circuit-mode basic services and call state definitions used in the TPs.
• ETS 300 406 - gives the testing and conformance specification methodology used for generating TPs.
• ISO/IEC 9646-1 - provides the general conformance testing framework.
• ISO/IEC 9646-2 - provides the abstract test suite specification rules used for compliance.
• ISO/IEC 9646-3 - provides Tree and Tabular Combined Notation (TTCN).
• ITU-T Recommendation I.112 - provides ISDN vocabulary.
• ITU-T Recommendation I.210 - provides principles for describing telecommunication services.
• EN 301 060-1 and ETR 172 - define the VPN "b" service entry point context used by this standard.
• Part 2 of EN 301 491 - provides the ATS and PIXIT proforma for this service.

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

The document contains a Test Suite Structure that groups procedures for the VPN "b" service entry point, followed by detailed Test Purposes written in a common format. Those test purposes cover originating and terminating behaviour, path retention, timer expiry, and interactions with CT, CFU, CFB, DNDO, and CI.

It also contains naming rules for test purposes, a mapping between user-side and network-side call states, and selection references to PICS and PIXIT items. The compliance clause states how an ATS must be built from these test purposes, and the final clause states the minimum method for a comprehensive testing service.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Zasebno omrežje z integriranimi storitvami (PISN) – Signalizacijski protokol med centralami – Dopolnilna storitev: ponudba klica – 1. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) – SpecifikacijaPrivate Integrated Services Network (PISN); Inter-exchange signalling protocol; Call offer supplementary service; Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 491-1 Version 1.1.2SIST EN 301 491-1 V1.1.2:2005en01-januar-2005SIST EN 301 491-1 V1.1.2:2005SLOVENSKI
STANDARD
ETSIEN301491-1V1.1.2(2000-11)EuropeanStandard(Telecommunicationsseries)PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Calloffersupplementaryservice;Part1:TestSuiteStructureandTestPurposes(TSS&TP)specificationSIST EN 301 491-1 V1.1.2:2005

ETSIETSIEN301491-1V1.1.2(2000-11)2ReferenceDEN/SPAN-05191-2KeywordsPISN,supplementaryservice,testing,TSS&TP,QSIGETSI650RoutedesLuciolesF-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 491-1 V1.1.2:2005

ETSIETSIEN301491-1V1.1.2(2000-11)3ContentsIntellectualPropertyRights.4Foreword.41Scope.52References.53Definitionsandabbreviations.63.1Definitions.63.2Abbreviations.64TestSuiteStructure(TSS).75TestPurposes(TP).85.1Introduction.85.1.1TPnamingconvention.85.1.2SourceofTPdefinition.85.1.3TPstructure.95.1.4Teststrategy.95.2TPsforCO.95.2.1SS-COsignallingprocedures.105.2.1.1ActionsattheOriginatingPINX.105.2.1.1.1SendingCORequestwithoutPathRetention.105.2.1.1.2SendingCORequestwithPathRetention.115.2.1.2ActionsattheTerminatingPINX.125.2.1.2.1ReceiptCOrequestwithoutPathRetention.125.2.1.2.2ReceiptCOrequestwithPathRetention.125.2.2ImpactofInterworkingwithPublicISDNs.135.2.3ProtocolInteractionbetweenSS-COandotherSupplementaryServicesandANFs.135.2.3.1InteractionwithCallTransfer.135.2.3.1.1ActionsattheCO-OriginatingPINX.135.2.3.1.2ActionsattheCO-TerminatingPINX.135.2.3.2InteractionwithCallForwardingUnconditional.145.2.3.2.1ActionsattheCO-OriginatingPINX.145.2.3.2.2ActionsattheCO-TerminatingPINX.155.2.3.3InteractionwithCallForwardingBusy.155.2.3.3.1ActionsattheCO-OriginatingPINX.155.2.3.3.2ActionsattheCO-TerminatingPINX.165.2.3.4InteractionwithDoNotDisturbOverride.185.2.3.4.1ActionsattheCO-TerminatingPINX.185.2.3.5InteractionwithCallIntrusion.185.2.3.5.1ActionsattheCO-OriginatingPINX.185.2.3.5.2ActionsattheCO-TerminatingPINX.186Compliance.197Requirementsforacomprehensivetestingservice.19History.20SIST EN 301 491-1 V1.1.2:2005

ETSIETSIEN301491-1V1.1.2(2000-11)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).ThepresentdocumentcoversthePrivateIntegratedServiceNetwork(PISN)Inter-exchangesignallingprotocol-CallOffersupplementaryservice-TestSuiteStructureandTestPurposes(TSS&TP)specification.Thepresentdocumentispart1ofamulti-partENcoveringthePrivateIntegratedServiceNetwork(PISN);Inter-exchangesignallingprotocol;Calloffersupplementaryservice,asidentifiedbelow:Part1:"TestSuiteStructureandTestPurposes(TSS&TP)specification";Part2:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proforma".NationaltranspositiondatesDateofadoptionofthisEN:3November2000DateoflatestannouncementofthisEN(doa):28February2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31August2001DateofwithdrawalofanyconflictingNationalStandard(dow):31August2001SIST EN 301 491-1 V1.1.2:2005

ETSIETSIEN301491-1V1.1.2(2000-11)51ScopeThepresentdocumentspecifiestheTestSuiteStructureandTestPurposes(TSS&TP)fortheCallOffersupplementaryservicesoftheInterexchangesignallingprotocolforPrivateIntegratedServicesNetworks(PISN).Theobjectiveofthepresentdocumentistoprovideconformancetestswhichgiveagreaterprobabilityofinter-operability.TheTSSandTPsspecificationcoverstheproceduresdescribedinEN300362[3].TheISOstandardforthemethodologyofconformancetesting(ISO/IEC9646-1[5],ISO/IEC9646-2[6]andISO/IEC9646-3[11])isusedasbasisforthetestmethodology.TheTestSuiteStructureandTestPurposesspecifiedinthepresentdocumentareonlyintendedforVPNscenariosatthe"b"serviceentrypoint.TheVPN"b"serviceentrypointisdefinedinEN301060-1[9]andETR172[10].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(1995):"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Genericfunctionalprotocolforthesupportofsupplementaryservices[ISO/IEC11582(1995),modified]".[3]ETSIEN300362:"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Calloffersupplementaryservice[ISO/IEC14843(1996),modified]".[4]ETSIETS300406(1995):"MethodsforTestingandSpecification(MTS);Protocolandprofileconformancetestingspecifications;Standardizationmethodology".[5]ISO/IEC9646-1(1994):"Informationtechnology;OpenSystemsInterconnection;Conformancetestingmethodologyandframework;Part1:Generalconcepts".[6]ISO/IEC9646-2(1994):"Informationtechnology;OpenSystemsInterconnection;Conformancetestingmethodologyandframework;Part2:Abstracttestsuitespecification".[7]ITU-TRecommendationI.112(1993):"VocabularyoftermsforISDNs".[8]ITU-TRecommendationI.210(1993):"PrinciplesoftelecommunicationservicessupportedbyanISDNandthemeanstodescribethem".[9]ETSIEN301060-1:"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Basiccallcontrol;Enhancementatthe"b"serviceentrypointforVirtualPrivateNetwork(VPN)applications;Part1:Protocolspecification".[10]ETSIETR172:"BusinessTeleCommunications(BTC);VirtualPrivateNetworking(VPN);Servicesandnetworkingaspects;Standardizationrequirementsandworkitems".SIST EN 301 491-1 V1.1.2:2005

ETSIETSIEN301491-1V1.1.2(2000-11)6[11]ISO/IEC9646-3:"Informationtechnology;OpenSystemsInterconnection;Conformancetestingmethodologyandframework;Part3:TheTreeandTabularCombinedNotation(TTCN)".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:AbstractTestSuite(ATS):refertoISO/IEC9646-1[5].ImplementationUnderTest(IUT):refertoISO/IEC9646-1[5].ProtocolImplementationConformanceStatement(PICS):refertoISO/IEC9646-1[5].PICSproforma:refertoISO/IEC9646-1[5].TestPurpose(TP):refertoISO/IEC9646-1[5].callindependentsignallingconnection:seeETS300239[2],definition4.7.callrelated:seeETS300239[2],definition4.9.incomingcall:seeEN300172[1],subclause4.4.InformationElements(IEs)withinvalidcontents:seeEN300172[1],subclause4.14.IntegratedServicesDigitalNetwork(ISDN):seeITU-TRecommendationI.112[7],definition308.invokeAPDU:seeETS300239[2],subclause11.3.3.4.originatingPINX:seeEN300172[1],subclause4.5.outgoingcall:seeEN300172[1],subclause4.4.rejectAPDU:seeETS300239[2],subclause11.3.3.4.returnerrorAPDU:seeETS300239[2],subclause11.3.3.4.returnresultAPDU:seeETS300239[2],subclause11.3.3.4.service;telecommunicationservice:seeITU-TRecommendationI.112[7],definition201.supplementaryservice:seeITU-TRecommendationI.210[8],subclause2.4.terminatingPINX:seeEN300172[1],subclause4.5.transitPINX:seeEN300172[1],subclause4.5.VirtualPrivateNetwork(VPN):refertoEN301060-1[9]andETR172[10].3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:APDUApplicationProtocolDataUnitATSAbstractTestSuiteCFBCallForwardingBusyCFUCallForwardingUnconditionalCICallIntrusionCOCallOfferCR1CallReference#1SIST EN 301 491-1 V1.1.2:2005

ETSIETSIEN301491-1V1.1.2(2000-11)7CR2CallReference#2CTCallTransferDNDODoNotDisturbOverrideIEInformationElementISDNIntegratedServicesDigitalNetworkIUTImplementationUnderTestPICSProtocolImplementationConformanceStatementPINXPrivateIntegratedServicesNetworkeXchangePISNPrivateIntegratedServicesNetworkPIXITProtocolImplementationeXtraInformationforTestingT1TimerT1PRT1TimerPRT1TPTestPurposeTSSTestSuiteStructureVPNVirtualPrivateNetwork4TestSuiteStructure(TSS)SignallingproceduresattheVPN"b"serviceentrypointGroupProceduresattheOriginatingPINXforSendingSS-CORequestwithoutPathRetentionOrig01forSendingSS-CORequestwithPathRetentionOrig02ProceduresattheTerminatingPINXforReceiptSS-CORequestwithoutPathRetentionTerm01forReceiptSS-CORequestwithPathRetentionTerm02ProceduresforProtocolInteractionsbetweenCallOfferandCallTransferattheCO-OriginatingPINXCT_OrigattheCO-TerminatingPINXCT_TermProceduresforProtocolInteractionsbetweenCallOfferandCallForwardingUnconditionalattheCO-OriginatingPINXCFU_OrigattheCO-TerminatingPINXCFU_TermProceduresforProtocolInteractionsbetweenCallOfferandCallForwardingBusyattheCO-OriginatingPINXCFB_OrigattheCO-TerminatingPINXCFB_TermProceduresforProtocolInteractionsbetweenCallOfferandDoNotDisturbOverrideattheCO-TerminatingPINXDNDO_TermProceduresforProtocolInteractionsbetweenCallOfferandCallIntrusionattheCO-OriginatingPINXCI_OrigattheCO-TerminatingPINXCI_TermSIST EN 301 491-1 V1.1.2:2005

ETSIETSIEN301491-1V1.1.2(2000-11)85TestPurposes(TP)5.1IntroductionForeachtestrequirementaTPisdefined.5.1.1TPnamingconventionTPsarenumbered,startingat001,withineachgroup.GroupsareorganizedaccordingtotheTSS.Additionalreferencesareaddedtoidentifytheactualtestsuiteandwhetheritappliestothenetworkortheuser(seetable1).Table1:TPidentifiernamingconventionschemeIdentifier:__=supplementaryservice:"CO"=groupupto10digitfieldrepresentinggroupreferenceaccordingtoTSS=sequentialnumber(001-999)5.1.2SourceofTPdefinitionTheTPsarebasedonEN300362[3].SIST EN 301 491-1 V1.1.2:2005

ETSIETSIEN301491-1V1.1.2(2000-11)95.1.3TPstructureEachTPhasbeenwritteninamannerwhichisconsistentwithallotherTPs.TheintentionofthisistomaketheTPsmorereadableandcheckable.Aparticularstructurehasbeenusedandthisisillustratedintable2.ThistableshouldbereadinconjunctionwithanyTP,i.e.useaTPasanexampletofullyunderstandthetable.Table2:StructureofasingleTPforCOTPpartTextExampleHeadertabSeetable1tabSubclause0.0.0StimulusEnsurethattheIUTintheorState3orCO-Idle,etc.seebelowformessagestructureReceivingaXXXXmessageortorequesta.ReactionSends,saves,does,etc.Usingenblocsending.Iftheactionissendingseebelowformessagestructure,etc.andremainsinthesamestateorandentersstateMessagestructuremessagecontainingaSETUP,FACILITY,CONNECT.a)informationelementwithb)aencodedasorincludingandbacktoaorb,Bearercapability,Facility.SelectionSelectioncriteriareferenceSupportofSS-COinOriginatingPINX.PICS:A1NOTE1:Inordertousethesamestructureasforthetestgroupselection,theselectioncriteriaisindicatedatthebottomofthetestpurpose.NOTE2:Unlessspecifiedthemessagesarevalidandcontainatleastthemandatoryinformationelementsandpossiblyoptionalinformationelements,theinformationelementsarevalidandcontainatleastthemandatoryparametersandpossiblyoptionalparameters.5.1.4TeststrategyAsthebasestandardEN300362[3]containsnoexplicitrequirementsfortesting,theTPsweregeneratedasaresultofananalysisofthebasestandardandthecorrespondingPICSproforma.TheTPsareonlybasedonconformancerequirementsrelatedtotheexternallyobservablebehaviouroftheIUT,andarelimitedtoconceivablesituationstowhicharealimplementationislikelytobefaced(ETS300406[4]).5.2TPsforCOAllPICSitemsreferredtointhissubclauseareasspecifiedinEN300362[3]unlessindicatedotherwisebyanothernumberedreference.Unlessspecified:-onlytherequirementsfromthepointofviewoftheVPN"b"serviceentrypointareconsidered.ThisimpliesthattheinteractionswithothernetworksareoutofscopeofthisspecificationandcausesthatthecorrespondingTestPurposesarenotincludedinthisspecification;-themessagesindicatedarevalidandcontainatleastthemandatoryinformationelementsandpossiblyoptionalinformationelements;-theinformationelementsindicatedarevalidandcontainatleastthemandatoryparametersandpossiblyoptionalparameters.SIST EN 301 491-1 V1.1.2:2005

ETSIETSIEN301491-1V1.1.2(2000-11)10Thefollowingwordingconventionwasdefinedtomakethetestpurposesmorereadable:-whenamessageistobesentorreceivedonacallindependentsignallingconnection,themessagenameshallbefollowedbya"(sc)",e.g.CONNECT(sc)meansthattheCONNECTmessageisconveyedonacallindependentsignallingconnection.AllthetestpurposesarevalidforbothuserandnetworksideoftheVPNbinterface.Inordertosimplifythetextandtomakethetestpurposesmorereadable,onlytheUsersideCallstates(Ux)areindicatedinthetestpurposes.ForthenetworksideoftheVPNbinterface,themappingtable3indicateswhichnetworkcallstate(Ny)correspondstotheusercallstateusedinthetestpurpose.EquivalentcallstatemeanstherethatthesamemessageflowappliesfromtheIUTpointofview(e.g.:IUTsendsaSETUPmessagegivesthecallstateU01orN06).Table3UsersidecallstateEquivalentnetworksidecallstateU00N00U03N09U04N07U07N04U09N03U10N10U11N12U19N19EXAMPLE:EnsurethattheIUTinthecallstateU03…isequivalenttothefollowingnetworksidetestpurpose:EnsurethattheIUTinthecallstateN09…5.2.1SS-COsignallingprocedures5.2.1.1ActionsattheOriginatingPINX5.2.1.1.1SendingCORequestwithoutPathRetentionCO_Orig01_001subclause6.6.1.1EnsurethattheIUTinthecallstateU00andintheCO-Idlestate,inordertoinitiateaCORequest,sendsaSETUPmessagecontainingintheFacilityIEacallOfferRequestinvokeAPDUandenterstheCO-Wait-Ackstate.CO_Orig01_002subclause6.6.1.1EnsurethattheIUTinthecallstateU03andintheCO-Wait-Ackstate,receivingaFACILITYmessagecontainingintheFacilityIEacallOfferRequestreturnresultAPDU,sendsnomessages,remainsinthecallstateU03andenterstheCO-Idlestate.CO_Orig01_003subclause6.6.1.1EnsurethattheIUTinthecallstateU03andintheCO-Wait-Ackstate,receivingaPROGRESSmessagecontainingintheFacilityIEacallOfferRequestreturnresultAPDU,sendsnomessages,remainsinthecallstateU03andenterstheCO-Idlestate.CO_Orig01_004subclause6.6.1.1EnsurethattheIUTinthecallstateU03andintheCO-Wait-AckstatereceivinganALERTINGmessagecontainingintheFacilityIEacallOfferRequestreturnresultAPDU,sendsnomessages,entersthecallstateU04andtheCO-Idlestate.SIST EN 301 491-1 V1.1.2:2005

ETSIETSIEN301491-1V1.1.2(2000-11)11CO_Orig01_005subclause6.6.1.2EnsurethattheIUTinthecallstateU03andintheCO-Wait-Ackstate,receivingaALERTINGmessagewithoutanyFacilityIE,sendsnomessages,entersthecallstateU04andtheCO-Idlestate.CO_Orig01_006subclause6.6.1.2EnsurethattheIUTinthecallstateU03andintheCO-Wait-Ackstate,receivingaCONNECTmessagecontainingintheFacilityIEacallOfferRequestreturnerrorAPDU,sendsaCONNECTACKNOWLEDGEmessage,entersthecallstateU10andtheCO-Idlestate.CO_Orig01_007subclause6.6.1.2EnsurethattheIUTinthecallstateU03andtheCO-Wait-Ackstate,receivingaDISCONNECTmessagecontainingintheFacilityIEacallOfferRequestrejectAPDU,sendsaRELEASEmessage,entersthecallstateU19andtheCO-Idlestate.CO_Orig01_008subclause6.6.1.2EnsurethattheIUTinthecallstateU03andtheCO-Wait-Ackstate,onexpiryoftimerT1,sendsnomessage,remainsinthesameprotocolcontrolstateasitwasandenterstheCO-Idlestate.5.2.1.1.2SendingCORequestwithPathRetentionCO_Orig02_001subclauseA.5.1EnsurethattheIUTinthecallstateU00andinthePRTO-Idlestate,inordertorequestpathretentionforCORequestinvocation,sendsaSETUPmessagecontainingintheFacilityIEapathRetaininvokeAPDUwiththebitforcallO
...