SIST ETS 300 412 E1:2003

• Abstract:

  Define the capabilities to configure under management operations the multiplexing structure in SDH Network elements

• 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 412 ed.1 (1995-05) - Transmission and Multiplexing (TM); Payload configuration; Information model for the Network Element (NE) view

SIST ETS 300 412 E1:2003 is the Slovenian adoption of ETS 300 412 Edition 1 from ETSI. It defines an information model for payload configuration management in Synchronous Digital Hierarchy (SDH) network elements (NEs), so it tells management systems and equipment vendors which managed objects, actions, parameters and bindings are used at the NE view.

What does SIST ETS 300 412 E1:2003 specify?

SIST ETS 300 412 E1:2003 specifies the information model for configuring SDH payload structure in the network element view. It is about the management information needed to describe and control payload configuration inside the equipment domain seen from the element manager - element interface.

The standard is organized into:

• Clause 1 - scope
• Clause 2 - normative references
• Clause 3 - abbreviations
• Clause 4 - payload configuration management model
• Clause 5 - managed object class definitions
• Clause 6 - packages
• Clause 7 - attributes
• Clause 8 - actions
• Clause 9 - notifications
• Clause 10 - parameters
• Clause 11 - name bindings
• Clause 12 - subordination and connectivity pointer constraints rules
• Annex A - bibliography

Annex A is informative and gives background references rather than additional requirements.

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

SIST ETS 300 412 E1:2003 focuses on the management objects and relationships needed to configure SDH payload structure in an NE. In practice, it tells implementers which objects, actions and bindings belong to the NE-facing management model and which parts are delegated to ITU-T G.774.2.

Scope of the management model

Clause 1 limits the model to payload configuration management for SDH NEs. It is concerned with information available within the equipment domain visible at the element manager - element interface, which matters because it keeps NE management separate from network-level management.

Managed object classes

Clause 5 imports only the object classes that can be instantiated in the scope of this ETS, including the modifiable TUG and VC classes in source, sink and bidirectional forms. For implementers, this means the standard identifies the manageable payload structures rather than defining a generic object model.

Actions and parameters

Clause 8 imports actions such as defineVC4Structure, defineTug3Structure, defineTug2Structure and defineClientType, and clause 10 imports defineSDHStructureError. These names show that the model supports configuring SDH structure and reporting structure-related errors during management operations.

Name bindings and termination points

Clause 11 imports name bindings for rs, ms, electrical, optical, datacom, orderwire and user-channel CTPs, plus TTPs and VC-related bindings. In practice, this is what links the payload configuration model to the actual termination points in the NE.

Constraints and hierarchy

Clause 12 points to G.774.2 for connectivity pointer constraints rules and subordination rules. That matters because payload configuration is not just a list of objects - it also has defined containment and connectivity relationships that management systems must respect.

What is not defined here

The scope explicitly leaves out the protocol stack for message communication, network-level management processes, application contexts, conformance requirements and information models for other systems or equipment. This keeps the ETS limited to the NE information model itself.

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

• NE - Network Element, the SDH equipment whose payload configuration is being managed.
• SDH - Synchronous Digital Hierarchy, the transmission hierarchy to which the model applies.
• TMN - Telecommunication Management Network, the management architecture used for exchanging management information.
• CTP - Connection Termination Point, a managed point where a connection terminates.
• TTP - Trail Termination Point, a managed point where a trail terminates.
• TUG - tributary unit group, a grouping used in SDH payload structure.
• VCn - Virtual Container n, a family of SDH virtual containers used in the payload model.

Who uses SIST ETS 300 412 E1:2003?

SDH network operators use SIST ETS 300 412 E1:2003 to model payload configuration in network elements. Equipment manufacturers and system integrators use it when implementing the NE management view, especially the managed object classes, actions and name bindings.

Quality and test teams use it to check that management interfaces present the expected SDH configuration objects and relationships. It is also relevant to engineers working on element managers and TMN-based management applications.

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

The normative references are:

• CCITT Recommendation M.3010 - provides the TMN principles that frame the management architecture.
• ITU-T Recommendation G.774.2 - provides the detailed SDH payload configuration model, including the requirements, connectivity pointer constraints rules and subordination rules that this ETS relies on.

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

SIST ETS 300 412 E1:2003 is an information-model standard rather than a procedure or test document. Its main content is a structured set of imported managed object classes, actions, parameters and name bindings taken from the SDH management information model.

The most technical material is concentrated in clauses 5, 8, 10 and 11, where the model names the objects and relationships used for payload configuration. Clause 12 then points to the rule sets that control how those objects relate to each other.

Annex A provides bibliography entries for related SDH, management and ASN.1/OSI standards. For a reader implementing or checking NE management, the useful takeaway is the object model and its bindings, not tables of values or worked examples.

SLOVENSKI STANDARD
01-december-2003
Prenos in multipleksiranje (TM) – Informacijski model za konfiguracijo koristnega
signala, gledano s strani omrežnega elementa (NE)
Transmission and Multiplexing (TM); Payload configuration; Information model for the
Network Element (NE) view
Ta slovenski standard je istoveten z: ETS 300 412 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 412
TELECOMMUNICATION May 1995
STANDARD
Source: ETSI TC-TM Reference: DE/TM-02217
ICS: 33.080
Information model, NE
Key words:
Transmission and Multiplexing (TM);
Payload configuration 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 1995. All rights reserved.
New presentation - see History box

Page 2
ETS 300 412: May 1995
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 412: May 1995
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Abbreviations.8
4 Payload configuration management model.8
5 Managed object class definitions .8
6 Packages.8
7 Attributes .8
8 Actions.8
9 Notifications.9
10 Parameters.9
11 Name bindings .9
12 Subordination, connectivity pointer constraints rules .10
Annex A (informative): Bibliography.11
History.12

Page 4
ETS 300 412: May 1995
Blank page
Page 5
ETS 300 412: May 1995
Foreword
This European Telecommunication Standard (ETS) has been 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) for the payload configuration.
Proposed transposition dates
Date of latest announcement of this ETS (doa): 31 August 1995
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 August 1995
Date of withdrawal of any conflicting National Standard (dow): 29 February 1996

Page 6
ETS 300 412: May 1995
Blank page
Page 7
ETS 300 412: May 1995
1 Scope
This European Telecommunication Standard (ETS) provides an information model for the payload
configuration management of Synchronous Digital Hierarchy (SDH) networks. This model describes the
managed object classes and their properties for the payload configuration function as related to SDH
Network Elements (NEs). These objects are useful to describe information exchanged across interfaces
defined in CCITT Recommendation M.3010 [1] Telecommunications Management Network (TMN)
architecture for the management of the payload configuration function.
This ETS defines:
- an information model, as related to the payload configuration for the SDH.
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 element
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 with
...