SIST EN 301 217-4 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-4 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 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)

SIST EN 301 217-4 V1.1.1:2003 is the Slovenian identical standard to ETSI EN 301 217-4 for the VB5.2 reference point at the digital Service Node (SN). It defines the Abstract Test Suite (ATS), Abstract Test Method (ATM), ATS conventions, a partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma, and Protocol Conformance Test Report (PCTR) proformas for checking Broadband Bearer Connection Control (BBCC) between an Access Network (AN) and an SN.

It is aimed at people who need to test or assess VB5.2 implementations, especially AN and SN vendors, conformance laboratories, and acceptance or quality teams.

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

SIST EN 301 217-4 V1.1.1:2003 specifies how to test BBCC conformance at the VB5.2 reference point. The scope covers the physical, procedural and protocol requirements for the interface between an AN and an SN.

The document is organized into five clauses and six annexes. Clause 4 explains the test architecture, and clause 5 sets the ATS conventions. Annexes A to D provide the test suite and report proformas, while annexes E and F give supporting ASN.1 data definitions and Extended SDL process diagrams.

Annex	What it covers
A	ATS for BBCC at the VB5.2 interface, in TTCN.GR and TTCN.MP form
B	Partial PIXIT proforma for BBCC at the VB5.2 interface
C	PCTR proforma when testing BBCC in AN
D	PCTR proforma when testing BBCC in SN
E	ASN.1 data definitions for the ATS
F	Extended SDL process diagrams for the BBCC protocol

Clause 4 also makes clear that some behaviour cannot be fully controlled or observed through one point of observation, so extra testing may be needed when internal access is available. More elaborate multi-protocol system testing is outside the document’s scope.

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

SIST EN 301 217-4 V1.1.1:2003 defines a remote single-layer test method for VB5.2 BBCC testing. The Lower Tester (LT) is in the test system, and the Point of Control and Observation (PCO) is at the Data link Service Access Point (DSAP). In practice, testers work through BBCC protocol data rather than direct access to upper service primitives.

Test architecture and control

Clause 4 says the VB5.2 implementations are not required to expose direct access to the upper service boundary, so the ATS uses indirect control and observation. There is no explicit Upper Tester (UT), although some UT-like effects may be implied by the SUT. For users, this means the test plan must be based on what can actually be stimulated and checked on the interface.

ATS conventions

Clause 5 requires ATS types to be defined by reference, using the standard ASN.1 definitions. It also sets naming rules for test suite parameters, timers, constraints, PDUs and test cases. For a reader, this is important because it tells implementers how to map the standard into TTCN files and how to keep test results comparable.

Test case structure

Clause 5 defines a one-to-one mapping between test purposes and test cases. Test case names use a structured form that identifies the VB5.2 reference point, the protocol, the IUT role, the procedure, the category and a sequence number. That naming scheme helps laboratories select the right cases and keep reports traceable.

Preambles, defaults and timers

Clause 5 defines preambles for AN and SN starting states, and it states that there is no postamble because each test begins with a complete reset. It also defines standardized timers, supervision timing and operator-action timing. In practice, this means test execution starts from known states and uses controlled timing for repeatable verdicts.

PIXIT and report data

Annex B provides the partial PIXIT proforma, including test laboratory data, SUT information, protocol-layer information, required stimuli and parameter values. Annexes C and D provide the PCTR proformas for AN and SN, including identification, conformance status, static and dynamic summaries, and campaign results. These forms are what a lab fills in to document the test environment and the outcome.

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

• Abstract Test Suite (ATS) - The TTCN test suite used to check conformance of a VB5.2 implementation.
• Abstract Test Method (ATM) - The test approach used to control and observe the implementation during conformance testing.
• Protocol Implementation eXtra Information for Testing (PIXIT) - Implementation-specific information needed to run the ATS correctly.
• Protocol Conformance Test Report (PCTR) - The report form used to record conformance test results.
• Implementation Under Test (IUT) - The AN or SN implementation being assessed.
• Point of Control and Observation (PCO) - The interface point where test events are applied and observed.
• System Under Test (SUT) - The broader system that contains the IUT and related support functions.

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

SIST EN 301 217-4 V1.1.1:2003 is used by telecommunications engineers, test laboratories, and quality teams working on broadband access networks and service nodes. It is also relevant to vendors of AN and SN equipment who need to verify BBCC conformance before delivery or acceptance. Buyers and procurement teams can use the PCTR structure as a basis for acceptance evidence.

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

Clause 2 names the companion parts of the same VB5.2 family:

• EN 301 217-1 - interface specification that the ATS tests against.
• EN 301 217-2 - PICS proforma specification, used to describe implementation capabilities.
• EN 301 217-3 - test suite structure and test purposes, which the ATS implements.

It also relies on the conformance-testing framework and related protocol definitions:

• ETS 300 406, ISO/IEC 9646-1, ISO/IEC 9646-2, ISO/IEC 9646-7, and ISO/IEC 9646 - methodology and framework for conformance testing.
• ITU-T G.902 and ITU-T M.3010 - functional access network and management principles.
• ITU-T Q.2931, EN 300 443-1, EN 301 067-1, ITU-T Q.2961.3, ITU-T Q.2961.5, EN 301 005-4, and EN 301 068 - protocol and parameter definitions used in the ATS data and message structures.

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

SIST EN 301 217-4 V1.1.1:2003 contains the ATS in TTCN.GR and TTCN.MP form, plus the partial PIXIT and PCTR proformas used in actual conformance campaigns. The annexes also include ASN.1 data definitions and Extended SDL process diagrams that support test generation and interpretation.

It includes named test cases and test groups for connection establishment, release, modification, branch establishment, branch release, housekeeping, and common error handling. In practice, these are the scenarios a lab runs to see whether BBCC behaves correctly for normal, invalid and timing-related cases.

