SIST ETS 300 376-2:1997

• Abstract:

  MOCS proforma for the Q3 AN configuration management specification.

• Status: Published
• Publication Date: 31-Oct-1997
• ICS: 33.040.30 - Switching and signalling systems
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Nov-1997
• Due Date: 01-Nov-1997
• Completion Date: 01-Nov-1997
• Ref Project: ETSI ETS 300 376-2 ed.1 (1995-11) - Q3 interface at the Access Network (AN) for configuration management of V5 interfaces and associated user ports; Part 2: Managed Object Conformance Statement (MOCS) proforma specification

Overview

SIST ETS 300 376-2:1997 specifies the Managed Object Conformance Statement (MOCS) proforma for the Q3 interface at the Access Network (AN) for configuration management of V5 interfaces and associated user ports. Developed by the Slovenski inštitut za standardizacijo (SIST) and aligned with the European Telecommunications Standards Institute (ETSI), this standard supports the Telecommunication Management Network (TMN) by ensuring conformance and interoperability of equipment through clear declarations of support for specific managed object classes.

The MOCS proforma enables manufacturers and suppliers to formally state compliance with the base information model defined in ETS 300 376-1, helping telecommunication providers evaluate solutions for managing V5 interfaces in access network environments.

Key Topics

• Q3 Interface for Access Network: The Q3 interface plays a crucial role in configuration management between the access network (AN) and local exchanges, focusing on V5 interfaces and user ports.
• Managed Object Conformance Statement (MOCS): The proforma serves as a checklist for identifying support of mandatory, conditional, and optional elements of the information model as specified in the base standard.
• Managed Object Classes: Includes conformance specifications for multiple managed object classes such as v5Interface, v5Ttp (termination points), user ports, communication paths, and protection groups.
• Conformance Assessment: The structure enables suppliers to demonstrate compliance with the model by indicating support for specific attributes, actions, notifications, and packages required for configuration management.
• Standardized Notation: Adopts common status symbols (mandatory, conditional, optional, not applicable) defined in ISO/IEC 9646-7 to provide a consistent approach for implementation declarations.

Applications

SIST ETS 300 376-2:1997 is widely used in the following practical applications:

• Supplier Conformance Reporting: Equipment vendors use the MOCS proforma to declare product compliance with V5 interface configuration management requirements, facilitating certification and procurement processes.
• Network Element Interoperability: By standardizing configuration management support, this standard promotes seamless interaction between access networks and local exchanges within multi-vendor environments.
• Telecommunications Network Management: Network operators rely on MOCS-compliant equipment to streamline integration, automate configuration management, and support fault and performance management extensions per related standards.
• Regulatory and Quality Assurance: Adhering to this standard supports regulatory compliance and helps network providers verify the functional completeness of implemented management solutions for V5 interfaces.

Related Standards

Several other standards are integral to implementing robust Q3 interface and V5 configuration management solutions:

• ETS 300 376-1: Defines the base specification for the Q3 interface at the Access Network for configuration management of V5 interfaces and associated user ports.
• ETS 300 377: Covers the Q3 interface at the Local Exchange for configuration management of V5 interfaces and associated customer profiles.
• ETS 300 378: Focuses on fault and performance management over Q3 interfaces at the Access Network.
• ETS 300 379: Details fault and performance management of V5 interfaces at the Local Exchange.
• ISO/IEC 9646-7: Provides general conformance testing methodology and framework, including definitions of evaluation criteria used in MOCS proformas.

---

Keywords: Q3 interface, Access Network, V5 interface, Managed Object Conformance Statement, MOCS, configuration management, telecommunication management network, ETSI, switching and signalling systems, managed object class, conformity, network management standards.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Signalling Protocols and Switching (SPS) - Q3 interface at the Access Network (AN) for configuration management of V5 interfaces and associated user ports; Part 2: Managed Object Conformance Statement (MOCS) proforma specification33.040.30Komutacijski in signalizacijski sistemSwitching and signalling systemsICS:Ta slovenski standard je istoveten z:ETS 300 376-2 Edition 1SIST ETS 300 376-2:1997en01-november-1997SIST ETS 300 376-2:1997SLOVENSKI
STANDARD
EUROPEANETS 300 376-2TELECOMMUNICATIONNovember 1995STANDARDSource: ETSI TC-SPSReference: DE/SPS-03013.3ICS:35.100.70Key words:TMN, information model, Q3 interface, AN, V5 interface, configuration, management, MOCSSignalling Protocols and Switching (SPS);Q3 interface at the Access Network (AN)for configuration management of V5 interfaces andassociated user ports;Part 2: Managed Object Conformance Statement (MOCS)proforma specificationETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail].: [phone] - Fax: [phone]Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1995. All rights reserved.SIST ETS 300 376-2:1997*

