SIST ETS 300 377-1:1997

SLOVENSKI STANDARD
01-november-1997
Signalizacijski protokoli in komutacija (SPS) - Vmesnik Q3 v krajevni centrali (LE)
za upravljanje in konfiguriranje vmesnikov V5 in pridruženih uporabniških profilov
- 1. del: Specifikacija vmesnika Q3
Signalling Protocols and Switching (SPS) - Q3 interface at the Local Exchange (LE) for
configuration management of V5 interfaces and associated customer profiles; Part 1: Q3
interface specification
Ta slovenski standard je istoveten z: ETS 300 377-1 Edition 1
ICS:
33.040.30 Komutacijski in signalizacijski Switching and signalling
sistem systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 377-1
TELECOMMUNICATION December 1994
STANDARD
Source:ETSI TC-SPS Reference:DE/SPS-03013.2
ICS: 33.080
TMN, information model, Q3 interface, LE, V5 interface, configuration, management
Key words:
Signalling Protocols and Switching (SPS);
Q3 interface at the Local Exchange (LE)
for configuration management of V5 interfaces
and associated customer profiles;
Part 1: Q3 interface specification
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 - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 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 1994. All rights reserved.
New presentation - see History box

Page 2
ETS 300 377-1: December 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 377-1: December 1994
Contents
Foreword.9
Introduction .9
1 Scope .11
2 Normative references .11
3 Definitions. 12
4 Abbreviations.13
5 Information model diagrams .14
5.1 Entity relationship diagram .14
5.1.1 Overview .15
5.1.2 V5 interface fragment. 16
5.1.3 Communication path fragment . 16
5.1.4 Protection fragment.18
5.1.5 Relation to I-ETS 300 291 - customer administration. 19
5.2 Inheritance hierarchy . 20
5.3 Naming hierarchy .21
6 Information model description.21
6.1 Object class descriptions.21
6.1.1 Managed element fragment.22
6.1.1.1 Managed element (managedElement) .22
6.1.2 V5 interface fragment. 22
6.1.2.1 V5 interface (v5Interface). 22
6.1.2.2 V5 TTP (v5Ttp) . 23
6.1.2.3 V5 time slot (v5TimeSlot) .25
6.1.2.4 V5 provision (v5Provision) .27
6.1.3 Virtual access port fragment .28
6.1.3.1 Virtual access port (virtualAccessPort).28
6.1.3.2 Virtual analogue access (virtualAnalogueAccess) .29
6.1.3.3 Virtual basic rate access (virtualBasicRateAccess).30
6.1.3.4 Virtual primary rate access (virtualPrimaryRateAccess).30
6.1.3.5 Virtual Leased Access (virtualLeasedAccess) .31
6.1.3.6 Virtual access channel (virtualAccessChannel) .32
6.1.4 Communication path fragment . 32
6.1.4.1 V5 communication channel (commChannel).32
6.1.4.2 Communication path (commPath).33
6.1.4.3 ISDN communication path (isdnCommPath) .34
6.1.4.4 PSTN communication path (pstnCommPath).34
6.1.4.5 BCC communication path (bccCommPath).34
6.1.4.6 Control communication path (controlCommPath) .34
6.1.4.7 Protection communication path (protCommPath).34
6.1.4.8 Link control communication path (linkControlCommPath).35
6.1.5 Protection fragment.35
6.1.5.1 V5 protection group (v5ProtectionGroup).35
6.1.5.2 V5 protection unit (v5ProtectionUnit). 35
6.1.6 V5 service fragment .36
6.1.6.1 V5 bearer channel reservation (v5BcReservation) .36
6.1.6.2 V5 leased line reservation (v5LlReservation).37
6.1.7 Supporting object classes .37

