SIST EN 301 005-3:2001
(Main)V interfaces at the digital Service Node (SN); Interfaces at the VB5.1 reference point for the support of broadband or combined narrowband and broadband Access Networks (ANs); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification
- Abstract
TSS&TP for DE/SPS-03046-1.
- Status
- Published
- Publication Date
- 31-Aug-2001
- Technical Committee
- SPS - Signalling protocols and switching
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Sep-2001
- Due Date
- 01-Sep-2001
- Completion Date
- 01-Sep-2001
- Mandate
- M/213
SIST EN 301 005-3:2001 is the Slovenian adoption of ETSI EN 301 005-3 V1.1.2 for the VB5.1 reference point. It specifies the Test Suite Structure and Test Purposes (TSS&TP) for checking conformance of interfaces at the digital Service Node (SN) between an Access Network (AN) and an SN.
What does SIST EN 301 005-3:2001 specify?
SIST EN 301 005-3:2001 specifies how conformance tests for the VB5.1 Real Time Management Co-ordination (RTMC) protocol are structured and what each test purpose checks. It is written for implementations where the AN or the SN is the Implementation Under Test (IUT), and it provides the basis for the Message Sequence Charts (MSCs) used to document each test scenario.
The document is organized into scope, references, definitions and abbreviations, test suite structure, test purpose description and naming, and test purpose definitions. It also has two informative annexes.
| Annex | What it covers |
|---|---|
| Annex A | PIXIT parameters and the informative values used in the MSCs |
| Annex B | Test methods, including the abstract test method for the RTMC protocol |
What are the key requirements of SIST EN 301 005-3:2001?
SIST EN 301 005-3:2001 is mainly a test specification, so its key content is the way test cases are built and selected, not product requirements. The practical value is that it tells a test lab how to set up, name, run, and interpret conformance tests for VB5.1 RTMC behavior.
Test suite structure and naming
Clause 4 structures the test suite by RTMC procedures and then by test category. The document gives separate trees for when the AN is the IUT and when the SN is the IUT, so each side is tested against the same protocol in its own role.
Clause 5.2 defines the test purpose name format VB5_<i>_<IUT>_<pp>_<cc>_<nn>. This matters because the name itself encodes the interface, whether the AN or SN is under test, the procedure, the category, and the sequence number.
How each test purpose is described
Clause 5.1 says each test purpose is given in a table followed by an MSC. The table captures the reference, purpose, test description, pass criteria, selection, preamble, postamble, and any additional testing, so a reader can see both why the case exists and what must happen on the interface.
Startup, selection, and setup
Clause 5.3 uses startup preambles to bring the IUT from power-on to the state needed for testing. Separate startup procedures are given for AN and SN, which matters in practice because the equipment under test may need different initial conditions depending on which side is being exercised.
Test selection is driven by PICS statements from EN 301 005-2, and one consistency-check branch also depends on the PIXIT parameter PIX_automatic_loopback_results. This means a test campaign has to be matched to the implementation options and to whether loopback results are reported automatically or by tester action.
Core RTMC procedures covered
Clause 6 covers the main RTMC procedures for both AN and SN as IUT:
- basic capability and startup behavior
- blocking and unblocking of resources
- shutdown behavior
- VPCI consistency check
- verify LSPId
- reset Logical Service Port (LSP)
- reset Virtual Path Connection (VPC)
- common error handling
In practice, these cases check single resources, lists of resources, and ranges of VPCIs, and they distinguish valid, unknown, and timeout behavior. That is important because the same protocol must work for normal control, partial resource sets, and error recovery.
Error handling
Clause 6.1.12 checks message-header and information-element errors such as invalid protocol discriminator, transaction identifier format, message length, wrong message type, and missing mandatory IE. The expected behavior is either to ignore the bad PDU or to return PROTOCOL_ERROR with the appropriate cause, which is how the standard checks robust protocol handling without reproducing invalid traffic.
What terms does SIST EN 301 005-3:2001 define?
- Abstract Test Suite (ATS) - A formal set of test cases derived from the protocol specification for conformance testing.
- Implementation Under Test (IUT) - The implementation being exercised by the test case.
- System Under Test (SUT) - The wider system containing the IUT.
- Protocol Implementation Conformance Statement (PICS) - The statement of implementation options used to select applicable tests.
- Access Network (AN) - The access-side network connected to the Service Node at the VB5.1 reference point.
- Service Node (SN) - The node on the service side of the VB5.1 reference point.
- Virtual Path Connection (VPC) - The ATM connection object used throughout the blocking, unblocking, shutdown, and reset tests.
- Logical Service Port (LSP) - The logical port identifier used in the verify and reset procedures.
Who uses SIST EN 301 005-3:2001?
SIST EN 301 005-3:2001 is used by conformance test laboratories, equipment manufacturers, and protocol implementers working on VB5.1 AN and SN interfaces. Quality teams and buyers can also use it to see which protocol behaviors are covered before asking for test evidence or certification results.
Which standards are used with SIST EN 301 005-3:2001?
- EN 301 005-1 - Provides the interface specification whose requirements the test purposes check.
- EN 301 005-2 - Provides the PICS proforma used to select the applicable test cases.
- ISO/IEC 9646-1 - Supplies the general conformance testing concepts and framework.
- ISO/IEC 9646-2 - Supplies the abstract test suite specification method used here.
- ITU-T Recommendation G.902 - Gives the framework for functional access networks and the AN/SN context.
- ITU-T Recommendation M.3010 - Provides the Q3 management interface reference point mentioned in the document.
- EN 301 217-1 - Provides the VB5.2 reference point context used for comparison.
What does the SIST EN 301 005-3:2001 document contain?
The document contains structured test-purpose tables and MSCs for each RTMC test case. It also includes startup procedures, naming rules, and separate test sets for AN and SN as IUT.
Annex A gives the PIXIT parameter table and the values used in the MSCs. Annex B describes the test methods and the abstract test method for the RTMC protocol.
For readers running tests, the useful content is the combination of case selection rules, message sequences, pass criteria, and the way valid, invalid, and timeout behaviors are exercised.
Get Certified
Connect with accredited certification bodies for this standard
BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.
NYCE
Mexican standards and certification body.
Sponsored listings
Frequently Asked Questions
SIST EN 301 005-3:2001 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "V interfaces at the digital Service Node (SN); Interfaces at the VB5.1 reference point for the support of broadband or combined narrowband and broadband Access Networks (ANs); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification". This standard covers: TSS&TP for DE/SPS-03046-1.
TSS&TP for DE/SPS-03046-1.
SIST EN 301 005-3:2001 is classified under the following ICS (International Classification for Standards) categories: 35.200 - Interface and interconnection equipment. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 301 005-3:2001 is associated with the following European legislation: Standardization Mandates: M/213. 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 005-3:2001 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.LQV interfaces at the digital Service Node (SN); Interfaces at the VB5.1 reference point for the support of broadband or combined narrowband and broadband Access Networks (ANs); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification35.200Vmesniška in povezovalna opremaInterface and interconnection equipmentICS:Ta slovenski standard je istoveten z:EN 301 005-3 Version 1.1.2SIST EN 301 005-3:2001en01-september-2001SIST EN 301 005-3:2001SLOVENSKI
STANDARD
ETSIEN301005-3V1.1.2(2000-05)EuropeanStandard(Telecommunicationsseries)VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.1referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part3:TestSuiteStructureandTestPurposes(TSS&TP)specificationSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)2ReferenceDEN/SPS-09046-3KeywordsAN,B-ISDN,ISDN,SN,TSS&TP,PSTN,Vinterface,V5interface,VB5interfaceETSI650RoutedesLuciolesF-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 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)3ContentsIntellectualPropertyRights.5Foreword.5Introduction.51Scope.72References.73Definitionsandabbreviations.73.1Definitions.73.2Abbreviations.84TestSuiteStructure.95TestPurposesdescriptionandnaming.125.1MethodusedforthedescriptionoftheTPs.125.2Testpurposenamingconvention.125.3Preamblesandpostambles.135.3.1Preambledescriptions.135.3.1.1ANistheIUT.135.3.1.2SNistheIUT.175.3.2Postambledescriptions.206TestPurposesdefinitions.216.1ANistheIUT.216.1.1Basiccapabilitytests(CA).216.1.2Blockingresourceprocedure(BR).246.1.3Unblockingresourceprocedure(UR).366.1.4Shutdownresourceprocedure(SR).406.1.5VPCIconsistencycheckprocedure(CC).486.1.6VerifylogicalserviceportId(LSPId)procedure,SNinitiated(VLS).636.1.7VerifylogicalserviceportId(LSPId)procedure,ANinitiated(VLA).636.1.8ResetLogicalServicePort(LSP)procedure,SNinitiated(RLS).656.1.9ResetLogicalServicePort(LSP)procedure,ANinitiated(RLA).676.1.10ResetVirtualPathConnection(VPC)procedure,SNinitiated(RVS).696.1.11ResetVirtualPathConnection(VPC)procedure,ANinitiated(RVA).766.1.12CommonErrorHandling(CEH)procedure.806.1.12.1ErrorHandlingonMessageHeader.806.1.12.2ErrorHandlingonInformationElement(IE).876.2SNistheIUT.886.2.1Basiccapabilitytests(CA).886.2.2Blockingresourceprocedure(BR).916.2.3Unblockingresourceprocedure(UR).1026.2.4Shutdownresourceprocedure(SR).1086.2.5VPCIconsistencycheckprocedure(CC).1216.2.6VerifylogicalserviceportId(LSPId)procedure,SNinitiated(VLS).1286.2.7VerifylogicalserviceportId(LSPId)procedure,ANinitiated(VLA).1306.2.8ResetLogicalServicePort(LSP)procedure,SNinitiated(RLS).1316.2.9ResetLogicalServicePort(LSP)procedure,ANinitiated(RLA).1346.2.10ResetVirtualPathConnection(VPC)procedure,SNinitiated(RVS).1366.2.11ResetVirtualPathConnection(VPC)procedure,ANinitiated(RVA).1406.2.12CommonErrorHandling(CEH)procedure.1446.2.12.1ErrorHandlingonMessageHeader.1446.2.12.2ErrorHandlingonInformationElement(IE).150SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)4AnnexA(informative):PIXITparametersandtheinformativevaluesused.151A.1ParametervaluesasusedintheMSCs.151AnnexB(informative):Testmethods.153B.1AbstracttestmethodfortheRTMCprotocol.153B.2Scopeoftestpurposesandadditionaltesting.153Bibliography.155History.156SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)5IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinSR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinSR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeSignallingProtocolsandSwitching(SPS).Thepresentdocumentispart3ofamulti-partENcoveringtheVinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.1referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs)asidentifiedbelow:Part1:"Interfacespecification";Part2:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part3:"TestSuiteStructureandTestPurposes(TSS&TP)specification";Part4:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecification".NationaltranspositiondatesDateofadoptionofthisEN:28April2000DateoflatestannouncementofthisEN(doa):31July2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31January2001DateofwithdrawalofanyconflictingNationalStandard(dow):31January2001IntroductionGeneralTheworkonanewbroadbandVBreferencepointconceptwasinitiatedbyETSITechnicalCommitteeSPStoconsiderpossiblenewstructuresandreferencepointsfortheconnectionofnewbroadbandandcombinednarrowband/broadbandaccessarrangementstoServiceNodes(SN),inco-operationwithotherTCs.TheVB5referencepointconcept,basedonITU-TRecommendationG.902[5],wassplitintotwovariants.ThefirstvariantbasedonanATMcross-connectwithprovisionedconnectivity,calledtheVB5.1referencepoint,isdescribedinthepresentdocument.Theothervariantwhichfurtherenableson-demandconnectivitywithintheAN,calledtheVB5.2referencepoint,iscoveredbyEN301217-1[7].SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)6RelationshipbetweentheVB5.1andVB5.2referencepointconceptsVB5.2extendsthecapabilitiesattheVB5.1referencepointtoincludeon-demandconnectivityintheANunderthecontrolofSN.ThemajorcommonfeaturesbetweentheVB5.1andVB5.2interfacesare:-bothVB5interfacessupportB-ISDNaswellasnarrowbandandothernon-B-ISDNcustomeraccesstypes;-bothVB5interfacessupportATMmultiplexing/cross-connectingintheANattheVPand/orVClevel.ItisanticipatedthattheRealTimeManagementCo-ordination(RTMC)protocolfortheVB5.1referencepointwillbeasubsetoftheRTMCprotocolfortheVB5.2referencepoint.SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)71ScopeThepresentdocumentspecifiestheTestSuiteStructureandTestPurposes(TSS&TP)andanexampleoftestarchitecturefortestingtheconformityofanimplementationtothespecificationofinterfacesattheVB5.1referencepointbetweenanAccessNetwork(AN)andaServiceNode(SN).ThetestarchitectureproposedhereisusedforthedesignoftheMessageSequenceCharts(MSCs)producedastestpurposedocumentation.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN301005-1(V1.1):"VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.1referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part1:Interfacespecification".[2]ETSIEN301005-2(V1.1):"VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.1referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[3]ISO/IEC9646-1:"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[4]ISO/IEC9646-2:"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part2:Abstracttestsuitespecification".[5]ITU-TRecommendationG.902:"FrameworkRecommendationonfunctionalaccessnetworks(AN)-Architectureandfunctions,accesstypes,managementandservicenodeaspects".[6]ITU-TRecommendationM.3010:"PrinciplesforaTelecommunicationsmanagementnetwork".[7]ETSIEN301217-1:"VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.2referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part1:Interfacespecification".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingdefinitionsapply:-termsdefinedinEN301005-1[1];-termsdefinedinISO/IEC9646-1[3]andinISO/IEC9646-2[4].SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)8Inparticular,thefollowingtermsdefinedinISO/IEC9646-1[3]apply:-AbstractTestSuite(ATS);-ImplementationUnderTest(IUT);-SystemUnderTest(SUT);-ProtocolImplementationConformanceStatement(PICS).3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:AALATMAdaptationLayerAAL-SAPAAL-ServiceAccessPointANAccessNetworkATMAsynchronousTransferModeB-ISDNBroadbandISDNB-ISUPBroadbandISDNSignallingUserPartB-UNIBroadbandUNIBABasic(rate)AccessCPECustomerPremisesEquipmentCPNCustomerPremisesNetworkETEquipmentTerminalFSMFiniteStateMachineIDIdentityIEInformationElementINIInter-NetworkInterfaceISDNIntegratedServicesDigitalNetworkLANLocalAreaNetworkLELocalExchangeLMELayerManagementEntityLMILocalManagementInterfaceLSPLogicalServicePortLUPLogicalUserPortMIBManagementInformationBaseMSCMessageSequenceChartN-ISDNNarrowbandISDNNNINetwork-to-NetworkInterfaceOAMOperationsAdministrationandMaintenancePDHPlesiochronousDigitalHierarchyPDUProtocolDataUnitsPSPPhysicalServicePortPSTNPublicSwitchedTelephoneNetworkPUPPhysicalUserPortQ3"Q"managementinterfacereferencepointasITU-TRecommendationM.3010[6]RTMCRealTimeManagementCo-ordinationSAALSignallingATMAdaptationLayerSAPServiceAccessPointSARSegmentationandReassemblySDHSynchronousDigitalHierarchySDLSpecificationandDescriptionLanguageSDUServiceDataUnitsSNServiceNodeSNIServiceNodeInterfaceSPServicePortSPSSignallingProtocolsandSwitchingSSCFServiceSpecificCo-ordinationFunctionSSCOPServiceSpecificConnectionOrientedProtocolTCTechnicalCommitteesSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)9TETerminalEquipmentTMNTelecommunicationsManagementNetworkTPTransmissionPathUNIUser-NetworkInterfaceVBBroadband"V"referencepointVCVirtualChannel(ATM)VCEVirtualChannelEntityVPVirtualPathVPCVPConnectionVPCIVPConnectionIdentifierVPCI-CCVPConnectionIdentifier-ConsistencyCheckVPIVPIdentifierVPLVPLink4TestSuiteStructureFigure1showsthestructureoftheV5.1RTMCtestsuitewhentheANistheIUT.Figure2showsthestructureoftheV5.1RTMCtestsuitewhentheSNistheIUT.ThefirstlevelisstructuredaccordingtotheRTMCprocedures.Thesecondlevelisstructuredaccordingtotestcategory.Themeaningofthecodesinthetreeisgiveninsubclause5.2.SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)10VB5_RTMCANSTCABVBRTIBVURTIBVSRTIBVCCTIBOVLSBVVLABVTIBVRLSBIBVRLATIBVRVSBIBVRVATICEHBIFigure1:VB5RTMCANTSSSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)11VB5_RTMCSNSTCABVBRBIBVURBIBVSRBITIBVCCBITIBVVLSBITIVLABVBVRLSBITIBVRLABIBVRVSTIBVRVABICEHBIFigure2:VB5RTMCSNTSSSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)12Invalidbehaviourofthetestercomprises:referencetounknownresources,unknownmessagetype,errorsincommonmessagefields(protocoldiscriminator,transactionidentifier,messagelength).RTMCtimertestsandinopportunebehaviourtestsarerelatedtoanumberofspecificRTMCproceduresandthetestsuitehasbeenstructuredaccordingly.5TestPurposesdescriptionandnaming5.1MethodusedforthedescriptionoftheTPsEachTPisdescribedusingtextualinformationpresentedinatable.ThistableisfollowedbyanMSCrepresentingthetestscenario.ThetabledescribingeachTPisasfollows:TP-Nameisauniqueidentifier,createdaccordingtotheTPnamingconventions(alsothenameofthecorrespondingtestcase)ReferencetotheparagraphnumberofspecificationEN301005-1[1]statingtheconformancerequirementPurposePurposeofthetestperformedagainstarequirementoftheprotocol.TestdescriptionInformationonthetestbody,describingactionsandparametersPasscriteriaVisibleactiontobeobservedatPCOtodeclarethattheIUTpassesthetestandconformstothespecificationsSelection"None"orexpressionbasedonEN301005-2[2]PICSstatements,usedtoselectordeselectthecorrespondingtestcaseaccordingtotheoptionsoftheimplementation.Preamble"None"ornameofthepreambleprocedurebringingtheIUTfromidlestatetothestaterequiredtorunthetest.Postamble"None"ornameofthepostambletobringtheIUTbacktoidlestate.AdditionaltestingAdditionalinformation,presentinspecification,forpossibleinformaltestingbeyondRTMCprotocol(forinstance,iftesteriscapableofobservation/actionviaadditionalinterfacelikeQ3orsignallinginterfaces)AnMSCfollowseachTPtabulateddescription.TheMSCisproducedbyexercisingtheSDLmodel,wheneverpossible,i.e.eachtimethefunctionorprocedureismodelled.TheseMSCsarethenvalidatedandareverifiedinaccordancewiththespecification.Iftheprocedureisnotmodelled,thenthecorrespondingMSCisdrawnmanuallyandcannotbevalidated.ThecolumnsidentifiedintheMSCrepresent,fromlefttoright,theIUTenvironment,thetester,thelowerlayerinterfacerelevantonlywhenstartingthetestitself,andtheIUT.AsanMSCisfocusingonthebodyofthetest,thepreambleisrepresentedbyasinglelineintheMSC.EachfollowinglinerepresentsanexchangeofPDUattheVB5interface,andshowsthemodelledparametersmostrelevantforagiventestpurpose.Thevaluesoftheseparametersareeithermandatoryandimposedbythespecifications,ortheyareinformativeonlyandchosenarbitrarilyinrangescompatiblewiththespecifications.Thelistoftheinformativeparameters,forwhichavalueistobeassignedbytheimplementeroftheIUTfortheexecutionofatestsuite,isincludedinthePIXITproformaoftheRTMCprotocol.AnnexAofthepresentdocumentcontainsacopyofthisPIXITproformaparametertable.ThisproformatableisfilledupandcontainstheparametervaluesusedforthedefinitionoftheMSCsandTPs.5.2TestpurposenamingconventionTheidentifieroftheTPisbuiltaccordingtothefollowingscheme.SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)13Table1:TPidentifiernamingconventionschemeIdentifier:VB5_____VB5VB5.1referencepointspecificationRTMCprotocolatinterfaceANAccessNetworkistheIUTSNServiceNodeistheIUT=procedureidentifierlikeSTStartUpBRBlockingResourceURUnblockingResourceSRShutdownResourceCCVPCIConsistencyCheckVLSVerifyLSPId(SNinitiated)VLAVerifyLSPId(ANinitiated)RLSResetLSPId(SNinitiated)RLAResetLSPId(ANinitiated)RVSResetVPC(SNinitiated)RVAResetVPC(ANinitiated)CEHCommonErrorHandling=testcategory:CACapabilitytestsBVValidBehaviourtestsBIInvalidBehaviourtestsBOInopportuneBehaviourtestsTITimertests=sequentialnumber:(01-99)Exampleoftestpurposeandtestcasename:VB5_RTMC_AN_CC_BV_025.3Preamblesandpostambles5.3.1PreambledescriptionsThepreamblesareusedtobringtheIUTfrompower-onstatetothecorrectstatewhereatestcantakeplace.TheydifferwhethertheIUTisanANoranSN.5.3.1.1ANistheIUTStartup_AN:initializesandstartstheANconfiguration(allresourcesunblocked).SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)14MSC VB5_RTMC_Startup_ANAN_ENVVB5_SNSAALIUTVB5_ANInit_ANStart_ANThefirstcomponent,Init_AN,initializestheresourcesusedfortestingtheAN.Thewaytoinitializedependsupontheimplementation,butifmadethroughtheenvironmentinterface(Q3),itisequivalenttothefollowingMSC.SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)15MSC VB5_RTMC_Init_ANAN_ENVVB5_SNSAALIUTVB5_ANmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLUP }, logRsc ’000101’H, vpci1 ’0101’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLUP }, logRsc ’000101’H, vpci1 ’0102’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLUP }, logRsc ’000101’H, vpci1 ’0104’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLUP }, logRsc ’000101’H, vpci1 ’0105’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLSP }, logRsc ’008181’H, vpci1 ’8181’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLSP }, logRsc ’008181’H, vpci1 ’8182’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLSP }, logRsc ’008181’H, vpci1 ’8184’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLSP }, logRsc ’008181’H, vpci1 ’8185’H }meeVPCCreateConfSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)16Thesecondcomponent,Start_AN,startseffectivelytheAN.MSC VB5_RTMC_Start_ANAN_ENVVB5_SNSAALIUTVB5_ANmeeStartupReqAAL_establish_reqAAL_establish_confREQ_LSPID1, {}LSPID1, {rscId {rscIdContent { rscIndOctet {compLSP }, logRsc ’008181’H } } }RESET_RSC2, {rscList { multRscId { {rscIdContent { rscIndOctet {compLSP }, logRsc ’008181’H } } } } }RESET_RSC_ACK2, {result {resultIndOctet {successResultInd } }, rscList { multRscId {
} } }meeStartupConfenvSuccessSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)175.3.1.2SNistheIUTStartup_SN:initializesandstartstheSNconfiguration(allresourcesareunblocked).MSC VB5_RTMC_Startup_SNSN_ENVCH_SN_ANSAALIUTVB5_SNInit_SNStart_SNStartbu_SN:initializesandstartstheSNconfiguration(someresourcesarebusycarryingconnections)SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)18MSC VB5_RTMC_Startbu_SNSN_ENVCH_SN_ANSAALIUTVB5_SNInit_SNStart_SNThefirstcomponentofeachpreamble,Init_SN,initializestheresourcesusedfortestingtheSN.Thewaytoinitializedependsupontheimplementation,butifmadethroughtheenvironmentinterface(Q3),itisequivalenttothefollowingMSC.SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)19MSC VB5_RTMC_Init_SNSN_ENVCH_SN_ANSAALIUTVB5_SNmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLUP }, logRsc ’000101’H, vpci1 ’0101’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLUP }, logRsc ’000101’H, vpci1 ’0102’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLUP }, logRsc ’000101’H, vpci1 ’0104’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLUP }, logRsc ’000101’H, vpci1 ’0105’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLSP }, logRsc ’008181’H, vpci1 ’8181’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLSP }, logRsc ’008181’H, vpci1 ’8182’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLSP }, logRsc ’008181’H, vpci1 ’8184’H }meeVPCCreateConfmeeVPCCreateReq{ rscIndOctet {logIdUnk,connLSP }, logRsc ’008181’H, vpci1 ’8185’H }meeVPCCreateConfSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)20Thesecondcomponent,Start_SN,startseffectivelytheSN.MSC VB5_RTMC_Start_SNSN_ENVCH_SN_ANSAALIUTVB5_SNmeeStartupReqAAL_establish_reqAAL_establish_confREQ_LSPID1, {}LSPID1, {rscId {rscIdContent { rscIndOctet {compLSP }, logRsc ’008181’H } } }RESET_RSC2, {rscList { multRscId { {rscIdContent { rscIndOctet {compLSP }, logRsc ’008181’H } } } } }RESET_RSC_ACK2, {result {resultIndOctet {successResultInd } }, rscList { multRscId {
} } }meeStartupConfenvSuccess5.3.2PostambledescriptionsNopreambleisusedinthistestsuite.SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)216TestPurposesdefinitions6.1ANistheIUT6.1.1Basiccapabilitytests(CA)ThesetestsverifythecapabilityoftheANtoexchangevalidmessageswiththetester.ThefirststepconsistsofstartinguptheANRTMC.Subsequently,anumberofvalidmessagesaresentbythetester,inresponsetotherequestssentbytheANduringstart-up.StartUpprocedure(ST).StartUpinitiatedbyAN,firststep.VB5_RTMC_AN_ST_CA_01ReferenceEN301005-1[1]:13.3.4.1.2PurposeCheckstartupofRTMC,onrequestofoperatorassociatedwithAN.TestdescriptionThetestersetsupthelayer2thenissuesanimplicitsendtocausetheIUTtoinitiateastartupprocedure.PasscriteriaCheckthatthetesterisreceivingsuccessivelytheSAALPDUtosetupthelayer2andsubsequentlytheRTMCPDUREQ_LSPIDSelectionNonePreambleNonePostambleNoneAdditionaltestingNoneSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)22MSC VB5_RTMC_AN_ST_CA_01AN_ENVVB5_SNSAALIUTVB5_ANmeeStartupReqAAL_establish_reqAAL_establish_confREQ_LSPID1, {}StartUpinitiatedbyAN,complete.VB5_RTMC_AN_ST_CA_02ReferenceEN301005-1[1]:13.3.4.1.2PurposeCheckstartupofRTMC,onrequestofoperatorassociatedwithAN.TestdescriptionThetestersetsupthelayer2thenissuesanimplicitsendtocausetheIUTtoinitiateastartupprocedure.ThetesterisreceivingsuccessivelytheSAALPDUtosetupthelayer2andsubsequentlytheRTMCPDUREQ_LSPID.ThetestersendsbackitsLSPIDPasscriteriaCheckthatthetesterreceivesRESET_RSCwithresourceindicator=completeLSPandvalidLSPId.SelectionNonePreambleNonePostambleNoneAdditionaltestingWhentesterhascompletedthesendingoftheRESET_RSC_ACKPDUmeeStartupConfissenttotheANenvironmentSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)23MSC VB5_RTMC_AN_ST_CA_02AN_ENVVB5_SNSAALIUTVB5_ANmeeStartupReqAAL_establish_reqAAL_establish_confREQ_LSPID1, {}LSPID1, {rscId {rscIdContent { rscIndOctet {compLSP }, logRsc ’008181’H } } }RESET_RSC2, {rscList { multRscId { {rscIdContent { rscIndOctet {compLSP }, logRsc ’008181’H } } } } }VB5_RTMC_AN_ST_CA_03ReferenceEN301005-1[1]:13.3.1.4PurposeCheckthattheANisansweringtoatestercommandusingsametransactionIdentifierTestdescriptionThetestersendsREQ_LSPIDPDUtotheIUT.PasscriteriaCheckthatthetesterisreceivingLSPIDPDUcontainingthecorrecttransactionidentifierSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingNoneSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)24MSC VB5_RTMC_AN_ST_CA_03AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANREQ_LSPID101, {}LSPID101, {rscId {rscIdContent { rscIndOctet {compLSP }, logRsc ’008181’H } } }6.1.2Blockingresourceprocedure(BR)-VPCatLUP.VB5_RTMC_AN_BR_BV_01ReferenceEN301005-1[1]:13.3.2.1PurposeCheckblockingofasingleVPC,withvalidparameters,reason=admFullTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateaBLOCKresourceprocedure.PasscriteriaCheckthatthetesterisreceivingBLOCK_RSCPDUcontainingvalidparameters:LUPIdandVPCI,reason=AdmFullSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithBlock_RSC_ACK,meeBlockRscConfwithResultindicator=successissenttoANenvironment.Thecellflowontheblockedresourceisinhibitedinallcases,alsowhentheresourceisusedin(semi-)permanentconnections.NOTE:ThisinhibitionisactivatedintheANindependentlyfromtheinitiationoftheblockresourceprocedureintheVB5.1interface,asaparallelaction.SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)25MSC VB5_RTMC_AN_BR_BV_01AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeBlockRscReq{ {admFullEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } }BLOCK_RSC3, {blRscList { multBlRscId { {blRscIdContent { blReasonIndOctet {rTMCErrNone,rTMCAdmFull }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } } } }VB5_RTMC_AN_BR_BV_02ReferenceEN301005-1[1]:13.3.2.1PurposeCheckblockingofasingleVPC,withvalidparameters,reason=admPartTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateaBLOCKresourceprocedure.PasscriteriaCheckthatthetesterisreceivingBLOCK_RSCPDUcontainingvalidparameters:LUPIdandVPCI,reason=AdmPartSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithBlock_RSC_ACK,meeBlockRscConfwithResultindicator=successissenttoANenvironmentSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)26MSC VB5_RTMC_AN_BR_BV_02AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeBlockRscReq{ {admPartEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } }BLOCK_RSC3, {blRscList { multBlRscId { {blRscIdContent { blReasonIndOctet {rTMCErrNone,rTMCAdmPart }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } } } }VB5_RTMC_AN_BR_BV_03ReferenceEN301005-1[1]:13.3.2.1PurposeCheckblockingofasingleVPC,withvalidparameters,reason=errorTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateaBLOCKresourceprocedure.PasscriteriaCheckthatthetesterisreceivingBLOCK_RSCPDUcontainingvalidparameters:LUPIdandVPCI,reason=ErrSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithBlock_RSC_ACK,meeBlockRscConfwithResultindicator=successissenttoANenvironmentSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)27MSC VB5_RTMC_AN_BR_BV_03AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeBlockRscReq{ {errorEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } }BLOCK_RSC3, {blRscList { multBlRscId { {blRscIdContent { blReasonIndOctet {rTMCErr,rTMCAdmNone }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } } } }VB5_RTMC_AN_BR_BV_04ReferenceEN301005-1[1]:13.3.2.1PurposeCheckblockingofasingleVPC,withvalidparameters,reason=error+admPartTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateaBLOCKresourceprocedure.PasscriteriaCheckthatthetesterisreceivingBLOCK_RSCPDUcontainingvalidparameters:LUPIdandVPCI,reason=Err+admPartSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithBlock_RSC_ACK,meeBlockRscConfwithResultindicator=successissenttoANenvironmentSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)28MSC VB5_RTMC_AN_BR_BV_04AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeBlockRscReq{ {admPartErrEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } }BLOCK_RSC3, {blRscList { multBlRscId { {blRscIdContent { blReasonIndOctet {rTMCErr,rTMCAdmPart }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } } } }VB5_RTMC_AN_BR_BV_05ReferenceEN301005-1[1]:13.3.2.1PurposeCheckblockingofasingleVPC,withvalidparameters,reason=error+admFullTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateaBLOCKresourceprocedure.PasscriteriaCheckthatthetesterisreceivingBLOCK_RSCPDUcontainingvalidparameters:LUPIdandVPCI,reason=Err+admFullSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithBlock_RSC_ACK,meeBlockRscConfwithResultindicator=successissenttoANenvironmentSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)29MSC VB5_RTMC_AN_BR_BV_05AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeBlockRscReq{ {admFullErrEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } }BLOCK_RSC3, {blRscList { multBlRscId { {blRscIdContent { blReasonIndOctet {rTMCErr,rTMCAdmFull }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } } } }SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)30MSC VB5_RTMC_AN_BR_BV_06AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeBlockRscReq{ {admFullEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } }, {admFullEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0102’H } } }BLOCK_RSC3, {blRscList { repeatInd {repeatIndOctet {repeatIndMultList } }, multBlRscId { {blRscIdContent { blReasonIndOctet {rTMCErrNone,rTMCAdmFull }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } }, {blRscIdContent { blReasonIndOctet {rTMCErrNone,rTMCAdmFull }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0102’H } } } } }VB5_RTMC_AN_BR_BV_06ReferenceEN301005-1[1]:13.3.2.1PurposeCheckblockingofseveralVPCs,usinglistofvalidparametersTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateaBLOCKresourceprocedure.PasscriteriaCheckthatthetesterisreceivingBLOCK_RSCPDUcontainingalistofblockedresourceidentifiers,containingvalidparameters:LUPIdandknownVPCIs,reason=AdmFullSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithBlock_RSC_ACK,meeBlockRscConfwithResultindicator=successissenttoANenvironmentSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)31MSC VB5_RTMC_AN_BR_BV_06AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeBlockRscReq{ {admFullEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } }, {admFullEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0102’H } } }BLOCK_RSC3, {blRscList { repeatInd {repeatIndOctet {repeatIndMultList } }, multBlRscId { {blRscIdContent { blReasonIndOctet {rTMCErrNone,rTMCAdmFull }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } }, {blRscIdContent { blReasonIndOctet {rTMCErrNone,rTMCAdmFull }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0102’H } } } } }VB5_RTMC_AN_BR_BV_07ReferenceEN301005-1[1]:13.3.2.1PurposeCheckblockingofpartofaPUP(severalVPC),usingvalidparameterboundariestodefinearangeTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateaBLOCKresourceprocedure.PasscriteriaCheckthatthetesterisreceivingBLOCK_RSCPDUcontainingvalidparameters:LUPIdandfirstandlastofalistofconsecutiveknownVPCIs,reason=AdmFullSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithBlock_RSC_ACK,meeBlockRscConfwithResultindicator=successissenttoANenvironmentSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)32MSC VB5_RTMC_AN_BR_BV_07AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeBlockRscReq{ {admFullEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H, vpci2 ’0102’H } } }BLOCK_RSC3, {blRscList { multBlRscId { {blRscIdContent { blReasonIndOctet {rTMCErrNone,rTMCAdmFull }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H, vpci2 ’0102’H } } } } }VB5_RTMC_AN_BR_BV_08ReferenceEN301005-1[1]:13.3.2.1PurposeCheckblockingofseveralVPCs,usingalistofblockedresourceidentifierscontainingvalidparameters,oneofthemincludingboundariestodefinearangeofVPCIsTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateaBLOCKresourceprocedure.PasscriteriaCheckthatthetesterisreceivingBLOCK_RSCPDUcontainingvalidmixtureofparameters:LUPIdandVPCIs,reason=AdmFullSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithBlock_RSC_ACK,meeBlockRscConfwithResultindicator=successissenttoANenvironmentSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)33MSC VB5_RTMC_AN_BR_BV_08AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeBlockRscReq{ {admFullEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H,
vpci1 ’0101’H ,
vpci2 ’0102’H } }, {admFullEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0105’H } } }BLOCK_RSC3, {blRscList { repeatInd {repeatIndOctet {repeatIndMultList } }, multBlRscId { {blRscIdContent { blReasonIndOctet {rTMCErrNone,rTMCAdmFull }, blRscIndOctet {connLUP }, logRsc ’000101’H,
vpci1 ’0101’H ,
vpci2 ’0102’H } }, {blRscIdContent { blReasonIndOctet {rTMCErrNone,rTMCAdmFull }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0105’H } } } } }VB5_RTMC_AN_BR_TI_01ReferenceEN301005-1[1]:13.3.2.1PurposeChecktimeouton"blockingresource"ofasingleVPCTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateaBLOCKresourceprocedure.ThentheIUTsendsBLOCK_RSCPDUtothetesterwithvalidLUPIdandVPCI,reason=AdmFull.ThetesterdoesnotrespondwithBLOCK_RSC_ACKPDUwithinT_blocktimePasscriteriaCheckthatthetesterisreceivingasecondBLOCK_RSCPDUcontainingsamecorrectparametersSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithBlock_RSC_ACK,meeBlockRscConfwithResultindicator=transmissionerrorissenttoANenvironmentSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)34MSC VB5_RTMC_AN_BR_TI_01AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeBlockRscReq{ {admFullEnv, rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } }BLOCK_RSC3, {blRscList { multBlRscId { {blRscIdContent { blReasonIndOctet {rTMCErrNone,rTMCAdmFull }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } } } }BLOCK_RSC3, {blRscList { multBlRscId { {blRscIdContent { blReasonIndOctet {rTMCErrNone,rTMCAdmFull }, blRscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } } } }meeBlockRscConfenvTransErr, { { rscIdContent { rscIndOctet {logIdUnk,connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } }-VPCatLSP.Itispossibletoblockasingle,alistorarangeofVPCbelongingeithertoaLUPortoaLSP.ThismeansthatasetofTPs,identicaltothepreviousone,ismadebyreplacingLUPIdbyLSPId.Testpurposenamingcorrespondenceisasfollows:SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)35VPCatLUPVPCatLSPVB5_RTMC_AN_BR_BV_01VB5_RTMC_AN_BR_BV_11VB5_RTMC_AN_BR_BV_02VB5_RTMC_AN_BR_BV_12VB5_RTMC_AN_BR_BV_03VB5_RTMC_AN_BR_BV_13VB5_RTMC_AN_BR_BV_04VB5_RTMC_AN_BR_BV_14VB5_RTMC_AN_BR_BV_05VB5_RTMC_AN_BR_BV_15VB5_RTMC_AN_BR_BV_06VB5_RTMC_AN_BR_BV_16VB5_RTMC_AN_BR_BV_07VB5_RTMC_AN_BR_BV_17VB5_RTMC_AN_BR_BV_08VB5_RTMC_AN_BR_BV_18VB5_RTMC_AN_BR_TI_01VB5_RTMC_AN_BR_TI_11TheMSCsforthesetofTPsrelativetoVPCatLSParenotincludedinthispresentdocument.ThefollowingMSCgivesanexampleofthechangesduewhengoingfromVPCatLUPtoVPCatLSP.MSC VB5_RTMC_AN_BR_BV_11AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeBlockRscReq{ {admFullEnv, rscIdContent { rscIndOctet {connLSP }, logRsc ’008181’H, vpci1 ’8181’H } } }BLOCK_RSC3, {blRscList { multBlRscId { {blRscIdContent { blReasonIndOctet {rTMCErrNone,rTMCAdmFull }, blRscIndOctet {connLSP }, logRsc ’008181’H, vpci1 ’8181’H } } } } }SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)366.1.3Unblockingresourceprocedure(UR)-VPCatLUP.VB5_RTMC_AN_UR_BV_01ReferenceEN301005-1[1]:13.3.2.1PurposeCheckunblockingofasingleVPC,withvalidparametersTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateanUNBLOCKresourceprocedure.PasscriteriaCheckthatthetesterisreceivingUNBLOCK_RSCPDUcontainingcorrectparametersLUPIdandVPCISelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithUnblock_RSC_ACK,meeUnblockRscConfwithResultindicator=successissenttoANenvironmentMSC VB5_RTMC_AN_UR_BV_01AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeUnblockRscReq{ { rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } }UNBLOCK_RSC3, {rscList { multRscId { {rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } } } }SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)37VB5_RTMC_AN_UR_BV_02ReferenceEN301005-1[1]:13.3.2.1PurposeCheckunblockingofseveralVPCs,usinglistofvalidparametersTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateanUNBLOCKresourceprocedure.PasscriteriaCheckthatthetesterisreceivingUNBLOCK_RSCPDUcontainingcorrectparameters:listofresourceidentifierscontainingknownLUPIdandVPCIsSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithUnblock_RSC_ACK,meeUnblockRscConfwithResultindicator=successissenttoANenvironmentMSC VB5_RTMC_AN_UR_BV_02AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeUnblockRscReq{ { rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } }, { rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0102’H } } }UNBLOCK_RSC3, {rscList { repeatInd {repeatIndOctet {repeatIndMultList } }, multRscId { {rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } }, {rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0102’H } } } } }SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)38VB5_RTMC_AN_UR_BV_03ReferenceEN301005-1[1]:13.3.2.1PurposeCheckunblockingofapartofaPUP(severalVPC),usingvalidparameterboundariestodefinearangeTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateanUNBLOCKresourceprocedure.PasscriteriaCheckthatthetesterisreceivingUNBLOCK_RSCPDUcontainingcorrectparameters:LUPIdandfirstandlastofalistofconsecutiveknownVPCIsSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithUnblock_RSC_ACK,meeUnblockRscConfwithResultindicator=successissenttoANenvironmentMSC VB5_RTMC_AN_UR_BV_03AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeUnblockRscReq{ { rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H, vpci2 ’0102’H } } }UNBLOCK_RSC3, {rscList { multRscId { {rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H, vpci2 ’0102’H } } } } }SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)39VB5_RTMC_AN_UR_TI_01ReferenceEN301005-1[1]:13.3.2.1PurposeChecktimeouton"unblockingresource"ofasingleVPCTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateanUNBLOCKresourceprocedure.ThentheIUTsendsUNBLOCK_RSCPDUtothetesterwithvalidLUPIdandVPCI.ThetesterdoesnotrespondwithUNBLOCK_RSC_ACKPDUwithinT_unblocktimePasscriteriaCheckthatthetesterisreceivingasecondUNBLOCK_RSCPDUcontainingsamecorrectparametersSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingWhentesteranswerswithUnblock_RSC_ACK,meeUnblockRscConfwithResultindicator=transmissionerrorissenttoANenvironmentMSC VB5_RTMC_AN_UR_TI_01AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeUnblockRscReq{ { rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } }UNBLOCK_RSC3, {rscList { multRscId { {rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } } } }UNBLOCK_RSC3, {rscList { multRscId { {rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } } } }meeUnblockRscConfenvTransErr, { { rscIdContent { rscIndOctet {logIdUnk,connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } }SIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)40-VPCatLSP.Itispossibletounblockasingle,alistorarangeofVPCbelongingeithertoaLUPortoaLSP.ThismeansthatasetofTPsidenticaltothepreviousone,ismadebyreplacingLUPIdbyLSPId.Testpurposenamingcorrespondenceisasfollows:VPCatLUPVPCatLSPVB5_RTMC_AN_UR_BV_01VB5_RTMC_AN_UR_BV_11VB5_RTMC_AN_UR_BV_02VB5_RTMC_AN_UR_BV_12VB5_RTMC_AN_UR_BV_03VB5_RTMC_AN_UR_BV_13VB5_RTMC_AN_UR_TI_01VB5_RTMC_AN_UR_TI_116.1.4Shutdownresourceprocedure(SR)-VPCatLUP.VB5_RTMC_AN_SR_BV_01ReferenceEN301005-1[1]:13.3.2.2PurposeCheckinitializationofshutdownprocedureofasingleVPC,withvalidparametersTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateaSHUTDOWNresourceprocedure.PasscriteriaCheckthatthetesterisreceivingAWAIT_CLEARPDUcontainingcorrectparameters:validLUPIdandVPCISelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingNoneSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)41MSC VB5_RTMC_AN_SR_BV_01AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeAwaitClearReq{ { rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } }AWAIT_CLEAR3, {rscList { multRscId { {rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0101’H } } } } }VB5_RTMC_AN_SR_BV_02ReferenceEN301005-1[1]:13.3.2.2PurposeCheckcompleteshutdownprocedureofasingleVPC,withvalidparametersTestdescriptionThetesterissuesanimplicitsendtocausetheIUTtoinitiateaSHUTDOWNresourceprocedure.ThentheIUTsendsAWAIT_CLEARPDUtothetesterwithvalidLUPIdandVPCI.ThetesteranswerswithAWAIT_CLEAR_ACKPDUwithinT_acltimewithResultindicator=success.ThenthetestersendsAWAIT_CLEAR_COMPPDUwithsamevalidparametersPasscriteriaCheckthatthetesterisreceivingAWAIT_CLEAR_COMPACKPDUwithnoparametersSelectionNonePreambleStartup_ANPostambleNoneAdditionaltestingmeeAwaitClearConfwithResultindicator=successandLUPId/VPCIparametersaresenttoANenvironmentSIST EN 301 005-3:2001
ETSIETSIEN301005-3V1.1.2(2000-05)42MSC VB5_RTMC_AN_SR_BV_02AN_ENVVB5_SNSAALIUTVB5_ANStartup_ANmeeAwaitClearReq{ { rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0102’H } } }AWAIT_CLEAR3, {rscList { multRscId { {rscIdContent { rscIndOctet {connLUP }, logRsc ’000101’H, vpci1 ’0102’H } } } } }AWAIT_CLEAR_ACK3, {result {resultIndOctet {successResultInd } }, rscLi
...