Page 2ETS 300 376-2: November 1995Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 376-2:1997

Page 3ETS 300 376-2: November 1995ContentsForeword.7Introduction.71Scope.92Normative references.93Definitions, symbols and abbreviations.93.1Definitions.93.2Symbols.93.3Abbreviations.104Statements of conformance.114.1Statement of conformance to managed object class v5Interface.114.1.1Name bindings.114.1.2Packages.114.1.3Attributes.124.1.4Attribute groups.134.1.5Actions.134.1.6Notifications.134.1.7Parameters.144.2Statement of conformance to managed object class v5Ttp.144.2.1Name bindings.144.2.2Packages.154.2.3Attributes.154.2.4Attribute groups.164.2.5Actions.164.2.6Notifications.174.2.7Parameters.174.3Statement of conformance to managed object class v5TimeSlot.184.3.1Name bindings.184.3.2Packages.184.3.3Attributes.194.3.4Attribute groups.204.3.5Actions.204.3.6Notifications.204.3.7Parameters.214.4Statement of conformance to managed object class v5Provision.214.4.1Name bindings.224.4.2Packages.224.4.3Attributes.224.4.4Attribute groups.234.4.5Actions.234.4.6Notifications.234.4.7Parameters.234.5Statement of conformance to managed object class commChannel.244.5.1Name bindings.244.5.2Packages.244.5.3Attributes.254.5.4Attribute groups.254.5.5Actions.254.5.6Notifications.254.5.7Parameters.264.6Statement of conformance to managed object class isdnCommPath.264.6.1Name bindings.264.6.2Packages.27SIST ETS 300 376-2:1997

Page 4ETS 300 376-2: November 19954.6.3Attributes.274.6.4Attribute groups.284.6.5Actions.284.6.6Notifications.284.6.7Parameters.284.7Statement of conformance to managed object class pstnCommPath.294.7.1Name bindings.294.7.2Packages.294.7.3Attributes.294.7.4Attribute groups.304.7.5Actions.304.7.6Notifications.304.7.7Parameters.314.8Statement of conformance to managed object class bccCommPath.314.8.1Name bindings.314.8.2Packages.324.8.3Attributes.324.8.4Attribute groups.334.8.5Actions.334.8.6Notifications.334.8.7Parameters.334.9Statement of conformance to managed object class controlCommPath.334.9.1Name bindings.344.9.2Packages.344.9.3Attributes.344.9.4Attribute groups.354.9.5Actions.354.9.6Notifications.354.9.7Parameters.364.10Statement of conformance to managed object class protCommPath.364.10.1Name bindings.364.10.2Packages.374.10.3Attributes.374.10.4Attribute groups.384.10.5Actions.384.10.6Notifications.384.10.7Parameters.384.11Statement of conformance to managed object class linkControlCommPath.384.11.1Name bindings.394.11.2Packages.394.11.3Attributes.394.11.4Attribute groups.404.11.5Actions.404.11.6Notifications.404.11.7Parameters.414.12Statement of conformance to managed object class v5ProtectionGroup.414.12.1Name bindings.414.12.2Packages.424.12.3Attributes.424.12.4Attribute groups.424.12.5Actions.434.12.6Notifications.434.12.7Parameters.434.13Statement of conformance to managed object class v5ProtectionUnit.434.13.1Name bindings.444.13.2Packages.444.13.3Attributes.444.13.4Attribute groups.454.13.5Actions.454.13.6Notifications.454.13.7Parameters.454.14Statement of conformance to managed object class isdnBAUserPort.454.14.1Name bindings.46SIST ETS 300 376-2:1997

Page 5ETS 300 376-2: November 19954.14.2Packages.464.14.3Attributes.474.14.4Attribute groups.484.14.5Actions.484.14.6Notifications.484.14.7Parameters.494.15Statement of conformance to managed object class isdnPRAUserPort.494.15.1Name bindings.504.15.2Packages.504.15.3Attributes.504.15.4Attribute groups.524.15.5Actions.524.15.6Notifications.524.15.7Parameters.534.16Statement of conformance to managed object class pstnUserPort.534.16.1Name bindings.544.16.2Packages.544.16.3Attributes.544.16.4Attribute groups.564.16.5Actions.564.16.6Notifications.564.16.7Parameters.564.17Statement of conformance to managed object class leasedPort.574.17.1Name bindings.574.17.2Packages.574.17.3Attributes.584.17.4Attribute groups.594.17.5Actions.594.17.6Notifications.594.17.7Parameters.604.18Statement of conformance to managed object class userPortBearerChannelCtp.604.18.1Name bindings.614.18.2Packages.614.18.3Attributes.624.18.4Attribute groups.634.18.5Actions.634.18.6Notifications.634.18.7Parameters.63Annex A (informative):Bibliography.64History.65SIST ETS 300 376-2:1997

