Transmission and Multiplexing (TM); Synchronous Digital Hierarchy (SDH); SDH information model for the Network Element (NE) view

RE/TM-02213

Prenos in multipleksiranje (TM) – Sinhrona digitalna hierarhija (SDH) – Informacijski model v sistemu SDH, gledano s strani omrežnega elementa (NE)

General Information

Status
Published
Publication Date
11-Feb-1997
Current Stage
12 - Completion
Due Date
20-Feb-1997
Completion Date
12-Feb-1997
Standard
ETS 300 304 E2:2003
English language
52 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-december-2003
Prenos in multipleksiranje (TM) – Sinhrona digitalna hierarhija (SDH) –
Informacijski model v sistemu SDH, gledano s strani omrežnega elementa (NE)
Transmission and Multiplexing (TM); Synchronous Digital Hierarchy (SDH); SDH
information model for the Network Element (NE) view
Ta slovenski standard je istoveten z: ETS 300 304 Edition 2
ICS:
33.040.20 Prenosni sistem Transmission systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 304
TELECOMMUNICATION February 1997
STANDARD Second Edition
Source: ETSI TC-TM Reference: RE/TM-02213
ICS: 33.020
Key words: Transmission, SDH, management, information model, NE
Transmission and Multiplexing (TM);
Synchronous Digital Hierarchy (SDH);
SDH information model for the Network Element (NE) view
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
Copyright Notification: No 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 1997. All rights reserved.

Page 2
ETS 300 304: February 1997
Whilst 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.

Page 3
ETS 300 304: February 1997
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Abbreviations.8
4 Registration supporting Abstract Syntax Notation one (ASN.1).9
5 Generic objects fragment.9
5.1 Generic objects - object classes.9
5.2 Generic objects - packages, attributes, ASN.1, name-bindings .9
6 SDH Termination Point (TP) fragment .9
6.1 SDH TP - object classes.9
6.2 SDH TP - packages.10
6.3 SDH TP - attributes.10
6.4 SDH TP - name bindings .11
6.5 SDH TP - subordination rules .12
6.6 SDH TP - constraints .13
7 Plesiochronous Digital Hierarchy (PDH) fragment .14
7.1 Object classes definitions .14
7.2 Attributes definitions.16
7.3 Name bindings definitions.17
7.4 ASN.1 definitions .18
8 Cross-connection fragment.18
8.1 Cross-connection - object classes.18
8.2 Cross-connection - packages .18
8.3 Cross-connection - attributes.18
8.4 Cross-connection - name bindings .19
9 Protection fragment.20
9.1 Object classes .20
9.2 Packages .20
9.3 Attributes.20
9.4 Name bindings.20
10 Equipment fragment.21
10.1 Equipment - object classes.21
10.2 Equipment - attributes.22
10.3 Equipment - parameter.24
10.4 Equipment - name bindings .24
10.5 Equipment - supporting ASN.1 .25
11 Support objects fragment.26
11.1 Support objects - object classes.26
11.2 Support objects - packages .28
11.3 Support objects - attributes.29
11.4 Support objects - name bindings .31
11.5 Support objects - parameter .31
11.6 Support objects - supporting ASN.1 .32

Page 4
ETS 300 304: February 1997
Annex A (normative): Figures and tables . 33
Annex B (informative): Bibliography . 51
History. 52

Page 5
ETS 300 304: February 1997
Foreword
This second edition European Telecommunication Standard (ETS) has been produced by the
Transmission and Multiplexing (TM) Technical Committee of the European Telecommunications
Standards Institute (ETSI).
This second edition ETS describes the information model for Network Elements (NEs) which use the
Synchronous Digital Hierarchy (SDH) multiplexing structure.
Transposition dates
Date of adoption 18 October 1996
Date of latest announcement of this ETS (doa): 31 May 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 November 1997
Date of withdrawal of any conflicting National Standard (dow): 30 November 1997

Page 6
ETS 300 304: February 1997
Blank page
Page 7
ETS 300 304: February 1997
1 Scope
This second edition ETS defines the information model to be used at the interface between Network
Elements (NEs) and management systems, for the management of Synchronous Digital Hierarchy (SDH)
NEs.
This ETS defines the information model for SDH NEs.
This ETS does not define:
- the protocol stack to be used for message communication;
- the network level management processes;
- the application contexts;
- the conformance requirements to be met by an implementation of this information model;
- information models for other systems or equipment.
The information model defined here (and the corresponding message set) is concerned with the
management of NEs, the equipment by which they are implemented and the functions contained within
them. More precisely, it applies to an equipment domain visible at the element manager to NE interface
and is only concerned with information available within that domain. Information proper to the domain of a
network level management process is not included within this model.
2 Normative references
This ETS incorporates, by dated or undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references, the
latest edition of the publication referred to applies.
[1] ITU-T Recommendation G.709 (1993): "Synchronous multiplexing structure".
[2] ITU-T Recommendation G.774 (1992): "Synchronous digital hierarchy (SDH)
management information model for the network element view".
[3] ITU-T Recommendation G.774.03 (1994): "Synchronous digital hierarchy (SDH)
management of multiplex-section protection for the network element view".
[4] ITU-T Recommendation G.783 (1993): "Characteristics of synchronous digital
hierarchy (SDH) equipment functional blocks".
[5] ITU-T Recommendation M.3100 (1995): "Generic network information model".
[6] ITU-T Recommendation X.721 (1992): "Information technology - Open Systems
Interconnection - Structure of management information: Definition of
management information".
[7] ITU-T Recommendation G.702 (1988): "Digital hierarchy bit rates".
[8] ETS 300 371 (1994): "Transmission and Multiplexing (TM); Plesiochronous
Digital Hierarchy (PDH) information model for the Network Element (NE) view".

