ETSI ETS 300 376-1 ed.1 (1994-12)

Q3 interface at the Access Network (AN) for configuration management of V5 interfaces and associated user ports; Part 1: Q3 interface specification

DE/SPS-03013.1

Signalizacijski protokoli in komutacija (SPS) - Vmesnik Q3 v dostopovnih omrežjih (AN) za upravljanje in konfiguriranje vmesnikov V5 in pridruženih uporabniških priključkov - 1. del: Specifikacija vmesnika Q3

General Information

• Status: Published
• Publication Date: 03-Jan-1995
• Technical Committee: SPS 3 - IN protocols
• Current Stage: 12 - Completion
• Due Date: 30-Dec-1994
• Completion Date: 04-Jan-1995
• Ref Project: SIST ETS 300 376-1:1997 - 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

Standards Content (Sample)

SLOVENSKI STANDARD
01-november-1997
6LJQDOL]DFLMVNLSURWRNROLLQNRPXWDFLMD6369PHVQLN4YGRVWRSRYQLKRPUHåMLK
$1]DXSUDYOMDQMHLQNRQILJXULUDQMHYPHVQLNRY9LQSULGUXåHQLKXSRUDEQLãNLK
SULNOMXþNRYGHO6SHFLILNDFLMDYPHVQLND4
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
Ta slovenski standard je istoveten z: ETS 300 376-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 376-1
TELECOMMUNICATION December 1994
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-03013.1
ICS: 33.080
TMN, information model, Q3 interface, AN, V5 interface, configuration, management
Key words:
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
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 376-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 376-1: December 1994
Contents
Foreword.7
Introduction .7
1 Scope .9
2 Normative references .9
3 Definitions. 10
4 Abbreviations.11
5 Information model diagrams .12
5.1 Entity relationship diagram .12
5.1.1 Overview .13
5.1.2 V5 interface fragment. 14
5.1.3 Communication path fragment . 14
5.1.4 Protection fragment.16
5.2 Inheritance hierarchy . 17
5.3 Naming hierarchy .17
6 Information model description.18
6.1 Object class description.18
6.1.1 V5 fragment.18
6.1.2 Access fragment. 18
6.1.2.1 Access network (accessNetwork).18
6.1.2.2 User port TTP (userPortTtp).19
6.1.2.3 ISDN Basic Access (BA) user port (isdnBAUserPort) .19
6.1.2.4 ISDN Primary Rate Access (PRA) user port
(isdnPRAUserPort) . 19
6.1.2.5 PSTN user port (pstnUserPort).20
6.1.2.6 Leased port (leasedPort) .20
6.1.2.7 User port bearer channel CTP
(userPortBearerChannelCtp) .20
6.2 Definition of attributes.21
6.3 Actions description .21
6.4 Notifications description .21
7 Formal definitions.21
7.1 Definition of managed object classes .21
7.1.1 V5 fragment.21
7.1.2 Access fragment. 22
7.1.2.1 Access network (accessNetwork).22
7.1.2.2 User port TTP (userPortTtp). 22
7.1.2.3 ISDN BA user port (isdnBAUserPort) .23
7.1.2.4 ISDN PRA user port (isdnPRAUserPort).23
7.1.2.5 PSTN user port (pstnUserPort).23
7.1.2.6 Leased port (leasedPort) .24
7.1.2.7 User port bearer channel CTP
(userPortBearerChannelCtp) .24
7.2 Name bindings .25
7.2.1 V5 interface (v5Interface) .25
7.2.2 V5 TTP (v5Ttp). 25
7.2.3 User port TTP (userPortTtp) .25

