ETSI EN 300 820-1 V1.1.1 (1998-07)

SLOVENSKI STANDARD
SIST EN 300 820-1 V1.1.1:2005
01-julij-2005
2PUHåQLYLGLNL1$,QIRUPDFLMVNLPRGHOXSUDYOMDQMDDVLQKURQHJDSUHQRVQHJD
QDþLQD$70]DYPHVQLN;PHGREUDWRYDOQLPLVLVWHPL26RPUHåMDV
SUHYH]RYDQMHPQDYLGH]QHSRWL93QDYLGH]QHJDNDQDOD9&GHO9LGLNL
XSUDYOMDQMDNRQILJXUDFLMH"""
Telecommunications Management Network (TMN); Management information model for
the X-type interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual
Channel (VC) cross connected network; Part 1: Configuration management aspects
Ta slovenski standard je istoveten z: EN 300 820-1 Version 1.1.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST EN 300 820-1 V1.1.1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST EN 300 820-1 V1.1.1:2005

---------------------- Page: 2 ----------------------

SIST EN 300 820-1 V1.1.1:2005
EN 300 820-1 V1.1.1 (1998-07)
European Standard (Telecommunications series)
Network Aspects (NA);
Management information model for the X-type
interface between Operation Systems (OSs)
of a Virtual Path (VP)/Virtual Channel (VC)
cross connected network;
Part 1: Configuration management aspects

---------------------- Page: 3 ----------------------

SIST EN 300 820-1 V1.1.1:2005
2 EN 300 820-1 V1.1.1 (1998-07)
Reference
DEN/NA-052212-1 (7lc90ico.PDF)
Keywords
ATM, B-ISDN, management, TMN
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Internet
secretariat@etsi.fr
http://www.etsi.fr
http://www.etsi.org
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 1998.
All rights reserved.
ETSI

---------------------- Page: 4 ----------------------

SIST EN 300 820-1 V1.1.1:2005
3 EN 300 820-1 V1.1.1 (1998-07)
Contents
Intellectual Property Rights.6
Foreword .6
1 Scope.7
2 Normative references .7
3 Definitions and abbreviations .8
3.1 Definitions . 8
3.2 Abbreviations. 9
4 Management architecture.10
4.1 X-interface at the Service Management level . 10
4.2 Consumer/Provider . 11
4.3 Organizational model. 12
4.4 Responsibility of PNOs regarding a VP / VC connection. 13
4.4.1 Examples of application of the responsibility rules. 13
5 General overview of the X-interface specification .14
6 Requirements .14
6.1 General requirements. 14
6.2 Configuration management requirements . 15
7 Management services.16
7.1 Management services. 16
7.2 Management Service Components (MSC). 16
7.2.1 Establish MSC. 16
7.2.2 Release MSC. 17
7.2.3 Modification MSC . 18
7.2.4 Reconfiguration MSC. 18
7.2.5 Continuity Check MSC . 19
7.3 Management Functions (MF). 20
7.3.1 Activate Change . 20
7.3.2 Activate VP / VC Subnetwork Connection . 20
7.3.3 Cancel Change. 20
7.3.4 Release VP / VC Subnetwork Connection . 20
7.3.5 Change Reservation. 21
7.3.6 Check Available Cell Rate . 21
7.3.7 Deactivate VP / VC Subnetwork Connection. 22
7.3.8 Destination User Checking. 22
7.3.9 Reserve VP / VC Subnetwork Connection. 23
7.3.10 Topology Info Changes. 23
7.3.11 Cancel VP / VC Subnetwork Connection. 24
7.3.12 Activate Bidirectional Continuity Monitor Sink for Continuity Check . 24
7.3.13 Allow F4 flow . 25
7.3.14 Create Bidirectional Continuity Monitor for Continuity Check . 25
7.3.15 Deactivate Bidirectional Continuity Monitor Sink for Continuity Check . 26
7.3.16 Delete Bidirectional Continuity Monitor. 26
7.3.17 Notification of Bidirectional Continuity Monitor Operational State Change. 26
7.3.18 Report of Continuity Check. 26
7.3.19 Stop F4 flow. 27
8 Management information model.27
8.1 Introduction. 27
8.2 Inheritance tree . 28
8.3 Entity relationship diagram. 29
8.4 I-ETS 300 653 and ITU-T Recommendation I.751 Object Classes adapted for the X . 29
8.4.1 Connectivity . 29
ETSI

---------------------- Page: 5 ----------------------

SIST EN 300 820-1 V1.1.1:2005
4 EN 300 820-1 V1.1.1 (1998-07)
8.4.2 Subnetwork Connection . 30
8.4.3 Network TP. 31
8.4.4 Network CTP Sink . 32
8.4.5 Network CTP Source . 32
8.4.6 Network CTP Bi-directional . 32
8.4.7 Admin Domain. 32
8.4.8 Subnetwork Pair . 33
8.4.9 Sub-Network . 33
8.4.10 bidirectionalContinuityMonitor. 34
8.5 ATM VP X Object Classes. 35
8.5.1 Introduction. 35
8.5.2 VP Connection Fragment . 37
8.5.3 VP Connection Termination Point Fragment . 38
8.5.4 Topology Fragment. 39
8.5.5 Continuity Check Fragment. 40
8.6 Package Definitions . 40
8.6.1 Attribute Value Change Notification Package. 40
8.6.2 Create Delete Notification Package. 40
8.6.3 State Change Notification Package . 40
8.6.4 TMN Communication Alarm Information Package . 40
8.6.5 cancelVpNetworkConnectionNotification Package . 40
8.6.6 vpTestStatePackage. 41
8.6.7 flowDirectionPackage . 41
8.7 Attribute Definitions . 41
8.7.1 Associated SubNetwork Pair Id . 41
8.7.2 Backward QoS Class. 41
8.7.3 Change Reservation Information. 41
8.7.4 Forward QoS Class. 42
8.7.5 Initiating Pno Subnetwork Id. 42
8.7.6 Intiating Vp Connection Id. 42
8.7.7 List of ATM Access Point Pair Resources . 42
8.7.8 Max Num VPI Bits Supported . 42
8.7.9 Operational State. 42
8.7.10 PNO NW Access Point Id . 42
8.7.11 VPCTP Id. 43
8.7.12 VP Schedulers . 43
8.7.13 vpTestState. 43
8.7.14 continuityMonitorId . 43
8.7.15 sinkCCMecanismActive. 43
8.7.16 sourceCCMechanismActive . 43
8.8 Attribute Group Definitions. 43
8.9 Parameter Definitions . 43
8.10 Notification Definitions . 44
8.10.1 Cancel VP Network Connection Notification . 44
8.11 Action Definitions. 44
8.11.1 Activate Change . 44
8.11.2 Check User. 44
8.11.3 Give Available Links. 44
8.11.4 Release PNO VP Subnetwork Connection. 45
8.11.5 Reserve PNO VP Subnetwork Connection. 45
8.11.6 controlCC. 47
8.12 Name Binding Definitions . 47
8.12.1 interPnoTopologicalSubnetworkPair-pnoVpSubnetwork . 47
8.12.2 pnoNWAtmAccessPoint-pnoVpSubnetwork . 48
8.12.3 pnoVPCTP-pnoNWAtmAccessPoint. 48
8.12.4 pnoVpSubnetworkConnection-pnoVpSubnetwork . 48
8.12.5 pnoBidirectionalContinuityMonitor-pnoVPCTP . 48
8.13 ASN.1 Module. 49
ETSI

---------------------- Page: 6 ----------------------

SIST EN 300 820-1 V1.1.1:2005
5 EN 300 820-1 V1.1.1 (1998-07)
Annex A (informative): About the influence of timers on the X-interface communication.53
Annex B (informative): Security aspects.54
Annex C (informative): Mapping between Management Functions, CMISE Services and
ObjectClasses .55
Annex D (informative): Future organizational models.56
D.1 Responsibility of PNOs regarding a VP / VC connection .57
D.1.1 Examples of application of the responsibility rules . 57
D.2 Scenarios .59
Annex E (informative): Traffic Descriptor reference problems.63
Annex F (informative): Bibliography.65
History.66
ETSI

---------------------- Page: 7 ----------------------

SIST EN 300 820-1 V1.1.1:2005
6 EN 300 820-1 V1.1.1 (1998-07)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETR 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of
ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSI
Web server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETR 314 (or the updates on the ETSI Web server) which
are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunication series) has been produced by ETSI Technical Committee Network
Aspects (NA).
The present document is part 1 of a multi-part EN covering the management information model for the X-type interface
between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected network, as identified
below:
Part 1: "Configuration management aspects";
Part 2: "Asynchronous Transfer Mode (ATM) VP alarm management";
Part 3: "Performance management aspects".
National transposition dates
Date of adoption of this EN: 3 July 1998
Date of latest announcement of this EN (doa): 31 October 1998
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 April 1999
Date of withdrawal of any conflicting National Standard (dow): 30 April 1999
ETSI

---------------------- Page: 8 ----------------------

SIST EN 300 820-1 V1.1.1:2005
7 EN 300 820-1 V1.1.1 (1998-07)
1 Scope
The present document addresses the requirements of network, and service providers of Asynchronous Transfer Mode
(ATM) cross connected networks for establishing, maintaining and releasing Virtual Path (VP) Virtual Channel (VC)
connections, which span several administrative ATM domains. These requirements are satisfied by the use of a
standardized interface (the "X-interface") between Operation Systems (OSs) belonging to different network operators.
The present document contains a general overview describing the different management areas that will be covered in the
different X-interface ENs - configuration, fault and performance - as well as the relationships between them.
The present document describes the configuration management area covering the following aspects:
- a management architecture that shows how the X-interface is to be used between service or network providers;
- the management services and functions needed to manage ATM connections, which span several administrative
domains. These management services and functions cover the requirements for the X-interface;
- the management information crossing the X-interface. This management information specification uses the
Guidelines for the Definition of Managed Objects (GDMO) formalism, described in
ITU-T Recommendation X.722 [6].
2 Normative references
References may be made to:
a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in
which case, subsequent revisions to the referenced document do not apply; or
b) all versions up to and including the identified version (identified by "up to and including" before the version
identity); or
c) all versions subsequent to and including the identified version (identified by "onwards" following the version
identity); or
d) publications without mention of a specific version, in which case the latest version applies.
A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ITU-T Recommendation M.3100: "Generic network information model".
[2] ITU-T Recommendation X.721 | ISO 10165-2: "Information technology - Open Systems
Interconnection - Structure of management information: Definition of management information".
[3] I-ETS 300 653 (1996): "Telecommunications Management Network (TMN); Generic managed
object class library for the network level view".
[4] ITU-T Recommendation M.1400: "Designations for international networks".
[5] ITU-T Recommendation I.751 (03/96): "Asynchronous transfer mode management of the network
element view".
[6] ITU-T Recommendation X.722: "Information technology - Open Systems Interconnection -
Structure of Management information: Guidelines for the definition of managed objects".
[7] EN 300 820-2: "Telecommunications Management Networks (TMN); Management information
model for the X-type interface between Operation Systems (OSs) of a Virtual Path (VP) /
Virtual Channel (VC) cross connected network; Part 2: Fault management aspects".
ETSI

---------------------- Page: 9 ----------------------

SIST EN 300 820-1 V1.1.1:2005
8 EN 300 820-1 V1.1.1 (1998-07)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following definitions apply:
(Some definitions depend on the future acceptance of the "cascaded/mixed mode" as described in annex D. This
dependence is already taken into account in these definitions.)
A Public Network Operator (PNO): The A PNO is the PNO whose subnet is connected to the A User. The A PNO
can be the Initiating one, but this is not always the case. It is the Consumer of other PNO's parts of the VP / VC
connection.
connection: A "transport entity" which is capable of transferring information transparently between "Connection Points
(CP)". A "connection" defines the association between the "CPs" and the "CPs" delimit the "connection".
consumer and provider roles of a PNO: With respect to a particular VP / VCC, a Consumer PNO is a PNO that has
delegated the management of a VP / VC subnetwork connection plus the outgoing link connection (both shall be part of
the connection) to another PNO (being a Provider PNO). If, in future, the „cascaded/mixed" mode should be accepted
(annex D) a PNO can have both roles at once, if it is providing part of the VP / VCC (being a Provider), and at the same
time asks another PNO to provide a part of the connection (being a Consumer).
initiating Public Network Operator (PNO): The Initiating PNO is the PNO requesting for a particular ATM
connection starting in the subnetwork of the A side; It controls the overall VP / VC connection.
link connection: A "transport entity" provided by the "client/server" association. It is formed by a near-end
"adaptation" function, a server "trail" and a far-end "adaptation" function between "CPs". It can be configured as part of
the "trail management process" in the associated server layer.
link: A "topological component" which describes the fixed relationship between a "sub-network" and another "sub-
network" or "access group".
network connection: A "transport entity" formed by the series of "connections" between "termination CPs".
sub-network connection: A "transport entity" formed by a "connection" across a "sub-network" between "CPs". It can
be configured as part of the "trail management process".
VP trail
Inserts/ Inserts/
EExxtrtracactsts
Extracts
OAOAMM
OAM
cecellllss
cells
VPSC
VPLC VPSC
Administration #1 Administration #2
VPNC
VPLC: VP Link Connection
VPNC: VP Network Connection
VPSC: VPSub Network Connection
Figure 1: Functional architecture of a VPC provided by two administrations
subnetwork view: A subtree of the X-interface tree. A subnetwork view belongs to a particular PNO: The PNO at the
root of the subtree.
ETSI

---------------------- Page: 10 ----------------------

SIST EN 300 820-1 V1.1.1:2005
9 EN 300 820-1 V1.1.1 (1998-07)
sub-network: A "topological component" used to effect routing and management. It describes the potential for "sub-
network connections" across the "sub-network". It can be partitioned into interconnected "sub-networks" and "links".
Each " sub-network" in turn can be partitioned into smaller "sub-networks " and "links" and so on. A "sub-network" may
be contained within one physical node.
transit PNO: A Transit PNO is a PNO using its own subnetwork to perform its required transit part of VP / VC
connection. It has a provider role and corresponds to a leaf in the X-interface tree, not being the Z side. In the
"cascaded/mixed approach" case it can be both a Provider (where it acts as a Transit) and a Consumer (where it virtually
acts as an Initiating).
X-interface tree: With respect to a particular VP / VCC, X-interface relations exist between each Provider PNO and
their Consumer PNO. Because each Provider has exactly one Consumer, the X-interface relations between all PNOs
involved in the management of a particular VP / VCC form a tree, the X-interface relation tree.
NOTE: For a particular VP / VCC there can be several possible X-interface relation trees; the actual tree is
formed at VP / VCC setup. The root of the tree is the Initiating PNO; it uses (and via an X-interface
controls) t
...