Page 8
ETS 300 304: February 1997
3 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AIS Alarm Indication Signal
AP Access Point
ATM Asynchronous Transfer Mode
AU Administrative Unit
AUG Administrative Unit Group
CCITT Comité Consultatif International Télégraphique et Téléphonique
CMIP Common Management Information Protocol
CMIS Common Management Information Service
CP Connection Point
CTP Connection Termination Point
GTP Group Termination Point
HPA Higher Order Path Adaptation
HPC Higher Order Path Connection
HPT Higher Order Path Termination
IA Indirect Adaptor
IOS Intra-Office Section
ISO International Organization for Standardization
ITU-T International Telecommunications Union - Telecommunications sector
LOF Loss Of Frame
LPA Lower Order Path Adaptation
LPC Lower Order Path Connection
LPT Lower Order Path Termination
MS Multiplexer Section
MSA Multiplexer Section Adaptation
MST Multiplexer Section Termination
MSTTP Multiplexer Section Trail Termination Point
NE Network Element
OS Operation System
OSI Open Systems Interconnection
PDH Plesiochronous Digital Hierarchy
Pkg Packages
POH Path OverHead
PPI Plesiochronous Physical Interface
RDN Relative Distinguished Name
RS Regenerator Section
RST Regenerator Section Termination
RSTTP Regenerator Section Trail Termination Point
SDH Synchronous Digital Hierarchy
SDHNE Synchronous Digital Hierarchy Network Element
Snk Sink
Src Source
SPI Synchronous Physical Interface
STM-N Synchronous Transport Module-N
TMN Telecommunication Management Network
TP Termination Point
TTP Trail Termination Point
TU Tributary Unit
TUG Tributary Unit Group
VC-n Virtual Container n
Page 9
ETS 300 304: February 1997
4 Registration supporting Abstract Syntax Notation one (ASN.1)
PrETS5 {ccitt(0) identified-organization(4) etsi(0) ets304(304) informationModel(0) asn1Module(2)
prETS5(0)}
DEFINITIONS IMPLICIT TAGS ::= BEGIN
-- EXPORT Everything
prETS300304 OBJECT IDENTIFIER ::= {ccitt(0) identified-organization(4) etsi(0) ets304(304)
informationModel(0)}
etsObjectClass OBJECT IDENTIFIER ::= {prETS300304 managedObjectClass(3)}
etsPackage OBJECT IDENTIFIER ::= {prETS300304 package(4)}
etsParameter OBJECT IDENTIFIER ::= {prETS300304 parameter(5)}
etsNameBinding OBJECT IDENTIFIER ::= {prETS300304 nameBinding(6)}
etsAttribute OBJECT IDENTIFIER ::= {prETS300304 attribute(7)}
etsAction OBJECT IDENTIFIER ::= {prETS300304 action(9)}
etsNotification OBJECT IDENTIFIER ::= {prETS300304 notification(10)}
END
5 Generic objects fragment
In this fragment, a working sub-set of standard and mature object classes have been adopted, mainly
from the ITU-T X.700 series of Recommendations.
5.1 Generic objects - object classes
In this context the IMPORTS clause specifies the object classes which can be instantiated in the scope of
this ETS. The IMPORTS clause does not include uninstantiated superclasses.
BEGIN
IMPORTS
alarmRecord,
attributeValueChangeRecord,
eventForwardingDiscriminator,
log,
objectCreationRecord
objectDeletionRecord
stateChangeRecord,
FROM {joint-iso-ccitt ms(9) smi(3) part2(2) managedObjectClass(3) }
alarmSeverityAssignmentProfile
FROM {ccitt(0) recommendation(0) m(13) m3100(3100) informationModel(0) managedObjectClass(3) }
;
END
5.2 Generic objects - packages, attributes, ASN.1, name-bindings
All packages, attributes, ASN.1 and name-bindings associated with object classes are implicitly imported
from ITU-T Recommendations defining the appropriate object classes.
6 SDH Termination Point (TP) fragment
6.1 SDH TP - object classes
In this context, the IMPORTS clause specifies the object classes which can be instantiated in the scope of
this ETS. The IMPORTS clause does not include uninstantiated superclasses.
BEGIN
IMPORTS
au4CTPBidirectional,
au4CTPSink,
au4CTPSource,
augBidirectional,
augSink,
augSource,
electricalSPITTPBidirectional,
electricalSPITTPSink,
electricalSPITTPSource,
msCTPBidirectional,
msCTPSink,
msCTPSource,
msDatacomCTPBidirectional,
msDatacomCTPSink,
msDatacomCTPSource,
msOrderwireCTPBidirectional,
Page 10
ETS 300 304: February 1997
msOrderwireCTPSink,
msOrderwireCTPSource,
msTTPBidirectional,
msTTPSink,
msTTPSource,
opticalSPITTPBidirectional,
opticalSPITTPSink,
opticalSPITTPSource,
rsCTPBidirectional,
rsCTPSink,
rsCTPSource,
rsDatacomCTPBidirectional,
rsDatacomCTPSink,
rsDatacomCTPSource,
rsOrderwireCTPBidirectional,
rsOrderwireCTPSink,
rsOrderwireCTPSource,
rsTTPBidirectional,
rsTTPSink,
rsTTPSource,
rsUserChannelCTPBidirectional,
rsUserChannelCTPSink,
rsUserChannelCTPSource,
tu11CTPBidirectional,
tu11CTPSink,
tu11CTPSource,
tu12CTPBidirectional,
tu12CTPSink,
tu12CTPSource,
tu2CTPBidirectional,
tu2CTPSink,
tu2CTPSource,
tu3CTPBidirectional,
tu3CTPSink,
tu3CTPSource,
tug2Bidirectional,
tug2Sink,
tug2Source,
tug3Bidirectional,
tug3Sink,
tug3Source,
vc11TTPBidirectional,
vc11TTPSink,
vc11TTPSource,
vc12TTPBidirectional,
vc12TTPSink,
vc12TTPSource,
vc2TTPBidirectional,
vc2TTPSink,
vc2TTPSource,
vc3TTPBidirectional,
vc3TTPSink,
vc3TTPSource,
vc4TTPBidirectional,
vc4TTPSink,
vc4TTPSource,
vcnUserChannelCTPBidirectional,
vcnUserChannelCTPSink,
vcnUserChannelCTPSource
FROM {ccitt(0) recommendation(0) g(7) g774(774) informationModel(0) managedObjectClass(3) }
;
END
6.2 SDH TP - packages
All packages associated with object classes are implicitly imported from ITU-T Recommendations defining
the appropriate object classes.
6.3 SDH TP - attributes
All attributes associated with object classes are implicitly imported from ITU-T Recommendations defining
the appropriate object classes.
supportedByObjectList
The value of the supportedByObjectList attribute points to the equipment and software
objects which implement the TPs.

