Ets 30037601e01p

EUROPEAN ETS 300 376-1
TELECOMMUNICATION December 1994
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-03013.1
ICS: 33.080
Key words: TMN, information model, Q3 interface, AN, V5 interface, configuration, management
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
New presentation - see History box
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE

Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
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.

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.2 Blocking initiated by the LE ........................................................................................ 52
F.3 Message flows for the mapping of ISDN primary rate access user port states on X.731 states..... 56
F.3.2 Blocking initiated by the LE ........................................................................................ 56
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".

technology - Open systems interconnection - Systems management: State
management function".

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.
1 access 1
Network
1
c
c c
n n
a 1 v5Interface 1 n
a v5Ttp
fragment
1
1 1 1
c c c
n n
n n
commPath a
n 1 commChannel c
a fragment
m n
userPortTtp
1 0,1 0,1
1 a
a a
c
1 0,1,2
v5Protection
fragment 1
n 1 31
(only V5.2) 1
a
1
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.
userPortTtp a v5Interface a v5Ttp

n 1 1 n
0,1,2 n 0,1 n
v5Protection
fragment commPath
fragment v5Provision commChannel
(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
1
isdn a
userPortTtp a commChannel
n 1 CommPath 1
Basic access, Each one instance for:

Primary rate access - Ds-type data
- p-type data
- f-type data
pstn
CommPath 0,1
bcc
CommPath
0,1
(only V5.2)
control
commPath i
CommPath 0,1
linkControl
CommPath
0,1
(only V5.2)
prot v5Protection
CommPath a fragment
1 1
(only V5.2) (only V5.2)
communication path fragment
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
0,1,2
prot 1 1 v5Protection
a
CommPath Group
only protection
group 1
1
protection
c fragment
n (protection group 1: n=2)
comm 0,1 1 v5Protection 1 1

a a v5TimeSlot
Channel Unit
0,1 1
c contains
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.
Table 2

"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.

Page 20
ETS 300 376-1: December 1994
Table 3

"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.5 PSTN user port (pstnUserPort)
A PSTN user port is an object class representing a PSTN 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.
Table 4

"ETS 300 377-1":layer3PortAddress M single
specialFeatures M set
special Features: this attribute indicates whether or not there are any special features at the
PSTN user port and what the features are if they are present.
6.1.2.6 Leased port (leasedPort)
A leased port is an object class representing a generic leased line port on an AN. It is a specialization of
the user port TTP object class defined in this ETS. This object class may contain instances of other objects
which give further details of leased line ports.
Table 5

"ETS 300 377-1":v5UserPortAddress M single
6.1.2.7 User port bearer channel CTP (userPortBearerChannelCtp)
A user port bearer channel CTP is an object class representing a 64 kbit/s bearer channel of a user port. It
is a specialization of the CTP bidirectional object class defined in CCITT Recommendation M.3100 [11].
Page 21
ETS 300 376-1: December 1994
Table 6

"M.3100":cTPId M RDN
assocTimeSlot C single
bearerChannelType C single
"X.721":administrativeState O single
"M.3100":operationalState O single
assocTimeSlot: points to the associated object which represents a time slot at the service
interface to the local exchange or to another service node such as a leased
line network node.
bearerChannelType: indicates whether or not the bearer channel is used for Permanent Line (PL)
access.
6.2 Definition of attributes
The contents of this subclause are identical to subclause 6.2 in ETS 300 377-1 [5].
The attributes specific to this information model are already explained within the object class descriptions.
6.3 Actions description
6.4 Notifications description
7 Formal definitions
This clause gives the formal definitions of the managed object classes, name bindings, general packages,
behaviours, attributes, actions and notifications.
7.1 Definition of managed object classes
This subclause specifies the object classes for all of the managed objects used in the management
information model. These objects are either defined here or by reference to other specifications.
7.1.1 V5 fragment
In this subclause the definitions of the classes of the AN V5 fragment are specified by importing from
ETS 300 377-1 [5]. In this context, the IMPORTS clause specifies the object classes which can be
instantiated in the scope of this ETS. The IMPORTS clause does not include uninstantiated superclasses.
Clarification of the use of the package "CCITT Recommendation M.3100:1992":

tmnCommunicationsAlarmInformationPackage in these imported classes is contained in ETS 300 378-1 [6]
and ETS 300 379-1 [7].
Page 22
ETS 300 376-1: December 1994
BEGIN
IMPORTS
v5Interface,
v5Ttp,
v5TimeSlot,
v5Provision,
commChannel,
isdnCommPath,
pstnCommPath,
bccCommPath,
controlCommPath,
protCommPath,
linkControlCommPath,
v5ProtectionGroup,
v5ProtectionUnit
FROM "ETS 300 377-1";
END
7.1.2 Access fragment
In this subclause, the definitions of the new classes specific to the AN are specified.
7.1.2.1 Access network (accessNetwork)
The definition of this object class is outside the scope of this ETS.
7.1.2.2 User port TTP (userPortTtp)
userPortTtp MANAGED OBJECT CLASS

DERIVED FROM "CCITT Recommendation M.3100:1992":trailTerminationPointBidirectional;
CHARACTERIZED BY
"CCITT Recommendation M.3100:1992":ttpInstancePackage,
"CCITT Recommendation X.721:1992":administrativeStatePackage,
"CCITT Recommendation M.3100:1992":createDeleteNotificationsPackage,
"CCITT Recommendation M.3100:1992":stateChangeNotificationPackage,
"ETS 300 377-1":commonDeleteBehaviourPackage,
userPortTtpPackage PACKAGE
BEHAVIOUR
userPortTtpBehaviour BEHAVIOUR
DEFINED AS "This managed object class represents the generic user port which is
subclassed to create the classes for specific types of user ports. Only subclasses of
userPortTtp are instantiated for ports associated with a V5 interface.
An access port may have assigned one or more bearer time slots and/or one or more
communication paths. The Operational state attribute shall be set to "enabled" as long
as the port has access to any service and there is no other condition to prevent this.
The Operational state attribute shall be set to "disabled" if an access port has no
service at all."
;;
NOTIFICATIONS
"ETS 300 377-1":shutdownRejected;
;;
CONDITIONAL PACKAGES
blockingStatusPackage PRESENT IF "blocking status is recorded at the port",
assocV5InterfacePackage PRESENT IF "user port is associated with a V5 interface",
"ETS 300 377-1":qualityOfServiceAlarmPackage
PRESENT IF "there is an access digital section or if
performance parameters are to be monitored against a
pre-defined threshold";
REGISTERED AS {managedObjectClass 1};
Page 23
ETS 300 376-1: December 1994
7.1.2.3 ISDN BA user port (isdnBAUserPort)
isdnBAUserPort MANAGED OBJECT CLASS

DERIVED FROM userPortTtp;
CHARACTERIZED BY
assocCommPathsPackage,
isdnBAUserPortPackage PACKAGE
BEHAVIOUR
isdnBAUserPortBehaviour BEHAVIOUR
DEFINED AS "This managed object class represents an ISDN basic user port which is
associated with a V5 interface on an AN. It can contain up to 2 instances of
userPortBearerChannelCtp."
;;
ATTRIBUTES
"ETS 300 377-1":envelopeFunctionAddress GET-REPLACE,
accessDigitalSection GET;
;;
gradingEnabledPackage PRESENT IF "there is an access digital section for the port";
7.1.2.4 ISDN PRA user port (isdnPRAUserPort)
isdnPRAUserPort MANAGED OBJECT CLASS

CHARACTERIZED BY
assocCommPathsPackage,
isdnPRAUserPortPackage PACKAGE
BEHAVIOUR
isdnPRAUserPortBehaviour BEHAVIOUR
DEFINED AS "This managed object class represents an ISDN primary rate user port
which is associated with a V5 interface on an AN. It can contain up to 30 instances of
userPortBearerChannelCtp."
;;
ATTRIBUTES
"ETS 300 377-1":envelopeFunctionAddress GET-REPLACE,
accessDigitalSection GET;
;;
gradingEnabledPackage PRESENT IF "there is an access digital section for the port";
7.1.2.5 PSTN user port (pstnUserPort)
pstnUserPort MANAGED OBJECT CLASS

CHARACTERIZED BY
pstnUserPortPackage PACKAGE
BEHAVIOUR
pstnUserPortBehaviour BEHAVIOUR
DEFINED AS "This managed object class represents a PSTN user port which is
associated with a V5 interface on an AN. In addition to the specialFeatures attribute,
additional information about PSTN user ports may be modelled by objects contained in
instances of pstnUserPort."
;;
ATTRIBUTES
"ETS 300 377-1":layer3PortAddress GET-REPLACE,
specialFeatures
DEFAULT VALUE ASN1DefinedTypesModule.defaultSpecialFeatures
GET-REPLACE ADD-REMOVE;
Page 24
ETS 300 376-1: December 1994
;;
7.1.2.6 Leased port (leasedPort)
This object class is used to model the generic characteristics of leased line ports which are associated
with a V5 interface. Additional details of leased ports may be given in objects which are contained in
instances of this class.
leasedPort MANAGED OBJECT CLASS

CHARACTERIZED BY
leasedPortPackage PACKAGE
BEHAVIOUR
leasedPortBehaviour BEHAVIOUR
DEFINED AS "Instances of leasedPort represents the generic form of leased line
ports, which are defined as ports which do not have on demand signalling. Leased line
ports which are related to V5 interfaces can only have their 64 kbit/s bearer channels
connected to the host exchange via the V5 interface.
Instances of this class do not differentiate between analogue and digital leased line
ports, but they do differentiate between ports which have a single bearer channel
connected via the V5 interface and ports which have more than one channel connected
via the V5 interface.
The v5UserPortAddress attribute has the value of the layer 3 port address on the V5
interface if a single bearer channel at the port is connected via the V5 interface. The
attribute has the value of the layer 2 port address on the V5 interface if more than one
bearer channel at the port is connected via the V5 interface. In either case the value
should not be the same as that used for any PSTN or ISDN port.
Additional information concerning specific types of leased port may be added by
containing an additional object within this object or by making use of connectivity
pointers in contained channel objects."
;;
ATTRIBUTES
"ETS 300 377-1":v5UserPortAddress GET-REPLACE;
;;
7.1.2.7 User port bearer channel CTP (userPortBearerChannelCtp)
userPortBearerChannelCtp MANAGED OBJECT CLASS

DERIVED FROM "CCITT Recommendation M.3100:1992":connectionTerminationPointBidirectional;
CHARACTERIZED BY
"CCITT Recommendation M.3100:1992":ctpInstancePackage,
"CCITT Recommendation M.3100:1992":createDeleteNotificationsPackage,
"ETS 300 377-1":commonDeleteBehaviourPackage,
userPortBearerChannelCtpPackage PACKAGE
BEHAVIOUR
userPortBearerChannelCtpPackage BEHAVIOUR
DEFINED AS "This managed object class represents the point where a 64 kbit/s
bearer channel is terminated. The connectivity pointers of instances of
userPortBearerChannelCtp may be used to extend the modelling, but are otherwise
null.
The cTPId attribute is used to number the channels consecutively from 1."
;;
;;
assocTimeSlotPackage PRESENT IF "the bearer channel has a call-independent
association with a specific time slot at the interface to the
local exchange or at the interface to some other service node
such as a leased line network.",
Page 25
ETS 300 376-1: December 1994
bearerChannelTypePackage PRESENT IF "the bearer channel is contained in an ISDN port

which can support PL service",
"CCITT Recommendation X.721:1992":administrativeStatePackage
PRESENT IF "an instance supports it",
"CCITT Recommendation M.3100:1992":stateChangeNotificationPackage
PRESENT IF "administrativeStatePackage is present";
7.2 Name bindings
This subclause specifies the new name bindings for the managed objects used in the management
information model.
7.2.1 V5 interface (v5Interface)
This name binding is not specified here.
7.2.2 V5 TTP (v5Ttp)
7.2.3 User port TTP (userPortTtp)
7.2.4 User port Bearer channel CTP (userPortBearerChannelCtp)
userPortBearerChannelCtp-userPortTtp NAME BINDING

SUBORDINATE OBJECT CLASS userPortBearerChannelCtp AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS userPortTtp AND SUBCLASSES;
WITH ATTRIBUTE cTPId;
CREATE;
DELETE ONLY-IF-NO-CONTAINED-OBJECTS;
REGISTERED AS {nameBinding 1};
7.3 Definition of packages
This subclause specifies new general packages.
7.3.1 Associated communication paths (assocCommPathsPackage)
assocCommPathsPackage PACKAGE
BEHAVIOUR
assocCommPathsPackageBehaviour BEHAVIOUR
DEFINED AS
"The assocIsdnSignallingCommPath attribute points to the associated ISDN Communication
Path carrying the signalling messages of the assigned ISDN access.
The assocPacketCommPath attribute points to the associated ISDN Communication Path
carrying the D-channel packet mode data of the assigned ISDN access, if the customer has
subscribed to this service. Else, it has NULL value.
The assocFrameCommPath attribute points to the associated ISDN Communication Path
carrying the D-channel frame mode data of the assigned ISDN access, if the customer has
subscribed to this service. Else, it has NULL value.
These are group relationships according to CCITT Recommendation X.732 [18]. The ISDN
Communication Path is the owner in each case. The relationships are maintained by the use
of the setReciprocalPointers and releaseReciprocalPointers actions of the related v5Interface
object class."
;;
Page 26
ETS 300 376-1: December 1994
ATTRIBUTES
"ETS 300 377-1":assocIsdnSignallingCommPath GET,
"ETS 300 377-1":assocPacketCommPath GET,
"ETS 300 377-1":assocFrameCommPath GET;
REGISTERED AS {package 1};
7.3.2 Associated V5 interface (assocV5InterfacePackage)
assocV5InterfacePackage PACKAGE
BEHAVIOUR
assocV5InterfacePackageBehaviour BEHAVIOUR
DEFINED AS
"The assocV5Interface attribute points to the related V5 interface. It is a group relationship
according to CCITT Recommendation X.732 [18]. The V5 interface is the owner object. The
relationship with the V5 interface is maintained by the use of the setReciprocalPointers and
releaseReciprocalPointers actions of the v5Interface object class."
;;
ATTRIBUTES
"ETS 300 377-1":assocV5Interface GET;
7.3.3 Associated time slot (assocTimeSlotPackage)
assocTimeSlotPackage PACKAGE
BEHAVIOUR
assocTimeSlotPackageBehaviour BEHAVIOUR
DEFINED AS
"The assocTimeSlot attribute points to the related time slot on a V5 interface or other service
interface. It is a peer relationship according to CCITT Recommendation X.732 [18]. The
relationship with a time slot on a V5 interface is maintained by the use of the
setReciprocalPointers and releaseReciprocalPointers actions of the related v5Interface object
class."
;;
ATTRIBUTES
assocTimeSlot GET;
7.3.4 Bearer channel type (bearerChannelTypePackage)
bearerChannelTypePackage PACKAGE
ATTRIBUTES
bearerChannelType GET-REPLACE;
7.3.5 Blocking status (blockingStatusPackage)
blockingStatusPackage PACKAGE
ATTRIBUTES
"ETS 300 377-1":blockingStatus GET;
7.3.6 Grading enabled (gradingEnabledPackage)
gradingEnabledPackage PACKAGE
ATTRIBUTES
gradingEnabled GET-REPLACE;
Page 27
ETS 300 376-1: December 1994
7.4 Definition of behaviours
No new general behaviours need to be defined in this ETS.
7.5 Definition of attributes
This subclause specifies new general attributes.
7.5.1 Associated time slot (assocTimeSlot)
assocTimeSlot ATTRIBUTE
WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.Pointer;
MATCHES FOR EQUALITY;
BEHAVIOUR
assocTimeSlot BEHAVIOUR
DEFINED AS "This attribute points to an object representing the associated time slot."
;;
REGISTERED AS {attribute 1};
7.5.2 Bearer channel type (bearerChannelType)
bearerChannelType ATTRIBUTE
WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.BearerChannelType;
BEHAVIOUR
bearerChannelType BEHAVIOUR
DEFINED AS "This attribute indicates whether or not the bearer channel is used for PL
access."
;;
7.5.3 Grading enabled (gradingEnabled)
gradingEnabled ATTRIBUTE
WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.GradingEnabled;
BEHAVIOUR
gradingEnabledBehaviour BEHAVIOUR
DEFINED AS "This attribute allows grading messages to the LE to be enabled and disabled
for ISDN ports with an access digital section."
;;
7.5.4 Access digital section (accessDigitalSection)
accessDigitalSection ATTRIBUTE
WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.AccessDigitalSection;
BEHAVIOUR
accessDigitalSectionBehaviour BEHAVIOUR
DEFINED AS "This attribute indicates whether or not there is an access digital section at an
ISDN port."
;;
Page 28
ETS 300 376-1: December 1994
7.5.5 Special feature (specialFeatures)
specialFeatures ATTRIBUTE
WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.SpecialFeatures;
MATCHES FOR EQUALITY, SET-COMPARISON, SET-INTERSECTION;
BEHAVIOUR
specialFeaturesBehaviour BEHAVIOUR
DEFINED AS "This attribute indicates whether or not there are special features and if so what
they are. It has a default value of the empty set which indicates that there are no special
features."
;;
7.6 Definition of actions
No new general actions need to be defined in this ETS.
7.7 Definition of notifications
No new general notifications need to be defined in this ETS.
7.8 ASN.1 defined types module
Table 7
ASN1DefinedTypesModule {ccitt(0) identified-organization(4) etsi(0) v5AnConfigurationManagement(376)

informationModel(0) asn1Module(2) asn1DefinedTypesModule(0)}
DEFINITIONS IMPLICIT TAGS ::=
BEGIN -- EXPORTS everything
IMPORTS
ObjectInstance
FROM CMIP-1 {joint-iso-ccitt ms(9) cmip(1) version1(1) protocol(3)};
informationModel OBJECT IDENTIFIER ::= {ccitt(0) identified-organization(4) etsi(0)

v5AnConfigurationManagement(376) informationModel(0)}
standardSpecificExtension OBJECT IDENTIFIER ::= {informationModel standardSpecificExtension(0)}
managedObjectClass OBJECT IDENTIFIER ::= {informationModel managedObjectClass(3)}
package OBJECT IDENTIFIER ::= {informationModel package(4)}
nameBinding OBJECT IDENTIFIER ::= {informationModel nameBinding(6)}
attribute OBJECT IDENTIFIER ::= {informationModel attribute (7)}
action OBJECT IDENTIFIER ::= {informationModel action(9)}
notification OBJECT IDENTIFIER ::= {informationModel notification(10)}
defaultSpecialFeatures SpecialFeatures ::= {}
AccessDigitalSection ::= ENUMERATED {

absent (0),
present (1)}
Page 29
ETS 300 376-1: December 1994
Table 7 (concluded)
BearerChannelType ::= ENUMERATED {

non-PL-channel (0),
pL-channel (1)}
GradingEnabled ::= ENUMERATED {

disabled (0),
enabled (1)}
Pointer ::= ObjectInstance
SpecialFeature ::= ENUMERATED {

directDiallingIn (0),
publicTelephone (1),
privateMeter (2),
specialLoopResistance (3),
securityLine (4),
other (5)}
SpecialFeatures ::= SET OF SpecialFeature
END -- of ASN1DefinedTypesModule
8 Protocol requirements
Protocol stacks are specified in ITU-T Recommendations Q.811 [12], Q.812 [13], G.773 [8] and the SDH
Data Communications Channel (DCC) part of CCITT Recommendation G.784 [9]. No special requirements
are identified.
NOTE: In addition, it will be possible to use 64 kbit/s bearer channels and p-type and f-type
data channels on a V5 interface. These will act as virtual user ports (see
ETS 300 324-1 [3]) and the initial port addresses cannot be configurable over the Q3
interface of the AN. Layer 1 and the envelope part of layer 2 of the V5 interface will be
used for the lower layers of the protocol stack, but the higher layers will be the same
as the stacks already specified in this clause. The initial configuration of a V5 interface
to enable the use of 64 kbit/s bearer channels and p-type and f-type data channels
may be through pre-definition of a default configuration or using a local craft interface.
Page 30
ETS 300 376-1: December 1994
Annex A (normative): Mapping of V5 user port states on X.731 states
This annex defines the mapping of PSTN user ports, ISDN basic access user ports and ISDN primary rate
user ports on CCITT Recommendation X.731 [17] states, including the case of permanent line capability.
A.1 Mapping of V5 PSTN user port states on X.731 states
State transition table A.1 shows the mapping of the V5 PSTN user port states on CCITT Recommendation
X.731 [17] operational and administrative states.
The locked/enabled state means that the port has been locked by the Q3 interface of the AN and that
there are no local fault conditions.
In the "locked" state the operational state attribute only reflects AN internal failures, i.e. "enabled" means
no AN fault and "disabled" means AN fault regardless of any knowledge about the LE side.
However, in the "unlocked" state the operational state attribute is changed from "enabled" to "disabled"
due to AN fault or blocking by the LE. There the information about the presence of a local or access
disabling reason needs to be available. A "local reason" entry is made when a "port-not-ok" message is
received and removed when a "port-ok" messages arrives. A "remote reason" entry is made when MPH-BI
is received and removed when MPH-UBR arrives. State 4 is also entered as part of the unblocking
procedure if the OS sent UNLOCK to the port object and an acknowledgement from the LE needs to be
awaited.
Table A.1
state 1 state 2 state 3 state 4 state 5

locked locked shutting down unlocked unlocked
disabled enabled disabled enabled
LOCK - - MPH-BI; 2 no local reason: MPH-BI; 2
MPH-BI; 2
else:
MPH-BI; 1
UNLOCK ;4 MPH-UBR; 4 MPH-UBR; 5 - -
SHUTDOWN / / - no local reason: MPH-BR; 3
MPH-BI; 2
else:
MPH-BI; 1
MPH-BI -; -; -; 2 -; -; 4
MPH-UBR -; -; MPH-BR; no local reason: /
MPH-UBR;
else:
-;
MPH-UBI / / - -; -
5
Port-ok -; 2 / / MPH-UBR; /
Port-not-ok / -; 1 MPH-BI; 1 MPH-BI; MPH-BI; 4
Key: <output signal>;<new state>
/ = unexpected event
- = no action
Disabling reasons
Local:
Port-ok: disappearance/not existence of internal disabling reasons;
Port-not-ok: occurrence/presence of internal disabling reasons.
Remote:
MPH-BI: LE reason for blocking the port due to failure or management decision;
MPH-UBR: disappearance of an LE reason for blocking the port.
Page 31
ETS 300 376-1: December 1994
Sources of messages
LOCK, UNLOCK, SHUTDOWN are generated by the OS. MPH-BI, MPH-UBR, MPH-UBI are generated by
the user port FSM. Port-ok, Port-not-ok are generated by an internal management entity, e.g. a resource
manager, see figure A.1.
OS
LOCK
UNLOCK
SHUTDOWN
System
Management
PSTN Port Object

Port-ok
state attributes Resource
Port-not-ok Manager
see table A.1
PSTN Port FSM
NOTE: This figure is for information only.
Figure A.1: General relationship between the PSTN port object and system management
A.2 Mapping of V5 ISDN basic access user port states on X.731 states
State transition table A.2 shows the mapping of the V5 ISDN basic access user port states on CCITT
Recommendation X.731 [17] operational and administrative states.
It covers both the use of the port for on-demand service and (partial or full) permanent line service. In
table A.2 two variables are used for determining the transitions in case of permanent line service. PLp is
TRUE if the port is used for PL service. PLa is TRUE if the port FSM is in one of the AN3.x PL activation
states.
In the "locked" state the operational state attribute reflects only AN internal failures, i.e. "enabled" means
due to AN fault or blocking by the LE. There the information about the presence of a local or remote
disabling reason needs to be available. A "local reason" entry is made when an internal disabling reason
occurs and is removed when there is no internal reason for being disabled. A "remote reason" entry is
made when MPH-BI is received and removed when MPH-UBR arrives. This information can be stored in
the blockingStatus attribute of the port object. State 4 is also entered as part of the unblocking and
activation procedure if the OS sends UNLOCK to the port object and an acknowledgement from the LE
needs to be awaited.
Page 32
ETS 300 376-1: December 1994
Table A.2: State table for ISDN port object state attributes

locked locked shutting unlocked unlocked
disabled enabled down disabled enabled
LOCK - - MPH-BI; 2 (if PLa: MPH-DR; if PLa: MPH-DR; 2
else: MPH-BI, else: MPH-BI; 2
(if TPL1 running:
stop TPL1)),
if no local reason:
-; 2
else: -; 1
UNLOCK -;4 MPH-UBR, MPH-UBR; 5 - -
(if PLp: start TPL1); 4
SHUTDOWN / / - if PLa: / if PLp: /
else: else: MPH-BR; 3
(if TPL1 running:
stop TPL1),
(if no local reason:
MPH-BI; 2
else: MPH-BI; 1)
expiry of TPL1 / / / if PLp: /
MPH-AR,;
else: /
MPH-BI -; -; -; 2 -; if PLa: /
else:
(if PLp: MPH-AR); 4
MPH-UBR -; -; / no local reason: /
MPH-UBR;
else: -
MPH-UBI / / SHUTDOWNRej; (if TPL1 running: if PLa: /
stop TPL1);5 else: -;
MPH-T1 / / - if PLa:-; if PLa: /
else: / else: -;
MPH-I1 / / - / if PLa: /
else: -;
MPH-I2 MPH-DR; MPH-DR; - if PLa: / if PLa: /
else: MPH-DR; else: -;
MPH-DSAI MPH-DR; MPH-DR; - if PLa:- if PLa: /
else: MPH-DR; else: -;
MPH-AI MPH-DR; MPH-DR; - if PLa: / -
else: MPH-DR;
MPH-I5 / / - / if PLa: /
else: -;
MPH-DI - - - - -
MPH-EI7 MPH-DR; MPH-DR; - if PLa: - -
else: MPH-DR;
MPH-PAI / / / if PLa: -; 5 if PLa: -
else: / else: /
MPH-EI12 MPH-DR; MPH-DR; - if PLa: / -
else: MPH-DR;
disappearance of -; 2 / / MPH-UBR, /
internal disabling (if PLp: start TPL1);
reasons
occurrence of - -; 1 MPH-BI; if PLa: MPH-DR; if PLa: MPH-DR; 4
internal disabling 1 else: else: MPH-BI; 4
reasons (if TPL1 running:
stop TPL1),
MPH-BI;
Key: <action>[,<action>][,(<action>)];<new state>
- = no action
no local reason: blockStatus = none or blockStatus = remote
PLp = Permanent Line provisioned
PLa = TRUE if the ISDN port FSM is in PL state AN3.1 or AN3.2. The variable is updated by the system
management.
Page 33
ETS 300 376-1: December 1994
Assumptions
1) PLa = TRUE means ISDN port FSM is in state AN3.x.
2) PLp = TRUE means at least one B-channel is provisioned as permanent line.
3) An unlocked enabled port provisioned for permanent line service rejects a SHUTDOWN from the
OS. LOCK should be used to take this port out of service.
4) In case of a port without PL, the activation and deactivation status of layer 1 does not affect the
enabled state. This status can be stored e.g. in an activation variable, not visible to the OS.
5) If the port object is in state 1 or 2, the ISDN port FSM is in one of AN1.x, or AN4.x, respectively. If
the port object is in state 3, the ISDN port FSM is in an AN2.x state. If the port object is in state 4,
the ISDN port FSM is in an AN1.x state or in AN3.1. If the port object is in state 5, the ISDN port
FSM is in an AN2.x state, or in AN3.2.
6) If a port is provisioned for PL services, it is assumed to be enabled if layer 1 is activated,

