General Information

Abstract

Extension of the current ETS 300 820-1 to include configuration of Permanent Virtual Circuits, to support the differences between ATC and QoS classes and the support of matching orders.

Status
Published
Publication Date
31-Oct-2003
ICS
33.040.35 - Telephone networks
Technical Committee
SPN - Services and Protocols for Networks
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Nov-2003
Due Date
01-Nov-2003
Completion Date
01-Nov-2003
Ref Project
ETSI EN 300 820-1 V1.2.1 (2000-11) - Telecommunications Management Network (TMN); Asynchronous Transfer Mode (ATM) management information model for X interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected networks; Part 1: Configuration management

Buy Documents

SIST EN 300 820-1 V1.2.1:2003 - Page 1 previewSIST EN 300 820-1 V1.2.1:2003 - Page 2 previewSIST EN 300 820-1 V1.2.1:2003 - Page 3 previewSIST EN 300 820-1 V1.2.1:2003 - Page 4 preview
PreviousNext
Standard

SIST EN 300 820-1 V1.2.1:2003

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

Overview

SIST EN 300 820-1 V1.2.1:2003 is a key standard from the Slovenski inštitut za standardizacijo (SIST) that outlines the configuration management requirements for the Telecommunications Management Network (TMN) within Asynchronous Transfer Mode (ATM) cross-connected networks. This standard specifically addresses the X interface between Operation Systems (OSs) for configuring and managing Virtual Path (VP) and Virtual Channel (VC) connections spanning multiple administrative ATM domains. An important extension of the European standard EN 300 820-1, it includes the configuration of Permanent Virtual Circuits (PVCs) and supports both ATM Traffic Classes (ATC) and Quality of Service (QoS) classes, as well as mechanisms for matching configuration orders.

TMN standards such as this provide a framework for multi-vendor, multi-operator network management, ensuring interoperability and effective ATM configuration management.

Key Topics

  • Management Architecture
    Defines how the X interface operates between service or network providers, facilitating cooperation between different network domains in the establishment and management of VP/VC connections.

  • Configuration Management
    Addresses the processes and information models required for establishing, maintaining, and releasing ATM VP and VC connections, including support for Permanent Virtual Circuits.

  • ATM Connection Management Services and Functions
    Details the necessary management services, including the management of both resource allocation and connection resilience across service provider boundaries. This also includes establishment, modification, and termination of virtual paths and virtual channels.

  • Information Model for the X Interface
    Specifies a comprehensive information model based on ITU-T and ETSI recommendations, leveraging managed objects defined with GDMO (Guidelines for the Definition of Managed Objects) as per ITU-T X.722.

  • Interoperability across Administrative Domains
    Ensures that network and service providers can reliably manage connections that cross multiple administrative and technological boundaries, a necessity within the global telecommunications infrastructure.

Applications

The SIST EN 300 820-1 V1.2.1:2003 standard delivers practical guidance for:

  • Telecommunications Operators and Service Providers
    Enabling unified configuration, control, and management of ATM-based networks, even when those networks span multiple organizations or geographic regions.

  • ATM Network Equipment Vendors
    Assisting manufacturers in implementing network management interfaces that comply with European and international TMN standards, ensuring device interoperability.

  • Network Management System Developers
    Providing a standardized information model and service architecture for developing robust network management software solutions that interface with various operations systems using the ATM X interface.

  • Cross-Domain Network Configuration
    Facilitating secure and consistent configuration of VPs, VCs, and PVCs, with clear guidelines for managing quality of service and resiliency, necessary for critical business and public communication infrastructure.

Related Standards

Key related documents and standards include:

  • ETSI EN 300 820-2
    Alarm management for ATM management information model for the X interface.

  • ETSI EN 300 820-3
    VP performance management for the X interface.

  • ITU-T M.3100 & M.3010
    Generic network information model and telecommunications management network principles.

  • ITU-T X.722
    Guidelines for the definition of managed objects.

  • ITU-T I.751
    Management of the ATM network element view.

  • ETSI ES 200 653
    Network level generic class library for telecommunications management.