Page 11
ETS 300 304: February 1997
6.4 SDH TP - name bindings
BEGIN
IMPORTS
au4CTPBidirectional-augBidirectional,
au4CTPSink-augBidirectional,
au4CTPSink-augSink,
au4CTPSource-augBidirectional,
au4CTPSource-augSource,
augBidirectional-msTTPBidirectional,
augSink-msTTPSink,
augSource-msTTPSource,
electricalSPITTPBidirectional-sdhNE,
electricalSPITTPSink-sdhNE,
electricalSPITTPSource-sdhNE,
msCTPBidirectional-rsTTPBidirectional,
msCTPSink-rsTTPBidirectional,
msCTPSink-rsTTPSink,
msCTPSource-rsTTPBidirectional,
msCTPSource-rsTTPSource,
msDatacomCTPBidirectional-msTTPBidirectional,
msDatacomCTPSink-msTTPBidirectional,
msDatacomCTPSink-msTTPSink,
msDatacomCTPSource-msTTPBidirectional,
msDatacomCTPSource-msTTPSource,
msOrderwireCTPBidirectional-msTTPBidirectional,
msOrderwireCTPSink-msTTPBidirectional,
msOrderwireCTPSink-msTTPSink,
msOrderwireCTPSource-msTTPBidirectional,
msOrderwireCTPSource-msTTPSource,
msTTPBidirectional-sdhNE,
msTTPSink-sdhNE,
msTTPSource-sdhNE,
opticalSPITTPBidirectional-sdhNE,
opticalSPITTPSink-sdhNE,
opticalSPITTPSource-sdhNE,
rsCTPBidirectional-electricalSPITTPBidirectional,
rsCTPBidirectional-opticalSPITTPBidirectional,
rsCTPSink-electricalSPITTPBidirectional,
rsCTPSink-electricalSPITTPSink,
rsCTPSink-opticalSPITTPBidirectional,
rsCTPSink-opticalSPITTPSink,
rsCTPSource-electricalSPITTPBidirectional,
rsCTPSource-electricalSPITTPSource,
rsCTPSource-opticalSPITTPBidirectional,
rsCTPSource-opticalSPITTPSource,
rsDatacomCTPBidirectional-rsTTPBidirectional,
rsDatacomCTPSink-rsTTPBidirectional,
rsDatacomCTPSink-rsTTPSink,
rsDatacomCTPSource-rsTTPBidirectional,
rsDatacomCTPSource-rsTTPSource,
rsOrderwireCTPBidirectional-rsTTPBidirectional,
rsOrderwireCTPSink-rsTTPBidirectional,
rsOrderwireCTPSink-rsTTPSink,
rsOrderwireCTPSource-rsTTPBidirectional,
rsOrderwireCTPSource-rsTTPSource,
rsTTPBidirectional-sdhNE,
rsTTPSink-sdhNE,
rsTTPSource-sdhNE,
rsUserChannelCTPBidirectional-rsTTPBidirectional,
rsUserChannelCTPSink-rsTTPBidirectional,
rsUserChannelCTPSink-rsTTPSink,
rsUserChannelCTPSource-rsTTPBidirectional,
rsUserChannelCTPSource-rsTTPSource,
tu11CTPBidirectional-tug2Bidirectional,
tu11CTPSink-tug2Bidirectional,
tu11CTPSink-tug2Sink,
tu11CTPSource-tug2Bidirectional,
tu11CTPSource-tug2Source,
tu12CTPBidirectional-tug2Bidirectional,
tu12CTPSink-tug2Bidirectional,
tu12CTPSink-tug2Sink,
tu12CTPSource-tug2Bidirectional,
tu12CTPSource-tug2Source,
tu2CTPBidirectional-tug2Bidirectional,
tu2CTPSink-tug2Bidirectional,
tu2CTPSink-tug2Sink,
tu2CTPSource-tug2Bidirectional,
tu2CTPSource-tug2Source,
tu3CTPBidirectional-tug3Bidirectional,
tu3CTPSink-tug3Bidirectional,
tu3CTPSink-tug3Sink,
tu3CTPSource-tug3Bidirectional,
tu3CTPSource-tug3Source,
Page 12
ETS 300 304: February 1997
tug2Bidirectional-tug3Bidirectional,
tug2Sink-tug3Sink,
tug2Source-tug3Source,
tug3Bidirectional-vc4TTPBidirectional,
tug3Sink-vc4TTPSink,
tug3Source-vc4TTPSource,
vc11TTPBidirectional-sdhNE,
vc11TTPSink-sdhNE,
vc11TTPSource-sdhNE,
vc12TTPBidirectional-sdhNE,
vc12TTPSink-sdhNE,
vc12TTPSource-sdhNE,
vc2TTPBidirectional-sdhNE,
vc2TTPSink-sdhNE,
vc2TTPSource-sdhNE,
vc3TTPBidirectional-sdhNE,
vc3TTPSink-sdhNE,
vc3TTPSource-sdhNE,
vc4TTPBidirectional-sdhNE,
vc4TTPSink-sdhNE,
vc4TTPSource-sdhNE,
vcnUserChannelCTPBidirectional-vc3TTPBidirectional,
vcnUserChannelCTPBidirectional-vc4TTPBidirectional,
vcnUserChannelCTPSink-vc3TTPBidirectional,
vcnUserChannelCTPSink-vc3TTPSink,
vcnUserChannelCTPSink-vc4TTPBidirectional,
vcnUserChannelCTPSink-vc4TTPSink,
vcnUserChannelCTPSource-vc3TTPBidirectional,
vcnUserChannelCTPSource-vc3TTPSource,
vcnUserChannelCTPSource-vc4TTPBidirectional,
vcnUserChannelCTPSource-vc4TTPSource
FROM {ccitt(0) recommendation(0) g(7) g774(774) informationModel(0) nameBinding(6) }
;
END
6.5 SDH TP - subordination rules
BEGIN
IMPORTS
augSinkSubordination,
augSourceSubordination,
augBidirectionalSubordination,
electricalSPITTPSinkSubordination,
electricalSPITTPSourceSubordination,
electricalSPITTPBidirectionalSubordination,
opticalSPITTPSinkSubordination,
opticalSPITTPSourceSubordination,
opticalSPITTPBidirectionalSubordination,
msTTPSinkSubordination,
msTTPSourceSubordination,
msTTPBidirectionalSubordination,
rsTTPSinkSubordination,
rsTTPSourceSubordination,
rsTTPBidirectionalSubordination,
sdhNESubordination,
tug2SinkSubordination,
tug2SourceSubordination,
tug2BidirectionalSubordination,
tug3SinkSubordination,
tug3SourceSubordination,
tug3BidirectionalSubordination,
vc3TTPSinkSubordination,
vc3TTPSourceSubordination,
vc3TTPBidirectionalSubordination,
vc4TTPSinkSubordination,
vc4TTPSourceSubordination,
vc4TTPBidirectionalSubordination,
FROM {ccitt(0) recommendation(0) g(7) g774(774)}
;
END
Page 13
ETS 300 304: February 1997
6.6 SDH TP - constraints
BEGIN
IMPORTS
downstreamConnectivityPointer-au4CTPSink,
upstreamConnectivityPointer-au4CTPSource,
downstreamConnectivityPointer-msCTPSink,
upstreamConnectivityPointer-msCTPSource,
upstreamConnectivityPointer-msTTPSink,
downstreamConnectivityPointer-msTTPSource,
downstreamConnectivityPointer-rsCTPSink,
upstreamConnectivityPointer-rsCTPSource,
upstreamConnectivityPointer-rsTTPSink,
downstreamConnectivityPointer-rsTTPSource,
downstreamConnectivityPointer-tu11CTPSink,
upstreamConnectivityPointer-tu11CTPSource,
downstreamConnectivityPointer-tu12CTPSink,
upstreamConnectivityPointer-tu12CTPSource,
downstreamConnectivityPointer-tu2CTPSink,
upstreamConnectivityPointer-tu2CTPSource,
downstreamConnectivityPointer-tu3CTPSink,
upstreamConnectivityPointer-tu3CTPSource,
upstreamConnectivityPointer-vc11TTPSink,
downstreamConnectivityPointer-vc11TTPSource,
upstreamConnectivityPointer-vc12TTPSink,
downstreamConnectivityPointer-vc12TTPSource,
upstreamConnectivityPointer-vc2TTPSink,
downstreamConnectivityPointer-vc2TTPSource,
upstreamConnectivityPointer-vc3TTPSink,
downstreamConnectivityPointer-vc3TTPSource,
FROM {ccitt(0) recommendation(0) g(7) g774(774)}
;
END
ets_upstreamConnectivityPointer-vc4TTPSink CONSTRAINT RULE
OBJECT CLASS
vc4TTPSink AND SUBCLASSES;
IS RELATED TO
vc4TTPSource, vc4TTPBidirectional,
au4CTPSink, au4CTPBidirectional;
USING ATTRIBUTE
"Recommendation M.3100":upstreamConnectivityPointer;
ACCORDING TO RULE
SET SIZE (1) OF CHOICE{
vc4TTPSource, vc4TTPBidirectional,
au4CTPSink, au4CTPBidirectional};
;
ets_downstreamConnectivityPointer-vc4TTPSource CONSTRAINT RULE
OBJECT CLASS
vc4TTPSource AND SUBCLASSES;
IS RELATED TO
vc4TTPSink, vc4TTPBidirectional,
au4CTPSource, au4CTPBidirectional;
USING ATTRIBUTE
"Recommendation M.3100":downstreamConnectivityPointer;
CASE{
single ACCORDING TO RULE
SET SIZE (1) OF CHOICE{
vc4TTPSink, vc4TTPBidirectional,
au4CTPSource, au4CTPBidirectional};
;  broadcast ACCORDING TO RULE
SET SIZE (1.N) OF CHOICE{
vc4TTPSink, vc4TTPBidirectional,
au4CTPSource, au4CTPBidirectional};
}
Page 14
ETS 300 304: February 1997
7 Plesiochronous Digital Hierarchy (PDH) fragment
This clause provides managed objects required to model PDH interfaces on SDH equipment.
7.1 Object classes definitions
ITU-T Recommendation G.702 2 Mbit/s connection termination point
p12CTPSink MANAGED OBJECT CLASS
DERIVED FROM "Recommendation M.3100":connectionTerminationPointSink;
CHARACTERIZED BY
"Recommendation M.3100":createDeleteNotificationsPackage,
"Recommendation M.3100":operationalStatePackage,
"Recommendation M.3100":stateChangeNotificationPackage,
p12CTPSinkPkg PACKAGE
BEHAVIOUR
p12CTPSinkBehaviourPkg BEHAVIOUR
DEFINED AS
*This managed object class terminates a G.702 2 Mbit/s connection and includes
the lower order path adaptation function (LPA).*
;;
ATTRIBUTES
p12CTPId                 GET;
;;
REGISTERED AS { etsObjectClass 13 };
p12CTPSource MANAGED OBJECT CLASS
DERIVED FROM "Recommendation M.3100":connectionTerminationPointSource;
CHARACTERIZED BY
"Recommendation M.3100":createDeleteNotificationsPackage,
p12CTPSourcePkg PACKAGE
BEHAVIOUR
p12CTPSourceBehaviourPkg BEHAVIOUR
DEFINED AS
*This object class originates a G.702 2 Mbit/s connection*
;;
ATTRIBUTES
p12CTPId                 GET;
;;
REGISTERED AS { etsObjectClass 2 };
p12CTPBidirectional MANAGED OBJECT CLASS
DERIVED FROM "Recommendation M.3100":connectionTerminationPointBidirectional,
p12CTPSink,
p12CTPSource;
REGISTERED AS { etsObjectClass 3 };
G702 34 Mbit/s connection termination point
p31CTPSink MANAGED OBJECT CLASS
DERIVED FROM "Recommendation M.3100":connectionTerminationPointSink;
CHARACTERIZED BY
"Recommendation M.3100":createDeleteNotificationsPackage,
"Recommendation M.3100":operationalStatePackage,
"Recommendation M.3100":stateChangeNotificationPackage,
p31CTPSinkPkg PACKAGE
BEHAVIOUR
p31CTPSinkBehaviourPkg BEHAVIOUR
DEFINED AS
*This managed object class terminates a G.702 34 Mbit/s connection and includes
the lower order path adaptation function (LPA).*
;;
ATTRIBUTES
p31CTPId                 GET;
;;
REGISTERED AS { etsObjectClass 4 };
p31CTPSource MANAGED OBJECT CLASS
DERIVED FROM "Recommendation M.3100":connectionTerminationPointSource;
CHARACTERIZED BY
"Recommendation M.3100":createDeleteNotificationsPackage,
p31CTPSourcePkg PACKAGE
BEHAVIOUR
p31CTPSourceBehaviourPkg BEHAVIOUR
DEFINED AS
*This object class originates a G.702 34Mbit/s connection.*
;;
ATTRIBUTES
Page 15
ETS 300 304: February 1997
p31CTPId                 GET;
;;
REGISTERED AS { etsObjectClass 5 };
p31CTPBidirectional MANAGED OBJECT CLASS
DERIVED FROM "Recommendation M.3100":connectionTerminationPointBidirectional,
p31CTPSink,
p31CTPSource;
REGISTERED AS { etsObjectClass 6 };
G702 140 Mbit/s connection termination point
p4CTPSink MANAGED OBJECT CLASS
DERIVED FROM "Recommendation M.3100":connectionTerminationPointSink;
CHARACTERIZED BY
"Recommendation M.3100":createDeleteNotificationsPackage,
"Recommendation M.3100":operationalStatePackage,
"Recommendation M.3100":stateChangeNotificationPackage,
p4CTPSinkPkg PACKAGE
BEHAVIOUR
p4CTPSinkBehaviourPkg BEHAVIOUR
DEFINED AS
*This managed object class terminates a G.702 140 Mbit/s connection and
includes the lower order path adaptation function (LPA).*
;;
ATTRIBUTES
p4CTPId                 GET;
;;
REGISTERED AS { etsObjectClass 7 };
p4CTPSource MANAGED OBJECT CLASS
DERIVED FROM "Recommendation M.3100":connectionTerminationPointSource;
CHARACTERIZED BY
"Recommendation M.3100":createDeleteNotificationsPackage,
p4CTPSourcePkg PACKAGE
BEHAVIOUR
p4CTPSourceBehaviourPkg BEHAVIOUR
DEFINED AS
*This object class originates a G.702 140 Mbit/s connection.*
;;
ATTRIBUTES
p4CTPId                 GET;
;;
REGISTERED AS { etsObjectClass 8 };
p4CTPBidirectional MANAGED OBJECT CLASS
DERIVED FROM "Recommendation M.3100":connectionTerminationPointBidirectional,
p4CTPSink,
p4CTPSource;
REGISTERED AS { etsObjectClass 9 };