independent of the blocking status, which is relevant for on demand services.
7) The usual way to activate a port provisioned for PL is to send an unblock request (FE202) to the LE,
which takes over responsibility for activating layer 1 after unblocking the port (see
ETS 300 324-1 [3], subclause 14.1.3.1). This is reflected in MPH-AR being an unexpected event in
state AN1.2 and AN2.0. A timer TPL1 is used to supervise this unblock procedure. If the LE does
not respond within an appropriate time the AN becomes responsible for the activation of layer 1 and
issues MPH-AR.
8) If a port provisioned for PL services is in the unlocked/enabled state and is blocked by the LE, the
AN immediately starts re-activation of layer 1 by issuing MPH-AR and the port becomes enabled
again after the successful activation. A short interruption of the PL service can be expected.
9) In case of semi-permanent connections the LE will reject a shutdown request (MPH-BR, FE205)
from the AN by sending an unblock request (FE201, MPH-UBI). The OS of the AN shall then be
notified to change the administrative state from SHUTTINGDOWN back to UNLOCKED.
10) Partial activation (states AN5.x) is not covered.
Disabling reasons
Local: occurrence/presence of internal disabling reasons, e.g. bit error rate ≥ 10-3.
Remote: MPH-BI: LE reason for blocking the port due to failure or management decision.
Enabling reasons
Local: disappearance/non-existence of internal disabling reasons, e.g. bit error rate < 10 -3.
Remote: MPH-UBR: disappearance of an LE reason for blocking the port.
Sources of messages
LOCK, UNLOCK, SHUTDOWN are generated by the OS. SHUTDOWNRej is sent from the ISDN port
object to the OS. MPH-BI, MPH-UBR, MPH-UBI, MPH-T1, MPH-I1, MPH-I2, MPH-DSAI, MPH-AI, MPH-
I5, MPH-DI, MPH-EI7, MPH-DB, MPH-DU, MPH-PAI, MPH-EI12 are generated by the user port FSM.
Internal disabling reasons are detected, e.g. by a resource manager, see figure A.2.
Page 34
ETS 300 376-1: December 1994
OS
LOCK
grading
UNLOCK SHUTDOWNRej
enabled/
SHUTDOWN
disabled
System
Management
ISDN BA Port Object

