SIST ETS 300 304 E1:2003

• Abstract:

  An information model which describes in object-oriented terms a model (utilising ISO templates) for management of both plesiochronous and synchronous digital transmission systems. Phase 1: alarm and performance aspects

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.040.20 - Transmission systems
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI ETS 300 304 ed.1 (1994-11) - Transmission and Multiplexing (TM); Synchronous Digital Hierarchy (SDH) information model for the Network Element (NE) view

SIST ETS 300 304 E1:2003 is the Slovenian adoption of ETS 300 304 Edition 1 from ETSI. It defines an object-oriented information model for managing Synchronous Digital Hierarchy (SDH) network elements, and it also covers plesiochronous digital transmission in the same management view. The model is aimed at the interface between Network Elements (NEs) and management systems, with Phase 1 focused on alarm and performance aspects.

What does SIST ETS 300 304 E1:2003 specify?

SIST ETS 300 304 E1:2003 specifies the information model to be used at the NE-to-management-system interface for SDH NEs. It is written as an object-oriented model using ISO templates and is scoped to the equipment domain visible at the element manager to NE interface.

The standard explicitly leaves out the protocol stack, network-level management processes, application contexts, implementation conformance requirements, and information models for other systems or equipment. In practice, that means it tells implementers what the managed objects are and how they relate, but not how the messages are carried or how the wider TMN is organized.

Annex	What it covers
A	Figures showing inheritance, naming, protection, timing, and example relationships between object classes and transmission functions
B	Mapping of G.783 defects to probable causes in M.3100 or X.721
C	Bibliography

The document is organized into clauses for scope, normative references, abbreviations, ASN.1 registration, and then fragments for generic objects, SDH TP, PDH, cross-connection, protection, equipment, and support objects.

What are the key requirements of SIST ETS 300 304 E1:2003?

Model structure and shared management vocabulary

Clause 4 registers the ASN.1 object identifiers for the information model modules. In practice, this gives the managed objects, attributes, name bindings and notifications a common registration basis so that management systems can reference them consistently.

Clause 5 reuses generic object classes such as alarmRecord, log, eventForwardingDiscriminator, objectCreationRecord, objectDeletionRecord and stateChangeRecord from the X.700 series. That matters because alarms, logs and state changes can be handled in the same way across different managed-object families.

SDH transport objects

Clause 6 defines the SDH TP fragment, including object classes, packages, attributes, name bindings, subordination rules and constraints. It covers AU, MS, RS, TU, TUG, VC and user-channel objects in source, sink and bidirectional forms, which is the core of the SDH transport model.

Clause 6.3 says the supportedByObjectList attribute points to the equipment and software objects that implement the TPs. In practice, this lets an operator or management system trace a termination point back to the physical or software resources that realize it.

Clause 6.6 adds connectivity pointer constraints. For example, the relationships between upstream and downstream connectivity pointers are controlled for specific TTP and CTP classes, so implementers must preserve the correct connection direction and association logic.

PDH interfaces on SDH equipment

Clause 7 provides managed objects for PDH interfaces on SDH equipment. It defines 2 Mbit/s, 34 Mbit/s and 140 Mbit/s connection termination point classes, with identification attributes used as relative distinguished names (RDNs).

For the 2 Mbit/s sink object, the behaviour text states that a communicationsAlarm is issued when Loss Of Frame (LOF) is detected in SDH byte-synchronous mapping. In practice, that tells the manager when the object is expected to raise an alarm and what probable cause to record.

Cross-connections and protection

Clause 8 defines the crossConnection, fabric, gtp, mpCrossConnection and tpPool fragments. It also states what happens when a crossConnection instance is deleted: pointers are redirected, counters are updated where relevant, and disconnected termination points are cleared.

Clause 9 brings in the protection fragment from Draft ITU-T Recommendation G.774.03 and defines protected and unprotected termination points, protectionGroup and protectionUnit. This gives the model for multiplex-section protection and how protected resources are related to the SDH NE.

Equipment and support objects

Clause 10 defines sdhEquipment and its key attributes, including equipmentExpected, equipmentActual, specificPhysicalInstance and physicalConnectorList. This matters in practice for inventory matching, physical identification, connector tracing and mismatch alarm handling.

