ETSI EN 301 271 V1.1.1 (1998-11)

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

DEN/TMN-00004

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

General Information

• Status: Published
• Publication Date: 25-Nov-1998
• Technical Committee: TMN - Telecommunications Management Network
• Current Stage: 12 - Completion
• Due Date: 13-Nov-1998
• Completion Date: 26-Nov-1998
• Ref Project: SIST EN 301 271 V1.1.1:2003 - Telecommunications Management Network (TMN); Management interfaces associated with the VB5.1 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.1 reference point;33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 271 Version 1.1.1SIST EN 301 271 V1.1.1:2003en01-november-2003SIST EN 301 271 V1.1.1:2003SLOVENSKI
STANDARD



SIST EN 301 271 V1.1.1:2003



EN 301 271 V1.1.1 (1998-11)European Standard (Telecommunications series)Telecommunications Management Network (TMN);Management interfaces associatedwith the VB5.1 reference pointSIST EN 301 271 V1.1.1:2003



ETSIEN 301 271 V1.1.1 (1998-11)2ReferenceDEN/TMN-00004 (bro00ico.PDF)KeywordsTMN, Q3 interface, ATM, configuration,management, performance, V5 interface, OAMETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: [phone]
Fax: [phone]Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/[e-mail] copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1998.All rights reserved.SIST EN 301 271 V1.1.1:2003



ETSIEN 301 271 V1.1.1 (1998-11)3ContentsIntellectual Property Rights.6Foreword.61Scope.72References.73Definitions, abbreviations, and conventions.83.1Definitions.83.2Abbreviations.83.3Conventions.94General Overview.94.1Entity-Relationship Models.104.1.1Entity relationship diagram for the service node.114.1.2Entity relationship diagram for the access network.124.1.3Entity relationship diagram for circuit emulation.134.2Inheritance Hierarchy.145Formal Definitions.155.1Object classes.155.1.1ATM Generic Fragment.165.1.1.1ATM fabric (atmFabric).165.1.1.2TC adapter TTP bi-directional (tcAdaptorTTPBidirectional).165.1.2VB5 specific fragment.165.1.2.1Communications path for broadband (commPathBb).165.1.2.2Logical service port (logicalServicePort).175.1.2.3Logical service port for VB5.1(lspVb51).175.1.2.4Logical service port for VB5.1 in the access network (lspVb51An).185.1.2.5 Logical service port for VB5.1 in the service node (lspVb51Sn).185.1.2.6Logical User Port (logicalUserPort).185.1.2.7RTMC communications path for broadband (rtmcCommPathBb).185.1.2.8TC adaptor TTP extension (tcAdaptorTtpExtension).195.1.2.9UNI access VB5 (uniAccessVb5).195.1.2.10VPC at Logical User Port (vpcLup).195.1.2.11VP CTP bi-directional VB5 (vpCtpBidirectionalVb5).205.1.2.12VP TTP bi-directional VB5 (vpTtpBidirectionalVb5).205.2Name bindings.205.2.1commPathBb-logicalServicePort.205.2.2logicalServicePort-managedElementR1.205.2.3logicalUserPort-managedElementR1.205.2.4tcAdaptorTtpExtension-tcAdaptorTTPBidirectional.215.2.5vpcLup-uniAccessVb5.215.2.6vcCTPBidirectional-managedElementR1.215.3Definition of packages.215.3.1Automatic VPCI consistency check package (automaticVpciConsistencyCheckPkg).215.3.2Check logical service port identification package (checkLspIdentificationPkg).215.3.3Check VPCI consistency package (checkVpciConsistencyPkg).215.3.4Partial administrative state package (partialAdministrativeStatePkg).225.3.5Remote blocking VB5 package (remoteBlockingVb5Pkg).225.3.6Reset package (resetPkg).225.3.7Start-up logical service port package (startupLspPkg).225.3.8VP CTP and VPCI pointer list package (vpCtpAndVpciPtrListPkg).225.4Definition of attributes.225.4.1Communications path for broadband identifier (commPathBbId).225.4.2Logical service port activation state (lspActivationState).235.4.3Logical service port identifier (logicalServicePortId).235.4.4Logical service port number (logicalServicePortNumber).23SIST EN 301 271 V1.1.1:2003



