SIST EN 301 452-1 V1.1.4:2005

• Abstract:

  TSS&TP for Call completion services. Supporting members: BT, Ericsson, Viag Interkom, Cegetel.

• 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 452-1 V1.1.4 (2000-09) - 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

SIST EN 301 452-1 V1.1.4:2005 is the SIST publication of the ETSI European Standard EN 301 452-1 Version 1.1.4. It defines the Test Suite Structure and Test Purposes (TSS&TP) for the Call completion supplementary service in the Private Integrated Services Network (PISN) inter-exchange signalling protocol at the VPN "b" service entry point. In practice, it is used to build conformance tests for implementations that need to follow the Call completion procedures in ETS 300 366.

What does SIST EN 301 452-1 V1.1.4:2005 specify?

SIST EN 301 452-1 V1.1.4:2005 specifies the TSS&TP for Call completion supplementary services in PISN. The document is written for conformance testing and is limited to VPN scenarios at the "b" service entry point.

The standard says its test purposes are based on ETS 300 366 and on the ISO/IEC 9646 testing framework. It also states that interworking with public ISDNs is outside the scope of the "b" service entry point.

The document is organized into these main parts:

• Scope
• References
• Definitions and abbreviations
• Test Suite Structure (TSS)
• Test Purposes (TP)
• Compliance
• Requirements for a comprehensive testing service
• Bibliography

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

The core of SIST EN 301 452-1 V1.1.4:2005 is in Clause 5, which turns the service procedures into named test purposes. The TP naming convention, TP structure, and test strategy matter because they show how test cases are selected and how results are traced back to the service behavior.

Test purposes are structured and traceable

Clause 5.1.1 defines a naming scheme for each TP, and Clause 5.1.3 gives a fixed TP structure. In practice, this helps test developers keep test cases readable and consistent across suites.

Clause 5.1.4 says the TPs are derived from the base standard and the PICS proforma, and they focus on externally observable behavior. That means the tests are meant to check what the implementation actually sends, receives, and changes in state.

The tests are grouped by service behavior

Clause 4 organizes the TSS into procedures at the originating PINX, terminating PINX, and protocol interactions. This grouping matters because it separates the tests by the side of the VPN "b" interface and by the kind of behavior being exercised.

Originating PINX behavior is covered in detail

Clause 5.2.1.1 covers CCBS and CCNR invocation, not-busy and busy cases, cancellation, and timer expiry. In practice, these test purposes verify that the originating side sets up, retains, cancels, or clears the call correctly when User A is busy or becomes free.

The timer cases for T1 to T4 are important because they check timeout handling. For a test lab, that means the implementation must react properly when waiting too long for acknowledgements, completion, or path setup.

Terminating PINX behavior is also tested

Clause 5.2.1.2 checks how the terminating PINX handles CCBS and CCNR requests, including acceptance, rejection, and the indication that User B is not busy. It also covers call completion with and without path reservation.

The same clause includes suspension, resumption, and cancellation. This matters because the implementation must manage the service state when User B changes from busy to free, or when the request is withdrawn.

Interactions with other services are limited but explicit

Clauses 5.2.3 and 5.2.4 cover protocol interaction with other supplementary services and ANFs when the call is diverted to a user. The test purposes use the nominatedNr from diverting leg information and check that the correct party number is carried into the CCBS or CCNR request.

Compliance is tied to the test purposes and PICS

Clause 6 says a compliant ATS must match the TPs, use an appropriate subset of the TSS, follow the same naming conventions, preserve the PICS selection links, and comply with ISO/IEC 9646-2. In practice, that means a test suite is compliant only if its cases can be traced back to the defined TP set and selection rules.

Clause 7 says any organization claiming a comprehensive testing service shall use the Remote test method from ISO/IEC 9646-2 as a minimum.

What terms does SIST EN 301 452-1 V1.1.4:2005 define?

• Abstract Test Suite (ATS) - A structured set of abstract test cases used to check conformance.
• Implementation Under Test (IUT) - The implementation being exercised by the conformance tests.
• Protocol Implementation Conformance Statement (PICS) - The statement used to select which test purposes apply to a given implementation.
• Protocol Implementation eXtra Information for Testing (PIXIT) - Additional implementation information needed to run or adapt the tests.
• CCBS - Call Completion to Busy Subscriber, the service for a busy called user.
• CCNR - Call Completion on No Reply, the service for a called user that does not answer.
• PINX - Private Integrated Services Network exchange, the network node at the PISN interface.

Who uses SIST EN 301 452-1 V1.1.4:2005?

SIST EN 301 452-1 V1.1.4:2005 is used by test laboratories, protocol engineers, equipment vendors, and quality teams working on PISN and VPN "b" service entry point implementations. It is also relevant to buyers or evaluators who need evidence that a product can be tested against the Call completion procedures defined for inter-exchange signalling.