Clause 11 defines powerSupply and timingGenerator. It models power feeds and clock-source selection, including the currentTimingSourcePointer and poweredEquipmentPtrList attributes, so a management system can track which equipment is powered and which timing source is active.

What terms does SIST ETS 300 304 E1:2003 define?

• Synchronous Digital Hierarchy (SDH) - The multiplexing structure used by the standard for transport-network management.
• Network Element (NE) - The managed node or piece of network equipment at the interface to management systems.
• Connection Termination Point (CTP) - A managed object that represents the endpoint of a connection in the transport model.
• Trail Termination Point (TTP) - A managed object that represents the termination of a trail in the SDH hierarchy.
• Plesiochronous Digital Hierarchy (PDH) - The lower-rate digital transmission family whose interfaces are modelled on SDH equipment.
• Telecommunication Management Network (TMN) - The management environment in which these objects and interfaces are used.
• Common Management Information Protocol (CMIP) - The management protocol family referenced by the normative material for object management.
• Common Management Information Service (CMIS) - The service model used with CMIP for management interactions.

Who uses SIST ETS 300 304 E1:2003?

SIST ETS 300 304 E1:2003 is used by telecom equipment vendors, NE software developers, and management-system integrators who need a common SDH object model. It is also useful for operations and assurance teams that have to interpret alarms, performance objects, equipment mismatch conditions, cross-connections, protection states, and timing or power relationships.

Quality managers and buyers use it to check whether an SDH management implementation models the right NE functions, especially when they need inventory, alarm, protection or transport-layer visibility across mixed SDH and PDH equipment.

What changed in SIST ETS 300 304 E1:2003 from the previous edition?

SIST ETS 300 304 E1:2003 corresponds to ETS 300 304 Edition 1. The document history identifies the first edition in November 1994 and a later PDF conversion in December 1995.

Which standards are used with SIST ETS 300 304 E1:2003?

• X.701 - gives the OSI systems management overview.
• X.710 and X.711 - provide the CMIS and CMIP service and protocol base.
• X.720, X.721 and X.722 - provide the management information model, definition of managed objects, and guidance for defining them.
• X.730, X.731, X.733, X.734 and X.735 - provide object, state, alarm, event report and log control functions.
• G.774 - provides the SDH management information model that the SDH transport fragment builds on.
• G.774.03 - provides the protection fragment used for the protection model.
• M.3100 - provides the generic network information model used for cross-connection, equipment and support objects.

What does the SIST ETS 300 304 E1:2003 document contain?

The document contains ASN.1 registration modules, object-class definitions, attribute definitions, name bindings, subordination rules and constraints. It also defines PDH, cross-connection, protection, equipment and support-object fragments that describe how SDH management objects are organized and related.

Annex A adds figures for inheritance, naming and worked relationship examples, including transport-layer and protection-layer cases. Annex B provides a defect-to-probable-cause mapping for G.783-related conditions, and Annex C lists background references used to build the model.

SLOVENSKI STANDARD
01-december-2003
Prenos in multipleksiranje (TM) – Informacijski model v sistemu sinhrone digitalne
hierarhije (SDH), gledano s strani omrežnega elementa (NE)
Transmission and Multiplexing (TM); Synchronous Digital Hierarchy (SDH) information
model for the Network Element (NE) view
Ta slovenski standard je istoveten z: ETS 300 304 Edition 1
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 November 1994
STANDARD
Source: ETSI TC-TM Reference: DE/TM-02201
ICS: 33.080
SDH, NE
Key words:
Transmission and Multiplexing (TM);
Synchronous Digital Hierarchy (SDH) information model
for the Network Element (NE) view
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - [e-mail]
X.400: Internet:
Tel.: [phone] - Fax: [phone]
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 1994. All rights reserved.
New presentation - see History box