Page 4
ETS 300 376-1: December 1994
7.2.4 User port Bearer channel CTP (userPortBearerChannelCtp).25
7.3 Definition of packages .25
7.3.1 Associated communication paths (assocCommPathsPackage).25
7.3.2 Associated V5 interface (assocV5InterfacePackage) .26
7.3.3 Associated time slot (assocTimeSlotPackage).26
7.3.4 Bearer channel type (bearerChannelTypePackage).26
7.3.5 Blocking status (blockingStatusPackage).26
7.3.6 Grading enabled (gradingEnabledPackage).26
7.4 Definition of behaviours.27
7.5 Definition of attributes.27
7.5.1 Associated time slot (assocTimeSlot).27
7.5.2 Bearer channel type (bearerChannelType).27
7.5.3 Grading enabled (gradingEnabled).27
7.5.4 Access digital section (accessDigitalSection).27
7.5.5 Special feature (specialFeatures) .28
7.6 Definition of actions .28
7.7 Definition of notifications .28
7.8 ASN.1 defined types module .28
8 Protocol requirements.29
Annex A (normative): Mapping of V5 user port states on X.731 states.30
A.1 Mapping of V5 PSTN user port states on X.731 states.30
A.2 Mapping of V5 ISDN basic access user port states on X.731 states.31
A.3 Mapping of V5 ISDN primary rate access user port states on X.731 states .34
Annex B (normative): Mapping of link control states on X.731 states.37
Annex C (normative): TMN management service "V5 related configuration at the AN".38
C.1 Task Information Base (TIB) A .38
C.1.1 Description .38
C.1.2 Components of service .38
C.1.2.1 General requirements .38
C.1.2.1.1 Association of user ports with V5 interfaces.38
C.1.2.1.2 Information flow across the Q3 interface .38
C.1.2.1.3 Compatibility between AN and LE .38
C.1.2.1.4 Configuration of bearer channels.38
C.1.2.2 V5 interface requirements .38
C.1.2.2.1 V5 interface and link IDs.38
C.1.2.2.2 Provisioning variant .38
C.1.2.2.3 Channel configuration .39
C.1.2.2.4 Association of interfaces with exchanges.39
C.1.2.2.5 Standby operation.39
C.1.2.2.6 Persistency checking.39
C.1.2.2.7 Global PSTN parameters .39
C.1.2.3 User port requirements .39
C.1.2.3.1 Operational threshold.39
C.1.2.3.2 Port blocking .39
C.1.2.3.3 User port addresses .39
C.1.2.3.4 Split ISDN ports.40
C.1.2.3.5 User requirements .40
C.1.2.3.6 ISDN with access digital sections.40
C.1.2.3.7 Port specific PSTN parameters.40
C.2 Management function list.40
C.2.1 User port functions .40

Page 5
ETS 300 376-1: December 1994
C.2.1.1 Insert a user port .40
C.2.1.2 Delete a user port .40
C.2.1.3 Modify a user port.40
C.2.1.4 Read a user port.41
C.2.2 V5 interface functions .41
C.2.2.1 Insert a V5 interface. 41
C.2.2.2 Delete a V5 interface.41
C.2.2.3 Modify a V5 interface .41
C.2.2.4 Read a V5 interface . 41
C.2.3 Cross-connection functions .41
C.2.3.1 Establish a connection .41
C.2.3.2 De-establish a connection .41
C.2.3.3 Modify a connection.42
C.2.3.4 Read a connection.42
Annex D (informative): Functional architecture.43
Annex E (informative): Link control message flows.47
Annex F (informative): User port control message flows.48
F.1 Message flows for the mapping of PSTN user port states on X.731 states .48
F.1.1 Blocking initiated by AN .48
F.1.2 Blocking request initiated by AN .48
F.1.3 Blocking initiated by LE.48
F.1.4 Co-ordinated unblocking initiated by the LE . 49
F.1.5 Co-ordinated unblocking initiated by the AN. 49
F.2 Message flows for the mapping of ISDN basic access user port states on X.731 states.51
F.2.1 Blocking initiated by AN .51
F.2.2 Blocking initiated by the LE .52
F.2.3 Co-ordinated unblocking initiated by the LE . 53
F.2.4 Co-ordinated unblocking initiated by the AN. 54
F.3 Message flows for the mapping of ISDN primary rate access user port states on X.731 states.56
F.3.1 Blocking initiated by AN .56
F.3.2 Blocking initiated by the LE .56
F.3.3 Co-ordinated unblocking initiated by the LE . 56
F.3.4 Co-ordinated unblocking initiated by the AN. 57
Annex G (normative): Location of the Q3 interface.59
Annex H (normative): Summary of V5 requirement details.60
Annex J (normative): Defaults and predefined items.61
Annex K (informative): Bibliography.62
History.64

