ETSI TS 132 111-1-2017 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fault Manageme.pdf

1、 ETSI TS 132 111-1 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Fault Management; Part 1: 3G fault management requirements (3GPP TS 32.111-1 version 14.0.0 Release 14) TECHNICAL SP

2、ECIFICATION ETSI ETSI TS 132 111-1 V14.0.0 (2017-04)13GPP TS 32.111-1 version 14.0.0 Release 14Reference RTS/TSGS-0532111-1ve00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742

3、 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and

4、/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version

5、 kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatu

6、s.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocop

7、ying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017

8、. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of

9、 its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 111-1 V14.0.0 (2017-04)23GPP TS 32.111-1 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETS

10、I. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is availab

11、le from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). 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 ETSI SR 000

12、 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports u

13、sing their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology I

14、n the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI de

15、liverables except when used in direct citation. ETSI ETSI TS 132 111-1 V14.0.0 (2017-04)33GPP TS 32.111-1 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 6g32 References 6g33 Definitions and abbreviation

16、s . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Fault Management concept and requirements 8g34.0 Introduction 8g34.1 Faults and alarms 9g34.1.0 Introduction. 9g34.1.1 Fault detection 9g34.1.2 Generation of alarms . 10g34.1.3 Clearing of alarms . 11g34.1.4 Alarm forwarding and filtering . 12g34.1.

17、5 Storage and retrieval of alarms in/from the NE 12g34.1.6 Fault Recovery 12g34.1.7 Configuration of Alarms . 13g34.1.8 Correlation of Alarms and Events . 14g34.1.9 Root Cause Analysis . 14g34.1.10 Managed Alarm 14g34.2 State Management 15g34.2.0 Introduction. 15g34.2.1 Propagation of state change 1

18、6g34.3 Test management 16g34.4 Operators alarm handling 17g34.5 Quality of Alarms . 18g35 Fault Management over Itf-N . 18g35.1 Fault Management concept. 18g35.2 Management of alarm event reports . 19g35.2.1 Mapping of alarm and related state change event reports . 19g35.2.2 Real-time forwarding of

19、event reports 19g35.2.3 Alarm clearing 20g35.3 Retrieval of alarm information . 20g35.3.0 Introduction. 20g35.3.1 Retrieval of current alarm information on NM request. 20g35.3.2 Logging and retrieval of alarm history information on NM request . 21g35.4 Co-operative alarm acknowledgement on the Itf-N

20、 . 21g35.5 Overview of IRPs related to Fault Management (FM) . 21g3Annex A (informative): General principles of alarm generation . 23g3Annex B (informative): Change history . 24g3History 25g3ETSI ETSI TS 132 111-1 V14.0.0 (2017-04)43GPP TS 32.111-1 version 14.0.0 Release 14Foreword This Technical Sp

21、ecification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by t

22、he TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is increm

23、ented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rdGeneration Partnership Project: Te

24、chnical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.111-1 “Fault Management; Part 1: 3G fault management requirements“. 32.111-2 “Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“. 32.111-3 “Fault M

25、anagement; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. 32.111-6 “Fault Management; Part 6: Alarm Integration Reference Point (IRP): Solution Set (SS) definitions“. The present document is part of a TS-family, which describes

26、the requirements and information model necessary for the Telecommunication Management (TM) of 3GPP systems. The TM principles and TM architecture are specified in 3GPP TS 32.101 2 and 3GPP TS 32.102 3. A 3GPP system is composed of a multitude of Network Elements (NE) of various types and, typically,

27、 different vendors, which inter-operate in a co-ordinated manner in order to satisfy the network users communication requirements. The occurrence of failures in a NE may cause a deterioration of this NEs function and/or service quality and will, in severe cases, lead to the complete unavailability o

28、f the respective NE. In order to minimize the effects of such failures on the Quality of Service (QoS) as perceived by the network users it is necessary to: - detect failures in the network as soon as they occur and alert the operating personnel as fast as possible; - isolate the failures (autonomou

29、sly or through operator intervention), i.e. switch off faulty units and, if applicable, limit the effect of the failure as much as possible by reconfiguration of the faulty NE/adjacent NEs; - if necessary, determine the cause of the failure using diagnosis and test routines; and, - repair/eliminate

30、failures in due time through the application of maintenance procedures. This aspect of the management environment is termed “Fault Management“ (FM). The purpose of FM is to detect failures as soon as they occur and to limit their effects on the network Quality of Service (QoS) as far as possible. Th