Page 4
ETS 300 377-1: December 1994
6.2 Definition of attributes.38
6.2.1 Relative distinguished name.38
6.2.2 State attributes .38
6.2.2.1 Operational state.38
6.2.2.2 Administrative state.38
6.2.2.3 Availability status .38
6.2.3 Relationship attributes.39
6.3 Actions description .39
6.4 Notifications description .42
7 Formal object class definitions.43
7.1 Definition of object classes.43
7.1.1 Managed element fragment.43
7.1.1.1 Managed element (managedElement) .43
7.1.2 V5 interface fragment .43
7.1.2.1 V5 interface (v5Interface).43
7.1.2.2 V5 TTP (v5Ttp).44
7.1.2.3 V5 time slot (v5TimeSlot) .46
7.1.2.4 V5 provision (v5Provision).47
7.1.3 Virtual access port fragment.48
7.1.3.1 Virtual access port (virtualAccessPort) .48
7.1.3.2 Virtual analogue access (virtualAnalogueAccess).48
7.1.3.3 Virtual basic rate access (virtualBasicRateAccess).49
7.1.3.4 Virtual primary rate access (virtualPrimaryRateAccess).50
7.1.3.5 Virtual leased access (virtualLeasedAccess).50
7.1.3.6 Virtual access channel (virtualAccessChannel).51
7.1.4 Communication path fragment .52
7.1.4.1 V5 communication channel (commChannel).52
7.1.4.2 Communication path (commPath).53
7.1.4.3 ISDN communication path (isdnCommPath) .53
7.1.4.4 PSTN communication path (pstnCommPath) .54
7.1.4.5 BCC communication path (bccCommPath).54
7.1.4.6 Control communication path (controlCommPath).54
7.1.4.7 Protection communication path (protCommPath) .55
7.1.4.8 Link control communication path (linkControlCommPath) .55
7.1.5 Protection fragment.55
7.1.5.1 V5 protection group (v5ProtectionGroup).55
7.1.5.2 V5 protection unit (v5ProtectionUnit).56
7.1.6 V5 service fragment.57
7.1.6.1 V5 bearer channel reservation (v5BcReservation).57
7.1.6.2 V5 leased line reservation (v5LlReservation) .57
7.2 Name bindings .58
7.2.1 v5Interface.58
7.2.2 v5Ttp.58
7.2.3 v5TimeSlot.58
7.2.4 v5Provision .58
7.2.5 virtualAccessPort.58
7.2.6 virtualAccessChannel.59
7.2.7 commChannel .59
7.2.8 commPath .59
7.2.9 v5ProtectionGroup.59
7.2.10 v5ProtectionUnit .59
7.3 Definition of packages .60
7.3.1 anSwitchOverToNewVariantPackage.60
7.3.2 commonDeleteBehaviourPackage.60
7.3.3 leSwitchOverToNewVariantPackage .60
7.3.4 neSpecificPointerPackage.60
7.3.5 peerManagedElementPackage.60
7.3.6 relationshipChangeNotificationPackage .61
7.3.7 supportedByObjectListPackage.61

