SIST ETS 300 378-1:1997

• Abstract:

  To specify the Q3-inerface at access network for supporting maintenance of V5 interfaces & associated user ports.

• Status: Published
• Publication Date: 31-Oct-1997
• ICS: 33.040.30 - Switching and signalling systems
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Nov-1997
• Due Date: 01-Nov-1997
• Completion Date: 01-Nov-1997
• Ref Project: ETSI ETS 300 378-1 ed.1 (1995-11) - Q3 interface at the Access Network (AN) for fault and performance management of V5 interfaces and associated user ports; Part 1: Q3 interface specification

SIST ETS 300 378-1:1997 is the Slovenian adoption of ETS 300 378-1 from ETSI. It specifies the Q3 interface at the Access Network (AN) for fault and performance management of V5 interfaces and associated user ports, so Operations Systems (OSs) in the Telecommunications Management Network (TMN) can monitor alarms, run tests and collect performance data.

What does SIST ETS 300 378-1:1997 specify?

SIST ETS 300 378-1:1997 specifies the Q3 interface between an Access Network (AN) and the TMN for fault and performance management of V5 interfaces and their associated user ports. It focuses on the management information model, the alarm and test information that crosses the interface, and the protocol framework needed to carry those management functions.

The scope is limited to V5-related management. It covers line and line circuit testing at the user ports associated with the V5 interface, fault logging and related functions, but it leaves out transmission, media and services that are not related to V5 interfaces. The standard also keeps local-management-only V5 error handling and implementation-specific fault handling outside its scope.

The document is organized into clauses 1 to 7, followed by annexes. The main body defines the scope, references, terminology, information model diagrams, object class descriptions, formal object class definitions and protocol requirements.

Annex	What it covers
Annex A	Normative specification of parameters for V5-specific alarm reports
Annex C	User port and V5 interface test requirements
Annex D	Detailed test categories and their request/result content
Annex E	Task Information Base (TIB) reference
Annex F	Management functions reference
Annex G	Example test procedures in an AN environment
Annex J	Intrusive tests and conflict handling with normal service
Annex K	Message flow examples
Annex L	Bibliography

What are the key requirements of SIST ETS 300 378-1:1997?

The standard defines a TMN management model for AN fault and performance supervision. In practice, this means the AN has to expose managed objects, attributes, actions and notifications that describe V5 interfaces, user ports, test objects and related performance data in a form that OS applications can use.

Management information model and object structure

Clauses 4 to 6 define the information model through entity relationship diagrams, inheritance hierarchy and naming hierarchy, then formal object class definitions, name bindings, packages, attributes, actions, notifications and parameters. The model includes fragments for the V5 interface, user ports, communications path, protection, performance, alarm surveillance, support and tests.

This matters because implementers need a consistent object structure, not just a message format. The standard tells the AN how to present managed objects such as pstnUserPort, isdnBAUserPort, isdnPRAUserPort, leasedPort and the various test objects in a way that can be addressed and managed over Q3.

State, relationship and identity handling

Clause 5.2 identifies the generic attributes used across the model: Relative Distinguished Name (RDN), state attributes and relationship attributes. The state attributes include operational state, administrative state and availability status.

In practice, these attributes are what an operator sees when deciding whether a user port is serviceable, locked, blocked or available for testing. They are also the basis for change reports and for managing intrusive tests without confusing them with normal service states.

Alarm reporting for V5-specific faults

Annex A specifies how V5-specific alarm reports are generated with the communicationsAlarm notification. It groups alarm reporting by object class, including the V5 interface, trail termination point, time slot, user port and user port subclasses.

This is important for fault management because it gives the AN a common way to report control protocol errors, link failures, PSTN protocol errors, ISDN layer faults and line faults. The operator can then filter, correlate and act on faults by the object they affect.

Test management and test categories

Annex C sets out general test management requirements for scheduled testing and test capability, then addresses V5 interface testing and user port testing. It covers test scheduling, test result management and test threshold management, and it points to PSTN line testing, PSTN inward tests, ISDN BA testing and ISDN PRA testing.

Annex D gives the practical test categories behind those requirements. The categories include electrical measurement tests, dialled digit tests, dial tone tests, SPM pulses, ringing tests, test to line circuit and ISDN loopback tests. For users of the standard, this is the part that says what kinds of tests can be requested and what kind of result information is expected back.