ETSIEN 301 271 V1.1.1 (1998-11)45.4.5Logical service port pointer (logicalServicePortPtr).235.4.6Logical user port identifier (logicalUserPortId).235.4.7Logical user port number (logicalUserPortNumber).245.4.8Partial administrative state (partialAdministrativeState).245.4.9Remote blocking reason VB5 (remoteBlockingReasonVb5).245.4.10Remote blocking VB5 (remoteBlockingVb5).245.4.11TC adaptor extension identifier (tcAdaptorExtensionId).245.4.12VPC at logical user port identifier (vpcLupId).255.4.13VPC at logical user port number (vpcLupNumber).255.4.14VP CTP and VPCI pointer list (vpCtpAndVpciPtrList).255.4.15VP TTP and VPCI pointer list (vpTtpAndVpciPtrList).255.5Definition of actions.255.5.1Reset (reset).255.5.2Start-up logical service port (startupLsp).265.5.3Check VPCI consistency (checkVpciConsistency).265.5.4Check logical service port identification (checkLspIdentification).265.6Definition of notifications.265.6.1Automatic VPCI consistency check initiated (automaticVpciConsistencyCheckInitiated).265.6.2Automatic VPCI consistency check result (automaticVpciConsistencyCheckResult).275.6.3Reset result (resetResult).275.7Definition of parameters.275.7.1Cause value (causeValue).276Type Definitions.277Protocol stacks.29Annex A (normative):Management Requirements.30A.1General management requirements.30A.1.1General configuration management requirements.30A.1.2ATM transport layer configuration requirements.30A.1.2.1Configuration of OAM cells.30A.2Real time management co-ordination requirements.30A.2.1Configuration management requirements.30A.2.1.1General configuration management requirement.30A.2.1.2Common configuration management requirement for AN and SN.30A.2.1.2.1Shutting-down of VPs.30A.2.1.2.2VB5 interface ID checking.30A.2.1.2.3Handling of VB5 primitives.30A.2.1.2.4Co-ordination of VP and VC resources.31A.2.1.2.5Non B-ISDN accesses.31A.2.1.3Configuration management requirement for AN.31A.2.1.4Configuration management requirement for SN.31A.2.1.4.1Assignment of indirect accesses.31A.2.1.4.2Co-ordination of indirect accesses with logical user ports.31A.2.1.4.3Consistency of configuration.31A.2.2Fault management requirements.31A.2.2.1Alarm surveillance requirements.31A.2.2.1.1General alarm surveillance requirements.31A.2.2.1.1.1Co-ordination of operational states.31A.2.2.2Test and fault localization requirements.31A.2.2.2.1General test and fault localization requirements.31A.2.2.2.1.1Test traffic.31A.3Non real time management requirements.32A.3.1General configuration requirements.32A.3.1.1Co-ordinated VP and VC configuration.32A.3.1.1.1VPC checking.32A.3.1.1.2Co-ordination of port configuration data.32A.3.1.1.3Co-ordination of VPCI values.32SIST EN 301 271 V1.1.1:2003



ETSIEN 301 271 V1.1.1 (1998-11)5A.3.1.1.4Consistency of configuration.32A.3.1.2Common configuration management requirement for AN and SN.32A.3.1.3Configuration management requirement for AN.32A.3.1.4Configuration management requirement for SN.32A.3.1.4.1Co-ordinated VC Switch-over.32Annex B (normative):Functional architecture.33B.1Functional architecture associated with VB5 reference point.33Annex C (normative):Relationship between VB5.1 interfaces and the management model.35C.1Introduction.35C.2LSP, LUP and VPCI labels.36C.3Shutting down.36C.4Blocking and unblocking.36C.5VPCI consistency checking.37C.6Start-up.37C.6.1Activation by OS.38C.6.2Automatic start-up.39C.7LSP identity checking.40C.8Reset.40Annex D (informative):Instantiation Examples.42D.1Conventions.42D.2VP cross connection.42D.2.1VP cross connection in the service node.43D.2.2VP cross connection in the access network.44D.3VC cross connection.45D.3.1VC cross connection in the service node.46D.3.2VC cross connection in the access network.47Bibliography.48History.50SIST EN 301 271 V1.1.1:2003



ETSIEN 301 271 V1.1.1 (1998-11)6Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical CommitteeTelecommunications Management Network (TMN).National transposition datesDate of adoption of this EN:6 November 1998Date of latest announcement of this EN (doa):28 February 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 August 1999Date of withdrawal of any conflicting National Standard (dow):31 August 1999SIST EN 301 271 V1.1.1:2003



ETSIEN 301 271 V1.1.1 (1998-11)71ScopeThe present document specifies the management interfaces (Q3 interfaces and X interfaces) associated with the VB5.1reference point [1], [2] and EN 301 217-1 [18] for the support of configuration, fault & performance managementfunctions, including a management interface for co-ordinated management between the access networks and the servicenode (the X interface). Fault and performance management together include both passive monitoring of reports andactive fault isolation.The Q3 interface [5] is the TMN interface between network elements or Q-adapters which interface to OSs withoutmediation and between OSs and mediation devices. The X-interface [5] is the TMN interface between OSs.Existing protocols are used where possible, and the focus of the work is on defining the object model. The definition ofthe functionality of TMN Operations Systems is outside the scope of the present document.Q.2931 is supported at the UNI, and the ATM Forum UNI is supported for compatibility with the established base ofATM equipment.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.· References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.· For a specific reference, subsequent revisions do not apply.· For a non-specific reference, subsequent revisions do apply.· A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]ETR 257: "V interfaces at the digital Service Node (SN); Identification of the applicability ofexisting protocol specifications for a VB5 reference point in an access arrangement with AccessNetworks (ANs)".[2]EN 301 005-1: "V interfaces at the digital Service Node (SN); Interfaces at VB5.1 reference pointfor the support of broadband or combined narrowband and broadband Access Networks (ANs);Part 1: Interface specification".[3]ITU-T Recommendation G.851.01 (1996): "Management of the transport network – Application ofthe RM-ODP framework".[4]ITU-T Recommendation G.902: "Framework Recommendation on functional access networks -Architecture and functions, access types, management and service node aspects."[5]ITU-T Recommendation M.3010: "Principles for a Telecommunications Management Network".[6]ITU-T Recommendation M.3100(7/95): "Generic Network Information Model".[7]ITU-T Recommendation Q.82bcm (Draft new): "Broadband configuration management."[8]ITU-T Recommendation X.721 | ISO/IEC 10165-2 (1992): "Information technology - Opensystems interconnection - Structure of management information: Definition of managementinformation".[9]ITU-T Recommendation X.731 | ISO/IEC 10164-2 (1992): "Information technology - Opensystems interconnection - Systems management: State management function".[10]ITU-T Recommendation I.751: "Asynchronous Transfer Mode (ATM) Management of theNetwork Element View".SIST EN 301 271 V1.1.1:2003