Page 16
ETS 300 304: February 1997
7.2 Attributes definitions
supportedByObjectList
The value of the supportedByObjectList attribute points to the equipment and software objects
which implement the TPs.
G.702 2Mbit/s Connection Termination Point Identification
p12CTPId ATTRIBUTE
WITH ATTRIBUTE SYNTAX    PrETS8.NameType ;
MATCHES FOR         EQUALITY;
BEHAVIOUR
p12CTPIdBehaviour BEHAVIOUR
DEFINED AS
This attribute is used as an RDN for naming instances of the p12CTP object classes.
;;
REGISTERED AS { etsAttribute 1 };
G.702 34Mbit/s Connection Termination Point Identification
p31CTPId ATTRIBUTE
WITH ATTRIBUTE SYNTAX    PrETS8.NameType ;
MATCHES FOR         EQUALITY;
BEHAVIOUR
p31CTPIdBehaviour BEHAVIOUR
DEFINED AS
This attribute is used as an RDN for naming instances of the p31CTP object classes.
;;
REGISTERED AS { etsAttribute 2 };
G.702 140Mbit/s Connection Termination Point Identification
p4CTPId ATTRIBUTE
WITH ATTRIBUTE SYNTAX    PrETS8.NameType ;
MATCHES FOR         EQUALITY;
BEHAVIOUR
p4CTPIdBehaviour BEHAVIOUR
DEFINED AS
This attribute is used as an RDN for naming instances of the p4CTP object classes.
;;
REGISTERED AS { etsAttribute 3 };