Test requests, results and parameters

Clause 6.7 defines the parameter types used for test requests and responses, including loopback request and result handling, electrical measurement requests, dial tone and dialled digit results, and test-to-line-circuit results. Clause 6.8 gives the ASN.1 module that defines the associated types.

This matters because the standard is not only descriptive - it is implementable. An engineer can map a test request into the defined ASN.1 structures and know what kind of result or notification should come back.

Intrusive test handling and service interaction

Annex J explains how intrusive tests interact with normal service. It uses the testConditions and waitTime ideas, and it discusses the administrative locked state, V5 blocking mechanisms and the choice between reject if busy, wait if busy and test if busy.

In practice, this is the key operational rule set for testing live user ports without causing unnecessary service interruption. It tells the operator or network element how to deal with busy ports, call attempts during testing and short tests that may not need visible state changes on Q3.

Protocol stack

Clause 7 states that the protocol stack for this Q3 interface is the same as in ETS 300 376-1 clause 8. That keeps the fault and performance management part aligned with the companion configuration management part.

For implementers, this means the transport and protocol framework is not redefined here. The focus is on the managed object model and the management content carried across the interface.

What terms does SIST ETS 300 378-1:1997 define?

• Access Network (AN) - The network side where the Q3 interface is located and where the V5-related user ports are managed.
• Telecommunications Management Network (TMN) - The management environment that uses OS functions to supervise network elements such as the AN.
• Operations System (OS) - The management system that issues requests, receives notifications and uses the Q3 interface for supervision and control.
• V5 interface - The interface between a Local Exchange (LE) and an AN that supports narrowband ISDN and PSTN services.
• Q3 interface - The management interface used here to carry fault and performance management information between the AN and the TMN.
• Bearer Channel Connection (BCC) - A V5 protocol area referenced in the scope and definitions for some error handling and management information.
• Task Information Base (TIB) - The task-oriented management reference point mentioned in the annexes on management functions.

Who uses SIST ETS 300 378-1:1997?

This standard is used by telecom network operators, access network engineers, service assurance teams and management system vendors who need to supervise V5 interfaces and their user ports. It is also relevant to maintenance technicians who perform line tests, interpret alarms or run subscriber-assisted test procedures.

Quality managers and buyers use it when they need an AN or OS platform that can support V5 fault management, performance monitoring and test workflows. It is especially relevant in networks carrying PSTN and ISDN access over V5 interfaces.

What changed in SIST ETS 300 378-1:1997 from the previous edition?

SIST ETS 300 378-1:1997 is identical to ETS 300 378-1 Edition 1. The history box identifies it as the first edition.

Which standards are used with SIST ETS 300 378-1:1997?

• ETS 300 376-1 - The companion AN Q3 standard for configuration management, and the reference for the Q3 interface location and protocol stack.
• ETS 300 377-1 - The related LE Q3 standard for configuration management of V5 interfaces and associated customer profiles.
• ETS 300 379-1 - The related LE Q3 standard for fault and performance management of V5 interfaces and associated customer profiles.
• ETS 300 324-1 and ETS 300 347-1 - The V5.1 and V5.2 interface standards that define the underlying V5 terms, objects and protocol context.
• ETS 300 233 and ETS 300 297 - The ISDN primary rate and basic access standards used for the access-side context.
• CCITT Recommendation M.3010 and M.3100 - The TMN principles and generic network information model that frame the management approach.
• ITU-T Recommendations Q.821 and Q.822 - The alarm surveillance and performance management descriptions used by the management model.
• CCITT/ITU-T Recommendations X.208, X.711, X.720, X.721, X.730, X.731, X.732, X.737, X.738, X.739, X.745 and X.746 - The ASN.1, CMIP and object-management standards that provide the formal management-model machinery.

What does the SIST ETS 300 378-1:1997 document contain?

Clauses 4 and 5 contain the information model diagrams, the object class descriptions and the common attribute, action and notification framework. Clause 6 provides the formal managed object definitions, name bindings, packages, attributes, actions, notifications, parameters and the ASN.1 type module.

The annexes add the operational detail that implementers and operators usually need. Annex A gives V5 alarm report parameters, annex C and D describe test management and test categories, annex G gives example test procedures, annex J explains intrusive-testing behaviour, and annex K shows message-flow examples.

