SIST EN 300 378-1 V1.2.1:2003

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.YQHJDLGUXåHQLKTelecommunications Management Network (TMN); Q3 interface at the Access Network (AN) for fault and performance management of V5 interfaces and associated user ports; Part 1: Q3 interface specification33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 300 378-1 Version 1.2.1SIST EN 300 378-1 V1.2.1:2003en01-november-2003SIST EN 300 378-1 V1.2.1:2003SLOVENSKI
STANDARD
ETSIETSI EN 300 378-1 V1.2.1 (1999-10)2ReferenceREN/TMN-02003-1 (3i090ioo.PDF)KeywordsAN, information model, management,performance, Q3 interface, TMN, V5 interfaceETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frIndividual copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: editor@etsi.frImportant noticeThis ETSI deliverable may be made available in more than one electronic version or in print. In any case of existing orperceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).In case of dispute, the reference should be the printing on ETSI printers of the PDF version kept on a specific networkdrive within ETSI Secretariat.Copyright NotificationNo 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 1999.All rights reserved.SIST EN 300 378-1 V1.2.1:2003

ETSIETSI EN 300 378-1 V1.2.1 (1999-10)3ContentsIntellectual Property Rights.8Foreword.8Introduction.81Scope.102References.103Definitions and abbreviations.123.1Definitions.123.2Abbreviations.134Information model diagrams.144.1Entity relationship diagram.144.1.1Traffic measurement.154.1.2Line testing and line circuit testing.154.1.3The test result notifications of the tests.164.1.4Performance monitoring of ISDN user ports.164.2Inheritance hierarchy.174.3Naming hierarchy.185Information model description.195.1Managed object classes description.195.1.1V5 interface fragment.195.1.2User port fragment.195.1.2.1PSTN user port (pstnUserPort).205.1.2.2ISDN basic access user port (isdnBAUserPort).205.1.2.3ISDN primary rate access user port (isdnPRAUserPort).215.1.2.4Leased port (leasedPort).215.1.3Communication path fragment.215.1.4Protection fragment.215.1.5Performance fragment.225.1.5.1Bearer channel current data.225.1.5.2Bearer channel history data.225.1.5.3Communication channel current data.225.1.5.4Communication channel history data.225.1.6Alarm surveillance fragment.225.1.7Support fragment.225.1.8Test fragment.235.1.8.1Access test (accessTest).235.1.8.2Cable pair identification Tone (cablePairIdTone).235.1.8.3Dialled digit test (dialledDigitTest).235.1.8.4Dial tone test (dialToneTest).245.1.8.5Dry Loop (dryLoop).245.1.8.6Electrical measurement test (electricalMeasurementTest).245.1.8.7ISDN quick test (isdnQuickTest).255.1.8.8Loop test (loopTest).255.1.8.9Metallic test access (metallicTestAccess).265.1.8.10Pattern test (patternTest).265.1.8.11Ringing (ringing).275.1.8.12Subscriber Private Meter (SPM) pulses (spmPulses).275.1.8.13Test to line circuit (testToLineCircuit).275.1.8.14Test threshold class (testThresholdClass).285.1.8.15Voice Access Test (voiceAccessTest).285.2Attributes description.285.3Actions description.285.4Notifications description.29SIST EN 300 378-1 V1.2.1:2003

ETSIETSI EN 300 378-1 V1.2.1 (1999-10)46Formal managed object classes definitions.296.1V5 interface fragment.296.2Access port fragment.296.3Communication path fragment.306.4Protection fragment.306.5Performance fragment.306.6Alarm surveillance fragment.306.7Support fragment.316.8Test fragment.317Protocol requirements.31Annex A (normative):Specification of parameters for V5 specific alarm reports.32A.1Alarm reports related to the V5 interface object class.32A.1.1Control protocol errors.32A.1.2Link control protocol errors.33A.1.3BCC protocol errors.33A.1.4Protection protocol errors.33A.1.5PSTN protocol errors.34A.1.6Interface control failures.34A.1.7V5 data link failures.34A.2Alarm reports related to the V5 trail termination point object class.35A.2.1Link control failures.35A.2.2Link layer 1 failures.36A.3Alarm reports related to the V5 time slot object class.37A.3.1V5 communication channel failures.37A.4Alarm reports related to the user port object class and subclasses.37A.4.1Control protocol errors.37A.4.2PSTN protocol errors.38A.4.3ISDN layer 1 faults (Q(AN) only).38A.4.3.1ISDN BA layer 1 faults (Q(AN) only).38A.4.3.2ISDN PRA layer 1 faults (Q(AN) only).39A.4.4ISDN layer 2 faults (Q(AN) only).40A.4.5Line faults (Q(AN) only).40Annex B (normative):V5 specific traffic measurement.41Annex C (normative):Requirements and specification of parameters for user port tests.42C.1General test requirements.42C.1.1Scheduled testing.42C.1.2Test capability.42C.2V5 interface test requirements.42C.2.1V5 interface ID testing.42C.2.2Link ID testing.42C.2.3Provisioning variant testing.42C.3User port test requirements.43C.3.1User port test management functions.43C.3.2Test scheduling.43C.3.3Test result management.44C.3.4Test threshold management.44C.3.5Test requirements description.44C.3.5.1PSTN line testing.45C.3.5.1.1Foreign voltage or current.45C.3.5.1.2Capacitance measurement.45C.3.5.1.3Insulation resistance measurement.45C.3.5.1.4Loop resistance measurement.45C.3.5.1.5Dial pulse test.45SIST EN 300 378-1 V1.2.1:2003

