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

1、 ETSI TS 13Digital cellular telecoUniversal Mobile TelTelecommFaPart 1: 3G faul(3GPP TS 32.11TECHNICAL SPECIFICATION132 111-1 V13.0.0 (20communications system (Phaelecommunications System (LTE; munication management; Fault Management; ult management requirement111-1 version 13.0.0 Release 12016-01)

2、hase 2+); (UMTS); nts e 13) ETSI ETSI TS 132 111-1 V13.0.0 (2016-01)13GPP TS 32.111-1 version 13.0.0 Release 13Reference RTS/TSGS-0532111-1vd00 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

3、 00017 - NAF 742 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 an

4、y electronic and/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 Form

5、at (PDF) version 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 http:/portal.etsi.org/tb/statu

6、s/status.asp 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 ph

7、otocopying 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 Institut

8、e 2016. 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. GSM and the GSM logo are Trade Marks

9、registered and owned by the GSM Association. ETSI ETSI TS 132 111-1 V13.0.0 (2016-01)23GPP TS 32.111-1 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential I

10、PRs, 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 available from the ETSI Secretariat. Latest updates are a

11、vailable 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 314 (or the updates on the ETSI Web server) which

12、 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 using their 3GPP identities, UMTS identities or GSM

13、 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 In the present document “shall“, “shall not“, “shou

14、ld“, “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 deliverables except when used in direct citation. ET

15、SI ETSI TS 132 111-1 V13.0.0 (2016-01)33GPP TS 32.111-1 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34

16、 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.5 Storage and retrieval of alarms in/from the NE 1

17、2g34.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 16g34.3 Test management 16g34.4 Operators“ alarm ha

18、ndling 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 event reports 19g35.2.3 Alarm clearing 20g35.3 Re

19、trieval 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 . 21g35.5 Overview of IRPs related to Fault Mana

20、gement (FM) . 21g3Annex A (informative): General principles of alarm generation . 23g3Annex B (informative): Change history . 24g3History 25g3ETSI ETSI TS 132 111-1 V13.0.0 (2016-01)43GPP TS 32.111-1 version 13.0.0 Release 13Foreword This Technical Specification (TS) has been produced by the 3rdGene

21、ration 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 the TSG with an identifying change of release date

22、 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 incremented for all changes of substance, i.e. technica

23、l 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: Technical Specification Group Services and System A

24、spects; 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 Management; Part 3: Alarm Integration Reference Po

25、int (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 the requirements and information model necessary

26、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, different vendors, which inter-operate in a co-o

27、rdinated 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 of the respective NE. In order to minimize the eff

28、ects 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 (autonomously or through operator intervention), i.e. switc

29、h 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 failures in due time through the application of m

30、aintenance procedures. ETSI ETSI TS 132 111-1 V13.0.0 (2016-01)53GPP TS 32.111-1 version 13.0.0 Release 13This 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 Se

31、rvice (QoS) as far as possible. The latter is achieved by bringing additional/redundant equipment into operation, reconfiguring existing equipment/NEs, or by repairing/eliminating the cause of the failure. Fault Management (FM) encompasses all of the above functionalities except commissioning/decomm

32、issioning 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 alarms list, the presentation of operational state in

33、formation 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 V13.0.0 (2016-01)63GPP TS 32.111-1 version 13.0.0 Release 131 Scope The present document specifies the overall requirements for 3GPP Fau

34、lt 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 alarms, operational state data and test results acro

35、ss 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 surveillance and detection in the NEs; - notification

36、 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 data presentation and analysis at the Operations

37、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 described in 19. Clause 5 of the present document de

38、fines 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. 2 References The following documents contain pro

39、visions 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 refe

40、rence, 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.601: “Telecommunication management; Configuration M

41、anagement (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: “Telecommunication management; Performance Management

42、 (PM); Concept and requirements“. 5 Void. 6 Void. ETSI ETSI TS 132 111-1 V13.0.0 (2016-01)73GPP TS 32.111-1 version 13.0.0 Release 137 Void. 8 Void. 9 ITU-T Recommendation X.733: “Information technology - Open Systems Interconnection - Systems Management: Alarm reporting function“. 10 Void. 11 ITU-T

43、 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 function“. 13 3GPP TS 32.111-2: “Telecommunication ma

44、nagement; 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 requirements“. 20 3GPP TS 28.625: “State managem

45、ent 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) Integration Reference Point (IRP); Information Ser

46、vice (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, the terms and definitions in 3GPP TS 32.101 2, 3G

47、PP 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 “Automatically Detected and Automatically Cleared“ by the

48、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 resource (e.g. network element, link) for which an o

49、perator 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 V13.0.0 (2016-01)83GPP TS 32.111-1 version 13.0.0 Release 13undesired 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 not. In such context, the NM may receive alarms that