The document is therefore useful both for implementation and for day-to-day network operation. It tells you what management objects exist, how they relate, what alarm and test information they carry, and how V5-related testing is expected to interact with live service.

SLOVENSKI STANDARD
01-november-1997
6LJQDOL]DFLMVNLSURWRNROLLQNRPXWDFLMD6369PHVQLN4YGRVWRSRYQHPRPUHåMX
$1]DXSUDYOMDQMHY]GUåHYDOQLKIXQNFLMYPHVQLNRY9LQSULGUXåHQLKXSRUDEQLãNLK
SULNOMXþNRYGHO6SHFLILNDFLMDYPHVQLND4
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
Ta slovenski standard je istoveten z: ETS 300 378-1 Edition 1
ICS:
33.040.30 Komutacijski in signalizacijski Switching and signalling
sistem systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 378-1
TELECOMMUNICATION November 1995
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-03014.1
ICS: 35.100.70
TMN, information model, Q3 interface, AN, V5 interface, fault, performance, management
Key words:
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
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - [e-mail]
X.400: Internet:
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1995. All rights reserved.
New presentation - see History box

Page 2
ETS 300 378-1: November 1995
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 378-1: November 1995
Contents
Foreword .9
Introduction.9
1 Scope .11
2 Normative references.11
3 Definitions and abbreviations .13
3.1 Definitions .13
3.2 Abbreviations .14
4 Information model diagrams.15
4.1 Entity relationship diagram.15
4.1.1 Traffic measurement .16
4.1.2 Line testing and line circuit testing .17
4.1.3 The testResultNotifications of the tests.17
4.1.4 Performance monitoring of ISDN user ports .17
4.2 Inheritance hierarchy .18
4.3 Naming hierarchy.19
5 Information model description.19
5.1 Description of object classes .20
5.1.1 V5 interface fragment.20
5.1.2 User port fragment .20
5.1.2.1 PSTN user port (pstnUserPort) .20
5.1.2.2 ISDN basic access user port (isdnBAUserPort) .20
5.1.2.3 ISDN primary rate access user port (isdnPRAUserPort).21
5.1.2.4 Leased port (leasedPort) .21
5.1.3 Communications path fragment .22
5.1.4 Protection fragment.22
5.1.5 Performance fragment .22
5.1.5.1 Bearer channel current data .22
5.1.5.2 Communication channel current data.22
5.1.6 Alarm surveillance fragment.22
5.1.7 Support fragment.22
5.1.8 Test fragment .23
5.1.8.1 Access test (accessTest) .23
5.1.8.2 Dialled digit test (dialledDigitTest) .23
5.1.8.3 Dial tone test (dialToneTest) .23
5.1.8.4 Electrical measurement test (electricalMeasurementTest) .24
5.1.8.5 Subscriber Private Meter (SPM) pulses (spmPulses) .24
5.1.8.6 Cable pair identification Tone (cablePairIdTone) .24
5.1.8.7 Ringing (ringing) .24
5.1.8.8 Test to line circuit (testToLineCircuit) .25
5.1.8.9 Dry Loop (dryLoop).25
5.1.8.10 Loop test (loopTest).25
5.1.8.11 Pattern test (patternTest).25
5.1.8.12 Voice Access Test (voiceAccessTest) .26
5.2 Definition of attributes .26
5.2.1 Relative distinguished name .26
5.2.2 State attributes .27
5.2.2.1 Operational state (operationalState).27
5.2.2.2 Administrative state (administrativeState) .27
5.2.2.3 Availability status (availabilityStatus) .27
5.2.3 Relationship attributes.27
5.3 Actions description.27

