ETSI EN 301 271 V1.2.1 (2001-07)

Telecommunications Management Network (TMN); Management interfaces associated with the VB5.1 reference point;

REN/TMN-ASM005

Telekomunikacijsko upravljavno omrežje (TMN) - Upravljavni vmesniki, pridruženi referenčni točki VB5.1

General Information

• Status: Published
• Publication Date: 08-Jul-2001
• Technical Committee: TMN ASM - Access Switching Management
• Current Stage: 12 - Completion
• Due Date: 23-Jul-2001
• Completion Date: 09-Jul-2001
• Ref Project: SIST EN 301 271 V1.2.1:2003 - Telecommunications Management Network (TMN); Management interfaces associated with the VB5.1 reference point;

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN 301 271 V1.2.1:2003
01-november-2003
7HOHNRPXQLNDFLMVNRXSUDYOMDYQRRPUHåMH7018SUDYOMDYQLYPHVQLNLSULGUXåHQL
UHIHUHQþQLWRþNL9%
Telecommunications Management Network (TMN); Management interfaces associated
with the VB5.1 reference point;
Ta slovenski standard je istoveten z: EN 301 271 Version 1.2.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST EN 301 271 V1.2.1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST EN 301 271 V1.2.1:2003

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

SIST EN 301 271 V1.2.1:2003
ETSI EN 301 271 V1.2.1 (2001-07)
European Standard (Telecommunications series)
Telecommunications Management Network (TMN);
Management interfaces associated
with the VB5.1 reference point

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

SIST EN 301 271 V1.2.1:2003
2 ETSI EN 301 271 V1.2.1 (2001-07)
Reference
REN/TMN-ASM005
Keywords
ATM, configuration, management, OAM,
performance, Q3 interface, TMN,V5 interface
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: [phone] Fax: [phone]
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
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
[e-mail]
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 2001.
All rights reserved.
ETSI

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

SIST EN 301 271 V1.2.1:2003
3 ETSI EN 301 271 V1.2.1 (2001-07)
Contents
Intellectual Property Rights .6
Foreword.6
1 Scope.7
2 References.7
3 Definitions, abbreviations, and conventions .8
3.1 Definitions . 8
3.2 Abbreviations. 8
3.3 Conventions . 9
4 General Overview.9
4.1 Entity-relationship models. 10
4.1.1 Entity relationship diagram for the service node. 11
4.1.2 Entity relationship diagram for the access network. 12
4.2 Inheritance hierarchy. 13
5 Formal Definitions.13
6 Type definitions.14
7 Protocol stacks.14
Annex A (normative): Management requirements.15
A.1 General management requirements .15
A.1.1 General configuration management requirements. 15
A.2 Real-time management coordination requirements .15
A.2.1 Configuration management requirements. 15
A.2.1.1 General configuration management requirement. 15
A.2.1.2 Common configuration management requirement for AN and SN. 15
A.2.1.2.1 Shutting-down of VPs. 15
A.2.1.2.2 VB5 interface ID checking. 15
A.2.1.2.3 Handling of VB5 primitives. 15
A.2.1.2.4 Coordination of VP and VC resources. 15
A.2.1.2.5 Non B-ISDN accesses. 15
A.2.1.3 Configuration management requirement for AN . 16
A.2.1.4 Configuration management requirement for SN. 16
A.2.1.4.1 Assignment of indirect accesses . 16
A.2.1.4.2 Coordination of indirect accesses with logical user ports . 16
A.2.1.4.3 Consistency of configuration. 16
A.2.2 Fault management requirements . 16
A.2.2.1 Alarm surveillance requirements . 16
A.2.2.1.1 General alarm surveillance requirements. 16
A.2.2.1.1.1 Coordination of operational states. 16
A.2.2.2 Test and fault localization requirements. 16
A.2.2.2.1 General test and fault localization requirements. 16
A.2.2.2.1.1 Test traffic . 16
A.3 Non-real time management requirements .16
Annex B (normative): Functional architecture .17
B.1 Functional architecture associated with VB5 reference point .17
Annex C (normative): Relationship between VB5.1 interfaces and the management model .19
C.1 Introduction.19
C.2 LSP, LUP and VPCI labels .20
ETSI

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

