SIST EN 300 376-1 V1.2.1:2003

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

To align the published I-ETS with the corresponding ITU-T Recommendation.

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

• 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 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

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
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.: [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.orgIf you find errors in the present document, send yourcomment to: [e-mail] 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 NetworkTTPTrail Termination PointSIST EN 300 376-1 V1.2.1:2003

ETSIETSI EN 300 376-1 V1.2.1 (1999-10)114Information model diagramsThe entity relationship diagram is given in subclause 4.1 and the inheritance hierarchy (is a relationships) and naminghierarchy (containment relationships) are given in subclauses 4.2 and 4.3, respectively.4.1Entity relationship diagramFigures 1 to 4 show the overall relationships between the various entities. These correspond to the managed objectswhich are manipulated at the Q3 interface.For V5.1 interfaces, bearer channels on user ports are associated with bearer time slots on a V5.1 interface byconfiguration over the Q3 interface of the AN. For V5.2, bearer channels on user ports are associated with bearer timeslots on a V5.2 interface by the V5.2 Bearer Channel Connection (BCC) protocol. For both V5.1 and V5.2, theassociation of user signalling with communication paths and the association between communication paths and logicalcommunication channels on the V5 interface is by configuration over the Q3 interface of the AN. The association oflogical communication channels with physical communication time slots on the V5 interface is initially established overthe Q3 interface, but can be changed for V5.2 interfaces by the V5.2 protection protocol.The AN treats time slots on the V5.2 interface which are used for semi-permanent connections like any other bearer timeslot on a V5.2 interface.Signalling protocols and their associated communication are modelled using various objects which represent thecommunication paths and the communication time slots. There are six classes of communication path objects. There is asingle class for all Integrated Services Digital Network (ISDN) signalling with an attribute to distinguish betweenDs-type, p-type, and f-type data. There are classes for Public Switched Telephone Network (PSTN) signalling, thecontrol protocol, the BCC protocol, link control protocol, and the protection protocol. In addition to these sixcommunication path object classes, there is also an object class which represents communication channels.There is one instance of the appropriate object class per communication path and per communication channel. These arecontained in instances of v5Interface.V5 control messages relating to provisioning are managed by an optional object on the Q3 interface. These messagesmay not be required once a TMN X interface or an integrated OS is available.If control messages relating to provisioning are not supported on the Q3 interface then a default value for provisioningvariant will be automatically used on the V5 interface. All V5 interfaces will use this default value unless activelychanged via the Q3 interface. The value of this default is all zeroes.Protection group 1 and its contained protection unit(s) are to be instantiated for the V5.2 case only if there is more thanone 2,048 Mbit/s link.A Trail Termination Point (TTP) contains the Connection Termination Points (CTPs) at the higher network layer whichit serves. This relationship allows the entity relationship diagram to mapped onto the functional architecture (seeannex D).4.1.1OverviewA single managedElement can contain a number of userPortTtps, a number of v5Interfaces, and a number of v5Ttps(which each represent a 2,048 Mbit/s link). There is a bi-directional association between each v5Interface and all of itsrelated userPorts. Likewise there is a bi-directional relationship between each v5Interface and all of its related v5Ttps(2,048 Mbit/s links).Each userPortTtp can contain a number of userPortBearerChannelCtps, one for each of its 64 kbit/s bearer channels.Each v5Ttp contains 31 v5TimeSlots which represent the CTPs corresponding to each of the 31 physical time slotswhich may be configured. Each userPortBearerChannelCtp can be associated with a unique v5TimeSlot for a V5.1interface, but for the V5.2 case there is no corresponding association because the relationship is controlled by the V5.2BCC protocol.SIST EN 300 376-1 V1.2.1:2003

ETSIETSI EN 300 376-1 V1.2.1 (1999-10)12 a1nnccontains1a31nc11n1 a ac0,10,11commChannelnuserPortTtpc a1n1mncc1n1ncn aonly V5.11a1is associated with (reciprocal relation) ais associated with (unidirectional) a a1ac0,1,210,111cv5Ttpv5TimeSlotuserPortBearerChannelCtp11managedElement"M.3100":"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":v5InterfacefragmentfragmentcommPathv5Protectionfragment(only V5.2)Figure 1: Entity relationship diagram - overviewLink blocking requests on the Link control protocol are generated by setting the administrative state attribute of therelevant instance of v5Ttp to shutting down. Only deferred blocking requests can be generated in this way. Deferredblocking requests on the Link control protocol cannot be generated by manipulating the object model. Port blockingrequests for the Control protocol are generated by setting the administrative state attribute of the relevant instance of thesubclass of userPortTtp to shutting down.SIST EN 300 376-1 V1.2.1:2003

ETSIETSI EN 300 376-1 V1.2.1 (1999-10)134.1.2V5 interface fragmentEach v5Interface contains a number of communication path objects in its commPath fragment, a number ofcommChannels, and one or two v5ProtectionGroup objects if it represents a V5.2 interface. Each instance of v5Interfacemay contain an instance of v5Provision to support the V5 pre-provisioning messages.n1c an1 an1v5Ttpnv5Provision0,1commChannelv5Interfaceccontainsis associated with a0,1,2userPortTtpV5 interfacefragment"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":commPathfragmentv5Protectionfragment(only V5.2)Figure 2: Entity relationship diagram - V5 interface fragment4.1.3Communication path fragmentEach ISDN userPortTtp can be associated with up to three isdnCommPaths, one for each type of ISDN signalling. EachisdnCommPath handles a certain type of ISDN signalling for a number of userPortTtps, and is associated with these.There may be more than one isdnCommPath contained in the v5Interface for each type of ISDN signalling.The v5Interface contains a single controlCommPath. It contains a single pstnCommPath, but only if there are any PSTNuserPortTtps associated with it. It also contains a single bccCommPath, a single protCommPath, and a singlelinkControlCommPath if it represents a V5.2 interface.Each commChannel can be associated with up to three isdnCommPaths representing three different types of ISDNsignalling. It can also be associated with the pstnCommPath. The commChannel which is associated withcontrolCommPath shall also be associated with the bccCommPath and with the linkControlCommPath if the v5Interfacewhich contains it represents a V5.2 interface.SIST EN 300 376-1 V1.2.1:2003

ETSIETSI EN 300 376-1 V1.2.1 (1999-10)14 an1Basic access,Primary rate access a10,1,2,3 a10,1,2,3userPortTtpisdnCommPathpstnCommPathEach one instance for:- Ds-type data- p-type data- f-type data0,10,11 a1is associated with (reciprocal relation) ais associated with (unidirectional) acontrolCommPath0,10,1commPath
i
iis acommChannellinkControlCommPath(only V5.2)protCommPath(only V5.2)communication path fragmentbccCommPath(only V5.2)v5Protectionfragment(only V5.2)"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":Figure 3: Entity relationship diagram - communication path fragmentSIST EN 300 376-1 V1.2.1:2003

ETSIETSI EN 300 376-1 V1.2.1 (1999-10)154.1.4Protection fragmentThere is a bi-directional one-to-one association between commChannels and certain v5TimeSlots. Not every v5TimeSlotis associated with a commChannel. Some are used for bearer traffic and others are available for protection ofcommChannels on V5.2 interfaces. This protection adds onto the modelling for the V5.1 interfaces, and does not affectthat modelling.The time slots which may be associated with the commChannel which is associated with the controlCommPath areconstrained by the V5 interface specifications EN 300 324-1 [3] and EN 300 347-1 [4]. A v5Interface which representsa V5.2 interface shall contain a v5ProtectionGroup of type 1 which contains two v5ProtectionUnits (see figure 4). Oneof these v5ProtectionUnits points to the protected commChannel which is associated with both the controlCommPath,the bccCommPath, and the linkControlCommPath. The corresponding pointer in the other v5ProtectionUnit is null. Bothv5ProtectionUnits point to their associated v5TimeSlots. The containing v5ProtectionGroup of type 1 is pointed to bythe protCommPath for the v5Interface, so there is an indirect mapping from the protCommPath through thev5ProtectionGroup of type 1, through its two contained v5ProtectionUnits onto its related v5TimeSlots. accontainsis associated with (reciprocal relation) ais associated with (unidirectional) aprotCommPath1 c av5ProtectionUnitv5ProtectionGroup110,1,211v5TimeSlotcomm a10,110,1v5Interface c1nprotectionfragment aonly protectiongroup 1(protection group 1: n=2)Channel"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":Figure 4: Entity relationship diagram - protection fragmentA v5Interface which represents a V5.2 interface also contains a v5ProtectionGroup of type 2 if other commChannels areprotected (see figure 4). The v5ProtectionGroup of type 2 contains a number of v5ProtectionUnits, each of which pointsto its associated v5TimeSlot. The v5ProtectionUnits which point to active v5TimeSlots also point to the commChannelswhich are associated with the active v5TimeSlots. The corresponding pointers in the other v5ProtectionUnits are set tonull.SIST EN 300 376-1 V1.2.1:2003

ETSIETSI EN 300 376-1 V1.2.1 (1999-10)164.2Inheritance hierarchyFigure 5 traces the inheritance from the highest level object "ITU-T Recommendation X.721 [16]":top to the managedobjects defined in the present document.M.3100":"M.3100":connection-connection-"Q.824.5":userPort-Termination-Termination-BearerChannelCtpPointSourcePoint-(note)Bidirectional(note)"M.3100":"X.721":"M.3100":connection-topterminationPointTermination-(note)(note)PointSink(note)"M.3100":managedElement"M.3100":"M.3100":trail-trail-"Q.824.5":"Q.824.5":Termination-Termination-userPortTtpisdnBAUserPortPointSourcePoint-(note)(note)Bidirectional"Q.824.5":(note)isdnPRAUserPort"M.3100":trail-"Q.824.5":Termination-pstnUserPortPointSink(note)"Q.824.5":leasedPortNOTE:Non-instantiable object class.Figure 5: Inheritance hierarchy4.3Naming hierarchyFigure 6 shows the naming (i.e. containment) relationships for the AN's managed objects associated with configurationmanagement."M.3100":managedElement"Q.824.5":"Q.824.5":"Q.824.5":v5Ttpv5InterfaceuserPortTtp"Q.824.5":userPortBearerChannelCtp"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":"Q.824.5":v5TimeSlotcommChannelv5ProvisioncommPathv5ProtectionGroup"Q.824.5":v5ProtectionUnitFigure 6: Naming hierarchySIST EN 300 376-1 V1.2.1:2003

ETSIETSI EN 300 376-1 V1.2.1 (1999-10)175Information model descriptionThis clause provides a high-level informal description of the management information model for configurationmanagement of the AN.The principle managed objects for configuration management are logical constructs and do not represent physicalequipment. The relationship between these managed objects and equipment is achieved by using thesupportedByObjectList pointer in the logical managed objects to point to the equipment which supports them, and byusing the affectedObjectList pointer on equipment to point to the logical managed objects that the equipmentimplements.Subclause 5.1 contains a brief description for each object class used in the model covering:-the purpose of the object class;-the attributes defined for the object class;-the relationship of the object class to other object classes.In the tables listing the attributes of the object classes, the inherited attributes are only mentioned explicitly if theirconditionality has been altered. The other inherited attributes are still present in these classes.Subclause 5.2 describes attributes which are common to several object classes in the information model.Subclause 5.3 describes actions which are common to several object classes in the information model.Subclause 5.4 describes the common aspects of the notifications used in the information model.5.1Managed object classes descriptionSubclause 5.1 is divided into further subclauses which describe the fragments of the information model.5.1.1V5 fragmentThe object classes of the V5 fragment are described in ITU-T Recommendation Q.824.5 [19]. The following classes areused in the AN:-V5 interface (v5Interface);-V5 TTP (v5Ttp);-V5 time slot (v5TimeSlot);-V5 provision (v5Provision);-V5 communication channel (commChannel);-ISDN communication path (isdnCommPath);-PSTN communication path (pstnCommPath);-BCC communication path (bccCommPath);-control communication path (controlCommPath);-protection communication path (protCommPath);-link Control communication path (linkControlCommPath);-V5 protection group (v5ProtectionGroup);-V5 protection unit (v5ProtectionUnit).SIST EN 300 376-1 V1.2.1:2003

ETSIETSI EN 300 376-1 V1.2.1 (1999-10)185.1.2Access fragmentThe following classes are specific to the AN.5.1.2.1Managed element (managedElement)The managed element object class is defined in ITU-T Recommendation M.3100 [11].5.1.2.2User port TTP (userPortTtp)A user port TTP is an object class representing a generic user port on an AN. It is a specialization of the TTPbidirectional object class defined in ITU-T Recommendation M.3100 [11].This managed object class is defined in ITU-T Recommendation Q.824.5 [19].In addition to the inherited attributes, it has the attributes given in table 1.Table 1NameM/C/OValue set"ITU-T Recommendation M.3100 [11]":tTPIdMRDN"ITU-T Recommendation X.721 [16]":administrativeStateMsingle"ITU-T Recommendation Q.824.5 [19]":assocV5InterfaceCsingle"ITU-T Recommendation Q.824.5 [19]":blockingStatusCsingle5.1.2.3ISDN Basic Access (BA) user port (isdnBAUserPort)An ISDN BA user port is an object class representing an ISDN basic user port which is associated with a V5 interfaceon an AN. It is a specialization of the user port TTP object class.This managed object class is defined in ITU-T Recommendation Q.824.5 [19].In addition to the inherited attributes, it has the attributes given in table 2.Table 2NameM/C/OValue set"ITU-T Recommendation Q.824.5[19]":assocIsdnSignallingCommPathMsingle"ITU-T Recommendation Q.824.5 [19]":assocPacketCommPathMsingle"ITU-T Recommendation Q.824.5 [19]":assocFrameCommPathMsingle"ITU-T Recommendation Q.824.5 [19]":envelopeFunctionAddressMsingle"ITU-T Recommendation Q.824.5 [19]":accessDigitalSectionMsingle"ITU-T Recommendation Q.824.5 [19]":gradingEnabledCsingleNOTE 1:accessDigitalSection: indicates whether the NT1 is implemented separately from the AN.NOTE 2:gradingEnabled: indicates for a port with an access digital section whether the grading messages shouldbe sent to the LE.SIST EN 300 376-1 V1.2.1:2003

ETSIETSI EN 300 376-1 V1.2.1 (1999-10)195.1.2.4ISDN Primary Rate Access (PRA) user port (isdnP
...