Page 4
ETS 300 378-1: November 1995
5.4 Notifications description . 27
6 Formal object class definitions . 28
6.1 Definitions of object classes. 28
6.1.1 V5 interface fragment . 28
6.1.2 Access port fragment. 28
6.1.3 Performance fragment. 28
6.1.4 Alarm surveillance fragment . 28
6.1.5 Support fragment. 28
6.1.6 Test fragment . 29
6.1.6.1 Access test. 29
6.1.6.2 Dialled digit test. 30
6.1.6.3 Dial tone test . 30
6.1.6.4 Electrical measurement test. 31
6.1.6.5 SPM pulses. 31
6.1.6.6 Cable pair identification tone. 32
6.1.6.7 Ringing. 32
6.1.6.8 Test to line circuit . 32
6.1.6.9 Dry loop. 33
6.1.6.10 Loop test . 33
6.1.6.11 Pattern test. 34
6.1.6.12 Voice access test . 34
6.2 Name bindings . 35
6.2.1 Test fragment . 35
6.2.1.1 Access test. 35
6.2.1.2 Dialled digit test. 35
6.2.1.3 Dial tone test . 35
6.2.1.4 Electrical measurement test. 35
6.2.1.5 SPM pulses. 35
6.2.1.6 Cable pair identification tone. 35
6.2.1.7 Ringing. 36
6.2.1.8 Test to line circuit . 36
6.2.1.9 Dry loop. 36
6.2.1.10 Loop test . 36
6.2.1.11 Pattern test. 36
6.2.1.12 Voice access test . 36
6.3 Definition of packages. 37
6.3.1 Test environment conditions. 37
6.3.2 Voice access. 37
6.4 Definition of Attributes . 38
6.4.1 Electrical measurement test . 38
6.4.2 Iterations . 38
6.4.3 Loopback duration . 38
6.4.4 Loopback position. 38
6.4.5 Loopback channel. 38
6.4.6 Monitor and speak . 39
6.4.7 Number of digits. 39
6.4.8 Off hook simulation. 39
6.4.9 Request result type. 39
6.4.10 Ring . 39
6.4.11 Ring back number . 40
6.4.12 Number of SPM pulses. 40
6.4.13 Wait time. 40
6.5 Definition of actions. 40
6.5.1 Loopback select. 40
6.6 Definition of notifications . 40
6.7 Definition of parameters. 41
6.8 ASN.1 defined types module. 44
7 Protocol requirements . 48
Annex A (normative): Specification of parameters for V5 specific alarm reports . 49

Page 5
ETS 300 378-1: November 1995
A.1 Alarm reports related to the V5 interface object class.49
A.1.1 Control protocol errors .49
A.1.2 Link control protocol errors .49
A.1.3 BCC protocol errors .50
A.1.4 Protection protocol errors .50
A.1.5 PSTN protocol errors .50
A.1.6 Interface control failures .51
A.1.7 V5 data link failures.51
A.2 Alarm reports related to the V5 trail termination point object class.52
A.2.1 Link control failures.52
A.2.2 Link layer 1 failures.53
A.3 Alarm reports related to the V5 time slot object class.53
A.3.1 V5 communication channel failures.53
A.4 Alarm reports related to the user port object class and subclasses.54
A.4.1 Control protocol errors .54
A.4.2 PSTN protocol errors .54
A.4.3 ISDN layer 1 faults (Q(AN) only).55
A.4.3.1 ISDN BA layer 1 faults (Q(AN) only).55
A.4.3.2 ISDN PRA layer 1 faults (Q(AN) only).55
A.4.4 ISDN layer 2 faults (Q(AN) only).56
A.4.5 Line faults (Q(AN) only) .56
Annex B (normative): V5 specific traffic measurement.57
Annex C (normative): Requirements and specification of parameters for user port tests.58
C.1 General test requirements.58
C.1.1 Scheduled testing .58
C.1.2 Test capability .58
C.2 V5 interface test requirements .58
C.2.1 V5 interface ID testing.58
C.2.2 Link ID testing .58
C.2.3 Provisioning variant testing .58
C.3 User port test requirements.58
C.3.1 User port test management functions.59
C.3.2 Test scheduling.59
C.3.3 Test result management.59
C.3.4 Test threshold management.60
C.3.5 Test requirements description .60
C.3.5.1 PSTN line testing.60
C.3.5.1.1 Foreign voltage or current.60
C.3.5.1.2 Capacitance measurement.60
C.3.5.1.3 Insulation resistance measurement.61
C.3.5.1.4 Loop resistance measurement .61
C.3.5.1.5 Dial pulse test .61
C.3.5.1.6 DTMF dialling test.61
C.3.5.1.7 Subscriber private meter testing.61
C.3.5.1.8 Ring subscriber.61
C.3.5.1.9 Monitoring of the line .62
C.3.5.1.10 Cable pair identification tone .62
C.3.5.1.11 Dry loop .62
C.3.5.1.12 Register recall button test.62
C.3.5.1.13 Ring back procedure .62
C.3.5.2 PSTN inward tests.62
C.3.5.2.1 Line circuit testing.62
C.3.5.2.1.1 Feeding voltage .62
C.3.5.2.1.2 Feeding current.62
C.3.5.2.1.3 Loop and ring trip detection .63