The document also provides the parameter names used to configure tests, such as connection references, branch identifiers, traffic descriptors, QoS parameters, and timer values. That gives implementers the exact information they must supply before a campaign can start.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.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 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)35.200Vmesniška in povezovalna opremaInterface and interconnection equipmentICS:Ta slovenski standard je istoveten z:EN 301 217-4 Version 1.1.1SIST EN 301 217-4 V1.1.1:2003en01-november-2003SIST EN 301 217-4 V1.1.1:2003SLOVENSKI
STANDARD
ETSIEN301217-4V1.1.1(2001-01)EuropeanStandard(Telecommunicationsseries)VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.2referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part4:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)2ReferenceDEN/SPAN-09047-4KeywordsAN,ATS,PIXIT,SN,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-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)3ContentsIntellectualPropertyRights.5Foreword.5Introduction.51Scope.72References.73Definitionsandabbreviations.83.1Definitions.83.2Abbreviations.94Testarchitecture.104.1AbstractTestMethod(ATM).104.2Scopeoftestpurposes/testcasesandadditionaltesting.115ATSconventions.125.1Namingconventions.125.1.1Declarationspart.125.1.1.1Testsuitetypeandstructuredtypedefinitions-ByReference.125.1.1.2Testsuiteparameterdeclarations.125.1.1.3Testcaseselectionexpressiondefinitions.125.1.1.4Testcasevariabledeclarations.125.1.1.5Timerdeclarations.125.1.1.6ASPtypedefinitions.135.1.1.7PDUnames.135.1.2Constraintsnaming.145.1.3Simplifiedrepresentationofparametersinconstraints.145.1.4Dynamicpart.145.1.4.1Testcaseidentifier.145.1.4.2Preambleidentifier.155.1.4.3Postambleidentifier.165.1.4.4Defaultidentifier.16AnnexA(normative):ATSforBBCCatVB5.2interface.17A.1TheTTCNGraphicalform(TTCN.GR).17A.2TheTTCNMachineProcessableform(TTCN.MP).17AnnexB(normative):PartialPIXITproformaforBBCCatVB5.2interface.18B.1Identificationsummary.18B.2ATSsummary.18B.3Testlaboratory.18B.4Clientidentification.18B.5SUT.19B.6Protocollayerinformation.19B.6.1Protocolidentification.19B.6.2IUTinformation.20B.6.2.1StimulifortheIUT.20B.6.2.2PIXITParametervalues.21SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)4AnnexC(normative):ProtocolConformanceTestReport(PCTR)proformawhentestingBBCCinAN.23C.1Identificationsummary.23C.1.1Protocolconformancetestreport.23C.1.2IUTidentification.23C.1.3Testingenvironment.23C.1.4Limitsandreservation.24C.1.5Comments.24C.2IUTconformancestatus.24C.3Staticconformancesummary.24C.4Dynamicconformancesummary.25C.5Staticconformancereviewreport.25C.6Testcampaignreport.26C.7Observations.27AnnexD(normative):ProtocolConformanceTestReport(PCTR)proformawhentestingBBCCinSN.28D.1Identificationsummary.28D.1.1Protocolconformancetestreport.28D.1.2IUTidentification.28D.1.3Testingenvironment.28D.1.4Limitsandreservation.29D.1.5Comments.29D.2IUTconformancestatus.29D.3Staticconformancesummary.29D.4Dynamicconformancesummary.30D.5Staticconformancereviewreport.30D.6Testcampaignreport.31D.7Observations.32AnnexE(informative):ASN.1datadefinitionsfortheAbstractTestSuite.33AnnexF(informative):ExtendedSDLprocessdiagramsforBBCCprotocol.41History.42SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.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).Thepresentdocumentispart4ofamulti-partstandardcoveringtheinterfacesattheVB5.2referencepointasdescribedbelow:Part1:"Interfacespecification";Part2:"ProtocolImplementationConformanceStatement(PICS)specification";Part3:"TestSuiteStructureandTestPurposes(TSS&TP)";Part4:"AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)".NationaltranspositiondatesDateofadoptionofthisEN:19January2001DateoflatestannouncementofthisEN(doa):30April2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31October2001DateofwithdrawalofanyconflictingNationalStandard(dow):31October2001IntroductionGeneralTheworkonanewbroadbandVBreferencepointconceptwasinitiatedbyETSITechnicalCommitteeSPStoconsiderpossiblenewstructuresandreferencepointsfortheconnectionofnewbroadbandandcombinednarrowband/broadbandaccessarrangementstoServiceNodes(SN),inco-operationwithotherTCs.TheVB5referencepointconcept,basedonITU-TRecommendationG.902[8],wassplitintotwovariants.ThefirstvariantbasedonanATMcross-connectwithprovisionedconnectivity,calledtheVB5.1referencepoint,isdescribedinthepresentdocument.Theothervariantwhichfurtherenableson-demandconnectivitywithintheAN,calledtheVB5.2referencepoint,isbyEN301217-1[1].SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)6RelationshipbetweentheVB5.1andVB5.2referencepointconceptsVB5.2extendsthecapabilitiesattheVB5.1referencepointtoincludeon-demandconnectivityintheANunderthecontrolofSN.ThemajorcommonfeaturesbetweentheVB5.1andVB5.2interfacesare:-bothVB5interfacessupportB-ISDNaswellasnarrowbandandothernon-B-ISDNcustomeraccesstypes;-bothVB5interfacessupportATMmultiplexing/cross-connectingintheANattheVPand/orVClevel.TheRealTimeManagementCo-ordination(RTMC)protocoliscommonfortheVB5.1andtheVB5.2referencepoints.SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)71ScopeThepresentdocumentspecifiestheAbstractTestSuite(ATS),theAbstractTestMethod(ATM),ATSconventions,thepartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformafortestingtheconformityofanimplementationtotheBBCCspecificationofinterfacesattheVB5.2referencepointbetweenanAccessNetwork(AN)andaServiceNode(SN).Aproformaforthetestingreport(PCTR)isalsoincluded.Thereareinfacttwoseparatetestsuites,aswellastwoPCTRproformas,oneversionfortestingtheconformityofanANimplementation,theotheroneforaSN.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN301217-1(V1.2.2):"VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.2referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part1:Interfacespecification".[2]ETSIEN301217-2(V1.1.3):"VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.2referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part2:ProtocolImplementationConformanceStatement(PICS)proformaspecification".[3]ETSIEN301217-3(V1.1.1):"VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.2referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part3:TestSuiteStructureandTestPurposes(TSS&TP)".[4]ETSIETS300406(1995):"MethodsforTestingandSpecification(MTS);Protocolandprofileconformancetestingspecifications;Standardizationmethodology".[5]ISO/IEC9646-1:"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[6]ISO/IEC9646-2:"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part2:Abstracttestsuitespecification".[7]ISO/IEC9646-7:"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part7:ProtocolImplementationConformanceStatement".[8]ITU-TRecommendationG.902:"FrameworkRecommendationonfunctionalaccessnetworks(AN)Architectureandfunctions,accesstypes,managementandservicenodeaspects".[9]ISO/IEC9646:"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework".[10]ITU-TRecommendationM.3010:"PrinciplesforaTelecommunicationsmanagementnetwork".[11]ITU-TRecommendationQ.2931:"BroadbandIntegratedServicesDigitalNetwork(B-ISDN)-DigitalSubscriberSignallingSystemNo.2(DSS2)-User-NetworkInterface(UNI)-Layer3specificationforbasiccall/connectioncontrol".SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)8[12]ETSIEN300443-1(V1.3.5):"BroadbandIntegratedServicesDigitalNetwork(B-ISDN);DigitalSubscriberSignallingSystemNo.two(DSS2)protocol;B-ISDNuser-networkinterfacelayer3specificationforbasiccall/bearercontrol;Part1:Protocolspecification[ITU-TRecommendationQ.2931(1995),modified]".[13]ETSIEN301067-1(V1.1.3):"BroadbandIntegratedServicesDigitalNetwork(B-ISDN);DigitalSubscriberSignallingSystemNo.two(DSS2)protocol;Connectioncharacteristics;Negotiationduringcall/connectionestablishmentphase;Part1:Protocolspecification[ITU-TRecommendationQ.2962(1996),modified]".[14]ITU-TRecommendationQ.2961.3:"DigitalSubscriberSignallingSystemNo.2-Additionaltrafficparameters:Signallingcapabilitiestosupporttrafficparametersfortheavailablebitrate(ABR)ATMtransfercapability".[15]ITU-TRecommendationQ.2961.5:"DigitalsubscribersignallingsystemNo.2-Additionaltrafficparameters:Additionaltrafficparametersforcelldelayvariationtoleranceindication".[16]ETSIEN301005-4(V1.1.2):"VInterfacesattheDigitalServiceNode(SN);InterfacesattheVB5.1ReferencePointfortheSupportofBroadbandorCombinedNarrowbandandBroadbandAccessNetworks(ANs);Part4:AbstractTestSuite(ATS)andPartialProtocolImplementationeXtraInformationforTesting(PIXIT)ProformaSpecification".[17]ETSIEN301068:"BroadbandIntegratedServicesDigitalNetwork(B-ISDN);DigitalSubscriberSignallingSystemNo.Two(DSS2)Protocol;ConnectionCharacteristics;ATMTransferCapabilityandTrafficParameterIndication".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingdefinitionsapply:-termsdefinedinEN301217-1[1];-termsdefinedinISO/IEC9646-1[5]andinISO/IEC9646-2[6].Inparticular,thefollowingtermsdefinedinISO/IEC9646[9]apply:AbstractTestSuite(ATS)AbstractTestMethod(ATM)ImplementationConformanceStatement(ICS)ImplementationUnderTest(IUT)ImplementationeXtraInformationforTesting(IXIT)LowerTester(LT)PICSproformaPIXITproformaPointofControlandObservation(PCO)ProtocolImplementationConformanceStatement(PICS)ProtocolImplementationeXtraInformationforTesting(PIXIT)ServiceAccessPoint(SAP)SinglePartyTesting(SPyT)SystemUnderTest(SUT)UpperTester(UT)TTCN.GRTTCN.MPProtocolConformanceTestReport(PCTR)PCTRproformaSIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)93.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:AALATMAdaptationLayerAAL-SAPAAL-ServiceAccessPointANAccessNetworkATMAsynchronousTransferModeBBCCBroadbandBearerConnectionControlB-ISDNBroadbandISDNB-ISUPBroadbandISDNSignallingUserPartB-UNIBroadbandUNIBABasic(rate)AccessCPECustomerPremisesEquipmentCPNCustomerPremisesNetworkETEquipmentTerminalFSMFiniteStateMachineIDIdentityIEInformationElementINIInter-NetworkInterfaceISDNIntegratedServicesDigitalNetworkLANLocalAreaNetworkLELocalExchangeLMELayerManagementEntityLMILocalManagementInterfaceLSPLogicalServicePortLUPLogicalUserPortMIBManagementInformationBaseMSCMessageSequenceChartN-ISDNNarrowbandISDNNNINetwork-to-NetworkInterfaceOAMOperationsAdministrationandMaintenancePDHPlesiochronousDigitalHierarchyPDUProtocolDataUnitsPSPPhysicalServicePortPSTNPublicSwitchedTelephoneNetworkPUPPhysicalUserPortQ3"Q"managementinterfacereferencepointasITU-TRecommendationM.3010[10]RTMCRealTimeManagementCo-ordinationSAALSignallingATMAdaptationLayerSAPServiceAccessPointSARSegmentationandReassemblySDHSynchronousDigitalHierarchySDLSpecificationandDescriptionLanguageSDUServiceDataUnitsSNServiceNodeSNIServiceNodeInterfaceSPServicePortSPSSignallingProtocolsandSwitchingSSCFServiceSpecificCo-ordinationFunctionSSCOPServiceSpecificConnectionOrientedProtocolTCTechnicalCommitteesTETerminalEquipmentTMNTelecommunicationManagementNetworkTPTransmissionPathUNIUser-NetworkInterfaceVBBroadband"V"referencepointVCVirtualChannel(ATM)VCCVCConnectionVCCTVCCTerminationVCEVirtualChannelEntitySIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)10VCIVCIdentifierVCLVCLinkVCMEVCMultiplexEntityVPVirtualPathVPCVPConnectionVPCIVPConnectionIdentifierVPCTVPCTerminationVPEVPEntityVPIVPIdentifierVPLVPLinkVPMEVPMultiplexEntityVUPVirtualUserPort4Testarchitecture4.1AbstractTestMethod(ATM)ThisclausedescribestheAbstractTestMethod(ATM)andthePointofControlandObservation(PCO)usedtotesttheVB5.2BBCCprotocolfortheANandSNcomponents.TheremotetestmethodisusedforVB5.2BBCCconformancetesting,sincetheVB5.2implementationsarenotmandatedtoofferadirectaccesstotheupperserviceboundary(i.e.tothe"mee"and"cee"serviceprimitives).Theco-ordinationprocedurescanonlybeexpressedinaninformalway.SUTServiceProviderDLL&PHLlayersLTControlandDLconnectionendpointsVB5TestSystemIUTVB5-RTMCDL-DATAPCO/DSAPUTVB5BBCCPDUsFigure1:RemotesinglelayertestmethodappliedtotheVB5.2BBCCtestingLT:ALowerTester(LT)islocatedintheVB5.2testsystem.ItcontrolsandobservesthebehavioursoftheIUT.DSAP:AuniqueDatalinkServiceAccessPoint(DSAP)isdefinedattheVB5.2interfaceandcommonlyusedforexchangingservicedataoftheBBCCprotocolfunctionalentities.PCO:ThePCOforBBCCtestingislocatedontheDSAP.AlltesteventsatthePCOarespecifiedintermsofdatalinkAbstractServicePrimitives(ASPs)andnetworklayerPDUs.UT:NoexplicitUpperTester(UT)existsinthetestsystem.However,theSUTneedstocarryoutsomeUTfunctionstoachievesomeeffectsoftestco-ordinationprocedures.DesigningATS,thecapabilityoftheVB5.2applicationfunctionsmaybetakenintoaccount.ThecontrolsoftheIUTwillbeimpliedorinformallyexpressedintheATS,butnoassumptionshallbemaderegardingtheirfeasibilityorrealization.AnexampleofsuchinformalcontrolscouldbetoprovokestartupoftheIUTintheSN.AnexampleofimpliedcontrolsistheautomaticresponseofVB5.2applicationfunctionsintheAN.SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)11VB5-BBCC:ThePDUconveyingthisinformationwillbetransferredtoandfromthetesterviaasingle,dedicatedvirtualconnection.4.2Scopeoftestpurposes/testcasesandadditionaltestingThespecifiedIUTbehaviourcannotbefullycontrolledandobservedviaasinglePCO.Additionaltestingisthusrequiredtocoversuchbehaviour(insomecasesashortdescriptionofsuchadditionaltestingrequirementshasbeenappendedtotherelatedBBCCtestpurposes).Theactualtestingoftheserequirementscanonlybeperformedifadditionalmeansareprovidedtoaccessinternaldata,whichcannotbeinterrogatedviaBBCCmessages.Onewayofperformingthisistouseanad-hoctesterloadedintotheSUT,ifavailable.Thisisnottypicallythecase.ApracticalapproachistoconsiderthatanyNetworkElementcomprisesseveralprotocolinterfaces,eachofwhichisfirsttestedattheindividualprotocollevel(again,theseteststypicallyhavetoleaveoutanumberofprotocolrequirements,ifaremotetestmethodisused).Asecondhierarchicalleveloftesting(seefigure2)couldcoverasubstantialnumberofsuchuntestedrequirementsbycheckinginteractionsbetweentwoormoreprotocols,whichhavepassedindividualconformancetesting.Thisishoweveroutsidethescopeofthepresentdocument.ANorSNSystemTestDSS-2ProtocolProtocolQ3PlaneMan.ProtocolBBCCVB5.2(note1)NOTE:TheDSS-2protocolisnotterminatedintheAN.Figure2:ExampleofhierarchicaltestarchitectureappliedbeyondVB5.2testingSIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)125ATSconventionsThisclausedescribestheconventionsappliedtodefinetheATSandgivesthenamingconventionschosenforthedifferentelementsoftheATS.TheATSconventionsareintendedtogiveabetterunderstandingoftheATSbuttheydescribealsotheconventionsmadeforthedevelopmentoftheATS,thusforanylatermaintenancepurposesorfurtherdevelopmentoftheATS,theconventionsdescribedinthisclauseshallbeconsidered.5.1Namingconventions5.1.1DeclarationspartThisclausedescribesthenamingconventionschosenfortheelementsoftheATSdeclarationspart.5.1.1.1Testsuitetypeandstructuredtypedefinitions-ByReferenceInordertoavoidmisalignmentproblemswiththestandard,allthetypesusedinthisATShavebeendefinedbyreference.ThesameASN1filecontainingthestandardtypedefinitionshasbeenusedasmodulecontainingthereferencedtypedefinitions.EXAMPLE:TypeNameTypeReferenceModuleIdentifierTransIdTransIdDataModule5.1.1.2TestsuiteparameterdeclarationsThetestsuiteparameteridentifiersarecomposedofstringsinuppercaselettersandseparatedbyunderscores.IfthetestsuiteparameterreferencesaPIXITitem,theprefix"PIX_"isused.EXAMPLE:ParameterNameTypePIX_LSP_VPCI_1VPCI5.1.1.3TestcaseselectionexpressiondefinitionsThetestcaseselectionexpressionsarebasedonPICSorPIXITtestsuiteparameterdefinitions.EXAMPLE1:PIC_AN_multipointtakingthevalueTRUEorFALSE,basedonaPICSstatement.EXAMPLE2:PIX_MODIFY_COMP_REJtakingthevalueTRUEorFALSE,basedonaPIXITstatement.5.1.1.4TestcasevariabledeclarationsThetestcasevariableidentifiersarecomposedofstringinlowercaselettersstartingbythelowercasestring"TCV_".EXAMPLE:TCV_transIdVal5.1.1.5TimerdeclarationsSeveralkindsoftimerscanbedistinguished:1)standardized:Thosedefinedinthestandard,e.g.T_Alloc,usethesamenameasinthestandard,beginningwithacapital"T".TheirdurationisdefinedinthePIXITundersamename,forexamplePIX_T_Alloc.SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)132)fortestingsupervision:Inordertocontrolthedurationofindividualtestcases,aspecifictimeranditsduration,PIX_T_supervision,isdefined.3)foroperatoraction:InordertocontrolthedurationofactionrequiredtosetuptheIUTintoagivenstate,ortogenerateaspecificactionontheIUT,atimerT_Operatorisdefined.5.1.1.6ASPtypedefinitionsASPdefinitionsfollowthePDUspecificationwhenacorrespondingdefinitionexists,withtheadditionofaprefixlikeSN.EXAMPLE:SN_AddBranch5.1.1.7PDUnamesThePDUnamesusedintheTTCNtestsuitearetheonesusedintheASN.1declarations.Thecorrespondencewiththenamesusedinthespecificationsisgivenintable1.Table1PDUnamesinSpecificationsPDUnamesinTestSuiteALLOCAllocALLOC_ACCAllocAccALLOC_REJAllocRejALLOC_COMPAllocCompALLOC_COMP_ACCAllocCompAccALLOC_COMP_REJAllocCompRejDEALLOCDeallocDEALLOC_ACCDeallocAccBBCC_RESETBbccResetBBCC_RESET_ACCBbccResetAccBBCC_RESET_REJBbccResetRejBBCC_PRESYNCBbccPresyncBBCC_PRESYNC_ACCBbccPresyncAccBBCC_PRESYNC_REJBbccPresyncRejAN_FAULTAnFaultAN_FAULT_ACCAnFaultAccPROTOCOL_ERRORProtocolErrorMODIFYModifyMODIFY_ACCModifyAccMODIFY_REJModifyRejMODIFY_COMPModifyCompMODIFY_COMP_ACCModifyCompAccMODIFY_COMP_REJModifyCompRejMODIFY_ABORTModifyAbortMODIFY_ABORT_ACCModifyAbortAccMODIFY_ABORT_REJModifyAbortRejADD_BRANCHAddBranchADD_BRANCH_ACCAddBranchAccADD_BRANCH_REJAddBranchRejUPDATE_BRANCHUpdateBranchUPDATE_BRANCH_ACCUpdateBranchAccUPDATE_BRANCH_REJUpdateBranchRejDROP_BRANCHDropBranchDROP_BRANCH_ACCDropBranchAccDROP_BRANCH_REJDropBranchRejSIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)145.1.2ConstraintsnamingThisclausedescribesthenamingconventionschosenfortheelementsoftheATSconstraintspart.Constraintidentifierscommencewithlowercasec,followedbythePDU_TYPE,followedbyanumericalvaluelike001,002,etc.TypeDefinitionConstraintDefinitionExampleALLOCc_ALLOC_002ALLOC_COMPc_ALLOC_COMP_001Theconstraintvaluesaredefined,showingthespecifiedvalues,like‘49’Hforprotocoldiscriminator,orthevaluestobechosenbytheimplementer(PIX_xxforPIXITvalues)foreachInformationElement(IE).5.1.3SimplifiedrepresentationofparametersinconstraintsInordertoreducethecomplexityofconstraintdefinitions,somepackedparametershavebeenintroduced.TheseparametersarealloftypeOCTETSTRING.Theyrepresenttheconcatenationofseveralindividualfieldsunderauniquename.IntheTTCNconstraints,thevalueassignedtosuchparametersmayeitherappearexplicitly,(e.g.asahexadecimalvalue),oritmayberepresentedsymbolically,intheformofaPIXITparametername.Therearetwoclassesofpackedparameters:Oneclasscomprises5packedparameterswhicharespecifictotheBBCCprotocolandwhosecontentisderivedfromtheVB5.2interfacespecificationitself.Undernormalcircumstances,theparametersmsgCompatIndandiECompatInd,arealwaysassignedthevalue‘80’HwhileparametertransIdLengthisalwaysassignedthevalue‘03’H.Thelasttwo,usrPortConnIdIEOctet5andsrvcPortConnIdIEOctet5canbeassignedasmallnumberofdistinctvalues,dependingontheleveloftheidentifier(completeport,VPCIonly,VPCI/VCIcombination).Thesecondclasscontains7packedparameterswhosenameisoftype"XXX_contents".TheseparametersareusedinInformationElementsdefinedindetailinotherstandards,suchasITU-Trecommendations.Thesepackedparametersareusedtoholdtheentirecontentofthespecificpartoftheinformationelement,i.e.thepartwhichfollowsthecommonIEinformation.Theyareoftype"octetstring"ofvariablesize.Thevalueofthe"XXX_contents"parameterisalwaysrepresentedbyasymbolicPIXITname.Inotherwords,inTTCNconstraints,theparameterappearsundertheformof"XXX_contentsPIX_name"wherePIX_namerepresentsavaluetobespecifiedbytheimplementer,inaccordancewiththecodingrulesoftheInformationElementtowhichitbelongs.TheassignedvalueshallalsotakeaccountofthecapabilitiessupportedbytheVB5.2applicationfunctionsintheSystemUnderTest.Examplesare:broadbandbearercapabilityvalues,ATMtrafficdescriptorvalues,QOSparametervalues,endtoendtransitdelayvalues,OAMtrafficdescriptorvalues,ABRsetupparametervalues,CDVTdescriptorvalues.DetailsofthedefinitionofpackedparametersaregiveninannexE.5.1.4DynamicpartThisclausedescribesthenamingconventionschosenfortheelementsoftheATSdynamicpart.5.1.4.1TestcaseidentifierThereisaone-to-onemappingbetweentheTestPurposesandthetestcases.TheidentifierofaTCanditscorrespondingTestPurposeisdescribedintable2.SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)15Table2:TPidentifiernamingconventionschemeIdentifier:VB5_____VB5VB5.2referencepointspecificationBBCCprotocolatinterfaceVB5.2AN:BBCCSystemintheAccessNetworkistheIUTSN:BBCCSystemintheServiceNodeistheIUT=procedureidentifierlikeSTStartUpCEConnectionEstablishmentCRConnectionReleaseCMConnectionModifyBEBranchEstablishmentBRBranchReleaseHKHouseKeeping(Reset,Fault)CEHCommonErrorHandling=testcategory:CACapabilitytestsBVValidBehaviourtestsBIInvalidBehaviourtestsTITimertests=sequentialnumber:(01-99)Exampleoftestpurposeandtestcasename:VB5_BBCC_AN_CM_BV_025.1.4.2PreambleidentifierApreambledefinesasetofTTCNstatementsneededtoinitializetheIUTthencarrytheIUTtoaparticularstateoraparticularcallconfigurationsituationfromwhichthetestcaseshallstart.Hereisthelistofpreambles.ANistheIUTP_startAN:startstheANconfigurationP_AN_1ptp:startsANandallocatesonePointtoPointconnectionP_AN_1ptm:startsANandallocatesonePointtoMultipointconnection,firstbranchonlyisestablishedP_AN_1ptmTwoB:startsANandallocatesPointtoMultipointPtM1connection,PtM1connectionhastwobranchesP_AN_1ptmThreeB:startsANandallocatesPtM2PointtoMultipointconnection,PtM2connectionhasthreebranchesP_AN_2ptp:startsANandallocatestwoPoint-to-Pointconnections,PtP1andPtP2P_AN_2ptm:startsANandallocatestwoPointtoMultipointconnections,PtM1connectionhastwobranches,PtM2hasthreebranchesP_AN_1ptp1ptm:startsANandallocatesonePointtoPointandonePointtoMultipointconnectionsSIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)16SNistheIUTP_startSN:startstheSNconfigurationP_SN_1ptp:startsSNandallocatesonePoint-to-PointconnectionP_SN_1ptm:startsSNandallocatesonePointtoMultipointconnection,firstbranchonlyisestablishedP_SN_1ptmTwoB:startsSNandallocatesPtM1PointtoMultipointconnection,PtM1connectionhastwobranchesP_SN_1ptmThreeB:startsANandallocatesPtM2PointtoMultipointconnection,PtM2connectionhasthreebranchesP_SN_2ptp:startsANandallocatestwoPointtoPointconnectionsP_SN_2ptm:startsANandallocatestwoPointtoMultipointconnections,PtM1connectionhastwobranches,PtM2hasthreebranchesP_SN_1ptp1ptm:startsANandallocatesonePointtoPointandonePointtoMultipointconnections5.1.4.3PostambleidentifierThereisnopostambledefined,aseachnewtestisbeginningbyacompletereset,itcannotbecorruptedbysideeffectsofthepreviousexecutedtestcase.5.1.4.4DefaultidentifierAdefaultisasetofTTCNstatementscalledhereOtherwiseFail,whichisusedtocompletethebehaviourtreerelatedtothetestcase.ItcoverssomedifferentalternativesbringingthetestcasetoaFAILorINCONCLUSIVEverdict.SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)17AnnexA(normative):ATSforBBCCatVB5.2interfaceThisATShasbeenproducedusingtheTreeandTabularCombinedNotation(TTCN)accordingtoISO/IEC9646-3[9].TheATSwasdevelopedonaseparateTTCNsoftwaretoolandthereforetheTTCNtablesarenotcompletelyreferencedinthetableofcontents.TheATSitselfcontainsatestsuiteoverviewpartwhichprovidesadditionalinformationandreferences.A.1TheTTCNGraphicalform(TTCN.GR)TheTTCN.GRrepresentationofthisATSiscontainedinAdobePortableDocumentFormat™files(Suite_SN.PDFandSuite_AN.PDFcontainedinarchiveen_30121704v010101p0.ZIP)whichaccompaniesthepresentdocument.A.2TheTTCNMachineProcessableform(TTCN.MP)TheTTCN.MPrepresentationcorrespondingtothisATSiscontainedinASCIIfiles(Suite_SN.MPandSuite_AN.MPcontainedinarchiveen_30121704v010101p0.ZIP)whichaccompaniesthepresentdocument.NOTE:WhereanETSIAbstractTestSuite(inTTCN)ispublishedinboth.GRand.MPformatthesetwoformsshallbeconsideredequivalent.Intheeventthatthereappearstobesyntacticalorsemanticdifferencesbetweenthetwothentheproblemshallberesolvedandtheerroneousformat(whicheveritis)shallbecorrected.SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)18AnnexB(normative):PartialPIXITproformaforBBCCatVB5.2interfaceNotwithstandingtheprovisionsofthecopyrightclauserelatedtothetextofthepresentdocument,ETSIgrantsthatusersofthepresentdocumentmayfreelyreproducethePIXITproformainthisannexsothatitcanbeusedforitsintendedpurposesandmayfurtherpublishthecompletedPIXIT.ThePIXITproformaisbasedonISO/IEC9646-6.Anyadditionalinformationneededcanbefoundinthepresentdocument.B.1IdentificationsummaryTableB.1PIXITnumber:Testlaboratoryname:Dateofissue:Issuedto:B.2ATSsummaryTableB.2Protocolspecification:EN301217-1Protocoltobetested:ATSspecification:EN301217-4Abstracttestmethod:RemotetestmethodB.3TestlaboratoryTableB.3Testlaboratoryidentification:Testlaboratorymanager:Meansoftesting:SAPaddress:B.4ClientidentificationTableB.4Clientidentification:Clienttestmanager:Testfacilitiesrequired:SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)19B.5SUTTableB.5Name:Version:SCSnumber:Machineconfiguration:Operatingsystemidentification:IUTidentification:PICSreferenceforIUT:LimitationsoftheSUT:Environmentalconditions:B.6ProtocollayerinformationB.6.1ProtocolidentificationTableB.6Name:EN301217-1:VB5.2interfaceVersion:PICSreferences:EN301217-2SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)20B.6.2IUTinformationB.6.2.1StimulifortheIUTImplicitsendeventsareusedinTTCNtoindicatetheneedforastimulus.Theexpectedresultofstimulationisdefinedbytheconstraintassociatedtotheimplicitsendevent,whichspecifiestheparameterswhicharerelevanttothestimulus,suchasconnectionreference,portidentifiers,trafficparameters,etc.TheimplicitsendeventnamesareidenticaltotheresultingPDUnames.TableB.7:ActionsrequiredtostimulatetheIUTItemStimulinameACTIONSWhatactionshavetobetakento:Invocationdescription1AnFaultCausetheANtorequestnotificationtotheSNthatafaultregardingthespecifiedbearerconnectionhasbeendetected2AllocCausetheSNtorequesttheallocationofabearerconnectionaccordingtospecifiedparameters3AllocCompCausetheSNtorequesttocompletetheallocationofabearerconnectionaccordingtospecifiedparameters4DeallocCausetheSNtorequestthede-allocationofaspecifiedbearerconnection5ModifyCausetheSNtorequestthemodificationofaspecifiedbearerconnection6ModifyCompCausetheSNtorequesttocompletethemodificationofaspecifiedbearerconnection7ModifyAbortCausetheSNtorequesttoabortthemodificationofaspecifiedbearerconnection8AddBranchCausetheSNtorequesttheallocationofaspecifiedadditionalbranchtoapointtomultipointconnection9UpdateBranchCausetheSNtorequesttoupdatetheallocationofanadditionalbranchtoapointtomultipointconnection10DropBranchCausetheSNtorequestthedeletionofabranchofapointtomultipointconnection11BbccResetCausetheSNtorequesttheresetofspecifiedresourcesatLUPoranLSPandhencetherelevantbearerconnection(s)12BbccPresyncCausetheSNtoinvoketheBBCCrestartprocedureSIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)21B.6.2.2PIXITParametervaluesTableB.8:ParametervaluesItemParameternameParametertype(ASN1)ExplanationValueinimplementation1PIX_ALLOC_COMP_REJBOOLEANGuidestheConnectionControlFunction2PIX_MODIFY_COMP_REJ_BOOLEANGuidestheConnectionControlFunction3PIX_MODIFY_ABORT_REJBOOLEANGuidestheConnectionControlFunction4PIX_BBCC_PRESYNC_REJBOOLEANGuidestheConnectionControlFunction5PIX_simulate_congestionBOOLEANGuidestheConnectionControlFunction6PIX_ConnRefNoVal_PtP1ConnRefNoValPointtopointconnection7PIX_ConnRefNoVal_PtP2ConnRefNoValPointtopointconnection8PIX_ConnRefNoVal_Unknown_PtPConnRefNoValUnknownPointtopointconnection9PIX_ConnRefNoVal_PtM1ConnRefNoValPointtoMultipointconnection,twobranches10PIX_ConnRefNoVal_PtM2ConnRefNoValPointtoMultipointconnection,threebranches11PIX_ConnRefNoVal_Unknown_PtMConnRefNoValUnknownPointtoMultipointconnection12PIX_PtM1_BranchId1BranchIdValBranchId1ofPtM113PIX_PtM1_BranchId2BranchIdValBranchId2ofPtM114PIX_PtM1_Unknown_BranchIdBranchIdValBranchIdunknownofPtM115PIX_PtM2_BranchId1BranchIdValBranchId1ofPtM216PIX_PtM2_BranchId2BranchIdValBranchId2ofPtM217PIX_PtM2_BranchId3BranchIdValBranchId3ofPtM218PIX_PtMu_BranchId1BranchIdValBranchId1ofPtMu19PIX_LUP_Id1LogIdLUPId20PIX_LUP_Id2LogIdLUPId21PIX_LUP_Id3LogIdLUPId22PIX_LUP_VPCI1VPCIVPCIatLUPptp123PIX_LUP_VPCI2VPCIVPCIatLUPptpunknown24PIX_LUP_VPCI3VPCIVPCIatLUPptm125PIX_LUP_VPCI4VPCIVPCIatLUPptm126PIX_LUP_VPCI6VPCIVPCIatLUPptm227PIX_LUP_VPCI7VPCIVPCIatLUPptm228PIX_LUP_VPCI8VPCIVPCIatLUPptm229PIX_LUP_VPCIBVPCIVPCIatLUPptp230PIX_LUP_VPCICVPCIVPCIatLUPalternative31PIX_LUP_VCI1VCIVCIatLUPptp132PIX_LUP_VCI2VCIVCIatLUPptpunknown33PIX_LUP_VCI3VCIVCIatLUPptm134PIX_LUP_VCI4VCIVCIatLUPptm135PIX_LUP_VCI6VCIVCIatLUPptm236PIX_LUP_VCI7VCIVCIatLUPptm237PIX_LUP_VCI8VCIVCIatLUPptm238PIX_LUP_VCIBVCIVCIatLUPptp239PIX_LSP_VPCI1VPCIVPCIatLSPptp140PIX_LSP_VPCI3VPCIVPCIatLSPptm141PIX_LSP_VPCI4VPCIVPCIatLSPptm242PIX_LSP_VPCI6VPCIVPCIatLSPptp243PIX_LSP_VPCICVPCIVPCIatLSPalternative44PIX_LSP_VCI1VCIVCIatLSPptp145PIX_LSP_VCI3VCIVCIatLSPptm146PIX_LSP_VCI4VCIVCIatLSPptm247PIX_LSP_VCI6VCIVCIatLSPptp248PIX_endtoend_transit_delayOCTET_STRINGLengthis:(3-6)Defaultvalueis:3SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)22ItemParameternameParametertype(ASN1)ExplanationValueinimplementation49PIX_ATM_traffic_descriptorOCTET_STRINGLengthis:(0-50)Defaultvalueis:250PIX_ATM_altern_traffic_descriptorOCTET_STRINGLengthis:(0-50)Defaultvalueis:251PIX_minimum_ATM_traffic_descriptorOCTET_STRINGLengthis:(0-50)Defaultvalueis:252PIX_OAM_traffic_descriptorOCTET_STRINGLengthis:(2)Defaultvalueis:253PIX_Broadband_capabilityOCTET_STRINGLengthis:(3-4)Defaultvalueis:354PIX_Broadband_capability_ABROCTET_STRINGLengthis:(3-4)Defaultvalueis:355PIX_ABR_setup_parameterOCTET_STRINGLengthis:(2-28)Defaultvalueis:256PIX_QOS_parameterOCTET_STRINGLengthis:(2)Defaultvalueis:257PIX_CDVT_descriptorOCTET_STRINGLengthis:(3-18)Defaultvalueis:3TableB.9:TimervaluesItemParameterParametertypeExplanationValueinImplementation1PIX_T_AnFaultIntegerTimervalue2PIX_T_AllocIntegerTimervalue3PIX_T_AllocCompIntegerTimervalue4PIX_T_BbccResetIntegerTimervalue5PIX_T_BbccPresyncIntegerTimervalue6PIX_T_DeallocIntegerTimervalue7PIX_T_ModifyIntegerTimervalue8PIX_T_ModifyCompIntegerTimervalue9PIX_T_ModifyAbortIntegerTimervalue10PIX_T_AddBranchIntegerTimervalue11PIX_T_UpdateBranchIntegerTimervalue12PIX_T_DropBranchIntegerTimervalue13PIX_T_ConnEstIntegerTimervalue14PIX_T_ModificationIntegerTimervalue15PIX_T_BranchEstIntegerTimervalue16PIX_T_BbccStartupIntegerTimervalue17PIX_T_BbccRestartIntegerTimervalue18PIX_T_supervisionIntegerSupervisiontimerSIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)23AnnexC(normative):ProtocolConformanceTestReport(PCTR)proformawhentestingBBCCinANNotwithstandingtheprovisionsofthecopyrightclauserelatedtothetextofthepresentdocument,ETSIgrantsthatusersofthepresentdocumentmayfreelyreproducethePCTRproformainthisannexsothatitcanbeusedforitsintendedpurposesandmayfurtherpublishthecompletedPCTR.ThePCTRproformaisbasedonISO/IEC9646-6.Anyadditionalinformationneededcanbefoundinthepresentdocument.C.1IdentificationsummaryC.1.1ProtocolconformancetestreportTableC.1PCTRnumber:PCTRdate:CorrespondingSCTRnumber:CorrespondingSCTRdate:Testlaboratoryidentification:Testlaboratorymanager:Signature:C.1.2IUTidentificationTableC.2Name:Version:Protocolspecification:PICS:PreviousPCTRifany:C.1.3TestingenvironmentTableC.3PIXITnumber:ATSspecification:Abstracttestmethod:Meansoftestingidentification:Dateoftesting:Conformancelogreference(s):Retentiondateforlogreference(s):SIST EN 301 217-4 V1.1.1:2003

ETSIETSIEN301217-4V1.1.1(2001-01)24C.1.4LimitsandreservationAdditionalinformationrelevanttothetechnicalcontentsorfurtheruseofthetestreport,ortherightsandobligationsofthetestlaboratoryandtheclient,maybegivenhere.Suchinformationmayincluderestrictiononthepublicationofthereport.C.1.5CommentsAdditionalcommentsmaybegivenbyeithertheclientorthetestlaboratoryonanyofthecontentsofthePCTR,forexample,tonotedisagreementbetweenthetwoparties.C.2IUTconformancestatusThisIUThasorhasnotbeenshownbyconformanceassessmenttobenon-conformingtothespecifiedprotocolspecification.Striketheappropriatewo
...