Page 6ETS 300 376-2: November 1995Blank pageSIST ETS 300 376-2:1997

Page 7ETS 300 376-2: November 1995ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS is part 2 of a multi-part standard as described below:Part 1:"Q3 interface specification at the Access Network (AN) for configuration management ofV5 interfaces and associated user ports";Part 2:"Managed Object Conformance Statement (MOCS) proforma specification".The following standards are directly related to this ETS:ETS 300 377:"Q3 interface at the Local Exchange (LE) for configuration management of V5 interfacesand associated customer profiles";ETS 300 378:"Q3 interface at the Access Network (AN) for fault and performance management of V5interfaces and associated user ports";ETS 300 379:"Q3 interface at the Local Exchange (LE) for fault and performance management of V5interfaces and associated customer profiles".Transposition datesDate of adoption of this ETS:17 November 1995Date of latest announcement of this ETS (doa):28 February 1996Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 August 1996Date of withdrawal of any conflicting National Standard (dow):31 August 1996IntroductionThe purpose of this Managed Object Conformance Statement (MOCS) proforma is to provide amechanism for a supplier of an implementation of a recommendation/standard which claims conformanceto a managed object class to provide conformance information, including management information, in astandard form.SIST ETS 300 376-2:1997

Page 8ETS 300 376-2: November 1995Blank pageSIST ETS 300 376-2:1997

Page 9ETS 300 376-2: November 19951ScopeThis second part of ETS 300 376 provides the Managed Object Conformance Statement (MOCS)proforma for the base standard ETS 300 376-1 [1]. It identifies the mandatory, conditional and optionalelements of the information model specified in ETS 300 376-1 [1].2Normative referencesThis ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 376-1 (1994): "Signalling Protocols and Switching (SPS); Q3 interfaceat the Access Network (AN) for configuration management of V5 interfaces andassociated user ports; Part 1: Q3 interface specification".[2]ETS 300 324-2 (1994): "Signalling Protocols and Switching (SPS); V interfacesat the digital Local Exchange (LE); V5.1 interface for the support of AccessNetwork (AN); Part 2: Protocol Implementation Conformance Statements (PICS)proforma".[3]ETS 300 347-2 (1994): "Signalling Protocols and Switching (SPS); V interfacesat the digital Local Exchange (LE); V5.2 interface for the support of AccessNetwork (AN); Part 2: Protocol Implementation Conformance Statements (PICS)proforma".[4]ISO/IEC 9646-7: "Information technology - Open systems interconnection -Conformance testing methodology and framework - Part 7: ImplementationConformance Statements".3Definitions, symbols and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply:configuration management: Each object class contains packages supporting creation, deletion andmodification of instances of that object class. This is referred to as configuration management. In somecases, these packages are conditional.fault management: Some object classes contain packages, in addition to those specified forconfiguration management, supporting fault reporting, logging, etc. This is referred to as faultmanagement. Typically, these packages are conditional.performance management: Some object classes contain packages, in addition to those specified forconfiguration management, supporting traffic measurements, reports when thresholds are exceeded, etc.This is referred to as performance management. Typically, these packages are conditional.3.2SymbolsThe following common notation is used for the tables in this ETS:afirst part of a table rowbsecond part of a table rowcthird part of a table rowSIST ETS 300 376-2:1997