enable (Note 1)
disable Manager
MPH-GI see table A.2
ISDN BA Port FSM
NOTE 1: enable: disappearance of internal disabling reasons;

disable: occurrence of internal disabling reasons.
NOTE 2: This figure is for information only.
Figure A.2: Management entities controlling the ISDN port FSM
Port maintenance
Loopback tests (states AN4.x) can only be applied while the port is locked by the OS. These tests are not
covered by the state mapping table A.2.
A.3 Mapping of V5 ISDN primary rate access user port states on X.731 states
State transition table A.3 shows the mapping of the V5 ISDN primary rate user port states on CCITT
Recommendation X.731 [17] operational and administrative states.
It covers both the use of the port for on-demand service and (partial or full) permanent line service. In
table A.3 two variables are used for determining the transitions in case of permanent line service. PLp is
TRUE if the port is used for PL service. PLa is TRUE if the port FSM is in the AN3.0 PL activation state.
In the "locked" state the operational state attribute reflects only AN internal failures, i.e. "enabled" means
due to AN fault or blocking by the LE. There the information about the presence of a local or remote
disabling reason needs to be available. A "local reason" entry is made when an internal disabling reason
occurs and is removed when there is no internal reason for being disabled. A "remote reason" entry is
made when MPH-BI is received and removed when MPH-UBR arrives. This information can be stored in
the blockingStatus attribute of the port object. State 4 is also entered as part of the unblocking and
activation procedure if the OS sends UNLOCK to the port object and an acknowledgement from the LE
needs to be awaited.
Page 35
ETS 300 376-1: December 1994
Table A.3: State table for ISDN primary rate access port object state attributes

