Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Call completion supplementary service for the VPN b service entry point; Part 1: Test Suite Structure and Test Purposes (TSS&TP) specification

DEN/SPS-05188-2

Zasebno omrežje z integriranimi storitvami (PISN) – Signalizacijski protokol med centralami – Dopolnilna storitev "dokončanje klica" za vstopno točko VPN "b" storitve – 1. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) – Specifikacija

General Information

Status
Published
Publication Date
24-Sep-2000
Technical Committee
Current Stage
12 - Completion
Due Date
15-Sep-2000
Completion Date
25-Sep-2000
Mandate

Buy Standard

Standard
EN 301 452-1 V1.1.4:2005
English language
31 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

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 completion 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 452-1 Version 1.1.4SIST EN 301 452-1 V1.1.4:2005en01-januar-2005SIST EN 301 452-1 V1.1.4:2005SLOVENSKI
STANDARD



SIST EN 301 452-1 V1.1.4:2005



ETSIEN301452-1V1.1.4(2000-09)EuropeanStandard(Telecommunicationsseries)PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;CallcompletionsupplementaryservicefortheVPNbserviceentrypoint;Part1:TestSuiteStructureandTestPurposes(TSS&TP)specificationSIST EN 301 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)2ReferenceDEN/SPS-05188-2KeywordsCCBS,CCNR,CCS,QSIG,stage3,supplementaryservice,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 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)3ContentsIntellectualPropertyRights.4Foreword.41Scope.52References.53Definitionsandabbreviations.63.1Definitions.63.1.1Definitionsrelatedtoconformancetesting.63.1.2DefinitionsrelatedtoETS300366.63.2Abbreviations.74TestSuiteStructure(TSS).85TestPurposes(TP).85.1Introduction.85.1.1TPnamingconvention.85.1.2SourceofTPdefinition.95.1.3TPstructure.95.1.4Teststrategy.95.2TPsforCCsignallingprocedures.105.2.1SS-CCsignallingprocedures.115.2.1.1ActionsattheOriginatingPINX.115.2.1.1.1CCBSinvocation.115.2.1.1.2CCNRinvocation.125.2.1.1.3UserAnotbusy-pathnon-reservationmethod.135.2.1.1.4UserAnotbusy-pathreservationmethod.145.2.1.1.5UserAbusy-pathnon-reservationmethod.175.2.1.1.6UserAbusy-eitherbeforeorafterthepathreservationmethod.175.2.1.1.7CCBS/CCNRcancellation.185.2.1.1.8Timersexpiry.205.2.1.2ActionsattheTerminatingPINX.225.2.1.2.1CCBSinvocation.225.2.1.2.2CCNRinvocation.235.2.1.2.3IndicationthatUserBisnotbusy.245.2.1.2.4CCCallwithoutPathReservation.245.2.1.2.5CCCallwithPathReservation.255.2.1.2.6CCBS/CCNRSuspensionandResumption.265.2.1.2.7CCBS/CCNRCancellation.275.2.2ImpactofInterworkingwithPublicISDNs.285.2.3ProtocolInteractionbetweenSS-CCBSandotherSupplementaryServicesandANFs.285.2.3.1OriginatingPINXproceduresforinvokingSS-CCBSataSS-CFU/SS-CFB/SS-CDdiverted-toUser.285.2.4ProtocolInteractionbetweenSS-CCNRandotherSupplementaryServicesandANFs.285.2.4.1OriginatingPINXproceduresforinvokingSS-CCNRataSS-CFU/SS-CFB/SS-CCNR/SS-CDdiverted-toUser.286Compliance.297Requirementsforacomprehensivetestingservice.29Bibliography.30History.31SIST EN 301 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)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)hasbeenproducedbyETSITechnicalCommitteeSignallingProtocolandSwitching(SPS).ThepresentdocumentcoversthePrivateIntegratedServiceNetwork(PISN)Inter-exchangesignallingprotocol-CallCompletionsupplementaryservice-TestSuiteStructureandTestPurposes(TSS&TP)specification.Thepresentdocumentispart1ofamulti-partdeliverablecoveringCallcompletionsupplementaryservice,asidentifiedbelow:Part1:"TestSuiteStructureandTestPurposes(TSS&TP)specification";Part2:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proforma".NationaltranspositiondatesDateofadoptionofthisEN:8September2000DateoflatestannouncementofthisEN(doa):31December2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):30June2001DateofwithdrawalofanyconflictingNationalStandard(dow):30June2001SIST EN 301 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)51ScopeThepresentdocumentspecifiestheTestSuiteStructureandTestPurposes(TSS&TP)fortheCallCompletionsupplementaryservicesoftheInterexchangesignallingprotocolforPrivateIntegratedServicesNetworks(PISN).Theobjectiveofthepresentdocumentistoprovideconformancetests,whichgiveagreaterprobabilityofinter-operability.TheTSS&TPsspecificationcoverstheproceduresdescribedinETS300366[3].TheISOstandardforthemethodologyofconformancetesting(ISO/IEC9646-1[5],ISO/IEC9646-2[6]andISO/IEC9646-3[7])isusedasbasisforthetestmethodology.TheTestSuiteStructureandTestPurposesspecifiedinthepresentdocumentareonlyintendedforVPNscenariosatthe"b"serviceentrypoint.TheVPN"b"serviceentrypointisdefinedinEN301060-1[10]andETR172[11].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.[1]ETSIEN300172(V1.4):"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Circuit-modebasicservices[ISO/IEC11572(1996)modified]".[2]ETSIETS300239(1993):"PrivateTelecommunicationNetwork(PTN);Inter-exchangesignallingprotocol;Genericfunctionalprotocolforthesupportofsupplementaryservices".[3]ETSIETS300366(1995):"PrivateIntegratedServicesNetwork(PISN);Inter-exchangesignallingprotocol;Callcompletionsupplementaryservices[ISO/IEC13870(1995)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]ISO/IEC9646-3(1992):"Informationtechnology;OpenSystemsInterconnection;Conformancetestingmethodologyandframework;Part3:TheTreeandTabularCombinedNotation(TTCN)".[8]ITU-TRecommendationI.112(1993):"VocabularyoftermsforISDNs".[9]ITU-TRecommendationI.210(1993):"PrinciplesofthetelecommunicationservicessupportedbyanISDNandthemeanstodescribethem".[10]ETSIEN301060-1(V1.2):"IntegratedServicesDigitalNetwork(ISDN);DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Basiccallcontrol;Enhancementatthe"b"serviceentrypointforVirtualPrivateNetwork(VPN)applications;Part1:Protocolspecification".[11]ETSIETR172(1995):"BusinessTeleCommunications(BTC);VirtualPrivateNetworking(VPN);ServicesandNetworkingaspects;Standardizationrequirementsandworkitems".SIST EN 301 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)6[12]ETSIEN300196-1(V1.2):"IntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingdefinitionsapply:3.1.1Definitionsrelatedtoconformancetestingabstracttestcase:RefertoISO/IEC9646-1[5]AbstractTestSuite(ATS):RefertoISO/IEC9646-1[5]activetest:TestcasewheretheIUTisrequiredtosendaparticularmessage,butnotinreactiontoareceivedmessage.ThiswouldusuallyinvolvetheuseofPIXITinformationtoseehowthismessagecanbegeneratedandquiteoftenisspecifiedinanATSusinganimplicitsendeventcomponent:RefertoEN300196-1[12]ImplementationUnderTest(IUT):RefertoISO/IEC9646-1[5]implicitsendevent:RefertoISO/IEC9646-3[7]lowertester:RefertoISO/IEC9646-1[5]passivetest:TestcasewheretheIUTisrequiredtorespondtoaprotocolevent(e.g.receivedmessage)withanotherprotocolevent(e.g.sendmessage)whichnormallydoesnotrequireanyspecialoperatorinterventionasassociatedwiththeimplicitsendeventpointofcontrolandobservation:RefertoISO/IEC9646-1[5]ProtocolImplementationConformanceStatement(PICS):RefertoISO/IEC9646-1[5]PICSproforma:RefertoISO/IEC9646-1[5]ProtocolImplementationeXtraInformationforTesting(PIXIT):RefertoISO/IEC9646-1[5]PIXITproforma:RefertoISO/IEC9646-1[5]systemundertest:RefertoISO/IEC9646-1[5]TestPurpose(TP):RefertoISO/IEC9646-1[5]3.1.2DefinitionsrelatedtoETS300366callindependentsignallingconnection:SeeETS300239[2],definition4.7callrelated:SeeETS300239[2],definition4.9incomingcall:SeeEN300172[1],subclause4.4incomingGatewayPINX:SeeEN300172[1],subclause4.6InformationElements(IEs)withinvalidcontents:SeeEN300172[1],subclause4.14IntegratedServicesDigitalNetwork(ISDN):SeeITU-TRecommendationI.112[8],definition308SIST EN 301 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)7invokeAPDU:SeeETS300239[2],subclause11.3.3.4originatingPINX:SeeEN300172[1],subclause4.5outgoingcall:SeeEN300172[1],subclause4.4outgoingGatewayPINX:SeeEN300172[1],subclause4.6rejectAPDU:SeeETS300239[2],subclause11.3.3.4returnerrorAPDU:SeeETS300239[2],subclause11.3.3.4returnresultAPDU:SeeETS300239[2],subclause11.3.3.4ROSEAPDU:SeeETS300239[2],definition4.33service;telecommunicationservice:SeeITU-TRecommendationI.112[8],definition201supplementaryservice:SeeITU-TRecommendationI.210[9],subclause2.4terminatingPINX:SeeEN300172[1],subclause4.5transitPINX:SeeEN300172[1],subclause4.5VirtualPrivateNetwork(VPN):RefertoEN301060-1[10]andETR172[11]3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:APDUApplicationProtocolDataUnitATSAbstractTestSuiteBCBasicCallCCBSCallCompletiontoBusySubscriberCCNRCallCompletiononNoReplyCRCallReferenceIEInformationElementISDNIntegratedServicesDigitalNetworkIUTImplementationUnderTestPICSProtocolImplementationConformanceStatementPINXPrivateIntegratedServicesNetworkeXchangePISNPrivateIntegratedServicesNetworkPIXITProtocolImplementationeXtraInformationforTestingPSS1PrivateIntegratedSignallingSystemNumber1sccallindependentsignallingconnectionSCMSignallingCarriageMechanismT1TimerT1T2TimerT2T3TimerT3T4TimerT4TPTestPurposeTSSTestSuiteStructureVPNVirtualPrivateNetworkSIST EN 301 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)84TestSuiteStructure(TSS)SignallingproceduresattheVPN"b"serviceentrypointGroupProceduresattheOriginatingPINXforSS-CCBSOrig01forSS-CCNROrig02forUserAnotbusy-pathnon-reservationmethodOrig03forUserAnotbusy-pathreservationmethodOrig04forUserAbusy-pathnon-reservationmethodOrig05forUserAbusy-eitherbeforeorafterthepathreservationmethodOrig06forCCBS/CCNRcancellationOrig07forTimersexpiryOrig08ProceduresattheTerminatingPINXforSS-CCBSTerm01forSS-CCNRTerm02forindicationthatUserBisnotbusyTerm03forCCCallwithoutPathReservationTerm04forCCCallwithPathReservationTerm05forCCBS/CCNRsuspensionandresumptionTerm06forCCBS/CCNRcancellationTerm07ProceduresforProtocolInteractionsbetweenSS-CCBSandothersupplementaryservicesandANFsProceduresfortheOriginatingPINXInt01ProceduresforProtocolInteractionsbetweenSS-CCNRandothersupplementaryservicesandANFsProceduresfortheOriginatingPINXInt025TestPurposes(TP)5.1IntroductionForeachtestrequirementaTPisdefined.5.1.1TPnamingconventionTPsarenumbered,startingat001,withineachgroup.GroupsareorganizedaccordingtotheTSS.Additionalreferencesareaddedtoidentifytheactualtestsuiteandwhetheritappliestothenetworkortheuser(seetable1).SIST EN 301 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)9Table1:TPidentifiernamingconventionschemeIdentifier:__=supplementaryservice:"CC"=groupupto8digitfieldrepresentinggroupreferenceaccordingtoTSS=sequentialnumber(001-999)5.1.2SourceofTPdefinitionTheTPsarebasedonETS300366[3].5.1.3TPstructureEachTPhasbeenwritteninamannerwhichisconsistentwithallotherTPs.TheintentionofthisistomaketheTPsmorereadableandcheckable.Aparticularstructurehasbeenusedandthisisillustratedintable2.ThistableshouldbereadinconjunctionwithanyTP,i.e.useaTPasanexampletofullyunderstandthetable.Table2:StructureofasingleTPforCCTPpartTextExampleHeadertabseetable1tabsubclause0.0.0StimulusEnsurethattheIUT,intheorstate3orCC-Idle,etc.seebelowformessagestructurereceivingaXXXXmessageortorequesta.Reactionsends,saves,does,etc.usingenblocsending,.iftheactionissendingseebelowformessagestructure,etc.andremainsinthesamestateorandentersstateMessagestructuremessagecontainingaSETUP,FACILITY,CONNECT,.a)informationelementwithb)aencodedasorincludingandbacktoaorb,Bearercapability,Facility,.SelectionSelectioncriteriareferencePINXcanactasOriginatingPINX.PICS:A1NOTE1:Inordertousethesamestructureasfortestgroupselection,theselectioncriteriaisindicatedatthebottomofthetestpurpose.NOTE2:Unlessspecifiedthemessagesarevalidandcontainatleastthemandatoryinformationelementsandpossiblyoptionalinformationelements,theinformationelementsarevalidandcontainatleastthemandatoryparametersandpossiblyoptionalparameters.5.1.4TeststrategyAsthebasestandardETS300366[3]containsnoexplicitrequirementsfortesting,theTPsweregeneratedasaresultofananalysisofthebasestandardandthecorrespondingPICSproforma.TheTPsareonlybasedonconformancerequirementsrelatedtotheexternallyobservablebehaviouroftheIUT,andarelimitedtoconceivablesituationstowhicharealimplementationislikelytobefaced(ETS300406[4]).SIST EN 301 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)105.2TPsforCCsignallingproceduresAllPICSitemsreferredtointhissubclauseareasspecifiedinETS300366[3]unlessindicatedotherwisebyanothernumberedreference.Unlessspecified:-OnlytherequirementsfromthepointofviewoftheVPN"b"serviceentrypointareconsidered.ThisimpliesthattheinteractionswithothernetworksareoutofscopeofthepresentdocumentandcausesthatthecorrespondingTestPurposesarenotincludedinthisspecification.-Themessagesindicatedarevalidandcontainatleastthemandatoryinformationelementsandpossiblyoptionalinformationelements.-Theinformationelementsindicatedarevalidandcontainatleastthemandatoryparametersandpossiblyoptionalparameters.Thefollowingwordingconventionwasdefinedtomakethetestpurposesmorereadable:-Whenamessageistobesentorreceivedonacallindependentsignallingconnection,themessagenameshallbefollowedbya'(sc)',e.g.CONNECT(sc)meansthattheCONNECTmessageisconveyedonacallindependentsignallingconnection.-Intestcaseswhereabearerconnectionandasignallingconnectionisrequiredatthesamesideoftheinterface,itisnecessarytodifferentiatebetweenthecallstatesofthebearerconnectionandthecallstatesofthesignallingconnection.Thereforethefollowingnamingconventionisintroduced:"EnsurethattheIUTinthecallstatesU03andU10(sc)…".ThismeansthattheIUTisincallstateU03forthebearerconnection,andtheIUTisinthecallstateU10forthesignallingconnection.-AllthetestpurposesarevalidforbothuserandnetworksideoftheVPNbinterface.Inordertosimplifythetextandtomakethetestpurposesmorereadable,onlytheUsersideCallstates(Ux)areindicatedinthetestpurposes.ForthenetworksideoftheVPNbinterface,themappingtablebelowindicateswhichnetworkcallstate(Ny)correspondstotheusercallstateusedinthetestpurpose.EquivalentcallstatemeanstherethatthesamemessageflowappliesfromtheIUTpointofview(e.g.:IUTsendsaSETUPmessagegivesthecallstateU01orN06).UsersidecallstateEquivalentnetworksidecallstateU00N00U01N06U10N10EXAMPLE:EnsurethattheIUT,inthecallstateU01…isequivalenttothefollowingnetworksidetestpurpose:EnsurethattheIUT,inthecallstateN06…SIST EN 301 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)115.2.1SS-CCsignallingprocedures5.2.1.1ActionsattheOriginatingPINX5.2.1.1.1CCBSinvocationCC_Orig01_001subclause6.5.2.1.1EnsurethattheIUTinthecallstateU00(sc)andintheCC-Idlestate,inordertoinitiateaCCBScall,sendsaSETUP(sc)messagecontainingintheFacilityIEaccbsRequestinvokeAPDUandenterstheCC-Wait-Ackstate.CC_Orig01_002subclause6.5.2.1.1EnsurethattheIUTinthecallstateU03(sc)andintheCC-Wait-Ackstate,receivingaCONNECT(sc)messagecontainingintheFacilityIEaccbsRequestreturnresultAPDU,sendsaCONNECTACKNOWLEDGE(sc)message,entersthecallstateU10(sc)andenterstheCC-Invoked-User-A-RETstate.CC_Orig01_003subclause6.5.2.1.1EnsurethattheIUTinthecallstateU03(sc)andintheCC-Wait-Ackstate,receivingaRELEASE(sc)messagecontainingintheFacilityIEaccbsRequestreturnresultAPDU,sendsaRELEASECOMPLETE(sc)messageandentersthecallstateU00(sc)andtheCC-Invoked-User-A-RLSstate.Selection:SupportofPathreservationmethodapplies,PICS:A8.CC_Orig01_004subclause6.5.2.2.1EnsurethattheIUTinthecallstateU03(sc)andintheCC-Wait-Ackstate,receivingaRELEASE(sc)messagecontainingintheFacilityIEaccbsRequestreturnerrorAPDU,sendsaRELEASECOMPLETE(sc)messageandentersthecallstateU00(sc)andtheCC-Idlestate.Selection:SupportofPathreservationmethodapplies,PICS:A8.CC_Orig01_005subclause6.5.2.2.1EnsurethattheIUTinthecallstateU03(sc)andintheCC-Wait-Ackstate,receivingaRELEASE(sc)messagecontainingintheFacilityIEaccbsRequestrejectAPDU,sendsaRELEASECOMPLETE(sc)messageandentersthecallstateU00(sc)andtheCC-Idlestate.Selection:SupportofPathreservationmethodapplies,PICS:A8.CC_Orig01_006subclauses6.5.2.2.1,6.5.2.1.10EnsurethattheIUTinthecallstateU03(sc)andintheCC-Wait-Ackstate,receivingaRELEASE(sc)messageforCR1containingintheFacilityIEaccbsRequestreturnresultAPDU,althoughtheconnectionretentionmethodisrequired,sendsaSETUP(sc)messageforCR2containingintheFacilityIEaccCancelinvokeAPDUincludingtheArgumentfullArgwiththesamebasiccallinformationaspreviouslysentintheccbsRequestinvokeAPDU,inordertoidentifytheCCrequesttobecancelledandenterstheCC-Idlestate.SIST EN 301 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)125.2.1.1.2CCNRinvocationCC_Orig02_001subclause6.5.2.1.2EnsurethattheIUTinthecallstateU00(sc)andintheCC-Idlestate,inordertoinitiateaCCNRcall,sendsaSETUP(sc)messagecontainingintheFacilityIEaccnrRequestinvokeAPDUandenterstheCC-Wait-Ackstate.CC_Orig02_002subclause6.5.2.1.2EnsurethattheIUTinthecallstateU03(sc)andintheCC-Wait-Ackstate,receivingaCONNECT(sc)messagecontainingintheFacilityIEaccnrRequestreturnresultAPDU,sendsaCONNECTACKNOWLEDGE(sc)message,entersthecallstateU10(sc)andenterstheCC-Invoked-User-A-RETstate.CC_Orig02_003subclause6.5.2.1.2EnsurethattheIUTinthecallstateU03(sc)andintheCC-Wait-Ackstate,receivingaRELEASE(sc)messagecontainingintheFacilityIEaccnrRequestreturnresultAPDU,sendsaRELEASECOMPLETE(sc)messageandentersthecallstateU00(sc)andtheCC-Invoked-User-A-RLSstate.Selection:SupportofPathreservationmethodapplies,PICS:A8.CC_Orig02_004subclause6.5.2.2.1EnsurethattheIUTinthecallstateU03(sc)andintheCC-Wait-Ackstate,receivingaRELEASE(sc)messagecontainingintheFacilityIEaccnrRequestreturnerrorAPDU,sendsaRELEASECOMPLETE(sc)messageandentersthecallstateU00(sc)andtheCC-Idlestate.Selection:SupportofPathreservationmethodapplies,PICS:A8.CC_Orig02_005subclause6.5.2.2.1EnsurethattheIUTinthecallstateU03(sc)andintheCC-Wait-Ackstate,receivingaRELEASE(sc)messagecontainingintheFacilityIEaccnrRequestrejectAPDU,sendsaRELEASECOMPLETE(sc)messageandentersthecallstateU00(sc)andtheCC-Idlestate.Selection:SupportofPathreservationmethodapplies,PICS:A8.CC_Orig02_006subclauses6.5.2.2.1,6.5.2.1.10EnsurethattheIUTinthecallstateU03(sc)andintheCC-Wait-Ackstate,receivingaRELEASE(sc)messageforCR1containingintheFacilityIEaccnrRequestreturnresultAPDU,althoughtheconnectionretentionmethodisrequired,sendsaSETUP(sc)messageforCR2containingintheFacilityIEaccCancelinvokeAPDUincludingtheArgumentfullArgwiththesamebasiccallinformationaspreviouslysentintheccnrRequestinvokeAPDU,inordertoidentifytheCCrequesttobecancelledandenterstheCC-Idlestate.SIST EN 301 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)135.2.1.1.3UserAnotbusy-pathnon-reservationmethodCC_Orig03_001subclauses6.5.2.1.4,6.5.2.1.5EnsurethattheIUTinthecallstateU10(sc)andintheCC-Invoked-User-A-RETstate(connectionretentioncase),receivingaFACILITY(sc)messagecontainingintheFacilityIEaccExecPossibleinvokeAPDUandUserAisnotbusy,entersstateCC-Wait-User-A-Answer-N,sendsaSETUPmessageforCR2containingintheFacilityIEaccRingoutinvokeAPDUandenterstheCC-Ringoutstate.CC_Orig03_002subclause6.5.2.1.5EnsurethattheIUTinthecallstateU03andintheCC-Ringoutstate,receivinganALERTINGmessage,entersthecallstateU04andtheCC-IdlestateandwaitsforaCONNECTmessage.CC_Orig03_003subclause6.5.2.1.5EnsurethattheIUTinthecallstateU03andintheCC-Ringoutstate,receivingaCONNECTmessage,sendsaCONNECTACKNOWLEDGEmessageandentersthecallstateU10andtheCC-Idlestate.CC_Orig03_004subclause6.5.2.2.6EnsurethattheIUTinthecallstateU03andintheCC-Ringoutstate,receivingaDISCONNECTmessagecontainingintheFacilityIEaccRingoutreturnerrorAPDUwithvalue"remoteUserBusyAgain"andtheserviceretentionmethodappliesforthatCCRequest,sendsaRELEASEmessageandenterstheCC-Invoked-User-A-RETstate(connectionretentioncase).Selection:Serviceretentionmethodapplies,PICS:A9.CC_Orig03_005subclause6.5.2.2.6EnsurethattheIUTinthecallstateU03andintheCC-Ringoutstate,receivingaDISCONNECTmessageforcontainingintheFacilityIEaccRingoutreturnerrorAPDUwithvalue"remoteUserBusyAgain"whentheserviceretentionmethoddoesnotapplyforthatCCRequestandnore-invocationisselected,sendsaRELEASEmessageandenterstheCC-Idlestate.Selection:FailureindicationtoUserA(nore-invocation),PICS:B13.CC_Orig03_006subclause6.5.2.2.6EnsurethattheIUTinthecallstateU03andintheCC-Ringoutstate,receivingaDISCONNECTmessagecontainingintheFacilityIEaccRingoutreturnerrorAPDUwithvalue"remoteUserBusyAgain"whentheserviceretentionmethoddoesnotapplyforthatCCRequestandre-invocationisselected,sendsaSETUP(sc)messagecontainingintheFacilityIEaccbsRequestinvokeAPDU,enterscallstateU01andtheCC-Wait-Ackstate.Selection:Re-invocation,PICS:B14.CC_Orig03_007subclause6.5.2.2.6EnsurethattheIUTinthecallstateU03andintheCC-Ringoutstate,receivingaDISCONNECTmessagecontainingintheFacilityIEaccRingoutreturnerrorAPDUwithvalue"failureToMatch"andacallindependentsignallingconnectionexists,sendsaRELEASEmessageenterstheCC-Idlestate.SIST EN 301 452-1 V1.1.4:2005