Page 10ETS 300 376-2: November 1995The following common notation, defined in ISO/IEC 9646-7 [4], is used for the "Status" column:cconditionalmmandatoryooptionalxprohibited-not applicableThe following common notation, defined in ISO/IEC 9646-7 [4], is used for the "Support" column:lgthe item is ignored (i.e., processed syntactically but not semantically)Nnot implementedYimplemented-not applicableThe following symbolic abbreviations are used throughout the proforma tables:v5Q(AN)-nbccitt(0) identified-organization(4) etsi(0) v5AnConfigurationManagement(376)informationModel(0) nameBinding(6)v5Q(AN)-pkgccitt(0) identified-organization(4) etsi(0) v5AnConfigurationManagement(376)informationModel(0) package(4)v5Q(AN)-attccitt(0) identified-organization(4) etsi(0) v5AnConfigurationManagement(376)informationModel(0) attribute(7)v5Q(AN)-actccitt(0) identified-organization(4) etsi(0) v5AnConfigurationManagement(376)informationModel(0) action(9)v5Q(AN)-notccitt(0) identified-organization(4) etsi(0) v5AnConfigurationManagement(376)informationModel(0) notification(10)v5Q(LE)-nbccitt(0) identified-organization(4) etsi(0) v5LeConfigurationManagement(377)informationModel(0) nameBinding(6)v5Q(LE)-pkgccitt(0) identified-organization(4) etsi(0) v5LeConfigurationManagement(377)informationModel(0) package(4)v5Q(LE)-attccitt(0) identified-organization(4) etsi(0) v5LeConfigurationManagement(377)informationModel(0) attribute(7)v5Q(LE)-actccitt(0) identified-organization(4) etsi(0) v5LeConfigurationManagement(377)informationModel(0) action(9)v5Q(LE)-notccitt(0) identified-organization(4) etsi(0) v5LeConfigurationManagement(377)informationModel(0) notification(10)admin-nbccitt(0) identified-organization(4) etsi(0) oca(291) informationModel(0) nameBinding(6)admin-pkgccitt(0) identified-organization(4) etsi(0) oca(291) informationModel(0) package(4)admin-attccitt(0) identified-organization(4) etsi(0) oca(291) informationModel(0) attribute(7)smi2-pkgjoint-iso-ccitt ms(9) smi(3) part2(2) packages(4)smi2-attjoint-iso-ccitt ms(9) smi(3) part2(2) attribute(7)smi2-notjoint-iso-ccitt ms(9) smi(3) part2(2) notification(10)m3100-pkgccitt recommendation m gnm(3100) informationModel(0) package(4)m3100-attccitt recommendation m gnm(3100) informationModel(0) attribute(7)3.3AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ANAccess NetworkLELocal ExchangeMOCSManaged Object Conformance StatementTMNTelecommunication Management NetworkSIST ETS 300 376-2:1997

Page 11ETS 300 376-2: November 19954Statements of conformanceNotwithstanding the provisions of the copyright Clause related to the text of this ETS, ETSI grants thatusers of this ETS may freely reproduce the MOCS proforma in this clause so that it can be used for itsintended purposes and may further publish the completed MOCS.4.1Statement of conformance to managed object class v5InterfaceTable 1: Object class supportIndexManaged object class template labelValue of OBJECT IDENTIFIER for the classStatusSupport1.1v5Interface{ccitt(0) identified-organization(4) etsi(0)v5LeConfigurationManagement(377)informationModel(0) managedObjectClass(3) 1}mThe supplier of the implementation shall state whether or not all mandatory features of the object listedabove are supported in table 2.Table 2: Feature supportIndexSub-IndexSupport2.12.1.1Is configuration management supported?2.1.2Are all mandatory features for configuration managementsupported?2.22.2.1Is fault management supported?2.2.2Are all mandatory features for fault management supported?4.1.1Name bindingsThe name binding of this object class depends on the architecture of the AN and is outside the scope ofthis ETS.4.1.2PackagesThe supplier of the implementation shall state whether or not the packages specified by this managedobject of this class are supported, in table 3.Packages of superclasses which are not applicable are listed in the package support table only. Theassociated attributes, actions and notifications are not mentioned in the following tables.Table 3: Package supportIndexPackage labelValue of OBJECT IDENTIFIERStatusSupport3.1peerManagedElementPackage{v5Q(LE)-pkg 5}o3.2supportedByObjectListPackage{v5Q(LE)-pkg 7}c13.3relationshipChangeNotificationPackage{v5Q(LE)-pkg 6}o3.4commonDeleteBehaviourPackage{v5Q(LE)-pkg 2}m3.5operationalStatePackage{m3100-pkg 19}o3.6v5availabilityStatusPackage{smi2-pkg 22}o3.7userLabelPackage{m3100-pkg 32}o3.8locationNamePackage{m3100-pkg 17}o3.9objectManagementNotificationsPackage{m3100-pkg 20}o3.10stateChangeNotificationsPackage{m3100-pkg 28}o3.11tmnCommunicationsAlarmInformationPackage{m3100-pkg 30}c23.12alarmSeverityAssignmentPointerPackage{m3100-pkg 3}c23.13packagesPackage{smi2-pkg 16}m3.14allomorphicPackage{smi2-pkg 17}oc1:if the information model is not only used for provisioning then m else -.c2:if 2.2.1 then m else -.SIST ETS 300 376-2:1997

