SIST EN 301 217-3 V1.1.1:2003

• Abstract:

  Specification of the Test Suite Structure, Test Purposes, Abstract Test Suite (Test Cases in TTCN), partial PIXIT proforma and conformance testing report proforma for the VB5.2 reference point covering the physical, procedural and protocol requirements between a broadband or combined narrowband & broadband access network and a service node.

• Status: Published
• Publication Date: 31-Oct-2003
• ICS: 35.200 - Interface and interconnection equipment
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Nov-2003
• Due Date: 01-Nov-2003
• Completion Date: 01-Nov-2003
• Ref Project: ETSI EN 301 217-3 V1.1.1 (2000-11) - V interfaces at the digital Service Node (SN); Interfaces at the VB5.2 reference point for the support of broadband or combined narrowband and broadband Access Networks (ANs); Part 3: Test Suite Structure and Test Purposes (TSS&TPP)

SIST EN 301 217-3 V1.1.1:2003 is the Slovenian adoption of the ETSI standard for VB5.2 interfaces at the digital Service Node (SN). It specifies the Test Suite Structure and Test Purposes for Broadband Bearer Connection Control (BBCC) at the VB5.2 reference point between an Access Network (AN) and an SN. The document is used to test conformance of AN and SN implementations, and it also provides the test case structure, partial PIXIT material, and the conformance testing report proforma.

What does SIST EN 301 217-3 V1.1.1:2003 specify?

SIST EN 301 217-3 V1.1.1:2003 defines how to organize and describe BBCC conformance tests for the VB5.2 reference point. It covers the physical, procedural, and protocol requirements between an AN and an SN, and it is written for both sides of the interface.

The document is organized into six clauses plus two informative annexes:

Annex	What it covers
Annex A	PIXIT parameters and the informative values used in the message sequence charts
Annex B	ASN.1 data declarations for the BBCC protocol

Clause 4 defines the test suite structure. Clause 5 explains how test purposes are written, named, and mapped to Message Sequence Charts (MSCs). Clause 6 gives the detailed test purposes for the AN and the SN.

What are the key requirements of SIST EN 301 217-3 V1.1.1:2003?

The main job of SIST EN 301 217-3 V1.1.1:2003 is to turn the BBCC protocol specification into executable conformance tests. That matters in practice because it tells a lab or vendor what to stimulate, what to observe, and what verdict to expect.

Test organization and naming

Clause 4 structures the test suite first by BBCC procedure and then by test category. Clause 5.2 defines the test purpose name format as VB5_<i>_<IUT>_<pp>_<cc>_<nn>, where <IUT> identifies whether the AN or SN is under test and <cc> identifies Capability, Valid Behaviour, Invalid Behaviour, or Timer tests. This makes each case traceable to its procedure and test type.

How a test purpose is described

Clause 5.1 says each TP includes a name, a reference to the protocol requirement, the purpose, the test description, pass criteria, selection information, a preamble, a postamble, and additional testing notes. In practice, this gives a single self-contained description that a test engineer can implement and review.

MSC-based test scenarios

Clause 5.1.2 uses MSCs to show the test scenario with the tester, the IUT, and the VB5.2 environment. The MSCs show BBCC PDU exchanges at the VB5 PCO, so the reader can see exactly which messages are sent and expected.

Parameter handling and PIXIT use

Clause 5.1.3 says the important parameters are taken from the PIXIT proforma and, in Annex A, from the values used in the MSC examples. Some values are fixed by the protocol, while others can be chosen within valid ranges. This matters because the test setup must match the implementation under test.

Procedure coverage

Clause 6 covers start-up, connection establishment, connection release, connection modification, branch establishment, branch release, housekeeping, and common error handling. Some procedures apply only to point-to-point configurations, others only to point-to-multipoint, so the chosen test set depends on the supported connection type.

Timers and error handling

The test purposes include timer tests and invalid-behaviour tests. They check acceptance windows around the named timers and verify that wrong protocol discriminators, bad transaction identifiers, missing information elements, unknown information elements, and unexpected information elements are handled correctly. In practice, this confirms both normal call control and robust error detection.

What terms does SIST EN 301 217-3 V1.1.1:2003 define?

• Broadband Bearer Connection Control (BBCC) - The BBCC protocol under test for connection control at the VB5.2 reference point.
• Access Network (AN) - The network side that can be the implementation under test in this document.
• Service Node (SN) - The service node side that can also be the implementation under test.
• Test Suite Structure and Test Purposes (TSS&TP) - The part of the conformance method that organizes the tests and states what each test checks.
• Abstract Test Suite (ATS) - The abstract set of test cases used for conformance testing.
• Implementation Under Test (IUT) - The implementation being tested, either the AN or the SN.
• Point of Control and Observation (PCO) - The point where the tester sends stimuli and observes protocol behavior.
• Protocol Implementation Conformance Statement (PICS) - The statement that identifies which protocol options an implementation supports.

Who uses SIST EN 301 217-3 V1.1.1:2003?

Test laboratories use this standard to build and run BBCC conformance tests. Equipment vendors use it to validate AN and SN implementations against the VB5.2 protocol behavior. Quality managers and buyers use it to check what kind of interoperability and conformance evidence a supplier can provide. Engineers use it to select test cases, prepare PIXIT values, and interpret accept, reject, and timer-related outcomes.

Which standards are used with SIST EN 301 217-3 V1.1.1:2003?

Reference	What it contributes
EN 301 217-1	The VB5.2 interface specification that states the protocol requirements tested here
EN 301 217-2	The PICS proforma specification used for test selection
EN 301 217-3	The related VB5.2 TSS&TP part in this standard family
EN 300 443-1	BBCC protocol specification for DSS2 basic call/bearer control
EN 301 067-1	Connection characteristics and negotiation during establishment
EN 301 068	ATM transfer capability and traffic parameter indication
EN 301 005-1	VB5.1 interface specification used for comparison and background
EN 301 005-3	VB5.1 TSS&TP specification for the RTMC-related test structure
EN 301 005-4	VB5.1 ATS and PIXIT proforma specification
ISO/IEC 9646-1	General conformance testing concepts
ISO/IEC 9646-2	Abstract test suite specification method
ITU-T M.3010	Telecommunications management network principles
ITU-T Q.2931	B-ISDN DSS2 UNI layer 3 basic call/connection control
ITU-T Q.2961.3	Signalling capabilities for ABR traffic parameters
ITU-T Q.2961.5	Additional traffic parameters for CDVT indication