Page 6
ETS 300 378-1: November 1995
C.3.5.2.1.4 Ringing current sending . 63
C.3.5.2.1.5 Private meter pulses . 63
C.3.5.2.1.6 Codec testing . 63
C.3.5.2.1.7 Digit reception . 63
C.3.5.2.2 Other inward tests. 63
C.3.5.2.2.1 Dial tone test . 63
C.3.5.3 ISDN BA testing. 63
C.3.5.3.1 ISDN BA line testing. 63
C.3.5.3.2 ISDN BA line termination testing. 63
C.3.5.3.2.1 Loopbacks. 63
C.3.5.3.2.2 Activation and deactivation of lines . 64
C.3.5.3.3 ISDN BA line circuit testing . 64
C.3.5.3.3.1 Power feed . 64
C.3.5.4 ISDN PRA testing . 64
C.3.5.4.1 ISDN PRA line testing. 64
C.3.5.4.2 ISDN PRA line termination testing . 64
Annex D (normative): Test categories . 65
D.1 Electrical measurement tests . 65
D.2 Dialled digit test . 66
D.3 Dial tone test. 67
D.4 Subscriber private meter pulses test . 68
D.5 Ringing test. 69
D.6 Test to line circuit test. 70
D.7 ISDN loopback test. 71
Annex E (informative): Task Information Base (TIB). 72
Annex F (informative): Description of management functions . 73
Annex G (informative): Description of test procedures. 74
G.1 Background. 74
G.2 Test procedures scenario. 74
G.2.1 Scenario for faultsman ringback tests in an AN environment . 74
G.2.2 Scenario for a subscriber assisted test in an AN environment . 75
G.2.2.1 Existing connection mode. 76
G.2.2.2 Parallel voice path mode . 76
Annex H (informative): Summary of requirements . 77
Annex J (informative): State management in relation with line testing - Application for V5 access
networks. 78
J.1 Intrusive tests. 78
J.2 Dealing with conflicts between intrusive tests and normal service . 78
J.3 State values during intrusive testing . 79
J.4 V5 blocking mechanism. 79
Annex K (informative): Message flows . 80

Page 7
ETS 300 378-1: November 1995
Annex L (informative): Bibliography.83
History.84

Page 8
ETS 300 378-1: November 1995
Blank page
Page 9
ETS 300 378-1: November 1995
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 as described below:
Part 1: "Q3 interface specification at the Access Network (AN) for fault and performance
management of V5 interfaces and associated user ports";
NOTE: A possible further part 2 may contain the Managed Object Conformance Statement
(MOCS) proforma specification.
The following standards are directly related to this ETS:
ETS 300 376: "Q3 interface at the Access Network (AN) for configuration management of V5 interfaces
and associated user ports";
ETS 300 377: "Q3 interface at the Local Exchange (LE) for configuration management of V5 interfaces
and associated customer profiles";
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 adoption of this ETS: 17 November 1995
Date of latest announcement of this ETS (doa): 28 February 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 August 1996
Date of withdrawal of any conflicting National Standard (dow): 31 August 1996
Introduction
V5 interfaces, as described in ETS 300 324-1 and ETS 300 347-1, operate between a Local Exchange
(LE) and an Access Network (AN) to support various narrowband Integrated Services Digital Network
(ISDN) and Public Switched Telephone Network (PSTN) services. These interfaces and their associated
user ports need to be managed by the Operations Systems (OSs) within the Telecommunications
Management Network (TMN). This management is performed by means of Q3 interfaces.
The companion standard on configuration management ETS 300 376-1 defines how the Q3 interface of
an AN handles the configuration information for V5 interfaces and their associated user ports. This ETS
specifies the extension to include fault and performance management.
Fault management of V5 interfaces and associated user ports is part of a management activity which is
performed by the operator in order to detect failure conditions and to bring the customer access back to its
normal state of operation whenever a deviation occurs.
Performance management of V5 interfaces and associated user ports is part of a management activity
which is employed in order to maintain the quality of service levels agreed with the customers. The
activities undertaken in performance management are monitoring, analysis and problem alerting,
diagnosis, optimization and control.
A customer access is considered as being that part of the local network which extends from the network
termination equipment up to and including the exchange termination.