locked locked shutting unlocked unlocked
disabled enabled down disabled enabled
LOCK - - MPH-BI; 2 MPH-BI, MPH-BI; 2
(if TPL1 running:
stop TPL1),
if no local reason:
-; 2
else: -; 1
UNLOCK -; 4 MPH-UBR, MPH-UBR; 5 - -
(if PLp: start TPL1); 4
SHUTDOWN / / - if PLp: / if PLp: /
else: else: MPH-BR; 3
(if TPL1 running:
stop TPL1),
MPH-BI,
(if no local reason:
-; 2
else: -; 1)
expiry of TPL1 / / / if PLp: /
MPH-PAR;
else: /
MPH-BI -; -; -; 2 if (no local reason if PLa: -
AND PLp): else:
MPH-UBR, (if PLp:
start TPL1; MPH-UBR,
else: - start TPL1); 4
(note) (note)
MPH-UBR -; -; / if no local reason: /
MPH-UBR;
else: -
MPH-UBI / / SHUTDOWNRej (if TPL1 running: -
stop TPL1); 5
MPH-PAI / / / if PLp: -; 5 if PLa: -
else: / else: /
disappearance of -; 2 / / MPH-UBR, /
internal disabling (if PLp: start TPL1);
reasons
occurrence of / -; 1 MPH-BI; 1 (if TPL1 running: MPH-BI; 4
internal disabling stop TPL1),
reasons MPH-BI;
Key: <action>[,<action>][,(<action>)];<new state>
- = no action
no local reason: blockStatus = none or blockStatus = remote
PLp = Permanent Line provisioned.
PLa = TRUE if the ISDN port FSM is in PL state AN3.0. The variable is updated by the system
management
NOTE: MPH-UBR moves the port into local unblock which is necessary to reach AN3.0 in case of permanent lines provisioned.
Subsequently MPH-PAR is issued on expiry of timer TPL1.
Assumptions
1) PLa = TRUE means ISDN port FSM is in state AN3.0.
2) PLp = TRUE means at least one B-channel is provisioned as permanent line.
3) An unlocked enabled port provisioned for permanent line service rejects a SHUTDOWN from the
OS. LOCK should be used to take this port out of service.
4) If the port object is in state 1 or 2 the ISDN port FSM is in one of AN1.0x, or AN4.x, respectively. If
the port object is in state 3 the ISDN port FSM is in AN2.0. If the port object is in state 4 the ISDN
port FSM is in one of the AN1.x states. If the port object is in state 5 the ISDN port FSM is in
AN2.0, or in AN3.0.
Page 36
ETS 300 376-1: December 1994
5) If a port provisioned for PL services is in the unlocked/enabled state and is blocked by the LE, the
AN immediately starts re-activation of layer 1 by issuing MPH-UBR and MPH-PAR, and the port
becomes enabled again after the successful activation. A short interruption of the PL service can be
expected.
6) In case of semi-permanent connections the LE will reject a shutdown request (MPH-BR, FE205)
from the AN by sending an unblock request (FE201, MPH-UBI). The OS of the AN shall then be
notified to change the administrative state from SHUTTING DOWN back to UNLOCKED.
Disabling reasons
Local: occurrence/presence of internal disabling reasons, e.g. MPH-EIlos, MPH-EIc, etc.;