SIST EN 301 271 V1.2.1:2003
4 ETSI EN 301 271 V1.2.1 (2001-07)
C.3 Shutting down .20
C.4 Blocking and unblocking .21
C.5 VPCI consistency checking.21
C.6 Start-up.22
C.6.1 Activation by OS. 22
C.6.2 Automatic start-up. 23
C.7 LSP identity checking.24
C.8 RTMC reset.24
Annex D (normative): State transitions .26
D.1 State transition table for AN.26
D.2 State transition table for SN .29
Annex E (informative): Clarification of the pointer relationships between the instances .31
Annex F (informative): Referenced Definitions.33
F.1 Object classes .33
F.1.1 Profiling notes for imported classes . 34
F.1.1.1 atmFabric (ATM fabric). 34
F.1.1.2 tcAdaptorTTPBidirectional (TC adapter TTP bidirectional). 34
F.1.2 Definition of classes . 34
F.1.2.1 commPathBb (communications path for broadband). 34
F.1.2.2 logicalServicePort (logical service port) . 34
F.1.2.3 lspVb51 (logical service port for VB5.1) . 35
F.1.2.4 lspVb51An (logical service port for VB5.1 in the access network) . 35
F.1.2.5 lspVb51Sn (logical service port for VB5.1 in the service node). 36
F.1.2.6 logicalUserPort (logical user port). 36
F.1.2.7 rtmcCommPathBb (RTMC communications path for broadband). 36
F.1.2.8 tcAdaptorTtpExtension (TC adaptor TTP extension).37
F.1.2.9 uniAccessVb5 (UNI access VB5). 37
F.1.2.10 vpcLup (VPC at logical user port) . 37
F.1.2.11 vpCtpBidirectionalVb5 (VP CTP bidirectional VB5).38
F.1.2.12 vpTtpBidirectionalVb5 (VP TTP bidirectional VB5) .38
F.2 Name bindings.38
F.2.1 commPathBb-logicalServicePort . 38
F.2.2 logicalServicePort-managedElementR1 . 38
F.2.3 logicalUserPort-managedElementR1. 39
F.2.4 tcAdaptorTtpExtension-tcAdaptorTTPBidirectional. 39
F.2.5 vpcLup-uniAccessVb5 . 39
F.3 Definition of packages .39
F.3.1 automaticVpciConsistencyCheckPkg (automatic VPCI consistency check package) . 39
F.3.2 checkLspIdentificationPkg (check logical service port identification package). 39
F.3.3 checkVpciConsistencyPkg (check VPCI consistency package). 40
F.3.4 partialAdministrativeStatePkg (partial administrative state package) . 40
F.3.5 remoteBlockingVb5Pkg (remote blocking VB5 package). 40
F.3.6 resetRtmcPkg (reset RTMC package) . 40
F.3.7 startupLspPkg (startup logical service port package) . 40
F.3.8 vpCtpVb5AndVpciPtrListPkg (VP CTP VB5 and VPCI pointer list package). 40
F.4 Definition of attributes.41
F.4.1 commPathBbId (communications path for broadband identifier) . 41
F.4.2 logicalServicePortId (logical service port identifier). 41
F.4.3 logicalServicePortNumber (logical service port number). 41
F.4.4 logicalServicePortPtr (logical service port pointer). 41
F.4.5 logicalUserPortId (logical user port identifier) . 42
F.4.6 logicalUserPortNumber (logical user port number) . 42
ETSI

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

SIST EN 301 271 V1.2.1:2003
5 ETSI EN 301 271 V1.2.1 (2001-07)
F.4.7 lspActivationState (logical service port activation state). 42
F.4.8 partialAdministrativeState (partial administrative state). 42
F.4.9 remoteBlockingReasonVb5 (remote blocking reason VB5). 42
F.4.10 remoteBlockingVb5 (remote blocking VB5). 43
F.4.11 tcAdaptorExtensionId (TC adaptor extension identifier). 43
F.4.12 vpcLupId (VPC at logical user port identifier). 43
F.4.13 vpcLupNumber (VPC at logical user port number). 43
F.4.14 vpCtpAndVpciPtrList (VP CTP and VPCI pointer list) .44
F.4.15 vpCtpVb5AndVpciPtrList (VP CTP VB5 and VPCI pointer list). 44
F.4.16 vpTtpAndVpciPtrList (VP TTP and VPCI pointer list). 44
F.5 Definition of actions .44
F.5.1 checkLspIdentification (check logical service port identification). 44
F.5.2 checkVpciConsistency (check VPCI consistency) . 45
F.5.3 resetRTMC (reset RTMC). 45
F.5.4 startupLsp (startup logical service port). 45
F.6 Definition of notifications .45
F.6.1 automaticVpciConsistencyCheckInitiated (automatic VPCI consistency check initiated) . 45
F.6.2 automaticVpciConsistencyCheckResult (automatic VPCI consistency check result) . 46
F.6.3 resetRtmcResult (reset RTMC Result) . 46
F.7 Type definitions.46
Annex G (informative): Bibliography.49
History .51
ETSI

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