Page 17
ETS 300 304: February 1997
7.3 Name bindings definitions
p12CTPSource-G774vc12TTPSource NAME BINDING
SUBORDINATE OBJECT CLASS p12CTPSource AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS  "Recommendation G.774":vc12TTPSource AND SUBCLASSES;
WITH ATTRIBUTE      p12CTPId;
BEHAVIOUR
p12CTPSource-vc12TTPSource BEHAVIOUR
DEFINED AS
The subordinate managed object may be automatically instantiated when the superior managed
object is instantiated, according to the make-up and mode of operation of the equipment.
;;
REGISTERED AS { etsNameBinding 20 };
p12CTPSink-G774vc12TTPSink NAME BINDING
SUBORDINATE OBJECT CLASS p12CTPSink AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS  "Recommendation G.774":vc12TTPSink AND SUBCLASSES;
WITH ATTRIBUTE      p12CTPId;
BEHAVIOUR
p12CTPSink-vc12TTPSink BEHAVIOUR
DEFINED AS
The subordinate managed object may be automatically instantiated when the superior managed
object is instantiated, according to the make-up and mode of operation of the equipment.
;;
REGISTERED AS { etsNameBinding 21 };
p31CTPSource-G774vc3TTPSource NAME BINDING
SUBORDINATE OBJECT CLASS p31CTPSource AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS  "Recommendation G.774":vc3TTPSource AND SUBCLASSES;
WITH ATTRIBUTE      p31CTPId;
BEHAVIOUR
p31CTPSource-vc3TTPSource BEHAVIOUR
DEFINED AS
The subordinate managed object may be automatically instantiated when the superior managed
object is instantiated, according to the make-up and mode of operation of the equipment.
;;
REGISTERED AS { etsNameBinding 22 };
p31CTPSink-G774vc3TTPSink NAME BINDING
SUBORDINATE OBJECT CLASS p31CTPSink AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS  "Recommendation G.774":vc3TTPSink AND SUBCLASSES;
WITH ATTRIBUTE      p31CTPId;
BEHAVIOUR
p31CTPSink-vc3TTPSink BEHAVIOUR
DEFINED AS
The subordinate managed object may be automatically instantiated when the superior managed
object is instantiated, according to the make-up and mode of operation of the equipment.
;;
REGISTERED AS { etsNameBinding 23 };
p4CTPSource-G774vc4TTPSource NAME BINDING
SUBORDINATE OBJECT CLASS p4CTPSource AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS  "Recommendation G.774":vc4TTPSource AND SUBCLASSES;
WITH ATTRIBUTE      p4CTPId;
BEHAVIOUR
p4CTPSource-vc4TTPSource BEHAVIOUR
DEFINED AS
The subordinate managed object may be automatically instantiated when the superior managed
object is instantiated, according to the make-up and mode of operation of the equipment.
;;
REGISTERED AS { etsNameBinding 24 };
p4CTPSink-G774vc4TTPSink NAME BINDING
SUBORDINATE OBJECT CLASS p4CTPSink AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS  "Recommendation G.774":vc4TTPSink AND SUBCLASSES;
WITH ATTRIBUTE      p4CTPId;
BEHAVIOUR
p4CTPSink-vc4TTPSink BEHAVIOUR
DEFINED AS
The subordinate managed object may be automatically instantiated when the superior managed
object is instantiated, according to the make-up and mode of operation of the equipment.
;;
REGISTERED AS { etsNameBinding 25 };