Page 6
ETS 300 376-1: December 1994
Blank page
Page 7
ETS 300 376-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 Access Network
(AN) for configuration management of V5 interfaces and associated user ports 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 377: "Q3 interface at the Local Exchange (LE) for configuration management of V5
interfaces and associated customer profiles";
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 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
V5 interfaces, as described in ETS 300 324 (1994) and ETS 300 347 (1994), operate between an
exchange and an Access Network (AN) to support various narrowband services. These interfaces and their
associated user ports have to be managed by the Operations Systems (OSs) within the
Telecommunications Management Network (TMN).
ITU-T Recommendation G.803 (1993) provides an abstracted view of telecommunications equipment,
based on the essential functions that such equipment needs to perform. These functional components are
modelled by objects, which represent the implementation-independent aspects of the equipment.
The following assumptions relating to the scope of this ETS were to be considered:
- existing protocols should be used where possible, and the focus of the ETS should be on defining
the object models;
- the interface should not involve objects specific to the control of a leased line network which is not
connected to the LE or of an external line test system;
- a model of the AN appears necessary. The model relevant to the present standards on the V5
interface and ports will be developed if it does not already exist elsewhere. Other object models
outside the scope of this ETS may share the same physical Q3 interface;
- the definition of OS functionality is outside the scope of this ETS;
- security management is excluded from this ETS, but aspects of security relating to configuration
management are included;
Page 8
ETS 300 376-1: December 1994
- configuration management includes provisioning and the provisioning activity may include testing, but
this testing is not included in this ETS. It will be included in the specification relating to fault and
performance management;
- the specification should cover the provisioning of national variants and type variants of lines. Existing
modelling, such as the customer administration model, should be used for this, if possible;
- the specification should not cover general functions within the AN, such as multiplexing, cross-
connection and transmission functions, unless some aspect impacts the configuration management
of V5 interfaces and related ports;
- configuration management related to redundancy of V5 interfaces is within the scope of this ETS,
both for multiple V5 interfaces and for the individual links within a V5.2 interface;
- the definition of an object model for a transparent channel on the V5 interface which supports the
synchronization of OSs is outside the scope of this ETS;
- it is assumed that the relationship between directory numbers and equipment is kept in the OSs of
the AN, so that the Q3 interface of the AN does not need to handle directory numbers.

