1、 ETSI TS 132 111-2 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) (3GPP TS 32.111-2 versio
2、n 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 111-2 V14.0.0 (2017-04)13GPP TS 32.111-2 version 14.0.0 Release 14Reference RTS/TSGS-0532111-2ve00 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 Si
3、ret N 348 623 562 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.
4、The content of any 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 Porta
5、ble Document Format (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 https:/portal
6、.etsi.org/TB/ETSIDeliverableStatus.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
7、or mechanical, including photocopying 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 Telecommun
8、ications Standards Institute 2017. 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 log
9、o is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 111-2 V14.0.0 (2017-04)23GPP TS 32.111-2 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present docum
10、ent 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 ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of
11、ETSI standards“, which is available 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 I
12、PRs not referenced in ETSI 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 Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to tech
13、nical specifications or reports using 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/queryfo
14、rm.asp. Modal verbs terminology In 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 “mus
15、t not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 111-2 V14.0.0 (2017-04)33GPP TS 32.111-2 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 7g3Introduction 7g31 Scope 9g32 References
16、9g33 Definitions and abbreviations . 10g33.1 Definitions 10g33.2 Abbreviations . 10g34 Basic aspects 11g34.1 Void 11g34.2 System Context 11g35 Information Object Classes 12g35.1 Imported information entities and local labels . 12g35.2 Class diagram . 12g35.2.0 Introduction. 12g35.2.1 Attributes and
17、relationships 12g35.2.2 Inheritance 13g35.3 Information Object Class Definitions . 13g35.3.1 AlarmInformation 13g35.3.1.1 Definition 13g35.3.1.2 Attribute 14g35.3.1.3 State diagram. 14g35.3.2 AlarmList . 16g35.3.2.1 Definition 16g35.3.2.2 Attribute 16g35.3.3 AlarmIRP . 17g35.3.3.1 Definition 17g35.3
18、.3.2 Attribute 17g35.3.3.3 Notification Table . 17g35.3.4 Comment . 17g35.3.4.1 Definition 17g35.3.4.2 Attribute 17g35.3.5 CorrelatedNotification 17g35.3.5.1 Definition 17g35.3.5.2 Attribute 18g35.3.6 MonitoredEntity 18g35.3.6.1 Definition 18g35.3.6.2 Attribute 18g35.4 Information relationships defi
19、nition . 19g35.4.1 relation-AlarmIRP-AlarmList (M) 19g35.4.1.1 Definition 19g35.4.1.2 Role . 19g35.4.1.3 Constraint 19g35.4.2 relation-AlarmList-AlarmInformation (M) . 19g35.4.2.1 Definition 19g35.4.2.2 Role . 19g35.4.2.3 Constraint 19g35.4.3 relation-AlarmInformation-Comment (M) . 19g35.4.3.1 Defin
20、ition 19g35.4.3.2 Role . 20g35.4.3.3 Constraint 20g3ETSI ETSI TS 132 111-2 V14.0.0 (2017-04)43GPP TS 32.111-2 version 14.0.0 Release 145.4.4 relation-AlarmInformation-CorrelatedNotification (M) . 20g35.4.4.1 Definition 20g35.4.4.2 Role . 20g35.4.4.3 Constraint 20g35.4.5 relation-AlarmedObject-AlarmI
21、nformation (M) . 20g35.4.5.1 Definition 20g35.4.5.2 Role . 20g35.4.5.3 Constraint 20g35.4.6 relation-backUpObject-AlarmInformation (O) . 21g35.4.6.1 Definition 21g35.4.6.2 Role . 21g35.4.6.3 Constraint 21g35.5 Information attribute definition 22g35.5.1 Definition and legal values . 22g35.5.2 Constra
22、ints 25g36 Interface Definition 26g36.1 Class diagram . 26g36.2 Generic rules 27g36.3 Interface AlarmIRPOperations_1 (M) 28g36.3.1 acknowledgeAlarms (M) 28g36.3.1.1 Definition 28g36.3.1.2 Input Parameters . 28g36.3.1.3 Output Parameters. 29g36.3.1.4 Pre-condition . 29g36.3.1.5 Post-condition . 29g36
23、.3.1.6 Exceptions . 30g36.3.2 getAlarmList (M) 30g36.3.2.1 Definition 30g36.3.2.2 Input Parameters . 31g36.3.2.3 Output Parameters. 32g36.3.2.4 Pre-condition . 35g36.3.2.5 Post-condition . 35g36.3.2.6 Exceptions . 35g36.4 Interface AlarmIRPOperation_2 (O) 35g36.4.1 getAlarmCount (M) 35g36.4.1.1 Defi
24、nition 35g36.4.1.2 Input Parameters . 36g36.4.1.3 Output Parameters. 36g36.4.1.4 Pre-condition . 37g36.4.1.5 Post-condition . 37g36.4.1.6 Exceptions . 37g36.5 Interface AlarmIRPOperation_3 (O) 37g36.5.1 unacknowledgeAlarms (M) 37g36.5.1.1 Definition 37g36.5.1.2 Input Parameters . 37g36.5.1.3 Output
25、Parameters. 38g36.5.1.4 Pre-condition . 38g36.5.1.5 Post-condition . 38g36.5.1.6 Exceptions . 39g36.6 Interface AlarmIRPOperation_4 (O) 39g36.6.1 setComment (M) . 39g36.6.1.1 Definition 39g36.6.1.2 Input Parameters . 39g36.6.1.3 Output Parameter 39g36.6.1.4 Pre-condition . 40g36.6.1.5 Post-condition
26、 . 40g36.6.1.6 Exceptions . 40g36.7 Interface AlarmIRPOperation_5 (O) 40g36.7.1 clearAlarms (M) 40g36.7.1.1 Definition 40g36.7.1.2 Input Parameter . 41g3ETSI ETSI TS 132 111-2 V14.0.0 (2017-04)53GPP TS 32.111-2 version 14.0.0 Release 146.7.1.3 Output Parameter 41g36.7.1.4 Pre-condition . 41g36.7.1.5
27、 Post-condition . 41g36.7.1.6 Exceptions . 42g36.8 Notification AlarmIRPNotifications_1 (M) . 42g36.8.0 Introduction. 42g36.8.1 notifyNewAlarm (M) 42g36.8.1.1 Definition 42g36.8.1.2 Input Parameters . 43g36.8.1.3 Input Parameters for notification related to security alarm . 44g36.8.1.4 Triggering Ev
28、ent . 44g36.8.1.4.1 From-state 44g36.8.1.4.2 To-state 45g36.8.2 notifyAckStateChanged (M) . 45g36.8.2.1 Definition 45g36.8.2.2 Input Parameters . 46g36.8.2.3 Triggering Event . 46g36.8.2.3.1 From-state 46g36.8.2.3.2 To-state 46g36.8.3 notifyClearedAlarm (M) . 47g36.8.3.1 Definition 47g36.8.3.2 Input
29、 Parameters . 47g36.8.3.3 Triggering Event . 47g36.8.3.3.1 From-state 47g36.8.3.3.2 To-state 48g36.8.4 notifyAlarmListRebuilt (M) 48g36.8.4.1 Definition 48g36.8.4.2 Input Parameters . 48g36.8.4.3 Triggering Event . 50g36.8.4.3.1 From-state 50g36.8.4.3.2 To-state 50g36.9 Notification AlarmIRPNotifica
30、tion_2 (O) 50g36.9.1 notifyChangedAlarm (M) . 50g36.9.1.1 Definition 50g36.9.1.2 Input Parameters . 51g36.9.1.3 Triggering Event . 51g36.9.1.3.1 From-state 51g36.9.1.3.2 To-state 51g36.10 Notification AlarmIRPNotification_3 (O) 52g36.10.1 notifyComments (M) 52g36.10.1.1 Definition 52g36.10.1.2 Input
31、 Parameters . 52g36.10.1.3 Triggering Events 52g36.10.1.3.1 From-state 52g36.10.1.3.2 To-state 53g36.11 Notification AlarmIRPNotification_4 (O) 53g36.11.1 notifyPotentialFaultyAlarmList (M) . 53g36.11.1.1 Definition 53g36.11.1.2 Input Parameters . 54g36.11.1.3 Triggering Event . 54g36.11.1.3.1 From-
32、state 54g36.11.1.3.2 To-state 54g36.12 Notification AlarmIRPNotification_5 (O) 55g36.12.1 notifyCorrelatedNotificationChanged (M) . 55g36.12.1.1 Definition 55g36.12.1.2 Input Parameters . 55g36.12.1.3 Triggering Events 55g36.12.1.3.1 From-state 55g36.12.1.3.2 To-state 56g36.13 Notification AlarmIRPN
33、otification_6 (O) 56g36.13.1 notifyChangedAlarmGeneral (M) . 56g36.13.1.1 Definition 56g3ETSI ETSI TS 132 111-2 V14.0.0 (2017-04)63GPP TS 32.111-2 version 14.0.0 Release 146.13.1.2 Input Parameters . 57g36.13.1.3 Input Parameters for notification related to security alarm . 58g36.13.1.4 Triggering E
34、vent . 58g36.13.1.4.1 From-state 58g36.13.1.4.2 To-state 59g3Annex A (normative) Event Types . 60g3Annex B (normative): Probable Causes . 61g3Annex C (informative): Examples of using notifyChangedAlarm 70g3Annex D (informative): Examples of using correlatedNotification . 72g3Annex E (informative): A
35、cknowledgeAlarms operation scenario 73g3Annex F (informative): Change history . 74g3History 75g3ETSI ETSI TS 132 111-2 V14.0.0 (2017-04)73GPP TS 32.111-2 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of
36、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 and an increase in version number as follows: Vers
37、ion 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. technical enhancements, corrections, updates, etc. z the th
38、ird 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 Aspects; Telecommunication management; as identified
39、 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-6 “Fault Management; Part 6: Alarm Integration Reference Point (IRP): Solution Set (SS) definitions. The prese
40、nt document is part of a set of TSs which describes 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 6 and 3GPP TS 32.102 7. A 3GPP system is composed of a multitude of Ne
41、twork Elements (NE) of various types and, typically, different vendors 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
42、 cases, lead to the complete unavailability of the 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;
43、 isolate the failures (autonomously 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 ro
44、utines; and, - repair/eliminate 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 QoS as far as p
45、ossible. 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/decommissioning of NEs and po
46、tential operator triggered reconfiguration (these are a matter of Configuration Management). ETSI ETSI TS 132 111-2 V14.0.0 (2017-04)83GPP TS 32.111-2 version 14.0.0 Release 14FM also includes associated features in the Operations System (OS), such as the administration of alarm list, the presentati
47、on 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-2 V14.0.0 (2017-04)93GPP TS 32.111-2 version 14.0.0 Release 141 Scope The present document defines the Alarm Int
48、egration Reference Point (IRP) Information Service (IS), which addresses the alarm surveillance aspects of Fault Management (FM), applied to the Itf-N. The purpose of the AlarmIRP is to define an interface through which a “system“ (typically a Network Element Manager or a Network Element) can commun
49、icate alarm information for its managed objects to one or several Manager Systems (typically Network Management Systems). The Alarm IRP IS defines the semantics of alarms and the interactions visible across the reference point in a protocol neutral way. It defines the semantics of the operations and notifications visible in the IRP. It does not define the syntax or encoding of the operations, notifications and their parameters. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. -