ETSIEN 301 271 V1.1.1 (1998-11)8[11]ITU-T Recommendation X.721 | ISO/IEC 10165-2 (1992): "Information technology - Opensystems interconnection - Structure of management information: Definition of managementinformation".[12]ITU-T Recommendation Q.2931: "Digital Subscriber Signalling System No. 2 – User-NetworkInterface (UNI) layer 3 specification for basic call/connection control".[13]EN 301 064-1: "Telecommunications Management Network (TMN); Information models andprotocols for the management and control of the Asynchronous Transfer Mode (ATM) switchingnetwork element; Part 1: Q3 interface specification".[14]ITU-T Recommendation Q.811: "Lower layer protocol profiles for the Q3 and X interfaces".[15]ITU-T Recommendation Q.812: "Upper layer protocol profiles for the Q3 and X interfaces".[16]ITU-T Recommendation G.773: "Protocol suites for Q-interfaces for management of transmissionsystems".[17]ITU-T Recommendation G.784: "Synchronous digital hierarchy (SDH) management".[18]EN 301 217-1: "V interfaces at the digital Service Node (SN); Interfaces at the VB5.2 referencepoint for the support of broadband or combined narrowband and broadband Access Networks;Part 1: Interface specification".3Definitions, abbreviations, and conventions3.1DefinitionsFor the purposes of the present document, the terms and definitions given in ITU-T Recommendation G.902 [4],EN 301 005-1 [2], ITU-T Recommendation I.751 [10] and the following apply.resources: the management of user port functions and service port functions providing UNI and SNI functionality,respectively, are considered in the present document based on the framework defined in ITU-T RecommendationG.902 [4]. Transmission specific resources lie outside its scope.3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply.AALATM Adaptation LayerAISAlarm Indication SignalANAccess NetworkASN.1Abstract Syntax Notation oneATMAsynchronous Transfer ModeB-BCCBroadband Bearer Connection ControlCTPConnection Termination PointERDEntity Relationship DiagramGDMOGuidelines for the Definition of Managed ObjectsLSPLogical Service PortLUPLogical User PortMCFMessage Communication FunctionMIBManagement Information BaseMOCManaged Object ClassNNINetwork Network InterfaceOAMOperations, Administration, and MaintenanceOLTOptical Line TerminalONUOptical Network UnitOSOperation SystemSIST EN 301 271 V1.1.1:2003



ETSIEN 301 271 V1.1.1 (1998-11)9PONPassive Optical NetworkPSPPhysical Service PortPUPPhysical User PortRDIRemote Defect IndicationRDNRelative Distinguished NameRTMCReal Time Management Co-ordinationSDHSynchronous Digital HierarchySNService NodeSNIService Node InterfaceTMNTelecommunications Management NetworkTTPTrail Termination PointUNIUser-Network InterfaceVCVirtual ChannelVDSLVery high speed Digital Subscriber LineVPVirtual PathVPCVirtual Path ConnectionVPCIVirtual Path Connection Identifier3.3ConventionsObjects and their characteristics and associated ASN.1 defined here are given names with capitals used to indicate thestart of the next word and acronyms are treated as if they were words.Throughout the present document, all new attributes are named according to the following guidelines:· The name of an attribute ends in the string "Ptr" if and only the attribute value is intended to identify a singleobject.· The name of an attribute ends in the string "PtrList" if and only the attribute value is intended to identify one ormore objects.· The name of an attribute is composed of the name of an object class followed by the string "Ptr" if and only theattribute value is intended to identify a specific object class.· If an attribute is intended to identify different object classes, a descriptive name is given to that attribute and adescription is provided in the attribute behaviour.· The name of an attribute ends in the string "Id" if and only the attribute value is intended to identify the name ofan object, in which case this attribute should be the first one listed, should use ASN.1 NameType and should notbe used to convey other information.· The name of an attribute is composed of the name of an objec
...