Page 9
ETS 300 376-1: December 1994
1 Scope
This European Telecommunication Standard (ETS) specifies the Q3 interface between an Access Network
(AN) and the Telecommunications Management Network (TMN) for the support of configuration
management functions for V5 interfaces, as described in ETS 300 324-1 [3] and ETS 300 347-1 [4], and
their associated user ports. 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 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.
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.
This ETS does not constrain the logical or physical size of the AN or its geographical dispersion. The
definition of the managed object class which represents an AN is outside the scope of this ETS.
Existing protocols are used where possible, and the focus of this ETS is on defining the object models.
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 378-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: "Network Aspects (NA); Functional specification of Customer
Administration (CA) on the Operations System/Network Element (OS/NE)
interface".
[2] ETS 300 297: "Integrated Services Digital Network (ISDN); Access digital
section for ISDN basic access".
[3] 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".
[4] 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".
[5] ETS 300 377-1 (1994): "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".
[6] 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 10
ETS 300 376-1: December 1994
[7] 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".
[8] ITU-T Recommendation G.773 (1993): "Protocol suites for Q-interfaces for
management of transmission systems".
[9] CCITT Recommendation G.784 (1990): "Synchronous Digital Hierarchy (SDH)
management".
[10] CCITT Recommendation M.3010 (1992): "Principles for a telecommunications
management network".
[11] CCITT Recommendation M.3100 (1992): "Generic network information model".
[12] ITU-T Recommendation Q.811 (1993): "Lower layer protocol profiles for the Q3
interface".
[13] ITU-T Recommendation Q.812 (1993): "Upper layer protocol profiles for the Q3
interface".
[14] CCITT Recommendation X.208 (1988): "Specification of Abstract Syntax
Notation One (ASN.1)".
[15] CCITT Recommendation X.711 (1991): "Common management information
protocol definition for CCITT applications".
[16] CCITT Recommendation X.721 | ISO/IEC 10165-2 (1992): "Information
technology - Open systems interconnection - Structure of management
information: Definition of management information".
[17] CCITT Recommendation X.731 | ISO/IEC 10164-2 (1992): "Information
technology - Open systems interconnection - Systems management: State
management function".
[18] 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 [3].
bearer channel: See ETS 300 324-1 [3].
Bearer Channel Connection (BCC): See ETS 300 347-1 [4].
Communication channel (C-channel): See ETS 300 324-1 [3].
Communication path (C-path): See ETS 300 324-1 [3].
control protocol: See ETS 300 324-1 [3].
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 [3], subclause 8.4).
envelope function address: See ETS 300 324-1 [3].

Page 11
ETS 300 376-1: December 1994
frame type (f-type) data: ISDN D-channel data with SAPI in the range from 32 to 62 (see
ETS 300 324-1 [3], subclause 8.4).
Local Exchange (LE): See ETS 300 324-1 [3].
Operations System (OS): See CCITT Recommendation M.3010 [10].
packet type (p-type) data: ISDN D-channel data with SAPI equal to 16 (see ETS 300 324-1 [3],
subclause 8.4).
Permanent Line (PL): See ETS 300 324-1 [3].
protection protocol: See ETS 300 347-1 [4].
provisioning variant: See ETS 300 324-1 [3].
semi-permanent leased line: See ETS 300 324-1 [3].
time slot number: See ETS 300 324-1 [3].
V5 interface: See ETS 300 324-1 [3].
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.
X interface: See CCITT Recommendation M.3010 [10].
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 [14])
BA Basic Access
BCC Bearer Channel Connection
C-channel Communication channel
C-path Communication path
CTP Connection Termination Point
DCC Data Communications Channel
Ds-type D-channel signalling type
f-type frame type
FSM Finite State Machine
ID Identity, Identifier
ISDN Integrated Services Digital Network
LE Local Exchange
M/O Mandatory/Optional
MPH primitive between Physical layer and layer 2 Management
NE Network Element
OS Operations System
p-type packet type
PL Permanent Line
PRA Primary Rate Access
PSTN Public Switched Telephone Network
RDN Relative Distinguished Name
SAPI Service Access Point Identifier