Page 5
ETS 300 377-1: December 1994
7.3.8 v5AvailabilityStatusPackage .61
7.3.9 v5ProtectionAnSwitchPackage .61
7.3.10 v5ProtectionLeSwitchPackage .61
7.3.11 v5TsAdministrativeStatePackage.61
7.3.12 qualityOfServiceAlarmPackage.61
7.3.13 anFaultReportedPackage.62
7.4 Definition of behaviours.62
7.5 Definition of attributes.62
7.5.1 assocCommChannel.62
7.5.2 assocFrameCommPath .62
7.5.3 assocIsdnSignallingCommPath .62
7.5.4 assocPacketCommPath.62
7.5.5 assocProtectionGroup .63
7.5.6 assocResource .63
7.5.7 assocV5CommPaths .63
7.5.8 assocV5Interface.63
7.5.9 assocV5TimeSlot .64
7.5.10 assocV5TimeSlotB1 .64
7.5.11 assocV5TimeSlotB2 .64
7.5.12 bcReserved .64
7.5.13 blockingStatus.64
7.5.14 clientUserPorts.65
7.5.15 commChannelId .65
7.5.16 commPathId .65
7.5.17 configuredReliableResourcePointer.65
7.5.18 dataType.65
7.5.19 envelopeFunctionAddress .66
7.5.20 layer3PortAddress .66
7.5.21 linkId .66
7.5.22 neSpecificPointer .66
7.5.23 noOfBcRequested.66
7.5.24 ownProvVariant.67
7.5.25 peerManagedElement.67
7.5.26 permanentLineReservation.67
7.5.27 protecting .67
7.5.28 provId.67
7.5.29 reliableResourcePointer.68
7.5.30 serverV5Ttps.68
7.5.31 supportedProtocolVersion.68
7.5.32 unreliableResourcePointer.68
7.5.33 v5ChannelType .68
7.5.34 v5InterfaceId.69
7.5.35 v5ProtectionGroupId.69
7.5.36 v5ProtectionGroupNumber.69
7.5.37 v5ProtectionGroupType.69
7.5.38 v5ProtectionUnitId .69
7.5.39 v5UserPortAddress .70
7.6 Definition of actions .70
7.6.1 setReciprocalPointers.70
7.6.2 releaseReciprocalPointers .70
7.6.3 verifyRemoteProvVariant .71
7.6.4 readyForReprovisioning .71
7.6.5 notReadyForReprovisioning.71
7.6.6 requestRemoteProvVariant .72
7.6.7 switchOverToNewVariant.72
7.6.8 anReprovisioningStarted .72
7.6.9 leBlockingStarted .72
7.6.10 cannotReprovision .73
7.6.11 v5ProtectionAnSwitch .73
7.6.12 v5ProtectionLeSwitch .73

Page 6
ETS 300 377-1: December 1994
7.6.13 checkLinkId.74
7.6.14 restart .74
7.6.15 systemStartup.74
7.7 Definition of notifications .75
7.7.1 switchOverRequest .75
7.7.2 anBlockingStarted .75
7.7.3 verifyRequest.75
7.7.4 v5ProtectionSwitchReporting.75
7.7.5 shutdownRejected .75
7.7.6 anFaultReported.76
7.7.7 verifyRemoteProvVariantResult .76
7.7.8 switchOverToNewVariantResult.76
7.7.9 requestRemoteProvVariantResult .76
7.7.10 checkLinkIdResult.76
7.7.11 restartResult .77
7.7.12 systemStartupResult.77
7.8 ASN.1 defined types module .78
8 Protocol requirements.81
Annex A (normative): Mapping of management primitives for user port FSM onto state transitions
for virtual analogue accesses, virtual basic rate accesses, and virtual primary
rate accesses.82
Annex B (normative): Mapping of link control states on X.731 states.83
B.1 State mapping tables for the AN side .85
B.2 State mapping tables for the LE side .87
Annex C (informative): Telecommunications Management Network (TMN) management service
"Customer administration at the V5 interface and administration of V5
interface related data at the LE".89
C.1 Task Information Base (TIB) A .89
C.1.1 Description .89
C.1.2 Components of service .89
C.1.2.1 Manage service provision.89
C.1.2.2 Administer service facilities and supplementary services.89
C.1.2.3 Administer customer line .90
C.1.2.4 Manage line test.90
C.1.2.5 Configure and reconfigure V5 interface.90
C.2 Management function list.90
C.2.1 Insert, delete, modify, read single and multi-line customer access (ISDN and analogue
access) accessed via a V5 interface.90
C.2.1.1 Customers accessed via a V5.1 interface (ISDN basic and analogue
access) .90
C.2.1.1.1 Insert customer accesses.90
C.2.1.1.2 Delete customer accesses .90
C.2.1.1.3 Modify customer accesses.90
C.2.1.1.4 Read customer accesses.90
C.2.1.2 Customers accessed via a V5.2 interface (ISDN basic and primary rate
and analogue access).91
C.2.1.2.1 Insert customer accesses.91
C.2.1.2.2 Delete customer accesses .91
C.2.1.2.3 Modify customer accesses.91
C.2.1.2.4 Read customer accesses.91
C.2.2 Insert, delete, modify, read customer (supplementary) service.91
C.2.3 Block/unblock single and multi-line customers .91

