ETSI EN 300 376-1 V1.2.1 (1999-10)
Telecommunications Management Network (TMN); Q3 interface at the Access Network (AN) for configuration management of V5 interfaces and associated user ports; Part 1: Q3 interface specification
Telecommunications Management Network (TMN); Q3 interface at the Access Network (AN) for configuration management of V5 interfaces and associated user ports; Part 1: Q3 interface specification
REN/TMN-02001-1
Telekomunikacijsko upravljavno omrežje (TMN) ) - Vmesnik Q3 dostopovnega omrežja (AN) za upravljanje konfiguracije vmesnikov V5 in pridruženih uporabniških priključkov - 1. del: Specifikacija vmesnika Q3
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.SRYQHJDHQLKTelecommunications Management Network (TMN); Q3 interface at the Access Network (AN) for configuration management of V5 interfaces and associated user ports; Part 1: Q3 interface specification33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 300 376-1 Version 1.2.1SIST EN 300 376-1 V1.2.1:2003en01-november-2003SIST EN 300 376-1 V1.2.1:2003SLOVENSKI
STANDARD
SIST EN 300 376-1 V1.2.1:2003
ETSI EN 300 376-1 V1.2.1 (1999-10)European Standard (Telecommunications series)Telecommunications Management Network (TMN);Q3 interface at the Access Network (AN)for configuration management of V5 interfacesand associated user ports;Part 1: Q3 interface specificationSIST EN 300 376-1 V1.2.1:2003
ETSIETSI EN 300 376-1 V1.2.1 (1999-10)2ReferenceREN/TMN-02001-1 (3hc90ioo.PDF)KeywordsTMN, information model, Q3 interface, AN, V5interface, configuration, managementETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frIndividual copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: editor@etsi.frCopyright 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 1999.All rights reserved.SIST EN 300 376-1 V1.2.1:2003
ETSIETSI EN 300 376-1 V1.2.1 (1999-10)3ContentsIntellectual Property Rights.6Foreword.6Introduction.61Scope.82References.83Definitions and abbreviations.93.1Definitions.93.2Abbreviations.104Information model diagrams.114.1Entity relationship diagram.114.1.1Overview.114.1.2V5 interface fragment.134.1.3Communication path fragment.134.1.4Protection fragment.154.2Inheritance hierarchy.164.3Naming hierarchy.165Information model description.175.1Managed object classes description.175.1.1V5 fragment.175.1.2Access fragment.185.1.2.1Managed element (managedElement).185.1.2.2User port TTP (userPortTtp).185.1.2.3ISDN Basic Access (BA) user port (isdnBAUserPort).185.1.2.4ISDN Primary Rate Access (PRA) user port (isdnPRAUserPort).195.1.2.5PSTN user port (pstnUserPort).195.1.2.6Leased port (leasedPort).195.1.2.7User port bearer channel CTP (userPortBearerChannelCtp).205.1.3Supporting managed object classes.205.2Attributes description.205.3Actions description.205.4Notifications description.206Formal managed object classes definition.206.1V5 fragment.216.2Access fragment.21SIST EN 300 376-1 V1.2.1:2003
ETSIETSI EN 300 376-1 V1.2.1 (1999-10)47Protocol requirements.22Annex A (normative):Mapping of V5 user port states on ITU-T Recommendation X.731states.23A.1Mapping of V5 PSTN user port states on ITU-T Recommendation X.731 states.23A.2Mapping of V5 ISDN basic access user port states on ITU-T Recommendation X.731 states.24A.3Mapping of V5 ISDN primary rate access user port states on ITU-T Recommendation X.731states.27Annex B (normative):Mapping of link control states on ITU-T Recommendation X.731states.30Annex C (normative):TMN management service "V5 related configuration at the AN".31C.1Task Information Base (TIB) A.31C.1.1Description.31C.1.2Components of service.31C.1.2.1General requirements.31C.1.2.1.1Association of user ports with V5 interfaces.31C.1.2.1.2Information flow across the Q3 interface.31C.1.2.1.3Compatibility between AN and LE.31C.1.2.1.4Configuration of bearer channels.31C.1.2.2V5 interface requirements.31C.1.2.2.1V5 interface and link IDs.31C.1.2.2.2Provisioning variant.32C.1.2.2.3Channel configuration.32C.1.2.2.4Association of interfaces with exchanges.32C.1.2.2.5Standby operation.32C.1.2.2.6Persistency checking.32C.1.2.2.7Global PSTN parameters.32C.1.2.3User port requirements.32C.1.2.3.1Operational threshold.32C.1.2.3.2Port blocking.32C.1.2.3.3User port addresses.32C.1.2.3.4Split ISDN ports.33C.1.2.3.5User requirements.33C.1.2.3.6ISDN with access digital sections.33C.1.2.3.7Port specific PSTN parameters.33C.2Management function list.33C.2.1User port functions.33C.2.1.1Insert a user port.33C.2.1.2Delete a user port.33C.2.1.3Modify a user port.33C.2.1.4Read a user port.34C.2.2V5 interface functions.34C.2.2.1Insert a V5 interface.34C.2.2.2Delete a V5 interface.34C.2.2.3Modify a V5 interface.34C.2.2.4Read a V5 interface.34C.2.3Cross-connection functions.34C.2.3.1Establish a connection.34C.2.3.2De-establish a connection.35C.2.3.3Modify a connection.35C.2.3.4Read a connection.35SIST EN 300 376-1 V1.2.1:2003
ETSIETSI EN 300 376-1 V1.2.1 (1999-10)5Annex D (informative):Functional architecture.36Annex E (informative):Link control message flows.40Annex F (informative):User port control message flows.41F.1Message flows for the mapping of PSTN user port states on ITU-T Recommendation X.731states.41F.1.1Blocking initiated by AN.41F.1.2Blocking request initiated by AN.41F.1.3Blocking initiated by LE.42F.1.4Co-ordinated unblocking initiated by the LE.42F.1.5Co-ordinated unblocking initiated by the AN.43F.2Message flows for the mapping of ISDN basic access user port states on ITU-TRecommendation X.731 states.43F.2.1Blocking initiated by AN.44F.2.2Blocking initiated by the LE.45F.2.3Co-ordinated unblocking initiated by the LE.46F.2.4Co-ordinated unblocking initiated by the AN.47F.3Message flows for the mapping of ISDN primary rate access user port states onITU-T Recommendation X.731 states.49F.3.1Blocking initiated by AN.50F.3.2Blocking initiated by the LE.50F.3.3Co-ordinated unblocking initiated by the LE.51F.3.4Co-ordinated unblocking initiated by the AN.51Annex G (normative):Location of the Q3 interface.53Annex H (normative):Summary of V5 requirement details.54Annex J (normative):Defaults and predefined items.55Bibliography.56History.58SIST EN 300 376-1 V1.2.1:2003
ETSIETSI EN 300 376-1 V1.2.1 (1999-10)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 from the ETSI Secretariat. Latest updates are available on the ETSI 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).The present document is part 1 of a multi-part European Standard (Telecommunications series) covering the Q3interface specification at the Access Network (AN) for configuration management of V5 interfaces and associated userports, as identified below:Part 1:"Q3 interface specification";Part 2:"Managed Object Conformance Statement (MOCS) proforma specification".National transposition datesDate of adoption of this EN:3 September 1999Date of latest announcement of this EN (doa):31 December 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):30 June 2000Date of withdrawal of any conflicting National Standard (dow):30 June 2000IntroductionV5 interfaces, as described in EN 300 324-1 [3] and EN 300 347-1[4], operate between an exchange and an AccessNetwork (AN) to support various narrowband services. These interfaces and their associated user ports have to bemanaged by the Operations Systems (OSs) within the Telecommunications Management Network (TMN).ITU-T Recommendation G.803 [1] provides an abstracted view of telecommunications equipment, based on theessential functions that such equipment needs to perform. These functional components are modelled by objects, whichrepresent the implementation-independent aspects of the equipment.The following assumptions relating to the scope of the present document were to be considered:-existing protocols should be used where possible, and the focus of the present document should be on definingthe object models;-the interface should not involve objects specific to the control of a leased line network which is not connected tothe LE or of an external line test system;SIST EN 300 376-1 V1.2.1:2003
ETSIETSI EN 300 376-1 V1.2.1 (1999-10)7-a model of the AN appears necessary. The model relevant to the present standards on the V5 interface and portswill be developed if it does not already exist elsewhere. Other object models outside the scope of the presentdocument may share the same physical Q3 interface;-the definition of OS functionality is outside the scope of the present document;-security management is excluded from the present document, but aspects of security relating to configurationmanagement are included;-configuration management includes provisioning and the provisioning activity may include testing, but thistesting is not included in the present document. It will be included in the specification relating to fault andperformance management;-the specification should cover the provisioning of national variants and type variants of lines. Existing modelling,such as the customer administration model, should be used for this, if possible;-the specification should not cover general functions within the AN, such as multiplexing, cross-connection andtransmission functions, unless some aspect impacts the configuration management of V5 interfaces and relatedports;-configuration management related to redundancy of V5 interfaces is within the scope of the present document,both for multiple V5 interfaces and for the individual links within a V5.2 interface;-the definition of an object model for a transparent channel on the V5 interface which supports thesynchronization of OSs is outside the scope of the present document;-it is assumed that the relationship between directory numbers and equipment is kept in the OSs of the AN, so thatthe Q3 interface of the AN does not need to handle directory numbers.SIST EN 300 376-1 V1.2.1:2003
ETSIETSI EN 300 376-1 V1.2.1 (1999-10)81ScopeThe present document specifies the Q3 interface between an Access Network (AN) and the TelecommunicationsManagement Network (TMN) for the support of configuration management functions for V5 interfaces, as described inEN 300 324-1 [3] and EN 300 347-1 [4], and their associated user ports. The management of transmission, media andservices which are not related to V5 interfaces is outside the scope of the present document.The Q3 interface is the TMN interface between network elements or Q-adapters which interface to Operations Systems(OSs) without mediation and between OSs and mediation devices. The location of the Q3 interface is illustrated inannex G.Generic modelling of leased line ports which are associated with a V5 interface is within the scope of the presentdocument, but the traffic from these ports can only be associated with 64 kbit/s bearer channels on the V5 interface.The definition of OS functionality, and the specification of Qx interfaces and proprietary interfaces are outside the scopeof the present document.The present document does not constrain the logical or physical size of the AN or its geographical dispersion. Thedefinition of the managed object class which represents an AN is outside the scope of the present document.Existing protocols are used where possible, and the focus of the present document is on defining the object models.NOTE:Configuration management includes provisioning and the provisioning activity may include testing, butthis testing is not included in the present document. It is included in the specification relating to fault andperformance management, EN 300 378-1 [6].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, the latest version applies.· A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]ITU-T Recommendation G.803 (1997): "Architecture of transport networks based on thesynchronous digital hierarchy (SDH)".[2]ETS 300 297: "Integrated Services Digital Network (ISDN); Access digital section for ISDN basicaccess".[3]EN 300 324-1: "V interfaces at the digital Local Exchange (LE); V5.1 interface for the support ofAccess Network (AN); Part 1: V5.1 interface specification".[4]EN 300 347-1: "V interfaces at the digital Local Exchange (LE); V5.2 interface for the support ofAccess Network (AN); Part 1: V5.2 interface specification".[5]EN 300 377-1: "Q3 interface at the Local Exchange (LE) for configuration management of V5interfaces and associated customer profiles; Part 1: Q3 interface specification".[6]EN 300 378-1: "Q3 interface at the Access Network (AN) for fault and performance managementof V5 interfaces and associated user ports; Part 1: Q3 interface specification".SIST EN 300 376-1 V1.2.1:2003
ETSIETSI EN 300 376-1 V1.2.1 (1999-10)9[7]EN 300 379-1: "Q3 interface at the Local Exchange (LE) for fault and performance management ofV5 interfaces and associated customer profiles; Part 1: Q3 interface specification".[8]ITU-T Recommendation G.773 (1993): "Protocol suites for Q-interfaces for management oftransmission systems".[9]ITU-T Recommendation G.784 (1994): "Synchronous Digital Hierarchy (SDH) management".[10]ITU-T Recommendation M.3010 (1996): "Principles for a telecommunications managementnetwork".[11]ITU-T Recommendation M.3100 (1995): "Generic network information model".[12]ITU-T Recommendation Q.811 (1997): "Lower layer protocol profiles for the Q3 and Xinterfaces".[13]ITU-T Recommendation Q.812 (1997): "Upper layer protocol profiles for the Q3 and Xinterfaces".[14]CCITT Recommendation X.208 (1988): "Specification of Abstract Syntax Notation One(ASN.1)".[15]Void.[16]ITU-T Recommendation X.721 | ISO/IEC 10165-2 (1992): "Information technology - Opensystems interconnection - Structure of management information: Definition of managementinformation".[17]ITU-T Recommendation X.731 | ISO/IEC 10164-2 (1992): "Information technology - Opensystems interconnection - Systems management: State management function".[18]Void.[19]ITU-T Recommendation Q.824.5 (1997): "Stage 2 and stage 3 description for the Q3 interface -Customer administration: Configuration management of V5 interface environments and associatedcustomer profiles".[20]ITU-T Recommendation G.960 (1993): "Access digital section for ISDN basic rate access".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following terms and definitions apply:Access Network (AN): see EN 300 324-1 [3].bearer channel: see EN 300 324-1 [3].Bearer Channel Connection (BCC): see EN 300 347-1 [4].Communication channel (C-channel): see EN 300 324-1 [3].Communication path (C-path): see EN 300 324-1 [3].control protocol: see EN 300 324-1 [3].D-channel signalling type (Ds-type) data: ISDN D-channel signalling type data with Service Access Point Identifier(SAPI) not equal to 16, and not equal to 32 to 62 (see EN 300 324-1 [3]).envelope function address: see EN 300 324-1 [3].SIST EN 300 376-1 V1.2.1:2003
ETSIETSI EN 300 376-1 V1.2.1 (1999-10)10frame type (f-type) data: ISDN D-channel data with SAPI in the range from 32 to 62 (see EN 300 324-1 [3]).Local Exchange (LE): see EN 300 324-1 [3].Operations System (OS): see ITU-T Recommendation M.3010 [10].packet type (p-type) data: ISDN D-channel data with SAPI equal to 16 (see EN 300 324-1 [3]).Permanent Line (PL): see EN 300 324-1 [3].protection protocol: see EN 300 347-1 [4].provisioning variant: see EN 300 324-1 [3].semi-permanent leased line: see EN 300 324-1 [3].time slot number: see EN 300 324-1 [3].V5 interface: see EN 300 324-1 [3].V5 time slot: object class representing a 64 kbit/s channel of a V5 interface that is used as bearer or communicationchannel. It is a subclass of "ITU-T Recommendation M.3100 [11]":connectionTerminationPointBidirectional.V5 Trail Termination Point (TTP): object class representing a 2 Mbit/s interface that is used as V5.1 interface or aspart of a V5.2 interface. It is a subclass of "ITU-T Recommendation M.3100 [11]": trailTerminationPointBidirectional.X interface: see ITU-T Recommendation M.3010 [10].3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:ANAccess NetworkASN.1Abstract Syntax Notation One (see CCITT Recommendation X.208 [14])BABasic AccessBCCBearer Channel ConnectionC-channelCommunication channelC-pathCommunication pathCTPConnection Termination PointDCCData Communications ChannelDs-typeD-channel signalling typef-typeframe typeFSMFinite State MachineIDIdentity, IdentifierISDNIntegrated Services Digital NetworkLELocal ExchangeM/OMandatory/OptionalMPHprimitive between Physical layer and layer 2 ManagementNENetwork ElementOSOperations Systemp-typepacket typePLPermanent LinePRAPrimary Rate AccessPSTNPublic Switched Telephone NetworkRDNRelative Distinguished NameSAPIService Access Point IdentifierTIBTask Information BaseTMNTelecommunications Management
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.