Page 12
ETS 300 376-1: December 1994
TIB Task Information Base
TMN Telecommunications Management Network
TTP Trail Termination Point
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 4 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, bearer channels on user ports are associated with bearer time slots on a V5.1
interface by configuration over the Q3 interface of the AN. For V5.2, bearer channels on user 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 AN. 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.
The AN treats time slots on the V5.2 interface which are used for semi-permanent connections like any
other bearer time slot on a V5.2 interface.
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, 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.
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.
A Trail Termination Point (TTP) contains the Connection Termination Points (CTPs) at the higher network
layer which it serves. This relationship allows the entity relationship diagram to mapped onto the functional
architecture (see annex D).
Page 13
ETS 300 376-1: December 1994
5.1.1 Overview
A single accessNetwork can contain a number of userPortTtps, 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 userPorts. Likewise there is a bi-directional relationship between each
v5Interface and all of its related v5Ttps (2,048 Mbit/s links).
Each userPortTtp can contain a number of userPortBearerChannelCtps, one for each of its 64 kbit/s
bearer channels. Each v5Ttp contains 31 v5TimeSlots which represent the CTPs corresponding to each of
the 31 physical time slots which may be configured. Each userPortBearerChannelCtp can be associated
with a unique v5TimeSlot for a V5.1 interface, but for the V5.2 case there is no corresponding association
because the relationship is controlled by the V5.2 BCC protocol.
access
Network
c
c
c
n
n
1n
v5Interface
a
a
v5Ttp
fragment
1 1
c
c c
n
n
n n
commPath
a
commChannel
c
n1
fragment
a
mn
userPortTtp
0,1
1 0,1
a
a
a
c
1 0,1,2
v5Protection
fragment
1 31
n
(only V5.2) 1
a
userPortBearer
v5TimeSlot
ChannelCtp
0,1
a
only V5.1 1
c
contains
a
is associated with (unidirectional)
a
is associated with (reciprocal relation)
Figure 1: Entity relationship diagram - overview

Page 14
ETS 300 376-1: December 1994
Link blocking requests on the Link control protocol are generated by setting the administrative state
attribute of the relevant instance of v5Ttp to shutting down. Only deferred blocking requests can be
generated in this way. Deferred blocking requests on the Link control protocol cannot be generated by
manipulating the object model. Port blocking requests for the Control protocol are generated by setting the
administrative state attribute of the relevant instance of the subclass of userPortTtp to shutting down.
5.1.2 V5 interface fragment
Each v5Interface contains a number of communication path objects in its commPath fragment, a number of
commChannels, and one or two v5ProtectionGroup objects if it represents a V5.2 interface. Each instance
of v5Interface may contain an instance of v5Provision to support the V5 pre-provisioning messages.
a a
userPortTtp v5Interface v5Ttp
n1 1 n
c
0,1,2 n 0,1 n
v5Protection
commPath
fragment
v5Provision commChannel
fragment
(only V5.2)
V5 interface
fragment c
contains
a
is associated with
Figure 2: Entity relationship diagram - V5 interface fragment
5.1.3 Communication path fragment
Each ISDN userPortTtp can be associated with up to three isdnCommPaths, one for each type of ISDN
signalling. Each isdnCommPath handles a certain type of ISDN signalling for a number of userPortTtps,
and is associated with these. There may be more than one isdnCommPath contained in the v5Interface for
each type of ISDN signalling.
The v5Interface contains a single controlCommPath. It contains a single pstnCommPath, but only if there
are any PSTN userPortTtps associated with it. It also contains a single bccCommPath, a single
protCommPath, and a single linkControlCommPath if it represents a V5.2 interface.
Each commChannel can be associated with up to three isdnCommPaths representing three different types
of ISDN signalling. It can also be associated with the pstnCommPath. The commChannel which is
associated with controlCommPath shall also be associated with the bccCommPath and with the
linkControlCommPath if the v5Interface which contains it represents a V5.2 interface.

Page 15
ETS 300 376-1: December 1994
0,1,2,3
a
0,1,2,3
isdn
a
userPortTtp a commChannel
CommPath
n1
Basic access, Each one instance for:
Primary rate access - Ds-type data
- p-type data
- f-type data
pstn
0,1
CommPath
bcc
CommPath
0,1
(only V5.2)
control
i
commPath
0,1
CommPath
linkControl
CommPath
0,1
(only V5.2)
prot v5Protection
fragment
CommPath
a
1 1
(only V5.2)
(only V5.2)
communication path fragment
a
is associated with (unidirectional)
a
is associated with (reciprocal relation)
i
is a
Figure 3: Entity relationship diagram - communication path fragment