Conclusion

By adhering to SIST EN 300 820-1 V1.2.1:2003, network providers, equipment vendors, and software developers can achieve a consistent, standardized approach to ATM network configuration management. This supports seamless service delivery, robust cross-domain network operation, and lays the foundation for future advancements in telecommunications management.

Buy Documents

SIST EN 300 820-1 V1.2.1:2003 - Page 1 previewSIST EN 300 820-1 V1.2.1:2003 - Page 2 previewSIST EN 300 820-1 V1.2.1:2003 - Page 3 previewSIST EN 300 820-1 V1.2.1:2003 - Page 4 preview
PreviousNext
Standard

SIST EN 300 820-1 V1.2.1:2003

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

Get Certified

Connect with accredited certification bodies for this standard

ANCE

Mexican certification and testing association.

EMA Mexico Verified
Visit Website

Intertek Slovenia

Intertek testing, inspection, and certification services in Slovenia.

UKAS Slovenia Verified
Visit Website

LNE (Laboratoire National de Métrologie et d'Essais)

French national laboratory for metrology and testing.

COFRAC France Verified
Visit Website

Sponsored listings

Frequently Asked Questions

SIST EN 300 820-1 V1.2.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 X interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected networks; Part 1: Configuration management". This standard covers: Extension of the current ETS 300 820-1 to include configuration of Permanent Virtual Circuits, to support the differences between ATC and QoS classes and the support of matching orders.

Extension of the current ETS 300 820-1 to include configuration of Permanent Virtual Circuits, to support the differences between ATC and QoS classes and the support of matching orders.

SIST EN 300 820-1 V1.2.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-1 V1.2.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 X interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected networks; Part 1: Configuration management33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 300 820-1 Version 1.2.1SIST EN 300 820-1 V1.2.1:2003en01-november-2003SIST EN 300 820-1 V1.2.1:2003SLOVENSKI
STANDARD
ETSIEN300820-1V1.2.1(2000-11)EuropeanStandard(Telecommunicationsseries)TelecommunicationsManagementNetwork(TMN);AsynchronousTransferMode(ATM)managementinformationmodelforXinterfacebetweenOperationSystems(OSs)ofaVirtualPath(VP)/VirtualChannel(VC)crossconnectednetworks;Part1:ConfigurationmanagementSIST EN 300 820-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)2ReferenceREN/TMN-GOM003-1KeywordsATM,B-ISDN,configuration,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-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)3ReferenceREN/TMN-GOM003-1KeywordsATM,B-ISDN,configuration,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-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)4ContentsIntellectualPropertyRights.8Foreword.81Scope.92References.93Definitionsandabbreviations.103.1Definitions.103.2Abbreviations.154Managementarchitecture.164.1X-interfaceattheServiceManagementlevel.164.2Consumer/Provider.174.3Organizationalmodel.184.4ResponsibilityofPNOsregardingaVPconnection.184.4.1BasicVPconnectionresponsibilityrules.184.4.2Examplesofapplicationoftheresponsibilityrules.195Void.206ConfigurationManagementandResilienceRequirements.206.1ATMVPresiliencerequirements.217Managementservices.227.1Managementservices.227.2ManagementServiceComponents(MSC).227.2.1EstablishMSC.227.2.2ReleaseMSC.247.2.3ModificationMSC.247.2.4ReconfigurationMSC.257.2.5ContinuityCheckMSC.257.2.6ResilienceMSC.277.3ManagementFunctions(MF).307.3.1ActivateBidirectionalContinuityMonitorSourceforContinuityCheck.307.3.2ActivateChange.317.3.3ActivateVCSubnetworkConnection.317.3.4ActivateVPLinkConnection.317.3.5ActivateVPSubnetworkConnection.317.3.6AllowF4flow.317.3.7AllowF5flow.327.3.8CancelChange.327.3.9CancelVCSubnetworkConnection.327.3.10CancelVPLinkConnection.327.3.11CancelVPSubnetworkConnection.337.3.12ChangeReservation.337.3.13CheckAvailableCellRate.337.3.14CreateBidirectionalContinuityMonitorforContinuityCheck.347.3.15DeactivateBidirectionalContinuityMonitorSourceforContinuityCheck.347.3.16DeactivateVCSubnetworkConnection.357.3.17DeactivateVPLinkConnection.357.3.18DeactivateVPSubnetworkConnection.357.3.19DeleteBidirectionalContinuityMonitor.367.3.20DestinationUserChecking.367.3.21NotificationofBidirectionalContinuityMonitorOperationalStateChange.377.3.22ReleaseVCSubnetworkConnection.377.3.23ReleaseVPLinkConnection.377.3.24ReleaseVPSubnetworkConnection.377.3.25ReportofContinuityCheck.38SIST EN 300 820-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)57.3.26ReserveEnhancedVPSubnetworkConnection.387.3.27ReserveVCSubnetworkConnection.397.3.28ReserveVPLinkConnection.417.3.29ReserveVPSubnetworkConnection.427.3.30StopF4flow.427.3.31StopF5flow.437.3.32SwitchToSubnetworkConnection.437.3.33TopologyInfoChanges.438Managementinformationmodel.448.1Introduction.448.2Inheritancetree.458.3EntityRelationshipDiagram.468.4ES200653,ITU-TRecommendationsI.751andX.721ObjectClassesadaptedforXIF.478.4.1Connectivity.478.4.2LinkConnection.488.4.3SubnetworkConnection.488.4.4NetworkTP.498.4.5NetworkCTPSink.508.4.6NetworkCTPSource.508.4.7NetworkTTPsink.508.4.8NetworkTTPsource.518.4.9NetworkCTPBi-directional.518.4.10NetworkTTPbi-directional.518.4.11AdminDomain.518.4.12SubnetworkPair.528.4.13Sub-Network.528.4.14bidirectionalContinuityMonitor.538.4.15system.538.5ATMXVP/VCObjectClasses.548.5.1Introduction.548.5.2ConnectionFragment.578.5.3ConnectionTerminationPointFragment.608.5.4TopologyFragment.618.5.5ContinuityCheckFragment.648.6PackageDefinitions.648.6.1AttributeValueChangeNotification.648.6.2cancelVcNetworkConnectionNotification.648.6.3cancelVpLinkConnectionNotification.648.6.4cancelVpNetworkConnectionNotification.648.6.5CreateDeleteNotification.648.6.6flowDirection.648.6.7KindOfResilience.648.6.8relatedSnc.658.6.9StateChangeNotification.658.6.10switchToSnc.658.6.11TMNCommunicationAlarmInformation.658.6.12vcTestState.658.6.13vpPerformAndResilience.658.6.14vpTestState.668.7AttributeDefinitions.668.7.1AssociatedSubNetworkPairId.668.7.2BackwardQoSClass.668.7.3ChangeReservationInformation.668.7.4continuityMonitorId.668.7.5ForwardQoSClass.678.7.6InitiatingPnoSubnetworkId.678.7.7InitiatingVcConnectionId.678.7.8InitiatingVpConnectionId.678.7.9kindOfResilience.678.7.10ListofATMAccessPointPairResources.688.7.11MaxNumVCIBitsSupported.68SIST EN 300 820-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)68.7.12MaxNumVPIBitsSupported.688.7.13OperationalState.688.7.14PNONWAccessPointId.688.7.15relatedSNC.688.7.16sinkCCMecanismActive.688.7.17sourceCCMechanismActive.688.7.18TrailTerminationPointId.688.7.19VCCTPId.688.7.20VCSchedulers.698.7.21vcTestState.698.7.22VPCTPId.698.7.23VPSchedulers.698.7.24vpTestState.698.8AttributeGroupDefinitions.698.9ParameterDefinitions.698.10NotificationDefinitions.708.10.1CancelVCNetworkConnectionNotification.708.10.2CancelVPLinkConnectionNotification.708.10.3CancelVPNetworkConnectionNotification.708.11ActionDefinitions.708.11.1ActivateChange.708.11.2CheckUser.708.11.3controlCC.718.11.4GiveAvailableLinks.718.11.5ReleasePNOVCSubnetworkConnection.718.11.6ReleasePNOVPLinkConnection.718.11.7ReleasePNOVPSubnetworkConnection.718.11.8ReservePNOEnhancedVpSubnetworkConnection.728.11.9ReservePnoVcSubnetworkConnection.728.11.10ReservePNOVPLinkConnection.748.11.11ReservePNOVPSubnetworkConnection.758.11.12switchToSnc.768.12NameBindingDefinitions.768.12.1interPnoTopologicalSubnetworkPair-pnoVcSubnetwork.768.12.2interPnoTopologicalSubnetworkPair-pnoVpSubnetwork.778.12.3interPnoTopologicalSubnetworkPair-pnoVpSubnetworkR2.778.12.4pnoBidirectionalContinuityMonitor-pnoVCCTP.778.12.5pnoBidirectionalContinuityMonitor-pnoVPCTP.778.12.6pnoNWAtmAccessPoint-pnoVpSubnetwork.778.12.7PnoNWAtmAccessPointR2-pnoVcSubnetwork.788.12.8pnoNWAtmAccessPointR2-pnoVpSubnetworkR2.788.12.9pnoVCCTP-pnoVPTTP.788.12.10pnoVcSubnetwork-system.798.12.11pnoVcSubnetworkConnection-pnoVcSubnetwork.798.12.12pnoVPCTP-pnoNWAtmAccessPoint.798.12.13pnoVPCTP-pnoNWAtmAccessPointR2.798.12.14PnoVpLinkConnection-interPnoTopologicalSubnetworkPair.798.12.15pnoVpSubnetworkConnection-pnoVpSubnetwork.808.12.16pnoVpSubnetworkConnectionR2-pnoVpSubnetworkR2.808.12.17pnoVpSubnetworkR2-system.808.12.18pnoVPTTP-pnoNWAtmAccessPointR2.808.12.19Subnetwork-system.808.13ASN.1Module.81SIST EN 300 820-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)7AnnexA(informative):AbouttheinfluenceoftimersontheX-interfacecommunication.86AnnexB(informative):SecurityAspects.87AnnexC(informative):ATMVP/VCResilience.88AnnexD(informative):MappingbetweenManagementFunctions,CMISEServicesandObjectClasses.92AnnexE(informative):MappingparametersVpQosClassandVcQosClasstoATMQoS.94AnnexF(informative):FutureOrganizationalModels.95F.1ResponsibilityofPNOsregardingaVP/VCconnection.96F.1.1Examplesofapplicationoftheresponsibilityrules.96F.2Scenarios.98AnnexG(informative):TrafficDescriptorreferenceproblems.102Bibliography.104History.105SIST EN 300 820-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)8IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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).Thepresentdocumentispart1ofamulti-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-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)91ScopeThepresentdocumentaddressestherequirementsofnetworkandserviceprovidersofAsynchronousTransferMode(ATM)crossconnectednetworksforestablishing,maintainingandreleasingVirtualPath(VP)and/orVirtualChannel(VC)connections(generallydenotedas'VP/VCconnections'inthepresentdocument),whichspanseveraladministrativeATMdomains.Theserequirementsaresatisfiedbytheuseofastandardizedinterface(the"X-interface")betweenOperationSystemsbelongingtodifferentnetworkoperators.Readersofthepresentdocumentshouldbemadeawarethattheabbreviation'PNO'istakentomeanProvidingNetworkOperator.Inthepreviousversionofthepresentdocument(andrelateddocuments),PNOwasdefinedasPublicNetworkOperator.Thechangeindefinitionhasbeenprovidedtoreflectthechangeinmarketconditionsforprovisionofinterconnectedtelecommunicationsservices.However,itisconsiderednecessarytoretaintheabbreviation'PNO'becauseitisfoundinmanyofthemanagedobjectdefinitionsusedtospecifytheX-interface.Itwouldbedisadvantageoustointroducemajorchangesinthesemanagedobjectdefinitions,whichservepurelytechnicalpurposesformanagementofinterconnectionsonly.ThepresentdocumentcontainsageneraloverviewdescribingthedifferentmanagementareasthatwillbecoveredinthedifferentX-interfaceENs-configuration,alarmandperformance-aswellastherelationshipsbetweenthem.Thepresentdocumentdescribestheconfigurationmanagementareacoveringthefollowingaspects:-amanagementarchitecturethatshowshowtheX-interfaceistobeusedbetweenserviceornetworkproviders;-themanagementservicesandfunctionsneededtomanageATMconnections,whichspanseveraladministrativedomains.ThesemanagementservicesandfunctionscovertherequirementsfortheX-interface;-themanagementinformationcrossingtheX-interface.ThismanagementinformationspecificationusestheGuidelinesfortheDefinitionofManagedObjectsGDMOformalism,describedinITU-TRecommendationX.722[4].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ITU-TRecommendationM.3100:"Genericnetworkinformationmodel".[2]ITU-TRecommendationM.1400:"Designationsforinternationalnetworks".[3]ITU-TRecommendationI.751(1996):"AsyncronousTransferModeManagementOfTheNetworkElementView".[4]ITU-TRecommendationX.722:"GuidelinesforthedefinitionofmanagedobjectsforITU-Tapplications".[5]ETSIEN300820-2:"TelecommunicationsManagementNetwork(TMN);AsynchronousTransferMode(ATM)managementinformationmodelfortheXinterfacebetweenOperationSystems(OSs)ofaVirtualPath(VP)/VirtualChannel(VC)crossconnectednetworks;Part2:Alarmmanagement".SIST EN 300 820-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)10[6]ITU-TRecommendationI.630(1999):"IntegratedServicesDigitalNetwork,MaintenancePrinciples:ATMProtectionSwitching"(PrepublishedRecommendation).[7]ITU-TRecommendationM.3010(1996):"PrinciplesforaTelecommunicationsmanagementnetwork".[8]ETSIEN300820-3:"TelecommunicationsManagementNetwork(TMN);AsynchronousTransferMode(ATM)managementinformationmodelfortheXinterfacebetweenOperationSystems(OSs)ofaVirtualPath(VP)/VirtualChannel(VC)crossconnectednetworks;Part3:VPPerformancemanagement".[9]ETSIES200653(V1.2.1):"TelecommunicationsManagementNetwork(TMN);Networklevelgenericclasslibrary".[10]ITU-TRecommendationX.721:"Informationtechnology-OpenSystemsInterconnection-Structureofmanagementinformation:Definitionofmanagementinformation".[11]ISO/IEC10165-2:"Informationtechnology-OpenSystemsInterconnection-Structureofmanagementinformation:Definitionofmanagementinformation".[12]ETSIETS300469(1997):"BroadbandIntegratedServicesDigitalNetwork(B-ISDN);AsynchronousTransferMode(ATM);Managementofthenetworkelementview[ITU-TRecommendationI.751(1996)]".[13]ETSIEN300820-1(V1.1.1):"TelecommunicationsManagementNetwork(TMN);ManagementinformationmodelfortheX-typeinterfacebetweenOperationSystems(OSs)ofaVirtualPath(VP)/VirtualChannel(VC)crossconnectednetwork;Part1:Configurationmanagementaspects".[14]ITU-TRecommendationI.356:"B-ISDNATMLayerCellTransferPerformance".3Definitionsandabbreviations3.1Definitions(Somedefinitionsdependonthefutureacceptanceofthe"cascaded/mixedmode"asdescribedinannexD.Thisdependenceisalreadytakenintoaccountinthesedefinitions).Forthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:APNO:PNOwheretheInitiatorstartsreservingtheend-to-endVPorVCconnectionNOTE1:IftheterminationpointoftheconnectionisataUseraccesspoint,thisisconsideredtobetheAUserAccesspoint.TheAPNOcanbetheInitiatingPNO,butthisisnotalwaysthecase.ItistheConsumerofotherPNO'spartsoftheVP/VCconnection.ATMAccesspoint:meansbywhichasubnetworkoffersexternalinterfacestoothersubnetworksNOTE2:ItisassociatedwithanendpointofanIPPL.ATMInterconnectionGateway:ATMaccesspointinonesubnetwork,whichisassociatedwithanATMaccesspointinanothersubnetworkforthepurposeoftopologicalinterconnectionconnection:"transportentity"whichiscapableoftransferringinformationtransparentlybetween"connectionpoints(CP)"NOTE3:A"connection"definestheassociationbetweenthe"connectionpoints"andthe"connectionpoints"delimitthe"connection".SIST EN 300 820-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)11consumerandproviderrolesofaPNO:withrespecttoaparticularEnd-to-endconnection,aConsumerPNOisaPNOthathasdelegatedthemanagementofasubnetworkconnectionplustheoutgoinglinkconnectiontoanotherPNO(beingaProviderPNO)NOTE4:If,infuture,the"cascaded/mixed"modeshouldbeaccepted(annexD)aPNOcanhavebothrolesatthesametime,ifitisprovidingpartoftheEnd-to-endconnection(beingaProvider),andatthesametimeasksanotherPNOtoprovideapartoftheEnd-to-endconnection(beingaConsumer).end:pointwhereaconnectionterminatesandwhichisassociatedwithanaddressNOTE5:TheaddressshouldbespecifiedinaccordancewithITU-TRecommendationM.1400[2].end-to-endConnection:overallConnectionwhichcanbeoneofthefollowingtypes:User-to-userVPC/VCC,Network-to-userVPC,User-to-networkVPCorNetwork-to-networkVPC)NOTE6:Thesetypesaredefinedintheremainderofthissubclause.NOTE7:Foragivenend-to-endconnection,anyPNOmayactinanyoftheI,A,TorZPNOrolesaccordingtotheinterconnectionrequirementstoprovidetheservice.EXAMPLE1:Figures2and3providesomeexamplesofend-to-endconnections.InterPNOPhysicalLink(IPPL):representsaphysicallinkthatoffersbidirectionaltransmissioncapabilitiesandconnectstwosubnetworks.EachInterPNOPhysicalLinkisterminatedbytwoATMAccessPointswhichareinchargeofemittingfailuresrelatedtothelinkortotheaccesspointitself.AnIPPLcanberealizedbyanytransmissioncapability(SDH,PDHetc.)IPNO:initiatingPNO.ItisthePNOrequestingforaparticularATMend-to-endconnection.ItstartsrequestinginthesubnetworkoftheAPNOandendsinthesubnetworkoftheZPNO.Itcontrolstheend-to-endconnectionlink:"topologicalcomponent"whichdescribesthefixedrelationshipbetweena"sub-network"andanother"sub-network"or"accessgroup".Itisdefinedbyanaccesspointononesub-network,whichisassociatedwithanaccesspointonanothersubnetworklinkconnection:linkconnectionissupportedbyatrailintheserverlayernetwork.ItiscapableoftransferringinformationtransparentlyacrossalinkbetweentwoconnectionpointsorbetweenaterminationconnectionpointandaconnectionpointinthecaseofalinkconnectionattheboundaryofalayernetworkNOTE8:Figures2and3showhowalinkconnectionisapartofanend-to-endconnection.network-to-networkVPC:VP"transportentity"formedbytheseriesof"connections"between"terminationCPs",startingatanATMInterconnectionGatewayandendingatanATMInterconnectionGateway.ThisinvolvestheATMresourcesofmorethanonePNO.TheNetwork-to-networkconnectionsthatarerelevanttotheXInterfaceareoftheVPtype(Figure2showshowaNetwork-to-networkconnectionisbuildupbyaseriesofotherconnections)network-to-userVPC:VP"transportentity"formedbytheseriesof"connections"between"terminationCPs",startingatanATMInterconnectionGatewayandendingattheZUserAccesspointinthenetworkoftheZPNO.ThisinvolvestheATMresourcesofmorethanonePNO.TheNetwork-to-userconnectionsthatarerelevanttotheXInterfaceareoftheVPtypePNO:providingNetworkOperator.AnoperatorabletoprovidenetworkresourcestocustomerspnoVcSubnetwork:topologicalcomponentusedtoeffectroutingandmanagementofATMcells.Itdescribesthepotentialforsettingup"ATM-VCconnections"acrossthesubnetwork.ThepnoVcSubnetworksaredelineatedbyATMAccessPointsandinterconnectedby"inter-PNOPhysicallinks"NOTE9:ApnoVcSubnetworkcanbepartitionedintointerconnected"sub-networks"and"links",butthispartitioningisnotshownoverXInterface.Inthecontextofthepresentdocument,onepnoVcSubnetworkrepresentsanATMnetworkbelongingtoonePNO.pnoVpSubnetwork:topologicalcomponentusedtoeffectroutingandmanagementofATMcells.Itdescribesthepotentialforsettingup"ATM-VPconnections"acrossthesubnetwork.ThepnoVpSubnetworksaredelineatedbyATMAccessPointsandinterconnectedby"inter-PNOPhysicallinks"SIST EN 300 820-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)12NOTE10:ApnoVpSubnetworkcanbepartitionedintointerconnected"sub-networks"and"links",butthispartitioningisnotshownoverXinterface.Inthecontextofthepresentdocument,onepnoVpSubnetworkrepresentsanATMnetworkbelongingtoonePNO.sub-network:"topologicalcomponent"usedtoeffectroutingandmanagement.Itdescribesthepotentialfor"sub-networkconnections"acrossthe"sub-network".Itcanbepartitionedintointerconnected"sub-networks"and"links".Each"sub-network"inturncanbepartitionedintosmaller"sub-networks"and"links"andsoon.A"sub-network"maybecontainedwithinonephysicalnode.Inthepresentdocumentthispartitionisnotusedsub-networkconnection:subnetworkconnectioniscapableoftransferringinformationtransparentlyacrossasubnetwork.Itisdelimitedbyconnectionterminationpointsattheboundaryofthesubnetworkandrepresentstheassociationbetweentheseconnectionpoints.ItcanbeaVPoraVCconnectionsubnetworkview:subtreeoftheX-interfacetree.AsubnetworkviewbelongstoaparticularPNO:ThePNOattherootofthesubtree.TPNO:transitPNO.ThisisaPNOusingitsownsubnetworktoperformitsrequiredtransitpartofVPconnection.IthasaproviderroleandcorrespondstoaleafintheX-interfacetree,notbeingtheZside.Inthe"cascaded/mixedapproach"caseitcanbebothaProvider(whereitactsasaTransitoperator)andaConsumer(whereitvirtuallyactsasanInitiatingoperator)trail:definedinES200653[9]user:consumeroftheATMinterconnection,providedbytheend-to-endconnectionuser-to-networkVPC:"transportentity"formedbytheseriesof"connections"between"terminationCPs",startingattheAUserAccesspointinthenetworkoftheAPNOandendingatanATMInterconnectionGateway.ThisinvolvestheATMresourcesofmorethanonePNO.TheUser-to-networkconnectionsthatarerelevanttotheXInterfaceareoftheVPtypeNOTE11:Figure2showshowaUser-to-networkconnectionisbuildupbyaseriesofotherconnections.User-to-userVPC/VCC:"transportentity"formedbytheseriesof"connections"between"terminationCPs",startingattheAUserAccesspointinthenetworkoftheAPNOandendingattheZUserAccesspointinthenetworkoftheZPNO.ThisinvolvestheATMresourcesofmorethanonePNO.TheUser-to-userconnectionsthatarerelevanttotheXInterfacecanbeoftheVPtypeortheVCtypeEXAMPLE2:Figures2and3showexamplesofUser-to-userconnections.X-interfacetree:withrespecttoaparticularVPC,X-interfacerelationsexistbetweeneachProviderPNOandtheirConsumerPNO.BecauseeachProviderhasexactlyoneConsumer,theX-interfacerelationsbetweenallPNOsinvolvedinthemanagementofaparticularVPCformatree,theX-interfacerelationtreeNOTE12:Forthecascaded/mixedmodetherecanbeseveralpossibleX-interfacerelationtrees;theactualtreeisformedatVPCsetup.TherootofthetreeistheInitiatingPNO;ituses(viaX-interfacecontrols)thePNOs(oftenTransitPNOs),towhichitisconnectedinthetreeviaitsbranches.ThemostrightleafofthetreeistheZPNO.Figure2showsanexampleofanX-interfacetreeforthestarmodewiththeAPNObeingtheInitiator.TZTIFigure1:ExampleofaX-interfacetreewiththeInitiatingPNObeingtheAPNOZPNO:PNOwheretheInitiatorendsreservingtheend-to-endconnectionNOTE13:IftheterminationpointoftheconnectionisataUseraccesspoint,thisisconsideredtobetheZUserAccesspoint.Inthiscase,theIPNOviewstheZPNOasaPNOwhosesubnetisconnectedtotheZUser.SIST EN 300 820-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)13(NotethatforUser-to-userConnectionstheVPLinkconnectionsthatarepartofitarenotvisibleacrosstheX-Interface.TheLinkConnectionsthatterminatethe"networkside"ofanend-to-endConnectionarevisibleovertheX-Interface)EXAMPLE3:Thefollowingfigures2and3showexamplesofpossibleend-to-endconnections.SIST EN 300 820-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)14Figure2:ExamplesofFunctionalarchitecturesofVPCsprovidedbythreePNOsVPSC:VPSubNetworkConnectionVPLC:VPLinkConnection:ConnectionpointsUD:UserDomain(notvisibleacrosstheX-Interface):NotvisibleacrosstheX-Interface:VisibleacrosstheX-InterfaceVPUUC(VPSC)(VPSC)(VPSC)PNO#1VPSCVPSCVPSCVPLCVPLCPNO#2PNO#3UDUDVPUUC:VPUsertouserConnectionVPUNC(VPSC)(VPSC)(VPLC)PNO#1VPSCVPSCVPLCVPLCPNO#2PNO#3UDVPUNC:VPUsertonetworkConnectionVPNNC(VPLC)(VPSC)(VPLC)PNO#1VPSCVPLCVPLCPNO#2PNO#3VPNNC:VPNetworktonetworkConnectionSIST EN 300 820-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)15Figure3:ExamplesofFunctionalarchitecturesofaVCCprovidedbythreePNOs3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ASN.1AbstractSyntaxNotationOneATMAsynchronousTransferModeATMCPATMConnectivityProviderBMBusinessManagementCMIPCommonManagementInformationProtocolCMISECommonManagementInformationServiceElementCPConnectionPointCTPConnectionTerminationPointEMElementManagementGCLGenericClassesLibraryGDMOGuidelinesfortheDefinitionofManagedObjectsIPPLInterPNOPhysicalLinkMFManagementFunctionMSManagementServiceMSCManagementServiceComponentNENetworkElementNEFNetworkElementFunctionNGCNetworkGenericClassLibraryNMNetworkManagementNMCNetworkManagementCentreNMSNetworkManagementSystemOSOperationsSystemOSFOperationsSystemFunctionOSSOperationsSupportSystemPNOProvidingNetworkOperatorQoSQualityofServiceSMServiceManagementTPNOTransitPNOTMNTelecommunicationsManagementNetworkVCUUC(VCSC)(VCSC)(VCSC)PNO#1VCSCVCSCVCSCVPLCVPLCPNO#2PNO#3UDUDVCUUC:VCUsertouserConnectionVCSC:VCSubNetworkConnectionVPLC:VPLinkConnection:ConnectionpointsUD:UserDomain(notvisibleacrosstheX-Interface):NotvisibleacrosstheX-Interface:VisibleacrosstheX-InterfaceSIST EN 300 820-1 V1.2.1:2003

ETSIETSIEN300820-1V1.2.1(2000-11)16TPTerminationPointVCVirtualChannelVCCVirtualChannelConnectionVCUUCVirtualChannelUser-to-userConnectionVPVirtualPathVPCVirtualPathConnectionVPLCVirtualPathLinkConnectionVPNCVirtualPathNetworkConnectionVPN
...