General Information

Abstract

PIXIT proforma and ATS for DE/SPS-03046-1.

Status
Published
Publication Date
31-Aug-2001
ICS
35.200 - Interface and interconnection equipment
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
BC-T-338
Ref Project
ETSI EN 301 005-4 V1.1.2 (2000-05) - 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 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification

Buy Documents

SIST EN 301 005-4:2001 - Page 1 previewSIST EN 301 005-4:2001 - Page 2 previewSIST EN 301 005-4:2001 - Page 3 previewSIST EN 301 005-4:2001 - Page 4 preview
PreviousNext
Standard

SIST EN 301 005-4:2001

English language (38 pages)
Preview
Preview
e-Library read for
×1 day

Overview

SIST EN 301 005-4:2001 defines the Abstract Test Suite (ATS) and the partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for V interfaces at the digital Service Node (SN), specifically focusing on the VB5.1 reference point. This standard plays a crucial role in ensuring interoperability and conformity for broadband or combined narrowband and broadband Access Networks (ANs). By establishing a common testing framework and reporting structure, the document supports consistent implementation and assessment of the VB5.1 interface between Access Networks and Service Nodes in telecommunications environments.

Key Topics

  • VB5.1 Reference Point
    Specifies guidelines for the interface logic and control between broadband and/or narrowband Access Networks and the digital Service Node.

  • Abstract Test Suite (ATS)
    Outlines the structure and conventions for developing test cases, including the use of standardized notations (TTCN).

  • Partial PIXIT Proforma
    Provides a template for implementers to declare additional necessary information for testing, ensuring that all relevant factors are considered during protocol conformance evaluation.

  • Test Method and Architecture
    Describes remote test methods and points of control/observation, enabling effective validation of protocol behavior without direct access to the upper service boundary.

  • Protocol Conformance Test Report (PCTR)
    Includes standardized reporting templates for recording the results of protocol conformance testing, applicable for both Access Networks and Service Nodes.

Applications

  • Telecommunications Equipment Testing
    Essential for manufacturers and service providers developing and validating products that interface with broadband and combined narrowband/broadband networks according to the VB5.1 reference point.

  • Certification and Compliance
    Provides a standardized approach for protocol implementers and independent test laboratories to demonstrate compliance with European telecom standards, instilling confidence in multi-vendor environments.

  • Network Interoperability
    Facilitates integration of diverse Access Networks and Service Nodes by ensuring consistent interpretation and implementation of interface specifications, thus reducing deployment risks in B-ISDN, ISDN, and PSTN environments.

  • Implementation Guidance
    Serves as a technical reference for developers and network architects who need clear requirements and procedures for designing, implementing, and testing VB5.1 interfaces.

Related Standards

  • EN 301 005-1: V interfaces at the digital Service Node (SN); Part 1: Interface specification
  • EN 301 005-2: VB5.1 reference point; Protocol Implementation Conformance Statement (PICS) proforma specification
  • EN 301 005-3: Test Suite Structure and Test Purposes (TSS&TP) specification
  • ISO/IEC 9646 Series: Information technology - OSI Conformance testing methodology and framework
  • ITU-T G.902: Functional access networks - Architecture and functional principles
  • EN 301 217-1: Interfaces at the VB5.2 reference point for support of broadband and combined networks

Summary

SIST EN 301 005-4:2001 provides a comprehensive framework for testing and validating the conformity of VB5.1 interfaces in digital Service Nodes and Access Networks. Through detailed testing conventions, standardized reporting, and structured proformas, the standard ensures reliable implementation and integration of telecommunications equipment, supporting network interoperability, compliance, and robust service provision in modern broadband and mixed-access network environments.

Buy Documents

SIST EN 301 005-4:2001 - Page 1 previewSIST EN 301 005-4:2001 - Page 2 previewSIST EN 301 005-4:2001 - Page 3 previewSIST EN 301 005-4:2001 - Page 4 preview
PreviousNext
Standard

SIST EN 301 005-4:2001

English language (38 pages)
Preview
Preview
e-Library read for
×1 day

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.

UKAS United Kingdom Verified
Visit Website

NYCE

Mexican standards and certification body.

EMA Mexico Verified
Visit Website

Sponsored listings

Frequently Asked Questions

SIST EN 301 005-4: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 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification". This standard covers: PIXIT proforma and ATS for DE/SPS-03046-1.

PIXIT proforma and ATS for DE/SPS-03046-1.