Page 16
ETS 300 376-1: December 1994
5.1.4 Protection fragment
There is a bi-directional one-to-one association between commChannels and certain v5TimeSlots. Not
every v5TimeSlot is associated with a commChannel. Some are used for bearer traffic and others are
available for protection of commChannels on V5.2 interfaces. This protection adds onto the modelling for
the V5.1 interfaces, and does not affect that modelling.
The time slots which may be associated with the commChannel which is associated with the
controlCommPath are constrained by the V5 interface specifications ETS 300 324-1 [3] and
ETS 300 347-1 [4]. A v5Interface which represents a V5.2 interface shall contain a v5ProtectionGroup of
type 1 which contains two v5ProtectionUnits (see figure 4). One of these v5ProtectionUnits points to the
protected commChannel which is associated with both the controlCommPath, the bccCommPath, and the
linkControlCommPath. The corresponding pointer in the other v5ProtectionUnit is null. Both
v5ProtectionUnits point to their associated v5TimeSlots. The containing v5ProtectionGroup of type 1 is
pointed to by the protCommPath for the v5Interface, so there is an indirect mapping from the
protCommPath through the v5ProtectionGroup of type 1, through its two contained v5ProtectionUnits onto
its related v5TimeSlots.
v5Interface
c
0,1,2
prot
1 1
v5Protection
a
CommPath
Group
only protection
group 1
protection
fragment
c
n (protection group 1: n=2)
comm v5Protection 1
0,1 1 1
a v5TimeSlot
a
Channel
Unit
0,1
a
c contains
a
is associated with (unidirectional)
a
is associated with (reciprocal relation)
Figure 4: Entity relationship diagram - protection fragment
A v5Interface which represents a V5.2 interface also contains a v5ProtectionGroup of type 2 if other
commChannels are protected (see figure 4). The v5ProtectionGroup of type 2 contains a number of
v5ProtectionUnits, each of which points to its associated v5TimeSlot. The v5ProtectionUnits which point to
active v5TimeSlots also point to the commChannels which are associated with the active v5TimeSlots. The
corresponding pointers in the other v5ProtectionUnits are set to null.