bit error rate ≥ 10-3.
Remote: MPH-BI: LE reason for blocking the port due to failure or management decision.
Enabling reasons
Local: disappearance/not existence of internal disabling reasons, e.g. MPH-NOF; bit error
rate < 10-3.
Remote: MPH-UBR: disappearance of an LE reason for blocking the port.
Sources of messages
LOCK, UNLOCK, SHUTDOWN are generated by the OS. SHUTDOWNRej is sent from the ISDN port
object to the OS. MPH-BI, MPH-UBR, MPH-UBI, MPH-PAI are generated by the user port FSM. Internal
disabling reasons are detected, e.g. by a resource manager, see figure A.3.
OS
LOCK
grading
UNLOCK SHUTDOWNRej
enabled/
SHUTDOWN
disabled
System
Management
ISDN PRA Port Object

enable (Note 1)
disable Manager
MPH-GI see table A.3
ISDN PRA Port FSM
NOTE 1: enable: disappearance of internal disabling reasons ;

disable: occurrence of internal disabling reasons.
NOTE 2: This figure is for information only.
Figure A.3: Management entities controlling the ISDN PRA port FSM
Port maintenance
Loopback tests (states AN4.x) can only be applied while the port is locked by the OS. Theses tests are
not covered by the state mapping table A.3.
Page 37
ETS 300 376-1: December 1994
Annex B (normative): Mapping of link control states on X.731 states
The mapping of link control states on X.731 states for the AN is described in annex B of
ETS 300 377-1 [5].
Page 38
ETS 300 376-1: December 1994
Annex C (normative): TMN management service "V5 related configuration at

the AN"
C.1 Task Information Base (TIB) A
C.1.1 Description
The task requirements relate either to the V5 interfaces, or to the user ports, or arise from more general
considerations.
C.1.2 Components of service
C.1.2.1 General requirements
These are the general requirements for the configuration management of V5 interfaces and related user
ports via the Q3 interface of an AN.
C.1.2.1.1 Association of user ports with V5 interfaces
All relevant bearer channels and non-bearer communication of a user port shall go through one V5
interface. The association of user ports and their relevant bearer channels with V5 interfaces are controlled
via the Q3 interface of the AN.
C.1.2.1.2 Information flow across the Q3 interface
All data for provisioning, including modification and cessation, of V5 interfaces and related user ports shall
be handled by the Q3 interface of the AN. This includes the relevant data for the user interface (for
example line circuit parameters).
The information flow for inventory and auditing functions in the AN shall be via the Q3 interface of the AN
using a generic approach.
C.1.2.1.3 Compatibility between AN and LE
The TMN function has the responsibility for ensuring that the configuration of the LE and of the AN are
compatible.
C.1.2.1.4 Configuration of bearer channels
Dynamic configuration of bearer channels (B-channels) via BCC for V5.2 is handled by the V5 interface and
is not the concern of the Q3 interface of the AN. The configuration of bearer channels on the V5.1 interface
is seldom changed and is handled over the Q3 interface of the AN.
C.1.2.2 V5 interface requirements
These are the requirements for the configuration management of V5 interfaces via the Q3 interface of an
AN.
C.1.2.2.1 V5 interface and link IDs
The Q3 interface on the AN shall define both the interface ID and the link IDs for each V5 interface. These
should be consistent with the fields allocated in the V5 interface specification (ETS 300 324-1 [3] and
ETS 300 347-1 [4], respectively).
C.1.2.2.2 Provisioning variant
The Q3 interface on the AN may optionally define the provisioning variant label for each V5 interface. This
should be consistent with the fields allocated in the V5 interface specification.
Page 39
ETS 300 376-1: December 1994
C.1.2.2.3 Channel configuration
The channel configuration related to the allocation of appropriate channels to p-type data, f-type data,
operations and maintenance, BCC, and PSTN and ISDN signalling on the V5 interface shall be performed
via the Q3 interface of the AN as part of provisioning.
C.1.2.2.4 Association of interfaces with exchanges
The Q3 interface of the AN is responsible for bringing up and taking down V5 interfaces as part of
associating them with LEs.
C.1.2.2.5 Standby operation
The Q3 interface of the AN should be able to support stand-by of a V5 interface.
The support of 2 Mbit/s standby for V5.1 does not create any additional requirements for the information
model.
For V5.2, there are additional requirements due to the protection protocol, and these may impact the
configuration model.
C.1.2.2.6 Persistency checking
The parameters for the persistence checking procedure for error detection should be set through the Q3
interface of the AN.
C.1.2.2.7 Global PSTN parameters
The Q3 interface of the AN shall support the provisioning of global parameters such as timers, cadencing
etc., which are related to PSTN services supported by the V5 interface and associated user ports.
C.1.2.3 User port requirements
These are the requirements for the configuration management of user ports via the Q3 interface of an AN.
C.1.2.3.1 Operational threshold
The Q3 interface of the AN is responsible for defining the threshold at which a user port is no longer
operational for any service. If this does not involve a change during the lifetime of the equipment then it
should not be supported by the Q3 interface.
C.1.2.3.2 Port blocking
The Q3 interface of the AN can request that a port be blocked for non-urgent configuration or
reconfiguration. If the port is routed through a V5 interface to a LE then this request can only be granted
by the LE via the V5 interface. This is intended to avoid interference with calls in progress, or calls being
set up or cleared down.
The Q3 interface on the AN can request that a port be blocked for urgent configuration or reconfiguration.
If the port is routed through a V5 interface to a LE the other side of the interface shall be informed of this
blocking via the V5 interface.
C.1.2.3.3 User port addresses
Addressing information which identify user ports is assigned to the ports during provisioning via the Q3
interface of the AN.
Page 40
ETS 300 376-1: December 1994
C.1.2.3.4 Split ISDN ports
The Q3 interface of the AN can be used to configure an ISDN user port so that channels on that port can
be split between the LE and leased lines which bypass the LE.
The TMN function has the responsibility of ensuring that the LE is informed about the availability of the B-
channels on the user ports for services under the control of the LE.
C.1.2.3.5 User requirements
The Q3 interface has the responsibility of provisioning user port related to the V5 interface according to the
requirements of the user.
C.1.2.3.6 ISDN with access digital sections
The Q3 interface shall be capable of supporting the communication associated with functional elements as
specified in ETS 300 297 [2] (based on ITU-T Recommendation G.960) that are not communicated over
the V5 interface.
C.1.2.3.7 Port specific PSTN parameters
The Q3 interface of the AN shall support the provisioning of port specific parameters such as timers,
cadencing etc., which are related to PSTN services supported by the V5 interface and associated user
ports.
C.2 Management function list
The management functions relate mostly to the TMN management service for customer access. The
functions are associated with the user ports, the V5 interface, or the cross-connection between the two.
There are create and read functions in each of the three groups. There are insert and delete functions for
the user ports and for V5 interfaces, and these are matched by the establish and de-establish functions for
cross-connection.
C.2.1 User port functions
The user port functions are "insert", "delete", "modify" and "read".
C.2.1.1 Insert a user port
The Insert User Port function performs the following actions:
- assign port address;