SIST EN 301 005-4: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-4:2001 is associated with the following European legislation: Standardization Mandates: BC-T-338. 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-4: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 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification35.200Vmesniška in povezovalna opremaInterface and interconnection equipmentICS:Ta slovenski standard je istoveten z:EN 301 005-4 Version 1.1.2SIST EN 301 005-4:2001en01-september-2001SIST EN 301 005-4:2001SLOVENSKI
STANDARD
ETSIEN301005-4V1.1.2(2000-05)EuropeanStandard(Telecommunicationsseries)VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.1referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part4:AbstractTestSuite(ATS)andpartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformaspecificationSIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)2ReferenceDEN/SPS-09046-4KeywordsAN,B-ISDN,ISDN,SN,PSTN,Vinterface,V5interface,VB5interface,ATS,PIXITETSI650RoutedesLuciolesF-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-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)3ContentsIntellectualPropertyRights.5Foreword.5Introduction.51Scope.72References.73Definitionsandabbreviations.83.1Definitions.83.2Abbreviations.84Testarchitecture.94.1AbstractTestMethod(ATM).94.2Scopeoftestpurposesandadditionaltesting.105ATSconventions.115.1Namingconventions.115.1.1Declarationspart.115.1.1.1Testsuitetypeandstructuredtypedefinitions"ByReference".115.1.1.2TestsuiteconstantdeclarationsByReference.115.1.1.3Testsuiteparameterdeclarations.125.1.1.4Testcaseselectionexpressiondefinitions.125.1.1.5Testsuitevariabledeclarations.125.1.1.6Timerdeclarations.125.1.1.7ASPtypedefinitions.125.1.1.8Aliasdefinitions.125.1.2Constraintsnaming.125.1.3Dynamicpart.135.1.3.1Testcaseidentifier.135.1.3.2Preambleidentifier.145.1.3.3Postambleidentifier.145.1.3.4Defaultidentifier.14AnnexA(normative):ATSforVB5.1interface.15A.1TheTTCNGraphicalform(TTCN.GR).15A.2TheTTCNMachineProcessableform(TTCN.MP).15AnnexB(normative):PartialPIXITproformaforVB5.1interface.16B.1Identificationsummary.16B.2ATSsummary.16B.3Testlaboratory.16B.4Clientidentification.16B.5SUT.17B.6Protocollayerinformation.17B.6.1Protocolidentification.17B.6.2IUTinformation.17B.6.2.1Implicitsendevents.17B.6.2.2Parametervalues.18SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)4AnnexC(normative):ProtocolConformanceTestReport(PCTR)proformawhentestingAN.19C.1Identificationsummary.19C.1.1Protocolconformancetestreport.19C.1.2IUTidentification.19C.1.3Testingenvironment.19C.1.4Limitsandreservation.20C.1.5Comments.20C.2IUTconformancestatus.20C.3Staticconformancesummary.20C.4Dynamicconformancesummary.21C.5Staticconformancereviewreport.21C.6Testcampaignreport.22C.7Observations.23AnnexD(normative):ProtocolConformanceTestReport(PCTR)proformawhentestingSN.24D.1Identificationsummary.24D.1.1Protocolconformancetestreport.24D.1.2IUTidentification.24D.1.3Testingenvironment.24D.1.4Limitsandreservation.25D.1.5Comments.25D.2IUTconformancestatus.25D.3Staticconformancesummary.25D.4Dynamicconformancesummary.26D.5Staticconformancereviewreport.26D.6Testcampaignreport.27D.7Observations.29AnnexE(normative):ASN.1datadefinitionsforRTMCprotocol.30Bibliography.37History.38SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.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).Thepresentdocumentispart4ofamulti-partENcoveringVinterfacesatthedigitalServiceNode(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[8],wassplitintotwovariants.ThefirstvariantbasedonanATMcross-connectwithprovisionedconnectivity,calledtheVB5.1referencepoint,isdescribedinthepresentdocument.Theothervariantwhichfurtherenableson-demandconnectivitywithintheAN,calledtheVB5.2referencepoint,iscoveredbyEN301217-1[10].SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.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-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)71ScopeThepresentdocumentspecifiestheAbstractTestSuite(ATS),theAbstractTestMethod(ATM),ATSconventions,thepartialProtocolImplementationeXtraInformationforTesting(PIXIT)proformafortestingtheconformityofanimplementationtothespecificationofinterfacesattheVB5.1referencepointbetweenanAccessNetwork(AN)andaServiceNode(SN).Aproformaforthetestingreport(PCTR)isalsoincluded.Thereareinfacttwoseparatetestsuites,aswellastwoPCTRproformas,oneversionfortestingtheAN,theotheronefortestingtheSN.TheATSisbasedontheTestSuiteSpecification&TestPurposesspecifiedinEN301005-3[3].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]ETSIEN301005-3(V1.1):"VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.1referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part3:TestSuiteStructureandTestPurposes(TSS&TP)specification".[4]ISO/IEC9646-1:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[5]ISO/IEC9646-2:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part2:Abstracttestsuitespecification".[6]ISO/IEC9646-3:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part3:TheTreeandTabularCombinedNotation(TTCN)".[7]ISO/IEC9646-6:"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part6:Protocolprofiletestspecification".[8]ITU-TRecommendationG.902:"FrameworkRecommendationonfunctionalaccessnetworks(AN)-Architectureandfunctions,accesstypes,managementandservicenodeaspects".[9]ITU-TRecommendationM.3010:"PrinciplesforaTelecommunicationsmanagementnetwork".[10]ETSIEN301217-1:"VinterfacesatthedigitalServiceNode(SN);InterfacesattheVB5.2referencepointforthesupportofbroadbandorcombinednarrowbandandbroadbandAccessNetworks(ANs);Part1:Interfacespecification".SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)83Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingdefinitionsapply:-termsdefinedinEN301005-1[1];-termsdefinedinISO/IEC9646-1[4]andinISO/IEC9646-2[5].Inparticular,thefollowingtermsdefinedinISO/IEC9646apply: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)PCTRproforma3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:AALATMAdaptationLayerAAL-SAPAAL-ServiceAccessPointANAccessNetworkATMAsynchronousTransferModeB-ISDNBroadbandISDNB-ISUPBroadbandISDNSignallingUserPartB-UNIBroadbandUNIBABasic(rate)AccessCPECustomerPremisesEquipmentCPNCustomerPremisesNetworkETEquipmentTerminalFSMFiniteStateMachineIDIdentityIEInformationElementINIInter-NetworkInterfaceISDNIntegratedServicesDigitalNetworkLANLocalAreaNetworkLELocalExchangeLMELayerManagementEntityLMILocalManagementInterfaceLSPLogicalServicePortLUPLogicalUserPortMIBManagementInformationBaseSIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)9MSCMessageSequenceChartN-ISDNNarrowbandISDNNNINetwork-to-NetworkInterfaceOAMOperationsAdministrationandMaintenancePDHPlesiochronousDigitalHierarchyPDUProtocolDataUnitsPSPPhysicalServicePortPSTNPublicSwitchedTelephoneNetworkPUPPhysicalUserPortQ3"Q"managementinterfacereferencepointasITU-TRecommendationM.3010[9]RTMCRealTimeManagementCo-ordinationSAALSignallingATMAdaptationLayerSAPServiceAccessPointSARSegmentationandReassemblySDHSynchronousDigitalHierarchySDLSpecificationandDescriptionLanguageSDUServiceDataUnitsSNServiceNodeSNIServiceNodeInterfaceSPServicePortSPSSignallingProtocolsandSwitchingSSCFServiceSpecificCo-ordinationFunctionSSCOPServiceSpecificConnectionOrientedProtocolTCTechnicalCommitteesTETerminalEquipmentTMNTelecommunicationManagementNetworkTPTransmissionPathUNIUser-NetworkInterfaceVBBroadband"V"referencepointVCVirtualChannel(ATM)VCEVirtualChannelEntityVPVirtualPathVPCVPConnectionVPCIVPConnectionIdentifierVPCI-CCVPConnectionIdentifier-ConsistencyCheckVPIVPIdentifierVPLVPLink4Testarchitecture4.1AbstractTestMethod(ATM)ThissubclausedescribestheAbstractTestMethod(ATM)andthePointofControlandObservation(PCO)usedtotesttheVB5.1RTMCprotocolfortheANandSNcomponents.TheremotetestmethodisusedforVB5.1RTMCconformancetesting,sincetheVB5.1implementationsarenotmandatedtoofferadirectaccesstotheupperserviceboundary(i.e.tothe"mee"serviceprimitives).Theco-ordinationprocedurescanonlybeexpressedinaninformalway.SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)10SUTVB5RTMCPDUsServiceProviderDLL&PHLlayersLTControlandDLconnectionendpointsVB5TestSystemIUTVB5-RTMCDL-DATAPCO/DSAPUTFigure1:RemotesinglelayertestmethodappliedtotheVB5.1RTMCtestingLT:ALowerTester(LT)islocatedintheVB5.1testsystem.ItcontrolsandobservesthebehaviouroftheIUT.DSAP:AuniqueDatalinkServiceAccessPoint(DSAP)isdefinedattheVB5.1interfaceandcommonlyusedforexchangingservicedataoftheRTMCprotocolfunctionalentities.PCO:ThePCOforRTMCtestingislocatedontheDSAP.AlltesteventsatthePCOarespecifiedintermsofdatalinkAbstractServicePrimitives(ASPs)andnetworklayerPDUs.UT:NoexplicitUpperTester(UT)existsinthetestsystem.However,theSUTneedstocarryoutsomeUTfunctionstoachievesomeeffectsoftestco-ordinationprocedures.DesigningATS,thecapabilityofthesystemmanagementfunctions,suchascontrolsoftheIUT,itsinteractionswiththeQ3interfacemaybetakenintoaccount.ThecontrolsoftheIUTwillbeimpliedorinformallyexpressedintheATS,butnoassumptionshallbemaderegardingtheirfeasibilityorrealization.AnexampleofsuchcontrolscouldbetoprovokestartupoftheIUTthroughtheQ3interface.VB5-RTMC:ThePDUconveyingthisinformationwillbetransferredtoandfromthetesterviaasingle,dedicatedvirtualconnection.4.2ScopeoftestpurposesandadditionaltestingBehaviourwhichcannotbefullycontrolledandobservedviatheRTMCprotocolalone,suchasthecheckingofcompletionofcertainactionsofthesystemonthemanagedresources,hasbeenincluded,whenappropriate,inindividualVB5.1testpurposesinanadditionalrequirementsection.Takingtheexampleofblocking,aneedmayarisetoverifythatthestatusofaresourcehasactuallybeenchanged,asspecifiedinthestandard,bycheckingthatitcannolongerbeallocatedtoacall.ThismayrequiretheexecutionofacallattemptviathesignallingprotocolsataUNIorNNI.SuchtestpurposesarenottestableinthescopeoftheRTMCprotocolalone.Anarchitecturehastobedefinedforsystemleveltestsrequiringthecombinationoftwoormoreinterfacesorprotocols.SuchtestsareoutsidethescopeoftheATSforRTMC.TheapproachtakenistoappendashortdescriptionofsuchrequirementstotherelatedRTMCtestpurposes.TheactualtestingoftheserequirementscanonlybeperformedifadditionalmeansareprovidedtoaccessinternaldatawhichcannotbeinterrogatedviaRTMCprocedures.Onewayofperformingthisistouseanad-hoctesterloadedintotheSUT,ifavailable.Thisisnottypicallythecase.AgenericapproachistoconsiderthatanysystemoftheNetworkElementtypecomprisesseveralinterfacesandprotocols,eachofwhichisfirsttestedattheindividualprotocollevel.Theseteststypicallyhavetoleaveoutanumberofrequirementswhicharenottestablewithinasingleprotocol.Asecondhierarchicalleveloftesting(seefigureB2)couldcoverasubstantialnumberofsuchrequirementsbycheckinginteractionsbetweentwoormoreprotocolswhichhavepassedindividualconformancetesting.Thisishoweveroutsidethescopeofthepresenttestingstandard.SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)11ANorSNSystemTestDSS-2ProtocolRTMCProtocolQ3PlaneMan.ProtocoVB5.1Figure2:ExampleofhierarchicaltestarchitectureappliedbeyondVB5.1testingNOTE:Theexampleofblockingdescribedaboveisanillustrationofsuchanapproach.ItcouldalsobeappliedinextendingthetestingoftheQ3managementprotocolbeyondthemerereceptionofanacknowledgementattheQ3interface:thefullexecutionablockingrequestissuedfromtheOperationSystemcouldbecheckedviaDDS-2toverifythattheresourceisactuallyblocked,andviaRTMCtoverifythatrealtimeco-ordinationbetweenANandSNhastakenplace.5ATSconventionsThisclausedescribestheconventionsappliedtodefinetheATSandgivesthenamingconventionschosenforthedifferentelementsoftheATS.TheATSconventionsareintendedtogiveabetterunderstandingoftheATSbuttheydescribealsotheconventionsmadeforthedevelopmentoftheATS,thusforanylatermaintenancepurposesorfurtherdevelopmentoftheATS,theconventionsdescribedinthisclauseshallbeconsidered.5.1Namingconventions5.1.1DeclarationspartThissubclausedescribesthenamingconventionschosenfortheelementsoftheATSdeclarationspart.5.1.1.1Testsuitetypeandstructuredtypedefinitions"ByReference"Inordertoavoidmisalignmentproblemswiththestandard,allthetypesusedinthisATShavebeendefinedbyreference.ThesameASN1file(RTMCMessages)containingthestandardtypedefinitionshasbeenusedasmodulecontainingthereferencedtypedefinitions.EXAMPLE:TypeNameTypeReferenceModuleIdentifierAwaitClearAwaitClearRTMCMessages5.1.1.2TestsuiteconstantdeclarationsByReferenceInordertoavoidmisalignmentproblemswiththestandard,alltheconstantsusedinthisATShavebeendefinedbyreference.ThesameASN.1fileRTMCMessagescontainingthestandardconstantdefinitionshasbeenusedasmodulecontainingthereferencedtypedefinitions.SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)12EXAMPLE:ConstantNameTypeValueReferenceModuleIdentifierconnLUPBIT_STRINGconnLUPRTMCMessages5.1.1.3TestsuiteparameterdeclarationsThetestsuiteparameteridentifiersarecomposedofstringsinuppercaselettersandseparatedbyunderscores.IfthetestsuiteparameterreferencesaPIXITitem,theprefix"PIX_"isused.EXAMPLE:PIX_LSP_VPCI_15.1.1.4TestcaseselectionexpressiondefinitionsThetestcaseselectionexpressionsarebasedonPICSorPIXITtestsuiteparameterdefinitions.EXAMPLE:PIX_automatic_loopback_results5.1.1.5TestsuitevariabledeclarationsThetestsuitevariableidentifiersarecomposedofstringinlowercaselettersstartingbythelowercasestring"tsv_".EXAMPLE:TSV_transId5.1.1.6TimerdeclarationsTwokindsoftimerscanbedistinguished:1)standardized:Thosedefinedinthestandard,e.g.T_block.,usethesamenameasinthestandard,beginningwithacapital"T".theirdurationisdefinedinthePIXITundersamename,forexamplePIX_T_block.2)fortestingsupervision:Inordertocontrolthedurationofindividualtestrelatedtotimeoutofstandardizedtimertests,aspecifictimeranditsduration,PIX_T_supervision,isdefined.5.1.1.7ASPtypedefinitionsASPdefinitionsfollowthespecificationwhenacorrespondingdefinitionexists.ForexampleRESET_RSCisused.Ifnotspecified,afreenameisused.EXAMPLE:msg_too_short.5.1.1.8AliasdefinitionsNoaliasdefinitionsareusedinthetestsuite.5.1.2ConstraintsnamingThissubclausedescribesthenamingconventionschosenfortheelementsoftheATSconstraintspart.Constraintidentifierscommencewithlowercasec,followedbytheASP_TYPE,possiblyfollowedbyothermnemonicswhichcompleteitsdefinition,likeLSPorLUPwhenbasedonasomePDU,followedbyanumericalvaluelike001,002,etc.WhentheconstraintisbasedonaPDU,thetransactionIdvaluecontainedinthePDUisconsideredasavariableandthisvalueisnottakenintoaccountforthedefinitionoftheconstraintname.SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)13Table1TypeDefinitionConstraintDefinitionExampleUNBLOCK_RSCc_UNBLOCK_RSC_LSP_002UNBLOCK_RSCc_UNBLOCK_RSC_LUP_004REQ_LSPIDc_REQ_LSPID_0025.1.3DynamicpartThissubclausedescribesthenamingconventionschosenfortheelementsoftheATSdynamicpart.5.1.3.1TestcaseidentifierThereisaone-to-onemappingbetweentheTestPurposesandthetestcases.TheidentifierofaTCanditscorrespondingTestPurposeisdescribedintable2.Table2:TPidentifiernamingconventionschemeIdentifier:VB5_____VB5VB5.1referencepointspecificationRTMCprotocolatinterfaceANAccessNetworkistheIUTSNServiceNodeistheIUT=procedureidentifierlikeSTStartUpBRBlockingResourceURUnblockingResourceSRShutdownResourceCCVPCIConsistencyCheckVLSVerifyLSPId(SNinitiated)VLAVerifyLSPId(ANinitiated)RLSResetLSPId(SNinitiated)RLAResetLSPId(ANinitiated)RVSResetVPC(SNinitiated)RVAResetVPC(ANinitiated)CEHCommonErrorHandling=testcategory:CACapabilitytestsBVValidBehaviourtestsBIInvalidBehaviourtestsBOInopportuneBehaviourtestsTITimertests=sequentialnumber:(01-99)Exampleoftestcasename:VB5_RTMC_AN_CC_BV_02SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)145.1.3.2PreambleidentifierApreambledefinesasetofTTCNstatementsneededtoinitializetheIUTthencarrytheIUTtoaparticularstateoraparticularcallconfigurationsituationfromwhichthetestcaseshallstart.PreamblesarecalledStartupANorStartupSN.Inaddition,aStartbuSNisdefinedwhenthetestrequirestosetaspecificVPCIbusypriortothetest.5.1.3.3PostambleidentifierThereisnopostambledefined,aseachnewtestisbeginningbyacompletereset,itcannotbecorruptedbysideeffectsofthepreviousexecutedtest.5.1.3.4DefaultidentifierAdefaultisasetofTTCNstatementscalledhereOtherwiseFail,whichisusedtocompletethebehaviourtreerelatedtothetestcase.ItcoverssomedifferentalternativesbringingthetestcasetoaFAILorINCONCLUSIVEverdict.SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)15AnnexA(normative):ATSforVB5.1interfaceThisATShasbeenproducedusingtheTreeandTabularCombinedNotation(TTCN)accordingtoISO/IEC9646-3.TheATSwasdevelopedonaseparateTTCNsoftwaretoolandthereforetheTTCNtablesarenotcompletelyreferencedinthetableofcontents.TheATSitselfcontainsatestsuiteoverviewpartwhichprovidesadditionalinformationandreferences.A.1TheTTCNGraphicalform(TTCN.GR)TheTTCN.GRrepresentationofthisATSiscontainedinAdobePortableDocumentFormat™files(AN_Suite.PDFandSN_Suite.PDFcontainedinarchiveen_30100504v010102p0.ZIP)whichaccompaniesthepresentdocument.A.2TheTTCNMachineProcessableform(TTCN.MP)TheTTCN.MPrepresentationcorrespondingtothisATSiscontainedinASCIIfiles(AN_Suite.MPandSN_Suite.MPcontainedinarchiveen_30100504v010102p0.ZIP)whichaccompaniesthepresentdocument.SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)16AnnexB(normative):PartialPIXITproformaforVB5.1interfaceNotwithstandingtheprovisionsofthecopyrightclauserelatedtothetextofthepresentdocument,ETSIgrantsthatusersofthepresentdocumentmayfreelyreproducethePIXITproformainthisannexsothatitcanbeusedforitsintendedpurposesandmayfurtherpublishthecompletedPIXIT.ThePIXITproformaisbasedonISO/IEC9646-6.Anyadditionalinformationneededcanbefoundinthisinternationalstandarddocument.B.1IdentificationsummaryTableB.1PIXITnumber:Testlaboratoryname:Dateofissue:Issuedto:B.2ATSsummaryTableB.2Protocolspecification:EN301005-1Protocoltobetested:ATSspecification:EN301005-4Abstracttestmethod:RemotetestmethodB.3TestlaboratoryTableB.3Testlaboratoryidentification:Testlaboratorymanager:Meansoftesting:SAPaddress:B.4ClientidentificationTableB.4Clientidentification:Clienttestmanager:Testfacilitiesrequired:SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)17B.5SUTTableB.5Name:Version:SCSnumber:Machineconfiguration:Operatingsystemidentification:IUTidentification:PICSreferenceforIUT:LimitationsoftheSUT:Environmentalconditions:B.6ProtocollayerinformationB.6.1ProtocolidentificationTableB.6Name:EN301005-1:VB5.1interfaceVersion:PICSreferences:EN301005-2B.6.2IUTinformationB.6.2.1ImplicitsendeventsTableB.7:ImplicitsendeventsItemPIXIT(Seenote)Relatedimplicitsendmessage(PDU)Invocationdescription12345678910111213141516SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)18B.6.2.2ParametervaluesTableB.8:ParametervaluesItemParameternameParametertype(ASN1)ExplanationValueinMSCs1.PIX_LUP_addressLogIdLUPofPUP012.PIX_LUP_unkaddrLogIdUnknownLUPofPUP013.PIX_LUP_VPCI_1VPCIFirstVPCIofLUP01ofPUP014.PIX_LUP_VPCI_2VPCI2ndVPCIofLUP01ofPUP015.PIX_LUP_VPCI_unkVPCIunknownVPCIofLUP01ofPUP016.PIX_LUP_VPCI_busyVPCIBusyVPCIofLUP01ofPUP017.PIX_LUPVPCI_lastVPCILastVPCIofLUP01ofPUP018.PIX_LSP_addressLogIdLSPid9.PIX_LSP_unkaddrLogIdunknownLSPid10.PIX_LSP_VPCI_1VPCIFirstVPCIofLSP81ofPSP8111.PIX_LSP_VPCI_2VPCI2ndVPCIofLSP12.PIX_LSP_VPCI_unkVPCIunknownVPCIofLSP13.PIX_LSP_VPCI_busyVPCIBusyVPCIofLSP14.PIX_LSPVPCI_lastVPCILastVPCIofLSP15.PIX_automatic_loopback_resultsBooleanchoicedictatedbyimplementationPIX_T_aclintegerTimervaluePIX_T_blockintegerTimervaluePIX_T_consreqintegerTimervaluePIX_T_consendintegerTimervaluePIX_T_lspidintegerTimervaluePIX_T_resetintegerTimervaluePIX_T_startintegerTimervaluePIX_T_unblockintegerTimervaluePIX_T_supervisionintegersupervisiontimerSIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)19AnnexC(normative):ProtocolConformanceTestReport(PCTR)proformawhentestingANNotwithstandingtheprovisionsofthecopyrightclauserelatedtothetextofthepresentdocument,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 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)20C.1.4LimitsandreservationAdditionalinformationrelevanttothetechnicalcontentsorfurtheruseofthetestreport,ortherightsandobligationsofthetestlaboratoryandtheclient,maybegivenhere.Suchinformationmayincluderestrictiononthepublicationofthereport.C.1.5CommentsAdditionalcommentsmaybegivenbyeithertheclientorthetestlaboratoryonanyofthecontentsofthePCTR,forexample,tonotedisagreementbetweenthetwoparties.C.2IUTconformancestatusThisIUThasorhasnotbeenshownbyconformanceassessmenttobenon-conformingtothespecifiedprotocolspecification.Striketheappropriatewordsinthissentence.IfthePICSforthisIUTisconsistentwiththestaticconformancerequirementsasspecifiedinclauseC.3inthisreportandthereareno"FAIL"verdictstoberecordedinclauseC.6strikethewords"hasor".otherwisestrikethewords"orhasnot".C.3StaticconformancesummaryThePICSforthisIUTisorisnotconsistentwiththestaticconformancerequirementsinthespecifiedprotocol.Striketheappropriatewordsinthissentence.SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)21C.4DynamicconformancesummaryThetestcampaigndidordidnotrevealerrorsintheIUT.Striketheappropriatewordsinthissentence.Ifthereareno"FAIL"verdictstoberecordedinclauseC.6strikethewords"didor"otherwisestrikethewords"ordidnot".Summaryoftheresultsofgroupsoftest:.C.5StaticconformancereviewreportIfclauseC.3indicatesnon-conformance,thissubclauseitemizesthemismatchesbetweenthePICSandthestaticconformancerequirementsofthespecifiedprotocolspecification.SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)22C.6TestcampaignreportTableC.4ATSreferenceSelectedRunVerdictObservationsVB5_RTMC_AN_ST_CA_01Yes/NoYes/NoVB5_RTMC_AN_ST_CA_02Yes/NoYes/NoVB5_RTMC_AN_ST_CA_03Yes/NoYes/NoVB5_RTMC_AN_BR_BV_01Yes/NoYes/NoVB5_RTMC_AN_BR_BV_02Yes/NoYes/NoVB5_RTMC_AN_BR_BV_03Yes/NoYes/NoVB5_RTMC_AN_BR_BV_04Yes/NoYes/NoVB5_RTMC_AN_BR_BV_05Yes/NoYes/NoVB5_RTMC_AN_BR_BV_06Yes/NoYes/NoVB5_RTMC_AN_BR_BV_07Yes/NoYes/NoVB5_RTMC_AN_BR_BV_08Yes/NoYes/NoVB5_RTMC_AN_BR_TI_01Yes/NoYes/NoVB5_RTMC_AN_BR_BV_11Yes/NoYes/NoVB5_RTMC_AN_BR_BV_12Yes/NoYes/NoVB5_RTMC_AN_BR_BV_13Yes/NoYes/NoVB5_RTMC_AN_BR_BV_14Yes/NoYes/NoVB5_RTMC_AN_BR_BV_15Yes/NoYes/NoVB5_RTMC_AN_BR_BV_16Yes/NoYes/NoVB5_RTMC_AN_BR_BV_17Yes/NoYes/NoVB5_RTMC_AN_BR_BV_18Yes/NoYes/NoVB5_RTMC_AN_BR_TI_11Yes/NoYes/NoVB5_RTMC_AN_UR_BV_01Yes/NoYes/NoVB5_RTMC_AN_UR_BV_02Yes/NoYes/NoVB5_RTMC_AN_UR_BV_03Yes/NoYes/NoVB5_RTMC_AN_UR_TI_01Yes/NoYes/NoVB5_RTMC_AN_UR_BV_11Yes/NoYes/NoVB5_RTMC_AN_UR_BV_12Yes/NoYes/NoVB5_RTMC_AN_UR_BV_13Yes/NoYes/NoVB5_RTMC_AN_UR_TI_11Yes/NoYes/NoVB5_RTMC_AN_SR_BV_01Yes/NoYes/NoVB5_RTMC_AN_SR_BV_02Yes/NoYes/NoVB5_RTMC_AN_SR_BV_03Yes/NoYes/NoVB5_RTMC_AN_SR_BV_04Yes/NoYes/NoVB5_RTMC_AN_SR_TI_01Yes/NoYes/NoVB5_RTMC_AN_SR_BV_11Yes/NoYes/NoVB5_RTMC_AN_SR_BV_12Yes/NoYes/NoVB5_RTMC_AN_SR_BV_13Yes/NoYes/NoVB5_RTMC_AN_SR_BV_14Yes/NoYes/NoVB5_RTMC_AN_SR_TI_11Yes/NoYes/NoVB5_RTMC_AN_CC_BI_01Yes/NoYes/NoVB5_RTMC_AN_CC_BV_01Yes/NoYes/NoVB5_RTMC_AN_CC_BV_02Yes/NoYes/NoVB5_RTMC_AN_CC_BO_01Yes/NoYes/NoVB5_RTMC_AN_CC_BI_02Yes/NoYes/NoVB5_RTMC_AN_CC_BV_11Yes/NoYes/NoVB5_RTMC_AN_CC_BV_12Yes/NoYes/NoVB5_RTMC_AN_CC_BO_11Yes/NoYes/NoVB5_RTMC_AN_CC_BI_12Yes/NoYes/NoVB5_RTMC_AN_VLS_BV_01Yes/NoYes/NoSIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)23ATSreferenceSelectedRunVerdictObservationsVB5_RTMC_AN_VLA_BV_01Yes/NoYes/NoVB5_RTMC_AN_VLA_TI_01Yes/NoYes/NoVB5_RTMC_AN_RLS_BV_01Yes/NoYes/NoVB5_RTMC_AN_RLS_BI_01Yes/NoYes/NoVB5_RTMC_AN_RLA_BV_01Yes/NoYes/NoVB5_RTMC_AN_RLA_TI_01Yes/NoYes/NoVB5_RTMC_AN_RVS_BV_01Yes/NoYes/NoVB5_RTMC_AN_RVS_BV_02Yes/NoYes/NoVB5_RTMC_AN_RVS_BI_01Yes/NoYes/NoVB5_RTMC_AN_RVS_BI_02Yes/NoYes/NoVB5_RTMC_AN_RVS_BI_03Yes/NoYes/NoVB5_RTMC_AN_RVS_BV_11Yes/NoYes/NoVB5_RTMC_AN_RVS_BV_12Yes/NoYes/NoVB5_RTMC_AN_RVS_BI_11Yes/NoYes/NoVB5_RTMC_AN_RVS_BI_12Yes/NoYes/NoVB5_RTMC_AN_RVS_BI_13Yes/NoYes/NoVB5_RTMC_AN_RVA_BV_01Yes/NoYes/NoVB5_RTMC_AN_RVA_BV_02Yes/NoYes/NoVB5_RTMC_AN_RVA_TI_01Yes/NoYes/NoVB5_RTMC_AN_RVA_BV_11Yes/NoYes/NoVB5_RTMC_AN_RVA_BV_12Yes/NoYes/NoVB5_RTMC_AN_RVA_TI_11Yes/NoYes/NoVB5_RTMC_AN_CEH_BI_01Yes/NoYes/NoVB5_RTMC_AN_CEH_BI_02Yes/NoYes/NoVB5_RTMC_AN_CEH_BI_03Yes/NoYes/NoVB5_RTMC_AN_CEH_BI_04Yes/NoYes/NoVB5_RTMC_AN_CEH_BI_05Yes/NoYes/NoVB5_RTMC_AN_CEH_BI_06Yes/NoYes/NoVB5_RTMC_AN_CEH_BI_07Yes/NoYes/NoVB5_RTMC_AN_CEH_BI_11Yes/NoYes/NoVB5_RTMC_AN_CEH_BI_12Yes/NoYes/NoVB5_RTMC_AN_CEH_BI_13Yes/NoYes/NoC.7ObservationsAdditionalinformationrelevanttothetechnicalcontentofthePCTRaregivenhere.SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)24AnnexD(normative):ProtocolConformanceTestReport(PCTR)proformawhentestingSNNotwithstandingtheprovisionsofthecopyrightclauserelatedtothetextofthepresentdocument,ETSIgrantsthatusersofthepresentdocumentmayfreelyreproducethePCTRproformainthisannexsothatitcanbeusedforitsintendedpurposesandmayfurtherpublishthecompletedPCTR.ThePCTRProformaisbasedonISO/IEC9646-6.Anyadditionalinformationneededcanbefoundinthepresentdocument.D.1IdentificationsummaryD.1.1ProtocolconformancetestreportTableD.1PCTRnumber:PCTRdate:CorrespondingSCTRnumber:CorrespondingSCTRdate:Testlaboratoryidentification:Testlaboratorymanager:Signature:D.1.2IUTidentificationTableD.2Name:Version:Protocolspecification:PICS:PreviousPCTRifany:D.1.3TestingenvironmentTableD.3PIXITnumber:ATSspecification:Abstracttestmethod:Meansoftestingidentification:Dateoftesting:Conformancelogreference(s):Retentiondateforlogreference(s):SIST EN 301 005-4:2001

ETSIETSIEN301005-4V1.1.2(2000-05)25D.1.4LimitsandreservationAdditionalinformationrelevanttothetechnicalcontentsorfurtheruseofthetestreport,ortherightsandobligationsofthetestlaboratoryandtheclient,maybegivenhere.Suchinformationmayincluderestrictiononthepublicationofthereport.
...