31、e latter is achieved by bringing additional/redundant equipment into operation, reconfiguring existing equipment/NEs, or by repairing/eliminating the cause of the failure. ETSI ETSI TS 132 111-1 V14.0.0 (2017-04)53GPP TS 32.111-1 version 14.0.0 Release 14Fault Management (FM) encompasses all of the

32、above functionalities except commissioning/decommissioning of NEs and potential operator triggered reconfiguration (these are a matter of Configuration Management (CM), cf. TS 32.600 19). FM also includes associated features in the Operations System (OS), such as the administration of a pending alar

33、ms list, the presentation of operational state information of physical and logical devices/resources/functions, and the provision and analysis of the alarm and state history of the network. ETSI ETSI TS 132 111-1 V14.0.0 (2017-04)63GPP TS 32.111-1 version 14.0.0 Release 141 Scope The present documen

34、t specifies the overall requirements for 3GPP Fault Management (FM) as it applies to the Network Elements (NE), Element Manger (EM) and Network Manager (NM). Clause 4 defines the FM concept and functional requirements for the detection of faults and the generation, collection and presentation of ala

35、rms, operational state data and test results across 3GPP systems. These functions are described on a non-formal level since the formal standardization of these functions across the different vendors equipment is not required. The functional areas specified in the present document cover: - fault surv

36、eillance and detection in the NEs; - notification of alarms (including alarm cease) and operational state changes; - retrieval of current alarms from the NEs; - fault isolation and defence mechanisms in the NEs; - alarm filtering; - management of alarm severity levels; - alarm and operational state

37、data presentation and analysis at the Operations System (OS); - retention of alarm and operational state data in the NEs and the OS; and - the management of tests. Any (re)configuration activity exerted from the EM as a consequence of faults will not be subject of the present document. These are des

38、cribed in 19. Clause 5 of the present document defines the functional requirements for the standard Itf-N, for the purpose of Fault Management of 3GPP systems , as seen from the Network Manager (NM). The Itf-N is fully standardized so as to connect systems of any vendor to the NM via this interface.

39、 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, subsequen

40、t revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 32.60

41、1: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements“. 2 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GPP TS 32.401: “Tel

42、ecommunication management; Performance Management (PM); Concept and requirements“. 5 Void. 6 Void. ETSI ETSI TS 132 111-1 V14.0.0 (2017-04)73GPP TS 32.111-1 version 14.0.0 Release 147 Void. 8 Void. 9 ITU-T Recommendation X.733: “Information technology - Open Systems Interconnection - Systems Managem

43、ent: Alarm reporting function“. 10 Void. 11 ITU-T Recommendation X.735: “Information technology - Open Systems Interconnection - Systems Management: Log control function“. 12 ITU-T Recommendation X.745: “Information technology - Open Systems Interconnection - Systems Management: Test management func

44、tion“. 13 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP); Information Service (IS)“. 14 Void. 15 Void. 16 Void. 17 Void. 18 NGMN Top OPE Recommendations V1.0. 19 3GPP TS 32.600: “Configuration Management (CM); Concept and high-level

45、 requirements“. 20 3GPP TS 28.625: “State management data definition Integration Reference Point (IRP); Information Service (IS)“. 21 3GPP TS 32.302: “Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS)“. 22 3GPP TS 32.332: “Notification Log (NL) I

46、ntegration Reference Point (IRP); Information Service (IS)“. 23 ANSI/ISA standard 18.2 -2009: “Management of Alarm Systems for the Process Industries “. 24 3GPP TS 21.905: “Vocabulary for 3GPP Specifications“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document,

47、the terms and definitions in 3GPP TS 32.101 2, 3GPP TS 32.102 3, 3GPP TS 21.905 24 and the following apply: active alarm: An alarm that has not been cleared and which is active until the fault that caused the alarm is corrected and a “clear alarm“ is generated. ADAC Faults: Faults that are “Automati

48、cally Detected and Automatically Cleared“ by the system when they occur and when they are repaired. ADMC Faults: Faults that are Automatically Detected by the system when they occur and Manually Cleared by the operator when they are repaired. alarm: An alarm signifies an undesired condition of a res

49、ource (e.g. network element, link) for which an operator action is required. It emphasizes a key requirement that operators (above Itf-N) should not be informed about an ETSI ETSI TS 132 111-1 V14.0.0 (2017-04)83GPP TS 32.111-1 version 14.0.0 Release 14undesired condition unless it requires operator action. Use of this emphasis does not exclude this case: In certain context, it is not possible for alarm reporters (below Itf-N) to know whether a particular undesired condition requires operator action or no