ETSIETSI EN 300 378-1 V1.2.1 (1999-10)5C.3.5.1.6DTMF dialling test.46C.3.5.1.7Subscriber private meter testing.46C.3.5.1.8Ring subscriber.46C.3.5.1.9Monitoring of the line.46C.3.5.1.10Cable pair identification tone.46C.3.5.1.11Dry loop.46C.3.5.1.12Register recall button test.46C.3.5.1.13Ring back procedure.47C.3.5.2PSTN inward tests.47C.3.5.2.1Line circuit testing.47C.3.5.2.1.1Feeding voltage.47C.3.5.2.1.2Feeding current.47C.3.5.2.1.3Loop and ring trip detection.47C.3.5.2.1.4Ringing current sending.47C.3.5.2.1.5Private meter pulses.47C.3.5.2.1.6Codec testing.47C.3.5.2.1.7Digit reception.48C.3.5.2.2Other inward tests.48C.3.5.2.2.1Dial tone test.48C.3.5.3ISDN BA testing.48C.3.5.3.1ISDN BA line testing.48C.3.5.3.2ISDN BA line termination testing.48C.3.5.3.2.1Loop backs.48C.3.5.3.2.2Activation and deactivation of lines.48C.3.5.3.3ISDN BA line circuit testing.49C.3.5.3.3.1Power feed.49C.3.5.4ISDN PRA testing.49C.3.5.4.1ISDN PRA line testing.49C.3.5.4.2ISDN PRA line termination testing.49Annex D (normative):Test categories.50D.1Dialled digit test.50D.1.1Test category name.50D.1.2Test category purpose.50D.1.3MORT requirements.50D.1.4Associated object requirements.50D.1.5Test environment.50D.1.6Test request service type.50D.1.7Specific errors.50D.1.8Test category information parameter.51D.1.9Uncontrolled test response additional information parameter.51D.2Dial tone test.51D.2.1Test category name.51D.2.2Test category purpose.51D.2.3MORT requirements.51D.2.4Associated object requirements:.51D.2.5Test environment.51D.2.6Test request service type.51D.2.7Specific errors.51D.2.8Test category information parameter.52D.2.9Uncontrolled test response additional information parameter.52D.3Electrical measurement tests.52D.3.1Test category name.52D.3.2Test category purpose.52D.3.3MORT requirements.52D.3.4Associated object requirements.52D.3.5Test environment.52D.3.6Test request service type.52D.3.7Specific errors.53SIST EN 300 378-1 V1.2.1:2003

ETSIETSI EN 300 378-1 V1.2.1 (1999-10)6D.3.8Test category information parameter.53D.3.9Uncontrolled test response additional information parameter.53D.4ISDN quick test.53D.4.1Test category name.53D.4.2Test category purpose:.53D.4.3MORT requirements.53D.4.4Associated object requirements.53D.4.5Test environment.53D.4.6Test request service type:.54D.4.7Specific errors.54D.4.8Test category information parameter.54D.4.9Uncontrolled test response additional information parameter.54D.5Loop back test.54D.5.1Test category name.54D.5.2Test category purpose:.54D.5.3MORT requirements.54D.5.4Associated object requirements.54D.5.5Test environment.54D.5.6Test request service type:.55D.5.7Specific errors.55D.5.8Test category information parameter.55D.5.9Uncontrolled test response additional information parameter.55D.6Ringing test.55D.6.1Test category name.55D.6.2Test category purpose.55D.6.3MORT requirements.55D.6.4Associated object requirements.55D.6.5Test environment.56D.6.6Test request service type.56D.6.7Specific errors.56D.6.8Test category information parameter.56D.6.9Uncontrolled test response additional information parameter.56D.7Subscriber private meter pulses test.56D.7.1Test category name.56D.7.2Test category purpose.56D.7.3MORT requirements.56D.7.4Associated object requirements.56D.7.5Test environment.57D.7.6Test request service type.57D.7.7Specific errors.57D.7.8Test category information parameter.57D.7.9Uncontrolled test response additional information parameter.57D.8Test to line circuit test.57D.8.1Test category name.57D.8.2Test category purpose.57D.8.3MORT requirements.58D.8.4Associated object requirements.58D.8.5Test environment.58D.8.6Test request service type:.58D.8.7Specific errors.58D.8.8Test category information parameter.58D.8.9Uncontrolled test response additional information parameter.58SIST EN 300 378-1 V1.2.1:2003