Page 7
ETS 300 377-1: December 1994
C.2.4 Block/unblock customer (supplementary) service .91
C.2.5 Activate/de-activate malicious call tracing.91
C.2.6 Activate/de-activate charging observation.91
C.2.7 Activate/de-activate line test and measurement .91
C.2.8 Insert, delete, modify, read a V5 interface . 92
C.2.8.1 V5.1 interface . 92
C.2.8.1.1 Insert a V5.1 interface . 92
C.2.8.1.2 Delete a V5.1 interface . 92
C.2.8.1.3 Modify a V5.1 interface. 92
C.2.8.1.4 Read a V5.1 interface. 92
C.2.8.2 V5.2 interface . 92
C.2.8.2.1 Insert a V5.2 interface . 92
C.2.8.2.2 Augment a V5.2 interface.92
C.2.8.2.3 Delete a V5.2 interface . 92
C.2.8.2.4 Reducing a V5.2 interface .92
C.2.8.2.5 Modify a V5.2 interface. 92
C.2.8.2.6 Read a V5.2 interface. 93
C.2.8.2.7 Upgrade a V5.1 to a V5.2 interface.93
Annex D (informative): Functional architecture.94
Annex E (informative): Link control message flows.95
Annex F (informative): Message flows for the mapping of virtual access ports on X.731 states. 100
F.1 PSTN X.731 state management . 100
F.1.1 Blocking initiated by the AN. 100
F.1.2 Blocking request initiated by the AN. 100
F.1.3 Blocking initiated by the LE . 101
F.1.4 Co-ordinated unblocking initiated by the LE . 101
F.1.5 Co-ordinated unblocking initiated by the AN. 102
F.2 ISDN X.731 state management . 104
F.2.1 Blocking initiated by the AN. 104
F.2.2 Blocking request initiated by the AN. 105
F.2.3 Blocking initiated by the LE . 106
F.2.4 Co-ordinated unblocking initiated by the LE . 107
F.2.5 Co-ordinated unblocking initiated by the AN. 108
Annex G (informative): Bibliography. 110
History. 111

Page 8
ETS 300 377-1: December 1994
Blank page
Page 9
ETS 300 377-1: December 1994
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS is part 1 of a multi-part standard covering the Q3 interface specification at the Local Exchange
(LE) for configuration management of V5 interfaces and associated customer profiles as described below:
Part 1: "Q3 interface specification";
Part 2: "Managed Object Conformance Statement (MOCS) proforma specification".
The following multi-part standards are directly related to this ETS:
ETS 300 376: "Q3 interface at the Access Network (AN) for configuration management of V5
interfaces and associated user ports";
ETS 300 378: "Q3 interface at the Access Network (AN) for fault and performance
management of V5 interfaces and associated user ports";
ETS 300 379: "Q3 interface at the Local Exchange (LE) for for fault and performance
management of V5 interfaces and associated customer profiles".
Transposition dates
Date of latest announcement of this ETS (doa): 31 March 1995
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 September 1995
Date of withdrawal of any conflicting National Standard (dow): 30 September 1995
Introduction
Customer administration is a management activity that the network operator performs in order to exchange
with the customer all the customer related management data and functions required to offer a
telecommunications service and to exchange with the network all the customer related management data
and functions necessary for the network to produce that telecommunications service.
It is considered that the customer's terminal equipment can be connected directly to the Local Exchange
(LE) or via a V5 interface.
In a wide sense, this could include interactions for the purpose of service provision management,
configuration administration, fault administration, charging (including detailed billing) administration,
complaints administration, quality of service administration, traffic measurement administration etc. In this
ETS, however, only customer administration in the more traditional sense of service provision and service
configuration has been included.
In particular, the tasks to be performed in the LE to provide service for customers which are connected via
a V5 interface to the LE are considered.
Administration of V5 interface related data is a management activity that the network operator performs in
order to configure initially or to reconfigure a V5 interface to enable and maintain the service offering for
the customers connected.
Page 10
ETS 300 377-1: December 1994
An agreement was reached to consider all items concerning configuration management of V5 interfaces.
This covers:
- the labelling of a V5 interface with protocol version and provisioning variant;
- a switch-over possibility between V5 interface datasets with different provisioning variants and
protocol versions for reconfiguration of a V5 interface;
- allocation of communication and bearer channels for a V5 interface;
- handling of customer port related data relevant for the LE;
- administrative blocking of user ports within a V5 interface;
- association of user ports to a specific V5 interface;
- marking of ISDN user port B-channels as unavailable when used for the permanent line service in the
AN;
- upgrading a V5.1 interface to a V5.2 interface.