- assign port type;
- assign port specific parameters.
C.2.1.2 Delete a user port
The Delete User Port function deletes the user port, including the items listed for the Insert User Port
function defined in subclause C.2.1.1.
C.2.1.3 Modify a user port
It may not be appropriate to modify certain items relating to user ports unless the port is blocked. The
Modify User Port function can be used to block and unblock ports and to modify the items, other than port
address, listed for the Insert User Port function defined in subclause C.2.1.1.
Page 41
ETS 300 376-1: December 1994
C.2.1.4 Read a user port
The Read User Port function reads any of the items listed for the Insert User Port function defined in
subclause C.2.1.1.
C.2.2 V5 interface functions
The V5 interface functions are "insert", "delete", "modify" and "read".
C.2.2.1 Insert a V5 interface
The Insert V5 interface function performs the following actions:
- assign interface ID;

- assign provisioning variant;
- assign grading thresholds;
- assign number of 2 Mbit/s links;
- define persistency checking;
- reserve time slots for communication channels;
- allocate communication channels.
C.2.2.2 Delete a V5 interface
The Delete V5 interface function deletes the V5 interface, including the items listed for the Insert V5
interface function defined in subclause C.2.2.1.
C.2.2.3 Modify a V5 interface
The Modify V5 interface function modifies one of the items, other than interface ID, listed for the Insert V5
interface function defined in subclause C.2.2.1. This function can be used to activate a change in
provisioning on either side of a V5 interface.
C.2.2.4 Read a V5 interface
The Read V5 interface function reads any of the items listed for the Insert V5 interface function defined in
subclause C.2.2.1. This function can be used to read interface ID and provisioning variant information from
the other side of the V5 interface.
C.2.3 Cross-connection functions
The cross-connection functions are "establish", "de-establish", "modify" and "read".
C.2.3.1 Establish a connection
The Establish Connection function performs the following actions:
- assign access port to V5 interface, including V5 port address;

- assign port bearer channel to V5 bearer channel;
- assign PSTN signalling to V5 communication channel;
- assign ISDN Ds-type data to V5 communication channel;
- assign ISDN p-type data to V5 communication channel;
- assign ISDN f-type data to V5 communication channel.
C.2.3.2 De-establish a connection
The De-establish Connection function removes a connection which has been established by the Establish
Connection function defined in subclause C.2.3.1.
Page 42
ETS 300 376-1: December 1994
C.2.3.3 Modify a connection
The Modify Connection function modifies one of the items listed for the Establish Connection function
defined in subclause C.2.3.1.
C.2.3.4 Read a connection
The Read Connection function reads any of the items listed for the Establish Connection function defined in
subclause C.2.3.1.
Page 43
ETS 300 376-1: December 1994
Annex D (informative): Functional architecture
Figures D.1 to D.4 represent the functional architecture for PSTN and ISDN, respectively.
TTPs and CTPs are used as a basis for defining object classes for modelling. The V5 ports and the user
ports are identified as TTPs, with the user ports at a higher level than the V5 ports, i.e. the V5 layer either
directly or indirectly serves the user ports. The user port layer is related to the V5 layer by cross
connections.
ACCESS CHANNEL BEARER
CONNECTION
B Ps B Ps
POTS POTS
Ps O&M
USER
TP TP
PORT
2W
TIMESLOT
TIMESLOT
ALLOCATION
FUNCTION LINK
CONNECTION
V5
V5 TRAIL
TTP
Figure D.1: Access network side V5 functional architecture for PSTN

Page 44
ETS 300 376-1: December 1994
BEARER VIRTUAL
CONNECTION ACCESS CHANNEL
Ps B
POTS
O&M Ps VIRTUAL
TP TP ACCESS
PORT
TIMESLOT
TIMESLOT
ALLOCATION
LINK FUNCTION
CONNECTION
V5
V5 TRAIL
TTP
Figure D.2: Local exchange side V5 functional architecture for PSTN

Page 45
ETS 300 376-1: December 1994
ACCESS CHANNEL BEARER
CONNECTION
S F P
TTP TTP TTP
B B D B B P F S
ISDN ISDN
COMMUNICATIONS
USER PATH ALLOCATION
PORT FUNCTION
2W
CHNL
TTP
TIMESLOT
TIMESLOT
ALLOCATION
FUNCTION LINK
CONNECTION
V5
V5 TRAIL
TTP
Figure D.3: Access network side V5 functional architecture for ISDN

Page 46
ETS 300 376-1: December 1994
BEARER VIRTUAL
CONNECTION ACCESS CHANNEL
P F S
TTP TTP TTP
S F P B B
ISDN
COMMUNICATIONS VIRTUAL
PATH ALLOCATION ACCESS
FUNCTION PORT
CHNL
TTP
TIMESLOT TIMESLOT
ALLOCATION
LINK
FUNCTION
CONNECTION
V5
V5 TRAIL
TTP
Figure D.4: Local exchange side V5 functional architecture for ISDN

Page 47
ETS 300 376-1: December 1994
Annex E (informative): Link control message flows
The link control message flows for the AN are described in annex E of ETS 300 377-1 [5].
Page 48
ETS 300 376-1: December 1994
Annex F (informative): User port control message flows
This annex describes typical flows of control messages for PSTN user ports, ISDN basic access user
ports and ISDN primary rate user ports on CCITT Recommendation X.731 [17] states, including the case
of permanent line capability.
F.1 Message flows for the mapping of PSTN user port states on X.731 states
A state and a message written in the same line means that this state is entered and the message is sent
as part of the transition into this state. There are transitions where two messages are sent. Since the
resource manager is not shown in a separate column "port-ok" and "port-not-ok" messages appear in
brackets in the MPH message column. Notifications to the OS due to state transitions are not shown.
F.1.1 Blocking initiated by AN
Table F.1: Blocking initiated by AN
OS X.731 MPH Port V5 Port MPH X.731 OS

command state message state message state message state command
5 2.0 2.0 enabled
LOCK→
2 MPH-BI→
1.0 FE204→
1.0 MPH-BI→
disabled
F.1.2 Blocking request initiated by AN
Table F.2: Blocking request initiated by AN

5 2.0 2.0 enabled
SHUTDOWN→
3 MPH-BR→
2.0 FE205→
2.0 MPH-BR→
enabled
←MPH-BI (access free)
disabled
←FE203 1.0
←MPH-BI 1.0
2
F.1.3 Blocking initiated by LE
Table F.3: Blocking initiated by LE

5 2.0 2.0 enabled
←LOCK
←MPH-BI disabled
←FE203 1.0
←MPH-BI 1.0
4
Page 49
ETS 300 376-1: December 1994
F.1.4 Co-ordinated unblocking initiated by the LE
Table F.4: AN administrative state is UNLOCKED (i.e. AN agrees to unblocking request from LE)

4 1.0 1.0 disabled
←UNLOCK
←MPH-UBR disabled
←FE201 1.1
1.2
←MPH-UBR
4 MPH-UBR→
←MPH-UBI 2.0 FE202→
5 2.0 MPH-UBI→
enabled
Table F.5: AN administrative state is LOCKED in the meantime

(i.e. AN rejects the unblocking request from LE)

1 1.0 1.0 disabled
←UNLOCK
←MPH-UBR disabled
←FE201 1.1
←MPH-UBR 1.2
1
F.1.5 Co-ordinated unblocking initiated by the AN
Table F.6: Administrative state = LOCKED, Operational state = ENABLED