The document supports people who write ATS test cases, interpret PICS data, or verify message flows for CCBS and CCNR. It is especially useful where conformance testing, interoperability checking, and TTCN-based test design are part of acceptance or certification work.

Which standards are used with SIST EN 301 452-1 V1.1.4:2005?

• ETS 300 366 - The base Call completion supplementary services specification; the test purposes are derived from its procedures.
• ISO/IEC 9646-1, -2, -3 - The conformance testing framework, abstract test suite methodology, and TTCN notation used as the test basis.
• ETS 300 406 - The testing and specification methodology used to shape the test strategy.
• EN 300 172 and ETS 300 239 - Provide related PISN and supplementary-service definitions used in the document’s terminology.
• ITU-T Recommendation I.112 and I.210 - Provide ISDN vocabulary and service concepts used in the definitions.
• EN 301 060-1 and ETR 172 - Define the VPN "b" service entry point and its context.
• ETS 300 196-1 - Provides the generic functional protocol for supporting supplementary services.
• ETSI EN 301 452-2 - The companion part identified in the foreword, covering the ATS and PIXIT proforma.

What does the SIST EN 301 452-1 V1.1.4:2005 document contain?

The document contains the TSS, TP naming rules, a TP structure template, and a large set of numbered test purposes for originating and terminating PINX behavior. It also includes state mappings between user-side and network-side call states, which helps testers map a scenario to the right implementation state.

Clause 5 gives the detailed message sequences, APDU handling, and state transitions for CCBS, CCNR, cancellation, suspension, resumption, and timer expiry. Clause 6 turns those test purposes into compliance rules for ATS design, and Clause 7 states the minimum test method for a comprehensive testing service.

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
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.:[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 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)messagecontainingintheFacilityIEaccExecPossibleinvokeAPDUandtheserviceretentionmethodapplies(i.e.:thecallindependentsignallingconnectioncannotbereleased),sendsaSETUPmessageforCR2containingintheFacilityIEaccPathReserveinvokeAPDUandenterstheCC-Path-Setupstate.Selection:Serviceretentionmethodapplies,PICS:A9.CC_Orig04_004subclauses6.5.2.1.6,6.5.2.1.8,6.5.2.1.9EnsurethattheIUTinthecallstateU00andinstateCC-Wait-User-A-Free,onreceiptoftheindicationthatUserAisnotbusy,sendsaSETUPmessageforCR2containingintheFacilityIEaccPathReserveinvokeAPDUandenterstheCC-Path-Setupstate.SIST EN 301 452-1 V1.1.4:2005

ETSIETSIEN301452-1V1.1.4(2000-09)15CC_Orig04_005subclause6.5.2.1.6EnsurethattheIUTinthecallstateU03andintheCC-Path-Setupstate,receivingaPROGRESSmessagecontainingintheFacilityIEaccPathReservereturnresultAPDU,sendsaFACILITYmessagecontainingintheFacilityIEaccRingoutinvokeAPDU,remaininthesamecallstateandenterstheCC-Ringoutstate.CC_Orig04_006subclause6.5.2.2.2EnsurethattheIUTinthecallstateU00(sc)andinstateCC-Invoked-User-A-RLS,receivingaSETUP(sc)messagecontainingintheFacilityIEaccExecPossibleinvokeAPDUandtheassociationoftheAPDU,withaCCRequestthatisinstateCC-Invoked-User-A-RLS,isunsuccessful,sendsaRELEASE(sc)messagewithcausevalue#16"normalcallclearing"andcontainingintheFacilityIEaccCancelinvokeAPDU.CC_Orig04_007subclause6.5.2.2.5EnsurethattheIUTinthecallstateU03andintheCC-Path-Setupstate,receivingaDISCONNECTmessageforcontainingintheFacilityIEaccPathReservereturnerrorAPDUwithvalue"failedDueToInterworking",sendsaRELEASEmessagefor,sendsaSETUPmessageforCR3containingintheFacilityIEaccRingoutinvokeAPDUandenterscallstateU01andtheCC-Ringoutstate.Selection:NewPICSforretryCCCallwithoutPathReservation:B15.CC_Orig04_008subclause6.5.2.2.5EnsurethattheIUTinthecallstateU03andintheCC-Path-Setupstate,receivingaDISCONNECTmessageforcontainingintheFacilityIEaccPathReservereturnerrorAPDUwithvalue"failedDueToInterworking",sendsaRELEASEmessageforCR,sendsaSETUPmessageforCR3containingintheFacilityIEaccPathReserveinvokeAPDUandremainsintheCC-Path-Setupstate.Selection:SetupCCcallwithpathreservation,PICS:B7andnewPICSforretryPathReservationonanotherroute:B16.CC_Orig04_009subclause6.5.2.2.5EnsurethattheIUTinthecallstateU03andintheCC-Path-Setupstate,receivingaDISCONNECTmessageforcontainingintheFacilityIEaccPathReservereturnerrorAPDUwithvalue"failedDueToInterworking,sendsaREL
...