Page 2
ETS 300 304: November 1994
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: November 1994
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 TP fragment.10
6.1 SDH TP - object classes.10
6.2 SDH TP - packages.11
6.3 SDH TP - attributes.11
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 .15
7.2 Attributes definitions.17
7.3 Name bindings definitions.17
7.4 ASN.1 definitions .20
8 Cross-connection fragment.21
8.1 Cross-connection - object classes.21
8.2 Cross-connection - packages .21
8.3 Cross-connection - attributes.21
8.4 Cross-connection - name bindings .21
9 Protection fragment.22
9.1 Object classes .22
9.2 Packages .22
9.3 Attributes.22
9.4 Name bindings.23
10 Equipment fragment.23
10.1 Equipment fragment - object classes .23
10.2 Equipment - attributes.24
10.3 Equipment - name bindings .25
10.4 Equipment - supporting ASN.1 .25
11 Support objects fragment.25
11.1 Support objects - object classes.25
11.2 Support objects - attributes.26
11.3 Support objects - name bindings .27
11.4 Support objects - supporting ASN.1 .27
Annex A (informative): Figures.29
Annex B (informative): Mapping of G.783 defects on M.3100 or X.721 probable causes .44

Page 4
ETS 300 304: November 1994
Annex C (informative): Bibliography . 45
History. 46

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

Page 6
ETS 300 304: November 1994
Blank page
Page 7
ETS 300 304: November 1994
1 Scope
This European Telecommunication Standard (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 and 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] CCITT Recommendation X.701 (1992): "Information technology - Open
Systems Interconnection - Systems management overview".
[2] CCITT Recommendation X.710 (1991): "Common management information
service definition for CCITT applications".
[3] CCITT Recommendation X.711 (1991): "Common management information
protocol specification for CCITT applications".
[4] CCITT Recommendation X.731 (1992): "Information technology - Open
Systems Interconnection - Systems management: State management function".
[5] CCITT Recommendation X.730 (1992): "Information technology - Open
Systems Interconnection - Systems management: Object management
function".
[6] CCITT Recommendation X.733 (1992): "Information technology - Open
Systems Interconnection - Systems management: Alarm reporting function".
[7] CCITT Recommendation X.734 (1992): "Information technology - Open
Systems Interconnection - System management: Event report management
function".
[8] CCITT Recommendation X.735 (1992): "Information technology - Open
Systems Interconnection - System management: Log control function".

Page 8
ETS 300 304: November 1994
[9] CCITT Recommendation X.720 (1992): "Information technology - Open
Systems Interconnection - Structure management information - Part 1:
Management information model".
[10] CCITT Recommendation X.721 (1992): "Information technology - Open
Systems Interconnection - Structure of management information: Definition of
management information".
[11] CCITT Recommendation X.722 (1992): "Information technology - Open
Systems Interconnection - Structure of management information: Guidelines for
the definition of managed objects".
[12] CCITT Recommendation G.774 (1992): "Synchronous Digital Hierarchy
management information model".
[13] Draft ITU-T Recommendation G.774.03: "Synchronous digital hierarchy (SDH)
management of multiplex-section protection for the network element view".
[14] CCITT Recommendation M.3100 (1992): "Generic network information model".
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
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
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