Page 12ETS 300 376-2: November 19954.1.3AttributesThe supplier of the implementation shall state whether or not the attributes specified by all the packagesinstantiated in a managed object class definition are supported, in the "Support" and "Additionalinformation" columns of table 4. The supplier of the implementation shall indicate support for each of theoperations for each attribute supported.Table 4: Attribute supportIndexAttribute template labelValue of OBJECT IDENTIFIERStatusSupport4.1av5InterfaceId{v5Q(LE)-att 34}m4.2apeerManagedElementId{v5Q(LE)-att 25}c14.3asupportedProtocolVersion{v5Q(LE)-att 31}m4.4aserverV5Ttps{v5Q(LE)-att 30}m4.5aclientUserPorts{v5Q(LE)-att 14}m4.6aoperationalState{smi2-att 35}c24.7aavailabilityStatus{smi2-att 33}c34.8asupportedByObjectList{m3100-att 40}c44.9auserLabel{m3100-att 50}c54.10alocationName{m3100-att 27}c64.11aobjectClass{smi2-att 65}m4.12anameBinding{smi2-att 63}m4.13apackages{smi2-att 66}m4.14aallomorphs{smi2-att 50}c7c1:if 3.1 then m else -.c4:if 3.2 then m else -.c7:if 3.14 then m else -.c2:if 3.5 then m else -.c5:if 3.7 then m else -.c3:if 3.6 then m else -.c6:if 3.8 then m else -.Table 4 (continued): Attribute supportStatusIndexSetByCreateGetReplaceAddRemoveSetToDefault4.1bomxxxx4.2bmmmxxx4.3bmmxxxx4.4bxmxxxx4.5bxmxxxx4.6bxmxxxx4.7bxmxxxx4.8bmmxxxx4.9bmmmxxx4.10bmmmxxx4.11bmmxxxx4.12bmmxxxx4.13bmmxxxx4.14bmmxxxxTable 4 (concluded): Attribute supportSupportIndexSetByCreateGetReplaceAddRemoveSetToDefaultAdditional information4.1c4.2c4.3c4.4c4.5c4.6c4.7c4.8c4.9c4.10c4.11c4.12c4.13c4.14cSIST ETS 300 376-2:1997

Page 13ETS 300 376-2: November 19954.1.4Attribute groupsThere are no attribute groups specified for this managed object class.4.1.5ActionsThe supplier of the implementation shall state whether or not the actions specified by all the packagesinstantiated in a managed object of this class are supported, in the "Support" and "Additional information"columns of table 5. The supplier of the implementation shall indicate support in terms on the confirmedand non-confirmed modes.Table 5: Action supportIndexAction type template labelValue of action typeidentifierStatusSupportAdditional information5.1setReciprocalPointer{v5Q(LE)-act 1}m5.2releaseReciprocalPointer{v5Q(LE)-act 2}m5.3restart{v5Q(LE)-act 14}m5.4stytemStartup{v5Q(LE)-act 16}m4.1.6NotificationsThe supplier of the implementation shall state whether or not the notifications specified by all thepackages instantiated in a managed object of this class are supported, in the "Support" and "Additionalinformation" columns of table 6. The supplier of the implementation shall indicate support in terms on theconfirmed and non-confirmed modes.Table 6: Notification supportSupportIndexNotification typetemplate labelValue of notificationtype identifierStatusConfirmedNon-confirmedAdditional information6.1aobjectCreation{smi2-not 6}c16.2aobjectDeletion{smi2-not 7}c16.3aattributeValueChange{smi2-not 1}c16.4astateChange{smi2-not 14}c26.5arelationshipChange{smi2-not 12}c36.6arestartResult{v5Q(LE)-not 11}m6.7asystemStartupResult{v5Q(LE)-not 12}mc1:if 3.9 then m else -.c2:if 3.10 then m else -.c3:if 3.3 then m else -.Table 6 (continued): Notification supportIndexSub-indexNotification fieldname labelValue of objectidentifier of attributetype associated withfieldStatusSupportAdditional information6.1b6.1.1sourceIndicator{smi2-att 26}o6.1.2attributeList{smi2-att 9}o6.1.3notificationIdentifier{smi2-att 16}o6.1.4correlatedNotifications{smi2-att 12}o6.1.5additionalText{smi2-att 7}o6.1.6additionalInformation{smi2-att 6}o6.2b6.2.1sourceIndicator{smi2-att 26}o6.2.2attributeList{smi2-att 9}o6.2.3notificationIdentifier{smi2-att 16}o6.2.4correlatedNotifications{smi2-att 12}o6.2.5additionalText{smi2-att 7}o6.2.6additionalInformation{smi2-att 6}o(continued)SIST ETS 300 376-2:1997