What does the SIST EN 301 217-3 V1.1.1:2003 document contain?

The document contains the test suite structure, naming rules, MSC-based test descriptions, and detailed BBCC test purposes for AN and SN implementations. It includes start-up, connection, release, modification, branch, housekeeping, and common error-handling tests. Annex A provides the PIXIT parameter table and example values used in the MSCs, and Annex B gives ASN.1 declarations for the BBCC protocol.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.ãHYDOQHJDV interfaces at the digital Service Node (SN); Interfaces at the VB5.2 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)35.200Vmesniška in povezovalna opremaInterface and interconnection equipmentICS:Ta slovenski standard je istoveten z:EN 301 217-3 Version 1.1.1SIST EN 301 217-3 V1.1.1:2003en01-november-2003SIST EN 301 217-3 V1.1.1:2003SLOVENSKI
STANDARD
ETSIEN301217-3V1.1.1(2001-01)EuropeanStandard(Telecommunicationsseries)VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.2referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part3:TestSuiteStructureandTestPurposes(TSS&TP)SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)2ReferenceDEN/SPAN-09047-3KeywordsAN,SN,TSS&TP,Vinterface,VB5interfaceETSI650RoutedesLuciolesF-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.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)3ContentsIntellectualPropertyRights.5Foreword.5Introduction.51Scope.72References.73Definitionsandabbreviations.83.1Definitions.83.2Abbreviations.84TestSuiteStructure.105TestPurposesdescriptionandnaming.135.1MethodusedforthedescriptionoftheTPs.135.1.1TextformatofTP.135.1.2MSCassociatedtothetextofTP.135.1.3ParametersshowninTP.145.1.4StimulifortheIUT.145.2Testpurposenamingconvention.155.3Preamblesandpostambles.165.3.1Preambledescriptions.165.3.1.1ANistheIUT.165.3.1.2SNistheIUT.245.3.2Postambledescriptions.336TestPurposesdefinitions.336.1ANistheIUT.336.1.1Basiccapabilitytests(CA).336.1.2ConnectionEstablishmentprocedure(CE).346.1.2.1PointtoPointConnectionEstablishmentprocedure.346.1.2.2PointtoMultipointConnectionEstablishmentprocedure.416.1.3ConnectionReleaseprocedure(CR).436.1.3.1SingleConnectionReleaseprocedure.436.1.3.2MultipleConnectionsReleaseprocedure.476.1.4Connectionmodificationprocedure(CM).526.1.4.1Modification(firststep)procedure.526.1.4.2ModificationCompleteprocedure.536.1.4.3ModificationAbortprocedure.556.1.4.4Modificationexceptionalprocedure.566.1.4.5TestoftimerT_Modification.616.1.5BranchEstablishmentprocedure(BE).676.1.5.1AddBranchprocedure.676.1.5.2AddBranchCompleteprocedure.696.1.5.3T_BranchEsttimertest.716.1.5.4Exceptionalprocedure.726.1.6BranchReleaseprocedure(BR).756.1.6.1SingleBranchreleaseprocedure.756.1.6.2MultipleBranchreleaseprocedure.766.1.6.3Exceptionalprocedure.776.1.7Housekeepingprocedure(Reset,Fault).806.1.7.1Resetprocedure.806.1.7.2ANfaultprocedure.846.1.7.3BBCCrestartprocedure.866.1.8CommonErrorHandling(CEH)procedure.916.1.8.1ErrorHandlingonMessageHeader.916.1.8.2ErrorHandlingonInformationElement(IE).98SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)46.2SNistheIUT.1016.2.1Basiccapabilitytests(CA).1016.2.2ConnectionEstablishmentprocedure(CE).1026.2.2.1PointtoPointConnectionEstablishmentprocedure.1026.2.2.2PointtoMultipointConnectionEstablishmentprocedure.1086.2.3ConnectionReleaseprocedure(CR).1106.2.3.1SingleconnectionReleaseprocedure.1106.2.3.2MultipleconnectionsReleaseprocedure.1136.2.4Connectionmodificationprocedure(CM).1166.2.4.1Modification(firststep)procedure.1166.2.4.2ModificationCompleteprocedure.1196.2.4.3ModificationAbortprocedure.1216.2.5BranchEstablishmentprocedure(BE).1236.2.5.1AddBranchprocedure.1236.2.5.2AddBranch/Updateprocedure.1266.2.6BranchReleaseprocedure(BR).1286.2.7Housekeepingprocedure(Reset,Fault).1316.2.7.1Resetprocedure.1316.2.7.2ANfaultprocedure.1356.2.7.3BBCCrestartprocedure.1366.2.8CommonErrorHandling(CEH)procedure.1396.2.8.1ErrorHandlingonMessageHeader.1396.2.8.2ErrorHandlingonInformationElement(IE).146AnnexA(informative):PIXITparametersandtheinformativevaluesused.149A.1ParametervaluesasusedintheMSCs.149A.1.1Diagramofconnectionsusedinthetestsuites.149A.1.2TableofPIXITparameters.150A.1.3Transactionidentifiervalues.151A.1.4Timervalues.152AnnexB(informative):ASN.1datadeclarationsfortheBBCCprotocol.153Bibliography.162History.163SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)5IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeServicesandProtocolsforAdvancedNetworks(SPAN).Thepresentdocumentispart3ofmulti-partdeliverablecoveringtheinterfacesattheVB5.2referencepointasidentifiedbelow:Part1:"Interfacespecification";Part2:"ProtocolImplementationConformanceStatement(PICS)specification";Part3:"TestSuiteStructureandTestPurposes(TSS&TP)";Part4:"AbstractTestSuite(ATS)specificationandpartialProtocolImplementationeXtraInformationforTesting(PIXIT)".NationaltranspositiondatesDateofadoptionofthisEN:19January2001DateoflatestannouncementofthisEN(doa):30April2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31October2001DateofwithdrawalofanyconflictingNationalStandard(dow):31October2001IntroductionGeneralTheworkonanewbroadbandVBreferencepointconceptwasinitiatedbyETSITechnicalCommitteeSPStoconsider,inco-operationwithothergroupsinvolved,possiblenewstructuresandreferencepointsfortheconnectionofnewbroadbandandcombinednarrowband/broadbandaccessarrangementstoServiceNodes(SN).TheworkwastakenoverbyaspecialexpertsgrouponVB5,workingundertheauspicesofWorkingGroupSPS3,withinETSI.TheVB5referencepointconceptwassplitintotwovariants.ThefirstbasedonanATMcrossconnectwithprovisionedconnectivity,calledtheVB5.1referencepoint,iscontainedinEN301005-1[1].Theother,whichfurtherenableson-demandconnectivitywithintheAN,iscalledtheVB5.2referencepointandisdescribedinEN301217-1[3].SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)6RelationshipbetweentheVB5.1andVB5.2referencepointconceptTheVB5.2referencepointextendsthecapabilitiesattheVB5.1referencepointtoincludeon-demandconnectivityintheANunderthecontrolofSN.Inadditiontothemajordifferencegivenabove,themajorcorrespondencebetweentheVB5.1andVB5.2referencepointcanbedescribedas:-bothVB5interfacessupportB-ISDNaswellasnarrowbandandothernon-B-ISDNcustomeraccesstypes;-bothVB5interfacessupportATMmultiplexing/cross-connectingintheANatthevirtualpathand/orvirtualchannellevel.SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)71ScopeThepresentdocumentspecifiestheTestSuiteStructureandTestPurposes(TSS&TP)fortestingtheconformityofanimplementationtothespecificationofprotocolBroadbandBearerConnectionControl(BBCC)ofinterfacesattheVB5.2referencepointbetweenanAccessNetwork(AN)andaServiceNode(SN).TheTSS&TPfortestingtheotherprotocolnamedRTMCofinterfacesattheVB5.2referencepointisinEN301005-3[2],asitiscommonwithRTMCatVB5.1referencepoint.ThetestarchitectureproposedhereforthetestingofconformityisalsousedforthedesignoftheMessageSequenceCharts(MSCs)producedastestpurposedocumentation.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN301005-1(V1.1.4):"VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.1referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part1:Interfacespecification".[2]ETSIEN301005-3(V1.1.2):"VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.1referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part3:TestSuiteStructureandTestPurposes(TSS&TP)specification".[3]ETSIEN301217-1(V1.2.2):"VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.2referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part1:Interfacespecification".[4]ETSIEN301217-2(V1.1.3):"VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.2referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[5]ISO/IEC9646-1:"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[6]ISO/IEC9646-2:"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part2:Abstracttestsuitespecification".[7]ITU-TRecommendationM.3010:"PrinciplesforaTelecommunicationsmanagementnetwork".[8]ITU-TRecommendationQ.2931:"BroadbandIntegratedServicesDigitalNetwork(B-ISDN)-DigitalSubscriberSignallingSystemNo.2(DSS2)-User-NetworkInterface(UNI)-Layer3specificationforbasiccall/connectioncontrol".[9]ETSIEN300443-1(V1.3.5):"BroadbandIntegratedServicesDigitalNetwork(B-ISDN);DigitalSubscriberSignallingSystemNo.two(DSS2)protocol;B-ISDNuser-networkinterfacelayer3specificationforbasiccall/bearercontrol;Part1:Protocolspecification[ITU-TRecommendationQ.2931(1995),modified]".SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)8[10]ETSIEN301067-1(V1.1.3):"BroadbandIntegratedServicesDigitalNetwork(B-ISDN);DigitalSubscriberSignallingSystemNo.two(DSS2)protocol;Connectioncharacteristics;Negotiationduringcall/connectionestablishmentphase;Part1:Protocolspecification[ITU-TRecommendationQ.2962(1996),modified]".[11]ITU-TRecommendationQ.2961.3:"DigitalSubscriberSignallingSystemNo.2-Additionaltrafficparameters:Signallingcapabilitiestosupporttrafficparametersfortheavailablebitrate(ABR)ATMtransfercapability".[12]ITU-TRecommendationQ.2961.5:"DigitalsubscribersignallingsystemNo.2-Additionaltrafficparameters:Additionaltrafficparametersforcelldelayvariationtoleranceindication".[13]ETSIEN301005-4(V1.1.2):"VInterfacesattheDigitalServiceNode(SN);InterfacesattheVB5.1ReferencePointfortheSupportofBroadbandorCombinedNarrowbandandBroadbandAccessNetworks(ANs);Part4:AbstractTestSuite(ATS)andPartialProtocolImplementationeXtraInformationforTesting(PIXIT)ProformaSpecification".[14]ETSIEN301068:"BroadbandIntegratedServicesDigitalNetwork(B-ISDN);DigitalSubscriberSignallingSystemNo.Two(DSS2)Protocol;ConnectionCharacteristics;ATMTransferCapabilityandTrafficParameterIndication".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:-termsdefinedinEN301217-1[3];-termsdefinedinISO/IEC9646-1[5]andinISO/IEC9646-2[6].Inparticular,thefollowingtermsdefinedinISO/IEC9646-1[5]apply:AbstractTestSuite(ATS)ImplementationUnderTest(IUT)PointofControlandObservation(PCO)SystemUnderTest(SUT)ProtocolImplementationConformanceStatement(PICS)3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:AALATMAdaptationLayerAAL-SAPAAL-ServiceAccessPointANAccessNetworkATMAsynchronousTransferModeBBCCBroadbandBearerConnectionControlB-ISDNBroadbandISDNB-ISUPBroadbandISDNSignallingUserPartB-UNIBroadbandUNIBABasic(rate)AccessCPECustomerPremisesEquipmentCPNCustomerPremisesNetworkETEquipmentTerminalFSMFiniteStateMachineIDIdentitySIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)9IEInformationElementINIInter-NetworkInterfaceISDNIntegratedServicesDigitalNetworkLANLocalAreaNetworkLELocalExchangeLMELayerManagementEntityLMILocalManagementInterfaceLSPLogicalServicePortLUPLogicalUserPortMIBManagementInformationBaseMSCMessageSequenceChartN-ISDNNarrowbandISDNNNINetwork-to-NetworkInterfaceOAMOperationsAdministrationandMaintenancePDHPlesiochronousDigitalHierarchyPDUProtocolDataUnitsPSPPhysicalServicePortPSTNPublicSwitchedTelephoneNetworkPUPPhysicalUserPortQ3"Q"managementinterfacereferencepointasITU-TRecommendationM.3010[7]RTMCRealTimeManagementCo-ordinationSAALSignallingATMAdaptationLayerSAPServiceAccessPointSARSegmentationandReassemblySDHSynchronousDigitalHierarchySDLSpecificationandDescriptionLanguageSDUServiceDataUnitsSNServiceNodeSNIServiceNodeInterfaceSPServicePortSPSSignallingProtocolsandSwitchingSSCFServiceSpecificCo-ordinationFunctionSSCOPServiceSpecificConnectionOrientedProtocolTCTechnicalCommitteesTETerminalEquipmentTMNTelecommunicationManagementNetworkTPTransmissionPathUNIUser-NetworkInterfaceVBBroadband"V"referencepointVCVirtualChannel(ATM)VCCVCConnectionVCCTVCCTerminationVCEVirtualChannelEntityVCIVCIdentifierVCLVCLinkVCMEVCMultiplexEntityVPVirtualPathVPCVPConnectionVPCIVPConnectionIdentifierVPCTVPCTerminationVPEVPEntityVPIVPIdentifierVPLVPLinkVPMEVPMultiplexEntityVUPVirtualUserPortSIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)104TestSuiteStructureFigure1showsthestructureoftheV5.2BBCCtestsuitewhentheANistheIUT.Figure2showsthestructureoftheV5.2BBCCtestsuitewhentheSNistheIUT.ThefirstlevelisstructuredaccordingtotheBBCCprocedures.Thesecondlevelisstructuredaccordingtotestcategory.Themeaningofthecodesinthetreeisgiveninsubclause5.2.SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)11VB5_BBCCANSTCABVCEBITIBVCRBIBVCMBITIBVBEBITIBVBRBIBVHKTICEHBIFigure1:VB5BBCCANTSSSIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)12VB5_BBCCSNSTCABVCETIBVCRTIBVCMTIBVBETIBVBRTIBVHKTICEHBIFigure2:VB5BBCCSNTSSSIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)13Invalidbehaviourofthetestercomprises:referencetounknownresources,unknownmessagetype,anderrorsincommonmessagefields(protocoldiscriminator,transactionidentifier,messagelength).BBCCtimertestsandinopportunebehaviourtestsarerelatedtoanumberofspecificBBCCproceduresandthetestsuitehasbeenstructuredaccordingly.NOTE:Toleranceintervalfortimertest.Testsoftimersrelatedtocorrectionoftransmissionerrorsincommunicationwithpeernetworkelement(seeEN301217-1[3]subclause13.6.1.5.3)haveasessentialpurposetocheckthatthetimerfunctionandtheretransmissionfunctionareimplemented.Inthetestsuite,acalibrationofeachtimerisalsoperformed,i.e.alowertimelimitandanuppertimelimitaresetaroundthenominaltimervalueforthereceptionoftheretransmittedmessages.ThePASSverdictisgrantedifreceptionisobservedbetweenthesetwolimits.Theselimitsarechosenbytheimplementer.Thetimeintervaldefinedbytheselimitswillbecalledhereafterthe"toleranceinterval".5TestPurposesdescriptionandnaming5.1MethodusedforthedescriptionoftheTPsEachTPisdescribedusingtextualinformationpresentedinatable.ThistableisfollowedbyanMSCrepresentingthetestscenario.5.1.1TextformatofTPThetabledescribingeachTPisasfollows.TP-Nameisauniqueidentifier,createdaccordingtotheTPnamingconventions(alsothenameofthecorrespondingtestcase)ReferencetotheparagraphnumberofspecificationEN301217-1[3]statingtheconformancerequirementPurposePurposeofthetestperformedagainstarequirementoftheprotocolTestdescriptionInformationonthetestbody,describingactionsandparametersPasscriteriaVisibleactiontobeobservedatPCOtodeclarethattheIUTpassesthetestandconformstothespecificationsSelection"None"orexpressionbasedonEN301217-2[4]PICSandPIXITstatements,usedtoselectordeselectthecorrespondingtestcaseaccordingtotheoptionsoftheimplementation(note)Preamble"None"ornameofthepreambleprocedurebringingtheIUTfromidlestatetothestaterequiredtorunthetestPostamble"None"ornameofthepostambletobringtheIUTbacktoidlestateAdditionaltestingAdditionalinformation,presentinspecification,forpossibleinformaltestingbeyondBBCCprotocol(forinstance,iftesteriscapableofobservation/actionviaadditionalinterfacelikeQ3orsignallinginterfaces)NOTE:Forsometests,anexpressionbasedonPIXITparameterswithbinaryyes/novaluemaybeused.ThismayhappenifthetestcaseshallonlybeselectedwhenaspecificreactionoftheANVB5.2applicationfunctioncanbeexpected(e.g.rejectionofanALLOCrequestwithcause"ATMtransfercapabilitynotsupported").ThismaybeobtainedbysuitablesettingsintheSystemUnderTestcombinedwithsuitableassignmentofPIXITparametervaluesinthemessagessentbythetester.Theexactsettingissystemdependentandoutsidethescopeofthepresentdocument.5.1.2MSCassociatedtothetextofTPForillustrationpurposesaMSCingraphicalformfollowsselectedTPtabulateddescriptions.TheMSCisproducedbyexercisingtheSDLmodel,wheneverpossible.Iftheprocedureisnotmodelled,thenthecorrespondingMSCisdrawnmanually.ThecolumnsidentifiedintheMSCrepresent,fromlefttoright,thetester,theIUT(i.e.theANorSNSystem),andtheVB5.2environmentfunctions.AsanMSCisfocusingonthebodyofthetest,thepreambleisrepresentedbyasingleboxintheMSC.SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)14ThefollowingarrowsrepresenttheexchangeofPDUofBBCCprotocolattheVB5.2interface,whichcorrespondstoPCOnamedVB5inthetestsuite.Whenneeded,astimulustoinitiatetheexecutionofaBBCCprocedureisalsodepicted.5.1.3ParametersshowninTPForclaritysake,onlytheparametersmostrelevanttothetestpurposeareshowninthediagram.InadditionandoncertaintestcasesandPDUs,likeRESET_COMPLETE_LSPorBBCC_PRESYNC,theLSPconnectionidentifierisnotshown.ThevaluesoftheseparametersareeitherimposedbythetestbecausetheyarespecifiedbytheBBCCprotocol,ortheyareinformativebecausetheypertaintotheVB5.2applicationfunctions.Inthiscasetheycanbechosenarbitrarilyinrangescompatiblewiththespecifications.Thelistofparameters,forwhichavalueistobeassignedbeforetheexecutionofatestsuite,isincludedinthePIXITproformaoftheBBCCprotocol.AnnexAofthepresentdocumentcontainsacopyofthisPIXITproformaparametertable.Forillustrationpurposes,thisproformatablehasbeencompletedwiththeparametervaluesusedintheMSCsexamplesofthepresentdocument.Allrepresentedparametersaredefinedusingthecorrectformat,usuallyhexadecimal,exceptforthefollowingwhichappearindecimalvalue:-transIdVal;-connRefNoVal;-connRefNos;-branchIdVal;-branchIds;-rejCauseOctet;-protErrCause.5.1.4StimulifortheIUTTheenvironmentoftheANortheSNisusingastimulustoinitiatetheexecutionofaBBCCprocedure.ThesestimuliappearasspecialsignalsintheMSCsassociatedwitheachTestPurpose.Thesesignalsaredescribedheretogetherwiththeirassociatedparameters:-AN_Faulty()generatesAN_FAULT;-SN_ConnEst(connRefNoVal,branchId)generatesALLOCandALLOC_COMP;-SN_Dealloc(connRefNoVal)generatesDEALLOC;-SN_Modify(connRefNoVal)generatesMODIFY;-SN_ModifyComp(connRefNoVal)generatesMODIFY_COMP;-SN_ModifyAbort(connRefNoVal)generatesMODIFY_COMP;-SN_AddBranch(connRefNoVal,branchId)generatesADD_BRANCH;-SN_UpdateBranch(connRefNoVal,branchId)generatesUPDATE_BRANCH;-SN_DropBranch(connRefNoVal,branchId)generatesDROP_BRANCH;-SN_ResetgeneratesBBCC_RESET;-SN_PresyncgeneratesBBCC_PRESYNC.SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)155.2TestpurposenamingconventionTheidentifieroftheTPisbuiltaccordingtothefollowingscheme.Table1:TPidentifiernamingconventionschemeIdentifier:VB5_____VB5VB5.2referencepointspecificationBBCCprotocolatinterfaceVB5.2AN:BBCCSystemintheAccessNetworkistheIUTSN:BBCCSystemintheServiceNodeistheIUT=procedureidentifierlike:STStartUpCEConnectionEstablishmentCRConnectionReleaseCMConnectionModifyBEBranchEstablishmentBRBranchReleaseHKHouseKeeping(Reset,Fault)CEHCommonErrorHandling=testcategory:CACapabilitytestsBVValidBehaviourtestsBIInvalidBehaviourtestsTITimertests=sequentialnumber:(01-99)Exampleoftestpurposeandtestcasename:VB5_BBCC_AN_CM_BV_02.SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)165.3Preamblesandpostambles5.3.1PreambledescriptionsThepreamblesareusedtobringtheIUTfrompower-onstatetothecorrectstatewhereatestcantakeplace.TheydifferwhethertheIUTisanANoraSN.5.3.1.1ANistheIUTP_AN_start:startstheANconfiguration.AN_EnvironmentTesterAN_IUTMSC VB5_BBCC_P_AN_startBBCC_RESET_ACC({ transIdVal 1 })BBCC_RESET({ transIdVal 1 })Figure3SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)17P_AN_1ptp:startsANandallocatesonePoint-to-Pointconnection.TesterAN_IUTAN_EnvironmentMSC VB5_BBCC_P_AN_1ptpALLOC({ transIdVal 2, connRefNoVal 1, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A001’H }, srvcPortConnIdIE { vpci ’A081’H, vci ’A201’H } })BBCC_RESET({ transIdVal 1 })BBCC_RESET_ACC({ transIdVal 1 })ALLOC_ACC({ transIdVal 2 })ALLOC_COMP({ transIdVal 3, connRefNoVal 1 })ALLOC_COMP_ACC({ transIdVal 3 })Figure4SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)18P_AN_1ptm:startsANandallocatesonePointtoMultipointconnection,firstbranchonlyisestablished.TesterAN_IUTAN_EnvironmentMSC VB5_BBCC_P_AN_1ptmALLOC({ transIdVal 2, connRefNoVal 257,
branchIdVal 4113, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE,
usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A003’H }, srvcPortConnIdIE { vpci ’A083’H, vci ’A203’H }})BBCC_RESET_ACC({ transIdVal 1 })BBCC_RESET({ transIdVal 1 })ALLOC_ACC({ transIdVal 2 })ALLOC_COMP({ transIdVal 3, connRefNoVal 257 })ALLOC_COMP_ACC({ transIdVal 3 })Figure5SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)19P_AN_1ptmTwoB:startsANandallocatesPointtoMultipointPtM1connection,PtM1connectionhastwobranches.TesterAN_IUTAN_EnvironmentMSC VB5_BBCC_P_AN_1ptmTwoBALLOC({ transIdVal 2, connRefNoVal 257, branchIdVal 4113, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A003’H, vci ’A103’H }, srvcPortConnIdIE { vpci ’A083’H, vci ’A203’H } })ADD_BRANCH({ transIdVal 4, connRefNoVal 257, branchIdVal 4114, usrPortConnIdIE { lgclUsrPortId ’A00102’H, vpci ’A004’H, vci ’A104’H } })ALLOC_COMP({ transIdVal 3, connRefNoVal 257 })ALLOC_COMP_ACC({ transIdVal 3 })BBCC_RESET({ transIdVal 1 })BBCC_RESET_ACC({ transIdVal 1 })ALLOC_ACC({ transIdVal 2 })ADD_BRANCH_ACC({ transIdVal 4 })Figure6SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)20P_AN_1ptmThreeB:startsANandallocatesPtM2PointtoMultipointconnection,PtM2connectionhasthreebranches.TesterAN_IUTAN_EnvironmentMSC VB5_BBCC_P_AN_1ptmThreeBBBCC_RESET({ transIdVal 1 })BBCC_RESET_ACC({ transIdVal 1 })ALLOC({ transIdVal 2, connRefNoVal 258, branchIdVal 4129, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A006’H, vci ’A106’H }, srvcPortConnIdIE { vpci ’A084’H, vci ’A204’H } })ALLOC_ACC({ transIdVal 2 })ALLOC_COMP({ transIdVal 3, connRefNoVal 258 })ALLOC_COMP_ACC({ transIdVal 3 })ADD_BRANCH({ transIdVal 4, connRefNoVal 258, branchIdVal 4130, usrPortConnIdIE { lgclUsrPortId ’A00102’H, vpci ’A007’H, vci ’A107’H } })ADD_BRANCH_ACC({ transIdVal 4 })ADD_BRANCH({ transIdVal 5, connRefNoVal 258, branchIdVal 4131, usrPortConnIdIE { lgclUsrPortId ’A00103’H, vpci ’A008’H, vci ’A108’H } })ADD_BRANCH_ACC({ transIdVal 5 })Figure7SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)21P_AN_2ptp:startsANandallocatestwoPoint-to-Pointconnections,PtP1andPtP2.TesterAN_IUTAN_EnvironmentMSC VB5_BBCC_P_AN_2ptpBBCC_RESET({ transIdVal 1 })BBCC_RESET_ACC({ transIdVal 1 })ALLOC({ transIdVal 2, connRefNoVal 1, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A001’H, vci ’A101’H }, srvcPortConnIdIE { vpci ’A081’H, vci ’A201’H } })ALLOC_ACC({ transIdVal 2 })ALLOC_COMP({ transIdVal 3, connRefNoVal 1 })ALLOC_COMP_ACC({ transIdVal 3 })ALLOC({ transIdVal 4, connRefNoVal 2, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00103’H, vpci ’A00B’H, vci ’A10B’H }, srvcPortConnIdIE { vpci ’A086’H, vci ’A206’H } })ALLOC_ACC({ transIdVal 4 })ALLOC_COMP({ transIdVal 5, connRefNoVal 2 })ALLOC_COMP_ACC({ transIdVal 5 })Figure8SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)22P_AN_2ptm:startsANandallocatestwoPointtoMultipointconnections,PtM1connectionhastwobranches,PtM2hasthreebranches.TesterAN_IUTAN_EnvironmentMSC VB5_BBCC_P_AN_2ptmBBCC_RESET({ transIdVal 1 })BBCC_RESET_ACC({ transIdVal 1 })ALLOC({ transIdVal 2, connRefNoVal 257, branchIdVal 4113,aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A003’H, vci ’A103’H }, srvcPortConnIdIE { vpci ’A083’H, vci ’A203’H } })ALLOC_ACC({ transIdVal 2 })ALLOC_COMP({ transIdVal 3, connRefNoVal 257 })ALLOC_COMP_ACC({ transIdVal 3 })ALLOC({ transIdVal 4, connRefNoVal 258, branchIdVal 4129, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A006’H, vci ’A106’H }, srvcPortConnIdIE { vpci ’A084’H, vci ’A204’H } })ALLOC_ACC({ transIdVal 4 })ALLOC_COMP({ transIdVal 5, connRefNoVal 258 })ALLOC_COMP_ACC({ transIdVal 5 })Figure9SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)23P_AN_1ptp1ptm:startsANandallocatesonePoint-to-PointPointtoMultipointconnections.TesterAN_IUTAN_EnvironmentMSC VB5_BBCC_P_AN_1ptp1ptmALLOC({ transIdVal 2, connRefNoVal 1, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A001’H, vci ’A101’H }, srvcPortConnIdIE { vpci ’A081’H, vci ’A201’H } })BBCC_RESET({ transIdVal 1 })BBCC_RESET_ACC({ transIdVal 1 })ALLOC_ACC({ transIdVal 2 })ALLOC_COMP({ transIdVal 3, connRefNoVal 1 })ALLOC_COMP_ACC({ transIdVal 3 })ALLOC({ transIdVal 4, connRefNoVal 257, branchIdVal 4113, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A003’H, vci ’A103’H }, srvcPortConnIdIE { vpci ’A083’H, vci ’A203’H } })ALLOC_ACC({ transIdVal 4 })ALLOC_COMP({ transIdVal 5, connRefNoVal 257 })ALLOC_COMP_ACC({ transIdVal 5 })Figure10SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)245.3.1.2SNistheIUTP_SN_start:startstheSNconfiguration.TesterSN_EnvironmentSN_IUTMSC VB5_BBCC_P_SN_startBBCC_RESET({ transIdVal 0 })SN_RestartBBCC_RESET_ACC({ transIdVal 0 })Figure11SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)25P_SN_1ptp:startsSNandallocatesonePoint-to-Pointconnection.SN_EnvironmentTesterSN_IUTMSC VB5_BBCC_P_SN_1ptpALLOC({ transIdVal 1, connRefNoVal 1,aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A001’H, vci ’A101’H }, srvcPortConnIdIE { vpci ’A081’H, vci ’A201’H } })ALLOC_COMP({ transIdVal 2, connRefNoVal 1 })SN_ConnEst(1, 0)SN_RestartALLOC_COMP_ACC({ transIdVal 2 })ALLOC_ACC({ transIdVal 1 })BBCC_RESET_ACC({ transIdVal 0 })BBCC_RESET({ transIdVal 0 })Figure12SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)26P_SN_1ptm:startsSNandallocatesonePointtoMultipointconnection,firstbranchonlyisestablished.TesterSN_EnvironmentSN_IUTMSC VB5_BBCC_P_SN_1ptmALLOC_COMP({ transIdVal 2, connRefNoVal 257 })ALLOC({ transIdVal 1, connRefNoVal 257, branchIdVal 4113, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A003’H, vci ’A103’H }, srvcPortConnIdIE { vpci ’A083’H, vci ’A203’H } })SN_ConnEst(257, 4113)BBCC_RESET_ACC({ transIdVal 0 })BBCC_RESET({ transIdVal 0 })SN_RestartALLOC_COMP_ACC({ transIdVal 2 })ALLOC_ACC({ transIdVal 1 })Figure13SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)27P_SN_1ptmTwoB:startsSNandallocatesPtM1PointtoMultipointconnection,PtM1connectionhastwobranches.SN_EnvironmentTesterSN_IUTMSC VB5_BBCC_P_SN_1ptmTwoBADD_BRANCH({ transIdVal 3, connRefNoVal 257, branchIdVal 4114, usrPortConnIdIE { lgclUsrPortId ’A00102’H, vpci ’A004’H, vci ’A104’H } })ALLOC_COMP{ transIdVal 2, connRefNoVal 257 })ALLOC_ACC({ transIdVal 1 })ALLOC({ transIdVal 1, connRefNoVal 257, branchIdVal 4113, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A003’H, vci ’A103’H }, srvcPortConnIdIE { vpci ’A083’H, vci ’A203’H } })SN_ConnEst(257, 4113)BBCC_RESET_ACC({ transIdVal 0 })BBCC_RESET({ transIdVal 0 })SN_RestartADD_BRANCH_ACC({ transIdVal 3 })SN_AddBranch(257, 4114)ALLOC_COMP_ACC({ transIdVal 2 })Figure14SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)28P_SN_1ptmThreeB:startsANandallocatesPtM2PointtoMultipointconnection,PtM2connectionhasthreebranches.SN_EnvironmentSN_IUTTesterMSC VB5_BBCC_P_SN_1ptmThreeBADD_BRANCH_ACC({ transIdVal 4 })ADD_BRANCH({ transIdVal 4, connRefNoVal 258, branchIdVal 4131, usrPortConnIdIE { lgclUsrPortId ’A00103’H, vpci ’A008’H, vci ’A108’H } })SN_AddBranch(258, 4131)ADD_BRANCH_ACC({ transIdVal 3 })ADD_BRANCH({ transIdVal 3, connRefNoVal 258, branchIdVal 4130, usrPortConnIdIE { lgclUsrPortId ’A00102’H, vpci ’A007’H, vci ’A107’H } })SN_AddBranch(258, 4130)ALLOC_COMP_ACC({ transIdVal 2 })ALLOC_COMP({ transIdVal 2, connRefNoVal 258 })ALLOC_ACC({ transIdVal 1 })ALLOC({ transIdVal 1, connRefNoVal 258, branchIdVal 4129, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A006’H, vci ’A106’H }, srvcPortConnIdIE { vpci ’A084’H, vci ’A204’H }})SN_ConnEst(258, 4129)BBCC_RESET_ACC({ transIdVal 0 })BBCC_RESET({ transIdVal 0 })SN_RestartFigure15SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)29P_SN_2ptp:startsANandallocatestwoPoint-to-Pointconnections.SN_EnvironmentSN_IUTTesterMSC VB5_BBCC_P_SN_2ptpALLOC_COMP_ACC({ transIdVal 4 })ALLOC_COMP({ transIdVal 4, connRefNoVal 2 })ALLOC_ACC({ transIdVal 3 })ALLOC({ transIdVal 3, connRefNoVal 2, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00103’H, vpci ’A00B’H, vci ’A10B’H }, srvcPortConnIdIE { vpci ’A086’H, vci ’A206’H } })SN_ConnEst(2, 0)ALLOC_COMP_ACC({ transIdVal 2 })ALLOC_COMP({ transIdVal 2, connRefNoVal 1 })ALLOC_ACC({ transIdVal 1 })ALLOC({ transIdVal 1, connRefNoVal 1, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A001’H, vci ’A101’H },srvcPortConnIdIE { vpci ’A081’H, vci ’A201’H } })SN_ConnEst(1, 0)BBCC_RESET_ACC({ transIdVal 0 })BBCC_RESET({ transIdVal 0 })SN_RestartFigure16SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)30P_SN_2ptm:startsANandallocatestwoPointtoMultipointconnections,PtM1connectionhastwobranches,PtM2hasthree.SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)31SN_EnvironmentSN_IUTTesterMSC VB5_BBCC_P_SN_2ptmALLOC_COMP_ACC({ transIdVal 4 })ALLOC_COMP({ transIdVal 4, connRefNoVal 258 })ALLOC_ACC({ transIdVal 3 })ALLOC({ transIdVal 3, connRefNoVal 258, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A006’H, vci ’A106’H }, srvcPortConnIdIE { vpci ’A084’H, vci ’A204’H } })SN_ConnEst(258, 4129)ALLOC_COMP_ACC({ transIdVal 2 })ALLOC_COMP({ transIdVal 2, connRefNoVal 257 })ALLOC_ACC({ transIdVal 1 })ALLOC({ transIdVal 1, connRefNoVal 257, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A003’H, vci ’A103’H }, srvcPortConnIdIE { vpci ’A083’H, vci ’A203’H } })SN_ConnEst(257, 4113)BBCC_RESET_ACC({ transIdVal 0 })BBCC_RESET({ transIdVal 0 })SN_RestartFigure17SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)32P_SN_1ptp1ptm:startsANandallocatesonePoint-to-PointPointtoMultipointconnections.SN_EnvironmentSN_IUTTesterMSC VB5_BBCC_P_SN_1ptp1ptmALLOC_COMP_ACC({ transIdVal 4 })ALLOC_COMP({ transIdVal 4, connRefNoVal 257 })ALLOC_ACC({ transIdVal 3 })ALLOC({ transIdVal 3, connRefNoVal 257, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A003’H, vci ’A103’H }, srvcPortConnIdIE { vpci ’A083’H, vci ’A203’H } })SN_ConnEst(257, 4113)ALLOC_COMP_ACC({ transIdVal 2 })ALLOC_COMP({ transIdVal 2, connRefNoVal 1 })ALLOC_ACC({ transIdVal 1 })ALLOC({ transIdVal 1, connRefNoVal 1, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A001’H, vci ’A101’H }, srvcPortConnIdIE { vpci ’A081’H, vci ’A201’H } })SN_ConnEst(1, 0)BBCC_RESET_ACC({ transIdVal 0 })BBCC_RESET({ transIdVal 0 })SN_RestartFigure18SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)335.3.2PostambledescriptionsNopostambleisusedinthistestsuite.6TestPurposesdefinitions6.1ANistheIUT6.1.1Basiccapabilitytests(CA)ThistestverifiesthecapabilityoftheANtoexchangevalidmessageswiththetester.ItconsistsinstartinguptheANBBCC.StartUpprocedure(ST).VB5_BBCC_AN_ST_CA_01ReferenceEN301217-1[3]:13.6.4.5PurposeCheckstartupofBBCCTestdescriptionThetestersetsupthelayer2(SAALestablishment)thenitsendsaBBCC_RESETPDU(RESETcompleteLSP)PasscriteriaCheckthatthetesterisreceivingtheBBCC_RESET_ACCSelectionNonePreambleNonePostambleNoneAdditionaltestingTheANenvironmentreceivesmeeBBCCStartTrafficIndatSAALestablishment,thenceeBBCCResetIndAN_EnvironmentAN_IUTTesterMSC VB5_BBCC_AN_ST_CA_01BBCC_RESET_ACC({ transIdVal 20 })BBCC_RESET({ transIdVal 20 })Figure19SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)346.1.2ConnectionEstablishmentprocedure(CE)6.1.2.1PointtoPointConnectionEstablishmentprocedureAllocation.VB5_BBCC_AN_CE_BV_01ReferenceEN301217-1[3]:13.6.2.1.2PurposeCheckallocation(simplereservation)TestdescriptionThetesterissuesanALLOCPDUwithmandatoryparametersPasscriteriaCheckthatthetesterisreceivinganALLOC_ACCPDUwithinT_AlloctimeSelectionNonePreambleP_AN_startPostambleNoneAdditionaltestingceeAllocIndissenttoANenvironmentAN_EnvironmentTesterAN_IUTVB5_BBCC_P_AN_startMSC VB5_BBCC_AN_CE_BV_01ALLOC_ACC({ transIdVal 20 })ALLOC({ transIdVal 20, connRefNoVal 1, aTMTrfcDscrptrIE send, brdbndBcapIE, qoSParamsIE, usrPortConnIdIE { lgclUsrPortId ’A00101’H, vpci ’A001’H, vci ’A101’H }, srvcPortConnIdIE { vpci ’A081’H, vci ’A201’H } })Figure20SIST EN 301 217-3 V1.1.1:2003