SIST EN 301 271 V1.2.1:2003
6 ETSI EN 301 271 V1.2.1 (2001-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 ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (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 ETSI SR 000 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 (Telecommunications series) has been produced by ETSI Technical Committee
Telecommunications Management Network (TMN).
National transposition dates
Date of adoption of this EN: 6 July 2001
Date of latest announcement of this EN (doa): 31 October 2001
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 April 2002
Date of withdrawal of any conflicting National Standard (dow): 30 April 2002
ETSI

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

SIST EN 301 271 V1.2.1:2003
7 ETSI EN 301 271 V1.2.1 (2001-07)
1 Scope
The present document specifies the management interfaces (Q3 interfaces) associated with the VB5.1 reference
point [1], [2] and EN 301 217-1 (see bibliography) for the support of configuration, fault & performance management
functions. Fault and performance management together include both passive monitoring of reports and active fault
isolation.
The Q3 interface [9] is the TMN interface between network elements or Q-adapters which interface to OSs without
mediation and between OSs and mediation devices.
Existing protocols are used where possible, and the focus of the work is on defining the object model. The definition of
the functionality of TMN Operations Systems is outside the scope of the present document.
ITU-T Recommendation Q.2931 [11] is supported at the UNI, and the ATM Forum UNI is supported for compatibility
with the established base of ATM equipment.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
[1] ETSI ETR 257: "V interfaces at the digital Service Node (SN); Identification of the applicability
of existing protocol specifications for a VB5 reference point in an access arrangement with Access
Networks (ANs)".
[2] ETSI EN 301 005-1: "V interfaces at the digital Service Node (SN); Interfaces at the VB5.1
reference point for the support of broadband or combined narrowband and broadband Access
Networks (ANs); Part 1: Interface specification".
[3] Void.
[4] ITU-T Recommendation G.773: "Protocol suites for Q-interfaces for management of transmission
systems".
[5] ITU-T Recommendation G.784: "Synchronous digital hierarchy (SDH) management".
[6] ITU-T Recommendation G.902: "Framework Recommendation on functional access networks
(AN) Architecture and functions, access types, management and service node aspects".
[7] ITU-T Recommendation G.967.1 (1998): "V-interfaces at the service node (SN): VB5.1 reference
point specification".
[8] ITU-T Recommendation I.751: "Asynchronous transfer mode management of the network element
view".
[9] ITU-T Recommendation M.3010 (1996): "Principles for a telecommunications management
network".
[10] ITU-T Recommendation M.3100 (1995): "Generic network information model".
[11] ITU-T Recommendation Q.2931 (1995): "Broadband Integrated Services Digital Network
(B-ISDN) - Digital Subscriber Signalling System No. 2 (DSS 2) - User-Network Interface (UNI) -
Layer 3 specification for basic call/connection control".
ETSI

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

SIST EN 301 271 V1.2.1:2003
8 ETSI EN 301 271 V1.2.1 (2001-07)
[12] ITU-T Recommendation Q.811: "Lower layer protocol profiles for the Q3 and X interfaces".
[13] ITU-T Recommendation Q.812: "Upper layer protocol profiles for the Q3 and X interfaces".
[14] Void
[15] ITU-T Recommendation Q.824.6: "Stage 2 and stage 3 description for the Q3 interface - Customer
administration: Broadband switch management ".
[16] ITU-T Recommendation Q.832.1 (1998): "VB5.1 Management".
[17] ITU-T Recommendation Q.832.2 (1999): "VB5.2 Management".
[18] ITU-T Recommendation X.721 | ISO/IEC 10165-2 (1992): "Information technology - Open
Systems Interconnection - Structure of management information: definition of management
information".
[19] ITU-T Recommendation X.731 | ISO/IEC 10164-2 (1992): "Information technology - Open
Systems Interconnection - Systems management: State management function".
3 Definitions, abbreviations, and conventions
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ITU-T Recommendations G.902 [6] ,
G.967.1 [7] and M.3010 [9] and the following apply:
resources: management of user port functions and service port functions providing User Network Interface (UNI) and
Service Node Interface (SNI) functionality, respectively, are considered in the present document based on the
framework defined in ITU-T Recommendation G.902 [6]. Transmission specific resources lie outside the scope of this
term in the present document.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AEMF ATM Equipment Management Function
AN Access Network
ASN.1 Abstract Syntax Notation One
ATM Asynchronous Transfer Mode
GDMO Guidelines for the Definition of Managed Objects
LME Layer Management Entry
LSP Logical Service Port
LUP Logical User Port
ME Management Entry
MIB Management Information Base
MOC Managed Object Class
OAM Operations, Administration and Maintenance
OS Operations System
RTMC Real Time Management Coordination
SAAL Signalling ATM Adaptation Layer
SDH Synchronous Digital Hierarchy
SN Service Node
SNI Service Node Interface
TMN Telecommunications Management Network
TTP Trail Termination Point
UNI User-Network Interface
VC Virtual Channel
VP Virtual Path
VPC Virtual Path Connection
ETSI

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

SIST EN 301 271 V1.2.1:2003
9 ETSI EN 301 271 V1.2.1 (2001-07)
VPCI Virtual Path Connection Identifier
3.3 Conventions
Objects and their characteristics and associated ASN.1 defined here are given names with capitals used to indicate the
start of the next word, and acronyms are treated as if they were words.
Throughout the present document, all new attributes are named according to the following guidelines:
- the name of an attribute ends in the string "Ptr" if and only the attribute value is intended to identify a single
object;
- the name of an attribute ends in the string "PtrList" if and only the attribute value is intended to identify one or
more objects;
- the name of an attribute is composed of the name of an object class followed by the string "Ptr" if and only the
attribute value is intended to identify a specific object class;
- if an attribute is intended to identify different object classes, a descriptive name is given to that attribute and a
description is provided in the attribute behaviour;
- the name of an attribute ends in the string "Id" if and only the attribute value is intended to identify the name of
an object, in which case this attribute should be the first one listed, should use ASN.1 NameType and should not
be used to convey other information;
- the name of an attribute is composed of the name of an object class followed by the string "Id" if and only the
attribute value is intended to identify the name of the object class holding that attribute.
4 General Overview
The following information model diagrams have been drawn for the purpose of clarifying the relations between the
different object classes of the model:
1) entity-relationship models showing the relations of the different managed objects;
2) inheritance hierarchy showing how managed objects are derived from each other (i.e. the different paths of
inherited characteristics of the different managed objects).
These diagrams are only for clarification. The formal specification in terms of GDMO templates and ASN.1 type
definitions are the relevant information for implementations.
ETSI