Page 10
ETS 300 378-1: November 1995
Here, only these parts of the activities are covered which are related directly to a V5 interface between a
LE and an AN or to that part of the customer access which extends from the AN to the network
termination equipment. An ISDN access extends to but does not include the T reference point. An
analogue access extends to and may include the Customer Premise Equipment (CPE) (see figure 1).
Q(AN) Q(LE)
Z
AN
LE
PSTN PSTN
TE UP
T
ISDN
ISDN
NT1
TE
UP
V5 V5
T
TP TP
ISDN
ISDN
V5
TE
UP
LL UP
TE
NOTE: Shaded areas are subject to V5 fault and performance management. User ports represent the
different configurations for Line Circuit (LC), Line Termination (LT), Exchange Termination (ET)
and Network Termination (NT) as given in figure 2 of the V5 specifications ETS 300 324-1 and
ETS 300 347-1. For leased lines (semi-permanent lines), this ETS only covers aspects which
are common to PSTN and ISDN.
Figure 1: Scope of V5 fault and performance management
This ETS details only those functions and management information model components for which V5
specific descriptions are required. However, the use of other components which may be applicable from
other specifications is not precluded. In this case, combined applications incorporating both V5 specific
and more generic aspects would result. For example, if log control is to be provided in conjunction with the
V5 specific alarm reporting function (see annex A), then other specifications (e.g. CCITT
Recommendation X.735) are available to define this.
The management information model described in this ETS complements that for configuration; both
information models will normally share the same physical interface.

Page 11
ETS 300 378-1: November 1995
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 fault and
performance management functions for V5 interfaces, as described in ETS 300 324-1 [4] and
ETS 300 347-1 [5], 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.
This ETS includes the testing of the lines and line circuits at the user ports associated with the V5
interface, and the logging of faults and related functions. Messages on the V5 interface associated with
errors or other faults which are handled by local management (e.g. the non-deferred link blocking request)
or which involve implementation specific issues (e.g. faults which may result in the connection incomplete
information element being used in the Bearer Channel Connection (BCC) protocol) are outside the scope
of this ETS.
The location of the Q3 interface to which this ETS refers is specified in ETS 300 376-1 [6].
This ETS does not constrain the logical or physical size of the AN or its geographical dispersion.
Existing protocols are used where possible, and the focus of this ETS is on defining the object models.
The definition of Operations System (OS) functionality is outside the scope of this ETS.
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] ETS 300 233 (1994): "Integrated Services Digital Network (ISDN); Access digital
section for ISDN primary rate".
[2] I-ETS 300 291 (1995): "Network Aspects (NA); Functional specification of
Customer Administration (CA) on the Operations System/Network Element
(OS/NE) interface".
[3] ETS 300 297 (1995): "Integrated Services Digital Network (ISDN); Access digital
section for ISDN basic access".
[4] 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".
[5] 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".
[6] ETS 300 376-1 (1994): "Signalling Protocols and Switching (SPS); Q3 interface
at the Access Network (AN) for configuration management of V5 interfaces and
associated user ports; Part 1: Q3 interface specification".
[7] 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".
[8] ETS 300 379-1 (1995): "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".