ETSIETSIEN301217-3V1.1.1(2001-01)35BasedonprecedingtestpurposenumberedVB5_BBCC_AN_CE_BV_01,whichisusingasetofbasicmandatoryparameters(seeMSCfordetails),thefollowingadditionaltestpurposes,basedonvariationofALLOCPDUparameters,aredefined:B5_BBCC_AN_CE_BV_01aReferenceEN301217-1[3]:13.6.2.1.2PurposeCheckallocationwithALLOCPDUusingUserportconnectionidentifierdefinedwithVPCIonly,noVCISelectionNoneVB5_BBCC_AN_CE_BV_01bReferenceEN301217-1[3]:13.6.2.1.2PurposeCheckallocationwithALLOCPDUusingAlternateUserportVPCI2SelectionNoneVB5_BBCC_AN_CE_BV_01cReferenceEN301217-1[3]:13.6.2.1.2PurposeCheckallocationwithALLOCPDUusingAlternateServiceportVPCI1SelectionNoneVB5_BBCC_AN_CE_BV_01dReferenceEN301217-1[3]:13.6.2.1.2PurposeCheckallocationwithALLOCPDUusingABRsetupparameterSelectionA.63/1:ABRsupportVB5_BBCC_AN_CE_BV_01eReferenceEN301217-1[3]:13.6.2.1.2PurposeCheckallocationwithALLOCPDUusingCDVTdescriptorSelectionA.65/1:CDVTsupportVB5_BBCC_AN_CE_BV_01fReferenceEN301217-1[3]:13.6.2.1.2PurposeCheckallocationwithALLOCPDUusingEndtoendtransitdelaySelectionNoneVB5_BBCC_AN_CE_BV_01gReferenceEN301217-1[3]:13.6.2.1.2PurposeCheckallocationwithALLOCPDUusingAlternativeATMtrafficdescriptorSelectionA.54/11:ConnectioncharacteristicnegotiationprocedureduringconnectionestablishmentANDA.66/1:AlternativeATMtrafficdescriptorVB5_BBCC_AN_CE_BV_01hReferenceEN301217-1[3]:13.6.2.1.2PurposeCheckallocationwithALLOCPDUusingMinimumacceptableATMtrafficdescriptorSelectionA.54/11:Connectioncharacteristicnegotiationprocedureduringconnectionestablishment
...