SIST EN 300 820-2 V1.3.1:2003
(Main)Telecommunications Management Network (TMN); Asynchronous Transfer Mode (ATM) management information model for the X- interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected networks; Part 2: Alarm management
- Abstract
This document addresses the configuration management area, covering the following aspects: - the management services and functions needed to manage ATM connections, which span over several administrative domains. These management services and functions cover the fault management requirements for the X-interface; - the management information crossing the X-interface (using GDMO formalisms as described in ITU-T Recommendatio X.722).
- Status
- Published
- Publication Date
- 31-Oct-2003
- 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
SIST EN 300 820-2 V1.3.1:2003 is the Slovene national standard identical to ETSI EN 300 820-2 V1.3.1, for Telecommunications Management Network (TMN) alarm management in Asynchronous Transfer Mode (ATM) Virtual Path (VP) and Virtual Channel (VC) cross-connected networks. It specifies the alarm-management part of the X-interface between Operation Systems (OSs) in different telecommunications operators' domains. The document is aimed at operators, network-management engineers, and implementers who need a common alarm message model, logging model, and information model across administrative boundaries.
What does SIST EN 300 820-2 V1.3.1:2003 specify?
SIST EN 300 820-2 V1.3.1:2003 specifies the alarm management requirements for ATM VP/VC connections that span several administrative domains. It covers the management services and functions for fault alarms on the X-interface and the management information that crosses that interface using Guidelines for the Definition of Managed Objects (GDMO) formalisms from ITU-T Recommendation X.722.
The document is organized into clauses 1 to 9, covering scope, references, definitions, requirements, resources, management function sets, management functions, scenarios, and management information, plus one informative annex on security aspects.
| Annex | What it covers |
|---|---|
| Annex A | Security aspects, including access control considerations for alarm notifications and logs |
What are the key requirements of SIST EN 300 820-2 V1.3.1:2003?
The standard defines how fault alarms are reported, qualified, logged, and retrieved between operators. In practice, this means a PNO implementation has to turn local fault information into a common X-interface alarm record and control who can see or request those records.
- Clause 4 sets the alarm goals - faults should be localizable at PNO sub-network and/or Inter-PNO Physical Link (IPPL) level, affected parties should be informed, alarm information should be time-stamped, redundant multiple alarms should be removed before transfer, and protection switching and recovery results should be reported. This matters because operators need a clean alarm flow, not repeated noise.
- Clause 6 splits alarm handling into three Management Function Sets (MFS) - Alarm notification MFS, Alarm processing MFS, and Alarm event logging MFS. This separates sending, normalizing, and storing alarms, which helps implementation and troubleshooting.
- Clause 6.2 defines the alarm notification content - each alarm message carries subnetworkId, resourceId, time of event, probableCause, perceivedSeverity, and specificProblems. The standard restricts specificProblems to protection-switched, under-recovery, cleared, and unrecoverable, so systems exchange the same alarm meaning.
- Clause 7.1 defines the main notification types - protection switching, under recovery, recovery result, and unrecoverable cases are each mapped to an alarm notification, with severity values taken from the X.733 model. That lets an operator distinguish a temporary protection action from a service-impacting failure.
- Clause 6.3 and Clause 7.2 define alarm processing - received alarms are qualified, adapted to the INMS format, forwarded to the Received Alarm Log (RALog), and cleared is used to mark the end of an alarm event. This is the part that normalizes alarms from different systems before they are acted on.
- Clause 6.4 and Clause 7.3 define logging and retrieval - the Sent Alarm Log (SALog), Received Alarm Log (RALog), and Qualified Alarm Log (QALog) support sequential recording, reporting, and read access by request. This matters for audits, operator review, and post-fault analysis.
- Clause 8 gives operating scenarios - one for sub-network failure and one for IPPL failure, including the rule that a responsible PNO informs all interconnected PNOs when an IPPL fails. This keeps topology information aligned across domains.
- Clause 9 defines the managed objects and naming relationships - PnoVpSubnetworkConnection, PnoVcSubnetworkConnection, pnoNWAtmAccessPoint, and log objects are the basis for the interface model. Implementers use these objects to build the X-interface data model.
What terms does SIST EN 300 820-2 V1.3.1:2003 define?
- Providing Network Operator (PNO) - the operator that provides network resources to customers, including other PNOs.
- Initiating PNO (IPNO) - the PNO that starts reserving the end-to-end VP or VC connection and controls the overall connection.
- Transit PNO (TPNO) - a provider PNO that supplies the transit part of a VP/VC connection.
- X-interface - the management interface between two PNOs, used here for inter-operator alarm exchange.
- Inter-PNO Physical Link (IPPL) - a physical link connecting two PNO VP subnetworks and carrying alarm responsibility at the link level.
- Management Function Set (MFS) - a grouped set of management functions used to perform one part of the alarm service.
- Sent Alarm Log (SALog) - the log of alarms sent across the X-interface and the only log visible over that interface.
Who uses SIST EN 300 820-2 V1.3.1:2003?
SIST EN 300 820-2 V1.3.1:2003 is used by telecom network operators managing ATM VP/VC cross-connected networks across administrative domains. It is relevant to TMN architects, OSS/NMS designers, alarm-management engineers, and vendors implementing inter-operator management systems.
It is also useful for operations teams that need to decide how alarms are qualified, forwarded, logged, and read back between operators. Buyers and quality managers can use it to check whether a product supports inter-operator alarm exchange on the X-interface.
Which standards are used with SIST EN 300 820-2 V1.3.1:2003?
| Reference | Contribution |
|---|---|
| EN 300 820-1 | Companion part for configuration management and the GDMO description of the X-interface model |
| EN 300 820-3 | Companion part for VP performance management |
| ITU-T X.722 | GDMO formalism for defining managed objects |
| ITU-T X.733 | Alarm reporting function and alarm structure |
| ITU-T X.721 | Definition of management information and log objects |
| ITU-T X.711 | Common management information protocol specification |
| ITU-T X.734 | Event report management function |
| ITU-T X.208 | Abstract Syntax Notation One (ASN.1) syntax |
| ITU-T G.805 | Generic functional architecture of transport networks |
| ITU-T M.3010 | TMN principles and responsibility model |
| ITU-T M.3400 | TMN management functions |
| ETSI ES 200 653 | Network-level generic class library |
| NMF025 | Ensemble concepts and format |
| ETSI TS 101 674-1 | ATM service technical framework and NNI user/control plane specification |
What does the SIST EN 300 820-2 V1.3.1:2003 document contain?
The document contains the alarm-management architecture, the definitions of the management resources, and the breakdown of alarm handling into notification, processing, and logging functions. It also includes example scenarios for sub-network faults and IPPL faults, showing how alarm messages move between operators.
Clause 9 adds the managed-object relationships through an inheritance tree, a naming tree, a GDMO-oriented description, and an ASN.1 module for the X-interface alarm model. The informative annex gives security aspects, especially access control around alarm notifications and alarm records.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 300 820-2 V1.3.1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Telecommunications Management Network (TMN); Asynchronous Transfer Mode (ATM) management information model for the X- interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected networks; Part 2: Alarm management". This standard covers: This document addresses the configuration management area, covering the following aspects: - the management services and functions needed to manage ATM connections, which span over several administrative domains. These management services and functions cover the fault management requirements for the X-interface; - the management information crossing the X-interface (using GDMO formalisms as described in ITU-T Recommendatio X.722).
This document addresses the configuration management area, covering the following aspects: - the management services and functions needed to manage ATM connections, which span over several administrative domains. These management services and functions cover the fault management requirements for the X-interface; - the management information crossing the X-interface (using GDMO formalisms as described in ITU-T Recommendatio X.722).
SIST EN 300 820-2 V1.3.1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.040.35 - Telephone networks. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 300 820-2 V1.3.1:2003 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.Telecommunications Management Network (TMN); Asynchronous Transfer Mode (ATM) management information model for the X- interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected networks; Part 2: Alarm management33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 300 820-2 Version 1.3.1SIST EN 300 820-2 V1.3.1:2003en01-november-2003SIST EN 300 820-2 V1.3.1:2003SLOVENSKI
STANDARD
ETSIEN300820-2V1.3.1(2000-11)EuropeanStandard(Telecommunicationsseries)TelecommunicationsManagementNetwork(TMN);AsynchronousTransferMode(ATM)managementinformationmodelfortheX-interfacebetweenOperationSystems(OSs)ofaVirtualPath(VP)/VirtualChannel(VC)crossconnectednetworks;Part2:AlarmmanagementSIST EN 300 820-2 V1.3.1:2003
ETSIETSIEN300820-2V1.3.1(2000-11)2ReferenceREN/TMN-GOM003-2KeywordsATM,alarm,B-ISDN,broadband,interface,management,switching,TMNETSI650RoutedesLuciolesF-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 300 820-2 V1.3.1:2003
ETSIETSIEN300820-2V1.3.1(2000-11)3ContentsIntellectualPropertyRights.4Foreword.41Scope.52References.53Definitionsandabbreviations.63.1Definitions.63.2Abbreviations.94Requirements.105ResourcesforATMVP/VCalarmmanagement.105.1Thebasisfortheexchangeofmanagementinformation.105.2Themanagedresources.116TheVP/VCalarmreportingmanagementfunctionsets.126.1VP/VCalarmreportingMS-Overview.126.2AlarmnotificationMFS.126.3AlarmprocessingMFS.136.4AlarmeventloggingMFS.147Managementfunctions.157.1Alarmnotificationmanagementfunctions.157.2Alarmprocessingmanagementfunction.197.3Alarmeventloggingmanagementfunction.198Scenarios.209Managementinformation.229.1Relationships.229.1.1Managedobjects.229.1.2Inheritancetree.239.1.3Namingtree.239.2X-interfaceGDMOdescription.259.3X-interfaceATMVP/VCalarmmanagementASN.1module.25AnnexA(informative):Securityaspects.26History.27SIST EN 300 820-2 V1.3.1:2003
ETSIETSIEN300820-2V1.3.1(2000-11)4IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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).Thepresentdocumentispart2ofamulti-partdeliverablecoveringthemanagementinformationmodelfortheX-typeinterfacebetweenOperationsSystems(OSs)ofaVirtualPath(VP)/VirtualChannel(VC)crossconnectednetwork,asidentifiedbelow:Part1:"Configurationmanagement";Part2:"Alarmmanagement";Part3:"VPPerformancemanagement".(VCPerformanceManagementaspectsareforfurtherstudy).NationaltranspositiondatesDateofadoptionofthisEN:24November2000DateoflatestannouncementofthisEN(doa):28February2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31August2001DateofwithdrawalofanyconflictingNationalStandard(dow):31August2001SIST EN 300 820-2 V1.3.1:2003
ETSIETSIEN300820-2V1.3.1(2000-11)51ScopeThepresentdocumentaddressestherequirementsofnetworkandserviceprovidersofAsynchronousTransferMode(ATM)crossconnectednetworksformanagingthefaultalarmsassociatedwiththeVirtualPath(VP)connectionsandVirtualChannel(VC)connections(generallydenotedas'VP/VCconnections'inthepresentdocument),whichspanseveraladministrativeATMdomains.Theserequirementsaresatisfiedbytheuseofastandardizedinterface(the"X-interface")betweenOperationSystems(OSs)belongingtodifferentNetworkOperators(PNOs).Readersofthepresentdocumentshouldbemadeawarethattheabbreviation'PNO'istakentomeanProvidingNetworkOperator.Inthepreviousversionofthepresentdocument(andrelateddocuments),PNOwasdefinedasPublicNetworkOperator.Thechangeindefinitionhasbeenprovidedtoreflectthechangeinmarketconditionsforprovisionofinterconnectedtelecommunicationsservices.However,itisconsiderednecessarytoretaintheabbreviation'PNO'becauseitisfoundinmanyofthemanagedobjectdefinitionsusedtospecifytheX-interface.Itwouldbedisadvantageoustointroducemajorchangesinthesemanagedobjectdefinitions,whichservepurelytechnicalpurposesformanagementofinterconnectionsonly.ThepresentdocumentshouldbeusedinconjunctionwithEN300820-1[1]andEN300820-3[14].ThepresentdocumentdescribestheX-interfaceVP/VCalarmmanagementareacoveringthefollowingaspects:-theManagementServices(MS)andfunctionsneededthatprovidethenecessaryalarmmessagesforfaultsdetectedandrelatedrecoveryprocedureswithinATMVPorVCConnectionswhichspanseveraladministrativedomains;-themanagementinformationcrossingtheX-interface.ThismanagementinformationspecificationusestheGuidelinesfortheDefinitionofManagedObjects(GDMO)formalism,describedinITU-TRecommendationX.722[2].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN300820-1:"TelecommunicationsManagementNetwork(TMN);AsynchronousTransferMode(ATM)ManagementinformationmodelforXinterfacebetweenOperationSystems(OSs)ofaVirtualPath(VP)/VirtualChannel(VC)crossconnectednetworks;Part1:Configurationmanagement".[2]ITU-TRecommendationX.722:"InformationTechnology-OpenSystemsInterconnection-Structureofmanagementinformation:Guidelinesforthedefinitionofmanagedobjects".[3]ITU-TRecommendationG.805:"GenericFunctionalArchitectureofTransportNetworks".[4]ETSIES200653:"TelecommunicationsManagementNetwork(TMN);Networklevelgenericclasslibrary".[5]ITU-TRecommendationM.3010:"PrinciplesforaTelecommunicationsManagementNetwork".[6]NetworkManagementForumNMF025:"The'Ensembles'ConceptsandFormat",Issue1.0,August1992.SIST EN 300 820-2 V1.3.1:2003
ETSIETSIEN300820-2V1.3.1(2000-11)6[7]ITU-TRecommendationX.733:"InformationTechnology-OpenSystemsInterconnection-SystemsManagement:Alarmreportingfunction".[8]ITU-TRecommendationX.711:"CommonmanagementinformationprotocolspecificationforITU-TApplications".[9]ITU-TRecommendationX.721:"DefinitionofManagementInformation".[10]ITURecommendationM.3400:"TMNmanagementfunctions".[11]ITU-TRecommendationX.734:"EventreportmanagementFunction".[12]ITU-TRecommendationX.208:"SpecificationofAbstractSyntaxNotationOne".[13]ETSITS101674-1:"TechnicalFrameworkfortheprovisionofinteroperableATMservices;Part1:NNI-InterfaceUserandControlplanespecification(includingnetworkfunctionsandserviceaspects)Phase1".[14]ETSIEN300820-3:"TelecommunicationsManagementNetwork(TMN);AsynchronousTransferMode(ATM)managementinformationmodelfortheXinterfacebetweenOperationSystems(OSs)ofaVirtualPath(VP)/VirtualChannel(VC)crossconnectednetworks;Part3:VPPerformancemanagement".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:(Somedefinitionsdependonthefutureacceptanceofthe"cascaded/mixedmode"asdescribedinEN300820-1[1].Thisdependenceisalreadytakenintoaccountinthesedefinitions.PNOisprovidedasthefirstdefinitioninordertohelpclarifyseveraldifferentPNOrolessubsequentlyprovidedinthelistbelow).ProvidingNetworkOperator(PNO):operatorabletoprovidenetworkresourcestocustomers(includingotherPNOs).ForthepurposesofthepresentdocumenttheseresourcesareATMVPorVCsubnetworkresourceswhichmaybeinterconnectedtocompatibleresourcesprovidedbyanotheroperatororcustomeraccesspoint:definedinITU-TRecommendationG.805[3]APNO:PNOwheretheInitiator(IPNO)startsreservingtheEnd-to-endVPorVCconnection.IftheterminationpointoftheconnectionisataUseraccesspoint,thisisconsideredtobetheAUserAccesspoint.TheAPNOcanbetheInitiatingPNO,butthisisnotalwaysthecase.ItistheConsumerofotherPNO'spartsoftheVP/VCconnectionNOTE1:If,infuturethe"cascaded"modeshouldbeacceptedasdefinedinEN300820-1[1],andiftheAPNOalsoactsasinitiatingPNO,thentheAPNOistheconsumeroftheotherPNO'spartsoftheVP/VCconnection.ATMInterconnectionGateway:representsanATMaccesspointinonesubnetwork,whichisassociatedwithanATMaccesspointinanothersubnetworkforthepurposeoftopologicalinterconnectionconnection:"transportentity"whichiscapableoftransferringinformationtransparentlybetween"connectionpoints(CP)".A"connection"definestheassociationbetweenthe"connectionpoints"andthe"connectionpoints"delimitthe"connection"consumerandproviderrolesofaPNO:withrespecttoaparticularEnd-to-endconnection,aPNOactsasaconsumerifithasdelegatedthemanagementofaVP/VCsubnetworkconnectionplustheoutgoinglinkconnectiontoanotherPNO(beingaProviderPNO).If,infuture,the"cascaded/mixed"modeshouldbeaccepted(EN300820-1[1]),aPNOcanhavebothrolesatonce,ifitisprovidingpartoftheEnd-to-endconnection(beingaProvider),andatthesametimeasksanotherPNOtoprovideapartoftheEnd-to-endconnection(beingaConsumer)destinationPNO:ZPNO(Thistermwasusedinolderversionsofthespecification)SIST EN 300 820-2 V1.3.1:2003
ETSIETSIEN300820-2V1.3.1(2000-11)7end-to-endconnection:overallConnectionwhichcanbeoneofthefollowingtypes:-User-to-userVPC/VCC;-Network-to-userVPC;-User-to-networkVPCorNetwork-to-networkVPC.Thesetypesaredefinedin[1].Foragivenend-to-endconnection,anyPNOmayactinanyoftheI,A,TorZPNOrolesaccordingtotheinterconnectionrequirementstoprovidetheserviceinitiatingNetworkOperator(IPNO):initiatingPNOisthePNOrequestingaparticularATMEnd-to-endconnection.ItstartsrequestinginthesubnetworkoftheAPNOandendsinthesubnetworkoftheZPNO;ItcontrolstheoverallEnd-to-endconnectionInterPNOPhysicalLink(IPPL):itrepresentsaphysicallinkthatoffersbi-directionaltransmissioncapabilitiesandconnectstwopnoVpSubnetworks.EachInterPNOPhysicalLinkisterminatedbytwopnoNWAtmAccessPointswhichareinchargeofemittingfailuresrelatedtothelinkortotheaccesspointitself.AnIPPLcanberealizedbyanytransmissioncapability(SDH,PDHetc.).ThereisnoexplicitmanagedobjectdefinedintheX-interfacethatrepresentsthisresource.InformationaboutIPPLsisincludedintheinterPnoTopologicalSubnetworkPairobjectEN300820-1[1]link:"topologicalcomponent"whichdescribesthefixedrelationshipbetweena"sub-network"andanother"sub-network"or"accessgroup".Itisdefinedbyanaccesspointononesub-network,whichisassociatedwithanaccesspointonanothersubnetworknetwork-to-networkVPC:VP"transportentity"formedbytheseriesof"connections"between"terminationCPs",startingatanATMInterconnectionGatewayandendingatanATMInterconnectionGateway.ThisinvolvestheATMresourcesofmorethanonePNO.TheNetwork-to-networkconnectionsthatarerelevanttotheXInterfaceareoftheVPtypenetwork-to-userVPC:VP"transportentity"formedbytheseriesof"connections"between"terminationCPs",startingatanATMInterconnectionGatewayandendingattheZUserAccesspointinthenetworkoftheZPNO.ThisinvolvestheATMresourcesofmorethanonePNO.TheNetwork-to-userconnectionsthatarerelevanttotheXInterfaceareoftheVPtypeProvidingNetworkOperator(PNO):operatorabletoprovidenetworkresourcestocustomers(includingotherPNOs)pnoVcSubnetwork:topologicalcomponentusedtoeffectroutingandmanagementofATMcells.Itdescribesthepotentialforsettingup"ATM-VCconnections"acrossthesubnetwork.ThepnoVcSubnetworksaredelineatedbyATMAccessPointsandinterconnectedby"inter-PNOPhysicallinks".ApnoVcSubnetworkcanbepartitionedintointerconnected"sub-networks"and"links",butthispartitioningisnotshownoverXInterface.Inthecontextofthepresentdocument,onepnoVcSubnetworkrepresentsanATMnetworkbelongingtoonePNOpnoVpSubnetwork:topologicalcomponentusedtoeffectroutingandmanagementofATMcells.Itdescribesthepotentialforsettingup"ATM-VPconnections"acrossthesubnetwork.ThepnoVpSubnetworksaredelineatedbyATMAccessPointsandinterconnectedby"inter-PNOPhysicallinks".ApnoVpSubnetworkcanbepartitionedintointerconnected"sub-networks"and"links",butthispartitioningisnotshownovertheX-interface.InthecontextofthepresentdocumentonepnoVpSubnetworkrepresentsanATMVpnetworkbelongingtoonePNONOTE2:Inprinciple(cf.toES200653[4])onesubnetworkcanconsistofseveralsubcomponents:subnetworksandconnectionsbetweensubnetworks.However,thiscapabilityisnotsupportedinthisspecificationfortheX-interface.UsuallyonepnoVpSubnetworkorpnoVcSubnetworkrepresentsanATMnetworkbelongingtothedomainonenetworkoperator.protectionswitching:automaticswitchingtopre-assignedsparecapacityinnetworkresources,consequentonreactiontoreceiptofanalarmsignalbyanetworkmanagementsystem.(Inthecontextofthepresentdocument,thisisinternaltoaPNO)recovery:recoveryisaprocedureperformedbyaPNOwhichmakesuseofsparecapacityinthesubnetworkorinter-pnophysicallinksbelongingtothisPNO.ItfollowsafteranalarmsignalfromafaultinthePNO'snetworkresourcesstarorganization:itisdescribedinEN300820-1[1].ItistheorganizationalformthatisusedinthisspecificationSIST EN 300 820-2 V1.3.1:2003
ETSIETSIEN300820-2V1.3.1(2000-11)8subnetwork:"topologicalcomponent"usedtoeffectroutingandmanagement.Itdescribesthepotentialfor"subnetworkconnections"acrossthe"sub-network".Itcanbepartitionedintointerconnected"sub-networks"and"links".Each"sub-network"inturncanbepartitionedintosmaller"sub-networks"and"links"andsoon.A"sub-network"maybecontainedwithinonephysicalnode.Inthepresentdocumentthispartitionisnotusedsubnetworkconnection:"transportentity"formedbya"connection"acrossa"sub-network"between"connectionpoints".Itcanbeconfiguredaspartofthe"trailmanagementprocess"asdefinedinITU-TRecommendationG.805[3]transitPNO(TPNO):transitPNOisaPNOusingitsownsubnetworktoperformitsrequiredtransitpartofVP/VCconnection.IthasaproviderroleandcorrespondstoaleafintheX-interfacetree,notbeingtheZside.Inthe"cascaded/mixedapproach"case(EN300820-1[1]),itcanbebothaprovider(whereitactsasaTransitoperator)andaConsumer(whereitvirtuallyactsasanInitiatingPNO)user:consumeroftheATMinterconnection,providedbytheEnd-to-endconnectionUser-to-networkVPC:"transportentity"formedbytheseriesof"connections"between"terminationCPs",startingattheAUserAccesspointinthenetworkoftheAPNOandendingatanATMInterconnectionGateway.ThisinvolvestheATMresourcesofmorethanonePNO.TheUser-to-networkconnectionsthatarerelevanttotheXInterfaceareoftheVPtypeuser-to-userVPC/VCC:"transportentity"formedbytheseriesof"connections"between"terminationCPs",startingattheAUserAccesspointinthenetworkoftheAPNOandendingattheZUserAccesspointinthenetworkoftheZPNO.ThisinvolvestheATMresourcesofmorethanonePNO.TheUser-to-userconnectionsthatarerelevanttotheXInterfacecanbeoftheVPtypeortheVCtypeVCsubnetworkconnection:"transportentity"whichiscapableoftransferringinformationtransparentlybetween"connectionpoints"acrossaVCsubnetworkorfromaVCsubnetworkaccesspointtoauserVPsubnetworkconnection:"transportentity"whichiscapableoftransferringinformationtransparentlybetween"connectionpoints"acrossaVPsubnetworkorfromaVPsubnetworkaccesspointtoauserX-interface:managementinterfacebetweentwoPNOs.Inthe"ResponsibilityModel",whichisdescribedinITU-TRecommendationM.3010[5],twoOperationsSystemsFunctions(=Managers)thatarelocatedindifferentTMNs(=differentPNOs),communicateoveranXReferencePointX-interfacetree:withrespecttoaparticularVPC/VCC,anX-interfacerelationshipexistsbetweeneachproviderPNOanditsconsumerPNO.Becauseeachproviderhasexactlyoneconsumer,theX-interfacerelationsbetweenallPNOsinvolvedinthemanagementofaparticularVPC/VCCformatree,theX-interfacerelationtree.Note,thatforaparticularVP/VCtherecanbeseveralpossibleX-interfacerelationtrees;theactualtreeisformedatVP/VCset-up.TherootofthetreeistheInitiatingPNO;ituses(usingX-interfacemanagementprocesses)thePNOs(oftentransitPNOs),towhichitisconnectedinthetreeviaitsbranches.ThemostrightleafofthetreeistheZPNO.Figure1showsanexampleofanX-interfacetreeZPNO:PNOwheretheInitiator(IPNO)endsreservingtheEnd-to-endVPorVCconnection.IftheterminationpointoftheconnectionisataUseraccesspoint,thisisconsideredtobetheZUserAccesspoint.Inthiscase,theIPNOviewstheZPNOasaPNOwhosesubnetisconnectedtotheZUserSIST EN 300 820-2 V1.3.1:2003
ETSIETSIEN300820-2V1.3.1(2000-11)9IPNOAPNOTPNOZPNOTPNOLegend:PNOProvidingNetworkOperatorIPNOInitiatingPNOAPNOAccessPNOTPNOTransitPNOZPNOTerminatingPNOFigure1:ExampleofanX-interfacetreewiththeInitiatingPNOnotbeingtheAPNO3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:APNOAccessPNO.ReferalsotoDefinitionsASN.1AbstractSyntaxNotation.1ATMAsynchronousTransferModeCMISECommonManagementInformationServiceElementCPConnectionPointeFDEventForwardingDiscriminatorENEuropeanNormETSEuropeanTechnicalStandardGDMOGuidelinesfortheDefinitionofManagedObjectsIPNOInitiatingPNO.ReferalsotoDefinitionsINMSInter-operatorNetworkManagementSystemIPPLInter-PNOPhysicalLinkITU-TInternationalTelecommunicationsUnion,TelecommunicationsStandardizationSectorMFSManagementFunctionSetMSManagementServiceNMSNetworkManagementSystemONMSOperator'sNetworkManagementSystemOSOperationsSystemPDHPlesiochronousDigitalHierarchyPNOProvidingNetworkOperatorPSProtectionSwitchingQALogQualifiedAlarmLogRALogReceivedAlarmLogSALogSentAlarmLogSDHSynchronousDigitalHierarchyTPNOTransitPNO.ReferalsotoDefinitionsTMNTelecommunicationsManagementNetworkVCVirtualChannelVCCVirtualChannelConnectionVCSCVirtualChannelSubnetworkConnectionVPVirtualPathVPCVirtualPathConnectionVPSCVirtualPathSubnetworkConnectionX-typeNetworkManagementinterfacebetweentelecommunicationsoperatorsSIST EN 300 820-2 V1.3.1:2003
ETSIETSIEN300820-2V1.3.1(2000-11)104Requirements1)Incaseoffaults,itshouldbepossibletolocalizefaultsonaPNOsub-networkand/orIPPLlevel.2)AllpartieswhichareaffectedbyafaultyPNOsub-networkaretobeinformedofthefailure.3)AllalarminformationpassedacrosstheX-interfaceshouldbetime-stamped.4)EliminationofredundantmultiplealarmsrelatingtoasingleunderlyingcausebeforethealarminformationistransmittedacrosstheX-interface.5)Protectionswitchingandtheresultoftheprotectionshouldbenotified.6)Under_recoveryactionsandtheresultsofunder_recoveryactionsshouldbenotified.7)Itshouldbepossibletoenable/disablealarmreportingonagivenconnectionorgroupofconnections.5ResourcesforATMVP/VCalarmmanagement5.1ThebasisfortheexchangeofmanagementinformationThearchitecturalframeworkcharacterizingtheexchangeofmanagementinformationacrosstheX-interfaceisrepresentedinfigure2.X-interfaceRemoteINMSPNOVP/VCSubnetworkQinterfaceONMSAlarmNotificationMSLegend:PNOProvidingNetworkOperatorONMSOperatorNetworkManagementSystemINMSInter-operatorNetworkManagementSystemMSManagementServiceVP/VCVirtualPathorVirtualChannelPNOVP/VCSubnetworkQinterfaceONMSINMSAlarmNotificationMSOtherX-interfaceMS’s[1],[2]OtherX-interfaceMS’s[1],[2]Figure2:ArchitecturalframeworkfortheX-interfaceInfigure2,theterm"ONMS"isdefinedasanOperatorNetworkManagementSystem.ForthepurposeofthepresentdocumenttheONMSistakentobethemanagementsystemwhichcontrolsanoperator'sVP/VCsubnetworkwhichisinterconnectedtoanotheroperator'scompatibleVP/VCsubnetwork.(InterconnectionattheVP/VCsubneworklevelisnotshowninfigure2butmayinaccordancewiththespecificationdefinedinTS101674-1[13]).Thetermdenotedas'INMS'isdefinedasanInter-operatorNetworkManagementSystem."INMS"canbeconsideredasanoperator'smanagementsystemforanX-interfaceinterconnectionwithanotheroperator,whetherwithinnationalboundariesoracrossthem.ThedistinctionbetweenONMSandINMShasbeenmadebecausethesetwosystemsactondifferentInformationModelsandbecausethereisthenecessityofexchangeofinformationbetweenthem.Thelogicalpositioningofthe"Q"interface,whichbasicallycontrolsnetworkswitchesinthePNOVP/VCSubnetwork,isalsoindicatedbutanymattersrelatingtothisinterfaceareoutsidethescopeofthepresentdocument.SIST EN 300 820-2 V1.3.1:2003
ETSIETSIEN300820-2V1.3.1(2000-11)11TheINMSbelongingtoanyoperatorhastosupportthefollowingoperationsasfarastheAlarmNotificationMSisconcerned:-receptionofnotificationscomingfromaremoteINMS.Thesenotificationsaredescribedindetailinsubclause7.1;-receptionofalarmscomingfromtheONMSandrelevanttotheX-interface.ThesealarmsareassociatedwithfaultyVP/VCconnectionsusedforend-to-endconnections(theymaybePhysicalLayeralarmsorVP/VCLayeralarmsorfaultsaffectingtheATMCrossConnectwhichactsastheinter-networkgateway);-elaborationofalarmscomingfromtheONMS(qualificationandadaptationtointer-networkalarmformat);-sendingofalarmstotheappropriatePNOs(InitiatingPNOinthecaseofaVPSCorVCSCfaultorallPNOsinthecaseofInter-PNOPhysicalLink(IPPL)fault);-loggingalarmsandretrievingalarmreports.5.2ThemanagedresourcesAsimplifiedviewofthenetworklevelresourcesbeingmanagedisprovidedinfigure3.Thisviewisprovidedintheformofanexampleofthemanagementviewafterauser-to-userVPorVCconnectionhasbeensetup.Furtherdetailsandrelatedexamplesareprovidedin[1].Figure3showstheX-interfacesbetweentheIPNOandotherPNOswhichmaybeusedtosupporttheVP/VCalarmmanagementfunctionsdefinedinthepresentdocument.TheNMS'sassociatedwiththeA,TandZPNOsmayormaynothaveINMSfunctionalityimplementedasdefinedinsubclause5.1.X-interfaceX-interfaceQ-interface11111145545511APNONMSTPNONMSZPNONMS3Legend:1’pnoNWAtmAccessPointforuseraccess(noassociationwith(2))1:pnoNWAtmAccessPoint4:pnoVpSubnetworkConnectionorpnoVcSubnetworkConnection2:interPnoTopologicalSubnetworkPair5:pnoVPCTPorpnoVCCTP(VP/VCConnectionTerminationPoint)3:pnoVpSubnetworkorpnoVcSubnetworkNMS:NetworkManagementSystem(maycontainONMSandINMS)IPNOAPNOX-interfaceTPNOZPNOViewonX.InterfaceattheTPNONMSViewonXInterfaceattheAPNONMSViewonXInterfaceattheZPNONMSQ-interfaceQ-interface22221’User-access-point4551’User-access-point33IPNOINMSFigure3:X-interfacemanagednetworkresourcesandconnectionsSIST EN 300 820-2 V1.3.1:2003
ETSIETSIEN300820-2V1.3.1(2000-11)126TheVP/VCalarmreportingmanagementfunctionsets6.1VP/VCalarmreportingMS-OverviewIndefiningtheVP/VCAlarmReportingManagementService(MS)fortheX-interfaceandfollowingtheEnsemblesconcept,definedbytheNetworkManagementForumNMF025[6],someManagementFunctionSets(MFS)havebeenidentified.EachMFShasbeendecomposedinMF.ThefollowingMFSshavebeenidentifiedtomanagethenotificationsdescribedinclause7:-AlarmnotificationMFS;-AlarmeventloggingMFS;-AlarmprocessingMFS.TheidentifiedVP/VCsAlarmReportingMFSsareorganizedasdepictedinfigure4anddescribedinmoredetailinsubclauses6.2,6.3and6.4.(NotethatdetailsofimplementationoftheINMSfunctions,MSsanddatabasesareaninternalmatterforanyPNOwishingtoprovideanX-interfaceinaccordancewiththespecificationinthepresentdocumentandthereforeimplementationguidanceorspecificationsareoutsidethescopeofthepresentdocument).XInterfaceONMSINMSAlarmEventLogMFSAlarmNotificationMFSAlarmProcessingMFSAlarmMgtDataBaseVP/VCAlarmManagementMSOtherX-interfaceMS’s[1],[2]Figure4:MFSsandotherX-interfaceMSsrelativetotheVP/VCalarmmanagementMS6.2AlarmnotificationMFSThisMFSperformsthefollowingtasks:transmissionoffaultyVP/VCalarmnotificationsacrosstheX-interface;thesenotificationscontainthefollowingparameters:-subnetworkId,resourceid(vpConnectionIdorvcConnectionIdoratmAccessPoi
...