Page 12
ETS 300 378-1: November 1995
[9] ETR 080 (1993): "Transmission and Multiplexing (TM); Integrated Services
Digital Network (ISDN) basic rate access - Digital transmission system on
metallic local lines".
[10] CEPT Recommendation T/S 54-08 E (1987): "ISDN subscriber access and
installation maintenance".
[11] CCITT Recommendation G.821 (1988): "Error performance of an international
digital connection forming part of an integrated services digital network".
[12] ITU-T Recommendation G.826 (1993): "Error performance parameters and
objectives for international, constant bit rate digital paths at or above the primary
rate".
[13] CCITT Recommendation M.3010 (1992): "Principles for a telecommunications
management network".
[14] CCITT Recommendation M.3100 (1992): "Generic network information model".
[15] ITU-T Recommendation Q.543 (1993): "Digital exchange performance design
objectives".
[16] ITU-T Recommendation Q.821 (1993): "Stage 2 and stage 3 description for the
Q3 interface - Alarm surveillance".
[17] ITU-T Recommendation Q.822: "Stage 1, stage 2 and stage 3 description for
the Q3 interface - Performance management".
[18] CCITT Recommendation X.208 (1988): "Specification of Abstract Syntax
Notation One (ASN.1)".
[19] CCITT Recommendation X.711 (1991): "Common management information
protocol definition for CCITT applications".
[20] CCITT Recommendation X.720 (1992) | ISO/IEC 10165-1 (1993): "Information
technology - Open systems interconnection - Structure of management
information: Management information model".
[21] CCITT Recommendation X.721 (1992) | ISO/IEC 10165-2 (1992): "Information
technology - Open systems interconnection - Structure of management
information: Definition of management information".
[22] CCITT Recommendation X.730 (1992) | ISO/IEC 10164-1 (1993): "Information
technology - Open systems interconnection - Systems management: Object
management function".
[23] CCITT Recommendation X.731 (1992) | ISO/IEC 10164-2 (1993): "Information
technology - Open systems interconnection - Systems management: State
management function".
[24] CCITT Recommendation X.732 (1992) | ISO/IEC 10164-3 (1993): "Information
technology - Open systems interconnection - Systems management: Attributes
for representing relationships".
[25] ITU-T Recommendation X.737 | ISO/IEC 10164-14: "Information technology -
Open systems interconnection - Systems management: Confidence and
diagnostic test function".
[26] ITU-T Recommendation X.738 (1993) | ISO/IEC 10164-13: "Information
technology - Open systems interconnection - Systems management:
Summarization function".
Page 13
ETS 300 378-1: November 1995
[27] ITU-T Recommendation X.739 (1993)| ISO/IEC 10164-11 (1994): "Information
technology - Open systems interconnection - Systems management: Metric
objects and attributes".
[28] ITU-T Recommendation X.745 (1993)| ISO/IEC 10164-12 (1994): "Information
technology - Open systems interconnection - Systems management: Test
management function".
[29] ITU-T Recommendation X.746 (1995)| ISO/IEC 10164-15: "Information
technology - Open systems interconnection - Systems management: Scheduling
function".
[30] ITU-T Recommendation M.3603: "Application of maintenance principles to ISDN
basic rate access".
[31] ITU-T Recommendation M.3604: "Application of maintenance principles to ISDN
primary rate access".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
Access Network (AN): See ETS 300 324-1 [4].
activation-deactivation of the line: See subclause C.3.5.
bearer channel: See ETS 300 324-1 [4].
Bearer Channel Connection (BCC): See ETS 300 347-1 [5].
cable pair identification tone: See subclause C.3.5.
capacitance measurement: See subclause C.3.5.
codec testing: See subclause C.3.5.
Communication Channel (C-Channel): See ETS 300 324-1 [4].
communication path: See ETS 300 324-1 [4].
control protocol: See ETS 300 324-1 [4].
dial pulse test: See subclause C.3.5.
dial tone test: See subclause C.3.5.
digit reception: See subclause C.3.5.
dry loop: See subclause C.3.5.
Digital Tone Multi-Frequency (DTMF) dialling test: See subclause C.3.5.
envelope function address: See ETS 300 324-1 [4].
feeding current: See subclause C.3.5.
feeding voltage: See subclause C.3.5.
foreign voltage: See subclause C.3.5.