Page 11
ETS 300 377-1: December 1994
1 Scope
This European Telecommunication Standard (ETS) specifies the Q3 interface between a Local Exchange
(LE) and the Telecommunications Management Network (TMN) for the support of configuration
management functions for V5 interfaces, as described in ETS 300 324-1 [2] and ETS 300 347-1 [3], and
their associated customer profiles. The management of transmission, media and services which are not
related to V5 interfaces is outside the scope of this ETS.
The Q3 interface is the TMN interface between Network Elements (NEs) or Q-adapters which interface to
Operations Systems (OSs) without mediation and between OSs and mediation devices. The location of the
Q3 interface is illustrated in annex G of ETS 300 376-1 [4].
Generic modelling of leased line ports which are associated with a V5 interface is within the scope of this
ETS, but the traffic from these ports can only be associated with 64 kbit/s bearer channels on the V5
interface.
The definition of OS functionality, and the specification of Qx interfaces and proprietary interfaces are
outside the scope of this ETS.
Existing protocols are used where possible, and the focus of this ETS is on defining the object models.
Although security management is excluded from this ETS, any aspects of security relating to configuration
management are included as an integral part of configuration management.
NOTE: Configuration management includes provisioning and the provisioning activity may
include testing, but this testing is not included in this ETS. It is included in the
specification relating to fault and performance management, ETS 300 379-1 [6].
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] I-ETS 300 291 (1995): "Network Aspects (NA); Functional specification of
Customer Administration (CA) on the Operations Systems/Network Element
(OS/NE) interface".
[2] ETS 300 324-1 (1994): "Signalling Protocols and Switching (SPS); V interfaces
at the digital Local Exchange (LE); V5.1 interface for the support of Access
Network (AN); Part 1: V5.1 interface specification".
[3] ETS 300 347-1 (1994): "Signalling Protocols and Switching (SPS); V interfaces
at the digital Local Exchange (LE); V5.2 interface for the support of Access
Network (AN); Part 1: V5.2 interface specification".
[4] ETS 300 376-1 (1994): "Signalling Protocols and Switching (SPS); Q3 interface
at the Access Network (AN) for configuration management of V5 interfaces and
associated user ports; Part 1: Q3 interface specification".
[5] ETS 300 378-1: "Signalling Protocols and Switching (SPS); Q3 interface at the
Access Network (AN) for fault and performance management of V5 interfaces
and associated user ports; Part 1: Q3 interface specification".

