SIST EN 301 006-1 V1.2.2:2005
(Main)Q3 interface at the Local Exchange (LE) for line and circuit testing of analogue and Integrated Services Digital Network (ISDN) subscriber lines; Part 1: Q3 interface specification
- Abstract
To define the Q3 interface for the control of line and circuit tests of analogue and ISDN subscriber lines. Applies to subscriber lines connected to LE only.
- Status
- Published
- Publication Date
- 30-Jun-2005
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Jul-2005
- Due Date
- 01-Jul-2005
- Completion Date
- 01-Jul-2005
SIST EN 301 006-1 V1.2.2:2005 is the Slovenian standard identical to EN 301 006-1 Version 1.2.2 from ETSI. It specifies the Q3 interface at the Local Exchange (LE) for line and circuit testing of analogue and Integrated Services Digital Network (ISDN) subscriber lines. The document is for telecommunications operators and equipment implementers who need to model, request, control, terminate, and report tests on subscriber lines connected directly to an LE.
What does SIST EN 301 006-1 V1.2.2:2005 specify?
SIST EN 301 006-1 V1.2.2:2005 specifies the Q3 interface between a Local Exchange (LE) and the Telecommunications Management Network (TMN) for line and circuit test functions on analogue and ISDN lines connected directly to the LE. It focuses on the management information model, not on Operations System (OS) functionality.
The standard says its object model is based on ETS 300 378-1 and ITU-T Recommendation X.745, with the LE-specific add-ons, modifications, and restrictions needed for this use case. It also states that existing protocols are used where possible.
| Annex | What it covers |
|---|---|
| Annex A | Requirements and parameter specification for access port tests |
| Annex B | Test categories for uncontrolled test requests |
| Annex C | Test termination rules for uncontrolled and controlled tests |
| Annex D | Test result notification content |
| Annex E | Additional requirements on the test action performer |
| Annex F | Task Information Base (TIB) |
| Annex G | Description of management functions |
| Annex H | Message flows |
| Annex J | Bibliography |
What are the key requirements of SIST EN 301 006-1 V1.2.2:2005?
The standard organizes line and circuit testing around managed objects, test categories, requests, result notifications, and termination rules. In practice, that means an implementation has to support a coherent management model, not just individual test commands.
Scope of managed testing
Clause 1 limits the interface to subscriber lines that are connected directly to the LE. The introduction also narrows the covered access paths to the part of the customer access between the LE and the network termination equipment, with ISDN access extending to but not including the T reference point.
This matters because the same test naming and signaling model is not intended for every part of the access network.
Test functions and categories
Annex A and Annex B describe the test families that can be managed through the Q3 interface. These include electrical measurement tests, dialled digit tests, dial tone tests, Subscriber Private Meter (SPM) pulse tests, ringing tests, test to line circuit, ISDN loopback test, and ISDN quick test.
The practical point is that the manager must choose the right category for the physical situation:
- some tests are outward tests and need customer assistance
- some are inward tests and are performed with the line disconnected
- some can work with the line connected or disconnected
- some involve only one access object, while others can involve one or more object instances
Scheduled, uncontrolled, and controlled testing
Annex A covers scheduled testing and test capability, while Annex C distinguishes uncontrolled tests from controlled tests. Uncontrolled tests terminate spontaneously when the test finishes, fails, or meets predefined criteria. Controlled tests can be one-step tests or test sessions.
This matters for implementation and operations planning because the management system must handle both immediate test execution and longer test sessions with later termination.
Test result notification
Clause 5.4 and Annex D define how test results are reported. Result notifications carry the test invocation identifier, and if the request included them, the test session identifier and associated object identifier. The notification can also carry detailed measurement data through the additionalInformation field.
For readers, this means test results are not just pass or fail. The model is designed to return enough correlation data and measurement detail for fault analysis and ticketing.
Supported-test reporting and error handling
Annex E requires that the supported capabilities of the agent system can be retrieved. Controlled tests are identified through the relevant TO classes, and uncontrolled tests through their request parameters. The annex also defines how the system responds when a requested test is not supported.
In practice, a manager can query what the LE can actually do before attempting a test, which helps avoid failed operations and ambiguous results.
Parameters, thresholds, and ASN.1 data types
Clause 6.7 and the ASN.1 module define the data carried in requests and results. These include IsdnQuickTestUncontrolledRequestType, IsdnQuickTestResult, NumberOfMTA, MtaMsg, and threshold types for AC voltage, DC voltage, capacitance, resistance, dial speed, and pulse no pulse ratio.
This is important for integration work because implementers need to encode and decode the exact management data used for test setup, threshold administration, and result reporting.
Protocol basis
Clause 7 states that the protocol suites for the Q3 interface are specified in ITU-T Recommendations Q.811 and Q.812. The present document adds no specific protocol requirements of its own.
That means interoperability depends on using the defined Q3 protocol profiles together with the management model in this standard.
What terms does SIST EN 301 006-1 V1.2.2:2005 define?
- Local Exchange (LE) - The exchange side of the access network where the line and circuit tests are controlled.
- Telecommunications Management Network (TMN) - The management framework used to control and supervise network elements and their functions.
- Managed Object Referring to Test (MORT) - The managed object associated with the test being conducted and reported.
- Test Object (TO) - The object that represents the specific test to be performed or managed.
- Task Information Base (TIB) - The service description structure used to describe management tasks such as fault detection, localization, and restoration.
- Relative Distinguished Name (RDN) - The naming attribute used to identify a managed object within the containment hierarchy.
- Subscriber Private Meter (SPM) - The private metering function at the customer premises that can be verified by sending metering pulses.
- Basic Access (BA) - The ISDN access type used in the document’s ISDN testing model.
Who uses SIST EN 301 006-1 V1.2.2:2005?
SIST EN 301 006-1 V1.2.2:2005 is used by telecommunications operators, TMN engineers, Local Exchange maintainers, and network management system developers. It is also relevant to test equipment vendors and suppliers of LE or ISDN switching equipment.
In practice, these users apply it for tasks such as starting and stopping line tests, scheduling periodic checks, connecting external test systems, setting thresholds, reporting failures, and correlating results from controlled and uncontrolled tests. The annexes on Task Information Base and message flows make it particularly useful for fault detection, fault localization, verification after repair, and restoration to service.
Which standards are used with SIST EN 301 006-1 V1.2.2:2005?
| Reference | What it contributes |
|---|---|
| ETS 300 378-1 | Base Q3 interface object model for the access network, used as the starting point for this LE-specific model |
| ITU-T Recommendation X.745 | Test management function, including test requests, results, and termination behavior |
| ITU-T Recommendation X.737 | TestConditions used by the quick test request type |
| ITU-T Recommendation X.721 and X.730 | Object management and generic notifications such as creation, deletion, and attribute change |
| ITU-T Recommendation X.731 | State management, including state change notifications |
| ITU-T Recommendation X.732 | Relationship attributes and relationship change notifications |
| CCITT Recommendation M.3100 | Generic network information model and naming support |
| CCITT Recommendation M.3010 | Telecommunications management network principles and the definition of Operations System |
| ITU-T Recommendations Q.811 and Q.812 | Lower and upper layer protocol profiles for the Q3 interface |
| ETS 300 324-1 | Definitions for Access Network and Local Exchange used in the terminology |
The foreword also names Part 2 of the multi-part document: Managed Object Conformance Statement (MOCS) proforma specification.
What does the SIST EN 301 006-1 V1.2.2:2005 document contain?
The document contains an information model, object class descriptions, formal object definitions, parameters, and protocol guidance for LE line and circuit testing. It includes entity relationship, inheritance, and naming diagrams that show how the test-related managed objects fit together.
It also contains the ASN.1 module that defines the test-related data types, thresholds, enumerations, and request/result structures. Annexes add the test requirements, test categories, termination rules, result notification content, supported-test reporting, service/task descriptions, and message flow examples used for implementation and interoperability work.
Get Certified
Connect with accredited certification bodies for this standard