Page 9
ETS 300 304: November 1994
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
4 Registration supporting Abstract Syntax Notation one (ASN.1)
ETS5 {ccitt(0) identified-organization(4) etsi(0) ets(304) informationModel(0)
asn1Module(2) eTS5(0)}
DEFINITIONS IMPLICIT TAGS ::= BEGIN
-- EXPORTS everything
eTS300304 OBJECT IDENTIFIER ::= {ccitt(0) identified-organization(4) etsi(0) ets(304)
informationModel(0)}
etsObjectClass OBJECT IDENTIFIER ::= {eTS300304 managedObjectClass(3)}
etsNameBinding OBJECT IDENTIFIER ::= {eTS300304 nameBinding(6)}
etsAttribute OBJECT IDENTIFIER  ::= {eTS300304 attribute(7)}
etsAction OBJECT IDENTIFIER    ::= {eTS300304 action(9)}
etsNotification OBJECT IDENTIFIER ::= {eTS300304 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 CCITT X.700 series of Recommendations.
5.1 Generic objects - object classes
In this context the IMPORTS section specifies the object classes which can be instantiated in the scope of
this ETS. The IMPORTS section 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 CCITT Recommendations defining the appropriate object classes.

Page 10
ETS 300 304: November 1994
6 SDH TP fragment
6.1 SDH TP - object classes
In this context, the IMPORTS section specifies the object classes which can be instantiated in the scope
of this ETS. The IMPORTS section does not include uninstantiated superclasses.
BEGIN
IMPORTS
au4CTPBidirectional,
au4CTPSink,
au4CTPSource,
augBidirectional,
augSink,
augSource,
electricalSPITTPBidirectional,
electricalSPITTPSink,
electricalSPITTPSource,
msCTPBidirectional,
msCTPSink,
msCTPSource,
msDatacomCTPBidirectional,
msDatacomCTPSink,
msDatacomCTPSource,
msOrderwireCTPBidirectional,
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,
Page 11
ETS 300 304: November 1994
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 CCITT Recommendations
defining the appropriate object classes.
6.3 SDH TP - attributes
All attributes associated with object classes are implicitly imported from CCITT Recommendations
defining the appropriate object classes.
supportedByObjectList
The value of the supportedByObjectList attribute points to the equipment and software objects which
implement the TPs.
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,
Page 12
ETS 300 304: November 1994
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,
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
Page 13
ETS 300 304: November 1994
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 14
ETS 300 304: November 1994
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
"CCITT Recommendation M.3100:1992":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
"CCITT Recommendation M.3100:1992":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 15
ETS 300 304: November 1994
7 Plesiochronous Digital Hierarchy (PDH) fragment
This clause provides Managed Objects required to model PDH interfaces on SDH equipment.
7.1 Object classes definitions
CCITT Recommendation G.702 2 Mbit/s connection termination point
p12CTPSink MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation M.3100:1992":connectionTerminationPointSink;
CHARACTERIZED BY
"CCITT Recommendation M.3100:1992":createDeleteNotificationsPackage,
"CCITT Recommendation M.3100:1992":operationalStatePackage,
"CCITT Recommendation M.3100:1992":stateChangeNotificationPackage,
"CCITT Recommendation M.3100:1992":tmnCommunicationsAlarmInformationPkg,
p12CTPSinkPkg PACKAGE
BEHAVIOUR
p12CTPSinkBehaviourPkg BEHAVIOUR
DEFINED AS
"This managed object class terminates a CCITT Recommendation G.702 2
Mbit/s connection and
includes the lower order path adaptation function (LPA). For
asynchronous mappings there
are no communication alarms.
In SDH byte synchronous mapping, a communicationsAlarm notification
shall be issued if a
Loss Of Frame (LOF) is detected. The probable Cause parameter of the
notification shall
indicate LOF (Loss Of Frame)."
;;
ATTRIBUTES
p12CTPId                 GET;
;;
REGISTERED AS {etsObjectClass 1};
p12CTPSource MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation M.3100:1992":connectionTerminationPointSource;
CHARACTERIZED BY
"CCITT Recommendation M.3100:1992":createDeleteNotificationsPackage,
p12CTPSourcePkg PACKAGE
BEHAVIOUR
p12CTPSourceBehaviourPkg BEHAVIOUR
DEFINED AS
"This object class originates a CCITT Recommendation G.702 2 Mbit/s
connection"
;;
ATTRIBUTES
p12CTPId                 GET;
;;
REGISTERED AS {etsObjectClass 2};
p12CTPBidirectional MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation
M.3100:1992":connectionTerminationPointBidirectional,
p12CTPSink,
p12CTPSource;
REGISTERED AS {etsObjectClass 3};
G.702 34 Mbit/s connection termination point
p31CTPSink MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation M.3100:1992":connectionTerminationPointSink;
CHARACTERIZED BY
"CCITT Recommendation M.3100:1992":createDeleteNotificationsPackage,
"CCITT Recommendation M.3100:1992":operationalStatePackage,
"CCITT Recommendation M.3100:1992":stateChangeNotificationPackage,
p31CTPSinkPkg PACKAGE
BEHAVIOUR
p31CTPSinkBehaviourPkg BEHAVIOUR
DEFINED AS
"This managed object class terminates a CCITT Recommendation G.702
34 Mbit/s connection and includes the lower order path adaptation
function (LPA)."
Page 16
ETS 300 304: November 1994
;;
ATTRIBUTES
p31CTPId                 GET;
;;
REGISTERED AS {etsObjectClass 4};
p31CTPSource MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation M.3100:1992":connectionTerminationPointSource;
CHARACTERIZED BY
"CCITT Recommendation M.3100:1992":createDeleteNotificationsPackage,
p31CTPSourcePkg PACKAGE
BEHAVIOUR
p31CTPSourceBehaviourPkg BEHAVIOUR
DEFINED AS
"This object class originates a CCITT Recommendation G.702 34 Mbit/s
connection."
;;
ATTRIBUTES
p31CTPId                 GET;
;;
REGISTERED AS {etsObjectClass 5};
p31CTPBidirectional MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation
M.3100:1992":connectionTerminationPointBidirectional,
p31CTPSink,
p31CTPSource;
REGISTERED AS {etsObjectClass 6};
G.702 140 Mbit/s connection termination point
p4CTPSink MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation M.3100:1992":connectionTerminationPointSink;
CHARACTERIZED BY
"CCITT Recommendation M.3100:1992":createDeleteNotificationsPackage,
"CCITT Recommendation M.3100:1992":operationalStatePackage,
"CCITT Recommendation M.3100:1992":stateChangeNotificationPackage,
p4CTPSinkPkg PACKAGE
BEHAVIOUR
p4CTPSinkBehaviourPkg BEHAVIOUR
DEFINED AS
"This managed object class terminates a CCITT Recommendation 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 "CCITT Recommendation M.3100:1992":connectionTerminationPointSource;
CHARACTERIZED BY
"CCITT Recommendation M.3100:1992":createDeleteNotificationsPackage,
p4CTPSourcePkg PACKAGE
BEHAVIOUR
p4CTPSourceBehaviourPkg BEHAVIOUR
DEFINED AS
"This object class originates a CCITT Recommendation G.702 140
Mbit/s connection."
;;
ATTRIBUTES
p4CTPId                 GET;
;;
REGISTERED AS {etsObjectClass 8};
p4CTPBidirectional MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation
M.3100:1992":connectionTerminationPointBidirectional,
p4CTPSink,
p4CTPSource;
REGISTERED AS {etsObjectClass 9};

Page 17
ETS 300 304: November 1994
7.2 Attributes definitions
supportedByObjectList
The value of the supportedByObjectList attribute points to the equipment and software objects which
implement the TPs.
G.702 2 Mbit/s connection termination point identification
p12CTPId ATTRIBUTE
WITH ATTRIBUTE SYNTAX    ETS8.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 34 Mbit/s connection termination point identification
p31CTPId ATTRIBUTE
WITH ATTRIBUTE SYNTAX    ETS8.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 140 Mbit/s connection termination point identification
p4CTPId ATTRIBUTE
WITH ATTRIBUTE SYNTAX    ETS8.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};
7.3 Name bindings definitions
p12CTPBidirectional-G774vc12TTPBidirectional NAME BINDING
SUBORDINATE OBJECT CLASS p12CTPBidirectional;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc12TTPBidirectional;
WITH ATTRIBUTE      p12CTPId;
BEHAVIOUR
p12CTPBidirectional-vc12TTPBidirectional 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 1};
p12CTPSink-G774vc12TTPBidirectional NAME BINDING
SUBORDINATE OBJECT CLASS p12CTPBidirectional;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc12TTPBidirectional;
WITH ATTRIBUTE      p12CTPId;
BEHAVIOUR
p12CTPSink-vc12TTPBidirectional 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."
Page 18
ETS 300 304: November 1994
;;
REGISTERED AS {etsNameBinding 2};
p12CTPSource-G774vc12TTPBidirectional NAME BINDING
SUBORDINATE OBJECT CLASS p12CTPBidirectional;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc12TTPBidirectional;
WITH ATTRIBUTE      p12CTPId;
BEHAVIOUR
p12CTPSource-vc12TTPBidirectional 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 3};
p12CTPSource-G774vc12TTPSource NAME BINDING
SUBORDINATE OBJECT CLASS p12CTPSource;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc12TTPSource;
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 4};
p12CTPSink-G774vc12TTPSink NAME BINDING
SUBORDINATE OBJECT CLASS p12CTPSink;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc12TTPSink;
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 5};

