ETSI EN 301 754 V1.1.1 (2001-09)

Telecommunications Management Network (TMN); Management interfaces associated with the VB5.2 reference point

DEN/TMN-00003

Telekomunikacijsko upravljavno omrežje (TMN) - Upravljavni vmesniki, pridruženi referenčni točki VB5.2

General Information

• Status: Published
• Publication Date: 04-Sep-2001
• Technical Committee: TMN - Telecommunications Management Network
• Current Stage: 12 - Completion
• Due Date: 07-Sep-2001
• Completion Date: 05-Sep-2001
• Ref Project: SIST EN 301 754 V1.1.1:2003 - Telecommunications Management Network (TMN); Management interfaces associated with the VB5.2 reference point

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Telecommunications Management Network (TMN); Management interfaces associated with the VB5.2 reference point33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 754 Version 1.1.1SIST EN 301 754 V1.1.1:2003en01-november-2003SIST EN 301 754 V1.1.1:2003SLOVENSKI
STANDARD
ETSIEN301754V1.1.1(2001-09)EuropeanStandard(Telecommunicationsseries)TelecommunicationsManagementNetwork(TMN);ManagementinterfacesassociatedwiththeVB5.2referencepointSIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)2ReferenceDEN/TMN-00003KeywordsTMN,Q3interface,ATM,configuration,management,performance,V5interface,OAMETSI650RoutedesLuciolesF-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 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)3ContentsIntellectualPropertyRights.6Foreword.61Scope.72References.73Definitions,abbreviations,andconventions.83.1Definitions.83.2Abbreviations.83.3Conventions.94GeneralOverview.104.1Entity-relationshipmodels.104.1.1Entityrelationshipdiagramfortheservicenode.114.1.2Entityrelationshipdiagramfortheaccessnetwork.124.2Inheritancehierarchy.135FormalDefinitions.136Typedefinitions.137Protocolstacks.13AnnexA(normative):Managementrequirements.14A.1Generalmanagementrequirements.14A.1.1Generalconfigurationmanagementrequirements.14A.2Real-timemanagementcoordinationrequirements.14A.2.1Configurationmanagementrequirements.14A.2.1.1Generalconfigurationmanagementrequirement.14A.2.1.2CommonconfigurationmanagementrequirementforANandSN.14A.2.1.2.1Shutting-downofVPs.14A.2.1.2.2VB5interfaceIDchecking.14A.2.1.2.3HandlingofVB5primitives.14A.2.1.2.4CoordinationofVPandVCresources.14A.2.1.2.5NonB-ISDNaccesses.14A.2.1.3ConfigurationmanagementrequirementforAN.15A.2.1.4ConfigurationmanagementrequirementforSN.15A.2.1.4.1Assignmentofindirectaccesses.15A.2.1.4.2Coordinationofindirectaccesseswithlogicaluserports.15A.2.1.4.3Consistencyofconfiguration.15A.2.2Faultmanagementrequirements.15A.2.2.1Alarmsurveillancerequirements.15A.2.2.1.1Generalalarmsurveillancerequirements.15A.2.2.1.1.1Coordinationofoperationalstates.15A.2.2.2Testandfaultlocalizationrequirements.15A.2.2.2.1Generaltestandfaultlocalizationrequirements.15A.2.2.2.1.1Testtraffic.15AnnexB(normative):RelationshipbetweenVB5.2interfacesandthemanagementmodel.16B.1Introduction.16B.2LSP,LUPandVPCIlabels.17B.3Shuttingdown.17B.4Blockingandunblocking.17B.5VPCIconsistencychecking.18SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)4B.6Interfacestart-up.18B.6.1B-BCCstart-upfromSNside.19B.6.1.1B-BCCstart-upinitiatedbySNOS.19B.6.1.2B-BCCstart-upinitiatedautonomouslybytheSNNE.21B.6.2B-BCCstart-upfromANside.21B.6.2.1B-BCCstart-upinitiatedbyANOS.21B.6.2.2B-BCCstart-upautomaticallyinitiatedbytheANNE.22B.6.2.2.1B-BCCstart-upinSNduetoautomaticinitiationofstart-upinAN.23B.6.2.2.2B-BCCrestartinSNduetoautomaticinitiationofstart-upinAN.23B.7LSPidentitychecking.25B.8RTMCreset.25B.9B-BCCreset.26B.10Congestion.26AnnexC(normative):Statetransitions.27C.1StatetransitiontablesforAN.27C.2StatetransitiontablesforSN.28AnnexD:Void.30AnnexE(informative):Instantiationexample.31E.1Conventions.31E.2ExampleofVPs/VCsallocationattheANandtheSN.31E.3InstantiationofmanagedobjectsintheAN.31E.4InstantiationofmanagedobjectsattheSN.33AnnexF(informative):ReferencedDefinitions.35F.1Objectclasses.35F.1.1Profilingnotesforimportedclasses.35F.1.1.1vpcLup(VPCatlogicaluserport).35F.1.2Definitionofclasses.35F.1.2.1bbccCommPathBb(B-BCCcommunicationspathforbroadband).35F.1.2.2lspVb52An(logicalserviceportforVB5.2intheaccessnetwork).36F.1.2.3lspVb52Sn(logicalserviceportforVB5.2intheservicenode).36F.1.2.4vclLup(VClinkatthelogicaluserport).36F.1.2.5vpcLupVb52(VPCatthelogicaluserportforVB5.2).37F.1.2.6vpTtpLup(VPtrailterminationpointatthelogicaluserport).37F.2Namebindings.38F.2.1vclLup-vpcLupVb52.38F.2.2vpcLupVb52-uniAccessVb5.38F.3Definitionofpackages.38F.3.1lupVcLevelProfilePkg(LogicaluserportVCLevelprofilepackage).38F.4Definitionofattributes.39F.4.1bbccRequired(B-BCCrequired).39F.4.2connectionIdentifierFlag(Connectionidentifierflag).39F.4.3vcCtpPtr(VCCTPpointer).39F.4.4vciAtLup(VCIatthelogicaluserport).39F.4.5vclLupId(VClinkatthelogicaluserportidentifier).39F.5Definitionofactions.40F.5.1resetBbcc(resetBBCCprotocol).40F.6Definitionofnotifications.40F.6.1presyncBbccResult(resultofpresynchronizationofBBCCprotocol).40SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)5F.6.2resetBbccResult(resultofresetofBBCCprotocol).40F.7Typedefinitions.40AnnexG(informative):Bibliography.42History.44SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)6IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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)hasbeenproducedbyETSITechnicalCommitteeTelecommunicationsManagementNetwork(TMN).NationaltranspositiondatesDateofadoptionofthisEN:20July2001DateoflatestannouncementofthisEN(doa):31October2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):30April2002DateofwithdrawalofanyconflictingNationalStandard(dow):30April2002SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)71ScopeThepresentdocumentspecifiesthemanagementinterfaces(Q3interfaces)associatedwiththeVB5.2referencepoint[6]andEN301217-1(seebibliography)forthesupportofconfiguration,fault&performancemanagementfunctions.Faultandperformancemanagementtogetherincludebothpassivemonitoringofreportsandactivefaultisolation.TheQ3interfaceistheTMNinterfacebetweennetworkelementsorQ-adapterswhichinterfacetoOSswithoutmediationandbetweenOSsandmediationdevices.Existingprotocolsareusedwherepossible,andthefocusoftheworkisondefiningtheobjectmodel.ThedefinitionofthefunctionalityofTMNOperationsSystemsisoutsidethescopeofthepresentdocument.ITU-TRecommendationQ.2931[9]issupportedattheUNI,andtheATMForumUNIissupportedforcompatibilitywiththeestablishedbaseofATMequipment.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublicationand/oreditionnumberorversionnumber)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.[1]ETSIEN301271:"TelecommunicationsManagementNetwork(TMN);ManagementinterfacesassociatedwiththeVB5.1referencepoint".[2]ITU-TRecommendationG.773:"ProtocolsuitesforQ-interfacesformanagementoftransmissionsystems".[3]ITU-TRecommendationG.784:"Synchronousdigitalhierarchy(SDH)management".[4]ITU-TRecommendationG.902:"FrameworkRecommendationonfunctionalaccessnetworks(AN)Architectureandfunctions,accesstypes,managementandservicenodeaspects".[5]ITU-TRecommendationG.967.1(1998):"V-interfacesattheServiceNode(SN):VB5.1referencepointspecification".[6]ITU-TRecommendationG.967.2(1998):"V-interfacesattheServiceNode(SN):VB5.2referencepointspecification".[7]ITU-TRecommendationI.751:"Asynchronoustransfermodemanagementofthenetworkelementview".[8]ITU-TRecommendationM.3100(1995):"Genericnetworkinformationmodel".[9]ITU-TRecommendationQ.2931:"BroadbandIntegratedServicesDigitalNetwork(B-ISDN)-DigitalSubscriberSignallingSystemNo.2(DSS2)-User-NetworkInterface(UNI)-Layer3specificationforbasiccall/connectioncontrol".[10]ITU-TRecommendationQ.811:"LowerlayerprotocolprofilesfortheQ3andXinterfaces".[11]ITU-TRecommendationQ.812:"UpperlayerprotocolprofilesfortheQ3andXinterfaces".[12]Void.[13]ITU-TRecommendationQ.824.6:"Stage2andstage3descriptionfortheQ3interface-Customeradministration:Broadbandswitchmanagement".SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)8[14]ITU-TRecommendationQ.832.1(1998):"VB5.1Management".[15]ITU-TRecommendationQ.832.2(1999):"VB5.2Management".[16]ITU-TRecommendationX.721|ISO/IEC10165-2(1992):"Informationtechnology-OpenSystemsInterconnection-Structureofmanagementinformation:definitionofmanagementinformation".3Definitions,abbreviations,andconventions3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:VB5Resources:managementofuserportfunctionsandserviceportfunctionsprovidingUserNetworkInterface(UNI)andServiceNodeInterface(SNI)functionalityNOTE:TheyarerespectivelyconsideredinEN301754basedontheframeworkdefinedinITU-TRecommendationG.902.Transmissionspecificresourceslieoutsideitsscope.VB5ResourcesarereferredtointhepresentdocumentasresourcesInaddition,thepresentdocumentusestermsdefinedinITU-TRecommendations:ITU-TRecommendationG.902:Accessnetwork(AN),Userportfunctions,Servicenode(SN),Servicenodeinterface(SNI),Serviceportfunctions.ITU-TRecommendationG.967.1:Logicalserviceport(LSP),Logicaluserport(LUP),Physicalserviceport(PSP),Physicaluserport(PUP),Real-timemanagementcoordination(RTMC),Virtualuserport(VUP).ITU-TRecommendationG.967.2:Broadbandbearerconnectioncontrol(B-BCC).ITU-TRecommendationI.751:Messagecommunicationfunction(MCF).3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ANAccessNetworkASN.1AbstractSyntaxNotationOneATMAsynchronousTransferModeB-BCCBroadbandBearerConnectionControlGDMOGuidelinesfortheDefinitionOfManagedObjectsLSPLogicalServicePortLUPLogicalUserPortMIBManagementInformationBaseMOCManagedObjectClassOAMOperations,AdministrationandMaintenanceOSOperationsSystemRTMCReal-TimeManagementCoordinationSDHSynchronousDigitalHierarchySNServiceNodeSNIServiceNodeInterfaceTMNTelecommunicationsManagementNetworkTTPTrailTerminationPointUNIUser-NetworkInterfaceVCVirtualChannelVPVirtualPathVPCVirtualPathConnectionVPCIVirtualPathConnectionIdentifierSIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)93.3ConventionsNOTE:WhilethisspecificationonVB5.2managementmakesuseofITU-TRecommendationX.722/Amd.1(1995)ontheSET-BY-CREATEproperty,thereadershouldbeawarethatITU-TRecommendationX.722/Amd.1(1995)hasnotbeenappliedintheVB5.1managementspecification.ObjectsandtheircharacteristicsandassociatedASN.1definedherearegivennameswithcapitalsusedtoindicatethestartofthenextwordandacronymsaretreatedasiftheywerewords.Throughoutthepresentdocument,allnewattributesarenamedaccordingtothefollowingguidelines:• Thenameofanattributeendsinthestring"Ptr"ifandonlyiftheattributevalueisintendedtoidentifyasingleobject.• Thenameofanattributeendsinthestring"PtrList"ifandonlyiftheattributevalueisintendedtoidentifyoneormoreobjects.• Thenameofanattributeiscomposedofthenameofanobjectclassfollowedbythestring"Ptr"ifandonlyiftheattributevalueisintendedtoidentifyaspecificobjectclass.• Ifanattributeisintendedtoidentifydifferentobjectclasses,adescriptivenameisgiventothatattributeandadescriptionisprovidedintheattributebehaviour.• Thenameofanattributeendsinthestring"Id"ifandonlyiftheattributevalueisintendedtoidentifythenameofanobject,inwhichcasethisattributeshouldbethefirstonelisted,shoulduseASN.1NameTypeandshouldnotbeusedtoconveyotherinformation.• Thenameofanattributeiscomposedofthenameofanobjectclassfollowedbythestring"Id"ifandonlyiftheattributevalueisintendedtoidentifythenameoftheobjectclassholdingthatattribute.SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)104GeneralOverviewThefollowinginformationmodeldiagramshavebeendrawnforthepurposeofclarifyingtherelationsbetweenthedifferentobjectclassesofthemodel.1)Entity-relationshipmodelsshowingtherelationsofthedifferentmanagedobjects.2)InheritanceHierarchyshowinghowmanagedobjectsarederivedfromeachother(i.e.thedifferentpathsofinheritedcharacteristicsofthedifferentmanagedobjects).Thesediagramsareonlyforclarification.TheformalspecificationintermsofGDMOtemplatesandASN.1typedefinitionsaretherelevantinformationforimplementations.4.1Entity-relationshipmodelsThefollowingconventions(seefigure1)areusedinthediagrams:mocmocmociscontainedinisassociatedwith"is-a"relationshipmanagedobjectclass1:1containment1:Ncontainment1:1association1:Nassociationbidirectionalunidirectionaluninstantiableobjectclass(superclass)managedobjectclassoutsidetheactualfragmentcaiFigure1:ConventionsusedindiagramsforEntity-relationshipmodelsWherethedirectionalityofcontainmentisnotclear,itcanbeidentifiedbyimplicationssincetherootclassisunique.SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)114.1.1EntityrelationshipdiagramfortheservicenodeaaacaiiaaaacccaaaccmanagedElementR1tcAdaptorTTPBidirectionalvpCTPBidirectionalvcTTPBidirectionalvcCTPBidirectionalatmAccessProfilesaalUniProtocolProfilertmcCommPathBbbbccCommPathBbcommPathBbvpCtpBidirectionalVb5vpTtpBidirectionalVb5uniAccessVb5vpcLupVb52vclLuplspVb52SnvpcLupNOTE:NotallobjectclassesareshowninthisdiagramassomeobjectclassesarereusedunchangedfromITU-TRecommendationl.751[7].Figure2:Entity-relationshipdiagram-ServicenodeSIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)124.1.2EntityrelationshipdiagramfortheaccessnetworkaaaiiaacaacccamanagedElementR1tcAdaptorTTPBidirectionalvcTTPBidirectionalvcCTPBidirectionalatmAccessProfilesaalUniProtocolProfilertmcCommPathBbbbccCommPathBbcommPathBbvpCTPBidirectionalvpTTPBidirectionallspVb52AnlogicialUserPorttcAdaptorTtpExtensionvpTtpLupNOTE:NotallobjectclassesareshowninthisdiagramassomeobjectclassesarereusedunchangedfromITU-TRecommendationl.751[7].Figure3:Entity-relationshipdiagram-AccessnetworkSIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)134.2InheritancehierarchyFigure4tracestheinheritancerelationshipsfromthehighestlevelobject(ITU-TRecommendationX.721[16],"top")tothemanagedobjectswhicharedefinedinthepresentdocument.lspVb52AnlspVb52SnvpcLupVb52vclLup"X.721":top"Q.832.1":commPathBb"Q.832.1":logical-ServicePort"Q.832.1":lspVb51"Q.832.1":lspVb51An"Q.832.1":lspVb51Snbbcc-CommPathBb"Q.832.1":vpcLup"M.3100":termination-Point"M.3100":trailTermination-PointSource"M.3100":trailTermination-PointSink"M.3100":trailTermination-Point-Bidirectional"I.751":vpTTPBidirectionalvpTtpLupFigure4:Inheritancehierarchy5FormalDefinitionsThisclausegivestheformaldefinitionsofthemanagedobjectclasses,namebindings,generalpackages,behaviours,attributes,actionsandnotifications.FormaldefinitionsareshowninannexF.6TypedefinitionsTypedefinitionsareshowninannexF.7.7Protocolstacks• TheprotocolstacksspecifiedinITU-TRecommendationsQ.811[10],Q.812[11],G.773[2]andtheSDHdigitalcross-connectpartofITU-TRecommendationG.784[3]canbeusedaspartoftheprotocolstackforthepresentdocument.SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)14AnnexA(normative):ManagementrequirementsA.1GeneralmanagementrequirementsA.1.1Generalconfigurationmanagementrequirementsa)ThereisarequirementtoassignaVB5interfaceidentifier,alsoknownasalogicalserviceportidentifier,toaVB5interface.b)ThereisarequirementtoassignVPCIstoVPCsonaVB5interfacewhentheseVPCsareterminatedintheaccessnetwork.A.2Real-timemanagementcoordinationrequirementsA.2.1ConfigurationmanagementrequirementsA.2.1.1GeneralconfigurationmanagementrequirementThegeneralconfigurationrequirementsincludethegeneralreal-timemanagementcoordinationfunctionsbetweentheaccessnetworkandtheservicenode.A.2.1.2CommonconfigurationmanagementrequirementforANandSNA.2.1.2.1Shutting-downofVPsThemodelshouldsupporttheMEEprimitivesassociatedwiththeshuttingdownofVPs.A.2.1.2.2VB5interfaceIDcheckingThemanagementinterfacesmustsupporttheverificationoflogicalVB5interfaceIDssothattheconnectionofVB5interfacescanbecheckedbytheoperationssystems.A.2.1.2.3HandlingofVB5primitivesTheoperationssystemmustbeabletohandletheMEEprimitivesinANandtheSN.A.2.1.2.4CoordinationofVPandVCresourcesThereisarequirementfortheservicenodetohaveknowledgeofthestateofVPandVCresourcesusedtoprovideservicetothecustomer.A.2.1.2.5NonB-ISDNaccessesThereisarequirementtotakeaccountofVCsterminatedintheaccessnetworkfornon-B-ISDNaccessesrepresentedbyvirtualuserports(whosenatureisnotexplicit)andtoallowcrossconnectionsforthese.SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)15A.2.1.3ConfigurationmanagementrequirementforANA.2.1.4ConfigurationmanagementrequirementforSNA.2.1.4.1AssignmentofindirectaccessesThereisarequirementtoassignindirectUNIaccessesintheservicenodetoVB5interfacesattheservicenode.A.2.1.4.2CoordinationofindirectaccesseswithlogicaluserportsThereisrequirementtorelateindirectUNIaccessesintheservicenodetologicaluserportsintheaccessnetwork.A.2.1.4.3ConsistencyofconfigurationThereisarequirementtochecktheconsistencyoftheconfigurationVPCIsbetweentheaccessnetworkandtheservicenode.A.2.2FaultmanagementrequirementsA.2.2.1AlarmsurveillancerequirementsA.2.2.1.1GeneralalarmsurveillancerequirementsA.2.2.1.1.1CoordinationofoperationalstatesWherechangesoftheoperationalstateofATMentitiesarecommunicatedbetweentheaccessnetworkandtheservicenodeusingATMOAMcells,itmustbepossibletoinformtheoperationssystemsaboutthesecommunicatedchangessincehighermanagementfunctionsmaybeaffected.ThisisdealtwithinITU-TRecommendationI.751[7].A.2.2.2TestandfaultlocalizationrequirementsA.2.2.2.1GeneraltestandfaultlocalizationrequirementsA.2.2.2.1.1TesttrafficThereisarequirementtobeabletopermitonlytesttrafficacrossaVB5interface.SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)16AnnexB(normative):RelationshipbetweenVB5.2interfacesandthemanagementmodelB.1IntroductionThisannexdescribestherelationshipsbetweenVB5.2interfacesandthemanagementmodel.Inparticularitdescribeswhenprimitives(see"Generalfunctionalarchitecture"[6])arecreatedduetomessagesfromtheOSandwhenmessagesaresenttotheOSasaresultofprimitivesgeneratedbythemanagedsystem.FigureB.1showsthepositionofthemanagementfunctions(whichworksonthemanagementmodelandsends/receivesOSmessages)withinaVB5.2NE.Themanagementfunctiongeneratesdirectlymee-PrimitivestotheVB5.2system(channelsaandcinthefigure)andittriggerstheconnectioncontrolfunctiontosendcee-primitivestotheVB5.2system(channeldinthefigure)fordefinitionofmee-andcee-primitivesseeITU-TRecommendationsG.967.1[5]andG.967.2 [6]. The interworking between management function and connection control function is not described onprimitivelevelbutjustverbally.b)e)a)d)c)a)d)c)Q3Q3ANVB5.2applicationfunctionsANVB5.2systemSNVB5.2applicationfunctionsSNVB5.2systemANfunctionsSNfunctionsmanagementfunctionsconnectioncontrolfunctionsconnectioncontrolfunctionsmanagementfunctionsB-BCCsystemB-BCCsystemRTMCsystemRTMCsystema)ServiceprimitivesbetweenmanagementfunctionsandRTMCsystemb)RTMCprotocolmessagesacrosstheVB5.2referencepointc)ServiceprimitivesbetweenmanagementfunctionsandB-BCCsystemd)ServiceprimitivesbetweenconnectioncontrolfunctionsandB-BCCsysteme)B-BCCprotocolmessagesacrosstheVB5.2referencepointFigureB.1:OverallVB5.2systemspecificationmodelIncaseswhereattributesarechangedasaresultofprimitivesgeneratedbythemanagedsystem,theOSmaybeinformedbychangenotifications.ThefollowingclauseswithinthisannexdescribetheuseofthevariousVB5labelsandVB5.2proceduresandrelatetheinformationmodeloftheANandtheSNtotheprimitivesoftheVB5.2system.SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)17B.2LSP,LUPandVPCIlabelsTheLSPidentifierwhichisusedinVB5messagescorrespondstothelogicalServicePortNumberattributeofthelogicalserviceportobjects.TheLUPidentifierswhichareusedinVB5messagescorrespondtothelogicalUserPortattributeoftheVB5UNIaccessobjectsintheSNorofthelogicaluserportobjectsintheAN.TheVPCIvaluesforLUPsinANusedinVB5messagescorrespondtothevaluesassociatedwiththevpCtpAndVpciPtrListattributeoflogicaluserportobjectsiftheVPCsattheLUPsdonotterminateintheAN,ortothevaluesassociatedwiththevpTtpAndVpciPtrListattributeoflogicaluserportobjectsiftheVPCsattheLUPsdoterminateintheAN.TheVPCIvaluesforLUPsintheSNusedinVB5messagescorrespondtothevaluesassociatedwiththetpAndVpciPtrListattributeoftheVB5UNIaccessobjectsforVPCswhichterminateintheSN,ortothevaluesassociatedwiththevpCtpVb5AndVpciPtrListforVPCswhichdonotterminateintheSN.ForVPCswhichareassociatedwithVB5UNIaccessesandwhichterminateintheAN,theVPCIvaluesusedinVB5messagescorrespondtothevaluesofthevpcLupNumberattributeofthevpcLupobjectsintheSN.TheVPCIvaluesforLSPsusedinVB5messagescorrespondtothevaluesassociatedwiththevpTtpAndVpciPtrListattributeofthelogicalserviceportobjects.B.3ShuttingdownShuttingdownisinitiatedbytheOSoftheANchangingtheadministrativeStateattributeofanobjectwhichaffectsaVPorgroupofVPsrelatedtotheVB5interfacetoitsshutting-downvalue,orthepartialAdministrativeStateattributetothepartialshutting-downvalueforthoseobjectswhichsupportthisvalue.ThisresultsinthecreationofaMEE_await_clear_reqprimitiveorprimitivesintheAN.FollowingtheexchangeofVB5messages,theSNgeneratesaMEE_await_clear_indprimitiveorprimitiveswhichresultsinthechangingoftheremoteBlockingVb5attributefromremoteUnblockedtoremoteAwaitingClearintherelevantVB5VPCTPorTTPobjectsorintherelevantvpcLupobjects.TheSNrespondstotheMEE_await_clearprimitiveorprimitivesbywaitingforcallstoclear.Whenthisiscomplete,theSNgeneratesaMEE_await_clear_resprimitiveorprimitivesandsendstheappropriatemessagetotheAN,whichrespondsandgeneratesaMEE_await_clear_confprimitiveorprimitives.ThisallowstheadministrativeStateorpartialAdministrativeStateattributewhichinitiatedtheprocessintheANtochangetolockedorpartiallylockedrespectively.B.4BlockingandunblockingWhentherelevantadministrativeStateorpartialAdministrativeStateattributesintheANchangetolockedorpartiallylocked,eitherasaresultofshuttingdownorduetodirectinterventionbytheOS,aMEE_block_requestprimitivewithanadministrativecauseisgeneratedandamessageissenttotheSN.Onreceiptofthismessage,aMEE_block_indprimitiveisgeneratedintheSN.Inaddition,intherelevantVPCTP,TTP,vpcLuporlogicalserviceportobjectstheremoteBlockingVb5attributechangestoremoteBlockedandtheadministrativefieldoftheremoteBlockingReasonVb5attributechangestoadministrativecausepartialorfull,dependingonthenatureoftheblocking.IfthereisafaultwhichaffectsaVPorgroupofVPsintheAN,thenaMEE_block_requestprimitivewithafaultcauseisgenerated,amessageissenttotheSN,andoftentherewillbeanoperationalStateattributeinanobjectintheANwhichchangestodisabled.Onreceiptofthemessage,aMEE_block_indprimitiveisgeneratedintheSNandintherelevantVPCTP,TTP,vpcLuporlogicalserviceportobjectstheremoteBlockingVb5attributechangestoremoteBlockedandthefaultfieldoftheremoteBlockingReasonVb5attributechangestoerror.WhentheadministrativeStateorpartialAdministrativeStateattributeintheANischangedtounlockedbytheOSorthefaultconditioniscleared,aMEE_unblock_reqprimitiveisgeneratedintheANandamessageissenttotheSN.Onreceiptofthismessage,aMEE_unblock_indprimitiveisgeneratedintheSNandintherelevantVPCTP,TTP,vpcLuporlogicalserviceportobjectstheremoteBlockingVb5attributechangestoremoteUnblockedandthefaultoradministrativefieldoftheremoteBlockingReasonVb5attributechangestonone.TheadministrativeandfaultfieldsintheremoteBlockingVb5attributeareindependent.SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)18B.5VPCIconsistencycheckingTheCheckVpciConsistencyactionisinitiatedbytheOSoftheSNviaQ3andisonlyapplicabletoVPCsonaVB5interfacewhichterminateintheANandareassociatedwithanLSP.TheSNenvironmentisresponsibleforensuringthatthereisnosecondCheckVpciConsistencyinitiatedaslongthefirstoneisrunning.TheVPConwhichtheCheckVpciConsistencyactionisperformedhastobeintheoperationalstateenabled.Whenstartingtheaction,theoperatorhastoprovidetheCheckVpciConsistencyInformation.TheenvironmentoftheSNcreatesaMEE_cons_check_reqprimitiveandaVB5messageissentacrosstheinterfacetotheAN.OnreceiptofthisVB5message,theANgeneratesaMEE_cons_check_indprimitivetoactivatetheloopbackmonitoringfunctionontherequestedVPCIinANenvironment.AMEE_cons_check_resprimitivegeneratedintheANenvironmentdirectedtothesystemmanagementcontainstheinformationwhethertheactivationoftheloopbackmonitoringfunctionwassuccessfulortheCheckVpciConsistencywasrejected(e.g.ifanotherCheckVpciConsistencystartedbyadifferentSNisalreadyrunning).TheappropriateVB5messagecarriestheresultinformationbacktotheSNside.AMEE_cons_check_confprimitiveisgeneratedwhichtriggerstheSNenvironmenttostartsendingend-to-endloopbackcells(successfulcase)orleadstoanactionreplywhichissenttotheoperatorandterminatestheCheckVpciConsistencyactionwiththeRemoteReason"notPerformed"(rejectedorunknownresourcecase).IftheCheckVpciConsistencyissuccessfuluptothispoint,thedetectionbytheSNofcellswhichhavebeenloopedbackortheterminationofthetestresultsinthegenerationofaMEE_cons_check_end_reqprimitivefollowedbyaVB5messageacrosstheVB5.1interfacetowardstheAN.OnreceiptofthisVB5message,theANgeneratesaMEE_cons_check_end_indprimitivewhichresultsinthedeactivationoftheloopbackmonitoringfunction.TheANenvironmentgeneratesaMEE_cons_check_end_resprimitiveandaVB5messagecrossestheVB5.1interfacetotheSN.ThismessageconfirmsthestoppingoftheVPCIconsistencycheckprocedureandcarriestheinformationwhethertheANmonitoredtheloopbackcellsornot(successfulorfailed).IntheSNaMEE_cons_check_end_confprimitiveisgeneratedwhichtransferstheresult(successful,failedatAN)totheSNenvironment.TheactionreplyCheckVpciConsistencyResulttransfersthisinformationviaQ3totheOSwhichstartedtheaction.B.6Interfacestart-upTheB-BCCstart-upprovidesthecommunicationproceduresbetweenSNandANtoinitializetheB-BCCprotocolentitiesbysettingthemtotheidlestate.ThestartupLspactionisnormallysentbytheoperatorwhennoprotocolisactive(whentheoperationalStateattributeoftherelatedlspVb52objectclasshasthevalue"disabled").Theinterfacestart-upprocedureisinitiatedbyasinglestartupLspactionandshouldoccurinthefollowingsequence:a)RTMCstart-up:refertoclauseC.6ofEN301271[1]butnotethatthelspActivationStateattributedoesnotchangetothevalue"activated"andnostart-upactionreplyissentaftertheRTMCstart-upisfinished.b)B-BCCstart-up:specifiedinthisclause.AB-BCCstart-upshallbeinitiatedbytheNEsystemsaftertheRTMCprotocolisrunningwithoutfailure.Ifonlyoneprotocolisactive,thelspActivationStatedoesnotthehavevalue"activated".Fromtheviewofthemanagementinformationmodel,theB-BCCstart-upinvolvestheMOCslspVb52SnandlspVb52AnwiththeirstartupLspactionandlspActivationStateandoperationalStateattributes.ValuesoftheattributelspActivationStateare"activated","restarting"and"notactivated".ValuesoftheattributeoperationalStateare"enabled"and"disabled".SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)19OntheVB5.2interfacesidethefollowingprimitivesarerelatedtotheB-BCCstart-upprocedure:• meeBbccStartupReq(SNside)• meeBbccStartupConf(SNside)• meeBbccRestartReq(SNside)• meeBbccRestartConf(SNside)• meeBbccStartResetInd(SNside)• meeBbccStartTrafficInd(SNandANside)• meeBbccStartTrafficReq(ANside)• meeBbccStartTrafficConf(ANside)• meeBbccPresyncInd(ANside)• meeBbccPresyncAccRes(ANside)• meeBbccPresyncRejRes(ANside)Thefollowingoptionsforastart-upproceduresarevalid:• B-BCCstart-upSNside(seeclauseB.6.1);• B-BCCstart-upinitiatedbySNOS(seeclauseB.6.1.1);• B-BCCstart-upinitiatedautonomouslybytheSNNE(seeclauseB.6.1.2);• B-BCCstart-upfromANside(seeclauseB.6.2);• B-BCCstart-upinitiatedbyANOS(seeclauseB.6.2.1);• AutomaticallyinitiatedbytheSNNEonreceiptofanindicationthattheSAALfortheB-BCCprotocolhasbeenestablishedbytheAN(calledlater:B-BCCstart-upautomaticallyinitiatedbytheANNE)(seeclauseB.6.2.2).DetailsofstatetransitionsaregivenintherelevantstatetransitiontablesofannexC.PrimitivesintheSNandintheANarelinkedthroughVB5messagesasdescribedintheVB5interfacestandards.Inthediagrams'-A'indicatesanaction,'-R'indicatesanactionreply,'-N'indicatesanotificationand'(.)'indicatesanewvalueofanattribute.Thesediagramsdonotshowallofthepossibleinformationflows.B.6.1B-BCCstart-upfromSNsideB.6.1.1B-BCCstart-upinitiatedbySNOSSNeventsTheOSoftheSNinitiatesaninterfacestart-upthroughthestartupLspactionofthelspVb52Snobjectclass.TheactioncausesthemanagementfunctiontoexaminethevalueoftheoperationalStateattribute.Ifthevalueis"enabled",thestartupLspactionendsimmediatelyandinformstheOSoftheSNthroughthestart-upactionreply.IfthevalueoftheoperationalStateattributeis"disabled",thentheRTMCstart-upisinitiated,thevalueisofthechangedto"enabled",andthemanagementfunctionoftheSNgeneratesameeBbccStartupReqprimitivetowardstheSNB-BCCsystem.Aftercompletionoftheprocedure,theSNB-BCCsystemgeneratesameeBbccStartupConfprimitiveandtheresultinformationispresentedtotheOSwiththeactionreplyStartupLspResult.Theinformationsyntaxofthisactionreplyreflectstheaddressedresourceandcouldhaveatthisstagethefollowingvalues:"notsuccessful"and"successful".SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)20IfthevalueofthelspActivationStateattributechanges,anattributeValueChangenotificationissenttotheOSbutifthestateoftheoperationalStateattributechanges,astateChangenotificationissenttotheOS.TheseinformationflowsareillustratedinfigureB.2.OS(SN)SNSystemsstartupLsp-ARTMCStart-upstateChange-N(enabled)asforautonomousSNStart-upstartupLsp-RSNManagementFunctionNOTE:TheSNeventsfortheautonomousSNStart-upareshowninfigureB.4.FigureB.2:Interfacestart-upbyOS(SN)-SNeventsANeventsTheANmanagementfunctionreceivesameeBbccStartTrafficIndprimitivefromtheANB-BCCsystem.TheANOSisinformedbyanattributeValueChangenotificationofthelspActivationStateattribute.Thestart-upprocedureiscompletedbyareset.TheANconnectioncontrolfunctioninformsthemanagementfunctionoftheANaboutaresetrequestfromtheSNwhichcausesaresetBbccResultnotificationtobegeneratedbytheappropriatelspVb52Anobject.Theinformationsyntaxofthisnotificationreflectstheaddressedresourceandthesuccess/nosuccessoftheB-BCCresetprocedure.TheseinformationflowsareillustratedinfigureB.3.OS(AN)ANSystemsmeeBbccStartTrafficIndattributeValueChange-N(activated)ConnectionControlresetBbccResult-NANManagementFunctionFigureB.3:Start-upinitiatedatSNside-ANeventsSIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)21B.6.1.2B-BCCstart-upinitiatedautonomouslybytheSNNESNeventsIncaseofanautomaticstart-upprocedure,themanagementfunctionoftheSNgeneratesameeBbccStartupReqprimitivetowardstheSNB-BCCsystem.Aftercompletionoftheprocedure,theSNB-BCCsystemgeneratesameeBbccStartupConfprimitive.IfthevalueofthelspActivationStateattributechanges,anattributeValueChangenotificationissenttotheOSbutifthestateoftheoperationalStateattributechanges,astateChangenotificationissenttotheOS.TheseinformationflowsareillustratedinfigureB.4.OS(SN)SNSystemsmeeBbccStartupReqattributeValueChange-N(activated)ORstateChange-N(disabled)meeBbccStartupConfSNManagementFunctionFigureB.4:Autonomousinterfacestart-upbySN-SNeventsANeventsRefertotheANeventsforB-BCCstart-upinitiatedbySNOSinclauseB.6.1.1.B.6.2B-BCCstart-upfromANsideB.6.2.1B-BCCstart-upinitiatedbyANOSANeventsTheOSoftheANinitiatesaninterfacestart-upthroughthestartupLspactionofthelspVb52Snobjectclass.TheactioncausesthemanagementfunctiontoexaminethevalueoftheoperationalStateattribute.Ifthevalueis"enabled",thestartupLspactionendsimmediatelyandinformstheOSoftheANthroughthestart-upactionreply.IfthevalueoftheoperationalStateattributeis"disabled",thentheRTMCstart-upisinitiated,thevalueisofthechangedto"enabled",andthemanagementfunctionoftheANgeneratesameeBbccStartupReqprimitivetowardstheANB-BCCsystem.AfteranestablishmentoftheSAALhastakenplace,theANB-BCCsystemsendsameeBbccStartTrafficConfprimitivetotheANmanagementfunction.TheresultinformationispresentedtotheOSwiththeactionreplyStartupLspResult.Theinformationsyntaxofthisactionreplyreflectstheaddressedresourceandcouldhaveatthisstagethefollowingvalues:"notsuccessful"and"successful".IfthevalueofthelspActivationStateattributechanges,anattributeValueChangenotificationissenttotheOSbutifthestateoftheoperationalStateattributechangesastateChangenotificationissenttotheOS.Fromthispointon,refertoclauseB.6.2.2.1(iftheSNsidedecidesforaB-BCCstart-up)ortoclauseB.6.2.2.2(iftheSNdecidesforaB-BCCRestart).SIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)22TheseinformationflowsareillustratedinfigureB.5.OS(AN)ANsystemsstartupLsp-ARTMCstart-upstateChange-N(enabled)asforautonomousANstart-upstartupLsp-RANmanagementfunctionNOTE:TheANeventsfortheautonomousANstart-upareshowninfigureB.6.FigureB.5:Interfacestart-upbyOS(AN)-ANeventsSNeventsRefertotheSNeventsforB-BCCstart-upautomaticallyinitiatedbytheANNEinclauseB.6.2.2.B.6.2.2B-BCCstart-upautomaticallyinitiatedbytheANNEANeventsInthecaseofanautomaticstart-upprocedure,themanagementfunctionoftheANgeneratesameeBbccStartTrafficReqprimitivetowardstheANB-BCCsystem.AfteranestablishmentoftheSAALhastakenplace,theANB-BCCsystemsendsameeBbccStartTrafficConfprimitivetotheANmanagementfunction.IfthevalueofthelspActivationStateattributechanges,anattributeValueChangenotificationissenttotheOS,butifthestateoftheoperationalStateattributechanges,astateChangenotificationissenttotheOS.TheseinformationflowsareillustratedinfigureB.6.OS(AN)ANSystemsmeeBbccStartTrafficReqattributeValueChange-N(activated)ORstateChange-N(disabled)meeBbccStartTrafficConfANManagementFunctionFigureB.6:Autonomousinterfacestart-upbyAN-ANeventsSIST EN 301 754 V1.1.1:2003