Page 18
ETS 300 304: February 1997
7.4 ASN.1 definitions
PrETS8{ccitt(0) identified-organization(4) etsi(0) ets304(304) informationModel(0) asn1Module(2)
prETS8(1)}
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
-- EXPORTS everything
IMPORTS
NameType FROM ASN1DefinedTypesModule {ccitt(0) recommendation(0) m(13) m3100(3100)
informationModel(0) asn1Module(2) asn1DefinedTypesModule(0)}
END -- end of ASN1DefinedTypesModule
8 Cross-connection fragment
8.1 Cross-connection - object classes
In this context the IMPORTS clause specifies the object classes which can be instantiated in the scope of
this ETS. The IMPORTS clause does not include uninstantiated superclasses.
BEGIN
IMPORTS
crossConnection,
fabric,
gtp,
mpCrossConnection,
tpPool
FROM {ccitt(0) recommendation(0) m(13) m3100(3100) informationModel(0) managedObjectClass(3) }
;
END
8.2 Cross-connection - packages
All packages associated with object classes are implicitly imported from ITU-T Recommendations defining
the appropriate object classes.
8.3 Cross-connection - attributes
All attributes associated with object classes are implicitly imported from ITU-T Recommendations defining
the appropriate object classes.
supportedByObjectList
The value of the supportedByObjectList attribute points to the equipment and software
objects which implement the TPs.