ETSIETSI EN 300 378-1 V1.2.1 (1999-10)7Annex E (informative):Task Information Base (TIB).59Annex F (informative):Description of management functions.60Annex G (informative):Description of test procedures.61G.1Background.61G.2Test procedures scenario.61G.2.1Scenario for faultsman ringback tests in an AN environment.61G.2.2Scenario for a subscriber assisted test in an AN environment.63G.2.2.1Existing connection mode.63G.2.2.2Parallel voice path mode.64Annex H (informative):Summary of requirements.65Annex J (informative):State management in relation with line testing - Application for V5access networks.66J.1Intrusive tests.66J.2Dealing with conflicts between intrusive tests and normal service.66J.3State values during intrusive testing.67J.4V5 blocking mechanism.67Annex K (informative):Message flows.69Bibliography.72History.73SIST EN 300 378-1 V1.2.1:2003

ETSIETSI EN 300 378-1 V1.2.1 (1999-10)8Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server(http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan 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.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical CommitteeTelecommunications Management Network (TMN).The present document is part 1 of a multi-part EN covering the Access Network (AN), as identified below:Part 1:"Q3 interface specification";Part 2:"Managed Objects Conformance Statement (MOCS) proforma" (for further study).National transposition datesDate of adoption of this EN:15 October 1999Date of latest announcement of this EN (doa):31 January 2000Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 July 2000Date of withdrawal of any conflicting National Standard (dow):31 July 2000IntroductionV5 interfaces, as described in EN 300 324-1 [4] and EN 300 347-1 [5], operate between a Local Exchange (LE) and anAccess Network (AN) to support various narrowband Integrated Services Digital Network (ISDN) and Public SwitchedTelephone Network (PSTN) services. These interfaces and their associated user ports need to be managed by theOperations Systems (OSs) within the Telecommunications Management Network (TMN). This management isperformed by means of Q3 interfaces.The companion standard on configuration management EN 300 376-1 [6] defines how the Q3 interface of an ANhandles the configuration information for V5 interfaces and their associated user ports. The present document specifiesthe 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 theoperator in order to detect failure conditions and to bring the customer access back to its normal state of operationwhenever a deviation occurs.Performance management of V5 interfaces and associated user ports is part of a management activity which is employedin order to maintain the quality of service levels agreed with the customers. The activities undertaken in performancemanagement 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 terminationequipment up to and including the exchange termination.SIST EN 300 378-1 V1.2.1:2003

ETSIETSI EN 300 378-1 V1.2.1 (1999-10)9Here, only these parts of the activities are covered which are related directly to a V5 interface between a LE and an ANor to that part of the customer access which extends from the AN to the network termination equipment. An ISDNaccess extends to but does not include the T reference point. An analogue access extends to and may include theCustomer Premise Equipment (CPE) (see figure 1).V5Q(LE)Q(AN)ANZTPSTNTETLEV5TPV5TPNT1ISDNTEISDNTEPSTNUPISDNUPISDNUPLL UPTENOTE:Shaded areas are subject to V5 fault and performance management. User ports represent the differentconfigurations for Line Circuit (LC), Line Termination (LT), Exchange Termination (ET) and NetworkTermination (NT) as indicated in EN 300 324-1 [4] and EN 300 347-1 [5]. For leased lines(semi-permanent lines), the present document only covers aspects which are common to PSTNand ISDN.Figure 1: Scope of V5 fault and performance managementThe present document details only those functions and management information model components for which V5specific descriptions are required. However, the use of other components which may be applicable from otherspecifications is not precluded. In this case, combined applications incorporating both V5 specific and more genericaspects would result. For example, if log control is to be provided in conjunction with the V5 specific alarm reportingfunction (see annex A), then other specifications (e.g. ITU-T Recommendation X.735 [35]) are available to define this.The management information model described in the present document complements that for configuration; bothinformation models will normally share the same physical interface.SIST EN 300 378-1 V1.2.1:2003

ETSIETSI EN 300 378-1 V1.2.1 (1999-10)101ScopeThe present document specifies the Q3 interface between an Access Network (AN) and the TelecommunicationsManagement Network (TMN) for the support of fault and performance management functions for V5 interfaces, asdescribed in EN 300 324-1 [4] and EN 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 the present document.The present document 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 whichare handled by local management (e.g. the non-deferred link blocking request) or which involve implementation specificissues (e.g. faults which may result in the connection incomplete information element being used in the Bearer ChannelConnection (BCC) protocol) are outside the scope of the present document.The location of the Q3 interface to which the present document refers is specified in EN 300 376-1 [6].The present document 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 the present document is on defining the object models. Thedefinition of Operations System (OS) functionality is outside the scope of the present document.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.· References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.· For a specific reference, subsequent revisions do not appl
...