Page 14ETS 300 376-2: November 1995Table 6 (concluded): Notification supportIndexSub-indexNotification fieldname labelValue of objectidentifier of attributetype associated withfieldStatusSupportAdditional information6.3b6.3.1sourceIndicator{smi2-att 26}o6.3.2attributeIdentifierList{smi2-att 8}o6.3.3AttributeValueChangeDefinition{smi2-att 10}m6.3.4notificationIdentifier{smi2-att 16}o6.3.5correlatedNotifications{smi2-att 12}o6.3.6additionalText{smi2-att 7}o6.3.7additionalInformation{smi2-att 6}o6.4b6.4.1sourceIndicator{smi2-att 26}o6.4.2attributeIdentifierList{smi2-att 8}o6.4.3stateChangeDefinition{smi2-att 28}m6.4.4notificationIdentifier{smi2-att 16}o6.4.5correlatedNotifications{smi2-att 12}o6.4.6additionalText{smi2-att 7}o6.4.7additionalInformation{smi2-att 6}o6.5b6.5.1sourceIndicator{smi2-att 26}o6.5.2attributeIdentifierList{smi2-att 8}o6.5.3relationshipChangeDefinition{smi2-att 20}m6.5.4notificationIdentifier{smi2-att 16}o6.5.5correlatedNotifications{smi2-att 12}o6.5.6additionalText{smi2-att 7}o6.5.7additionalInformation{smi2-att 6}o4.1.7ParametersThere are no parameters specified for the configuration management in this managed object class.4.2Statement of conformance to managed object class v5TtpTable 7: Object class supportIndexManaged object class template labelValue of OBJECT IDENTIFIER for the classStatusSupport7.1v5Ttp{ccitt(0) identified-organization(4) etsi(0)v5ConfigurationLeManagement(377)informationModel(0) managedObjectClass(3) 2}mThe supplier of the implementation shall state whether or not all mandatory features of the object listedabove are supported in table 8.Table 8: Feature supportIndexSub-IndexSupport8.18.1.1Is configuration management supported?8.1.2Are all mandatory features for configuration managementsupported?8.28.2.1Is fault management supported?8.2.2Are all mandatory features for fault management supported?4.2.1Name bindingsThe name binding of this object class depends on the architecture of the AN and is outside the scope ofthis ETS.SIST ETS 300 376-2:1997

Page 15ETS 300 376-2: November 19954.2.2PackagesThe supplier of the implementation shall state whether or not the packages specified by this managedobject of this class are supported, in table 9.Packages of superclasses which are not applicable are listed in the package support table only. Theassociated attributes, actions and notifications are not mentioned in the following tables.Table 9: Package supportIndexPackage labelValue of OBJECT IDENTIFIERStatusSupport9.1neSpecificPointerPackage{v5Q[LE)-pkg 4}o9.2v5AvailabilityStatusPackage{v5Q[LE)-pkg 8}o9.3commonDeleteBehaviourPackage{v5Q[LE)-pkg 2}m9.4operationalStatePackage{m3100-pkg 19}m9.5administrativeStatePackage{smi2-pkg 14}m9.6supportableClientListPackage{m3100-pkg 27}o9.7ttpInstancePackage{m3100-pkg 31}m9.8createDeleteNotificationPackage{m3100-pkg 10}m9.9stateChangeNotificationPackage{m3100-pkg 28}o9.10attributeValueChangeNotificationPackage{m3100-pkg 4}o9.11crossConnectionPointerPackage{m3100-pkg 11}c19.12characteristicInformationPackage{m3100-pkg 7}o9.13networkLevelPackage{m3100-pkg 18}-9.14tmnCommunicationsAlarmInformationPackage{m3100-pkg 30}c29.15alarmSeverityAssignmentPointerPackage{m3100-pkg 3}c29.16packagesPackage{smi2-pkg 16}m9.17allomorphicPackage{smi2-pkg 17}oc1:if the termination point can be flexibly assigned then m else -.c2:if 8.2.1 then m else -.4.2.3AttributesThe supplier of the implementation shall state whether or not the attributes specified by all the packagesinstantiated in a managed object class definition are supported, in the "Support" and "Additionalinformation" columns of table 10. The supplier of the implementation shall indicate support for each of theoperations for each attribute supported.Table 10: Attribute supportIndexAttribute template labelValue of OBJECT IDENTIFIERStatusSupport10.1aassocV5Interface{v5Q(LE)-att 8}m10.2alinkId{v5Q(LE)-att 21}m10.3ablockingStatus{v5Q(LE)-att 13}m10.4asupportedByObjectList{m3100-att 40}m10.5aneSpecificPointer{v5Q(LE)-att 22}c110.6aoperationalState{smi2-att 35}m10.7aavailabilityStatus{smi2-att 33}c210.8aupstreamConnectivityPointer{m3100-att 49}m10.9aadministrativeState{smi2-att 31}m10.10asupportableClientList{smi2-att 39}c310.11atTPId{m3100-att 48}m10.12adownstreamConnectivityPointer{m3100-att 19}m10.13acrossConnectionObjectPointer{m3100-att 16}c410.14acharacteristicInformation{m3100-att 8}c510.15aobjectClass{smi2-att 65}m10.16anameBinding{smi2-att 63}m10.17apackages{smi2-att 66}m10.18aallomorphs{smi2-att 50}c6c1:if 9.1 then m else -.c4:if 9.11 then m else -.c2:if 9.2 then m else -.c5:if 9.12 then m else -.c3:if 9.6 then m else -.c6:if 9.17 then m else -.SIST ETS 300 376-2:1997