Page 19
ETS 300 304: February 1997
8.4 Cross-connection - name bindings
BEGIN
IMPORTS
fabric-managedElement,
gtp-fabric,
mpCrossConnection-fabric,
tpPool-fabric
FROM {ccitt(0) recommendation(0) m(13) m3100(3100) informationModel(0) nameBinding(6) }
;
END
etsCrossConnection-fabric NAME BINDING
SUBORDINATE OBJECT CLASS "Recommendation M.3100" : crossConnection
AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS  "Recommendation M.3100":fabric
AND SUBCLASSES;
WITH ATTRIBUTE      "Recommendation M.3100":crossConnectionId;
BEHAVIOUR
etsCrossConnection-fabricBehaviour BEHAVIOUR
DEFINED AS
*The value of the fromTermination attribute in the crossConnection object shall not be NULL. When
an instance of crossConnection is deleted, the following attributes will be affected. The
crossConnectionObjectPointer attributes in the termination points or in the gtp objects that were
pointing to the deleted crossConnection instance shall be set to point to the Fabric responsible
for the connection of the termination points. The counters in the appropriate TP Pool objects (if
applicable) shall be updated. The connectivityPointer attributes in the disconnected termination
points shall be set to NULL. Deleting a crossConnection object instance has no effect on the
composition of any GTP*
;;
REGISTERED AS {etsNameBinding 16 };
etsCrossConnection-mpCrossConnection NAME BINDING
SUBORDINATE OBJECT CLASS "Recommendation M.3100":crossConnection
AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS  "Recommendation M.3100":mpCrossConnection
AND SUBCLASSES;
WITH ATTRIBUTE      "Recommendation M.3100":crossConnectionId;
BEHAVIOUR
etsCrossConnection-mpCrossConnectionBehaviour BEHAVIOUR
DEFINED AS
*The value of the fromTermination attribute in the crossConnection object must be NULL. When an
instance of crossConnection is deleted, the following attributes will be affected. The
crossConnectionObjectPointer attributes in the termination points or in the gtp objects that were
pointing to the deleted crossConnection instance shall be set to point to the Fabric responsible
for the connection of the termination points. The counters in the appropriate TP Pool objects (if
applicable) shall be updated. The connectivityPointer attributes in the disconnected termination
points shall be set to NULL. Deleting the last cross-Connection contained in a multipoint cross
connection object has the effect of also deleting the multipoint cross connection object instance
(and updating the appropriate pointers). Deleting a crossConnection object instance has no effect
on the composition of any GTP*
;;
REGISTERED AS {etsNameBinding 17 };