Page 19
ETS 300 304: November 1994
p31CTPBidirectional-G774vc3TTPBidirectional NAME BINDING
SUBORDINATE OBJECT CLASS p31CTPBidirectional;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc3TTPBidirectional;
WITH ATTRIBUTE      p31CTPId;
BEHAVIOUR
p31CTPBidirectional-vc3TTPBidirectional 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 6};
p31CTPSink-G774vc3TTPBidirectional NAME BINDING
SUBORDINATE OBJECT CLASS p31CTPBidirectional;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc3TTPBidirectional;
WITH ATTRIBUTE      p31CTPId;
BEHAVIOUR
p31CTPSink-vc3TTPBidirectional 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 7};
p31CTPSource-G774vc3TTPBidirectional NAME BINDING
SUBORDINATE OBJECT CLASS p31CTPBidirectional;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc3TTPBidirectional;
WITH ATTRIBUTE      p31CTPId;
BEHAVIOUR
p31CTPSource-vc3TTPBidirectional 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 8};
p31CTPSource-G774vc3TTPSource NAME BINDING
SUBORDINATE OBJECT CLASS p31CTPSource;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc3TTPSource;
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 9};
p31CTPSink-G774vc3TTPSink NAME BINDING
SUBORDINATE OBJECT CLASS p31CTPSink;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc3TTPSink;
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 10};
p4CTPBidirectional-G774vc4TTPBidirectional NAME BINDING
SUBORDINATE OBJECT CLASS p4CTPBidirectional;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc4TTPBidirectional;
WITH ATTRIBUTE      p4CTPId;
BEHAVIOUR
p4CTPBidirectional-vc4TTPBidirectional BEHAVIOUR
DEFINED AS
Page 20
ETS 300 304: November 1994
"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 11};
p4CTPSink-G774vc4TTPBidirectional NAME BINDING
SUBORDINATE OBJECT CLASS p4CTPSink;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc4TTPBidirectional;
WITH ATTRIBUTE      p4CTPId;
BEHAVIOUR
p4CTPSink-vc4TTPBidirectional 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 12};
p4CTPSource-G774vc4TTPBidirectional NAME BINDING
SUBORDINATE OBJECT CLASS p4CTPSource;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc4TTPBidirectional;
WITH ATTRIBUTE      p4CTPId;
BEHAVIOUR
p4CTPSource-vc4TTPBidirectional 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 13};
p4CTPSource-G774vc4TTPSource NAME BINDING
SUBORDINATE OBJECT CLASS p4CTPSource;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc4TTPSource;
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 14};
p4CTPSink-G774vc4TTPSink NAME BINDING
SUBORDINATE OBJECT CLASS p4CTPSink;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation G.774:1992":vc4TTPSink;
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 15};
7.4 ASN.1 definitions
ETS8 {ccitt(0) identified-organization(4) etsi(0) ets(304) informationModel(0)
asn1Module(2) eTS8(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

Page 21
ETS 300 304: November 1994
8 Cross-connection fragment
8.1 Cross-connection - object classes
In this context the IMPORTS section specifies the object classes which can be instantiated in the scope of
this ETS. The IMPORTS section 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 CCITT Recommendations
defining the appropriate object classes.
8.3 Cross-connection - attributes
All attributes associated with object classes are implicitly imported from CCITT Recommendations
defining the appropriate object classes.
supportedByObjectList
The value of the supportedByObjectList attribute points to the equipment and software objects which
implement the TPs.
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
ets_crossConnection-fabric NAME BINDING
SUBORDINATE OBJECT CLASS "CCITT Recommendation M.3100:1992":crossConnection
AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation M.3100:1992":fabric
AND SUBCLASSES;
WITH ATTRIBUTE      "CCITT Recommendation M.3100:1992":crossConnectionId;
BEHAVIOUR
ets_crossConnection-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};

Page 22
ETS 300 304: November 1994
ets_crossConnection-mpCrossConnection NAME BINDING
SUBORDINATE OBJECT CLASS "CCITT Recommendation M.3100:1992":crossConnection
AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS  "CCITT Recommendation M.3100:1992":mpCrossConnection
AND SUBCLASSES;
WITH ATTRIBUTE      "CCITT Recommendation M.3100:1992":crossConnectionId;
BEHAVIOUR
ets_crossConnection-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 ha
...