Page 16ETS 300 376-2: November 1995Table 10 (continued): Attribute supportStatusIndexSetByCreateGetReplaceAddRemoveSetToDefault10.1bxmxxxx10.2bmmmxxx10.3bmmxxxx10.4bmmxxxx10.5bmmxxxx10.6bxmxxxx10.7bxmxxxx10.8bomxxxx10.9bmmmxxx10.10bmmxxxx10.11bomxxxx10.12bomxxxx10.13bmmxxxx10.14bmmxxxx10.15bmmxxxx10.16bmmxxxx10.17bmmxxxx10.18bmmxxxxTable 10 (concluded): Attribute supportSupportIndexSetByCreateGetReplaceAddRemoveSetToDefaultAdditional information10.1c10.2c10.3c10.4c10.5c10.6c10.7c10.8c10.9c10.10c10.11c10.12c10.13c10.14c10.15c10.16c10.17c10.18c4.2.4Attribute groupsThere are no attribute groups specified for this managed object class.4.2.5ActionsThe supplier of the implementation shall state whether or not the actions specified by all the packagesinstantiated in a managed object of this class are supported, in the "Support" and "Additional information"columns of table 11. The supplier of the implementation shall indicate support in terms on the confirmedand non-confirmed modes.Table 11: Action supportIndexAction type template labelValue of action typeidentifierStatusSupportAdditional information11.1checkLinkId{v5Q(LE)-act 13}cc:if v5.2 then m else -.SIST ETS 300 376-2:1997

Page 17ETS 300 376-2: November 19954.2.6NotificationsThe supplier of the implementation shall state whether or not the notifications specified by all thepackages instantiated in a managed object of this class are supported, in the "Support" and "Additionalinformation" columns of table 12. The supplier of the implementation shall indicate support in terms on theconfirmed and non-confirmed modes.Table 12: Notification supportSupportIndexNotification typetemplate labelValue of notificationtype identifierStatusConfirmedNon-confirmedAdditional information12.1aobjectCreation{smi2-not 6}m12.2aobjectDeletion{smi2-not 7}m12.3aattributeValueChange{smi2-not 1}c112.4astateChange{smi2-not 14}c212.5ashutdownRejected{v5(LE)-not 5}m12.6acheckLinkIdResult{v5(LE)-not 10}c3c1:if 10.10 then m else -.c2:if 10.9 then m else -.c3:if v5.2 then m else -.Table 12 (concluded): Notification supportIndexSub-indexNotification fieldname labelValue of objectidentifier of attributetype associated withfieldStatusSupportAdditional information12.1b12.1.1sourceIndicator{smi2-att 26}o12.1.2attributeList{smi2-att 9}o12.1.3notificationIdentifier{smi2-att 16}o12.1.4correlatedNotifications{smi2-att 12}o12.1.5additionalText{smi2-att 7}o12.1.6additionalInformation{smi2-att 6}o12.2b12.2.1sourceIndicator{smi2-att 26}o12.2.2attributeList{smi2-att 9}o12.2.3notificationIdentifier{smi2-att 16}o12.2.4correlatedNotifications{smi2-att 12}o12.2.5additionalText{smi2-att 7}o12.2.6additionalInformation{smi2-att 6}o12.3b12.3.1sourceIndicator{smi2-att 26}o12.3.2attributeIdentifierList{smi2-att 8}o12.3.3attributeValueChangeDefinition{smi2-att 10}m12.3.4notificationIdentifier{smi2-att 16}o12.3.5correlatedNotifications{smi2-att 12}o12.3.6additionalText{smi2-att 7}o12.3.7additionalInformation{smi2-att 6}o12.4b12.4.1sourceIndicator{smi2-att 26}o12.4.2attributeIdentifierList{smi2-att 8}o12.4.3stateChangeDefinition{smi2-att 28}m12.4.4notificationIdentifier{smi2-att 16}o12.4.5correlatedNotifications{smi2-att 12}o12.4.6additionalText{smi2-att 7}o12.4.7additionalInformation{smi2-att 6}o4.2.7ParametersThere are no parameters specified for the configuration management in this managed object class.SIST ETS 300 376-2:1997