ETSIETSIEN301452-1V1.1.4(2000-09)14CC_Orig03_008subclause6.5.2.2.6EnsurethattheIUTinthecallstateU03andintheCC-Ringoutstate,receivingaDISCONNECTmessagecontainingintheFacilityIEaccRingoutreturnerrorAPDUwithvalue"unspecified"andacallindependentsignallingconnectionexists,sendsaRELEASEmessageenterstheCC-Idlestate.CC_Orig03_009subclauses6.5.2.2.6,6.5.2.1.10EnsurethattheIUTinthecallstateU10(sc)andintheCC-Ringoutstate,getsaBCindicationthattheCCCallfailed-withoutccRingoutreturnerrorbeingreceivedandacallindependentsignallingconnectionexists,sendsaRELEASE(sc)messagecontainingintheFacilityIEaccCancelinvokeAPDUandenterstheCC-Idlestate.5.2.1.1.4UserAnotbusy-pathreservationmethodGroupselection:SupportofPathreservationmethodapplies,PICS:A8andSetupCCcallwithpathreservationapplies,PICS:B7.CC_Orig04_001subclauses6.5.2.1.4,6.5.2.1.6EnsurethattheIUTinthecallstatesU00andU00(sc)andinstateCC-Invoked-User-A-RLS(connectionreleasecase),receivingaSETUP(sc)messagecontainingintheFacilityIEaccExecPossibleinvokeAPDUandtheassociationoftheAPDUwithanexistingCCRequestissuccessfulandUserAisnotbusy,sendsaRELEASE(sc)messagewithcausevalue#16"normalcallclearing",sendsaSETUPmessageforCR2containingintheFacilityIEaccPathReserveinvokeAPDUandenterstheCC-Path-Setupstate.CC_Orig04_002subclauses6.5.2.1.4,6.5.2.1.6EnsurethattheIUTinthecallstatesU00andU10(sc)andintheCC-Invoked-User-A-RETstate(connectionretentioncase),receivingaFACILITY(sc)messagecontainingintheFacilityIEaccExecPossibleinvokeAPDUandtheserviceretentionmethoddoesnotapply(i.e.:thecallindependentsignallingconnectioncanbereleased),sendsaRELEASE(sc)messagewithcausevalue#16"normalcallclearing",sendsaSETUPmessageforCR2containingintheFacilityIEaccPathReserveinvokeAPDUandenterstheCC-Path-Setupstate.CC_Orig04_003subclauses6.5.2.1.4,6.5.2.1.6EnsurethattheIUTinthecallstatesU00andU10(sc)andintheCC-Invoked-User-A-RETstate(connectionretentioncase),receivingaFACILITY(sc)messagec
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.