Page 20
ETS 300 304: February 1997
9 Protection fragment
The protection fragment information model is to be found in ITU-T Recommendation G.774.03 [3].
9.1 Object classes
In this context the IMPORTS clause specifies the object classes which can be instantiated in the scope of
this ETS. The IMPORTS clause does not include uninstantiated superclasses.
BEGIN
IMPORTS
protectedTTPBidirectional
protectedTTPSink
protectedTTPSource
protectionGroup
protectionUnit
sdhMSProtectionGroup
sdhMSProtectionUnit
unprotectedCTPBidirectional
unprotectedCTPSink
unprotectedCTPSource
FROM {ccitt(0) recommendation(0) g(7) g774(774) hyphen(127) prot(03) informationModel(0)
managedObjectClass(3) }
;
END
9.2 Packages
All packages associated with object classes are implicitly imported from ITU-T Recommendations defining
the appropriate object classes.
9.3 Attributes
All attributes associated with object classes are implicitly imported from ITU-T Recommendations defining
the appropriate object classes.
supportedByObjectList
The value of the supportedByObjectList attribute points to the equipment and software
objects which implement the TPs.
9.4 Name bindings
BEGIN
IMPORTS
protectedTTPBidirectional-sdhNE
protectedTTPSink-sdhNE
protectedTTPSource-sdhNE
augBidirectional-protectedTTPBidirectional
augSink-protectedTTPSink
augSource-protectedTTPSource
protectionGroup-managedElement
protectionUnit-protectionGroup
unprotectedCTPBidirectional-msTTPBidirectional
unprotectedCTPSink-msTTPSink
unprotectedCTPSource-msTTPSource
FROM {ccitt(0) recommendation(0) g(7) g774(774) hyphen(127) prot(03) informationModel(0)
nameBinding(6) }
;
END
Page 21
ETS 300 304: February 1997
10 Equipment fragment
10.1 Equipment - object classes
In this context, the IMPORTS clause specifies the object classes which can be instantiated in the scope of
this ETS. The IMPORTS clause does not include uninstantiated superclasses.
BEGIN
IMPORTS
sdhNE
FROM {ccitt(0) recommendation(0) g(7) g774(774) informationModel(0) managedObjectClass(3) }
software
FROM M.3100ObjectClass {ccitt(0) recommendation(0) m(13) m3100(3100) informationModel(0)
managedObjectClass(3) }
;
END
The external TimePackage shall be supported by the sdhNE instance.
equipmentProtectionGroup MANAGED OBJECT CLASS
DERIVED FROM ”Recommendation G.774-03: 1994”:protectionGroup;
CHARACTERIZED BY
equipmentProtectionGroupPkg PACKAGE
BEHAVIOUR equipmentProtectionGroupBeh;
NOTIFICATIONS
”Recommendation G.774-03: 1994”: protectionSwitchReporting
equipmentProtectionStatusParameter;;;
REGISTERED AS { etsObjectClass 14 };
equipmentProtectionGroupBeh BEHAVIOUR
DEFINED AS
” This object class is used specifically for representing an equipment protection group in a
protection system.
The invokeProtection action switches always from protectedUnit to protectingUnit.
Either no or all equipmentProtectionUnits within an equipmentProtectionGroup shall have the
priorityPkg package.”;
equipmentProtectionUnit MANAGED OBJECT CLASS
DERIVED FROM ”Recommendation G.774-03: 1994”:protectionUnit;
CHARACTERIZED BY
”Recommendation M.3100: 1992”:createDeleteNotificationsPackage,
equipmentProtectionUnitPkg PACKAGE
BEHAVIOUR equipmentProtectionUnitBeh;
ATTRIBUTES
equipmentProtectionStatus GET;;;
REGISTERED AS { etsObjectClass 15 };
equipmentProtectionUnitBeh BEHAVIOUR
DEFINED AS
” This object class is specific to equipment protection systems. Instances of this object class
are used to represent a relationship between a functional object and an equipment.
equipmentProtectionUnits are self-instanciated by the agent according to the equipment protection
schemes adopted by the NE. An equipmentProtectionUnit instance is deleted when the sdhEquipment
instance pointed to by the unreliableResourcePointer attribute are deleted, and is created again
if the sdhEquipment are instantiated with the appropriate equipmentExpected attribute value.
The reliableResourcePointer inherited by the protectionUnit superclass can be optionally an empty
set for instances of this object class.
The agent can also create and delete instances of the equipmentProtectionUnit in order to reflect
local modifications in the equipment protection schemes.
The attributeValueChange notification shall only be used to notify changes of the priority
attribute.”;
sdhEquipmentR MANAGED OBJECT CLASS
DERIVED FROM "Recommendation M.3100":equipment;
CHARACTERIZED BY
"Recommendation M.3100":administrativeOperationalStatesPackage,
"Recommendation M.3100":attributeValueChangeNotificationPackage,
"Recommendation M.3100":createDeleteNotificationsPackage,
"Recommendation M.3100":currentProblemListPackage,
"Recommendation M.3100":locationNamePackage,
"Recommendation M.3100":stateChangeNotificationPackage,
"Recommendation M.3100":equipmentEquipmentAlarmPackage,
"Recommendation X.721":availabilityStatusPackage,
sdhEquipmentPackage PACKAGE
BEHAVIOUR
sdhEquipmentBehaviour BEHAVIOUR
DEFINED AS
Page 22
ETS 300 304: February 1997
* The equipment object may be instantiated or exist without the presence of the physical
resources. In this case the operational state shall be "disabled" and the availability status
attribute shall contain the value "notInstalled".
When the resource is physically removed, the corresponding equipment object is not automatically
deleted.
The equipmentExpected attribute shall be provided at instantiation time. The create request shall
fail if the value of this attribute is unacceptable to the NE, and the failure reason shall
indicate this mismatch in the response.
When there is a mismatch in the contents of the equipmentActual and the equipment Expected
attribute, an equipmentAlarm notification with probable cause "replaceableUnitTypeMis
match" shall be raised. This checking is only performed if the availabilityStatus does not
contain the value "notInstalled". The equipmentExpected value of "NULL" (no type) does not match
any other value than NULL for equipmentActual. Changes in the value of the equipmentExpected
attribute can only be achieved by object deletion and creation.
The "Recommendation M.3100":versionPackage package is not used.
The protectionUnitPointer at
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...