---------------------- Page: 11 ----------------------

SIST EN 301 271 V1.2.1:2003
10 ETSI EN 301 271 V1.2.1 (2001-07)
4.1 Entity-relationship models
The following conventions are used in the diagrams (see figure 1):
c is contained in
moc
managed object class
1:1 containment
1:N containment
uninstantiable object class
a is associated with moc
(superclass)
1:1 association
1:N association
managed object class
moc
outside the actual fragment
bidirectional
unidirectional
i "is-a" relationship
Figure 1: Conventions used in diagrams for entity-relationship models
Where the directionality of containment is not clear, it can be identified by implications since the root class is unique.
ETSI

---------------------- Page: 12 ----------------------

SIST EN 301 271 V1.2.1:2003
11 ETSI EN 301 271 V1.2.1 (2001-07)
4.1.1 Entity relationship diagram for the service node
managed
ElementR1
c
tcAdaptor
TTP
Bidirectional
c
a a
vpCTP
vpTtp
Bidirectional
lspVb51Sn
Bidirectional
Vb5
a a
uniAccess
Vb5
a
c
vpCtp
Bidirectional
c
Vb5
aa
c
vpcLup
a
a
vcTTP vcCTP atmAccess
comm
Bidirectional Bidirectional Profile
PathBb
a
saalUni
Protocol
i
Profile
rtmcComm
PathBb
NO
...