2 1.0 1.0 disabled
UNLOCK→
4 MPH-UBR→
1.1 FE202→
1.2 MPH-UBR→
←MPH-UBR disabled
←FE201 2.0 MPH-UBI→
←MPH-UBI 2.0 enabled
5
Table F.7: Administrative state = UNLOCKED, Operational state = DISABLED

4 1.0 1.0 disabled
(←port-ok)
4 MPH-UBR→
1.1 FE202→
1.2 MPH-UBR→
←MPH-UBR disabled
5
Page 50
ETS 300 376-1: December 1994
Table F.8: Administrative state = LOCKED, Operational state = ENABLED,

LE local unblocked (LE1.1)

2 1.2 1.1 disabled
UNLOCK→
4 MPH-UBR→
5 2.0 MPH-UBI→
enabled
Page 51
ETS 300 376-1: December 1994
F.2 Message flows for the mapping of ISDN basic access user port states on
X.731 states
The following message flows show the behaviour of the isdnBAUserPort object class in the case that at
least one bearer channel is provisioned for permanent line capability. For a port not being provisioned for
permanent line service, the message flows shown in ETS 300 377-1 [5], clause F.2 are valid. A state and
a message written in the same line imply that this state is entered and the message is sent as part of the
transition into this state. There are transitions where more than one message is sent. Notifications to the
OS due to state transitions are not shown.
Table F.9: Port operational deactivated (AN2.0)
OS X.731 MPH V1 FE Port V5 FE Port MPH X.731 OS

command state message ↔ ET state
DS↔ state message state command
5 2.0 2.0 enabled
LOCK→
2 MPH-BI→
1.0 FE204→
1.0 MPH-BI→
disabled
Table F.10: Port operational activation initiated (AN2.1)
OS X.731 MPH V1 FE Port V5 FE Port MPH/PH X.731 OS

5 2.1 2.1 enabled
LOCK→
2 MPH-BI→
←FE5 1.0 FE204→
1.0 MPH-BI→
MPH-DI→
PH-DI→
disabled
FE6→
←MPH-DI 1.0
2
Table F.11: Port operational and activated (AN2.2)

5 2.2 2.2 enabled
LOCK→
2 MPH-BI→
←FE5 1.0 FE204→
1.0 MPH-BI→
MPH-DI→
PH-DI→
disabled
FE6→
←MPH-DI 1.0
2
Page 52
ETS 300 376-1: December 1994
F.2.2 Blocking initiated by the LE
Table F.12: Port operational deactivated (AN2.0)

5 2.0 2.0 enabled
←MPH-BI disabled
←FE203 1.0
←MPH-BI 1.0
4 MPH-AR→
←FE1 3.1
FE2→
3.1
FE3→
←MPH-DSAI 3.1
4 FE4→
←MPH-PAI 3.2
5
Table F.13: Port operational activation initiated (AN2.1)

5 2.1 2.1 enabled
←MPH-BI disabled
←FE203 1.0
←MPH-BI ←FE5 1.0
4 MPH-AR→
←FE1 3.1
FE2→
3.1
FE3→
←MPH-DSAI 3.1
4 FE4→
←MPH-PAI 3.2
5
Table F.14: Port operational and activated (AN2.2)

5 2.2 2.2 enabled
←MPH-BI disabled
←FE203 1.0
←MPH-BI ←FE5 1.0
4 MPH-AR→
←FE1 3.1
FE2→
3.1
FE3→
←MPH-DSAI 3.1
4 FE4→
←MPH-PAI 3.2
5
Page 53
ETS 300 376-1: December 1994

4 1.0 1.0 disabled
←MPH-UBR enabled req
←FE201 1.1
←MPH-UBR 1.2
4 MPH-UBR→
5 2.0 MPH-UBI→
←MPH-AR enabled
←FE101 2.1
←MPH-I1 ←FE1 2.1
5
FE2→
2.1
FE3→
←MPH-DSAI 2.1 FE103→
5 2.1 MPH-DSAI→
FE4→ enabled
←MPH-AI 2.2 FE104→
5 2.2 MPH-AI→
PH-AI→
enabled


1 1.0 1.0 disabled
←MPH-UBR enabled req
←FE201 1.1
←MPH-UBR 1.2
1
Page 54
ETS 300 376-1: December 1994

2 1.0 1.0 disabled
UNLOCK→
(start TPL1) MPH-UBR→
4
1.1 FE202→
1.2 MPH-UBR→
←MPH-UBR disabled
(stop TPL1)
5
←MPH-AR
←FE101 2.1
←MPH-I1 ←FE1 2.1
5
FE2→
2.1
FE3→
5 2.1 MPH-DSAI→
FE4→ enabled
←MPH-AI 2.2 FE104→
5 2.2 MPH-AI→
PH-AI→
enabled

4 1.0 1.0 disabled
(internal error) 4 MPH-BI→
1.0 FE204→
1.0
(no internal error, MPH-UBR→
start TPL1)
4
1.1 FE202→
1.2 MPH-UBR→
←MPH-UBR disabled
(stop TPL1)
5
←MPH-AR
←FE101 2.1
←MPH-I1 ←FE1 2.1
5
FE2→
2.1
FE3→
5 2.1 MPH-DSAI→
FE4→ enabled
←MPH-AI 2.2 FE104→
5 2.2 MPH-AI→
PH-AI→
enabled
Page 55
ETS 300 376-1: December 1994


2 1.2 1.1 disabled
UNLOCK→
(start TPL1) MPH-UBR→
4
(stop TPL1) 2.0 MPH-UBI→
5
enabled
←MPH-AR
←FE101 2.1
←MPH-I1 ←FE1 2.1
5
FE2→
2.1
FE3→
5 2.1 MPH-DSAI→
FE4→ enabled
←MPH-AI 2.2 FE104→
5 2.2 MPH-AI→
PH-AI→
enabled
Page 56
ETS 300 376-1: December 1994
F.3 Message flows for the mapping of ISDN primary rate access user port
states on X.731 states
The following message flows show the behaviour of the isdnPRAUserPort object class in the case that at
least one bearer channel is provisioned for permanent line capability. For a port not provisioned for
permanent line service the messages flows shown in ETS 300 377-1 [5], clause F.2 are valid. A state and
a message written in the same line imply that this state is entered and the message is sent as part of the
transition into this state. There are transitions where more than one message is sent. Notifications to the
OS due to state transitions are not shown.
Table F.20: Access operational (AN2.0)
OS X.731 MPH V1 FE Port V5 FE Port MPH X.731 OS

5 2.0 2.0 enabled
LOCK→
2 MPH-BI→
←RAI 1.02 FE204→
1.0 MPH-BI→
PH-DI→
MPH-DI→
disabled
F.3.2 Blocking initiated by the LE
Table F.21: Access operational (AN2.0)

5 2.0 2.0 enabled
←MPH-BI disabled
←FE203 1.0
←MPH-BI ←RAI 1.02
(start TPL1)
4 MPH-UBR→
1.1 FE202→
1.2 MPH-UBR→
disabled
(expiry of TPL1)
4 MPH-PAR→
←MPH-PAI ←NOF AN3.0
5

4 1.02 1.0 disabled
←MPH-UBR (enabled
req)
←FE201 1.1
←MPH-UBR 1.22
4 MPH-UBR→
←MPH-UBI ←NOF 2.0 FE202→
5 2.0 MPH-AI→
PH-AI→
enabled
Page 57
ETS 300 376-1: December 1994


1 1.01 1.0 disabled
←MPH-UBR (enabled
req)
←FE201 1.1
←MPH-UBR 1.21
1

2 1.02 1.0 disabled
UNLOCK→
(start TPL1)
4 MPH-UBR→
1.1 FE202→
1.2 MPH-UBR→
←MPH-UBR disabled
←FE201 2.0 MPH-AI→
PH-AI→
←MPH-UBI ←NOF 2.0 enabled
(stop TPL1)
5
OS X.731 MPH V! FE Port V5 FE Port MPH/PH X.731 OS

4 1.02 1.0 disabled
(internal error)
4 MPH-BI→
1.02 FE204→
1.0
(no internal error,
start TPL1)
4 MPH-UBR→
1.1 FE202→
1.2 MPH-UBR→
←MPH-UBR disabled
←FE201 2.0 MPH-AI→
PH-AI→
←MPH-UBI ←NOF 2.0 enabled
(stop TPL1)
5
Page 58
ETS 300 376-1: December 1994