Page 12
ETS 300 377-1: December 1994
[6] ETS 300 379-1: "Signalling Protocols and Switching (SPS); Q3 interface at the
Local Exchange (LE) for fault and performance management of V5 interfaces
and associated customer profiles; Part 1: Q3 interface specification".
[7] CCITT Recommendation M.3010 (1992): "Principles for a telecommunications
management network".
[8] CCITT Recommendation M.3100 (1992): "Generic network information model".
[9] ITU-T Recommendation Q.811 (1993): "Lower layer protocol profiles for the Q3
interface".
[10] ITU-T Recommendation Q.812 (1993): "Upper layer protocol profiles for the Q3
interface".
[11] CCITT Recommendation X.208 (1988): "Specification of Abstract Syntax
Notation One (ASN.1)".
[12] CCITT Recommendation X.711 (1991): "Common management information
protocol definition for CCITT applications".
[13] CCITT Recommendation X.720 | ISO/IEC 10165-1 (1992): "Information
technology - Open systems interconnection - Structure of management
information: Management information model".
[14] CCITT Recommendation X.721 | ISO/IEC 10165-2 (1992): "Information
technology - Open systems interconnection - Structure of management
information: Definition of management information".
[15] CCITT Recommendation X.730 | ISO/IEC 10164-1 (1992): "Information
technology - Open systems interconnection - Systems management: Object
management function".
[16] CCITT Recommendation X.731 | ISO/IEC 10164-2 (1992): "Information
technology - Open systems interconnection - Systems management: State
management function".
[17] CCITT Recommendation X.732 | ISO/IEC 10164-3 (1992): "Information
technology - Open systems interconnection - Systems management: Attributes
for representing relationships".
3 Definitions
For the purposes of this ETS, the following definitions apply:
Access Network (AN): See ETS 300 324-1 [2].
B-channel number: Identifies a B-channel on the ISDN basic User-Network Interface (UNI) and ISDN
primary rate UNI.
bearer channel: See ETS 300 324-1 [2].
Bearer Channel Connection (BCC): See ETS 300 347-1 [3].
Communication channel (C-channel): See ETS 300 324-1 [2].
Communication path (C-path): See ETS 300 324-1 [2].
control protocol: See ETS 300 324-1 [2].