ETSIETSIEN301754V1.1.1(2001-09)23SNeventsOntheSNside,theB-BCCsystemindicateswithameeBbccStartTrafficIndprimitivethatanSAALestablishmenthastakenplace.AtthispointtheSNconnectioncontrolfunctiondecideswhethertheSNproceedswithaB-BCCstart-upasdescribedinclauseB.6.2.2.1oraB-BCCrestartasdescribedinclauseB.6.2.2.2.TheSNOSisneitherinvolvednorinformedaboutthisdecision.TheseinformationflowsareillustratedinfigureB.7.OS(SN)SNSystemsmeeBbccStartTrafficIndSNManagementFunctionasforB-BCCpartofSTARTUPintiatedbySN,butwithoutmeeBbccStartTrafficIndandattributeValueChangeattheANsidesincetheVB5interfaceisalreadyactivatedORasforRESTARTNOTE:TheSTARTUPoptionisshowninfiguresB.3andB.4.TheRESTARToptionisshowninfiguresB.8andB.9.FigureB.7:Start-upinitiatedatANside-SNeventsB.6.2.2.1B-BCCstart-upinSNduetoautomaticinitiationofstart-upinANSNeventsRefertotheSNeventsforB-BCCstart-upautomaticallyinitiatedbytheSNNEinclauseB.6.1.2.A
...