ANCE
Mexican certification and testing association.

Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 301 006-1 V1.2.2:2005 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Q3 interface at the Local Exchange (LE) for line and circuit testing of analogue and Integrated Services Digital Network (ISDN) subscriber lines; Part 1: Q3 interface specification". This standard covers: To define the Q3 interface for the control of line and circuit tests of analogue and ISDN subscriber lines. Applies to subscriber lines connected to LE only.
To define the Q3 interface for the control of line and circuit tests of analogue and ISDN subscriber lines. Applies to subscriber lines connected to LE only.
SIST EN 301 006-1 V1.2.2:2005 is classified under the following ICS (International Classification for Standards) categories: 33.080 - Integrated Services Digital Network (ISDN). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 301 006-1 V1.2.2:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-julij-2005
9PHVQLN4SULNUDMHYQLFHQWUDOL]DSUHVNXãDQMHYRGRYLQYH]LMDQDORJQLKLQ,6'1
QDURþQLãNLKSULNOMXþNRYGHO6SHFLILNDFLMD]DYPHVQLN4
Q3 interface at the Local Exchange (LE) for line and circuit testing of analogue and
Integrated Services Digital Network (ISDN) subscriber lines; Part 1: Q3 interface
specification
Ta slovenski standard je istoveten z: EN 301 006-1 Version 1.2.2
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EN 301 006-1 V1.2.2 (1998-08)
European Standard (Telecommunications series)
Q3 interface at the Local Exchange (LE)
for line and circuit testing of analogue
and Integrated Services Digital network (ISDN)
subscriber lines;
Part 1: Q3 interface specification
2 EN 301 006-1 V1.2.2 (1998-08)
Reference
DEN/SPS-03030-1 (9bc90ipc.PDF)
Keywords
TMN, information model, Q3 interface, LE, fault,
testing, management, PSTN, ISDN
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Internet
secretariat@etsi.fr
http://www.etsi.fr
http://www.etsi.org
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 1998.
All rights reserved.
ETSI
3 EN 301 006-1 V1.2.2 (1998-08)
Contents
Intellectual Property Rights.7
Foreword .7
Introduction .7
1 Scope.9
2 References.9
3 Definitions and abbreviations .10
3.1 Definitions . 10
3.2 Abbreviations. 11
4 Information model diagrams .12
4.1 Entity relationship diagram. 12
4.1.1 Line testing and line circuit testing. 13
4.1.2 The testResultNotifications of the tests . 13
4.2 Inheritance hierarchy . 14
4.3 Naming hierarchy. 14
5 Information model description.15
5.1 Description of object classes. 15
5.1.1 Access port fragment. 15
5.1.2 Support fragment. 15
5.1.2.1 Event report management . 15
5.1.2.2 Log control function . 15
5.1.3 Test fragment . 16
5.1.3.1 Access test (accessTest). 16
5.1.3.2 Dialled digit test (dialledDigitTest) . 16
5.1.3.3 Dial tone test (dialToneTest) . 16
5.1.3.4 Electrical measurement test (electricalMeasurementTest). 17
5.1.3.5 Subscriber Private Meter (SPM) pulses (spmPulses) . 17
5.1.3.6 Cable pair identification tone (cablePairIdTone). 17
5.1.3.7 Ringing (ringing) . 17
5.1.3.8 Test to line circuit (testToLineCircuit) . 17
5.1.3.9 Dry Loop (dryLoop) . 17
5.1.3.10 Loop test (loopTest) . 18
5.1.3.11 Pattern test (patternTest). 18
5.1.3.12 Voice access test (voiceAccessTest). 18
5.1.3.13 Metallic test access (metallicTestAccess). 19
5.1.3.14 Test threshold class administration (testThresholdClass) . 19
5.1.3.15 ISDN quick test (isdnQuickTest). 20
5.2 Definition of attributes. 20
5.2.1 Relative distinguished name. 20
5.2.2 State attributes. 20
5.2.2.1 Operational state (operationalState) . 20
5.2.2.2 Administrative state (administrativeState). 21
5.2.2.3 Availability status (availabilityStatus) . 21
5.2.3 Relationship attributes. 21
5.3 Actions description . 21
5.4 Notifications description. 21
6 Formal object class definitions .22
6.1 Definitions of object classes . 22
6.1.1 Access port fragment. 22
6.1.2 Support fragment. 22
6.1.3 Test fragment . 22
6.1.3.1 ISDN quick test . 23
6.1.3.2 Metallic test access . 23
ETSI
4 EN 301 006-1 V1.2.2 (1998-08)
6.1.3.3 Test threshold class. 24
6.2 Name bindings . 24
6.2.1 Test fragment . 24
6.2.1.1 ISDN quick test . 24
6.2.1.2 Metallic test access . 24
6.2.1.3 Test threshold class. 24
6.3 Definition of packages . 25
6.3.1 Metallic test access line package. 25
6.4 Definition of attributes. 25
6.4.1 AC voltage threshold. 25
6.4.2 Capacitance threshold . 25
6.4.3 DC voltage threshold. 25
6.4.4 Dial speed threshold. 25
6.4.5 ISDN quick test. 26
6.4.6 Metallic test access message . 26
6.4.7 Metallic test access timeout period. 26
6.4.8 Proposed metallic test access . 27
6.4.9 Pulse no pulse ratio . 27
6.4.10 Resistance threshold. 27
6.4.11 Test threshold class ID . 27
6.4.12 Type of line . 27
6.5 Definition of actions . 27
6.6 Definition of notifications. 27
6.7 Definition of parameters . 27
6.8 ASN.1 defined types module . 29
7 Protocol requirements .31
Annex A (normative): Requirements and specification of parameters for access port tests.32
A.1 General test requirements .32
A.1.1 Scheduled testing . 32
A.1.2 Test capability. 32
A.2 Access port test requirements .32
A.2.1 Access port test management functions . 32
A.2.2 Test scheduling . 33
A.2.3 Test result management . 33
A.2.4 Test threshold management. 34
A.2.5 Test requirements description . 34
A.2.5.1 PSTN line testing . 34
A.2.5.1.1 Foreign voltage or current . 34
A.2.5.1.2 Capacitance measurement. 34
A.2.5.1.3 Insulation resistance measurement. 34
A.2.5.1.4 Loop resistance measurement. 35
A.2.5.1.5 Dial pulse test . 35
A.2.5.1.6 DTMF dialling test . 35
A.2.5.1.7 Subscriber private meter testing . 35
A.2.5.1.8 Ring subscriber. 35
A.2.5.1.9 Monitoring of the line. 35
A.2.5.1.10 Cable pair identification tone. 35
A.2.5.1.11 Dry loop. 35
A.2.5.1.12 Register recall button test . 36
A.2.5.1.13 Ring back procedure. 36
A.2.5.2 PSTN inward tests. 36
A.2.5.2.1 Line circuit testing . 36
A.2.5.2.1.1 Feeding voltage. 36
A.2.5.2.1.2 Feeding current . 36
A.2.5.2.1.3 Loop and ring trip detection. 36
A.2.5.2.1.4 Ringing current sending . 36
A.2.5.2.1.5 Private meter pulses . 36
A.2.5.2.1.6 Codec testing. 37
ETSI
5 EN 301 006-1 V1.2.2 (1998-08)
A.2.5.2.1.7 Digit reception . 37
A.2.5.2.2 Other inward tests. 37
A.2.5.2.2.1 Dial tone test . 37
A.2.5.3 ISDN BA testing . 37
A.2.5.3.1 ISDN BA line testing. 37
A.2.5.3.2 ISDN BA line termination testing. 37
A.2.5.3.2.1 Loopbacks. 37
A.2.5.3.2.2 Activation and deactivation of lines. 38
A.2.5.3.3 ISDN BA line circuit testing. 38
A.2.5.3.3.1 Power feed . 38
A.2.5.4 ISDN PRA testing . 38
A.2.5.4.1 ISDN PRA line testing. 38
A.2.5.4.2 ISDN PRA line termination testing . 38
A.2.5.5 ISDN BA and PRA quick tests. 38
A.2.5.6 Connection of external test systems . 38
Annex B (normative): Test categories.39
B.1 Electrical measurement tests.39
B.2 Dialled digit test.40
B.3 Dial tone test .41
B.4 Subscriber private meter pulses test.42
B.5 Ringing test .42
B.6 Test to line circuit .43
B.7 ISDN loopback test .44
B.8 ISDN quick test.45
Annex C (normative): Test termination.47
C.1 Termination of uncontrolled tests .47
C.2 Termination of controlled tests .47
Annex D (normative): Test result notification .49
Annex E (normative): Additional requirements on the test action performer.50
E.1 Indication of supported tests .50
E.2 Indication of unsuccessful test requests.50
Annex F (informative): Task Information Base (TIB) .51
F.1 Description of the service .51
F.2 Components of service (TIB A).51
F.3 Management function list (TIB B).52
Annex G (informative): Description of management functions .53
G.1 Model for the test function.53
G.1.1 Environment. 53
G.1.2 Uncontrolled tests . 53
G.1.3 Controlled tests . 54
G.2 Functional model.55
G.2.1 Test initiation. 55
G.2.2 Test scheduling . 55
G.2.3 Reporting of test results . 56
G.2.4 Test suspension and resumption. 57
ETSI
6 EN 301 006-1 V1.2.2 (1998-08)
G.2.5 Test termination . 57
Annex H (informative): Message flows.58
Annex J (informative): Bibliography.61
History.62
ETSI
7 EN 301 006-1 V1.2.2 (1998-08)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)
which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Signalling
Protocols and Switching (SPS).
The present document is part 1 of a multi-part document covering the Q3 interface at the Local Exchange (LE) for line
and circuit testing of analogue and ISDN subscriber lines, as identified below:
Part 1: "Q3 interface specification";
Part 2: "Managed Object Conformance Statement (MOCS) proforma specification".
Proposed national transposition dates
Date of adoption of this EN: 7 August 1998
Date of latest announcement of this EN (doa): 30 November 1998
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 May 1999
Date of withdrawal of any conflicting National Standard (dow): 31 May 1999
Introduction
Line and circuit testing of analogue and ISDN lines 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.
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.
Here, only these parts of the activity are covered which are related directly to that part of the customer access which
extends from the LE 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).
ETSI
8 EN 301 006-1 V1.2.2 (1998-08)
Q(LE)
ZLE
PSTNPSTN
TEUP
T
ISDNISDN
NT1
TEUP
T
ISDNISDN
TEUP
NOTE: Shaded areas are subject to line and circuit testing. User ports represent the different configurations for
Line Circuit (LC), Line Termination (LT), Exchange Termination (ET) and Network Termination (NT). The
option of ISDN access without remote NT1 is valid for ISDN BA only.
Figure 1: Scope of line and circuit testing
The present document details only those functions and management information model components which are required
for line and circuit testing. However, the use of other components which may be applicable from other specifications is
not precluded. In this case, combined applications incorporating line and circuit test specific and more generic aspects
would result.
ETSI
9 EN 301 006-1 V1.2.2 (1998-08)
1 Scope
The present document specifies the Q3 interface between an Local Exchange (LE) and the Telecommunications
Management Network (TMN) for the support of line and circuit test functions for analogue and ISDN lines which are
connected directly to a LE.
The focus of the present document is on defining an object model based on the existing standards ETS 300 378-1 [3]
and ITU-T Recommendation X.745 [20]. The add-ons, modifications and restrictions to these standards are specified
which are necessary to adapt the object model to a LE. Existing protocols are used where possible. The definition of
Operations System (OS) functionality is outside the scope of the present document.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, subsequent revisions do apply.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] I-ETS 300 291 (1995): "Network Aspects (NA); Functional specification of Customer
Administration (CA) on the Operations System/Network Element (OS/NE) interface".
[2] ETS 300 324-1: "Signalling Protocols and Switching (SPS); V interfaces at the digital Local
Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 1: V5.1 interface
specification".
[3] ETS 300 378-1 (1995): "Signalling Protocols and Switching (SPS); Q3 interface at the Access
Network (AN) for fault and performance management of V5 interfaces and associated customer
profiles; Part 1: Q3 interface specification".
[4] CCITT Recommendation M.3010 (1992): "Principles for a telecommunications management
network".
[5] CCITT Recommendation M.3100 (1992): "Generic network information model".
[6] ITU-T Recommendation M.3603: "Application of maintenance principles to ISDN basic rate
access".
[7] ITU-T Recommendation M.3604: "Application of maintenance principles to ISDN primary rate
access".
[8] ITU-T Recommendation Q.543 (1993): "Digital exchange performance design objectives".
[9] ITU-T Recommendation Q.811 (1993): "Lower layer protocol profiles for the Q3 interface".
[10] ITU-T Recommendation Q.812 (1993): "Upper layer protocol profiles for the Q3 interface".
[11] CCITT Recommendation X.208 (1988): "Specification of Abstract Syntax Notation One
(ASN.1)".
[12] CCITT Recommendation X.720 | ISO/IEC 10165-1: "Information technology - Open systems
interconnection - Structure of management information: Management information model".
[13] CCITT Recommendation X.721 | ISO/IEC 10165-2: "Information technology - Open systems
interconnection - Structure of management information: Definition of management information".
ETSI
10 EN 301 006-1 V1.2.2 (1998-08)
[14] CCITT Recommendation X.730 | ISO/IEC 10164-1: "Information technology - Open systems
interconnection - Systems management: Object management function".
[15] CCITT Recommendation X.731 | ISO/IEC 10164-2: "Information technology - Open systems
interconnection - Systems management: State management function".
[16] CCITT Recommendation X.732 | ISO/IEC 10164-3: "Information technology - Open systems
interconnection - Systems management: Attributes for representing relationships".
[17] CCITT Recommendation X.734 | ISO/IEC 10164-5: "Information technology - Open systems
interconnection - Systems management: Event report management function".
[18] CCITT Recommendation X.735 | ISO/IEC 10164-6: "Information technology - Open systems
interconnection - Systems management: Log control functions".
[19] ITU-T Recommendation X.737 | ISO/IEC 10164-14: "Information technology - Open systems
interconnection - Systems management: Confidence and diagnostic test function".
[20] ITU-T Recommendation X.745 | ISO/IEC 10164-12: "Information technology - Open systems
interconnection - Systems management: Test management function".
[21] ITU-T Recommendation X.746 | ISO/IEC 10164-15: "Information technology - Open systems
interconnection - Systems management: Scheduling function".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following definitions apply:
Access Network (AN): See ETS 300 324-1 [2].
activation-deactivation of the line: See subclause A.2.5.
cable pair identification tone: See subclause A.2.5.
capacitance measurement: See subclause A.2.5.
Codec testing: See subclause A.2.5.
dial pulse test: See subclause A.2.5.
dial tone test: See subclause A.2.5.
digit reception: See subclause A.2.5.
dry loop: See subclause A.2.5.
Dual Tone Multi-Frequency (DTMF) dialling test: See subclause A.2.5.
feeding current: See subclause A.2.5.
feeding voltage: See subclause A.2.5.
foreign voltage: See subclause A.2.5.
insulation resistance measurement: See subclause A.2.5.
line circuit testing: See subclause A.2.5.
line testing: See subclause A.2.5.
Local Exchange (LE): See ETS 300 324-1 [2].
ETSI
11 EN 301 006-1 V1.2.2 (1998-08)
loop and ring trip detection: See subclause A.2.5.
loop resistance measurement: See subclause A.2.5.
loopback 1 (line termination loopback): See subclause A.2.5.
loopback 2, 2 and 1A (NT1 loopbacks): See subclause A.2.5.
monitoring of the line with mark tone: See subclause A.2.5.
monitoring of the line: See subclause A.2.5.
Operations System (OS): See CCITT Recommendation M.3010 [4].
power feed: See subclause A.2.5.
private meter pulses: See subclause A.2.5.
register recall button test: See subclause A.2.5.
subscriber private metering: See subclause A.2.5.
3.2 Abbreviations
For the purpose of the present document, the following abbreviations apply:
AC Alternating Current
AN Access Network
ASN.1 Abstract Syntax Notation One (see CCITT Recommendation X.208 [11])
BA Basic Access
CMIP Common Management Information Protocol
CPE Customer Premise Equipment
DC Direct Current
DTMF Dual Tone Multi-Frequency
ET Exchange Termination
ID Identity, identifier
ISDN Integrated Services Digital Network
LC Line Circuit
LE Local Exchange
LT Line Termination
M/C Mandatory/Conditional
MORT Managed Object Referring to Test
NE Network Element
NT Network Termination
OS Operations System
PRA Primary Rate Access
PSTN Public Switched Telephone Network
RDN Relative Distinguished Name
REG Regenerator
SPM Subscriber Private Meter
TARR Test Action Request Receiver
TIB Task Information Base
TMN Telecommunication Management Network
TO Test Object
ETSI
12 EN 301 006-1 V1.2.2 (1998-08)
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
Figure 2 shows the various entities related to line and circuit testing at the LE. They extend the information model
described in I-ETS 300 291 [1], which specifies management information describing the various user port aspects.
managed
Element
test
fragment
1 1
C C
N
test
testAction
Threshold
Performer
Class
a
1 1 1
C C C
N
N N N
metallic
access loop access access
a
Test a
Port Test Test Port
1 1 Access
1 M
a
1 1
1 1 1
C C C
N
N N
pattern isdn
(note)
Test QuickTest
NOTE: Other specific test object classes are defined in ETS 300 378-1 [3].
Figure 2: Entity relationship diagram - test fragment
ETSI
13 EN 301 006-1 V1.2.2 (1998-08)
4.1.1 Line testing and line circuit testing
Test requests from the OS are sent as Common Management Information Protocol (CMIP) testRequestControlled or
testRequestUncontrolled action to an instance of testActionPerformer. In this model, all controlled tests are delegated by
instances of testActionPerformer to instances of subclasses of testObject, i.e. when receiving a test request the
testActionPerformer automatically creates the required instances of these classes. Further instances of subclasses of
testObject are created if further delegation of the performance of the test is required. This creation is achieved by
sending additional testRequestControlled actions, the testSessionId parameter is used to identify in which access test
instance the new tests should be contained. All instances of these subclasses of testObject exist only for the duration of
their delegated operations. Details of the mechanism how to transmit test requests to testActionPerformer and how test
results are generated are described in ITU-T Recommendation X.745 [20].
Management information related to uncontrolled tests can be found in annex B.
Controlled testing is initially delegated to an instance of accessTest or to an instance of loopTest or to an instance of
metallicTestAccess. Each instance of loopTest or accessTest or metallicTestAccess is contained in an instance of
testActionPerformer.
The object class loopTest is used to set up loopbacks for the user port to which it is associated by an attribute. If patterns
are to be injected and compared within the LE as part of the loopback test, then this is delegated to an instance of
patternTest which is contained in the delegating instance of loopTest.
The object class accessTest has all specific non-loopback tests allocated to it. It has an attribute which specifies one or a
list of user ports which are to be tested.
If external test systems are used for line testing, the metallicTestAccess allows to connect it to each subscriber line
(outbound or bridged) and to each line circuit (inbound) of the LE. The implementation of the metallic test access is
outside the scope of this standard.
The creation of an instance of accessTest represents a test session and permits test access to lines or line circuits during
which a number of different tests can be performed. These delegated tests are handled by specific contained test objects.
Each contained test object triggers the specific test on one or more user ports which are specified in accessTest.
Electrical measurements, such as voltage, capacitance and resistance, are delegated to instances of
electricalMeasurementTest. Dialled digit tests, dial tone tests and other tests (in particular those involving sending meter
pulses to the line, cable pair identification tone and ringing) are triggered by the creation of instances of
dialledDigitTest, dialToneTest, spmPulses, cablePairIdTone and ringing, respectively. The dry loop condition is set up
by instances of dryLoopTest. The inward line circuit tests are delegated to instances of testToLineCircuit. The
voiceAccessTest allows for the provision of those test which involve the establishment of a voice connection with the
line under test. A quick check of an ISDN access is represented by a isdnQuickTest object.
The object class testThresholdClass can be used to modify predefined test thresholds via the Q3 interface.
4.1.2 The testResultNotifications of the tests
The sending time, the information contents and the number of testResultNotifications sent per test request are not
restricted. It is a matter up to the LE implementation. If the testResultNotification contains results whose testing time has
importance, they shall be ordered in the ASN.1 sequence oldest first.
ETSI
14 EN 301 006-1 V1.2.2 (1998-08)
4.2 Inheritance hierarchy
Figure 3 traces the inheritance from the highest level object "CCITT Recommendation X.721:1992":top to the managed
objects defined in the present document.
"X.721": "X.745":
top testActionPerformer
testThresholdClass
"X.745":
metallicTestAccess
testObject
isdnQuickTest
other specific
test objects
as specified in
ETS 300 378-1
NOTE: Only classes which are underlined may be instantiated.
Figure 3: Inheritance hierarchy
4.3 Naming hierarchy
Figure 4 shows the naming (i.e. containment) relationships for the LE's managed objects associated with line and circuit
testing.
"M.3100":
managedElement
"X.745":
testThresholdClass
testActionPerformer
accessTest
metallicTestAccess
loopTest
isdnQuickTest other specific test objects
patternTest
as specified in ETS 300 378-1
Figure 4: Naming hierarchy
ETSI
15 EN 301 006-1 V1.2.2 (1998-08)
5 Information model description
This clause provides a high-level informal description of the management information model for line and circuit testing
in the LE.
Subclause 5.1 contains a brief description for each object class or package used in the model as far as it is not described
in the reference documents. The description covers:
- the purpose of the object class or package;
- the attributes defined for the object class or package;
- the contents of the event reports defined in the present document;
- the relationship of the object class to other object classes;
- the applicability of these packages.
Attributes which are common to several object classes are described in subclause 5.2. Subclause 5.3 describes actions
which are common to several object classes in the information model. Subclause 5.4 describes the common aspects of
the notifications used in the information model.
5.1 Description of object classes
5.1.1 Access port fragment
In this fragment the following object classes are used. They are used in the test operations to identify the MORTs. They
are defined in I-ETS 300 291 [1]:
- "I-ETS 300 291":analogueAccess;
- "I-ETS 300 291":basicRateAccess;
- "I-ETS 300 291":primaryRateAccess.
5.1.2 Support fragment
5.1.2.1 Event report management
Event reporting manage
...