Page 13
ETS 300 377-1: December 1994
D-channel signalling type (Ds-type) data: ISDN D-channel signalling type data with Service Access
Point Identifier (SAPI) not equal to 16, and not equal to 32 to 62 (see ETS 300 324-1 [2], subclause 8.4).
envelope function address: See ETS 300 324-1 [2].
frame type (f-type) data: ISDN D-channel data with SAPI in the range from 32 to 62 (see
ETS 300 324-1 [2], subclause 8.4).
layer 3 address: See ETS 300 324-1 [2].
Local Exchange (LE): See ETS 300 324-1 [2].
Operations System (OS): See CCITT Recommendation M.3010 [7].
packet type (p-type) data: ISDN D-channel data with SAPI equal to 16 (see ETS 300 324-1 [2],
subclause 8.4).
Permanent line (PL): See ETS 300 324-1 [2].
protection protocol: See ETS 300 347-1 [3].
provisioning variant: See ETS 300 324-1 [2].
semi-permanent leased line: See ETS 300 324-1 [2].
time slot number: See ETS 300 324-1 [2].
V5 interface: See ETS 300 324-1 [2].
V5 time slot: Is an object class representing a 64 kbit/s channel of a V5 interface that is used as bearer
or communication channel. It is a subclass of "CCITT Recommendation
M.3100:1992":connectionTerminationPointBidirectional.
V5 Trail Termination Point (TTP): Is an object class representing a 2 Mbit/s interface that is used as
V5.1 interface or as part of a V5.2 interface. It is a subclass of "CCITT Recommendation
M.3100:1992":trailTerminationPointBidirectional.
virtual access channel: Is an object class representing an individual ISDN B-/D-channel of an ISDN
access port, or an individual channel of a digital access port, or the bearer channel for an analogue access
port. It is a subclass of "I-ETS 300 291":accessChannel.
virtual access port: Is an object class representing an image of the customer access port which is
located in an AN and connected to the LE via V5 interface. It is a subclass of "I-ETS 300 291":accessPort
and used for provisioning services to the customer. This object class is subclassed for the different types
of customer access ports.
4 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AN Access Network
ASN.1 Abstract Syntax Notation One (see CCITT Recommendation X.208 [11])
BCC Bearer Channel Connection
C-channel Communication channel
C-path Communication path
CTP Connection Termination Point
Ds-type D-channel signalling type
DS Default Standby
ET Exchange Termination
Page 14
ETS 300 377-1: December 1994
f-type frame type
FSM Finite State Machine
ID Identity, Identifier
ISDN Integrated Services Digital Network
LE Local Exchange
M/C/O Mandatory/Conditional/Optional
MDU Management Data Unit
MPH primitive between Physical layer and layer 2 Management
NE Network Element
OS Operations System
p-type packet type
PH primitive between Physical layer and layer 2
PL Permanent Line
PSTN Public Switched Telephone Network
Q3 Q3 interface at the Access Network
AN
Q3 Q3 interface at the Local Exchange
LE
RDN Relative Distinguished Name
SAPI Service Access Point Identifier
TIB Task Information Base
TMN Telecommunications Management Network
TTP Trail Termination Point
UNI User Network Interface
5 Information model diagrams
The entity relationship diagram is given in subclause 5.1 and the inheritance hierarchy (is-a relationships)
and naming hierarchy (containment relationships) are given in subclauses 5.2 and 5.3, respectively.
5.1 Entity relationship diagram
Figures 1 to 5 show the overall relationships between the various entities. These correspond to the
managed objects which are manipulated at the Q3 interface.
For V5.1 interfaces, access channels on access ports are associated with bearer time slots on a V5.1
interface by configuration over the Q3 interface of the LE. For V5.2, access channels on access ports are
associated with bearer time slots on a V5.2 interface by the V5.2 Bearer Channel Connection (BCC)
protocol. For both V5.1 and V5.2, the association of user signalling with communication paths and the
association between communication paths and logical communication channels on the V5 interface is by
configuration over the Q3 interface of the LE. The association of logical communication channels with
physical communication time slots on the V5 interface is initially established over the Q3 interface, but can
be changed for V5.2 interfaces by the V5.2 protection protocol.
Signalling protocols and their associated communication are modelled using various objects which
represent the communication paths and the communication time slots. There are six classes of
communication path objects. There is a single class for all Integrated Services Digital Network (ISDN)
signalling with an attribute to distinguish between Ds-type, p-type, and f-type data. There are classes for
Public Switched Telephone Network (PSTN) signalling, the control protocol, the BCC protocol, the link
control protocol, and the protection protocol. In addition to these six communication path object classes,
there is also an object class which represents communication channels.
There is one instance of the appropriate object class per communication path and per communication
channel. These are contained in instances of v5Interface.
V5 control messages relating to provisioning are managed by an optional object on the Q3 interface.
These messages may not be required once a TMN X interface or an integrated OS is available.
If control messages relating to provisioning are not supported on the Q3 interface then a default value for
provisioning variant will be automatically used on the V5 interface. All V5 interfaces will use this default
value unless actively changed via the Q3 interface. The value of this default is all zeroes.

Page 15
ETS 300 377-1: December 1994
Protection group 1 and its contained protection unit(s) are to be instantiated for the V5.2 case even if there
is only one 2,048 Mbit/s link.
5.1.1 Overview
A single managedElement can contain a number of virtualAccessPorts, a number of v5Interfaces, and a
number of v5Ttps (which each represent a 2,048 Mbit/s link). There is a bi-directional association between
each v5Interface and all of its related virtualAccessPorts. Likewise there is a bi-directional relationship
between each v5Interface and all of its related v5Ttps (2,048 Mbit/s links).
"M.3100":
managedElement
c
c
c
n
n
1n
v5Interface
a
a
v5Ttp
fragment
1 1
c
c
c
n
n
n n
commPath
a
co
...