Page 17
ETS 300 376-1: December 1994
5.2 Inheritance hierarchy
Figure 5 traces the inheritance from the highest level object "CCITT Recommendation X.721:1992":top to
the managed objects defined in this ETS.
"X.721": "M.3100":
top terminationPoint
"M.3100": "M.3100": userPortTtp isdnBAUserPort
trail- trail-
Termination- Termination- isdnPRAUserPort
PointSource Point-
Bidirectional pstnUserPort
"M.3100":
trail- leasedPort
Termination-
PointSink
"M.3100": "M.3100": userPortBearerChannelCtp
connection- connection-
Termination- Termination-
PointSource Point-
Bidirectional
"M.3100":
connection-
Termination-
PointSink
NOTE: Only classes which are underlined may be instantiated.
Figure 5: Inheritance hierarchy
5.3 Naming hierarchy
Figure 6 shows the naming (i.e. containment) relationships for the AN's managed objects associated with
configuration management.
(accessNetwork)
userPortTtp "ETS 300 377-1": "ETS 300 377-1":
v5Interface v5Ttp
userPortBearerChannelCtp
"ETS 300 377-1":
v5TimeSlot
"ETS 300 377-1": "ETS 300 377-1": "ETS 300 377-1": "ETS 300 377-1":
v5Provision commPath commChannel v5ProtectionGroup
"ETS 300 377-1":
v5ProtectionUnit
Figure 6: Naming hierarchy
Page 18
ETS 300 376-1: December 1994
6 Information model description
This clause provides a high-level informal description of the management information model for
configuration management of the AN.
The principle managed objects for configuration management are logical constructs and do not represent
physical equipment. The relationship between these managed objects and equipment is achieved by using
the supportedByObjectList pointer in the logical managed objects to point to the equipment which supports
them, and by using the affectedObjectList pointer on equipment to point to the logical managed objects
that the equipment implements.
Subclause 6.1 contains a brief description for each object class used in the model covering:
- the purpose of the object class;
- the attributes defined for the object class;
- the relationship of the object class to other object classes.
In the tables listing the attributes of the object classes, the inherited attributes are only mentioned explicitly
if their conditionality has been altered. The other inherited attributes are still present in these classes.
Subclause 6.2 describes attributes which are common to several object classes in the information model.
Subclause 6.3 describes actions which are common to several object classes in the information model.
Subclause 6.4 describes the common aspects of the notifications used in the information model.
6.1 Object class description
Subclause 6.1 is divided into further subclauses which describe the fragments of the information model.
6.1.1 V5 fragment
The object classes of the V5 fragment are described in ETS 300 377-1 [5]. The following classes are used
in the AN:
- V5 interface (v5Interface);
- V5 TTP (v5Ttp);
- V5 time slot (v5TimeSlot);
- V5 provision (v5Provision);
- V5 communication channel (commChannel);
- ISDN communication path (isdnCommPath);
- PSTN communication path (pstnCommPath);
- BCC communication path (bccCommPath);
- control communication path (controlCommPath);
- protection communication path (protCommPath);
- link Control communication path (linkControlCommPath);
- V5 protection group (v5ProtectionGroup);
- V5 protection unit (v5ProtectionUnit).
6.1.2 Access fragment
The following classes are specific to the AN.
6.1.2.1 Access network (accessNetwork)
The definition of this object class is outside the scope of this ETS.

Page 19
ETS 300 376-1: December 1994
6.1.2.2 User port TTP (userPortTtp)
A user port TTP is an object class representing a generic user port on an AN. It is a specialization of the
TTP bidirectional object class defined in CCITT Recommendation M.3100 [11].
In addition to the inherited attributes, it has the attributes given in table 1.
Table 1
Name M/C/O Value set
"M.3100":tTPId M RDN
"X.721":administrativeState M single
"M.3100":operationalState M single
"ETS 300 377-1":assocV5Interface C single
"ETS 300 377-1":blockingStatus C single
6.1.2.3 ISDN Basic Access (BA) user port (isdnBAUserPort)
An ISDN BA user port is an object class representing an ISDN basic user port which is associated with a
V5 interface on an AN. It is a specialization of the user port TTP object class defined in this ETS.
In addition to the inherited attributes, it has the attributes given in table 2.
Table 2
Name M/C/O Value set
"ETS 300 377-1":assocIsdnSignallingCommPath M single
"ETS 300 377-1":assocPacketCommPath M single
"ETS 300 377-1":assocFrameCommPath M single
"ETS 300 377-1":envelopeFunctionAddress M single
accessDigitalSection M single
gradingEnabled C single
accessDigitalSection: indicates whether the NT1 is implemented separately from the AN.
gradingEnabled: indicates for a port with an access digital section whether the grading
messages should be sent to the LE.
6.1.2.4 ISDN Primary Rate Access (PRA) user port (isdnPRAUserPort)
An ISDN PRA user port is an object class representing an ISDN primary rate user port which is associated
with a V5 interface on an AN. It is a specialization of the user port TTP object class defined in this ETS.
In addition to the inherited attributes, it has the attributes given in table 3.

Page 20
ETS 300 376-1: December 1994
Table 3
Name M/C/O Value set
"ETS 300 377-1":assocIsdnSignallingCommPath M single
"ETS 300 377-1":assocPacketCommPath M single
"ETS 300 377-1":assocFrameCommPath M single
"ETS 300 377-1":envelopeFunctionAddress M single
accessDigitalSection M single
gradingEnabled C sing
...