2 1.22 1.1 disabled
UNLOCK→
(start TPL1)
4 MPH-UBR→
←MPH-UBI ←NOF 2.0 FE202→
(stop TPL1) 2.0 MPH-AI→
5 PH-AI→
enabled
Page 59
ETS 300 376-1: December 1994
Annex G (normative): Location of the Q3 interface
The Q3 interface is the TMN interface between an OS and Q-adapters, mediation devices or network
elements (see figure G.1). The use of this ETS at these points is mandatory. The specification of Qx
interfaces and proprietary interfaces is outside the scope of this ETS.
The Q3 interface places no constraint on the integration of the V5 configuration model for the AN with other
object models relating to other aspects of the AN and the operation of these models over the same Q3
interface specified here.
There are also no constraints implied concerning the structure of the AN which supports the V5 interface.
For example, at one extreme the AN might involve a simple direct connection between customers and
exchanges, and at the other extreme it might involve a very large, highly complex transmission and
switching network between them.
TMN Boundary
Operations
System
Q3
Data Communication Network
Q3
Mediation M
Device
Q3 Q3 Qx
Data Communication Network
Qx Qx
Q Network Q Network
Adapter Element Adapter Element
M M
NOTE 1: Qx and M (proprietary) interfaces are outside the scope of this ETS.
NOTE 2: A mediation device can only have a M interface if it contains Q-adapter functionality.
Figure G.1: Location of the Q3 interface

Page 60
ETS 300 376-1: December 1994
Annex H (normative): Summary of V5 requirement details
This annex summarizes the V5 related items which need to be provisioned over the Q3 interface.
1) Identification of V5 interfaces
The interface ID field is three octets.
The link ID field is one octet.
2) Allocation of bearer channels to user ports
3) Service allocation to bearer channels
4) The allocation of addresses to ISDN and PSTN ports
The PSTN address field is 15 bits.
The ISDN address field is 13 bits with certain addresses reserved for non-ISDN use.
5) The identification of new provisioning variants
The provisioning variant field is one octet.
6) Communication path allocation
The V5.1 interface can have up to 3 communication time slots. Time slot 16 is always used. There
are constraints on the other two time slots.
7) Activation of ISDN BA for PL service
8) Activation of error performance monitoring for access digital sections
There are 2 grading levels.
9) PSTN line gain

Page 61
ETS 300 376-1: December 1994
Annex J (normative): Defaults and predefined items
A number of items are predefined, i.e. they need to be specified when equipment is procured, but they
cannot be changed via the Q3 interface, and may not be visible over the Q3 interface. Items may also
have default values which do not need to be specified via the Q3 interface. Predefined items and their
defaults are specified here.
1) Specific PSTN parameters
2) Autonomous-signalling-sequence
3) The sequence-response information element
4) The cadenced-ringing information element
5) The recognition time of PSTN signals
6) Signal information elements
7) PSTN protocol state AN1
8) Grading thresholds
The thresholds for the generation of grading messages related to error performance, including the
nature of these thresholds, the algorithm used and any hysteresis included are predefined.
9) Persistency check for V5 layer 1
10) CRC thresholds for V5 layer 1
11) PSTN line current
12) Provisioning variant
If the provisioning variant is not supported on the Q3 interface, for instance because of the existence
of an integrated OS or of an TMN X interface, then a default value of all zeroes shall be
automatically used on the V5 interface. All V5 interfaces shall use this default value unless actively
changed via the Q3 interface.
13) Initial configuration
If the Q3 information is transported over a V5 interface then an initial configuration needs to be

specified to support this. It is possible to use 64 kbit/s bearer channels and p- and f-type data
channels on virtual user ports (see ETS 300 324-1 [3]) of a V5 interface to transport the Q3
information.
Predefinition of the virtual user port on the AN side at least is required.

Page 62
ETS 300 376-1: December 1994
Annex K (informative): Bibliography
1) ETR 008 (1990): "Network Aspects (NA); The method for the characterisation of
the machine-machine interfaces utilised by a Telecommunications Management
Network (TMN)".
2) ETR 037 (1992): "Network Aspects (NA); Telecommunications Management

Network (TMN); Objectives, principle, concepts and reference configurations".
3) ETR 046 (1992): "Network Aspects (NA); Telecommunications management

networks modelling guidelines".

Network (TMN); Management services".

Network (TMN); Management services prose descriptions".
6) ETR 078 (1993): "Maintenance: Telecommunications management network;

TMN interface specification methodology [CCITT Recommendation
M.3020 (1992)]".
7) ETS 300 150 (1992): "Transmission and Multiplexing (TM); Protocol suites for Q
interfaces for management of transmission systems".
8) I-ETS 300 292: "Network Aspects (NA); Functional specification of call routeing
information management on the Operations System/Network Element (OS/NE)
interface".
9) I-ETS 300 293: "Telecommunications Management Network (TMN); Generic

managed objects".
10) ETS 300 304: "Transmission and Multiplexing (TM); Synchronous Digital
Hierarchy (SDH) information model for the Network Element (NE) view".
11) CCITT Recommendation G.774 (1992): "Synchronous Digital Hierarchy (SDH)

management information model for the network element view".
12) ITU-T Recommendation G.803 (1993): "Architecture of transport networks

based on the synchronous digital hierarchy".
13) ITU-T Recommendation G.831 (1993): "Management capabilities of transport

networks based on the synchronous digital hierarchy".
14) ITU-T Recommendation G.960 (1993): "Digital section for ISDN basic rate
access".
15) CCITT Recommendation X.710 (1991): "Common management information

service definition for CCITT applications".
16) CCITT Recommendation X.720 | ISO/IEC 10165-1 (1992): "Information

information: Management information model".

information: Guidelines for the definition of managed objects".
Page 63
ETS 300 376-1: December 1994

technology - Open systems interconnection - Systems management: Object
management function".
Page 64
ETS 300 376-1: December 1994
History
Document history
December 1994 First Edition
January 1996 Converted into Adobe Acrobat Portable Document Format (PDF)

Ets 30037601e01p

Uploaded by

Copyright:

Available Formats

Ets 30037601e01p

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ets 30037601e01p

Uploaded by

Copyright:

Available Formats

EUROPEAN ETS 300 376-1

TELECOMMUNICATION December 1994

Signalling Protocols and Switching (SPS);

Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE

© European Telecommunications Standards Institute 1994. All rights reserved.

2 Normative references ................................................................................................................9

5 Information model diagrams ..................................................................................................... 12

6 Information model description................................................................................................... 18

7 Formal definitions .................................................................................................................... 21

7.2.4 User port Bearer channel CTP (userPortBearerChannelCtp) ......................25

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

Annex B (normative): Mapping of link control states on X.731 states...............................................37

C.1 Task Information Base (TIB) A ................................................................................................. 38

C.2 Management function list..........................................................................................................40

C.2.1.1 Insert a user port ................................................................................... 40

Annex D (informative): Functional architecture................................................................................. 43

Annex E (informative): Link control message flows.......................................................................... 47

Annex F (informative): User port control message flows.................................................................. 48

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

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:

Date of latest publication of new National Standard

Date of withdrawal of any conflicting National Standard (dow): 30 September 1995

ITU-T Recommendation G.803 (1993) provides an abstracted view of telecommunications equipment,

- the definition of OS functionality is outside the scope of this ETS;

[9] CCITT Recommendation G.784 (1990): "Synchronous Digital Hierarchy (SDH)

[10] CCITT Recommendation M.3010 (1992): "Principles for a telecommunications

[11] CCITT Recommendation M.3100 (1992): "Generic network information model".

[14] CCITT Recommendation X.208 (1988): "Specification of Abstract Syntax

[15] CCITT Recommendation X.711 (1991): "Common management information

[16] CCITT Recommendation X.721 | ISO/IEC 10165-2 (1992): "Information

[17] CCITT Recommendation X.731 | ISO/IEC 10164-2 (1992): "Information

[18] CCITT Recommendation X.732 | ISO/IEC 10164-3 (1992): "Information

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].

envelope function address: See ETS 300 324-1 [3].

Local Exchange (LE): See ETS 300 324-1 [3].

Operations System (OS): See CCITT Recommendation M.3010 [10].

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].

X interface: See CCITT Recommendation M.3010 [10].

For the purposes of this ETS, the following abbreviations apply:

TIB Task Information Base

5 Information model diagrams

5.1 Entity relationship diagram