Page 18ETS 300 376-2: November 19954.3Statement of conformance to managed object class v5TimeSlotTable 13: Object class supportIndexManaged object class template labelValue of OBJECT IDENTIFIER for the classStatusSupport13.1v5TimeSlot{ccitt(0) identified-organization(4) etsi(0)v5LeConfigurationManagement(377)informationModel(0) managedObjectClass(3) 3}mThe supplier of the implementation shall state whether or not all mandatory features of the object listedabove are supported in table 14.Table 14: Feature supportIndexSub-IndexSupport14.114.1.1Is configuration management supported?14.1.2Are all mandatory features for configuration managementsupported?14.214.2.1Is fault management supported?14.2.2Are all mandatory features for fault management supported?4.3.1Name bindingsThe supplier of the implementation shall state which name bindings of the managed object class aresupported, in the "Support" and "Additional information" columns of table 15.Table 15: Name binding supportIndexName bindingtemplate labelValue of OBJECTIDENTIFIERSuperior object class template labelStatusSupport15.1av5TimeSlot - v5Ttp{v5Q(LE)-nb 3}v5TtpmTable 15 (concluded): Name binding supportStatusSupportIndexObjectcreationObjectdeletionObjectcreationObjectdeletionAdditional information15.1bccc:if 14.1.1 then m else -.4.3.2PackagesThe supplier of the implementation shall state whether or not the packages specified by this managedobject of this class are supported, in table 16.Packages of superclasses which are not applicable are listed in the package support table only. Theassociated attributes, actions and notifications are not mentioned in the following tables.SIST ETS 300 376-2:1997

Page 19ETS 300 376-2: November 1995Table 16: Package supportIndexPackage labelValue of OBJECT IDENTIFIERStatusSupport16.1operationalStatePackage{m3100-pkg 19}m16.2ctpInstancePackage{m3100-pkg 12}m16.3createDeleteNotificationsPackage{m3100-pkg 10}m16.4commonDeleteBehaviourPackage{v5Q(LE)-pkg 2}m16.5v5TsAdministrativeStatePackage{v5Q(LE)-pkg 11}o16.6tmnCommmunicationsAlarmInformation Package{m3100-pkg 30}c116.7alarmSeverityAssignmentPointerPackage{m3100-pkg 3}c116.8channelNumberPackage{m3100-pkg 6}o16.9attributeValueChangeNotificationPackage{m3100-pkg 4}o16.10stateChangeNotificationPackage{m3100-pkg28}o16.11crossConnectionPointerPackage{m3100-pkg 11}c216.12characteristicInformationPackage{m3100-pkg 7}o16.13networkLevelPackage{m3100-pkg 18}-16.14packagesPackage{smi2-pkg 16}m16.15allomorphicPackage{smi2-pkg 17}oc1:if 14.2.1 then m else -.c2:if the termination point can be flexibly assigned then m else -.4.3.3AttributesThe supplier of the implementation shall state whether or not the attributes specified by all the packagesinstantiated in a managed object class definition are supported, in the "Support" and "Additionalinformation" columns of table 17. The supplier of the implementation shall indicate support for each of theoperations for each attribute supported.Table 17: Attribute supportIndexAttribute template labelValue of OBJECT IDENTIFIERStatusSupport17.1av5ChannelType{v5Q(LE)-att 33}m17.2aassocResource{v5Q(LE)-att 6}m17.3aoperationalState{smi2-att 35}m17.4acTPId{m3100-att 13}m17.5aadministrativeState{smi2-att 31}c117.6adownstreamConnectivityPointer{m3100-att 19}m17.7aupstreamConnectivityPointer{m3100-att 49}m17.8asupportedByObjectList{m3100-att 40}m17.9achannelNumber{m3100-att 7}c217.10acrossConne
...