Page 14
ETS 300 378-1: November 1995
insulation resistance measurement: See subclause C.3.5.
layer 3 address: See ETS 300 324-1 [4].
leased lines: See ETS 300 324-1 [4].
line testing: See subclause C.3.5.
line circuit testing: See subclause C.3.5.
Local Exchange (LE): See ETS 300 324-1 [4].
loop detection and ring trip detection: See subclause C.3.5.
loop resistance measurement: See subclause C.3.5.
loopback 1 (line termination loopback): See subclause C.3.5.
loopback 2, 2 and 1A (NT1 loopbacks): See subclause C.3.5.
monitoring of the line: See subclause C.3.5.
monitoring of the line with mark tone: See subclause C.3.5.
Operations System (OS): See CCITT Recommendation M.3010 [13].
power feed: See subclause C.3.5.
private meter pulses: See subclause C.3.5.
protection protocol: See ETS 300 347-1 [5].
register recall button test: See subclause C.3.5.
subscriber private metering: See subclause C.3.5.
V5 interface: See ETS 300 324-1 [4].
V5 interface messages: This term refers to all Function Elements (FEs) and other V5 protocol messages
as defined in ETS 300 324-1 [4] and ETS 300 347-1 [5] which are communicated via the V5 interface.
V5 time slot: See ETS 300 324-1 [4].
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AIS Alarm Indication Signal
AN Access Network
ASN.1 Abstract Syntax Notation One (see CCITT Recommendation X.208 [18])
BA Basic Access
BCC Bearer Channel Connection
C-channel Communication channel
CMIP Common Management Information Protocol
CPE Customer Premise Equipment
DTMF Digital Tone Multi-Frequency
DS access Digital Section
ET Exchange Termination
FE Function Element
FSM Finite State Machine
ID Identity, identifier
Page 15
ETS 300 378-1: November 1995
ISDN Integrated Services Digital Network
LC Line Circuit
LE Local Exchange
LFA Loss of Frame Alignment
LOS Loss Of Signal
LT Line Termination
MORT Managed Object Referring to Test
NE Network Element
NT Network Termination
OS Operations System
OS OS of the Access Network
AN
OS OS of the Local Exchange
LE
PL Permanent Line
PRA Primary Rate Access
PSTN Public Switched Telephone Network
Q3 Q3 interface at the Access Network
AN
Q3 Q3 interface at the Local Exchange
LE
RDN Relative Distinguished Name
REG Regenerator
SPM Subscriber Private Meter
TIB Task Information Base
TMN Telecommunication Management Network
4 Information model diagrams
The entity relationship diagram is given in subclause 4.1 and the inheritance hierarchy (is-a relationships)
and naming hierarchy (containment relationships) are given in subclauses 4.2 and 4.3, respectively.
4.1 Entity relationship diagram
Figures 2 and 3 show the various entities related to traffic measurement and line testing at the AN. They
extend the information model described in ETS 300 376-1 [6], which covers the configuration aspects.
access
network
1 1 1
c c c
n n 1
log v5Interface
userPortTtp
test fragment
c
n
comm
1 1 1
Channel
c c c
n n 1
c
bearer comm
Channel
Channel
CurrentData CurrentData
n n
a a
1 1
scanReport simple
scan
Record Scanner
report
Figure 2: Entity relationship diagram - V5 traffic measurement and test fragment

Page 16
ETS 300 378-1: November 1995
access
network
C
test
testAction
fragment
Performer
1 1
C C
N N
loop access
A
A
userPortTtp userPortTtp
Test Test
1 1
1 M
1 1 1 1 1 1
C C C C C C
N N 1 1 N N
pattern electricalMeasurement dialledDigit dialTone testToLine
(1), (2), (3),
Test Test Test Test Test (4), (5)
NOTE: (1) = spmPulses
(2) = cablePairIdTone
(3) = ringing
(4) = dryLoop
(5) = voiceAccessTest
Figure 3: Entity relationship diagram - test fragment
4.1.1 Traffic measurement
Traffic measurements in the AN are concerned with bearer channel allocation and communication
channel traffic characteristics. Subclasses of ITU-T Recommendation Q.822 [17] currentData object
classes are used to store traffic measurement data obtained from the object instance they are contained
in. The current data is updated every 15 minutes.
The object class bearerChannelCurrentData has attributes for bearer channel oriented performance
measurements of a V5.2 interface. These measurements are obtained from the v5Interface object
instance representing a V5.2 interface which contains the bearerChannelCurrentData instance. For a V5.1
interface, no bearer channel related traffic measurements are foreseen. The object class
commChannelCurrentData is contained in an instance of commChannel. It has attributes for
communication channel oriented performance measurements related to a V5 communication channel.
Both object classes are described in detail in ETS 300 379-1 [8].
An instance of the ITU-T Recommendation X.738 [26] simpleScanner object class may be used to collect
the traffic measurement results stored in commChannelCurrentData and bearerChannelCurrentData
object instances in a certain time interval. It generates a scanReport notification being sent to the
managing system. In addition results may be logged in a scanReportRecord object instance which will
itself be contained in a log object.

Page 17
ETS 300 378-1: November 1995
4.1.2 Line testing and line circuit testing
Test requests from the OS are sent as Common Management Information Protocol (CMIP
...